hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 5 Key Issues
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 5.1 Key Issue #1: ADC establishment in alerting phase for early media
| This key issue will investigate how to support IMS application data channel establishment in alerting phase to provide early media for a normal IMS DC session.
This Key Issue will study:
- Whether and how the capability of supporting ADC establishment in alerting phase is exchanged between UE and IMS network.
- How the use of ADC during alerting phase is controlled.
- Whether and how to download a specific list of DC applications that can be used during alerting phase.
- How to establish and terminate an ADC during alerting phase.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 5.2 Key Issue #2: Enhancements to capability exposure framework for eMMTel services
| This Key Issue will investigate how to enhance IMS capability exposure framework to expose IMS capability for eMMTel services (voice/video) and related events besides Data Channel, supporting IMS session establishment, modification and release to enable eMMTel services that may require enhancing audio/video services with DC capabilities.
Solutions should describe how to enhance Rel-19 IMS event exposure framework and event definition to support IMS DC events supported by DCSF (e.g. application downloading event) and non-DC events, including subscriber specific and non-subscriber specific supported by IMS AS.
NOTE 1: This Key Issue will analyze relevant use cases, the gap between OMA and 3GPP APIs and specify exposure functionality missing from OMA APIs.
NOTE 2: This Key Issue does not intend to transfer the responsibility of OMA API(s) to 3GPP.
This Key Issue will study:
- Identification of new events and/or capabilities to be exposed, in addition to those already listed in Table AD.2.5.3-1 of TS 23.228 V19.3.0 [2].
- Assessment of whether existing OMA APIs support the exposure of the newly identified events and/or capabilities.
- Possible enhancement of exposure functionality where the assessment above identifies gaps in supporting exposure of the newly identified events and/or capabilities.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 5.3 Key Issue #3: Supporting dynamic configuration of MDC2 endpoints
| This Key Issue will investigate whether and how to define interfaces between DCSF and NEF/AF to complete existing P2A/P2A2P Data Channel procedures by specifying DC3/DC4 interfaces to enable dynamic configuration of MDC2 endpoints.
This Key Issue will study:
- the services and information elements that are exposed via DC3/DC4 for UE initiated P2A and P2A2P ADC session establishment.
5.X Key Issue #X: Key Issue Title
Editor's note: After approval of a Study Item Description by TSG SA the Key Issues to be included in the TR should be prepared.
- The rapporteur takes the lead to ensure input on draft Key Issues to the first meeting
- The rapporteur can draft these themselves, or ask for volunteers for each
- These should be distributed before the meeting for discussion during a conference call (if organized) or via email (this is not mandatory, but is advised)
- Companies are allowed to submit their own proposals for the Key Issues
It is recommended that the Key Issues are based on the Work Tasks documented in the Study Item Description.
Updates of these Key Issues, or addition of Key Issues, are allowed as required but this should be done as early as possible during the study.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6 Solutions
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.0 Mapping of Solutions to Key Issues
| Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
<Key Issue #X>KI#1
<Key Issue #Y>KI#2
KI#3
#1
x
#2
x
#3
x
#4
x
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.1 Solution #1: ADC establishment in alerting phase initiated by the UE
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.1.0 High-level solution Principles
| This solution addresses Key Issue #1: DC establishment in alerting phase for early media.
The solution reuses R19 23.228 [2] with the addition that
- Based on the UE request (via a specific root URL) , the DSCF sends to the UE(s) an application list related with the alerting phase- The calling party receive BDC from the terminating network during alerting phase.
- The UE(s) decide whether and which application to download (as per R19 specifications)
- The UE(s) decide when to release an application that was running in alerting phase; they may decide to continue this application after the alerting phase has finished. (as per R19 specifications)
The solution may e.g. be used for the case where the originating UE1 calls a help center and is immediately provided with an App that the user will be using when interacting with the call center.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.1.1 Description
| This solution provides a procedure on how to establish a P2A ADC in alerting phase.
Editor's Note: Current version of the solution supports P2A ADC establishment in alerting phase. it is FFS whether it can support other forms of ADC, i.e., P2A2P and P2P.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.1.2 Procedure
| The pre-condition of ADC establishment in alerting phase is the capability negotiation during the IMS registration phase on whether the UE supports the DC in alerting phase.
Based on the IMS DC capability negotiation defined in clause AC.7.0 of TS 23.228 [2], when the UE supporting DC in alerting phase and the UE is allowed to use DC in alerting phase, it includes the media feature tag of supporting DC in alerting phase in the Contact header field of the initial REGISTER request and any subsequent REGISTER request to allow the home IMS network to discover its capability of supporting DC in alerting phase.
If the IMS network supports DC in alerting phase, the S-CSCF includes a Feature-Caps header field indicating its capability of supporting DC in alerting phase in the 200 OK response to the initial and any subsequent REGISTER request, which is used by the UE to discover the IMS data channel capability of its home IMS network.
The UE may receive a Feature-Caps header field indicating IMS's capability of supporting DC in alerting phase in the 200 OK response to a subsequent REGISTER request when the network starts supporting DC in alerting phase after successful initial registration of the UE.
When the UE supporting DC in alerting phase initiates an IMS session and if the UE is allowed to use DC in alerting phase, it includes the media feature tag in the Contact header field of the initial INVITE message, regardless of data channel media being part of the SDP or not.
The UE shall not include the media feature tag in the Contact header field and data channel media description in the SDP offer of the initial INVITE request or any subsequent re-INVITE request message, if the S-CSCF has not included the capability indication of supporting DC in alerting phase in the Feature-Caps header field in the 200 OK response either to the initial REGISTER or a subsequent REGISTER request message.
If the UE is not configured whether to use DC in alerting phase, it is up to UE implementation whether or not to include the media feature tag in the Contact header field.
With a successful capability negotiation about the support of DC in alerting phase, the procedure is illustrated in Figure 6.1.2-1, which is based on clause AC.7.2.2 in TS 23.228 [2].
Figure 6.1.2-1: Procedure of ADC establishment in alerting phase.
The steps in the procedure are as follows:
1. Same as Step 1-14 of clause AC.7.1 in TS 23.228 [2], UE#1 initiates a SIP INVITE towards the IMS AS. After validating the user’s subscription, the IMS AS notifies the DCSF about DC support. The DCSF provides the IMS AS with instructions and media information for establishing BDC. The IMS AS allocates resources with MF accordingly and updates the INVITE with the negotiated media. The updated SIP INVITE is forwarded to the terminating network/UE#2 for terminating network negotiation.
2-3. UE#2 and terminating network returns an 18x response with the SDP answer to BDC to originating network. According to the received SDP answer, MF may update data channel media resource information for UE#2.
4. The IMS AS notifies the successful session establishment event, Nimsas_SessionEventControl Notify (SessionEstablishmentSuccessEvent, Session ID, Media Info List) to DCSF.
5. The DCSF responds to the Nimsas notification request.
6. The SIP message18x is forwarded to UE#1 which indicates the BDC has been established and that the alerting phase has started.
7. The originating network P-CSCF executes QoS procedure for BDC as specified in TS 23.203 [4] and TS 23.503 [5].
8. PRACK and 200 OK for PRACK procedure are performed.
9-10.
When the BDCs have been established between terminating MF and UE#1/UE#2, the DC application list for alerting phase and DC application for alerting phase is requested and downloaded to UE#1 and UE#2 from terminating DCSF.
The DCSF provides via MF the application list for alerting phase from the received specific URL , further to UE#1 and UE#2, based on their data channel capabilities and their choices.
The UE(s) use a specific URL related with the fact that they request a list of applications available in the alerting phase
Editor’s Note: it is FFs how the UE is alerted to initiate the download
11. UE#1 initiates a P2A ADC for the selected DC application for alerting phase. UE#1 sends SIP UPDATE with an updated SDP to IMS AS via originating network P-CSCF and S-CSCF. The updated SDP contains the BDC information, as well as the requested ADC and the associated DC application binding information.
12. Same as Step 3-14 of clause AC.7.2.2-1 in TS 23.228 [2], the IMS AS notifies the DCSF about DC support. The DCSF instructs the IMS AS to establish MF anchoring via MDC2. The IMS AS provisions the necessary media resources at the MF and returns the information to the DCSF. The DCSF then initiates ADC setup toward the DC Application Server via DC3/DC4. After receiving the DC AS’s response with its own MDC2 media resource, the DCSF instructs the IMS AS to update the MF resource accordingly. The IMS AS completes the MF configuration and notifies the DCSF.
13-14. IMS AS sends the SIP UPDATE to remote network side and UE#2, via the originating S-CSCF, which does not include a request in the SDP for the ADC.
15-17. UE#2 and terminating network returns a SIP UPDATE 200 OK response with SDP answer for audio/video/bootstrap.
18. IMS AS notifies the DCSF about the successful result of media confirmation.
19. DCSF replies to the notification.
20. The IMS AS includes SDP answer for ADC to UE#1 in SIP UPDATE 200 OK response that it sends towards the UE 1 via the S-CSCF and P-CSCF.
21. The originating network P-CSCF executes QoS procedure for ADC media based on the SDP answer information from the 200 OK response.
22. SIP UPDATE 200 OK forwarded to UE#1 with ADC SDP answer.
23. The ADC between UE#1 and DC AS is established via MF. MF forwards data channel traffic between UE#1 and DC AS based on MDC2 media point information.
24-25. UE#2 answers the call, and SIP INVITE 200 OK response is sent to the IMS AS via I/S-CSCF.
26. The IMS AS notifies the DCSF, via Nimsas_SessionEventControl_Notify (Session ID) of the call state change.
27. DCSF replies to the notification.
28-29. SIP INVITE 200 OK forwarded to UE#1 which indicates the call is answered, and ACK procedure is performed.
30. Both UE#1 and UE#2 retrieve a new application list via BDC since call is answered. The new list supersedes the previously downloaded list. The UEs send request to MF to request application list by providing a root URL, via the established BDC with its data channel capabilities. The DCSF provides the application list from the root URL provided by UE#1 via MF, further to UE#1 and UE#2, based on their data channel capabilities and their choices through MF.
31. Subsequent procedures for DC application, as defined in clause AC.7.2 of TS 23.228 [2]. Depending on the application and user interaction, the UE(s) determine when to release the application initiated in alerting phase but this aspect is out of scope of specifications and does not require a new UE behavior..
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.1.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- supporting retrieving DC application list and DC application for alerting phase; this includes providing a specific URL to get from DCSF the application list for alerting phase,
- supporting ADC establishment in alerting phase.
IMS AS:
- supporting negotiation of ADC in alerting phase.
Editor’s Note: impacts on IMS AS and DCSF are FFS
DCSF:
- providing DC application list based on the specific URL received from the UE and associated with the application list for alerting phase.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.2 Solution #2: Support for NW initiated data channel application in early media session with subscription
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.2.1 High level principles
| This solution has the following high level principles, in order to support IMS data channel application in early media session:
- Data Channel Application in Alerting Phase (DCAP) service can be configured by the user and stored in the HSS as part of the subscription data.
- IMS AS triggers the application data channel in alerting phase based on UE subscription data.
- IMS AS performs as a B2BUA to update the SDP for data channel in early session and media flow for the main session.
- The application data channel may coexistent with other early session services, e.g., CAT, CRS.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.2.2 Description
| This is a solution for Key issue #1 " DC establishment in alerting phase for early media".
The user of UE#2 is able to subscribe to the Data Channel Application in Alerting Phase (DCAP) service, including activate (or de-activate) the service, and update the settings, e.g., to change by configuration the active data channel application. The DCAP subscriber is able to refine the data channel application selection behaviour with configured rules, e.g. time, calling party's location, called party's location, the identity of the calling and called party. The DCAP service is able to select the appropriate data channel application according to the rules.
DCAP is a terminating network service, but can also have an originating network functional component. That is, DCAP can be selected on behalf of the called subscriber for presentation to the calling party, but the calling (IMS) subscriber can also subscribe to and activate the DCAP service.
Editor's note: The consideration on originating user consent of NW initiated ADC is FFS.
6.2.3 Procedures
The overall procedures of data channel establishment in early media phase are illustrated in figure 6.2.3-1.
Figure 6.2.3-1: ADC establishment in early media phase
0. The user of UE#2 subscribes Data Channel Application in Alerting Phase (DCAP) service to his/her serving IMS network. The data channel application to be initiated in alerting phase is selected by the user and configured in UE#2’s subscription data.
1. UE#1 sends a SIP INVITE targeting UE#2. The initial SDP contains offers for audio/video flow, bootstrap data channel. UE#1 indicates support for preconditions, reliable provisional responses, and indication of early-session supported.
2. The IMS AS sends Nimsas_SessionEventControl_Notify to the selected DCSF to notify the session establishment.
3. If the remote bootstrap data channel (BDC from UE#1 to the DCSF in the terminating network) is not requested by UE#1, the DCSF instructs the IMS AS to add the bootstrap data channel.
4. The DCSF invokes the Nimsas_MediaControl_MediaInstruction instructing the IMS AS how to set up bootstrap data channel with MF both for originating and terminating side.
5. The IMS AS instruct the MF to allocate required bootstrap data channel media resources.
6. The IMS AS responds to the MediaInstruction request received in step 4.
7. The DCSF responds to the Notify Request received in step 2.
8. The IMS AS sends the INVITE to UE#2.
9. UE#2 determines the subset of the media flows and responds with an Offer Response message back to the IMS AS.
10. The IMS AS forwards the Offer Response message (e.g., 183 Session Progress) to UE#1. The IMS AS may add a remote bootstrap data channel with UE#1 if not request in the INVITE message.
11-12. UE#1 reserves resource and confirms receipt of the Offer Response and sends the PRACK, which acknowledges the 183 (Session Progress) provisional response, towards UE#2.
13-14. UE#2 reserves resource and sends a SIP 200 (OK) response for the SIP PRACK request to UE#1. The BDC between the DCSF and UE#1 is established and UE#1 downloads the DC application list from the DCSF.
15. UE alerts the user and sends Ringing indication to the IMS AS.
16. Base on UE#2’s subscription of DCAP service and the availability of BDC to UE#1, the IMS AS decides to trigger the pre-configured data channel application to UE#1.
Editor's note: When the IMS AS triggers the ADC is FFS (e.g., after receiving 183 or 180 message) .
17. The IMS AS notifies the DCSF with the request of data channel application (e.g., application ID) in alerting phase.
18-19. The DCSF determines the media parameters for the application data channel and responses to the IMS AS.
20. The IMS AS instructs the MF to reserve the media resource and MDC2 end points to the DC AS.
21. The IMS AS response the DCSF the MediaInstruction with MDC2 end points information.
22. The DCSF indicate the DC AS reserving the media resource for the application data channel and MDC2 end points to the MF.
23-24. The DCSF response the notification in step 17 and instructs the MF to update the media resource.
25. The IMS AS triggers the IMS session update to UE#1 containing SDP for the application data channel with an indication of early media.
26. If the data channel application is not locally available, UE#1 downloads the application form the DCSF via the established bootstrap data channel.
27. UE#1 confirms the update for the application data channel.
28. UE#1 starts data channel application with the DC AS in early session.
29. UE#2 accepts the session and sends 200 OK to the INVITE.
30-31. The IMS AS updates UE#1 with SDP offer to initiate the media flow of the main session and terminate the application data channel in the early session.
32. The IMS AS instructs the MF to update the media resource and terminate the application data channel.
33-34. The IMS AS forwards 200 OK to UE#1. UE#1 sends ACK to UE#2.
35. The media flow of the main session between UE#1 and UE#2 starts.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.2.3 Procedures
| The overall procedures of data channel establishment in early media phase are illustrated in figure 6.2.3-1.
Figure 6.2.3-1: ADC establishment in early media phase
0. The user of UE#2 subscribes Data Channel Application in Alerting Phase (DCAP) service to his/her serving IMS network. The data channel application to be initiated in alerting phase is selected by the user and configured in UE#2's subscription data.
1. UE#1 sends a SIP INVITE targeting UE#2. The initial SDP contains offers for audio/video flow, bootstrap data channel. UE#1 indicates support for preconditions, reliable provisional responses, and indication of early-session supported.
2. The IMS AS sends Nimsas_SessionEventControl_Notify to the selected DCSF to notify the session establishment.
3. If the remote bootstrap data channel (BDC from UE#1 to the DCSF in the terminating network) is not requested by UE#1, the DCSF instructs the IMS AS to add the bootstrap data channel.
4. The DCSF invokes the Nimsas_MediaControl_MediaInstruction instructing the IMS AS how to set up bootstrap data channel with MF both for originating and terminating side.
5. The IMS AS instruct the MF to allocate required bootstrap data channel media resources.
6. The IMS AS responds to the MediaInstruction request received in step 4.
7. The DCSF responds to the Notify Request received in step 2.
8. The IMS AS sends the INVITE to UE#2.
9. UE#2 determines the subset of the media flows and responds with an Offer Response message back to the IMS AS.
10. The IMS AS forwards the Offer Response message (e.g. 183 Session Progress) to UE#1. The IMS AS may add a remote bootstrap data channel with UE#1 if not request in the INVITE message.
11-12. UE#1 reserves resource and confirms receipt of the Offer Response and sends the PRACK, which acknowledges the 183 (Session Progress) provisional response, towards UE#2.
13-14. UE#2 reserves resource and sends a SIP 200 (OK) response for the SIP PRACK request to UE#1. The BDC between the DCSF and UE#1 is established and UE#1 downloads the DC application list from the DCSF.
15. UE alerts the user and sends Ringing indication to the IMS AS.
16. Base on UE#2's subscription of DCAP service and the availability of BDC to UE#1, the IMS AS decides to trigger the pre-configured data channel application to UE#1.
Editor's note: When the IMS AS triggers the ADC is FFS (e.g. after receiving 183 or 180 message).
17. The IMS AS notifies the DCSF with the request of data channel application (e.g. application ID) in alerting phase.
18-19. The DCSF determines the media parameters for the application data channel and responses to the IMS AS.
20. The IMS AS instructs the MF to reserve the media resource and MDC2 end points to the DC AS.
21. The IMS AS response the DCSF the MediaInstruction with MDC2 end points information.
22. The DCSF indicate the DC AS reserving the media resource for the application data channel and MDC2 end points to the MF.
23-24. The DCSF response the notification in step 17 and instructs the MF to update the media resource.
25. The IMS AS triggers the IMS session update to UE#1 containing SDP for the application data channel with an indication of early media.
26. If the data channel application is not locally available, UE#1 downloads the application form the DCSF via the established bootstrap data channel.
27. UE#1 confirms the update for the application data channel.
28. UE#1 starts data channel application with the DC AS in early session.
29. UE#2 accepts the session and sends 200 OK to the INVITE.
30-31. The IMS AS updates UE#1 with SDP offer to initiate the media flow of the main session and terminate the application data channel in the early session.
32. The IMS AS instructs the MF to update the media resource and terminate the application data channel.
33-34. The IMS AS forwards 200 OK to UE#1. UE#1 sends ACK to UE#2.
35. The media flow of the main session between UE#1 and UE#2 starts.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.2.4 Impacts to Services, Entities and Interfaces
| UE
- Indicates supporting of early media session in SIP INVITE message, as specified in existing specification, e.g., TS 24.229 [6].
- Supports application data channel in the early session.
HSS
• Supports management of user subscription for Data Channel Application in Alerting Phase (DCAP) service.
• Supports the user configuration of data channel application(s) in alerting phase.
IMS AS:
- Triggers the application data channel in alerting phase.
- Terminates the application data channel when the call accepted by the terminating UE.
- Performs as B2BUA to update the media flow in the SDP exchanged with UE.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.3 Solution #3: IMS ADC establishment during alerting phase when initial INVITE does have BDC offer
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.3.0 High-level solution Principles
| The main principle of this solution for support of application data channel establishment during alerting phase of normal IMS DC session as follows
- The calling party will receive bootstrap data channel offer from the terminating network during alerting phase.
- The calling party will establish the bootstrap data channel, download the application and based on the interest, trigger application data channel establishment by selecting one particular application from the terminating network.
- The called party after getting notification about the application running status in the calling party device, will establish bootstrap data channel, download the application and once accepts the session, the call will be established.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.3.1 Description
| This paper proposes solution for supporting application data channel establishment during alerting phase when calling party has offered bootstrap data channel in the initial INVITE.
In this proposal, the calling party and the called party will establish bootstrap data channel(s), download application or application list and establish application data channel while call has not yet been established.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.3.2 Procedures
| The procedure of establishing application data channel during alerting phase
Figure 6.3.3-1: ADC establishment in early media phase
1. UE-A sends an initial SIP INVITE request to the originating IMS AS through P-CSCF and S-CSCF with an initial SDP offer for audio/video and for the bootstrap data channel establishment with bootstrap DC stream ID. The SDP contains bootstrap data channel offers for both the originating and the terminating side. P-CSCF may include the P-Early-Media header field to indicate the support for early media authorization in the initial SIP INVITE request.
NOTE: The UE is assumed to support P-Early-Media.
2-13. of Clause AC.7.1 in TS 23.228 [2] apply.
14. UE-B returns a SIP 18X response with an SDP answer for bootstrap data channel to the originating network. The terminating IMS AS includes P-Early-Media header field in the SIP 18X response indicating early media is allowed based on the SDP answer not including any application data channel.
15. The bootstrap data channel has been established between originating MF and UE-A. The UE shall request for a data channel application or data channel applications list from the MF via the established bootstrap data channel. The DCSF provides the data channel application or the data channel application list to UE-A through MF. UE-A may download the data channel application or the data channel application list through the established bootstrap data channel. .
16. The bootstrap data channel has also been established between terminating MF and UE-A.
17. UE-A sends a SIP PRACK request towards the terminating side before or during Step 15.
18. UE-B returns a SIP 200 OK response for the PRACK. Simultaneously, UE-B may alert the terminating user that the incoming session is a normal IMS DC session.
19. After the DC application is downloaded, UE-A initiates a SIP UPDATE request to update the IMS session for adding the application data channel and to inform UE-B about the associated DC application binding information. The IMS AS shall notify DCSF about the media change request event and request MF to allocate media resources for the application data channels based on instructions received from the DCSF if MF is anchoring application data channel. Once acknowledgement is received from the DCSF, the IMS AS shall send the update request to the terminating side and UE-B through S-CSCF. The SIP UPDATE request with the modified SDP offer includes the negotiated bootstrap data channel media description, requested application data channel media description and the associated data channel application binding information.
The IMS AS includes P-Early-Media header field in the SIP UPDATE request to indicate that early media is allowed based on the previously received SDP answer not indicating any application data channel.
20-22. The bootstrap data channel has been established between the originating MF and UE-B. The bootstrap data channel has also been established between the terminating MF and UE-B. UE-B may alert the terminating user that the data channel application is running in UE-A and to download the data channel application if not already available in UE-B. UE-B shall request for the data channel application and the DC application list from the MF for downloading via the established bootstrap data channels if needed.
23-29. When the DC application is available in UE-B, then the terminating network sends a 200 OK response to the originating side based on which the IMS AS notifies DCSF of the successful bootstrap DC and application DC establishment. Once the DCSF responds to the session establishment request, 200 OK response is forwarded to the UE-A. The originating network P-CSCF executes QoS procedures for bootstrap data channel. The IMS AS may include P-Early-Media header field in the 200 OK response to the SIP UPDATE request to indicate that early media is allowed. UE-B alerts the terminating user for running the DC application.
30. UE-B returns a SIP 180 response indicating that UE-B is ringing.
31. Once UE-B accepts to run the DC application, UE-B answers the IMS session. UE-B sends 200 OK to the initial SIP INVITE request and subsequent procedures follow.
Editor's note: The consideration on originating user consent of NW initiated ADC during alerting phase is FFS.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.3.3 Impacts on Services, Entities and Interfaces
| Editor’s Note: Impacts are FFS.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4 Solution #4: IMS ADC establishment during alerting phase when initial INVITE does not have BDC offer
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4.0 High-level solution Principles
| The main principle of this solution for support of application data channel establishment during alerting phase of normal IMS DC session as follows
- The calling party will receive bootstrap data channel offer from the terminating network during alerting phase.
- The calling party will establish the bootstrap data channel, download the application and based on the interest, trigger application data channel establishment by selecting one particular application from the terminating network.
- The called party after getting notification about the application running status in the calling party device, will establish bootstrap data channel, download the application and once accepts the session, the call will be established.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4.1 Description
| This paper proposes solution for supporting application data channel establishment during alerting phase when calling party has not offered bootstrap data channel in the initial INVITE.
In this proposal, one scenario is explained how the called party (e.g., restaurant customer service) network is providing bootstrap data channel offer to the calling party during alerting phase so that the calling party can establish bootstrap data channel, download the application or application list and then session is established once called party user accepts it.
Scenario.
• The calling party triggers a normal call to restaurant customer service with intention of reserving seats for lunch.
• The called party has taken an interactive ringback tone service which means whenever any incoming session is received for that restaurant, the network will offer bootstrap data channel and list of applications provided by the restaurant.
• The calling party will establish the bootstrap data channel, download the list of applications and select “seat reserve” application.
• The called party based on the notification of running application on the calling party side will download the application if not available and then accepts the session.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4.2 Procedures
| The procedure of establishing application data channel during alerting phase
Figure 6.4.3-1: ADC establishment in early media phase
1-2. UE-A sends an initial SIP INVITE request to the terminating side through P-CSCF and S-CSCF with an initial SDP offer for audio/video. P-CSCF may include the P-Early-Media header field to indicate the support for early media authorization in the initial SIP INVITE request.
NOTE: The UE is assumed to support P-Early-Media
3. UE-B returns a SIP 18X response with an SDP answer for audio/video session to the originating network. The terminating IMS AS includes P-Early-Media header field in the SIP 18X response indicating early media is allowed.
4-5. UE-A sends a SIP PRACK request towards the terminating side and UE-B returns a SIP 200 OK response for the PRACK.
6. UE-B sends a SIP UPDATE request to the terminating IMS AS through P-CSCF and S-CSCF with an SDP offer for audio/video and bootstrap data channel. The SDP contains bootstrap offer for the terminating side. Steps 2-10 of Clause AC.7.1 in TS 23.228 apply in which the terminating IMS AS determines to notify the terminating DCSF based on DC subscription and UE-B DC capability and the DCSF instructs the IMS AS and MF to establish the resource required for the terminating side. In this scenario, the DCSF allows for application selection from the remote UE, even before the application has been selected by the peer UE.
7. IMS AS sends the modified SIP UPDATE request including the SDP offer for audio/video and bootstrap data channel adding media information of MF to the originating side and UE-A.
8. Originating IMS AS determines to notify DCSF based on DC subscription and UE DC capability. If the network does not support DC service or UE-A does not have DC capability, then the originating network sends an SDP answer to setup only audio/video session and remove any bootstrap data channel media information.
9. The bootstrap data channel has been established between terminating MF and UE-A. The UE shall request for a data channel application or data channel applications list from the MF via the established bootstrap data channel. The DCSF provides the data channel application or the data channel application list to UE-A through MF. UE-A may download the data channel application or the data channel application list through the established bootstrap data channel.
Editor's note: The consideration on originating user consent of NW initiated ADC during alerting phase is FFS.
10. Once the bootstrap data channel has been established, UE-A sends 200 OK response for the SIP UPDATE request to the terminating side.
11. UE-B alerts the terminating user to indicate an incoming IMS session.
12. After the DC application is downloaded, UE-A initiates a SIP UPDATE request to update the IMS session for adding the application data channel and to inform UE-B about the associated DC application binding information. The IMS AS shall notify DCSF about the media change request event. Once acknowledgement is received from the DCSF, the IMS AS shall send the update request to the terminating side and UE-B through S-CSCF. The SIP UPDATE request with the modified SDP offer includes the negotiated bootstrap data channel media description, requested application data channel media description and the associated data channel application binding information.
The IMS AS includes P-Early-Media header field in the SIP UPDATE request to indicate that early media is allowed based on the previously received SDP answer not indicating any application data channel.
13-14. The bootstrap data channel has been established between the terminating MF and UE-B. UE-B may alert the terminating user that the data channel application is running in UE-A and to download the data channel application if not already available in UE-B. UE-B shall request for the data channel application and the DC application list from the MF for downloading via the established bootstrap data channels if needed.
15-21. When the DC application is available in UE-B, then the terminating network sends a 200 OK response to the originating side based on which the IMS AS notifies DCSF of the successful bootstrap DC and application DC establishment. Once the DCSF responds to the session establishment request, 200 OK response is forwarded to the UE-A. The originating network P-CSCF executes QoS procedures for bootstrap data channel. The IMS AS may include P-Early-Media header field in the 200 OK response to the SIP UPDATE request to indicate that early media is allowed.
22. UE-B alerts the terminating user for running the DC application.
23. The UE-B returns a SIP 180 response to indicate the UE-B is ringing.
24. Subsequent procedures continue. When the terminating user accepts to run the DC application for communication, the UE#2 answers the IMS session.
Editor's note: How to handle the both the existing ring back tone and interactive ring back tone together is FFS.
Editor's note: The BDC and ADC procedure should be executed before or after 180 ringing is FFS.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4.3 Impacts on Services, Entities and Interfaces
| This solution may have the following impacts to existing entities and interfaces:
IMS AS:
- Terminating IMS AS will provide a new offer for IMS bootstrap data channel based on the interactive ringback tone service subscription of called party user.
Editor's Note: Additional Impacts are FFS
6.X Solution #X: <Solution Title>
Editor’s Note: This Rapporteur is picky – please use unique descriptive titles for all solution proposals.
6.X.0 High-level solution Principles
Editor's note: Where possible similar/overlapping solution proposals should be documented as a single solution in the TR.
Documentation of more than one solution from the same company for the same KI is allowed but it shouldn't be expected that all of them will be documented in the TR.
6.X.1 Description
Editor's note: This clause will describe the solution principles and architecture assumptions for corresponding key issue(s). Further (sub-)clause(s) may be added to capture details.
6.X.2 Procedures
Editor's note: This clause will describe the high-level procedures and information flows for the solution.
6.X.3 Impacts on Services, Entities and Interfaces
Editor's note: This clause captures impacts on existing services, entities and interfaces.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 7 Interim agreements
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 7.1 Agreed Principles
| 7.1.Y Agreed Principles for KI#Y
Editor's note: This clause will include the principles that are agreed as work progresses for the specific KI#Y. This may be populated directly or e.g. also when a topic in clause 7.2.Y gets resolved and a principle is agreed.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 7.2 Topics for further consideration
| 7.2.Z Topics for further consideration for KI#Z
Editor's note: This clause will include the topics for further consideration as work progresses for the specific KI#Z. Eventually this clause should only contain topics for further consideration that did not result in agreements (i.e. in agreed principle(s) in a clause 7.1.Z) and can either be then marked as not pursued or postponed to a future release.
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 8 Conclusions
| Editor's note: This clause will capture conclusions for the study.
Where there is consensus, interim agreements (e.g. solution principles descriptions) should be documented in the TR as soon as possible during a study.
These can be documented in the TR as "7.1.Y Agreed Principles for KI#Y" in the "Interim Agreements" clause. If the interim agreement has impacts on another clause in the TR and if there is consensus, that TR clause can be updated.
By consensus interim agreements can become part of the final conclusions of the study.
The Overall Evaluation clause previously used in TR skeletons should not be used.
There should be a Topics for further consideration clause per Key Issue. It is recommended that this is used e.g. to capture common issues that need to be resolved for multiple solutions.
Annex A:
Change History
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08yyyy-mm
SA2#170
S2-2507417, S2-2507546, S2-2507547, S2-2507551, S2-2507610, S2-2507611, S2-2507612, S2-2507614, S2-2507615, S2-2507648, S2-2507655, S2-2507656
-
-
-
Baseline Doc, Scope, References, Architectural Assumptions Key issue 1, 2 &3, Solution 1, 2, 3, &4
0.1.00.0.0
yyyy-mm
|
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 4.2 Architectural Requirements
| |
de06d6f7b83561bec34bdae95ef8ccf9 | 23.700-56 | 6.4 Solution #4: IMS ADC establishment during alerting phase when initial INVITE does not have BDC offer
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 1 Scope
| The study item aims at investigating how to specify architectural and procedural enhancements to support Short Message Service to Emergency Response Centre in both EPS and 5GS for both roaming and non-roaming UEs, based on the requirements specified in TS 22.101 [6].
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 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.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2".
[4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System".
[5] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[6] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".
[7] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[8] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
[9] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[10] ATIS J-STD-110: "Joint ATIS/TIA Implementation Guideline for J-STD-110, Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification".
[11] GSMA NG.119: "Emergency Communication".
[12] 3GPP TS 23.221: "Architectural requirements".
[13] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[14] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[15] 3GPP TS 23.540: "5G System: Technical realization of Service Based Short Message Service; Stage 2".
[16] 3GPP TS 29.338: "Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)".
[17] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[18] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[19] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 3 Definitions of terms, symbols and abbreviations
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 3.1 Terms
| For the purposes of the present document, the terms given in 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 TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 4 Architectural Assumptions and Requirements
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 4.1 Architectural Assumptions
| Editor's note: This clause documents the common architecture assumptions identified for the study.
- The architectures for SMS over NAS (see TS 23.272 [7], TS 23.401 [5], TS 23.501 [2], TS 23.502 [3]) and SMS over IP (see TS 23.204 [8]) and the architectural principles of Emergency Services (see TS 23.167 [9]) will be used as a basis.
- SMS over IP can be applied for both 3GPP access and non-3GPP access (either over EPS or 5GS).
- The Short Message Service to Emergency Response Centre shall be supported also for roaming UEs, where roaming subscribers' SMS is routed to a local PSAP, according to the local regulations of the UE's location.
- For SMS over NAS over EPS, 3GPP access (including TN and NTN) is in scope.
- For SMS over NAS over 5GS, 3GPP access (including TN and NTN) and non-3GPP access are in scope.
- UEs in limited service state are not in scope of this document.
- Short Messages initiated by the Emergency Response Centre in response to a Short Message to the Emergency Response Centre sent from the UE are treated as regular Short Messages.
- Short Messages can be routed to different Emergency Response Centres, depending on the type of emergency service.
- The identification of the type of emergency service (police, ambulance, fire brigade, etc.) is based on the same mechanism used for emergency calls (see TS 23.167 [9]).
- This study builds upon requirements specified in clause 36 of TS 22.101 [6]. For SMS over IP emergency routing, existing IMS emergency services architecture in TS 23.167 [9] shall be leveraged.
- The payload structure of the SMS to Emergency Response Centre should be consistent across SMS over NAS and SMS over IP transport mechanisms to ensure uniform PSAP processing capabilities.
- Short Messages initiated by the Emergency Response Centre in response to the Short Message to the Emergency Response Centre are treated as regular Short Messages.
Editor's note: Whether the delivery of SMS to Emergency Response Centre shall be exclusively via an SMSC is FFS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 4.2 Architectural Requirements
| Editor's note: This clause defines the architectural requirements that serve as the foundation for the study.
Solutions shall be defined both for networks supporting IMS and networks not supporting IMS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5 Key Issues
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.1 Key Issue #1: Identification of SMS to Emergency Response Centre and Emergency Service Type
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.1.1 Description
| Based on the requirements in TS 22.101 [6], the EPS and 5GS shall have the capability to route a Short Message where the destination is an emergency number to a local Emergency Response Centre (i.e. a PSAP) according to the local regulation.
This key issue aims to study solutions to:
- identify whether an SMS should be routed to a PSAP;
- identify the type of emergency service (police, ambulance, fire brigade, etc.) required;
- address both the case of the UE detecting and the UE not detecting an SMS that is to be routed to Emergency Response Centre;
- consider the scenario where the serving PLMN does not support routing an SMS to an Emergency Response Centre.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.2 Key Issue #2: Support of SMS Delivery to Emergency Response Centre via NAS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.2.1 Description
| To support the SMS delivery to the Emergency Response Centre via NAS based on local regulations, following aspects are included:
- study how to route the SMS via NAS procedures for the support of SMS delivery to local Emergency Response Centre, e.g. UE location determination, via SMS service centre of the serving PLMN;
NOTE 1: Identification of SMS delivery to Emergency Response Centre is based on the conclusion of other KIs.
- how to support Emergency Response Centre callback for sending short messages using regular SMS delivery service.
The key issue covers SMS delivery via NAS both in EPS and 5GS.
NOTE 2: The solutions for EPS and 5GS are based on same principles.
The key issue covers both roaming and non-roaming scenarios.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.3 Key Issue #3: SMS over IP Routing to Appropriate PSAP
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 5.3.1 Description
| The following aspects are to be studied:
- how and when to trigger location determination and location data sharing when sending short messages using SMS over IP for routing to Emergency Response Centre, considering both 3GPP and non-3GPP access scenarios;
- how to route short messages using SMS over IP to Emergency Response Centre serving the UE's location, according to the local regulations (in roaming case, the regulations applicable to the UE's location);
- how to support PSAP callback capabilities for sending and routing regular short messages using SMS over IP.
The key issue covers SMS delivery via IP both in EPS and 5GS.
NOTE 1: The solutions for EPS and 5GS are based on same principles.
The key issue covers both roaming and non-roaming scenarios.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6 Solutions
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.0 Mapping of Solutions to Key Issues
| Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
1
2
3
1
X
2
X
3
X
4
X
X
5
X
X
6
X
X
7
X
X
8
X
9
X
10
X
11
X
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.1.2.2 Callback Handling
| When the PSAP replies, it sends the message back to the TP-OA (MSISDN).
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2 Solution #2: Capability and Identification of the SMS delivery to Emergency Response Centre
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.0 High level principles
| This solution aims to address KI#1 with the following key principles:
- The serving network provides indication of support for SMS delivery to Emergency Response Centre and the emergency number list to UE during UE registration/attach and IMS registration (in case of non-roaming), if SMS delivery to Emergency Response Centre is supported by the serving network based on local policy.
- The SMS delivery to serving network SMS service centre is routed by MME/SMSF and IMS/IP-SM-GW, based on the Relay layer RP-DA which include SMS service centre address/emergency call number, to the serving network SMS service centre.
- The SMS service centre is responsible to identify different type of emergency service based on the provided emergency number and route the SMS to corresponding Emergency Response Centre.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.1 Description
| This solution addresses KI#1 with the principles as described in clause 6.2.0.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.2 Procedures
| During the registration/attach and IMS registration procedure (in case of non-roaming), the AMF/MME/S-CSCF provides the indication of the supporting SMS delivery to Emergency Response Centre in the serving network and the emergency number list based on local policy.
For the SMS delivery to Emergency Response Centre, it's further described in solutions for KI#2/KI#3.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.2.1 Registration Procedures in 5GS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.2.2 IMS Registration procedure
| The following procedures are based on TS 23.204 [8] with addition below. This procedure is considered when UE is in non-roaming.
Figure 6.2.2.2-1: Based on TS 23.204 Figure 6.1: Registration procedure [8]
1) The UE establishes IP connection.
2) At any time after the establishment of the IP connection, the UE registers at the S-CSCF according to the IMS registration procedures. Based on local policy (e.g. the function is supported in IMS/IP-SM-GW), the S-CSCF also indicates the support of SMS over IP delivery to Emergency Response Centre by including e.g. “+g.3gpp.smsip-delivery to Emergency Response Centre” parameter in the Feature-Caps field header in 200 (OK) response. The “+g.3gpp.smsip-delivery to Emergency Response Centre” parameter indicates to UE whether the network allows the SMS over IP delivery to Emergency Response Centre.
NOTE 1: For simplicity, not all messages between UE and S-CSCF and between S-CSCF and HSS are shown in detail.
3) S-CSCF checks the initial filter criteria retrieved from the HSS during the IMS registration procedure.
4) After successful IMS registration and based on the retrieved initial filter criteria, the S-CSCF informs the IP-SM-GW (AS) about the registration of the user. IMSI is informed to the IP‑SM‑GW (AS) when there is no MSISDN in the UE's IMS subscription profile.
5) The IP-SM-GW (AS) returns OK to the S-CSCF.
6) The IP-SM-GW (AS) sends IP-SM-GW Register Req to the HSS.
7) The HSS stores the received IP-SM-GW address if necessary or for MT-SMS without MSISDN (see clause 6.0a.2), uses it as an indication that the UE is available to be accessed via the IMS to trigger an Alert service centre message if the message waiting flag is set, and responses to the IP-SM-GW (AS) with IP‑SM‑GW Register Res. IP‑SM‑GW gets the IMPU (SIP URI) for SMS delivery without TEL-URI from registration event package.
NOTE 2: IP-SM-GW Register Res can include the SC address to be used for this user in the subscriber data (see also clause 6.7).
NOTE 3: If the IP‑SM‑GW address stored in the HSS via registration procedure is not the same as the preconfigured IP‑SM‑GW address (if any), then the short message delivery attempted during registration can be unnecessarily delayed.
8) After successful registration of the IP‑SM‑GW address at the HSS the HSS checks whether message waiting data are stored and alerts all SCs using procedures described in TS 23.040 [13] (see also clause 6.5b).
Editor's note: roaming scenario is FFS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.2.3 Impacts to Services, Entities and Interfaces
| UE:
- Handling "SMS over NAS delivery to Emergency Response Centre allowed" indication and emergency number list in Registration/Attach Accept messages.
- Support the handling of SMS over IP delivery to Emergency Response Centre during IMS registration procedure, e.g. support of "+g.3gpp.smsip-delivery to Emergency Response Centre" field header handling.
AMF/MME:
- Support the indication and in Registration/Attach accept with "SMS over NAS delivery to Emergency Response Centre allowed" indication and emergency number list.
S-CSCF:
- Support the "+g.3gpp.smsip-delivery to Emergency Response Centre" field header handling during IMS registration procedure.
SMSF/MME/IP-SM-GW:
- Support of SMS delivery to SMS service centre of the serving PLMN based on identification of SMS service centre address/emergency number.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.3 Solution #3: Identification of SMS to EC
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.3.0 High level principles
| The following principles are applied to this solution:
- During initial attach/registration, a UE indicates support for SMS to EC and may be provided with local emergency numbers corresponding to different service types as specified in TS 23.167 [9] for emergency calls.
- The UE detects a MO SM to EC.
- If SMS to EC is supported by the network, the UE sends a SM with the destination corresponding to the emergency number.
- Additionally, the UE may send emergency-related information within the body text of the Short Message, within the size limit. This information, e.g. "police", "person injured at x location", may be treated once it reaches the visited SMSC.
- Upon reception of the Short Message, the network detects that it corresponds to an SMS to EC based on the used emergency number. It can then route the SM to the appropriate EC.
- This solution is applicable to both SMS over NAS and SMS over IMS, via EPS or 5GS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.3.1 Description
| The solution addresses KI#1 by enabling the UE and the network to be aware of the support of SMS to EC, the available emergency numbers and their related emergency service type.
The UE indicates its support of SMS to EC during initial attach/registration. If the network supports SMS to EC, it shall indicate it to the UE during MME/AMF attach/registration complete message. The attach/registration message may also contain a list of local emergency numbers and their corresponding emergency type, reusing the procedure for emergency calls as described in TS 23.167 [9].
Other emergency-related information may be relevant to the network or EC. For instance, accurate UE location information, but any other user-related information could be useful. Typically, the use of SMS instead of call may be motivated by the user not being able or willing to make an emergency call, be it due to accessibility issues or other circumstances. Thus, some information, within the limit of SM may be included. This can be used by the SMSC and forwarded to the EC.
From the network side, being able to provide SMS to EC and having registered with the UE, it will be able to identify a SM addressed to an EC and send it according to the used emergency number as well as other potential additional information in the body of the SM.
With all the previous steps achieved, the network can successfully identify a Short Message addressed to an Emergency Centre and forward it to the appropriate EC.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.3.2 Procedures
|
Figure 6.3.2-1: Detection of a Short Message to Emergency Centre
1a. The UE indicates its support of SMS to EC during initial attach/registration and the network acknowledges it.
1b. Depending on local PLMN emergency services and regulations, MME/AMF may provision the UE with local emergency numbers and service types according to TS 23.167 [9].
2. Upon detection of a MO SM to EC, the UE prepares the SM with the corresponding emergency number and emergency type and may include additional emergency-related information in the SM body.
3. The UE sends the emergency SM to the MME/AMF/IMS with the corresponding emergency number/type. Additional emergency-related information, e.g. UE location, may be included in the SM body. For SMS over NAS, early indication in the UL NAS type may be included to indicate that this is a SMS to EC.
4. The MME/AMF/IMS can detect the SMS to EC according to the used emergency number. Additionally, in case of a SM over NAS, UL NAS type may indicate SMS to EC.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.3.3 Impacts to Services, Entities and Interfaces
| UE:
- Indicates support for SMS to EC to the network.
- Addresses SM to EC with appropriate emergency number.
- In the case of SMS over NAS, includes an UL NAS type "SMS to EC".
MME/AMF:
- Reports support of SMS to EC during attach/register complete message.
- In the case of SMS to EC over NAS, detects SM to be sent to EC with UL NAS type.
MME/AMF/IMS:
- Detects SMS to EC based on emergency number and type.
SMSC:
- May inspect body of the SM for emergency-related information.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.4 Solution #4: SMS to PSAP over NAS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.4.0 High level principles
| The high-level principles of the proposed solution are as follows:
- The proposed solution focuses on SMS to Emergency Response Centre (SMS2EC) or PSAP over NAS.
- UE sends SMS2EC to the network via UL NAS TRANSPORT.
- There should be an emergency identifier included in the UL NAS TRANSPORT message content.
- The emergency identifier reuses the existing mechanism as emergency call.
- Whether to trigger Emergency Response Centre to callback via regular SMS delivery service depends on the UE support for regular SMS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.4.1 Description
| This solution addresses Key Issue#1 and Key Issue#2.
Currently the addresses of Emergency Response Centres/PSAPs vary in different areas even they belong to the same country. When UE triggers the request of SMS2EC service, it would be more flexible if the UE only needs to report certain emergency type identifier which is similar with the URN applied in emergency call. It is up to the network to reflect the received emergency type identifier to certain destination address of Emergency Response Centre/PSAP based on the local policy and deployment.
To assist the Emergency Response Centre/PSAP locate the UE more accurately, both the UE and the AMF may provide more UE location related information in the SMS2EC.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.4.2 Procedures
|
Figure 6.4.2-1: SMS to PSAP over NAS in 5GS
Editor's note: Procedure for EPS is FFS.
The steps of figure 6.4.2-1 are described as follows:
1. The UE performs initial registration for SMS over NAS and includes the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS supported", as described in clause 5.5.1.2.2 of TS 23.501 [2].
2. The UE triggers the request for SMS2EC over NAS with dedicated emergency type (e.g. sos.police, sos.ambulance, sos.fire, etc.). The UE encapsulates the NAS message with emergency type and UE location information included. The emergency type identifier is encapsulated in the Request Type IE of UL NAS TRANSPORT and UE location information may be encapsulated in the Payload container of UL NAS TRANSPORT.
3. The UE sends the NAS message to the AMF via UL NAS TRANSPORT.
4. The AMF identifies the UL NAS message as SMS2EC with the emergency type information in the NAS message IE.
5. The AMF forwards the SMS2EC to the SMSF by invoking Nsmsf_SMService_UplinkSMS service operation, including SUPI, SMS payload, emergency type identifier, UE location information and optionally UE location trends (e.g. from NWDAF) etc. The SMS payload may include the callback indication which could indicate the Emergency Response Centre whether to callback via regular SMS delivery service.
As it is an SMS2EC, the AMF may include the message priority indication in the request to SMSF.
6a. The SMSF determines the target address of the Emergency Response Centre/PSAP based on the emergency type identifier received from AMF and includes it in the SMS2EC destination address header.
6b-6c. The SMSF perform the reconstruction of SMS2EC. The SMSF may include the UE location information both from the UE and the AMF in the SMS2EC payload to assist the Emergency Response Centre/PSAP locate the UE more accurately.
In the case of excessive SMS2EC payload, the SMSF may need to manage the length the SMS payload within certain limit, or process the SMS2EC with Segmentation.
7. The SMSF sends the reconstructed SMS to the Emergency Response Centre/PSAP through SMSC. The Emergency Response Centre/PSAP may further send a callback regular SMS to the UE based on the callback indication included in the SMS payload.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.4.3 Impacts to Services, Entities and Interfaces
| Editor's note: Impacts on EPS entities is FFS.
UE:
- Encapsulates the NAS message with emergency type and UE location information included.
AMF:
- Identifies the SMS2EC over NAS by emergency type identifier.
- Determines the message priority of SMS2EC over NAS.
- Enhances the UE location information.
- Forwards the SMS2EC to SMSF with emergency type information.
SMSF:
- Stores the association between emergency type identifier and address of emergency response centre/PSAP.
- Identifies the SMS2EC by emergency type information.
- Includes the received UE location information in the message payload.
- Determines the address of emergency response centre/PSAP based on the emergency type information.
- Sends the message to the related Emergency Response Centre/PSAP.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5 Solution #5: Support of Short Message to Emergency Response Centre via SMS over NAS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.0 High level principles
| This solution aims to resolve Key Issue #1 & #2, i.e. "Support of Short Message to Emergency Response Centre via SMS over NAS". The solution principles shall follow the architectural assumptions described in clause 4.
To address the issue described in WT-1, the following solutions are proposed:
- UE sends a new indication during the Attach/Registration procedure with EPS/5GS, whether the UE supports emergency SMS over NAS and/or emergency SMS over IP.
- When the serving network receives the above indication from the UE, the serving network sends an indication in response to Attach/Registration procedure whether the serving PLMN supports emergency SMS over IP and/or emergency SMS over NAS.
- A UE receiving an indication that emergency SMS over NAS is supported in a serving PLMN but failed to send the SMS over NAS attempts emergency SMS over IP if configured in the UE, unless emergency SMS over NAS is supported over Non-3GPP access. In this case, the UE attempts to send the emergency SMS over NAS via Non-3GPP access first, prior to using emergency SMS over IP.
- If both emergency SMS over NAS and emergency SMS over IP are not supported in the serving network, it is up to the UE implementation how to proceed. The UE can, for example, try to choose another network to send the emergency SMS over IP or SMS over NAS (e.g. the UE can choose another network at the time when it detects that an SMS to EC needs to be sent). The UE can also try to establish an emergency call or indicate to the user that emergency SMS over IP or SMS over NAS is not possible.
To address the issue described in KI#-1, the following solutions are proposed:
- The UE uses the same mechanisms (local configuration and handling of emergency Number/emergency service and sub-service type received over NAS during attach/registration procedure).
The UE detects emergency SMS over IP and/or SMS over NAS based on used emergency numbers. Provisioning of emergency numbers and associated types or URN information as specified in clause 4.1 bullets 2a, 2b) and 2c) in TS 23.167 [9] applies.
To address the issue described in KI#1-1, the following solutions are proposed:
- When UE detects the sos emergency number and it does not have emergency registration for SMS, then UE shall complete emergency registration for SMS. During UE registration, when UE sends a registration request to the 5GC, the SMSF sends back the indication to the UE about emergency SMS service availability feature in the serving PLMN to the AMF and then AMF forwards the same indication (i.e. emergency SMS over NAS and SMS over IMS are allowed) to the UE in the registration accept.
- In the case of SMS over NAS in EPS during combined attach, the MSC/VLR can inform the MME on the support of emergency SMS routing or based on MME's local configuration (e.g. SGd interface case). The MME informs the UE about the emergency SMS routing in the serving PLMN.
- Any SMS sent back by the PSAP to the UE is handled as a regular SMS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.1 Description
| This solution addresses Key Issue #1 & #2.
- The SMSF, if configured with local emergency support, sends the EM availability indication during the registration procedure. AMF informs the UE about the EM SMS feature.
- UE needs to do access control for a new upper layer event (e.g. EM SMS) to trigger a service request with the indication of emergency SMS.
- The AMF informs the SMSF that the SMS payload is for an emergency. The AMF also prioritises the NAS procedure based on the emergency indication.
- The SMSF do not need to use subscription data for emergency SMS cases and routes the SMS to local SMSC/PSAP. The SMSF can replace the RP-DA with a local SMSC address. It may also set a higher transport priority (e.g. the DRMP).
Editor's note: The security implication if any due to RP-DA replacement is to be studied in SA WG3.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.2 Procedures
| During EPS/5GS registration, the UE indicates its capability to support SMS over NAS and/or SMS over IP. The serving network also indicates its capability to support these services in the registration response.
If the serving network has provided the above-mentioned SMS over NAS indication, then UE invokes the following procedures to send a Short Message to an Emergency Response Centre.
- Route a Short Message to the Emergency Response Centre via SMS over NAS via 5GS.
- Route a Short Message to the Emergency Response Centre via SMS over NAS via EPS (via MSC/VLR).
- Route a Short Message to the Emergency Response Centre via SMS over NAS via EPS (via SGd interface).
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.2.1 Short Message routing to the Emergency Response Centre via SMS over NAS via 5GS
|
Figure 6.5.2.1-1: Short Message to Emergency Response Centre via SMS over NAS via 5GS
0. UE registration to the 5GS follows clause 4.13.3.1 of TS 23.502 [3] with the additional indication as described in clause 6.5.2. This additional indication can be sent by AMF.
1. If the UE is in the CM-IDLE state, then the UE follows the same procedure defined in clause 4.13.3.3 of TS 23.502 [3]. UE indicates the emergency cause indicator in the service request.
2. If the UE is in the CM-CONNECTED state, it follows the same procedure defined in clause 4.13.3.3 of TS 23.502 [3] and it sends an uplink SMS message then, the UE needs to do access control for a new upper layer event (EM SMS in the SMS body of the NAS payload) to trigger a service request. The UE trying to send SMS to EC uses a different payload type in UL NAS transport.
3. The AMF forwards this message to the SMSF. The AMF provides the UE location and informs the SMSF that the SMS payload is for EM.
4. The SMSF does not lookup subscription data and routes the SMS to the local SMSC/PSAP. The SMSF can replace the RP-DA with a local SMSC address, if it is not sending the SMS payload directly to PSAP. It may also set a higher transport priority (e.g. the DRMP).
5. If in step 2 the UE includes a short message service centre address in the RP-DA instead of the NAS payload type as "EM SMS", then the SMSF routes to the serving PLMN SMSC.
The SMSC/PSAP forwards the SMS /Submit report to the SMSF.
6. The SMSF forwards to the AMF.
7. The AMF forwards the SMS submit report to the UE.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.2.2 Short Message routing to the Emergency Response Centre via SMS over NAS via EPS (via MSC/VLR)
|
Figure 6.5.2.2-1: Short Message to Emergency Response Centre via SMS over NAS via EPS (via MSC/VLR)
0. The attach procedure follows the procedure as specified in clause 5.2 of TS 23.272 [7] with the additional indication in the Attach Request/Response as described in clause 6.5.2. This indication can be sent by either MME or MSC/VLR.
1. The UE in idle-Mode or active-Mode follows the same procedure as defined in 8.2.2 of TS 23.272 [7] with additionally sending Emergency SMS as a different payload type in UL NAS transport.
2. The MME includes the location information (cell ID, tracking area, location area) and the payload type is EM SMS and forwards to the MSC/VLR in an Uplink Unidata message.
3. For roaming UEs, the MME does not send the EM SMS payload to the H-PLMN MSC/VLR; instead, it sends it to the local SMS-IWMSC.
4. If in step 3 the MME includes the short message service centre address in the RP-DA instead of the NAS payload type as "EM SMS", then the MSC/VLR routes it to the serving PLMN SMSC.
5. Alternatively, the MME can send the serving PLMN support of EM SMS based on local configuration without depending on the MSC/VLR. The MME forwards the EM SMS to the local SMSC for a roaming subscriber.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.2.3 Route a Short Message to Emergency Response Centre via SMS over NAS via EPS (via SGd interface)
|
Figure 6.5.2.3-1: Short Message to Emergency Response Centre via SMS over NAS via EPS (via SGd interface)
0. The attach procedure follows the procedure as specified in clause 5.3.2.1 of TS 23.401 [5] with the additional indication in the Attach Request/Response as described in clause 6.5.2. This indication can be sent by MME.
1. The UE in idle-mode or active-mode follows the same procedure as defined in clause 5.3.4.1 of TS 23.401 [5] with additionally sending Emergency SMS as a different payload type in UL NAS transport.
2. The MME mandatorily includes the location info (cell ID, tracking area, location area) and the payload type is EM SMS, towards the SMSC.
3. If in step 2 the UE includes the short message service centre address in the RP-DA instead of the NAS payload type as "EM SMS", then the SMSF routes to the serving PLMN SMSC.
4. For roaming UEs, the MME does not send the Emergency SMS payload to the H-PLMN SMSC but rather sends it to a local SMSC.
5. The local SMSC identifies the EM service type and forwards it to the appropriate SMS-IWMSC/PSAP.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.5.3 Impacts to Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- Need to support network feature indication from EPS and 5G core on the availability of Emergency Messaging.
AMF:
- Need to support a new NAS payload type for SMS meant for EC.
- Need to support feature indication to indicate serving PLMN's support for SMS routing to EC.
MME:
- Need to support a new NAS payload type for SMS meant for EC.
- Need to support feature indication to indicate serving PLMN's support SMS routing to EC.
SMSF:
- Replacement of RP-DA.
- Need to route to local SMSC for EM SMS.
MSC/VLR:
- Need to support SMS routing to EC.
- SMS to EC support indication to UE.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6 Solution #6: Support of Short Message Service Routing to Emergency Response Centre via NAS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.0 High level principles
| This solution addresses KI#1 and KI#2.
The principles of this solution are listed below:
- The UE detects Short Message Service to Emergency Centre (SMS2EC) based on the used emergency number.
- If the UE detects that the destination number of an Short Message is an valid emergency number, UE includes the emergency number, associated emergency service type and UE's location in the SMS-SUBMIT TPDU. If the local SMSC address in the serving PLMN is available, the RP-DA is set to the local SMSC address.
- If the SMSF/MSC determines that the destination number is an emergency number and the RP-DA is not a local SMSC address in the serving PLMN (in the event the UE did not detect SMS2EC), the SMSF/MSC replaces the RP-DA with local SMSC address. SMSF/MSC may also obtain the UE's location from AMF/MME or GMLC/E-SMLC and provide it to the SMSC.
- Based on the emergency number, associated emergency service type and the UE's location, SMSC delivers the SMS2EC to the local emergency response centre (i.e., PSAP).
- The emergency number, local SMSC address and associated emergency service type are provided to the UE via mobility management procedures in EPS and 5GS.
- If the Emergency Response Centre (i.e. PSAP) needs to respond to the UE, the PSAP sends the reply message to the SMSC in PSAP's HPLMN. SMSC treats the reply message as regular MT SMS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.1 Description
| In order to support routing of Short Message to the Emergency Centre, the network provides the emergency numbers, local SMSC address and associated emergency service types to the UE during the Attach, TAU, Initial registration and Mobility registration update procedure. Additionally, the network signals an indicator indicating its capability to support routing of SMS2EC to the UE through mobility management procedures in both EPS and 5GS. The MO Short Message consists of CP-DATA/RP-DATA/TPDU/SMS-SUBMIT parts as defined in TS 23.040 [13].
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.1.1 UE detecting Short Message Service to Emergency Centre
| The following figure depicts how a Short Message is routed to the local PSAP in case of UE detecting SMS2EC.
Figure 6.6.2.1-1: MO SMS routed to the local PSAP in case of UE detecting SMS2EC
If UE detects that the destination number is an emergency number, the UE replaces the RP-DA with local SMSC address (e.g. a local SMSC number) and hence the Short Message can be delivered to a local SMSC. In addition, the UE also includes the emergency number and associated emergency service type and UE's location (e.g. Latitude and longitude, etc.) in the TPDU part of the SMS2EC. The local SMSC forwards the received Short Message to the corresponding PSAP, considering the emergency number and associated emergency service type extracted from the SMS-SUBMIT TPDU.
An example of RP-DATA included in 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.
Editor's note: How to support SMS2EC in the scenario where the UE is not provided with a local SMSC address is FFS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.1.2 UE not detecting Short Message Service to Emergency Centre
| The following figure depicts how a Short Message is routed to the local PSAP in case of UE not detecting SMS2EC.
Figure 6.6.2.2-2: MO SMS routed to the local PSAP in case of UE not detecting SMS2EC
For the non-UE detectable emergency number, UE treats the SMS2EC as a regular Short Message. Upon determining that the destination number is an emergency number and the RP-DA is not a local SMSC address in the serving PLMN (which suggests the UE did not detect an emergency), the SMSF substitutes the RP-DA with the local SMSC address. Besides, the SMSF may also provide the UE's location to the SMSC. The UE's location can be the ULI provided by AMF, or the precise location information acquired from GMLC. The emergency number and associated emergency service type is configured in SMSC, so that the SMSC can figure out the emergency service type using emergency number. Based on the emergency number, emergency service type and UE's location, SMSC forwards the Short Message to the corresponding PSAP.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.2 Procedures
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.2.1 MO SMS over NAS in EPS
| The following figure depicts the mobile originating procedure for SMS2EC in EPS.
Figure 6.6.2.1-1: MO SMS over NAS in EPS
0-1: If a UE that supports SMS2EC under CM-IDLE state is sending a Short Message, then UE and network perform the UE Triggered Service Request procedure firstly to establish a NAS signalling connection to MME. If the UE is under CM-CONNECTED state, steps 0-1 are skipped.
2a: UE builds a Short Message to be sent as defined in TS 23.040 [13] (i.e., the Short Message consists of CP-DATA/RP-DATA/TPDU/SMS-SUBMIT parts).
Scenario 1: UE detecting SMS2EC.
If the UE detects the used number is an emergency number, the UE includes the local SMSC address in the RP-DA and also includes the emergency number, associated emergency service type, UE's location in the SMS-SUBMIT TPDU. UE can obtain the local SMSC address (i.e., local SMSC number) during Attach or TAU procedures.
The type of emergency service for an emergency number is derived from the emergency service category value as specified in clause 10.5.4.33 of TS 24.008 [19]). The emergency service value is included in the TP-DA together with the emergency number. For example, to call the police, the TP-DA can be set to 1121, where 112 is the emergency number and 1 is the code for police.
The UE's location (e.g., latitude and longitude) can be included in an existing TPDU parameter (e.g., TP-User-Data-Header) or a new parameter.
The SMS2EC is encapsulated in an NAS message and sent to MME.
Scenario 2: UE not detecting SMS2EC.
Editor's note: How to support SMS2EC in EPS in scenarios where the UE cannot detect SMS2EC is FFS.
2b: MME sends the Short Message to MSC.
2c: MSC acknowledges receipt of the Short Message to MME.
2d: The MME forwards the SMS ack message from the MSC to the UE using downlink unit data message.
3-4: MSC forwards the Short Message to SMS-IWMSC. SMS-IWMSC establishes the connection to the SMSC and transfers the Short Message to SMSC.
Scenario 1: UE detecting SMS2EC.
MSC forwards the Short Message to the local SMSC based on the RP-DA. Based on the emergency number, emergency service type and UE's location obtained from the SMS TPDU, SMSC forwards the Short Message to the corresponding PSAP.
5: SMSC returns a Submit Report for the receipt of the Short Message to MSC.
6: MSC sends the Submit Report to MME. MME encapsulates the Submit Report in DL NAS message and send it to the UE. UE acknowledges receipt of the Submit Report to MME.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.2.2 MO SMS over NAS in 5GS
| The following figure depicts the mobile originating procedure for SMS2EC in 5GS.
Figure 6.6.2.2-1: MO SMS over NAS in 5GS
0-1: If a UE that supports SMS2EC under CM-IDLE state is sending a Short Message, then UE and network perform the UE Triggered Service Request procedure firstly to establish a NAS signalling connection to AMF. If the UE is under CM-CONNECTED state, steps 0-1 are skipped.
2a: UE builds a Short Message to be sent as defined in TS 23.040 [13] (i.e., the Short Message consists of CP-DATA/RP-DATA/TPDU/SMS-SUBMIT parts).
Scenario 1: UE detecting SMS2EC.
If the UE detects the used number is an emergency number, the UE includes the local SMSC address in the RP-DA and also includes the emergency number, associated emergency service type and UE's location in the SMS-SUBMIT TPDU. UE can obtain the local SMSC address (i.e., local SMSC number) during registration procedures.
The type of emergency service for an emergency number is derived from the emergency service category value as specified in clause 10.5.4.33 of TS 24.008 [19]). The emergency service value is included in the TP-DA together with the emergency number. For example, to call the police, the TP-DA can be set to 1121, where 112 is the emergency number and 1 is the code for police.
The UE's location (e.g., latitude and longitude) can be included in an existing TPDU parameter (e.g., TP-User-Data-Header) or a new parameter.
The SMS2EC is encapsulated in an NAS message and sent to AMF.
Scenario 2: UE not detecting SMS2EC.
If the UE cannot detect the used number is an emergency number, the SMS2EC is treated as a regular SMS by the UE, i.e., the UE includes the home SMSC address in the RP-DA and also includes the emergency number in the SMS-SUBMIT TPDU.
2b: AMF sends the Short Message to SMSF. For roaming scenario, the AMF discovers and selects an SMSF in VPLMN.
2c: SMSF acknowledges receipt of the Short Message to AMF.
2d: The AMF forwards the SMS ack message from the SMSF to the UE using downlink unit data message.
3-4: SMSF forwards the Short Message to SMS-IWMSC. SMS-IWMSC establishes the connection to the SMSC and transfers the Short Message to SMSC.
Scenario 1: UE detecting the Short Message.
SMSF forwards the Short Message to the local SMSC based on the RP-DA. Based on the emergency number, associated emergency service type and UE's location obtained from the SMS TPDU, SMSC forwards the Short Message to the corresponding PSAP.
Scenario 2: UE not detecting SMS2EC.
The SMSF checks the SMS management subscription data. Upon determining that the destination number is an emergency number, if the RP-DA is not a local SMSC address in serving PLMN (which suggests the UE did not detect an emergency), the SMSF substitutes the RP-DA with the local SMSC address in serving PLMN. The local SMSC address can be preconfigured in SMSF. Besides, the SMSF may also obtain the UE's location from AMF or GMLC and provide it to the SMSC. The emergency number and associated emergency service type is configured in SMSC, so that the SMSC can figure out the emergency service type using emergency number. Based on the emergency service type and UE's location, SMSC forwards the Short Message to the corresponding PSAP.
5: SMSC returns a Submit Report for the receipt of the Short Message to SMSF.
6: SMSF sends the Submit Report to AMF. AMF encapsulates the Submit Report in DL NAS message and send it to the UE. UE acknowledges receipt of the Submit Report to AMF.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.2.3 Emergency Response Centre Callback
| If the Emergency Response Centre (i.e. PSAP) needs to respond to the UE, the PSAP sends the reply message to the SMSC in PSAP's HPLMN. SMSC treats the reply message as regular MT SMS and the procedures for delivering MT SMS to the UE are described in clause 4.13.3 of TS 23.502 [3] and clause 8.2 of TS 23.272 [7].
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.6.3 Impacts to Services, Entities and Interfaces
| UE:
- Support to include SMSC address in the serving PLMN in RP-DA field and also include emergency number, associated emergency service type and UE's location in the SMS-SUBMIT TPDU part of the Short Message Service to Emergency Centre.
SMSF:
- Support to replace RP-DA with local SMSC address in the serving PLMN, upon determining that the destination number is an emergency number and the RP-DA is not a local SMSC address.
- Support to obtain UE's location from GMLC/E-SMLC via Location services and provide it to SMS-SC.
AMF/MME:
- Providing emergency numbers, associated emergency service types, local SMSC address in the serving PLMN to the UE.
- Support to indicate to the UE whether network supports routing of SMS to emergency centre.
- Support to select an SMSF/MSC that is enabled to support SMS2EC.
SMS-SC:
- Support to deliver the Short Message to the PSAP based on the emergency number, associated emergency service type and UE's location.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7 Solution #7: Enabling SMS over NAS for conditional local routing to Emergency Response Centre
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7.0 High level principles
| This solution addresses KI#1 and KI#2 by enhancing short messages delivery using SMS over NAS and routing to local emergency response center (i.e. PSAP). This solution is proposed with the following principles:
- P1. Emergency Authentication Trigger: During Emergency Registration, the UE shall include a new authentication indication IE or set the new SMS Authentication Required bit in the 5GS update type IE. This explicit indication mandates the AMF/MME to perform immediate primary authentication to establish the necessary NAS security context for secure 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 Visted AMF as a conditional override to the default roaming policy.
- P3. Emergency Number Provisioning: 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. This is based on existing mechanism.
- P4. Explicit Routing Trigger: The UE shall use a specific indicator in the Uplink NAS Transport message to explicitly signal to the AMF that the embedded SMS is for routing to a PSAP and requires the conditional LBO route.
- P5. Home Routed Fallback for routing efficiency: 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 (AMF/SMSF) shall maintain the integrity of the SMS-TPDU payload during transit.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7.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 includes a new authentication indication IE or sets the SMS requested bit in the 5GS update type IE in the Registration Request message, the AMF/MME shall initiate primary authentication to ensure the creation of the NAS security context required for secure SMS over NAS transfer.
NOTE 1: The UE is not in limited state.
Editor's note: It is FFS whether and how the emergency registration procedure is used for UE not in limited state.
2. Conditional LBO Capability Negotiation:
- The UE network capability IE in the Registration Request message is extended to include a new SMS for LBO Support indication, to indicate the UE's capability and preference for MO SMS delivery using conditional LBO for routing to local PSAP.
- The Registration Accept message is extended to include a new optional IE, e.g. SMS for LBO Allowed indication, if the Visited AMF is configured to support this service for the roaming user.
3. Local PSAP Discovery:
- The Registration Accept message is enhanced to include the Emergency Number List IE to provide the local emergency numbers and emergency service types to the UE.
4. LBO Message Signalling:
- If the UE receives SMS for LBO Allowed indication during registration procedure and detects the emergency number for MO SMS, the UE indicates to the network using MO SMS over NAS delivery for LBO routing to local PSAP.
- In the Uplink NAS Transport message, a new value is defined for the Payload container type IE or a new emergency indication to explicitly signal to the AMF that the embedded SMS TPDU is destined for a PSAP and requires Local Breakout routing. The UE is also responsible for including current location information (e.g., Additional Mobile Location - AML) within the SMS-TPDU payload.
- The V-SMSC or the VPLMN's location function needs to validate or update the location data based on available network-based positioning data to ensure the most accurate location is provided to the local PSAP.
5. Home Routed Fallback Enhancements:
- Home Routed Fallback Enhancement: if Conditional LBO is not supported by the VPLMN, the AMF can optionally provide the visited SMSC Address to the UE in the Registration Accept message for use during Home Routed fallback.
- TPDU Integrity: All core network functions (AMF/SMSF/Home SMSC) shall maintain the integrity of the SMS-TPDU payload (TP-DA, TP-UD, etc.) during transit.
- The SMS-TPDU is enhanced with in a new dedicated routing field to carry the visited SMSC Address when provided by the UE in the Home Routed fallback scenario.
6. The principle of the MO SMS delivery using SMS over NAS include:
- UE Role: The UE builds the full message stack: SMS-SUBMIT TPDU (Telephony Protocol Data Unit) wrapped inside an RP-DATA PDU (Relay Protocol Data Unit). This entire package is the SMS-RPDU.
- NAS Transport: The UE places this SMS-RPDU inside the Payload Container of the Uplink NAS Transport message.
- AMF Role: The AMF extracts the payload. When the AMF interacts with the SMSF (Visited SMS Function) using the 5GC service operation, it forwards the core SMS-RPDA message. While the AMF doesn't necessarily transmit the SMS-RPDU directly to the SMSF (it uses the Nsmsf service), the AMF's job is to extract and handle the SMS-RPDU payload it received from the UE.
NOTE 2: The above principles are applied for EPS and 5GS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7.2 Procedures
| Editor's note: It is FFS how the same principles are applied for EPS and 5GS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7.2.1 MO SMS over NAS in 5GS
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.7.3 Impacts to Services, Entities and Interfaces
| Editor's note: The impacts for EPS is FFS.
UE:
- Negotiate the new UE capability using SMS for LBO Support indication for Conditional LBO Support for SMS routing to local PSAP for normal registration procedure.
- Indicate a new Authentication 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) for emergency registration procedure.
- Store the optional visited SMSC Address IE if received from the AMF and include the stored visited SMSC address in a new routing field within the TPDU during Home Routed Fallback.
- Use the new explicit emergency indication for MO SMS delivery and routing to local PSAP when LBO is allowed.
AMF/MME:
- Handle the network support and new UE capability indication for SMS for LBO negotiation.
- Trigger primary authentication to establish NAS security context during Emergency Registration when SMS is requested.
- Optionally provide visited SMSC Address to the UE in the Registration Accept.
- Use SMS for LBO Allowance status and Payload container type or emergency indication to determine SMS routing path for MO SMS delivery using LBO vs. Home routed.
SMSF/MSC (VPLMN):
- Manage the lifecycle of the Local Routing Context using a dedicated timer and delete it upon expiry and successful MT Callback delivery.
- Support interworking with a V-SMSC supporting routing to local PSAP.
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.
- Need to support roaming interface to forward SMS to visited SMSC.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8 Solution #8: SMS over NAS delivery to Emergency Response Centre based on emergency call numbers
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.0 High level principles
| This solution aims to address KI#2 with the following key principles (considering the solutions for KI#1):
- The UE uses emergency call numbers/serving PLMN SM service centre address as RP-DA-destination.
- The SMSF/MME is responsible to deliver the SMS to the SM service centre based on the identification of the emergency number/serving PLMN SM service centre address.
- The serving SMS service centre is responsible to forward the SMS to the local Emergency Response Centre.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.1 Description
| In this proposal, 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 NAS delivery to Emergency Response Centre is supported by the network during the UE Registration/Attach procedure).
The main change is SMSF/MME deliver the SMS to the SMS service centre based on the RP-DA field.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.2 Procedures
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.2.1 MO SMS over NAS delivery procedures
| |
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.2.1.1 MO SMS over NAS in CM-IDLE in 5GS
| The following procedures are based on clause 4.13.3 of TS 23.502 [3] with the following additions (in bold underline).
Figure 6.8.2.1.1-1: Based on TS 23.502 [3], Figure 4.13.3.3-1: MO SMS over NAS
1. The UE performs domain selection for UE originating SMS as defined in clause 5.16.3.8 of TS 23.501 [2] if SMS delivery via non 3GPP access is allowed and possible. If an UE under CM-IDLE state is going to send uplink SMS message, then UE and network perform the UE Triggered Service Request procedure firstly as defined in clause 4.2.3.2 to establish a NAS signalling connection to AMF.
2a. The UE builds the SMS message to be sent as defined in TS 23.040 [13] (i.e. the SMS message consists of CP-DATA/RP-DATA/TPDU/SMS-SUBMIT parts). The SMS message is encapsulated in an NAS message with an indication indicating that the NAS message is for SMS transporting. The UE send the NAS message to the AMF. When UE builds the SMS message to be sent to Emergency Response Centre, the RP-DA field includes the SMS service centre address/the emergency service number provided by the AMF when AMF sets the "SMS over NAS delivery to Emergency Response Centre allowed" indication during UE registration procedure.
2b. The AMF forwards the SMS message and SUPI to the SMSF serving the UE over N20 message by invoking Nsmsf_SMService_UplinkSMS service operation. In order to permit the SMSF to create an accurate charging record, the AMF adds the IMEISV, the current UE Location Information (ULI) of the UE as defined in clause 5.6.2 of TS 23.501 [2] and if the UE has sent the SMS via 3GPP access, the local time zone.
When the AMF determines that the UE has the MPS for Messaging indication set (enabled) in the UE context, the AMF includes a Message Priority header to indicate priority information. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500 [14].
2c. The SMSF invokes Namf_Communication_N1N2MessageTransfer service operation to forward SMS ack message to AMF.
2d. The AMF forwards the SMS ack message from the SMSF to the UE using downlink unit data message.
3-5. The SMSF checks the SMS management subscription data. If SMS delivery is allowed, the procedure defined in TS 23.040 [13] or in TS 23.540 [15] applies. If the Message Priority header received in step 2 contains a value that indicates MPS, the SMSF may set the transport priority (e.g. the DRMP) to a value appropriate for MPS. If the RP-DA includes the serving SMS service centre address/emergency service number, the SMSF delivers the SMS to the SMS service centre of the serving PLMN. The SMS service centre delivers the SMS to corresponding Emergency Response Centre based on emergency numbers.
6a-6b. The SMSF forwards the submit report to AMF by invoking Namf_Communication_N1N2MessageTransfer service operation which is forwarded to UE via Downlink NAS transport. If the SMSF knows the submit report is the last message to be transferred for UE, the SMSF shall include a last message indication in the Namf_Communication_N1N2MessageTransfer service operation so that the AMF knows no more SMS data is to be forwarded to UE.
NOTE: The behaviour of AMF based on the "last message indication" is implementation specific.
If the UE has more than one SMS message to send, the AMF and SMSF forwards SMS /SMS ack/submit report the same way as described in step 2a-6b.
6c-6d. When no more SMS is to be sent, UE returns a CP-ack as defined in TS 23.040 [13] to SMSF. The AMF forwards the SMS ack message by invoking Nsmsf_SMService_UplinkSMS service operation to SMSF.
Editor's note: Undetectable SMS delivery to Emergency Response Centre is FFS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.2.2 MO SMS over NAS delivery procedures in EPS
| The SMS over NAS delivery to Emergency Response Centre is similar to 5GS procedure with the change that the MME takes to role of AMF/SMSF.
Editor's note: SGs interface based on SMS delivery is FFS.
|
2b4a92fb259f5b8c209f1c52ea2cc338 | 23.700-65 | 6.8.3 Impacts to Services, Entities and Interfaces
| UE:
- Support the capability of SMS over NAS delivery to Emergency Response Centre during registration procedure, e.g., accept "SMS over NAS delivery to Emergency Response Centre allowed/supported" indication in Registration Accept.
- Formulates the RP-DA in the RP-DATA with serving PLMN SMS service centre or emergency number provided by the AMF.
AMF/MME:
- Support the capability of SMS over NAS delivery to Emergency Response Centre during registration procedure, e.g., accept "SMS over NAS delivery to Emergency Response Centre allowed/supported" indication in Registration Accept.
SMSF/MME:
- Support of SMS delivery to SMS service centre of the serving PLMN based on the identification of the SMS service centre address/emergency number.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.