hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.12.2 Procedures
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.12.2.1 Short Message routing to Emergency Response Centre via SMS over IP
| During EPS/5GS registration, the UE indicates its capability to support SMS over IP and/or SMS over NAS. The serving network also indicates its capability to support these services in the registration response.
If the serving network has provided the above-mentioned SMS over IP indication, and the UE decide to use SMS... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.12.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- The UE needs to support sending and receiving feature support flag for emergency SMS over IP and/or SMS over NAS.
- The UE needs to support the IMS emergency registration when the UE needs to send an SMS to the emergency centre.
P/S/E-CSCF:
- P-CSCF needs to select E-C... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13 Solution #13: Enhanced E-CSCF for SMS over IP Routing to Appropriate PSAP
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.0 High level principles
| This solution addresses KI#3.
The E-CSCF functionality is expanded to support the SIP MESSAGE handling, routing decisions, policy control, and managing roaming messaging failures.
The SMS to EC message is primarily identified by the Emergency Service URN in the Request-URI. An explicit emergency service indication ca... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.1 Description
| The proposed solution integrates SMS to EC functionality into the IMS core by enhancing the E-CSCF to manage SMS to EC handling, routing, location, and policy decisions. The entire architecture maintains consistency across both EPS and 5GS core networks.
The UE supports SMS over IP as specified in TS 23. 204, and is c... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.1.1 Deployment with ESInet
| The ESInet (Emergency Services IP Network) is defined by NENA i3 standard, NENA-STA-024.1.1-2025 [20]. The ESInet is the fundamental IP infrastructure for Next Generation 9-1-1 (NG9-1-1) [21], enabling the direct reception of multimedia emergency communications (voice, text, video, and data) at the PSAP with SIP signal... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.1.2 Deployment without ESInet
| For deployments without an ESInet, the E-CSCF routes the SIP MESSAGE to the IP-SM-GW. The IP-SM-GW performs the essential SIP-to-MAP/Diameter conversion and delivers the converted message via the SMS-GMSC to the PSAP Gateway that supports the legacy Text-to-9-1-1 interface, ATIS J-STD-110 [22].
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.1.3 Callback
| If the UE was already registered to the IMS network for normal services, that session has associated Public User Identity and TEL-URI would generally be known to the S-CSCF and the HSS/UDM. This prior binding can be used for callback with normal messaging service.
When the UE performs an IMS Emergency Registration, ba... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.1.4 Roaming
| For roaming users, the VPLMN's Enhanced E-CSCF handles the entire routing process via local breakout, ensuring the message is routed to the local PSAP serving the UE's current location, thereby satisfying local emergency regulation.
However, if the UE is unable to complete the SMS to EC request because the VPLMN's IMS... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.2 Procedures
| Figure 6.13.2-1 shows one example call flow for SMS over IP routing to appropriate PSAP.
Figure 6.13.2-1: Delivery of SMS to EC with SMS over IP
1. For a UE detectable SMS to EC, the UE first detects the emergency intent. The UE initiates the service using an IMS Emergency Registration if one is required, as specif... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.13.3 Impacts to Services, Entities and Interfaces
| P-CSCF:
- Recognize the SMS to EC messaging indication, e.g. Emergency Service URN in the SIP MESSAGE Request-URI, and forward the request to E-CSCF.
E-CSCF:
- Handle SIP MESSAGE with emergency indication, and route the message to the proper PSAP.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14 Solution #14: Short Message Service over IP to Emergency Centre Leveraging IMS Emergency Framework
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.0 High-level solution Principles
| This solution addressed Key Issue #3: SMS over IP Routing to Appropriate PSAP.
The principle proposed is to re-use the IMS emergency call framework when the UE attempts to send an SMS2EC so that the SMS is routed to the IMS of the serving network rather than by the IMS of the user's home PLMN.
The UE includes in the ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.1 Description
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.1.1 UE in VPLMN
| The description of this solution is as follows:
- A UE that supports SMS2EC starts the procedure to send an SMS2EC when the user requests to send an SMS to a known emergency number (stored in the USIM, stored in the UE, received from the serving network) and the serving network has indicated support for SMS2EC.
- The... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.1.2 Other scenarios
| If the UE is not roaming the same procedure as described in clauses 6.14.2.1 and 6.14.2.2 can be reused with the difference that the UE can use the existing IMS registration and submit the SIP MESSAGE with the SMS2EC to the P-CSCF.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.2 Procedures
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.2.1 High Level Procedure for SMS2EC over IP
| The following flow describes how an SMS2EC over IP is delivered to the appropriate PSAP when the UE is roaming and does not have sufficient credentials to access the IMS of the serving PLMN.
Figure 6.14.2.1-1: High level procedure for UE Detected SMS2EC over IP in VPLMN
The steps follow the UE Detected Emergency Se... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.2.2 SMS2EC over IP in VPLMN
| The following flow describes SMS2EC over IP delivery procedure when the UE is in VPLMN .
Figure 6.14.2.2-1: Emergency SMS delivery procedure
0. The UE performs DNS procedure to obtain the address of the P-CSCF of the serving network.
1. The UE encapsulates the SMS2EC in SIP MESSAGE request and send it to P-CSCF. T... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.14.3 Impacts on Services, Entities and Interfaces
| The following entities are impacted based on the solution above:
UE:
- Support to detect the request for the delivery of an SMS2EC.
- Support to include SMS2EC indication in SIP MESSAGE.
- Support to include "anonymous user" in SIP MESSAGE.
P-CSCF:
- Support to accept "anonymous user" for SMS2EC delivery.
- Inse... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15 Solution #15: Support of SMS to Emergency Centre over IP
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15.0 High-level solution principles
| This solution applies to KI#3.
This clause describes support for the SMS to Emergency Centre over IP.
SMS to Emergency Centre over IP in this context is an SMS over IMS using an emergency number as destination address. A key requirement for this service is that the SMS to Emergency Centre must be routed to a PSAP in ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15.1 Description
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15.1.1 General
| The proposed solution for SMS to Emergency Centre over IP enables reliability by using SIP end to end between the UE and the PSAP and enabling an actual "dialogue" between the UE and the PSAP. In case of potential subsequent voice emergency calls, the same PSAP would most probably be selected thus allowing for a better... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15.2 Procedures
|
Figure 6.15.2.1: Registration Procedure
1. The UE attaches or registers with the serving PLMN if subscribed for access and can be authenticated. The UE also performs IMS Registration according to existing mechanisms.
2. The UE detects that a user has instigated a short message (SM) to an emergency number. The UE is... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.15.3 Impacts on services, entities and interfaces
| UE:
- Identify the need to send SMS to Emergency Centre over IP based on the use of emergency numbers.
- Use the appropriate connectivity as described in step 3 of the procedure.
E-CSCF:
- Support handling of SMS to Emergency Centre.
- Support identification of the appropriate PSAP to route the SMS to Emergency Ce... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16 Solution #16: Short Message to Emergency Response Centre via SMS over IP
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16.0 High level principles
| This solution addresses KI#3.
This solution applies when the UE detects the SM to Emergency Response Centre based on the used emergency numbers.
The Short Message to Emergency Response Centre uses an emergency number or SOS URN as destination address. A key requirement for this service is that the Short Message (SM) ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16.1 Description
| This solution is only applicable for the non-roaming case.
The UE sends a SIP MESSAGE request to the P-CSCF containing a Request-URI set to SOS URN or an emergency number. The SIP MESSAGE contains the SM to the Emergency Response Centre.
The P-CSCF forwards the SIP MESSAGE to an E-CSCF that is capable of handling the... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16.2 Procedures
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16.2.1 Short Message routing to Emergency Response Centre via SMS over IP
| The serving PLMN sends an indication towards the UE during IP-CAN registration, e.g. during the 5GS Registration procedure or during E-UTRAN Attach/TAU procedure, to indicate support for SM to Emergency Response Centre over IMS. If the serving network has provided this indication, then UE performs this procedure to sen... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.16.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- The UE needs to support processing an indication whether serving PLMN supports the SM to Emergency Response Centre over IMS.
P-CSCF:
- The P-CSCF needs to select an E-CSCF and route the SIP MESSAGE request.
E-CSCF:
- The E-CSCF needs to includes the PSAP address in th... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17 Solution #17: SMS over IP delivery to Emergency Response Centre based on emergency call numbers
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.0 High level principles
| This solution aims to address KI#3 and KI#1 with the following key principles:
- The UE receives the support of SMS delivery to Emergency Response Centre indication during the IMS registration in case of non-roaming scenario, or during emergency IMS registration from VPLMN in case of roaming.
- The UE uses emergency ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.1 Description
| In this proposal, it is assumed that emergency PDU session is used to deliver the SMS over IP to Emergency Response Centre/PSAP. It is also assumed that UE is aware of the supporting capability of the network based on the solutions provided for KI#1 (e.g. UE is informed that SMS over IP delivery to Emergency Response C... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.2 Emergency IMS registration procedure
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.2.1 Emergency PDU session/PDN connection establishment in 5GS/EPS
| In order to use the SMS over IP delivery to Emergency Response Centre, the UE triggers Emergency PDU Session /PDN connection establishment procedure as specified in clause 4.3.2 of TS 23.502 [3] and clause 5.10.2 of TS 23.401 [5].
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.2.1 Emergency IMS registration in non-roaming scenario
| In order to use the SMS over IP delivery to Emergency Response Centre in non-roaming scenario, for UE-detectable SMS delivery to Emergency Response Centre, the UE performs emergency IMS registration first as described in clause 7.2 of TS 23.167 [9].
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.2.2 Emergency IMS registration in roaming scenario
| In order to use the SMS over IP delivery to Emergency Response Centre in roaming scenario, for UE-detectable SMS delivery to Emergency Response Centre, the UE performs emergency IMS registration as described in clause K.3 of TS 23.167 [9] with following additions:
8: When P-CSCF responds with 420 or 403, the P-CSCF al... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.3 MO SMS over IP delivery procedures
| The following procedures illustrate the MO SMS over IP delivery to PSAP with reference to TS 23.167 [9].
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.3.1 MO SMS over IP delivery to Emergency Response Centre using Emergency PDU session in 5GS
|
Figure 6.17.3.1-1: Successful encapsulated Short Message origination procedure
1. If the UE decides to send SMS over IP, then it sends a SIP MESSAGE containing the SMS to PSAP to the P-CSCF in the serving network containing an R-URI set to SOS URN or an emergency number. The UE may include also the UE location infor... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.3.2 MO SMS over IP delivery to Emergency Response Centre using Emergency PDN connection in EPS
| The SMS over IP delivery to Emergency Response Centre is similar to 5GS procedure with the change that the Emergency PDN connection is established to provide the IP tunnel.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.4 Non-detectable SMS to PSAP handling
| Like UE non-detectable voice calls, the UE would use the IMS PDN connection/PDU session for such cases. The network can be based on configuration, reject such attempts if the destination number is recognized as an emergency centre.
While for normal voice calls this is a function of HPLMN P-CSCF but to avoid performanc... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.17.5 Impacts to Services, Entities and Interfaces
| UE:
- Support the handling of SMS over IP delivery to Emergency Response Centre capability during IMS registration procedure, or during emergency IMS registration procedure.
- Formulates the RP-DA in the RP-DATA with serving PLMN emergency number and formulate the SIP message containing the SMS to PSAP.
P/S/E-CSCF:
... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18 Solution 18: enabling SMS over IP for conditional local routing to Emergency Response Centre
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.0 High level principles
| This solution addresses KI#1 and KI#3 by enhancing short messages delivery using SMS over IP and routing to local emergency respond centre (i.e. PSAP). This solution is proposed with the following principles:
- P1. Emergency Authentication Trigger: During Emergency Registration, the UE's request for SMS capability sha... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.1 Description
| The solution requires the following enhancements to the existing protocols and network functions:
1. Clarification of Emergency Authentication:
- When a UE performs Emergency Registration and sets the SMS requested bit in the 5GS update type IE of the Registration Request message, the IMS/Core network shall initiate ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2 Procedures
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1 MO SMS over IP in 5GS
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1.1 Emergency Registration Procedure in 5GS
| Figure 6.18.2.1.1-1 shows Emergency Registration procedure in 5GS.
Figure 6.18.2.1.1-1: Emergency Registration Procedure in 5GS
The following are the required enhancement for Emergency Registration Procedure:
1: The UE sends a Registration Request to the AMF. The message includes:
- 5GS registration type set to "... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1.2 IMS Emergency Service Registration Procedure
| Figure 6.18.2.1.2-1 shows IMS Emergency Registration procedure.
Figure 6.18.2.1.2-1: IMS Emergency Registration Procedure (VPLMN SMS for LBO Supported)
1: The UE performs emergency registration procedure.
2: The UE performs PDU Session Establishment Request Procedure indicating emergency request based on Figure 4.... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1.3 IMS Registration Procedure (VPLMN LBO Supported) for SMS over IP
| Figure 6.18.2.1.3-1 shows SIP Registration procedure in IMS network.
Figure 6.18.2.1.3-1: IMS Registration Procedure (VPLMN SMS for LBO Supported)
The following are the required enhancement for SIP Registration (Negotiating Conditional LBO Capability):
1: The UE performs normal registration procedure.
2: The UE p... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1.4 MO SMS over IP Delivery using LBO routing to local PSAP (VPLMN LBO Supported)
| Figure 6.18.2.1-4 shows MO SMS over IP Delivery using LBO routing to local PSAP.
Figure 6.18.2.1.4-1: MO SMS over IP Delivery using LBO routing to local PSAP
1: The UE performs normal registration procedure.
2: The UE performs PDU Session Establishment Request Procedure using IMS DNN/S-NSSAI based on Figure 4.3.2.... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.2.1.5 MO SMS over IP Delivery (VPLMN LBO Not Supported/Allowed - Home Routed Fallback)
| If LBO is not supported, the S-CSCF/IP-SM-GW applies the Home Routed policy. Figure 6.18.3.1-4 shows MO SMS over IP Delivery (VPLMN LBO Not Supported/Allowed- Home Routed Fallback).
If the UE performs an IMS Emergency Registration and then sends an emergency SMS, but the Visited PLMN (VPLMN) cannot support the Local B... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.18.3 Impacts to Services, Entities and Interfaces
| UE:
- Include the SMS authentication required bit in the 5GS update type IE (for NAS) to trigger immediate security context establishment for Emergency Registration procedure.
- Include a dedicated feature tag (e.g. +g.3gpp.emergency-sms-auth) in the SIP REGISTER for IMS Emergency Registration.
- Indicate support fo... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19 Solution 19: Support of Short Message Service Routing to Emergency Response Centre via IP
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.0 High level principles
| This solution addresses KI#1 and KI#3.
The principles of this solution are listed below:
Scenario 1: UE detecting SMS2EC:
- The emergency number and emergency service types of the home network and its roaming partners are configured in the UE or provided to the UE via mobility management procedures.
- If the UE sup... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.1 Description
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.1.1 UE detecting Short Message Service to Emergency Centre
| It is assumed that the emergency number and emergency service types of the home network and its roaming partners are configured in the UE or provided to the UE via mobility management procedures. The local SMSC address is configured in the UE.
If UE detects that the receiver's number is an emergency number, the establ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.1.2 UE not detecting Short Message Service to Emergency Centre
| As the UE cannot detect the emergency number, the Short Message over IP will be sent to a P-CSCF in the HPLMN. Assuming that the P-CSCF can store a configurable list of local emergency numbers and emergency service URNs. In addition, a configurable list of roaming partners' emergency numbers and emergency service URNs ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.2 Procedures
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.2.1 Procedure for MO SMS over IP in case of UE detecting SMS2EC
| The following figure depicts the mobile originating procedure for SMS over IP in case of UE detecting SMS2EC.
Figure 6.19.2.1-1: MO SMS over IP in case of UE detecting SMS2EC
1: UE registered in 5GS or EPS. Emergency Service Support indicator is provided to the UE in Attach/Registration Accept message. If the UE de... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.2.2 Procedure for MO SMS over IP in case of UE not detecting SMS2EC
| The following figure depicts the mobile originating procedure for SMS over IP in case of UE not detecting SMS2EC.
Figure 6.19.2.2-1: MO SMS over IP in case of UE not detecting SMS2EC
1a: UE setups a PDU session (or PDN connection) to transfer the Short Message to the P-CSCF in the HPLMN.
1b: The P-CSCF detects tha... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 6.19.3 Impacts to Services, Entities and Interfaces
| UE:
- Support to include emergency number, emergency service type, and UE's location in the SMS-SUBMIT TPDU part of the emergency Short Message.
- Support to include the address of SMSC in the serving PLMN in RP-DA field of the emergency Short Message, and also include the Public Service Identity (PSI) of local SMSC ... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 7 Interim Agreements
| Editor's note: This clause will capture interim agreements derived from solutions.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 8 Conclusions
| Editor's note: This clause will list conclusions that have been agreed during the course of the study item activities.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 8.1 Interim conclusions for KI#1
| Editor's note: This is not an exhaustive list containing all the conclusions necessary to conclude KI#1.
1. The serving PLMN provides the emergency number list and associated emergency service types to the UE during Registration/Attach or IMS registration procedures.
2. The UE detects the SM to Emergency Response Cen... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 1 Scope
| This TR provides guidelines for This TR provides guidelines for SEAL services usage for the benefit of the Application providers (developers/ application service provider) and application ecosystem partners (e.g., third party application platform providers).
It includes the overall introduction of SEAL layer from the... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 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.
-... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 3 Definitions of terms, symbols and abbreviations
| |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 3.1 Terms
| For the purposes of the present document, the terms 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].
For the purposes of the present document, the terms given in clause 3 of 3GPP TS 23.222 [... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 3.3 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].
For the purposes of the present document, the abbreviations give... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4 Overview of SEAL
| |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.1 The role and responsibility of SEAL within 3GPP system
| Editor's Note: This clause will describe the general role and responsibilities of SEAL layer
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.1.1 General description
| The services at this layer defined in 3GPP TS 23.434 [3], 3GPP TS 23.435 [4], 3GPP TS 23.436 [5], 3GPP TS 23.437 [6], 3GPP TS 23.438 [7], 3GPP TS 23.482 [12].
As figure 4.1.1-1 shows, SEAL is on the 3GPP services layer Services and provides the value-added services to enable application layer to utilize 3GPP n... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.1.2 The interaction with rest part of 3GPP system
|
Figure 4.1.2-1: Service based Architecture of 3GPP system supporting SEAL services
As the figure 4.1.2-1, SEAL services which are part of the 3GPP system are deployed either by the MNO or third party.
SEAL server(s) invokes service APIs exposed by 3GPP core network functions directly over the 3GPP core network SBA... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2 SEAL Entities
| Editor's Note: This clause will describe the service entities (SEAL servers and SEAL Clients) in SEAL layer.
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.1 General description
| The following service entities as shown in figure 4.2.1-1in SEAL layer are defined in 3GPP TS 23.433 [2], 3GPP TS 23.434 [3], 3GPP TS 23.435 [4], 3GPP TS 23.436 [5], 3GPP TS 23.437 [6], 3GPP TS 23.438 [7], 3GPP TS 23.482 [12].
The service entities at this layer can work independent with other entities. It is up to ope... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.2 NRM (network resource management) server/client
| Editor's Note: This clause will provide introduction of NRM server and client.
NRM server provides the value-added services by utilizing capabilities of 3GPP core network (e.g., NEF/PCF/MBSMF). It enables third party‘s application (application server or application client) to request 3GPP system to provide QoS service... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.3 SEALDD (service enabler architecture layer) server/client
| Editor's Note: This clause will provide introduction of SEALDD server and client.
SEALDD server provides application layer data(content) storage and forwarding services utilizing 3GPP network capabilities. By caching content closer to end users and co-operating with 3GPP network for improving transmission performance... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.4 NSCE (Network Slice Capability Exposure) server/client
| Editor's Note: This clause will provide introduction of SEALDD server and client.
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.5 LM (location management) server/client
| Editor's Note: This clause will provide introduction of LM server and client.
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 4.2.6 AIMLE (AIML enabler) server/client
| Editor's Note: This clause will provide introduction of AIMLE server and client.
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5 The use cases and advantages to applications
| |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.1 Summary of SEAL services
| Editor's Note: Brief summary of the value of each the SEAL services.
This clause is to address the overall summary of the values and beneficial use case(s) of each SEAL service.
The supporting of the following are the key services that make SEAL layer distinct with other non-3GPP basis developer API Platform:
- NSCE... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.2 Use cases and advantages for SEAL Servics provided by SEALDD
| Editor's Note: Details about the value of each SEAL services and how it brings advantages to applications
|
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.2.1 Use case
| CDN is known as a content distribution network. CDN is a global network server system that works together to provide super-fast delivery of Internet content such as website webpages, HTML pages, JavaScript files, stylesheets, images, and videos. When people try to access a website if using a CDN, then visitors will see... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.2.2 Advantages and values of SEALDD Services
| As it shows in figure 5.2.2-1, the application data information will be provided by SEAL DD in the way 3GPP system can read. So that 3GPP network layer can apply some enhancement transmission on SEALDD data.
Figure 5.2.2-1: SEALDD data transmission using differentiating-processing capability by 3GPP network
In addi... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.3 Use cases and advantages for SEAL Services provided by NRM
| |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 5.3.1 Use case
| Below list specifies the needs of the various applications utilizing the 3GPP network capabilities:
- URLLC as mentioned in clause 7.2 of 3GPP TS 22.261 [15]
- High data rate and low latency as mentioned in clause 7.6 of 3GPP TS 22.261 [15]
- Low latency e.g IMS/MCX Voice call/video call
- Background data transfer ... |
024c36bb093e22ea835bdef886e704b0 | 23.949 | 6 Deployment of SEAL entities and business relationship among stakeholders
| Editor's Note: Deployment alternatives by stakeholders and corresponding business relationship
Annex A:
Relationship between SEAL Enablers and external organizations
Editor's Note: This clause will describe how SEAL layer could be consumed in different vertical scenarios based on the analysis in solution#6 in the 3... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 1 Scope
| The present document studies a number of potential enhancements to the intent driven management services for 5G Advanced network. These include the definition of new targets and contexts for existing scenarios, negotiation enhancements, and utility function enhancements.
New functionality includes the introduction of ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 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.
-... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 3 Definitions of terms, symbols and abbreviations
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [11] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [11].
example: text used to clarify abstract rules by applying them literally.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [11] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [11].
<ABBREVIATION> <Expansion>
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4 Use cases and potential solutions for new areas
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.