hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.1.2 Gateway Control Session Establishment during BBERF Relocation | Figure 7.7.1.2-1: Gateway Control Session Establishment during BBERF Relocation
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Establishment between the BBERF in the VPLMN and the H-PCRF over... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2 Gateway Control Session Termination | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2.1 GW (BBERF)-Initiated Gateway Control Session Termination | Figure 7.7.2-1: BBERF-Initiated Gateway Control Session Termination
1. The GW (BBERF) is requested to terminate its Gateway Control Session.
2. The GW (BBERF) initiates a Gateway Control Session Termination towards the H-PCRF. If the GW (BBERF) is deployed in a visited network, this procedure is initiated by the GW (BB... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.2.2 PCRF-Initiated Gateway Control Session Termination | Figure 7.7.2-2: PCRF-Initiated Gateway Control Session Termination
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control Session Termination between the BBERF in the VPLMN and the H-PCRF over S9 based on PD... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.3 Gateway Control and QoS Rules Request | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.3.1 General | There are two cases considered for a Gateway Control and QoS Rules Request depending on the parameters the GW (BBERF) receives:
Case A: In case the GW (BBERF) action does not depend on the subsequent IP‑CAN session modification, the GW (BBERF) can acknowledge the request after interacting with the PCRF.
NOTE 1: If QoS ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.3.2 Event reporting for PCEF in visited network and locally terminated Gxx interaction | This procedure is only used for the event reporting for a PCEF in the visited network and when the Gxx interaction is locally terminated at the V-PCRF.
Figure 7.7.3-2: Event reporting for PCEF in visited network and locally terminated Gxx interaction
1. The GW (BBERF) is requested to report an event for a Gateway Contr... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.4 Gateway Control and QoS Rules Provision | Figure 7.7.4-1: Gateway Control and QoS Rules Provision
This procedure concerns both roaming and non-roaming scenarios. In the roaming case when a Gateway Control Session is used, the V-PCRF should proxy the Gateway Control and QoS Rules Provision between the BBERF in the VPLMN and the H-PCRF over S9 based on PDN-Id an... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.7.5 Void | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.8 Change in subscription for MPS priority services | Once the PCRF receives a notification of a change in MPS EPS Priority, MPS Priority Level and/or IMS Signalling Priority from the SPR, the PCRF shall make the corresponding policy decisions (i.e. ARP and/or QCI change) and initiates the necessary IP-CAN session modification procedure(s) to apply the change. |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9 Procedures over Sy reference point | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9.1 Initial Spending Limit Report Request | This clause describes the signalling flow for the H-PCRF to request the status of the policy counters available at the OCS and to subscribe to spending limit reporting (i.e. to notifications of policy counter status changes) by the OCS. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9.2 Intermediate Spending Limit Report Request | This clause describes the signalling flow for the H-PCRF to request the status of additional policy counters available at the OCS or to unsubscribe from spending limit reporting. If the H-PCRF provides the list of policy counter identifier(s), the OCS returns the policy counter status per policy counter identifier prov... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9.3 Final Spending Limit Report Request | This clause describes the signalling flow for the H-PCRF to cancel the subscriptions to status changes for the policy counters available at the OCS.
Figure 7.9.3: Final Spending Limit Report Request
1. The H-PCRF decides that notifications of policy counter status changes are no longer needed.
2. The H-PCRF sends a Fin... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9.4 Spending Limit Report | This clause describes the signalling flow for the OCS to notify the change of the status of the subscribed policy counters available at the OCS for that subscriber. Alternatively, the signalling flow can be used by the OCS to provide one or more pending statuses for a subscribed policy counter together with the time th... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.9.5 Sy Session Termination | This clause describes the signalling flow for the OCS to terminate the Sy session of a subscriber. This feature is optional.
NOTE 1: When the PCRF supports this procedure and a subscriber is removed from an OCS system, the existing Sy session of the subscriber can be terminated by this procedure.
Figure 7.9.5: Sy Sessi... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.10 Procedures over Np reference point | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.10.1 Report RAN user plane congestion information to PCRF | This clause describes the signalling flow for reporting RUCI (RAN User Plane Congestion Information) from the RCAF to the PCRF. Any RUCI changes shall be reported by RCAF unless reporting restrictions apply.
Two types of messages are used on Np for transfer of congestion information from RCAF to PCRF:
- Non-aggregated ... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.10.2 PCRF provided reporting restrictions | This clause describes the signalling flow for adding, updating or removing reporting restrictions for a given UE and APN. A pre-condition for this procedure is that the RCAF has already performed RUCI reporting for the given UE and APN. The PCRF stores the RCAF identity for the given UE when the RCAF performs RUCI repo... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.10.3 UE mobility between RCAFs | This clause describes the handling mobility of a UE from one RCAF to a different RCAF. The PCRF applies the rules described in clause 6.1.15.3.
The process is shown in Figure 7.10.3 below for the case when the UE is affected by congestion at RCAF2 after the UE was earlier affected by congestion at RCAF1.
Figure 7.10.3:... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.11 Procedures over Nt reference point | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.11.1 Negotiation for future background data transfer | This procedure enables the negotiation between the SCEF and the H-PCRF about the time window and the related conditions for future background data transfer (as described in clause 6.1.16). The interaction between the SCEF and the H-PCRF is not related to an IP-CAN session and the H-PCRF associates the information provi... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.12 Procedures for management of PFDs | |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.12.1 PFD Retrieval by the PCEF/TDF ("Pull mode") | This procedure enables the PCEF/TDF to retrieve PFDs for an Application Identifier from the PFDF when a PCC/ADC Rule with an Application Identifier is provisioned/activated and PFDs provisioned by the PFDF are not available at the PCEF/TDF.
In addition, this procedure enables the PCEF/TDF to retrieve PFDs from the PFDF... |
5817f2cb61f7e615e7879961cd761fa6 | 23.203 | 7.12.2 Management of PFDs in the PCEF/TDF ("push mode") | This procedure enables the provisioning, modification or removal of PFDs associated with an application identifier in the PCEF/TDF via PFDF. Either the complete list of all PFDs of all application identifiers, the complete list of all PFDs of one or more application identifiers or a subset of PFDs for individual applic... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 1 Scope | The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authe... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 3 Definitions and abbreviations | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following definitions apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]:
Converged IP Messaging: as defined in OMA-RD-CPM-V1_0 [15]. Converged IP... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply:
CPM Converged IP Messaging
IM Instant Message
IMDN Instant Message Disposition Notification
IP‑SM‑GW IP-Short-Message-Gateway
ISF Interworking Selection Function
SM Short Message |
b57c39c719229455cea55c4a75308a42 | 23.204 | 4 Void | 4a Architecture Requirements
4a.1 General
The SMS-IP architecture supports the following:
- Notification shall be sent to the HSS that a previously unreachable UE is now reachable.
- Functionality is required to be able to select the domain for message delivery between IMS and CS/PS, and to have the message delivered t... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5 Architecture model and reference points | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.1 Reference architecture | Figure 5.1 below shows the overall architecture for providing SMS over a generic IP CAN.
Figure 5.1: Architecture for providing SMS over a generic IP-CAN
NOTE: Nodes specific to the CPM functions such as ISF are either collocated with the IP-SM-GW or else are not shown. |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2 Reference points | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.1 General | The clauses below describe the needed enhancements and specific considerations to existing interfaces in order to support SMS over a generic IP-CAN. |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.2 C/S6c interface | The C or S6c interface allows the SMS-GMSC, using MAP or a Diameter based protocol, to obtain the address of the IP-Message-GW via mechanisms described in clause 5.3. |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.3 Interface between the IP-SM-GW and the HLR/HSS | The interface(s) between the IP-SM-GW and the HLR/HSS is used for:
- Supporting the registration and de-registration from the IP-SM-GW to the HLR/HSS for SMS delivery.
- Forwarding of the Send Routeing Information for Short Message requests from HLR/HSS to IP-SM-GW in order to return the address where the SM should be ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.4 E/Gd/Gdd/SGd interface | The E/Gd/Gdd/SGd interface allows the IP-SM-GW to connect to the SMS‑GMSC, appearing to the SMS‑GMSC as an MSC, SGSN, MME or SMSF.
For interworking with SMS in MME as defined in TS 23.272 [22], Annex C, an IWF may be used as described in that clause.
For interworking with an SGSN supporting the Gdd interface, an IWF ma... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.5 ISC interface | The ISC interface allows the IP-SM-GW to forward the receiving message to the SIP based UE via IMS core. |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.2.6 Void | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3 Functional entities | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3.1 IP-Short-Message-Gateway (IP-SM-GW) | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3.1.1 General | The IP-SM-GW shall provide the protocol interworking for delivery of the short message between the IP-based UE and the SMS-SC. The message is routed to the SMS-SC for delivery to the SMS-based user or the message is received from the SMS-SC of an SMS-based UE for delivery to an IP-based UE.
The general functions of the... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3.1.2 Transport-level interworking | The additional functions of the IP-SM-GW when interworking is done by carrying encapsulated Short Messages in IMS messages are:
- to communicate with the UE using IMS messaging as transport while maintaining the format and functionality of the Short Message;
- to carry the SMS status messages as encapsulated bodies of ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3.1.3 Service-level interworking | The additional functions of the IP-SM-GW when service-level interworking is done between Short Messages and Instant Messages in IMS are:
- to determine whether to transform the message format or not, and to perform the transformation of the message format when determined.
- to use the SC address retrieved either as par... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 5.3.2 HSS/UDM | In order to support SMS over generic IP access, the HSS/UDM shall support the following functions:
- storing the pre-configured address of the IP-SM-GW on a subscriber basis;
NOTE: If all subscribers are assigned to a single IP‑SM‑GW address, the IP‑SM‑GW address does not need to be pre-configured in the HSS.
- handlin... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6 Procedures | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.0 General | The clause describes the procedures for the support of transport-level interworking between Short Message service and encapsulated Short Message via IP service, for the support of the service-level interworking for the Short Message service and Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12], for the... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.1 Registration procedure | Figure 6.1: Registration procedure
1) The UE establishes IP connection.
2) At any time after the establishment of the IP connection, the UE registers at the S-CSCF according to the IMS registration procedures.
NOTE 1: For simplicity, not all messages between UE and S-CSCF and between S-CSCF and HSS are shown in detail.... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.2 De-registration procedure | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.2.1 UE initiated | Figure 6.2: UE initiated de-registration procedure
1) At any time after the registration procedure, the UE may initiate a de-registration procedure. The UE sends a De-Register request (Register request with Expires header having value 0) to the S-CSCF.
2) S-CSCF responds to the UE with OK.
3) S-CSCF checks the initial ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.2.2 Network initiated | Figure 6.2a: Network initiated de-registration procedure
1) After receiving a trigger (e.g. De-Register message from the S‑CSCF), the IP‑SM‑GW shall de-register the IP‑SM‑GW of a subscriber from the HSS sending a De-Register Req.
2) The HSS de-registers the UE and responds to the IP‑SM‑GW (AS) with De‑register Res. |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.3 Transport-level interworking: Successful encapsulated Short Message origination procedure with MSISDN | Figure 6.3: Successful encapsulated Short Message origination procedure
1) The UE registers to S-CSCF according the IMS registration procedure. Note that I-CSCF and P-CSCF are not shown in this figure.
2) UE submits the encapsulated Short Message (SMS-SUBMIT, SC Address) to the S-CSCF using an appropriate SIP method.
3... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.4 Transport-level interworking: Successful encapsulated Short Message termination procedure from SMS-GMSC | Figure 6.4: Successful encapsulated Short Message termination procedure
1) The UE registers to the S-CSCF according to the IMS registration procedure.
2) The SMS-SC forwards the Short Message (SMS‑DELIVER) to the SMS-GMSC.
3) Steps 3a to 3c are performed if SMS GMSC interrogates the HSS with MSISDN. For MT-SMS without ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.5 Transport-level interworking: Delivery Report procedure | Figure 6.5: Delivery report procedure
1) The UE has received the Short Message as described in clause 6.4 or clause 6.4a.
2) The UE sends a Delivery report (SMS‑DELIVER‑REPORT) to the S-CSCF, including either a positive or a negative acknowledgement to the Short Message received in step 1.
3) The S-CSCF forwards the D... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.6 Transport-level interworking: Alert service centre procedure when memory capacity is available | If the HLR/HSS has recorded the MWD with a failure reason that the message failed to be sent by IP‑SM‑GW due to the memory capacity of the UE is exceeded, once the HLR/HSS receives a message from any of the domain indicating that the memory capacity of the UE is available again, e.g. form the IMS, PS or CS domain, the ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.7 Service-level Interworking: IM or CPM capable UE sends an Instant Message to an SMS user | Figure 6.7: Successful IM origination to SMS procedure
1) The UE registers to S-CSCF according the IMS registration procedure.
2) UE submits the Instant Message to the S-CSCF using an appropriate SIP method. The UE may request to hide its Public User Identity from the recipient within the Instant Message, as described ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.8 Interaction between transport-level and service-level Interworking | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.8.1 General | The interaction between transport-level interworking (between SMS over CS/PS and SMS over IMS) and service-level interworking (between Instant Messaging and SMS) depends on the user subscription and authorisation, on the UE capabilities, and on operator policy.
If a user is only subscribed to either transport-level int... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.8.2 IMS Originating | In the originating network, a UE sends a SIP MESSAGE (Encapsulated Short Message or Instant Message). The originating S‑CSCF forwards the SIP MESSAGE to the IP-SM-GW based on the iFC. The subscription of the transport level interworking and the service level interworking applies for different iFC. However, the SIP MESS... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.8.3 IMS Terminating | When the IP-SM-GW receives a Short Message from the legacy network on the terminating side, it performs the domain selection to determine the preferred domain to transfer the short message. If the selected network is IMS, the IP-SM-GW will determine whether the transport level interworking or the service level interwor... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.9 Service-level Interworking: Concatenated Short Messages delivered as a large Instant Message | An IMS registered user with IM service or CPM service receives a concatenated short message delivered as two or more short messages. The information below describes the behaviour when the received concatenated Short Message exceeds the maximum payload size of an Instant Message.
Figure 6.9: Concatenated Short Messages ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.10 Service-level interworking: Status Report procedure for Instant Message to Short Message interworking | Figure 6.10: Status report procedure for Instant Message to Short Message interworking
1) An Instant Message from the UE is successfully delivered to the SMS user after service-level interworking. The original Instant Message requested a Disposition Notification.
NOTE 1: A Disposition Notification can be requested in t... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.11 IM or CPM user sends an Instant Message to an SMSIP UE | An IMS registered user with SIMPLE IM service or CPM service sends an Instant Message via service-level interworking as an encapsulated Short Message to an SMSIP UE, which did not indicate support for SIMPLE IM or CPM when registering to IMS.
NOTE 1: Based upon user subscription and depending on network deployment, oth... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.12 Delivery report for an Instant Message delivered as encapsulated Short Message | This procedure follows the procedure described in clause 6.11, when the original Instant Message included a delivery notification request.
Figure 6.12: Delivery report after a successful Instant Message to encapsulated Short Message procedure
NOTE: An encapsulated Short Message has been sent successfully according to t... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.13 Service-level interworking: IM or CPM capable UE sends an Instant Message to an SMS user with Interworking in the terminating side | This procedure describes the delivery of an Instant Message to a registered or an un-registered IMS subscriber. For the unregistered case, the S‑CSCF forwards the Instant Message to the IP‑SM‑GW based on the unregistered iFC of the subscriber.
Figure 6.13: Successful IM terminating to SMS procedure with Interworking in... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.14 Service-level interworking: IM or CPM user receives Short Message from an SMS user | An IMS registered user with SIMPLE IM or CPM service receives a Short Message formatted via service-level interworking to an Instant Message.
Figure 6.14: Successful IM termination after service-level interworking
1) The UE registers to the S-CSCF according to the IMS registration procedure.
2) The SMS-SC forwards a Sh... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.15 Service-level Interworking: CPM capable UE sends a Chat session invitation to an SMS user | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.15.1 IP-SM-GW in the originating network | Figure 6.15.1: Chat session invitation to SMS user and Message data exchange (IP-SM-GW in originating network)
1) The UE registers to S-CSCF according to the IMS registration procedure.
2) The UE sends a session invitation request for a chat session to the S-CSCF, using the appropriate SIP method. The UE may request to... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.15.2 IP-SM-GW in the terminating network | The SMS user (SMS UE B) in this flow is a CPM user (CPM user B) whose preferences are set in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.15.2: Chat session invitation to SMS user and message data exchange (IP-SM-GW in terminating network)
1) The originating network for CPM user A ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.16 Service-level Interworking: CPM capable UE tearing down a Chat session between a CPM user and an SMS user | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.16.1 IP-SM-GW in the originating network | Figure 6.16.1: Chat session teardown request to SMS (IP-SM-GW in originating network)
1) The CPM UE sends a SIP BYE for an ongoing session to the S-CSCF.
2) S-CSCF forwards the session teardown request to the IP-SM-GW. The IP-SM-GW performs service-level interworking by converting the session teardown request to a Shor... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.16.2 IP-SM-GW in the terminating network | The SMS user (SMS user B) in this flow is a CPM user (CPM user B) who has set his preferences in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.16.2: Chat session teardown request to SMS (IP-SM-GW in terminating network)
1) The CPM user's originating network sends a session teardown ... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.17 Service-level Interworking: SMS user requesting the IP-SM-GW to tear down the Chat session between a CPM user and an SMS user | |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.17.1 IP-SM-GW in the originating network | Figure 6.17.1: Chat session teardown request to CPM UE (IP-SM-GW in originating network)
1) A message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accordance to steps 2 to 4 and steps 10 to 13 of clause 6.14, with the operator defined Short Message indicating the SMS user wants to leave the chat s... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.17.2 IP-SM-GW in the terminating network | The SMS user in this flow is a CPM user who has set his preferences in his home network to receive his incoming chat sessions as Short Messages.
Figure 6.17.2: Chat session teardown request to CPM UE (IP-SM-GW in terminating network)
1) A message is received from the SMS user via the SMS-GMSC by the IP-SM-GW, in accord... |
b57c39c719229455cea55c4a75308a42 | 23.204 | 6.18 Service-level interworking: Status Report procedure for chat session message to Short Message interworking | Figure 6.18: Status report procedure for chat session message to Short Message interworking 1) A chat session message from the UE is successfully delivered to the SMS user after service-level interworking according to clause 6.15. The chat session message requested a success or failure delivery report. NOTE 1: A Reques... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 1 Scope
| The present document specifies the architecture, procedures and information flows necessary for the CAPIF. The aspects of this specification include identifying architecture requirements for the CAPIF (e.g. registration, discovery, identity management) that are applicable to any service APIs when used by northbound ent... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 3 Definitions and abbreviations
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
API: The means by which an API invoker can access the service.
API invok... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
5GS 5G System
AEF API Exposing Function
AF Application Functio... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4 Architectural requirements
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.1 General
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.1.1 Introduction
| This subclause specifies the general requirements for CAPIF architecture.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.1.2 Requirements
| [AR-4.1.2-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations.
[AR-4.1.2-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from the API providers.
[AR-4.1.2-c] Reference points between CAPIF and exte... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.1.3 Requirements for supporting 3rd party API providers
| [AR-4.1.3-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations from trusted 3rd party API providers.
[AR-4.1.3-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from trusted 3rd party API providers.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.2 Service API publish and discover
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.2.1 Introduction
| This subclause specifies the service API publish and discover related requirements.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.2.2 Requirements
| [AR-4.2.2-a] The CAPIF shall provide a mechanism to publish the service API information to be used by the API invokers to discover and subsequently invoke the service API.
[AR-4.2.2-b] The CAPIF shall provide a mechanism for the API invokers to discover the published service API information as specified in [AR-4.2.2-a... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.2.3 Requirements for 3rd party API providers
| [AR-4.2.3-a] The CAPIF shall provide a mechanism to publish the service API information of the 3rd party API providers.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.3 Security
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.3.1 Introduction
| This subclause specifies the security related requirements for API invokers.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.3.2 Requirements
| [AR-4.3.2-a] The CAPIF shall provide mechanisms to hide the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain.
[AR-4.3.2-b] The CAPIF shall provide mechanisms to authenticate API invokers prior to accessing the service APIs.
[AR-4.3.2-c] The CAPIF sh... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.3.3 Additional requirements for 3rd party API provider
| [AR-4.3.3-a] The CAPIF shall provide mechanisms to hide the topology of the 3rd party API provider trust domain from the API invokers accessing the service APIs from outside the 3rd party API provider trust domain.
[AR-4.3.3-b] The CAPIF shall provide authorization mechanism for service APIs from the 3rd party API pro... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.4 Charging
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.4.1 Introduction
| This subclause specifies the charging related requirements for the usage of service APIs.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.4.2 Requirements
| [AR-4.4.2-a] The CAPIF shall support online and offline charging for service APIs usage.
[AR-4.4.2-b] The CAPIF shall provide mechanisms to record the usage (e.g. invocation count) of the service APIs for charging purpose, on a per API invoker basis.
[AR-4.4.2-c] The CAPIF shall provide mechanisms to record timestamp... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.4.3 Requirements for 3rd party API providers
| [AR-4.4.3-a] The CAPIF shall support online and offline charging for 3rd party API providers' service APIs usage.
[AR-4.4.3-b] The CAPIF shall provide mechanisms to query charging related information of the 3rd party service APIs by the authorized users.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.5 Operations, Administration and Maintenance
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.