hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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, barring and roaming restrictions are ignored. The implicit registration set of the Public User Identifier used for emergency registrations shall contain an associated TEL-URI for callback messaging purposes, as specified in clause 4.2 of TS 23.167 [9].
The LRF/RDF may allocate ESQK or an equivalent callback identifier supported by the PSAP during routing. The E-CSCF receives this allocated ESQK or the equivalent callback identifier and includes it in the signalling toward the PSAP. The ESQK or the equivalent callback identifier is used as a temporary, routable telephone number for both messaging callback and querying location.
If the UE establishes an emergency session without registration (e.g. in an unauthenticated or "anonymous user" scenario), the E-CSCF shall derive a non-dialable callback number for the purpose of messaging where required by local regulation.
|
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 core network is incapable of supporting the SMS to EC functions, which includes scenarios where the E-CSCF is absent or non-functional, or coordinated HPLMN forwarding fails, the signalling flow is reversed. The E-CSCF (if reachable) initiates the failure, or the P-CSCF detects the failure and returns a SIP error response to the UE.
Upon receiving this SIP failure response from the P-CSCF, the UE is explicitly advised to attempt an alternative, higher-priority emergency communication channel, as mandatory fallback must occur. This fallback may involve, for example, one of the following actions:
- The VPLMN, via the SIP response, advises the UE to initiate an Emergency Voice Call (SIP INVITE).
- The UE's domain selection logic may automatically trigger a fallback to the CS domain.
- The system may advise fallback to an alternative transport method, such as SMS over NAS, depending on network capabilities (e.g. if utilizing NTN or other access types).
|
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 specified in clause 7.2 of TS 23.167 [9].
The UE then encapsulates the SMS to EC short message contained in SMS-SUBMIT type PDU in a SIP MESSAGE method and forward it to the P-CSCF.
The TP-UD in SMS-SUBMIT should contain specific Emergency Service-Type (police/fire/ambulance, etc.), UE location data (if available), and Callback Information (if available).
The SIP message defined in RFC 3428 [25] should be enhanced to include proper indication so that P-CSCF can recognize the SIP message contains an SMS to EC message. For example, the UE constructs an Emergency Service URN (e.g. urn:service:sos.text) in the Request-URI, which the P-CSCF is configured to recognize.
For Non UE Detectable SMS to EC, the session initially follows a normal establishment path to the P-CSCF.
2. In step 2, the P-CSCF recognizes the incoming SIP MESSAGE contains SMS to EC message. It then forwards the message to E-CSCF.
Otherwise, the P-CSCF checks the message destination against a database of local emergency numbers. If the destination matches a local or well-known emergency number, the P-CSCF treats the message as an emergency candidate and forwards it to the E-CSCF for emergency handling.
3. The enhanced E-CSCF recognizes the incoming SIP MESSAGE contains the SMS to EC message. The E-CSCF immediately uses existing interfaces to the LRF to obtain the UE's location, as described in clause 7.6 of TS 23.167 [9].
The E-CSCF then calls the LRF/RDF to resolve the final PSAP destination and obtain the necessary routing information for the UE's current location and requested Service-Type.
The LRF/RDF allocates the ESQK or an equivalent callback identifier supported by the PSAP and determines the ESRN. And the LRF returns the PSAP address along with TEL-URI, ESRN/ESQK or the equivalent callback identifier and other location/routing parameters to E-CSCF.
The E-CSCF then includes the allocated ESQK or an equivalent callback identifier and ESRN in the outbound signalling, applying the same Service-Type identifier and semantics used for IMS emergency calls (TS 23.167 [9]). This ESQK or the equivalent callback identifier serves as the mandatory key for the PSAP to query the LRF for location and identity information.
4. E-CSCF determines, based on the information provided in step 3 to route the SIP MESSAGE to the proper PSAP.
In 4a, for deployment supporting ESInet, the Enhanced E-CSCF directly resolves and routes the SIP MESSAGE (using the specific Service URN) to the Emergency Service Routing Proxy (ESRP) or an equivalent SIP entity within the ESInet. The ESRP, which is compliant with NENA's i3 standards, uses its own location and policy logic to guide the message to the proper PSAP instance.
In 4b, 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-IWMSC to the PSAP Gateway that supports SMS, e.g. Text-to-911 interface. Delivery acknowledgment returns via the reverse path: PSAP Gateway, SMS-GMSC, IP-SM-GW, E-CSCF, and to the UE.
|
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 SIP MESSAGE to the local P-CSCF an indication that the SIP MESSAGE contains an SMS2EC and the requested emergency type.
The solution is applicable to UE detectable SMS2EC. In case of non-UE detectable, the home network may instruct the UE to send the SMS again using the SMS2EC over IP described in this solution.
The UE populates the TP-OA field of the encapsulated SMS with its MSISDN enabling the Emergency Centre to reply to the SMS2EC.
|
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 UE prepares a SIP MESSAGE that includes the SMS2EC payload, an SMS2EC indication and the requested emergency type.
- For the UE does not have sufficient credentials to authenticate with the IMS network or registered on the home IMS whilst not in the home PLMN (i.e. the UE is roaming), the UE does send the SIP MESSAGE to the home P-CSCF, but instead initiates MO SMS submit towards the P‑CSCF of the serving PLMN with "anonymous user" in the MESSAGE request.
- Based on "SMS2EC" indication, the P-CSCF inserts UE identifiers and UE location in SIP MESSAGE, then forwards SIP MESSAGE request to an appropriate E-CSCF.
- the E-CSCF replace the "Request-URI" and "to" header with emergency SMSC address, then forwards SIP MESSAGE to IP-SM-GW.
- IP-SW-GW extracts SMS payload, the UE location and emergency type and forwards it to emergency SMSC.
- Based on emergency type and UE location, the SMS2EC is routed by the SMSC to the correct PSAP.
|
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 Session as defined in clause 7.1.1 of TS 23.167 [9] with the following differences:
1. The UE detects the request for the delivery of an SMS2EC.
2. In the case that the UE has insufficient resources or capabilities to deliver an SMS2EC due to other ongoing sessions then the UE should terminate the ongoing communication and release reserved bearer resources.
6. If the UE does not have sufficient credentials to authenticate with the IMS network or the UE is registered in the Home IMS but roaming, the UE shall not initiate an IMS emergency registration request, but instead immediately initiate step 7 (see clause 6.14.2.2 for details).
7. The UE initiates MO SMS2EC submit using the SIP MESSAGE procedures which is described in clause 6.14.2.2. If the UE has performed emergency registration, the UE shall use an emergency registered Public User Identifier.
|
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. The MESSAGE includes SMS2EC indication, emergency type and SMS payload. The UE includes the MSISDN in the TP-OA field.
The UE includes "anonymous user" in the SIP MESSAGE.
2. If "anonymous user" is included in SIP MESSAGE, the P-CSCF retrieves subscriber related identifier(s) (e.g. IMSI, IMEI(SV),MSISDN) from the IP-CAN. The P-CSCF also retrieves UE location from IP-CAN in this step.
3. The P-CSCF inserts UE identifiers and UE location in SIP MESSAGE, then forwards SIP MESSAGE request to an appropriate E-CSCF based on SMS2EC indication.
4. The E-CSCF, if required (e.g. because it has not received the UE location) may query the LRF for location information.
The E-CSCF replaces the "Request-URI" and "to" header in SIP MESSAGE with a suitable SMSC address (based on location and support of SMS2EC in the SMSC), then forwards the SIP MESSAGE to the IP-SM-GW.
5-7. The network acknowledges the SIP MESSAGE reception.
8. the IP-SM-GW extracts and forwards SMS, emergency type and UE location to the SMSC.
9. Based on the emergency type and UE location, SMSC forwards SMS to a correct EC/PSAP.
10-13. Acknowledgement of message submit report.
14-16. UE acknowledges receipt of the submit report.
|
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.
- Inserts UE identifiers and UE location in SIP MESSAGE and forwards SIP MESSAGE request to an appropriate E-CSCF.
E-CSCF:
- Support to forward SIP MESSAGE request to IP-SW-GW.
- Support to replace the "Request-URI" and "to" header in SIP MESSAGE and RP-DA in RP-DATA with emergency SMSC address if emergency SMSC is deployed.
SMSC:
- Support to forward SMS to EC/PSAP together with UE location based on emergency type.
|
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 the country where the UE initiating the SMS is located.
The following principles apply to the solution:
- Applies to UE detectable emergency numbers.
- Based on the concept of establishing a session between the UE and the PSAP.
- For roaming UE the solution is based on PDU session connectivity in the VPLMN and using the VPLMN for routing to the correct PSAP. The traditional IMS PDU session routed via the HPLMN is not used.
- The UE discovers whether the serving PLMN supports SMS to Emergency Centre over IMS during the initial attach and IMS registration to the serving PLMN.
- The SMS to Emergency Centre over IMS is routed via a PDU session in local breakout and via IMS in the VPLMN.
- The E-CSCF in the VPLMN is upgraded to handle SMS to Emergency Centre as if it were and SCSF and route the SMS to Emergency Centre to an appropriate PSAP.
- The SMS to Emergency Centre is not routed via an SMS-SC, in order to enable a future proof solution that can be expanded to additional media.
- The solution has UE impacts in order to enable a complete service for SMS to Emergency Centre over IMS that allows for a "dialogue" between the UE and the PSAP. Moreover, this allow for future extensions to enable additional media.
- The UE that supports SMS to Emergency Centre over IP detects an SMS to Emergency Centre based on used emergency numbers. Provisioning of emergency numbers and associated types as specified in clause 4.1, bullets 2a) and 2b), of TS 23.167 [9] apply.
- Serving network can support SMS to Emergency Centre over IP for own subscribers and inbound roamers.
- PSAP are upgraded to support SIP sessions.
|
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 end user service. The solution provides high reliability and security thanks to the use of IMS spoofing protection.
NOTE 1: The solution can be also be expanded to additional services to Emergency Centre (e.g. using MSRP for real-time text, voice, video).
NOTE 2: The solution assumes that PSAP supports IMS and SMS over IP.
Most PSAPs are already migrating to SIP/IP, thus the solution can be future proof.
The solution can be defined completely within 3GPP and does not require IETF change, since use of SDP without SIP media is an existing IETF option (in IETF RFC 3264 [27] and IETF RFC 4566 [26]).
|
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 aware whether the serving PLMN and local PSAP support "SMS to Emergency Centre over IMS" (SMS2EC over IMS) from step 1.
3. The UE may follow one of the following three options:
a. The UE attaches/registers with an SMS2EC-specific DNN configured via roaming agreement for the Serving PLMN that is routed in local breakout.
NOTE 1: The SM2EC-specific DNN is configured in the UE and is in the UE subscription.
b. Based on bi-lateral agreement between HPLMN and Serving PLMN, the UE uses a specific DNN/S-NSSAI pair in 5GS or APN in EPS that is routed in local breakout.
NOTE 2: The SM2EC-specific DNN/S-NSSAI pair is configured in the UE and is in the UE subscription.
c. The UE performs an emergency attach or emergency registration.
4. The UE establishes an PDN connection or PDU session as in step 3.
5. The UE attempts to perform an IMS Emergency Registration if step 1 occurred or if authentication succeeded in step 3.
6. The UE establishes an IMS emergency call with no SIP media to a PSAP.
6a. As part of step 6, the UE sends a SIP INVITE containing the emergency number detected at step 2 or an SOS URN corresponding to this number to a P-CSCF in the IMS which forwards the SIP INVITE to an E-CSCF. The SIP INVITE contains a Session Description Protocol (SDP) description for IETF compatibility but not necessarily SIP media if the intention is to be used only for SMS.
NOTE 3: The solution enables the UE to optionally include other media e.g. MSRP or voice/video in the SIP "offer".
6b. The E-CSCF routes the SIP INVITE towards a PSAP that supports SMS over IMS based on a location or current serving cell for the UE and possibly with the assistance of an LRF. As an option, the emergency SM can be included in the SIP INVITE in which case steps 7 and 8 are not performed. The SIP INVITE without SIP media (and with an emergency SM if included) can be an implicit indication that the UE is able to send and receive emergency SMS messages.
6c. The PSAP may recognize from the SIP message received at step 6b that the UE is able to send and receive emergency SMS messages. The PSAP returns a SIP 200 OK to the UE via the E-CSCF and P-CSCF that also contain an SDP description but no SIP media. The SIP 200 OK without SIP media can be an implicit indication that the PSAP is able to receive and send only emergency SMS messages.
NOTE 4: If the UE has optionally included other media in step 6a and the PSAP supports such media, the PSAP may accept them in the SIP "answer".
7. The UE sends the SMS message to the PSAP in a SIP MESSAGE in association with the SIP dialogue established at step 6.
8. The PSAP returns a SIP 200 OK to acknowledge receipt of the SMS MESSAGE and in association with the SIP dialogue established at step 6.
9. The PSAP optionally returns an SMS reply to the UE in a SIP MESSAGE in association with the SIP dialogue.
10. The UE returns a SIP 200 OK to acknowledge receipt of the SMS MESSAGE and in association with the SIP dialogue.
11. The UE and PSAP may exchange further SMS messages using SIP MESSAGEs as in steps 7 to 10.
NOTE 5: if additional media were offered by the UE and accepted by the PSAP, the UE and the PSAP may exchange such media in addition or instead of the SMS exchange of steps 7 to 10.
12a. Following a timeout after sending or receipt of the last SMS message, the UE sends a SIP BYE to the PSAP to release the SIP dialogue established at step 6.
12b. Alternatively, the PSAP can send a SIP BYE at any time to release the SIP dialogue.
|
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 Centre via the establishment of a SIP session.
PSAP:
- Support of IMS and SMS over IP.
|
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) to Emergency Response Centre is routed to a PSAP in the country where the UE is located.
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.
When the UE does not receive the indication that SM to Emergency Response Centre over IMS is supported in the serving PLMN, it attempts to send the SM to Emergency Response Centre over NAS, if configured in the UE.
NOTE: If SM to Emergency Response Centre is not supported in the serving network, it is up to UE implementation how to proceed. The UE can try to choose another network to send the SM to Emergency Response Centre. The UE can also try to establish an emergency call or indicate to the user that SM to Emergency Response Centre is not possible.
|
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 SM to the Emergency Response Centre.
The E-CSCF includes the PSAP address in the Request-URI in the SIP MESSAGE request and forwards it to the IP-SM-GW configured in the E-CSCF.
The IP-SM-GW selects a local SMSC and forwards the SM to the Emergency Response Centre via MAP-MO to the SMSC including the PSAP address.
The SMSC selects an appropriate Emergency Response Centre and sends the SM to the Emergency Response Centre.
|
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 send an SM to an Emergency Response Centre:
Figure 6.16.2.1-1: Procedure for Short Message to Emergency Response Centre via SMS over IP
1. 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.
2. The P-CSCF forwards the SIP MESSAGE to an E-CSCF that is capable of handling the SM to the Emergency Response Centre.
3. The E-CSCF optionally queries the LRF to get user location information and selects a proper PSAP.
4. The E-CSCF includes the PSAP address in the Request-URI in the SIP MESSAGE request and forwards it to the IP-SM-GW configured in the E-CSCF.
5. The IP-SM-GW selects a local SMSC and forwards the SM to the Emergency Response Centre via MAP-MO to the SMSC including the PSAP address.
6. The SMSC sends the SM to the Emergency Response Centre to the PSAP.
7-9. The successful response code 202 Accepted is sent from the IP-SM-GW to E-CSCF -> P-CSCF -> UE.
|
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 the SIP MESSAGE request carrying the SM to the Emergency Response Centre and forward the SIP MESSAGE request to a configured IP-SM-GW.
IP-SM-GW:
- IP-SM-GW needs to select a local SMSC and forward the SM to the Emergency Response Centre via MAP-MO to the SMSC including the PSAP address.
|
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 PDU session to support the SMS over IP delivery to Emergency Response Centre (ERC) and performs emergency IMS registration prior to the SMS over IP delivery to Emergency Response Centre.
- The IP-SM-GW in the serving PLMN is responsible to deliver the SMS to the SMS service centre based on the emergency number inserted in RP-DA.
- The serving SMS service centre is responsible to forward the SMS to the local Emergency Response Centre.
|
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 Centre is supported by the network during IMS registration) for the non-roaming case. For the roaming case, the UE realizes the support SMS over IP delivery to Emergency Response Centre during the emergency IMS registration.
The main change is IP-SM-GW deliver the SMS to the SMS service centre based on the RP-DA field.
|
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 also includes an indication if SMS over IP delivery to Emergency Response Centre is supported based local policy configuration.
When network supports SMS over IP delivery to Emergency Response Centre (ERC), and the Emergency IMS registration is triggered by UE due to the need of SMS over IP delivery to ERC, then UE continues steps 9-12 or steps 13-15.
NOTE: For the SMS over IP delivery to ERC in step 11-12 and step 13-15 are further detailed in clause 6.17.3 below
|
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 information in the SIP message. The UE include emergency number in RP-DA.
2. The P-CSCF forwards the SIP MESSAGE to an E-CSCF that is capable of handling SMS over IP delivery to PSAP.
3. E-CSCF optionally queries the LRF to get user location information and determines a suitable PSAP address.
NOTE: The optional LRF involvement is useful in markets where the PSAP to handle the emergency is determined based on the user location (e.g. cell -id).
4. E-CSCF sends the SIP MESSAGE to the IP-SM-GW. The SIP MESSAGE may optionally include the PSAP address.
5. The IP-SM-GW receives SIP message and optionally the PSAP address from E-CSCF and sends the SMS payload to SMS-C. If PSAP address is received, IP-SM-GW will include it in the RP-DA field.
6. SMSC may acknowledge to the IP-SM GW.
7. SMSC sends the SMS to local PSAP. Optionally, SMSC can use the PSAP address received in step 5 in the routing process.
8. The successful response code Accepted is sent from IP-SM-GW to E-CSCF -> P-CSCF -> UE.
|
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 performance penalties for P-CSCF having to scan all SIP MESSAGE messages, it is proposed that such function is performed by HPLMN IP-SM-GW. The IP-SM-GW is proposed to perform similar procedures as specified for P-CSCF in clause 5.2.10.5 of TS 24.229 [23] and the UE to follow similar procedures as specified in clause 5.1.2A.1.1 of TS 24.229 [23].
This would apply to both roaming and non-roaming scenarios.
|
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:
- Support SMS over IP delivery to Emergency Response Centre capability handling during IMS registration/emergency IMS registration and delivery of SMS to PSAP via IP-SM-GW.
IP-SM-GW:
- Support of SMS delivery to SMS service centre of the serving PLMN based on emergency number with PSAP address.
- If PSAP address is received from E-CSCF, IP-SM-GW inserts in the RP-DA field of the SMS sent to SMS-C.
- Support the handling of rejection in case of non-detectable SMS delivery to PSAP (e.g. returning a response with 380, the same way as P-CSCF handling the non-detectable emergency call).
|
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 shall trigger the AMF/MME to perform primary authentication to establish the necessary NAS security context for SMS transfer.
- P2. Negotiation of UE capability and network support for Conditional LBO Policy Override: For UEs in the Normal Registration State, Local Breakout for PSAP-destined SMS is negotiated between the UE and the IMS Network (via P-CSCF/S-CSCF) using SIP feature tags (e.g. +g.3gpp.smsip-lbo) as a conditional override to the default Home Routed policy. The P-CSCF makes the local policy check and S-CSCF determines network support of SMS over IP, and SMS for LBO routing. During the IMS registration procedure, the P-CSCF checks if the UE is successfully registered on the visited PLMN and retrieves subscriber related identifier(s) (e.g. IMSI, IMEI(SV), MSISDN) from the PCF to execute the local policy check and to determine if the roaming user is authorized for the Conditional LBO service based on the registration status in the visited PLMN.P3. Emergency Number Provisioning: As part of the normal registration procedure and emergency registration procedure, the AMF shall provide the UE with the VPLMN's local Emergency Number List to ensure the UE uses the correct destination address in the MO SMS TPDU.
- P4. Explicit Routing Trigger via SIP: The UE shall use a specific indicator in the SIP MESSAGE request to explicitly signal to the IMS network that the embedded SMS is for routing to a PSAP and requires the conditional LBO route via the visited IP-SM-GW.
- P5. Home Routed Fallback (for keeping integrity): When Conditional LBO is not supported by the VPLMN, Home Routed SMS is enhanced by optionally passing the Visited SMSC Address to the UE, allowing the Home SMSC to perform efficient, direct routing to the local PSAP.
- P6. Non-Modification of TPDU: The core network functions (IP-SM-GW) shall maintain the integrity of the SMS-TPDU payload during transit. This is to ensure the mechanism is robust and future-proof so that the SMS-TPDU payload is agnostic to how it's transported (over NAS in the control plane, or over IP in the application plane).
- P7. NAS Layer as Transport-Agnostic Policy Anchor: The VPLMN's LBO authorization is anchored in the NAS layer (MME/AMF) during the Registration/Attach procedure. This establishes a single master policy that governs the UE's LBO procedures for all delivery protocols. This requires the IMS core (P-CSCF/S-CSCF) to enforce this authorization status at the application layer for SMS over IP, ensuring the LBO policy is consistently applied regardless of the delivery mechanism (SMS over NAS or SMS over IP).
|
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 primary authentication to ensure the creation of the necessary security context required for secure SMS over NAS transfer.
2. Conditional LBO Capability Negotiation:
- During the IMS registration procedure, the P-CSCF checks if the UE is successfully registered on the visited PLMN and retrieves subscriber related identifier(s) (e.g. IMSI, IMEI(SV), MSISDN) from the PCF to execute the local policy check and determine if the roaming user is authorized for the Conditional LBO service based on the registration status in the visited PLMN.
- The IMS registration procedure must negotiate LBO capability, which serves as the final application-layer authorization check that enforces the core routing policy anchored in the NAS context.
- The UE shall include a new SIP feature tag (e.g. +g.3gpp.smsip-lbo) in the Supported or Require header of the SIP REGISTER message to indicate its capability and preference for MO SMS delivery using conditional LBO for routing to local PSAP. The SIP 200 OK message is extended to include an optional SIP feature tag in the P-Associated-URI header, e.g. +g.3gpp.smsip-lbo-allowed, if the Visited IMS network is configured to support this service for the roaming user.
3. LBO Message Signalling:
- For MO SMS destined for a PSAP, the UE shall use standardized urn:service:sos (to trigger emergency routing) and a new explicit SIP header (P-3GPP-SMS-LBO-Routing: true) in the SIP MESSAGE request to explicitly signal to the IMS network that the embedded SMS TPDU is destined for a PSAP and requires Local Breakout routing. This provides an unambiguous signal for conditional local routing.
4. Home Routed Fallback Enhancements:
- Home Routed Fallback Enhancement: If Conditional LBO is not supported by the VPLMN, the SIP 200 OK can optionally provide the visited SMSC Address to the UE for use during Home Routed fallback.
- TPDU Integrity: All core network functions (IP-SM-GW/Visited SMSC/Home SMSC) must maintain the integrity of the SMS-TPDU payload during transit.
- The SMS-TPDU is enhanced with a new optional field to carry the visited SMSC Address when provided by the UE in the Home Routed fallback scenario.
5. The principle of the MO SMS delivery using SMS over IP includes:
- UE Role: The UE builds the SMS message based on TS 23.040, which specifies the SMS-SUBMIT TPDU (Transport Protocol Data Unit). The UE uses the SMS-SUBMIT TPDU as the final message payload. The UE does not use the RP-DATA PDU or CP-DATA components, as these are specific to NAS transport.
- SIP Transport: The UE places the SMS-SUBMIT TPDU payload inside the message body of a SIP MESSAGE request. The necessary signalling (routing address, priority headers, etc.) is placed in the SIP headers (e.g. Request-URI, P-Headers).
- P-CSCF/IP-SM-GW Role: The P-CSCF/S-CSCF receives the SIP MESSAGE and routes it to the Visited IP-SM-GW. The V-IP-SM-GW extracts the SMS-TPDU payload from the SIP MESSAGE body and converts the SIP signalling into the core network's Mobile Originated (MO) SMS protocols (e.g. MAP or Diameter) for forwarding to the V-SMSC or H-IP-SM-GW.
|
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 "emergency registration".
- A new Authentication indication IE or 5GS update type IE with the SMS requested bit set to "SMS over NAS supported" and a new SMS authentication required bit set to true (acting as an authentication trigger).
1a. The AMF recognizes the Emergency Registration and the explicit authentication need for SMS over NAS support. The AMF overrides the default deferral policy and initiates the primary authentication procedure immediately with the AUSF/UDM. The AMF performs authentication procedures to interact with UDM to ensure that the UE's credentials are validated before enabling SMS services.
2: AMF uses the Nudm_UECM_Registration operation/Nudm_UEAuthentication/ Service/ Nudm_SDM_Get/Nudm_SDM_Subscription service operations to interact with UDM.
3: Upon successful authentication, the AMF derives the NAS security context and continues the registration procedure. The AMF provides the VPLMN Emergency Number List and 5GS registration result indicating "SMS allowed" bit that confirms successful authentication and SMS for routing to local PSAPs services are authorized. If primary authentication fails, the AMF sends registration accept message with 5GS registration result indicating SMS not allowed to notify the UE that SMS over NAS is not possible for emergency registration due to lack of a security context or authorization, recommending fallback to another mechanism, e.g. normal registration procedure enhanced with SMS for LBO routing to PSAP as described in clause 6.7.2.1.2.
4: The AMF sends Registration Accept message to the UE indicating Emergency services supported and SMS service allowed/disallowed in the 5GS registration result.
5: The UE stores 5GS registration result for UE allowed/disallowed in UE context.
|
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.3.2.2.1-1 of TS 23.502 [3].
3: The UE sends a SIP REGISTER to the P-CSCF. The message includes:
- The standard mechanism (e.g. dedicated P-CSCF discovery) to indicate an Emergency Registration.
- The +g.3gpp.smsip feature tag in the Supported header, indicating SMS over IP support.
- A new feature tag or parameter (e.g. a parameter like ;auth-req on +g.3gpp.smsip, or a new feature tag like +g.3gpp.emergency-sms-auth) explicitly indicating the need for immediate user authentication to establish a security context for emergency SMS over IP.
4: When the P-CSCF detects the IMS Emergency Registration and the explicit authentication need for emergency SMS over IP, the P-CSCF checks if the UE is successfully registered on the visited PLMN and retrieves subscriber related identifier(s) (e.g. IMSI, IMEI(SV), MSISDN) from the PCF in the Visited PLMN to establish the user identity required for immediate user authentication. Using these identifiers, the P-CSCF performs the local policy check to verify if the subscriber is authorized for Conditional LBO based on the registration status in the visited PLMN.
The S-CSCF overrides the default deferral policy for authentication and initiates the user authentication procedure immediately with the AUSF/UDM.
5: Upon successful authentication, the S-CSCF sends a SIP 200 OK to the UE, including the +g.3gpp.smsip feature tag in the Contact header, confirming the successful authorization of SMS over IP.. If authentication failed, the S-CSCF accepts the SIP Registration request while omitting the SMS capabilities (by not including the +g.3gpp.smsip feature tag), recommending fallback to another mechanism, e.g. IMS registration procedure enhanced with SMS for LBO routing to PSAP as described in clause 6.18.3.1.3.
|
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 performs PDU Session Establishment Request Procedure for IMS DNN/S-NSSAI based on Figure 4.3.2.2.1-1.
3: The UE sends a SIP REGISTER to the P-CSCF, including the SIP feature tag for SMS over IP (e.g.+g.3gpp.smsip) and SMS for LBO routing (e.g. +g.3gpp.smsip-lbo) in the Supported header to indicate SMS over IP (for home routed policy) and SMS for LBO Support (for routing to local PSAP).
4: The P-CSCF checks if the UE is successfully registered on the visited PLMN and retrieves subscriber related identifier(s) (e.g. IMSI, IMEI(SV), MSISDN) from the PCF in the Visited PLMN to establish the user identity required for immediate authentication. Using these identifiers, the P-CSCF performs the local policy check to verify if the subscriber is authorized for Conditional LBO based on the registration status in the visited PLMN. Subsequently, the S-CSCF determines network support of SMS over IP, and SMS for LBO routing.
5: If conditional LBO for PSAP-destined SMS is allowed, the S-CSCF sends a SIP 200 OK to the UE, including feature tag for SMS over IP (e.g. +g.3gpp.smsip), and feature tag for SMS for LBO (e.g. +g.3gpp.smsip-lbo-allowed in the contact header). The S-CSCF may optionally include the visited SMSC Address IE in the P-CSCF configuration message. If conditional SMS for LBO is not allowed, the S-CSCF omits the SMS for LBO Allowed indication.
6: The UE stores SMS over IP for LBO allowed indication (if available) in UE SIP context.
|
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.2.1-1 for normal PDU Session or Emergency PDU Session.
3: The UE performs IMS registration procedure or IMS emergency service registration procedure for enabling SMS over IP delivery using LBO routing to local PSAP.
4: The UE generates the SMS-SUBMIT TPDU with the local emergency number in the TP-DA field.
5: Based on the SMS for LBO Allowed status stored in the UE SIP context, the UE sends a SIP MESSAGE request to the P-CSCF. A new header, P-3GPP-SMS-LBO-Routing: true as the primary explicit trigger, used alongside the standardized urn:service:sos is included to signal conditional local routing preference. The message body carries the embedded SMS-SUBMIT TPDU payload. For IMS emergency registered UE, the Request-URI is set to the local emergency number (e.g. tel:911). The P-CSCF also detects the standard urn:service:sos.
6: The P-CSCF receives the SIP MESSAGE and detects the presence of the P-3GPP-SMS-LBO-Routing: true header or a dedicated URN (e.g. urn:service:sos.sms.psap.lbo) in the Request-URI. For IMS emergency registered UE, the P-CSCF also detects the standard urn:service:sos. The P-CSCF overrides the default policy and selects a locally configured Visited IP-SM-GW. The message is then routed via the S-CSCF to the V-IP-SM-GW. If the UE was not explicitly granted the SMS for LBO Allowed status during registration, the S-CSCF shall ignore the SMS for LBO header and follow the default Home Routed policy as described in Figure 6.18.3.1.4-1.
7: The P-CSCF/S-CSCF forwards the SIP MESSAGE to the V-IP-SM-GW.
8: The Visited IP-SM-GW determines that the MO SMS is for LBO routing.
9: The Visited IP-SM-GW forwards MO SMS to the V-SMSC.
10: The Visited SMSC identifies the MO SMS and routes it to local PSAP based on emergency number, emergency service type and location information, e.g. AML, indicated in the SMS-TPDU payload.
|
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 Breakout (LBO) functionality (e.g. if the V-IP-SM-GW lacks the necessary local configuration), the S-CSCF/IP-SM-GW is obligated to apply the Home Routed policy to ensure the message is delivered via the Home PLMN (HPLMN). This fallback mechanism guarantees reliability, which is essential for any emergency service.
Figure 6.18.2.1.5-1: MO SMS over NAS Delivery in 5GS (VPLMN LBO Not Supported/Allowed - Home Routed Fallback)
The following are the required enhancement MO SMS over NAS Delivery in 5GS (VPLMN LBO Not Supported/Allowed - Home Routed Fallback) in Figure 6.18.2.1.5-1:
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.2.1-1 for normal PDU Session or Emergency PDU Session.
3: The UE performs IMS registration procedure or IMS emergency service registration procedure for enabling SMS over IP delivery using home routed fallback.
4: The UE generates the SMS-SUBMIT TPDU with the local emergency number in the TP-DA field. If the UE received the visited SMSC Address IE in Registration procedure, the UE includes this address in a new dedicated routing field within the SMS TPDU.
5: Without SMS for LBO Allowed indication stored in UE SIP context, the UE sends a SIP MESSAGE request to the P-CSCF. The message body carries the embedded SMS-SUBMIT TPDU payload. For IMS emergency registered UE, the Request-URI is set to the local emergency number (e.g. tel:911). The P-CSCF also detects the standard urn:service:sos.
6: The P-CSCF/S-CSCF receives the SIP message and determines to follow the default Home routed roaming policy and select the H-IP-SM-GW (via the I-CSCF).
7: The S-CSCF forwards the SIP MESSAGE to the V-IP-SM-GW. The V-IP-SM-GW then applies home routing policy, converts the SIP message into core Mobile Originated (MO) SMS protocol, and forwards it to the H-IP-SM-GW. The H-IP-SM-GW then forwards the MO SMS to the H-SMSC.
8: The H-SMSC identifies the MO SMS for LBO routing to local PSAP based on emergency number, emergency service type and location information, e.g. AML, indicated in the SMS-TPDU payload. If the UE included the visited SMSC Address (received during SIP registration) in the SMS-TPDU payload, the H-SMSC uses this address for direct routing to the visited SMSC for routing to the local PSAP. If the visited SMSC Address is not present, the H-SMSC inspects the TP-DA and uses its global routing policy to route the message back to the appropriate visited SMSC for routing to local PSAP.
9: The H-SMSC routes the SMS-TPDU to the V-SMSC. The H-SMSC uses core inter-PLMN SMS protocols (like MAP or Diameter) and the V-SMSC's address (either from a database lookup or the optional address provided by the UE in the TPDU) to route the message.
10: The V-SMSC identifies the MO SMS for LBO routing to PSAP and routes it to local PSAP based on emergency number, emergency service type and location information, e.g. AML, indicated in the SMS-TPDU payload.
|
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 for Conditional LBO for PSAP routing by including the new SIP feature tag +g.3gpp.smsip-lbo in the SIP REGISTER message (for both Normal and Emergency Registration states).
- Store the VPLMN Emergency Number List and always use a local emergency number in the SMS-TPDU TP-DA field for PSAP-destined SMS.
- Support LBO Routing Trigger if SMS for LBO is allowed using either a dedicated URN in the Request-URI or a dedicated header in the SIP MESSAGE request to explicitly signal the network's conditional local routing preference.
- Support home Routed Fallback Enhancement for storing visited SMSC Address.
P-CSCF/S-CSCF/I-CSCF:
- Handle the network support and new UE capability indication for SMS over IP for LBO negotiation.
- Interact with the PCF in the Visited PLMN to retrieve subscriber related identifiers (e.g. IMSI) for performing the local policy check based on the registration status in the visited PLMN during IMS Registration/IMS emergency Registration.
- Trigger user authentication during IMS Emergency Registration when the authentication indicator is present.
- Enforce the core architectural mandate that the SMS-TPDU payload structure remains transport-agnostic, ensuring LBO policy established in the NAS layer is applied consistently to the SMS over IP delivery mechanism.
- Optionally provide visited SMSC Address to the UE in the SIP 200 OK message.
- Use the SMS for LBO Allowed status and the dedicated URN and/or header indication to determine SMS routing path (LBO via V-IP-SM-GW vs. Home Routed).
IP-SM-GW (Visited IP-SM-GW):
- Must maintain the integrity of the SMS-TPDU payload during transit.
- Support interworking with a Visited SMSC configured for routing to the local PSAP.
- Convert the SIP message to the core SMS protocol for tunnelling.
IP-SM-GW (Home IP-SM-GW):
- perform the final routing decision.
SMSC (Home PLMN):
- Need to be configured to support the optional visited SMSC Address in the TPDU payload for efficient Home Routed fallback.
- Maintain a global routing policy (inspecting TP-DA) for all Home Routed SMS when the new visited SMSC address field is absent or unsupported.
- Inspects the new dedicated routing field for the optional visited SMSC Address and performs the final routing decision for efficient local delivery.
|
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 supports SMS over IP detects that the receiver's number of a Short Message is an emergency number, the UE establishes an emergency PDU session (or PDN connection) towards the local IMS and performs IMS emergency registration.
- When UE builds a short message to emergency centre, the UE sets the RP-DA to the local SMSC address (e.g. local SMSC number) in the serving PLMN, and also includes the Public Service Identity (PSI) of local SMSC and emergency service URN in the Request-URI and To header of the SIP Messages.
Scenario 2: UE not detecting SMS2EC:
- The P-CSCF stores the emergency number and emergency service URNs of the home network and its roaming partners.
- If the home P-CSCF detects that this is for Short Message to Emergency Centre, the home P-CSCF may reject the SIP Message request with an emergency service URN.
- Upon reception of a rejection with the emergency service URN, UE establishes an emergency PDU session (or PDN connection) towards the local IMS, and performs IMS emergency registration. When UE builds a short message to emergency centre, the UE sets the RP-DA to the local SMSC address (e.g. local SMSC number) in the serving PLMN, and also includes the Public Service Identity (PSI) of local SMSC and emergency service URN in the Request-URI and To header of the SIP Messages.
- Based on the emergency number, and UE' location, SMSC delivers the Short Message to the emergency response centre (i.e. PSAP).
|
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 establishes an emergency PDU session (or PDN connection) towards the local IMS. If the UE has sufficient credentials to authenticate with the IMS network, it shall initiate an IMS emergency registration. If the UE does not have sufficient credentials to authenticate with the IMS network, UE establish emergency session as an "anonymous user".
When UE builds an short message, the UE sets the RP-DA to the local SMSC address (e.g. local SMSC number) in the serving PLMN, and also includes the Public Service Identity (PSI) of local SMSC and emergency service URN in the Request-URI and To header of the SIP Message. The PSI of the SC can be SIP URI or tel URI based on operator policy. The PSI of the SC can be obtained using the methods as described in clause 5.3.1.2 of TS 24.341 [24]. Based on the emergency service URN, P-CSCF can be aware that this is for SMS2EC, and then forwards the SIP message to the E-CSCF. E-CSCF forwards the SIP Message to IP-SM-GW. IP-SM-GW extracts the Short Message (SMS-SUBMIT) and forwards it to the local SMSC.
In addition, the UE includes the emergency number, associated emergency service type, and UE's location (e.g. Latitude and longitude, etc.) in the TPDU part of the Short Message. The local SMSC forwards the received Short Message to the corresponding PSAP, considering the emergency number, associated emergency service type, and UE' location extracted from the SMS-SUBMIT TPDU.
An example of RP-DATA included in a Short Message Service to emergency centre (SMS2EC) is as below:
RP-DATA:
RP-OA: Address of the originating UE.
RP-DA: Address of the SMSC, e.g. local SMSC number.
RP-User-Data:
TP-OA: Address of the originating UE.
TP-DA: Emergency number and associated emergency service category value as defined in TS 24.008 [19], e.g. 1121, where "112" is the emergency number and "1" is for police.
UE's location related TPDU parameter: Latitude and longitude are typically stored as double-precision floating-point numbers. Each value requires 8 bytes, so a combined pair uses 16 bytes. UE's location related TPDU parameter can be an existing TPDU parameter (e.g. TP-User-Data-Header) or a new parameter.
|
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 are also configured in P-CSCF. Therefore, the P-CSCF can detect SMS2EC using the emergency number. For example, the P-CSCF may detect that the TP-DA is an emergency number.
In the case that the P-CSCF detects that this is SMS2EC, the P-CSCF may, based on operator policy:
- reject the SIP Message request with an indication that this is for SMS2EC. For instance, P-CSCF includes the emergency service URN (e.g. urn: service: sos.police) in the response message as an emergency indication.
Upon reception of a rejection with the emergency indication, UE performs, and establishes an emergency PDU session (or PDN connection) towards the P-CSCF in the serving PLMN. UE builds a Short Message over IP as described in clause 6.19.2.1.
|
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 detects the receiver's number is an emergency number, the UE establishes an emergency PDU session (or PDN connection) towards the P-CSCF in the serving PLMN and performs IMS emergency registration.
2a: UE encapsulates the Short Message in SIP Message request. The request includes vnd.3gpp.sms payload and routing information for the IP-SM-GW to forward the Short Message. The payload includes an RP-DATA message containing the SMS-SUBMIT TPDU. If UE detects that the receiver's number is an emergency number, the UE sets the RP-DA to the local SMSC address (e.g. local SMSC number) in the serving PLMN, and also includes the PSI of local SMSC and emergency service URN in the Request-URI and To header. The PSI of the SC can be SIP URI or tel URI based on operator policy. The PSI of the SC can be obtained using the methods as described in clause 5.3.1.2 of TS 24.341 [24]. The UE sends the SIP Message to P-CSCF.
2b: Based on the emergency service URN included in the Request-URI and To header, P-CSCF is aware that this is for SMS2EC and forwards the SIP message to the E-CSCF.
2c: E-CSCF sends the SIP message to the IP-SM-GW.
2d: IP-SM-GW (AS) acknowledges the SIP message.
2e: E-CSCF forwards the SIP message acknowledge to P-CSCF.
2f: P-CSCF forwards the SIP message acknowledge to UE.
3: IP-SM-GW performs service authorization. IP-SM-GW extracts the Short Message (SMS-SUBMIT) and forwards it to the SMSC via SMS-IWMSC. IP-SM-GW forwards the Short Message to SMS-IWMSC.
4: The SMS-IWMSC forwards the Short Message (SMS-SUBMIT) to SMSC. Based on the emergency number, associated emergency service type, and UE's location obtained from the SMS TPDU, SMSC sends the Short Message to the corresponding PSAP. The SMSC sends a Submit report (SMS-SUBMIT REPORT) to SMS-IWMSC.
5: SMS-IWMSC sends the Submit report to IP-SM-GW.
6: IP-SM-GW encapsulates the Submit Report in an SIP message and send it to the UE. UE acknowledges receipt of the Submit Report to IP-SM-GW.
|
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 that this is for SMS2EC, the P-CSCF may, based on operator policy:
- reject the SIP Message request with an indication that this is for SMS2EC. For instance, P-CSCF includes the emergency service URN (e.g. urn: service: sos.police) in the response message as an emergency indication.
2a: Upon reception of a rejection with the emergency indication, UE establishes an emergency PDU session (or PDN connection) towards the P-CSCF in the serving PLMN and performs the IMS emergency registration. When UE encapsulates the Short Message in SIP Message request, the UE includes the receiver's number, emergency service type, and the UE's location in SMS-SUBMIT TPDU. The RP-DA is set to a local SMSC address in the serving PLMN. The PSI of local SMSC and emergency service URN is included in the Request-URI and To header. The PSI of the SC can be SIP URI or tel URI based on operator policy. The PSI of the SC can be obtained using the methods as described in clause 5.3.1.2 of TS 24.341 [24]. The UE sends the SIP Message to P-CSCF in the serving PLMN.
2b: Based on the emergency service URN included in the Request-URI and To header, P-CSCF is aware that this is for SMS2EC and forwards the SIP message to the E-CSCF.
2c: E-CSCF sends the SIP message to the IP-SM-GW.
2d: IP-SM-GW (AS) acknowledges the SIP message.
2e: E-CSCF forwards the SIP message acknowledge to P-CSCF.
2f: P-CSCF forwards the SIP message acknowledge to UE.
3: IP-SM-GW performs service authorization. IP-SM-GW extracts the Short Message (SMS-SUBMIT) and forwards it towards to the SMSC via SMS-IWMSC. IP-SM-GW forwards the Short Message to SMS-IWMSC.
4: The SMS-IWMSC forwards the Short Message (SMS-SUBMIT) to SMSC. Based on the emergency number, associated emergency service type, and UE's location obtained from the SMS TPDU, SMSC sends the Short Message to the corresponding PSAP. The SMSC sends a Submit report (SMS-SUBMIT REPORT) to SMS-IWMSC.
5: SMS-IWMSC sends the Submit report to IP-SM-GW.
6: IP-SM-GW encapsulates the Submit Report in an SIP message and send it to the UE. UE acknowledges receipt of the Submit Report to IP-SM-GW.
|
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 and emergency service URN in the Request-URI and To header of the SIP Message.
- Support to establish an emergency PDU session (or PDN connection) towards the P-CSCF in the serving PLMN.
P-CSCF:
- Support to reject the SIP Message request with an emergency indication (e.g. emergency service URN), upon determining that the receiver's number is an emergency number.
- Support to forward the SIP Message containing SMS2EC to the E-CSCF.
E-CSCF:
- Support to forward the SIP Message containing SMS2EC to the IP-SM-GW.
SMS-SC:
- Support to send the SMS2EC to the PSAP based on the emergency number, associated emergency service type and UE's location.
|
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 Centre based on the used emergency number matching a locally-configured number in the UE or a number from the network-provided emergency number list.
3. For sending a SM to Emergency Response Centre, the UE provides:
a) the local emergency number.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA2#170
S2-2507491
-
-
-
Proposed skeleton agreed for FS_SMS2EC_ARC at SA2#170
0.0.0
2025-09
SA2#170
-
-
-
-
Implementing the following approved pCRs: S2-2507492, S2-2507594, S2-2507595, S2-2507596, S2-2507644
0.1.0
2025-10
SA2#171
-
-
-
-
Implementing the following approved pCRs: S2-2509350, S2-2509353, S2-2509585, S2-2509586, S2-2509588, S2-2509589, S2-2509590, S2-2509615, S2-2509616, S2-2509617, S2-2509619, S2-2509620
0.2.0
2025-12
SA2#172
-
-
-
-
Implementing the following approved pCRs: S2-2511302, S2-2510525, S2-2510843, S2-2510847, S2-2510849, S2-2510904, S2-2510905, S2-2510906, S2-2510939.
0.3.0
2025-12
SA#110
SP-251350
-
-
-
MCC editorial update for presentation to TSG Sa#110 for information
1.0.0
|
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 aspects :1) SEAL role and responsibility within 3GPP exposure system, 2) the relationship between SEAL and with external SDO, 3) the introduction of SEAL services from the aspects including value, use case and advantages, and 4) deployment of SEAL entities and business relationship among stakeholders.
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications; Stage2".
[3] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Stage 2".
[4] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service; Stage 2".
[5] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service; Stage 2".
[6] 3GPP TS 23.437: "Service Enabler Architecture Layer for Verticals (SEAL); Spatial mapping and Spatial anchors management Stage 2".
[7] 3GPP TS 23.438: "Service Enabler Architecture Layer for Verticals (SEAL); Digital asset".
[8] 3GPP TS 23.501: "System architecture for the 5G System (5GS)"
[9] 3GPP TS26.522 5G Real-time Media Transport Protocol Configurations
[10] 3GPP TS 33.434: "Security aspects of Service Enabler Architecture Layer (SEAL) for verticals".
[11] ITU-T Rec H.265 (08/2021): "High efficiency video coding" | ISO/IEC 23008-2:2023: "High Efficiency Coding and Media Delivery in Heterogeneous Environments – Part 2: High Efficiency Video Coding".
[12] 3GPP TS 23.482: "Functional architecture and information flows for AIML Enablement Service".
[13] ITU-T Rec H.264 (08/2021): "Advanced video coding for generic audiovisual services" | ISO/IEC 14496-10:2022: "Information technology – Coding of audio-visual objects – Part 10: Advanced Video Coding".
[14] 3GPP TS 28.533: " Management and orchestration; Architecture framework”
[15] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1".
[16] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
[17] 3GPP TS 28.538: " Edge Computing Management".
[18] 3GPP TS 23.558: " Architecture for enabling Edge Applications".
[19] 3GPP TS 23.286: "Application layer support for Vehicle-to-Everything (V2X) services Functional architecture and information flows".
[20] 3GPP TS 23.255: "Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows".
[21] 3GPP TS 23.239: "Application enablement aspects for MMTel".
[22] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS)".
[23] 3GPP TS 23.502: "Procedures for the 5G System (5GS)"
|
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 [2] and clause 3 of 3GPP TS 29.222 [3] shall also apply.
|
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 given in clause 3 of 3GPP TS 23.222 [2] and clause 3 of 3GPP TS 29.222 [3] shall also apply.
|
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 network and UE capabilities in an easy-to-use way. SEAL services are generic to any application type.
Services at this layer are created by the combination use of different network connection layer capabilities from one or multiple Network Functions deployed in telecom system, may potentially combining the resources/information of SEAL client on the UE.
Services exposed at this layer normally is larger granularity than the services exposed by single network function at network connection layer and provide an application layer meaningful function. It could simply the application layer implementation compared to directly consume network connection layer services by invoking APIs one by one.
SEAL layer includes SEAL services server(s) and SEAL client(s).
- SEAL services server(s): it is implemented in network by MNO or 3rd part and are authorized to (1) provide services to application and SEAL client, and (2) consume 3GPP network services by invoking network APIs.
- SEAL client(s): it is implemented in UE and can be provided by same organization as SEAL service server or other origination e.g., UE vendor/OS and are authorized to (1) provide services to consumers by APIs, (2) consuming network services by invoking APIs from SEAL service server (3) trigger UE modem to initiate NAS procedures to request network capability so as to provide service result to application.
•
Figure 4.1.1-1: Layered representation of SEAL service layer in 3GPP network exposure system
|
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 when deployed as trusted AF in MNO's trusted domain as figure 4.x1.12-1.
NOTE 1: In the real case, SEAL server(s) may invoke service APIs exposed by 3GPP core network functions via NEF as a non-trusted AF e.g., when deployed by the third party.
NOTE2: SEAL server(s) when deployed as trusted AF in MNO's trusted domain may also invoke APIs from 3GPP core network functions via NEF.
SEAL server(s) invokes service APIs exposed by the OAM system over the OAM SBMA when deployed by MNO as specified in 3GPP TS28.533 [14].
NOTE 3: In the real case, SEAL server(s) may invoke service APIs exposed by 3GPP core network functions via AEF (e.g., when deployed by the third party, or even by MNO).
SEAL clients take two different responsibilities:
1) consumer of SEAL server API(s)
2) providing required terminal side information/resource to support the SEAL server function(s)
SEAL services APIs are provided and exposed by MNOs or third party, and they are consumed by the Application specific layer (VAL layer) or vertical application enabler layer (e.g., VAE server, UAE server), Edge enabler layer (e.g., EES, ECS), SEAL client(s) or third party's platform.
The interactions between the vertical application server(s) and SEAL server(s) for discovery, authentication and authorization are supported by CAPIF as specified in 3GPP TS 23.222 [9]. The VAL server acts as CAPIF's API invoker and SEAL server acts as CAPIF's API exposing function.
NOTE 4: It is up to application developer's implementation how to invoke the SEAL server's APIs in their application layer software.
NOTE 5: The API invokers as defined in 3GPP TS 23.222 [9] can either be on the network side (Application server) or on the UE side (e.g., SEAL clients, applications on UE), to use SEAL server API(s).
4.x2 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 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 operator’s business decision to deploy one or multiple services servers.
For each SEAL server, there is a related SEAL client resides on UE. The SEAL client connects to only the associated SEAL server.
Figure 4.2.1-1: SEAL functional entities
|
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 to improve the performance of applications traffic(s) in an easy-to-use way.
NOTE: The detailed information about NRM advantages to application developers is described in clause 5.3.
NRM client supports two types of functional role:
1) Provide assistant information or resource required by NRM server, to enable certain NRM service (e.g., providing MBMS listening status report required by NRM server to determine the data transmission mode), or
2) Trigger (acting asNRM service consumer) NRM server to excute NRM service logic, e.g., request NRM to manage End-to-End QoS service for traffic between application on one UE to application on another UE.
|
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, it will reduce latency and improve user experience of applications.
SEALDD client provides the capabilities which enable the application on the UE to request/receiving certain content from SEALDD server via SEALDD Uu.
Editor's Note: More content can be added later.
|
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/NRM/SEAL-DD which are specific to the usage of 5G/4G network capabilities.
- E-MMTel enabler which is specific the usage of IMS system capabilities.
- LMS utilize both 3GPP based position and non-3GPP based position.
- AI/ML enabler could support AI/ML service related to mobile UE, leveraging on the 3GPP network-for-AI capabilities
Service type
Service description
Benefits to application provides
NRM
• Provide value added APIs by abstrating the capabilties served by core network layer entities MB-SMF/PCF/NEF APIs/SCEF/BMSC, to enable third party to use 3GPP QoS service in a simple way
Simply the usage of App providers (APP deveolper, APP owner) of 3GPP network capabilities to:
- Improve qualitiy of application layer communication by using NRM API to tigger the 3GPP network connection with QoS supporting, compared to application layer communication over best effort 3GPP network connection.
SEAL DD
• Provide Caching and Distribution between application content server and mobile UE by using various 3GPP network capabilities designed for different type of application data to optimization purpose. For example reliable transmission mechanism specific to URLLC data.
Futher improve QoE of the applications when using Caching and Distribution service, by supporting the usage of 3GPP network capabilities(including control plane and user plane) for QoS optimization
NSCE
• Provide the API services to enable third party to retrive the slice SLA requirement automaticly, order slice product from MNO system, mornitor/change slice SLA, by aggregating the API services from OAM and Core network, SEAL layer services (service KQI information)
Provide the required functions(e.g deriving and recomending slice SLA to let a slice customer e.g., enterprise knows how much resource is required for there services) to enable third party to perform self-management operation on their dedicated slice, when NaaS is provided by operator OAM.
AI/ML enabler
• AI/ML AIMLE provides APIs for enabling and managing AI/ML services
• It leverages the network capabilities of 5G systems to support secure and efficient connection for mobile application to utilize AI services from MNO,
It could enable an MNO operator to use their AI capabilities to launch the new business to AI applications.
A mobile AI application can gain from offload the AI task to another node to promote the model performance or latency performance.
LMS
• LMS provides location management related functionality and location based services to the 3rd party applications. It utilizes the core network related location capabilities and value add on top of it in-order to provide a enriched location services.
Availability of enriched Location information from core network along with the GPS co-ordinates. provides readily available supplementary location based services such as geofencing, location deviation monitoring etc., apart from reporting and fetching of location information.
Group management
• Group management service provides the group management related operations considering the needs of multiple vertical applications. Apart from regular CRUD operations it provides the value add services like location based group creation, group regrouping, group member registration etc.
Re-usability : Single group management framework catering to multiple vertical needs easing the development time.
Configuration management
• Configuration management is to enable ASP to provide configuring data applicable to different vertical applications.
Re-usability : Single configuration management framework catering to multiple vertical needs easing the development time.
Digital asset
- Provides application enablement to Metaverse application by supporting following functionalities:
Digital asset profile management: which includes creating, updating, retrieving and deleting the digital asset profile
Digital asset discovery
- Digital asset media management – which includes uploading and downloading the digital asset media.
Capabilities to re-use the digital asset across multiple Metaverse applications (e.g. digital assets server provided by the MNO, which is trusted by different Metaverse applications to manage digital assets).
Spatial Anhor enabler and spitial mapping enabler
• Offers the platform for managing the spatial anchors and spatial maps for metaverse services. Enables the re-use of spatial anchors and spatial maps across multiple verticals and thus improving the metaverse experience for the end users.
Capability to re-use the spatial anchors and maps across multiple verticals.
Provides the insight on the spatial anchor usage to improve the effeciency
5.y2 Use cases and advantages for SEAL Service Xs 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 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 a copy of the website that is cached from the main server.
Existing widely deployed CDN server use Over-The-Top mechanism. It assumes network layer provide transparent forwarding of IP packets carrying application data. Normally it treats 3GPP mobile network as the same as other type of connection type.
Figure 5.2.1-1: Existing CDN data transmission by transparent forwarding
3GPP network specifies several mechanisms for improving the transmission quality of application data (e.g., PDU Set based QoS handling as defined by 3GPP TS 23.501 [8] and 3GPP TS 23.502 [23]), which requires application layer entity (e.g., application server) support some enhanced features e.g., using RTP or SRTP with RTP Header Extensions for PDU Set Marking as defined in 3GPP TS 26.522 [9] and together with RTP Payload Format;
SEALDD provides some enhanced content delivery functions, which fully use of 5G network to perform content delivery e.g., by providing application layer information required for 3GPP network layer transmission quality enhancement compared to transparent forwarding, the SEALDD data gets the best performance supporting from network. Thus, SEALDD provides content distribution service to third party with better service performance than CDN using Over-The-Top mechanism.
|
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 addition to the user plane co-operation between SEALDD and Network layer, SEALDD server also use the network APIs from 5G core control plane NF by behaving as trusted or untrusted AF, to trigger PDU Set based QoS handling for different data type, retrieving the network layer information to improving application layer data transmission mechanism (as figure 5.1.2-2).
Note: In some case, SEALDD server can also uses other SEAL service API e.g., NRM if deployed separated as 3GPP TS 23.433 [2].
Figure 5.2.2-2: SEALDD utilize 3GPP network APIs for different data traffic type
Compared to existing CDN, which provide the same transmission service to different applications. SEALDD could provide different mechanism to meet with different needs of applications as the following:
- Application layer signalling between AC and AS for different applications with different data transmission requirements.
- Best effort demanding applications;
- Low latency demanding applications like signalling for MCX call.
- Transmitting the application layer data for different applications with different data transmission requirement:
- Low latency and high reliable demanding application like remote robot/machine control.
- High data rate with low latency demanding application like Realtime XR video applications, Machine vision application
- Low latency like video call/voice call.
- Low cost demanding like background data
- Low power demanding like IoT device applications.
- Multiple flows synchronisation transmission service like multi-modal XR applications
Benefits to application providers (application owners/developers):
- Different applications will get different QoS assurance services for different data type when compared to using over-the-top CDN.
|
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
- supporting low power IOT device
The QoS mechanism supported by 5G network layer (NEF/SCEF or PCF/PCRF, MB-SMF) can be used for the case where the application providers negotiate the QoS parameters required for their applications and sign on business by offline way, or single QoS service for allow all application types can dynamically activating the network QoS service.
Since QoS assurance for different type of target applications requires different network resources and can cause different charging policy with different price, operator can need to further splitting QoS services into different types of QoS service. NRM service is defined to transform the 4G/5G network layer APIs to SEAL layer service API, to ease the usage of 3GPP QoS service (e.g., selecting the QoS services based on application needs).
5.3.2 Advantages and values of NRM Services
Figure 5.3.2-1: Capabilities of 5G system transformed by NRM service
The NRM service transforms 3GPP network capabilities and UE capabilities into the following types of service, enabling third party application providers to select and use network layer connection with different QoS services based on application needs, as shown in Figure 5.y.2-1:
NOTE: The NRM sever can directly connect to the core network entities which provides required capabilities when deployed in trusted domain of MNO. NRM may also connect to SCEF/NEF when deployed in untrusted domain or even in trusted domain.
- 4G/5G unicast network connection with different QoS
- 4G/5G multicast/broadcast network connection with QoS
- 5G network connection for TSC/TSN data flows
- 5G connection for background data transfer
- PDU session connection for low power IOT device
Benefits to application providers (application owners/developers):
- Simplifies the usage of 3GPP network capabilities by App providers (APP deveolper, APP owner)
- By using the NRM service APIs, QoE of the application can be improved when compared to application layer communication over best effort 3GPP network connection.
|
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 3GPP TR 23.700-35.
A.1 General description
SEAL layer services provides 3GPP enabler layer services, which are produced based on 3GPP system's capabilities. 3GPP SEAL layer services can be directly exposed to any applications, for example vertical applications of 5GAA,5GACIA as clause A.2. Meanwhile there is also other organzaitions working on the APP developer fcous APIs in their domain.
From 3GPP perspective, 3GPP API consumers can also be a third-party platform. There are no general restrictions on the API(s) consumer. It is possible that 3GPP application enabler layer( includingSEAL layer services) are selected by another API platform as SBI (e.g OP platform defined in GSMA Open gateway, or any hyperscaler’s API platforms), and making API formate transforming when needed to serve their target consumers as clause A.3.
NOTE: The content in Annex A is to provide the 3GPP understanding on the potential mapping relationship between 3GPP SEAL and the architecture defined by external organizations. It does not mandate any external SDO's decision on whether to adopt 3GPP SEAL service or re-specify their own value-add services by extra standard efforts.
A.2 Vertical applications consume 3GPP APIs directly
Figure A.2-1: Independent value-added service system with 3GPP SEAL layer
3GPP NBI including the APIs supporting network layer services, and also the APIs supporting application enabler layer services. These APIs can be directly invoked by vertical applications including applications defined in 5GAA, or 5GACIA etc.
External SDO platform can also support APIs for applications. It can only invoke 3GPP APIs supporting network layer services and defined their self-defining value-added layer services, then expose the 3GPP network layer services and value-added layer services by their defining non-3GPP NBI.
The non-3GPP NBI can expose the same services or different services with what are exposed by 3GPP NBI (possible with different stage-3 API design).
It up to each external platform provider/SDO's decision whether and how to make alignment with 3GPP NBI for the same services.
MNO operator can deploy 3GPP platform (together with 3GPP enabler layer services) and /or external SDO platform.
A.3 SEAL layer services as the SBI of external API platform
Figure A.3-1: Standard alternatives of exposure platform for market
3GPP application enabler layer including SEAL layer APIs are selected by external SDO as SBI In this solution, it is assumed external platform selects the 3GPP API(s) including network layer and application enabler layer APIs as southbound. Based on their customer's requirement, external platform can use the network layer services by adopting network API. Or it can use application enabler layer services by adopting 3GPP application enabler API(s).
External platform can perform API transformation upon 3GPP API(s), if 3GPP API(s) cannot be directly matched to their application layer's requirement.
Annex B:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-10
SA6#69
S6-254792
TS skeleton
0.0.0
2025-10
SA6#69
Implementation of the following pCRs approved by SA6: S6-254660, S6-254661, S6-254662, S6-254692
0.1.0
2025-11
SA6#70
Implementation of the following pCRs approved by SA6: S6-255590, S6-255591, S6-255592, S6-255672, S6-255674, S6-255675, S6-255676
0.2.0
|
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 intent guarantee requirements, support for intent traceability and support for natural language expression in intents.
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 28.312: "Management and orchestration; Intent driven management services for mobile networks".
[2] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[3] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
[4] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state".
[5] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[6] 3GPP TS 28.537: "Management and orchestration; Management capabilities".
[7] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2".
[8] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[9] 3GPP TR 28.914: "Study on intent driven management service for mobile network phase 3".
[10] 3GPP TS 28.105: "Management and orchestration; Artificial Intelligence/ Machine Learning (AI/ML) management".
[11] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[12] 3GPP TS 28.561: "Management and orchestration; Management aspects of network digital twins".
[13] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
|
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
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1 Use case #1: Enhancement of radio service delivering and assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation for delivering a radio service is described in clause 5.1.2. The RadioServiceExpectation is defined to represent MnS consumer's expectations for radio service delivering and assurance in the specified area. However, following scenarios are not supported:
- MnS consumer expresses the radio service delivering and assurance expectation with service reliability information.
- MnS consumer expresses the radio service delivering and assurance intent expectation for a specified area described in the form of civic location. The civic area can be represented by a civic address (e.g. country A, Building B, ROOM C) or location name (e.g. hotel name, school name). For example, MnS consumer wants to ensure the radio service targets (dLThptPerUETarget and dLLatencyTarget) for a specific civic address (e.g., the CivicAddress defined in clause 6.1.6.2.14 in TS 29.572 [3]).
- MnS consumer expresses the radio service delivering and assurance expectation for a specified assurance time duration. Using the concert as an example, MnS consumer expresses the intent indicating a radio service to be delivered and assured for two hours, or before concert, MnS consumer request to explore the supported maximum number of UE for the Radio Service which to be assured for two hours after it being delivered.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.2 Potential requirements
| REQ-IDMS_RadioServiceIntent-CON-1: The intent driven MnS producer for radio service should have capabilities enabling the MnS consumer to express service reliability requirements.
REQ-IDMS_RadioServiceIntent-CON-2: The intent driven MnS producer for radio service should have capabilities enabling the MnS consumer to express radio service delivering and assurance for a specified area described in the form of civic location.
REQ-IDMS_RadioServiceIntent-CON-3: The intent driven MnS producer for radio service should have capabilities enabling the MnS consumer to express radio service assurance time duration requirements.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.3 Potential solutions
| This solution proposes to reuse and enhance the existing RadioServiceExpectation defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Add following attributes as the ExpectationTargets for the RadioServiceExpectation to enable the MnS consumer to express service reliability requirements.
- ReliabilityTarget, it represents the reliability target for the radio service that the intent expectation is applied.
Enhancement Aspect2: Add following attributes as the ObjectContexts for the RadioServiceExpectation to enable the MnS consumer to express radio service delivering and assurance requirements for a specified area described in the form of civic address.
- CivicAreaContext, the coverage areas for the Radio Service that the intent expectation is applied in the form of civic area (i.e. represented by CivicArea <<dataType>>). The CivicArea <<dataType>> can support civic address (e.g. streets, districts, seats, etc.) or location label (e.g. hotel name, school name). The detailed definition for civic address reuses the CivicAddress Data Type defined in clause 6.1.6.2.14 in TS 29.572 [3]. The type for locationLabel is string. Following is the proposed definition for CivicArea <<dataType>>.
Attribute Name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
civicAddress
O
T
T
F
F
locationLabel
O
T
T
F
F
NOTE: The locationLabel can be used if the location cannot be expressed by civic address. The locationLabel should be used without ambiguity.
Enhancement Aspect3: Add following attributes as the Expectation Contexts for the RadioServiceExpectation to support assurance duration information:
- AssuranceDurationContext, it describes the time duration at which the radio service instance should be scheduled to be delivered and available. The type is integer and unit is hour.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2 Use case #2: Enhancement of radio network performance assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation on radio network performance to be assured and intent containing an expectation for RAN energy saving are described in clause 5.1.5 and clause 5.1.7. The RadioNetworkExpectation is defined in clause 6.2.2.1.1 to represent MnS consumer's expectations for radio network delivering and performance assurance. However, following scenarios are not supported:
- MnS consumer expresses radio network performance assurance expectation for a specific RAN feature (e.g., RedCap). For example, MnS consumer may express the radio network performance targets (e.g. weakRSRPRatioTarget, highUlPrbLoadRatioTarget and aveULRANUEThptTarget) to be assured for RedCap UEs in the specified areas. The detailed RAN feature need further investigation on TS 38.304 [4] and TS 38.331 [5].
- MnS consumer expresses relative values for several performance targets for the specified areas. For example, MnS consumer may express the expectation on RAN energy consumption reduction ratio (as percentage) for RAN SubNetwork that the intent expectation is applied to illustrates the difference between the energy consumption before and after performing energy saving actions.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.