hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.8.2 Actions at UE of user B | If the user B accepts the waiting communication and holds the active communication (as per procedures in 3GPP TS 24.615 [17]), the hold invoking UE of the user B shall perform the hold procedure. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.9 Advice Of Charge (AOC) | The Advice Of Charge (AOC) service specified in 3GPP TS 24.647 [22] shall allow the served user to be informed of IP Multimedia session related charging information even if the session is accompanying with data channel media.
According to 3GPP TS 32.260 [20] and 3GPP TS 32.255 [21], duration-based charging and volume-based charging are used for IMS data channel, which does not introduce specific requirements on charging information element specified in Annex C of 3GPP TS 24.647 [22]. So, AOC service has no interaction with IMS data channel. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.10 Flexible Alerting (FA) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.10.1 Actions at the AS serving the pilot identity | The flexible alerting telecommunication service with IMS data channel, procedures for the IMS AS serving user B identified by the FA pilot identity, shall be in accordance with 3GPP TS 24.239 [23] with the additions defined in the present document.
Upon reception of an incoming SIP INVITE request with DC media destined to the FA pilot identity of the user B, served by the IMS AS, the IMS AS:
- shall not trigger the IMS data channel resource reservation; and
- shall execute the FA procedures and route the incoming SIP INVITE request with DC media along with other MMTel media towards the FA group member identities, by sending the SIP INVITE request to S-CSCF in accordance with clause 4.5.5.2 3GPP TS 24.239 [23].
NOTE: The data channel media negotiation will be performed between the originating user and the FA group member together with audio, video media negotiation as per procedures defined in clause 9.3. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.11 Multi-Device (MuD) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.11.1 Actions at the AS serving user B | The multi-device service with IMS data channel, procedures for the IMS AS serving the user B having federated UEs, shall be in accordance with 3GPP TS 24.174 [24] with the additions defined in the present document.
On reception of a SIP initial INVITE request with an SDP offer containing IMS data channel media descriptions, the IMS AS of the user B, shall execute multi-device service procedure, which branch the call into several call legs to alert the federated UEs of the user B. The IMS AS shall determine whether the served user B is authorized to use IMS data channel. If the served user is authorized to use IMS data channel, then for each federated UE of the user B the IMS AS shall determine if the federated UE supports IMS data channel capabilities. For each created call leg towards the federated UE:
1) if the served user B is authorized to use IMS data channel and if the federated UE supports IMS data channel capabilities, the IMS AS shall follow procedure specified in clause 9.3.3.2.1, bullet 1); and
2) if the served user B is authorized to use IMS data channel but the federated UE does not support IMS data channel capabilities or if the served user B is not authorized to use IMS data channel, the IMS AS shall follow procedure specified in clause 9.3.3.2.1, bullet 2). |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.11.2 Call pull, actions at the AS serving user A | On reception of an INVITE request from the UE of the user A who has triggered the call pull request, to establish new partial dialog with the IMS AS of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.3:
1) the IMS AS shall update existing partial dialog towards the remote network in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.3 and 3GPP TS 24.229 [9], containing media descriptions to close established data channels associated with the UE of the user A whose call is getting pulled; and
2) after the successful session acknowledgement between the UE of the user A who has triggered the call pull request and the remote network, the IMS AS shall notify the DCSF about the session release event for the call leg towards the UE of the user A whose call is getting pulled and the established data channels associated with the UE of the user A whose call is getting pulled are closed as part of a partial dialog termination in accordance with clause 9.3.2.1.5. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.11.3 Call push, actions at the AS serving user A | On reception of a SIP REFER request for call push request from the UE of the user A involved in ongoing call:
1) the IMS AS shall establish new partial dialog with the target UE of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.4 and 3GPP TS 24.628 [28] clause 4.4.a;
2) the IMS AS shall update existing partial dialog towards the remote network in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.4 and 3GPP TS 24.229 [9], containing media descriptions to close established data channels associated with the UE of the user A who has triggered the call push request in accordance with clause 9.3.3.1.4 of this specification; and
3) after a successful session acknowledgement between the target UE of the user A and the remote network, the IMS AS shall notify the DCSF about the session release event for the call leg towards the UE of the user A who has initiated the call push request and the established data channels associated with the UE of the user A who has initiated the call push request are closed as part of a partial dialog termination in accordance with clause 9.3.2.1.5. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.12 Multi-iDentity (MiD) | No interaction with IMS data channel. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.13 Completion of Communications to Busy Subscriber (CCBS), Completion of Communications by No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.13.1 General | The CCBS, CCNR and CCNL services enable a user, encountering a destination that is busy, does not answer or is not logged-in, to have the communication completed at a later point in time without the user having to manually initiate a new communication attempt, which is defined in 3GPP TS 24.642 [25]. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.13.2 Action at the UE | When the UE initiates the initial IMS session before the CC services activation, the IMS data channel media description can be included in the INVITE along with other MMTel medias. The procedure defined in clause 9.3.2.1.2 applies.
On reception of the 486 (Busy Here) in case of CCBS or the 480 (Temporarily Unavailable) in case of CCNL or on sending the 487 (Request Terminated) in case of CCNR, the UE shall terminate the existing call session as specified in 3GPP TS 24.642 [25] including data channel media.
When the CC call is initiated, the IMS data channel media description can be included in initial INVITE message along with other MMTel medias. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.13.3 Action at the IMS AS serving the originating UE | Upon reception of the incoming sessions setup INVITE request in the IMS AS serving the originating UE with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4], the AS will trigger the DC media resources reservation according to 3GPP TS 23.228 [3] and route the INVITE message to the S-CSCF towards the terminating UE.
In case of CCBS activation, on reception of SIP response 486 (User Busy) from the terminating network, the IMS AS will release the reserved data channel media offered to the terminating network as per procedures defined in clause 9.3. On sending the SIP response 486 (User Busy) to the originating UE, the AS will release the reserved data channel media terminated from the originating UE as per procedures defined in clause 9.3.
In case of CCNL activation, on reception of SIP response 480 (Temporarily Unavailable) from the terminating network, the IMS AS will release the reserved data channel media offered to the terminating network as per procedures defined in clause 9.3. On sending the SIP response 480 (Temporarily Unavailable) to the originating UE, the IMS AS will release the reserved data channel media terminated from the originating UE as per procedures defined in clause 9.3.
In case of CCNR activation, upon reception a 180 (Ringing) response from the terminating network, the IMS AS will notify to DCSF and update the data channel media resources. Upon reception the SIP response 487 (Request Terminated) from the terminating network, the IMS AS will release the data channel media resources along with the session release. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.14 Enhanced Calling Name (eCNAM) | No interaction with IMS data channel. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.15 Closed User Group (CUG) | No interaction with IMS data channel. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.16 Communication Barring (CB) | No interaction with IMS data channel. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.17 Customized Ringing Signal (CRS) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.17.1 General | The CRS service is an operator specific service specified in 3GPP TS 24.183 [26], which describes three models of CRS service:
- Download and play model: it has no interaction with IMS data channel.
- Gateway model: it has no impact to IMS data channel.
- Early session model: it has no impact to IMS data channel.
As specified in 3GPP TS 24.183 [26], the CRS media can consist of music, voice, text, video or other customized ringing signals. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.17.2 Actions on the originating UE | When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its corresponding response.
In early session model, if the originating UE initiates an MMTel session with an IMS data channel, the UE shall include the data channel media description in the SDP offer of the initial SIP INVITE, as specified in the clause 9.3.2.1.2. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.17.3 Actions on the CRS AS | Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CRS AS shall ignore them and just transmit them transparently. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.18 Customized Alerting Tones (CAT) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.18.1 General | The CAT service is an operator specific service specified in 3GPP TS 24.182 [27], which describes three models of CAT service as follows:
- forking model: it has no impact to IMS data channel.
- gateway model: it has no impact to IMS data channel.
- early session model: it has no impact to IMS data channel.
As specified in 3GPP TS 24.182 [27], the CAT media can consist of favourable songs, multi-media clips or other customized alerting tones. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.18.2 Actions at the originating UE | When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its corresponding response.
In early session model, if the originating UE initiates MMTel session with an IMS data channel, the UE shall include the data channel media description in the SDP offer of initial SIP INVITE message, as specified in clause 9.3.2.1.2. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.18.3 Actions at the CAT AS | Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CAT AS shall ignore them and just transmit them transparently. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.19 Explicit Communication Transfer (ECT) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.19.1 General | The explicit communication transfer (ECT) service provides a party involved in a communication to transfer that communication to a third party as defined in 3GPP TS 24.629 [12].
There are three actors active in a transfer, they are acting in the following roles:
transferor: the party that initiates the transfer of the active communication that it has with the transferee;
transferee: the party which stays in the communication which is transferred;
transfer target: the party which the communication is transferred to and which replaces the transferor in the communication. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.19.2 Actions at the AS serving the transferor | On reception of REFER message, if ECT has been triggered as defined in 3GPP TS 24.629 [12], the IMS AS serving the transferor:
- shall trigger the closing of all the established data channels on the transferor’s network (including the data channel between the transferor’s network and the transferor, the data channel between the transferor’s network and the transferee, the data channel between transferor’s network and the transfer target) as per procedures defined in clause 9.3: and
- route the session setup INVITE request which includes audio, video and data channel media towards a REFER-TO user as defined in 3GPP TS 24.629 [12]. The data channel media set up shall be performed between the transferee and the transfer target together with audio, video media negotiation as per procedures defined in clause 9.3. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.19.3 Actions at the AS serving the transferee | If the transferee's network has established data channel media with the transferor before the transfer happens, the transferee's network shall release the data channel between transferor and transferee’s network. After establishment of an IMS session towards the transfer target data channels may be established towards the transfer target as per procedures defined in clause 9.3. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.19.4 Actions at the AS serving the transfer target | In case of blind transfer, if the transfer target's network provides data channel service, on reception of incoming INVITE request from transferor’s network, the transfer target's network shall send the INVITE message to transfer target. On reception of the 18x response or 200 (OK) response on the INVITE message from the transfer target, the transfer target's network shall trigger the reservation of the data channel media resources to establish the data channel for the transfer target and the transferee, together with audio, video media negotiation as per procedures defined in clause 9.3 and then sends the 18x response or 200 (OK) response to transferor’s network.
In case of consultative transfer, if the transfer target's network provides data channel service, on reception of incoming re-INVITE request with the SDP offer of transferee’s network from transferor’s network, the transfer target's network shall update the established data channel between transfer target’s network and transferor to data channel between transfer target’s network and transferee. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20 Communication Hold (HOLD) | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20.1 Actions at the invoking UE | If the UE want to put some media stream on hold, then in addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the invoking UE.
The invoking UE shall include in the generated SDP offer as specified in 3GPP TS 26.114 [4]:
1) for each data channel media that was previously active (i.e. the SDP direction attribute "a=sendrecv" was present in the last SDP body or no SDP direction attribute was included), the SDP direction attribute "a=inactive" associated with the corresponding "m=application" line if the invoking UE wants to suspend the data channel media; and
2) for each data channel media that was previously suspended (i.e. the SDP direction attribute "a=inactive" was present in the last SDP body), the SDP direction attribute "a=sendrecv" associated with the corresponding "m=application" line (or to omit the SDP direction attribute) if the invoking UE wants to resume the suspended data channel media;
and as specified in 3GPP TS 24.610 [32], the invoking UE shall send the generated SDP offer in a re-INVITE request to the remote UE. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20.2 Actions at the AS serving the invoking UE | |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20.2.1 General | In addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the AS serving the invoking UE.
NOTE: The AS serving the invoking UE can be the AS in the originating IMS network and/or the terminating IMS network, depending on by which network the media to be suspended is managed. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20.2.2 Event report | On reception of the SIP re-INVITE request with the SDP offer that contains an "a=inactive" SDP direction attribute in data channel media description and data channel media was previously active, the AS shall notify the DCSF that data channel media is to be suspended as specified in 3GPP TS 29.175 [18].
On reception of the SIP re-INVITE request with the SDP offer that contains an "a=sendrecv" SDP direction attribute (or the SDP direction attribute is omitted) in data channel media description and data channel media was previously suspended, the AS shall notify the DCSF that data channel media is to be resumed as specified in 3GPP TS 29.175 [18].
Based on the instruction from the DCSF, the AS serving the invoking UE shall modify the SDP offer where:
1) for each data channel media towards the remote UE that was previously active (i.e. the SDP direction attribute "a=sendrecv" was present in the last SDP body or no SDP direction attribute was included), the SDP direction attribute "a=inactive" associated with the corresponding "m=application" line;
2) for each data channel media towards the remote UE that was previously suspended (i.e. the SDP direction attribute "a=inactive" was present in the last SDP body), the SDP direction attribute "a=sendrecv" associated with the corresponding "m=application" line (or to omit the SDP direction attribute);
and as specified in 3GPP TS 24.610 [32], the IMS AS shall send the modified SDP offer in a re-INVITE request to the remote UE. |
28a605aed849a8e4682a36cdb0077b63 | 24.186 | 10.20.3 Actions at the held UE | In addition to the application of procedures according to 3GPP TS 24.610 [32], the held UE shall generate an SDP answer for the held data channel media as specified as 3GPP TS 26.114 [4]. Annex A (informative): Signalling flows This annex provides the signalling flows related to clause10. A.1 Interaction with supplementary services Below sections depict signalling flow diagram for IMS data channel service interaction with existing MMTel supplementary services. A.1.1 Communication Diversion A.1.1.1 Communication Forwarding unconditional Figure A.1.1.1-1 shows an example signalling flow for a successful communication forwarding unconditional based on an AS providing the forwarding and initial communication setup request consist of DC media session setup request along with other MMTel media session setup request. Figure A.1.1.1-1: Call Forwarding Unconditional The description of the steps mentioned in the figure A.1.1.1-1 is in accordance with the 3GPP TS 24.604 [16] with the additions defined in the present document: 1. in step 1), user A(UA-A) sends initial INVITE request towards the user B(UA-B), which contains: • the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field; • optionally the Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in IETF RFC 5688 [5] with a value of "webrtc-datachannel" as specified in 3GPP TS 26.114 [4]; and • the SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4]; 2. in step 3), the IMS AS serving the user B(UA-B) receives SIP INVITE request with DC media. CFU service condition is satisfied based on the diverting user B(UA-B) subscription data. Depending on the diverting user B (UA-B) IMS data channel subscription, the IMS AS of the diverting user does not send session event notification to the DCSF for data channel setup. Procedures for CFU are executed; 3. in step 5) the IMS AS sends SIP INVITE request with data channel media towards the diverted-to-user C(UA-C); 4. in step 7) the communication is routed towards the diverted-to-user C(UA-C) along with data channel media; 5. in step 9) bootstrap data channel is established for the originating user A(UA-A)/network and the diverted-to-user C(UA-C)/network; and 6. in step 10) application data channel is established along with other MMTel media. A.1.1.2 Communication Forwarding on Busy Figures A.1.1.2-1 shows an example signalling flow for a successful communication forwarding on busy based on an AS providing the forwarding and initial communication setup request consist of DC media session setup request along with other MMTel media session setup request. Figure A.1.1.2-1: Call Forwarding on Busy The description of the steps mentioned in the figure A.1.1.2-1 is in accordance with the 3GPP TS 24.604 [16] with the additions defined in the present document: 1. in step 1) user A(UA-A) sends initial INVITE request towards the user B(UA-B) in accordance with clause A.1.1.1 step 1); 2. in step 3) to step 12) the IMS AS serving the user B(UA-B) receives SIP INVITE request with DC media. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3]; 3. in step 13) the initial INVITE request is sent to the user B(UA-B) along with data channel media due to normal communication procedures; 4. in step 15) to step 17) on reception of the 486 (Busy Here) response for the initial INVITE request, in the IMS AS, CFB service condition is satisfied based on the diverting user B(UA-B) subscription data. Procedures for CFB are executed. The IMS AS notifies session establishment failure event to the DCSF and sends media resource management request to the MF to release the allocated data channel media resources for this SIP Session. 5. in step 19) the IMS AS sends SIP INVITE request with data channel media towards the diverted-to-user C(UA-C); 6. in step 21) the communication is routed towards the diverted-to-user C(UA-C) along with data channel media; 7. in step 23) bootstrap data channel is established between the originating user A(UA-A)/network and the diverted-to-user C(UA-C)/network; and 8. in step 24) application data channel is established along with other MMTel media. A.1.2 Communication Waiting (CW) A.1.2.1 Network based CW flows Figure A.1.2.1-1 shows an example of network-based communication waiting signalling flow at the terminating side and successful communication establishment. Waiting communication request contains DC media session along with other MMTel media sessions. Figure A.1.2.1-1: Network based CW flow: Successful communication establishment. The description of the steps mentioned in the figure A.1.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document: 1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1); 2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media; 3. in step 2a) to step 2c) the IMS AS of user B(UA-B) executes network-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3]; 4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media and call waiting indication for waiting communication, towards the user B(UA-B); 5. in step 13) the IMS AS of the user B(UA-B) receives 200OK response with data channel media from user B(UA-B) for the waiting communication; and 6. in step 13a) the IMS AS of the user B(UA-B) sends successful session establishment event notification for waiting communication to the DCSF serving the user B(UA-B). A.1.2.2 Terminal based CW flows A.1.2.2.1 Successful communication establishment Figure A.1.2.2.1-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and successful communication establishment. Waiting communication request contains DC media session along with other MMTel media sessions. Figure A.1.2.2.1-1 Terminal based CW: Successful communication establishment. The description of the steps mentioned in the figure A.1.2.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document: 1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1); 2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media; 3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3]; 4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B); 5. in step 8a), step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); 6. in step 18) the IMS AS of the user B(UA-B) receives 200OK response with data channel media from user B(UA-B) for the waiting communication; and 7. in step 18b) the IMS AS of the user B(UA-B) sends successful session establishment event notification for waiting communication, to the DCSF serving the user B(UA-B). A.1.2.2.2 AS CW Timer expires Figure A.1.2.2.2-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at IMS AS. Waiting communication request contains DC media session along with other MMTel media sessions. Figure A.1.2.2.2-1 Terminal based CW: CW timer expires at AS. The description of the steps mentioned in the figure A.1.2.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document: 1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1); 2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media; 3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3]; 4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B); 5. in step 8a), 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and 6. in step 14c) to step 14d) upon CW timer expiry for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response. A.1.2.2.3 UE CW timer expires Figure A.1.2.2.3-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at UE-B. Waiting communication request contains DC media session along with other MMTel media sessions. Figure A.1.2.2.3-1 Terminal based CW: CW timer expires at UE-B. The description of the steps mentioned in the figure A.1.2.2.3-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document: 1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1); 2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media; 3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3]; 4. in step 8a, step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and 5. in step 18a) to step 18b) upon reception of 480 (Temporarily Unavailable) SIP response for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response. A.1.3 Explicit Communication Transfer A.1.3.1 IMS serving the transferee provides data channel service A.1.3.1.1 Blind Transfer Figure A.1.3.1.1-1: Blind Transfer when IMS serving the transferee provides data channel service Figure A.1.3.1.1-1 shows a call flow for blind transfer when IMS serving the transferee provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: DC media resource is allocated by IMS-A for UE-A and UE-B. Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-A establishes BDC connection for UE-A and UE-B. And then IMS-A establishes ADC connections between UE-A and UE-B. Step7: UE-B starts transfer process. Step8: UE-B sends a REFER message to transfer the call to UE-C. Step9-10: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. UE-B releases reserved DC media resources of established BDC and ADC between UE-B and IMS-A/UE-A for A-B call. Step11-12: IMS-B sends an initial INVITE message to UE-C without SDP, UE-C replies SDP offer with audio media in 18X/200 response. Step13: IMS-B sends re-INVITE message to IMS-A and release the data channels between the IMS-B and UE-A. Step14-16: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-B. IMS-A releases reserved DC media resources of established BDC and ADC between IMS-A and UE-B for A-B call. Step17-19: IMS AS of IMS-A sends a re-INVITE message carrying SDP offer with data channel media towards UE-A. In SDP offer of re-INVITE message, the IMS AS of IMS-A adds previously established BDC and ADC between IMS-A and UE-A for A-B call with UDP ports set to zero. Earlier established BDC between UE-A and IMS-A (in step 4-1) can remain as it is or re-established as per operator policy. IMS-A releases the earlier established DC media resources between IMS-A and UE-A. UE-A releases the earlier established DC media resources between UE-A and IMS-A/UE-B and prepare SDP answer with earlier established DC media with UDP port zero. UE-A replies with the SDP answer with data channel media included in the 200 OK response. Step20-22: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-A. Step23: IMS AS of IMS-A sends a 200 OK message with updated data channel media to IMS-B. Step24: IMS-B sends PRACK/ACK message towards UE-C with no DC media in SDP answer. Step25: The session connection is established between UE-A and UE-C. A.1.3.1.2 Consultation Transfer Figure A.1.3.1.2-1: Consultative Transfer when IMS serving the transferee provides data channel service Figure A.1.3.1.2-1 shows a call flow for consultative transfer when IMS serving the transferee provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: DC media resource is allocated by IMS-A for UE-A and UE-B. Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-A establishes BDC connection for UE-A and UE-B. And then IMS-A establishes ADC connections between UE-A and UE-B. Step7-8: UE-B holds UE-A, and then calls UE-C. Step9: When UE-C sends 180 ringing or 200 response, UE-B starts transfer process. Step10: UE-B sends a REFER message to transfer the call to UE-C. Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. Step13-15: IMS-B sends a media re-negotiation request to UE-A, UE-A replies SDP offer with data channel media description. Step16-18: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-A. Step19: IMS AS sends a 200 OK response for re-INVITE to the IMS-B with updated data channel media. Step20-21: IMS-B sends a re-INVITE message carrying SDP offer with data channel media towards UE-C, and receives 200 OK response for reINVITE carrying SDP answer with data channel media from UE-C. Step22: IMS-B sends an ACK message carrying SDP answer with data channel media towards IMS-A. Step23-25: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-C. Step26: IMS AS of IMS-A sends an ACK message carrying SDP answer with data channel media towards UE-A. Step27: The BDC media connection is established between IMS-A and UE-C. Step28: The ADC media connections are established between UE-A and UE-C. Step29: The session connection is established between UE-A and UE-C. A.1.3.2 IMS serving the transferor provides data channel service A.1.3.2.1 Blind Transfer Figure A.1.3.2.1-1: Blind Transfer when IMS serving the transferor provides data channel service Figure A.1.3.2.1-1 shows a call flow for blind transfer when IMS serving the transferor provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: DC media resource is allocated by IMS-B for UE-A and UE-B. Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-B establishes BDC connection for UE-A and UE-B. And then IMS-B establishes ADC connections between UE-A and UE-B. Step7: UE-B starts transfer process. Step8: UE-B sends a REFER message to transfer the call to UE-C. Step9-10: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. Step11: IMS-B releases all the allocated data channel media resources on MF for UE-A, UE-B. Step12-17: IMS-B sends an INVITE message to UE-C, the audio along with data channel media connections are established between UE-A and UE-C, the data channel media can be provided either by IMS-A or IMS-C or both. A.1.3.2.2 Consultation Transfer Figure A.1.3.2.2-1: Consultative Transfer when IMS serving the transferor provides data channel service Figure A.1.3.2.2-1 shows a call flow for consultative transfer when IMS serving the transferor provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: DC media resource is allocated by IMS-B for UE-A and UE-B. Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-B establishes BDC connection for UE-A and UE-B. And then IMS-B establishes ADC connections between UE-A and UE-B. Step7-8: UE-B holds UE-A, and then calls UE-C. Step9: When UE-C sends 180 ringing or 200 response, UE-B starts transfer process. Step10: UE-B sends a REFER message to transfer the call to UE-C. Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. Step13: IMS-B releases all the allocated data channel media resources on MF for UE-A, UE-B and UE-C. Step14-18: IMS-B sends a media re-negotiation request with to establish the connection between UE-A and UE-C. Step19: The audio along with data channel media connections are established between UE-A and UE-C, the data channel media can be provided either by IMS-A or IMS-C or both. A.1.3.3 IMS serving the transfer target provides data channel service A.1.3.3.1 Blind Transfer Figure A.1.3.3.1-1: Blind Transfer when IMS serving the transfer target provides data channel service Figure A.1.3.3.1-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: UE-B answers the call, session connection is established between UE-A and UE-B. Step3: UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C. Step4-5: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. Step6: IMS-B sends an INVITE message towards UE-C. Step7-9: IMS-C forwards the INVITE message to UE-C. On reception of 18X/200 message with data channel media from UE-C, IMS-C allocates the data channel media resources on MF for UE-A and UE-C. Step10.: IMS-C sends the 18X/200 message to IMS-B. Step11-12: IMS-B transfers the 18X/200 message to reINVITE message and sends it towards UE-A, UE-A responses 200 OK with data channel media answer to IMS-B. Step13-14: IMS-B transfers the 200 OK message to PRACK/ACK message and sends it to IMS-C. IMS-C update data channel media on MF. Then IMS-C sends the PRACK/ACK message to UE-C. Step16: The BDC media connections are established on MF of IMS-C for both UE-A and UE-C. Step17: The ADC media connections are established between UE-A and UE-C. Step18: The session connection is established between UE-A and UE-C. A.1.3.3.2 Consultation Transfer Figure A.1.3.3.2-1: Consultative Transfer when IMS serving the transfer target provides data channel service Figure A.1.3.3.2-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service. Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B. Step2: UE-B answers the call, session connection is established between UE-A and UE-B. Step3-9: UE-B holds UE-A, and then calls UE-C, session connection is established between UE-B and UE-C. IMS-C establishes BDC connection for UE-B and UE-C. And then IMS-C establishes ADC connections between UE-B and UE-C. Step10: UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C. Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. Step13-15: IMS-B sends a re-INVITE request to establish the connection between UE-A and UE-C. Step16: IMS-C updates the DC media connection for UE-A when receiving the updated data channel media from UE-A. Step17-19: The media re-negotiation finished between UE-A and UE-C. Step20: The BDC media connection is established on MF of IMS-C for UE-A. Step21: The ADC media connections are established between UE-A and UE-C. Step22: The session connection is established between UE-A and UE-C. Annex B (normative): Extensions within the present document B.1 Feature-capability indicators defined in the present document This clause describes the feature-capability indicators definitions, according to IETF RFC 6809 [6], that are applicable for the 3GPP IM CN subsystem. B.1.1 Definition of feature-capability indicator g.3gpp.datachannel Feature-capability indicator name: g.3gpp.datachannel Summary of the feature indicated by this feature-capability indicator: This feature-capability indicator indicates the support of data channel capability in the network, and can be included in a Feature-Caps header field as specified in IETF RFC 6809 [6] in a 200 (OK) response to the REGISTER request. Feature-capability indicator specification reference: 3GPP TS 24.186, http://www.3gpp.org/ftp/Specs/archive/24_series/24.186/ Values appropriate for use with this feature-capability indicator: Not applicable Examples of typical use: Indicating the support of data channel capability in the network. Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of IETF RFC 6809[6]. B.1.2 Definition of feature-capability indicator g.3gpp.dc-mux Editor's note: this feature-capability indicator is to be registered with IANA when release 19 is completed. Feature-capability indicator name: g.3gpp.dc-mux Summary of the feature indicated by this feature-capability indicator:This feature-capability indicator indicates the support of IMS data channel multiplexing capability in the network, and can be included in a Feature-Caps header field as specified in IETF RFC 6809 [6] in SIP request and response. Feature-capability indicator specification reference: 3GPP TS 24.186, http://www.3gpp.org/ftp/Specs/archive/24_series/24.186/ Values appropriate for use with this feature-capability indicator: Not applicable Examples of typical use: Indicating the support of IMS data channel multiplexing capability in the network. Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of IETF RFC 6809[6]. Annex C(normative): Applications based on IMS data channel C.1 General The present annex depicts the applications based on the IMS data channel, including the corresponding procedures. C.2 AR communication C.2.1 AR Remote Cooperation C.2.1.1 General Description According to clause 6.39.2 of 3GPP TS 22.261 [2], the IMS network should support AR media processing. AR Remote Cooperation is a typical AR call service and the detailed user experience of AR Remote Cooperation is described in clause 5.3 of 3GPP TR 22.873 [13]. It’s assumed that the local UE shares the camera to the remote UE for assistance, and the remote UE displays the shared camera and provides assistances. A voice call is established between local UE and remote UE, and then AR Remote Assistance application is triggered by local UE. The overall solution is based on IMS DC architecture specified in Annex AC of 3GPP TS 23.228 [3] and shown as follows: - The local UE triggers the media renegotiation for AR Remote Cooperation based on user actions to establish a new video stream to transmit local video content (see A002 in figure C.2.1.1-1) and an application data channel to transmit AR anchors (see A001 in figure C.2.1.1-1). - After the DCSF recognizes the AR Remote Cooperation service, it anchors the video stream and application data channel to MF. Then the DCSF initiates media renegotiation with remote UE to establish a new video stream to transmit local video content (see B002 in figure C.2.1.1-1) and an application data channel to transmit AR anchors (see B001 in figure C.2.1.1-1). - The local UE may decide to start AR media split rendering negotiation as specified in 3GPP TS 26.264 [29] and 3GPP TS 23.228 [29]. - The local UE or remote UE extract the original AR anchors input from the user and transmits the anchors to the MF through the application data channel. - The local UE and remote UE receives the updated AR anchors from the MF, displays it on the video stream. Figure C.2.1.1-1 illustrates the media connection model of the AR Remote Cooperation. Figure C.2.1.1-1: Media Connection model of AR Remote Cooperation Table C.2.1.1-1 lists the media streams for the AR Remote Cooperation. Table C.2.1.1-1 Media stream list for the AR Remote Cooperation Media ID (Example) Media Resource Type Direction Description A001 DC bi-directional Transmit upstream and downstream AR anchors between MF and local UE and the split rendering messages. A002 Video unidirectional Transmit video content from local UE to the MF. B001 DC bi-directional Transmit upstream and downstream AR anchors between the MF and remote UE. B002 Video unidirectional Transmit local UE's video content to remote UE. C.2.2 Procedures C.2.2.1 Data Channel Setup C.2.2.1.1 Procedure at the UE Once AR remote cooperation application is launched, the local UE sends a SIP re-INVITE request with an SDP offer which includes a video media description with an "a=sendonly" attribute line to establish a video stream (see B001 in Figure C.2.1.1-1) as specified in 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10] and a data channel media description with "a=dcmap" attribute line containing "stream-id" parameter set to the values starting at 1000 and "a=3gpp-req-app " attribute line to establish an application data channel (see A001 in Figure C.2.1.1-1) as specified in clause 9.3. The "a=3gpp-req-app " attribute line indicates that the newly established application data channel is used for AR Remote Cooperation application. After application data channel and video stream established, the local UE may decide to start split rendering. If the local UE decides to split rendering, the UE shall use the procedure defined in 3GPP TS 26.264 [29]. After split rendering negotiation procedure finished, both the local UE or remote UE extracts the original AR anchors input by the user and transmits it to MF through the established application data channel. When receiving the updated AR anchors transmitted via application data channel from the MF, both the local UE and the remote UE displays the updated AR anchors based on video stream. C.2.2.1.2 Procedure at the IMS AS When receiving the SIP re-INVITE request from local UE, IMS AS shall notify the DCSF about media change request related to local UE requesting to setup an application data channel and a new video. When receiving media reservation instruction from DCSF, the IMS AS shall convert the media instructions to the corresponding media resource operations and request MF to create or update media resources, and reserve media processing resources for AR Remote Cooperation. When receiving response from MF on the media resources reservation or update, IMS AS sends media reservation response to DCSF, indicating the URL addresses of each stream involved AR Remote Cooperation service control, which is specified in 3GPP TS 29.175 [18]. C.2.2.2 Closing Data Channel If the UE wants to close the AR remote cooperation related application data channels, the procedure defined in clause 9.3 applies. C.3 Avatar communication C.3.1 General As specified in clause 5.2.2.2 in 3GPP TS 22.156 [34], the IMS network shall support avatar-based real time communication. The overall solution of avatar communication based on IMS data channel is defined in 3GPP TS 23.228 [3]. C.3.2 Procedures C.3.2.1 Procedure at the UE When the UE downloading the avatar application through the established bootstrap data channel as specified in clause 9.3.2.1.2 or clause 9.3.2.1.3.1, the UE may fetch the list of Avatar ID as specified in 3GPP TS 23.228 [3] through bootstrap data channel. NOTE: The list of Avatar ID can be pre-configured in the UE or downloaded to the UE through application data channel. These procedures are outside the scope of this specification. Editor’s note: How the application data channel for avatar communication is established and used is FFS. After the user selects the Avatar ID, based on the rendering mode, the two UEs in the call may get the Avatar Representation identified with the selected Avatar IDs via the application data channel if needed. Editor’s note: How the rendering mode is confirmed is FFS. Editor’s note: The avatar media rendering process and animation data generation is FFS. 3GPP Annex <D> (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2023-04 CT1#141 Draft skeleton provided by the rapporteur. 0.0.0 2023-04 CT1#141 Implementing the agreed pCR: C1-232932, C1-232933, C1-232934 0.1.0 2023-05 CT1#142 Implementing the agreed pCR: C1-234121, C1-234122, C1-234123, C1-234124 0.2.0 2023-08 CT1#143 Implementing the agreed pCR: C1-236169, C1-236178, C1-236184, C1-236188, C1-236189, C1-236191, C1-236544 0.3.0 2023-10 CT1#144 Implementing the agreed pCR: C1-238296, C1-238298, C1-238299, C1-238303, C1-238306, C1-238310, C1-238313, C1-238320, C1-238321, C1-238322, C1-238323 0.4.0 2023-11 CT1#145 Implementing the agreed pCR: C1-238764, C1-238928, C1-239524, C1-239525, C1-239526, C1-239527, C1-239528, C1-239530, C1-239531, C1-239532, C1-239534, C1-239535, C1-239536, C1-239539, C1-239542, C1-239543, C1-239544, C1-239545, C1-239546, C1-239555 0.5.0 2023-12 CT#102 Presentation to TSG CT for information 1.0.0 2024-01 CT1#146 Implementing the agreed pCR: C1-240115, C1-240131, C1-240137, C1-240193, C1-240195, C1-240281, C1-240283, C1-240343, C1-240344, C1-240345, C1-240346, C1-240347, C1-240348, C1-240349, C1-240352, C1-240377, C1-240378, C1-240379, C1-240380, C1-240383, C1-240384, C1-240385, C1-240386, C1-240387 1.1.0 2024-03 CT1#147 Implementing the agreed pCR: C1-240623, C1-240733, C1-241409, C1-241428, C1-241432, C1-241435, C1-241437, C1-241439, C1-241450, C1-241452, C1-241454, C1-241455, C1-241456, C1-241464, C1-241470, C1-241471, C1-241472, C1-241474, C1-241476, C1-241477, C1-241478 1.2.0 2024-03 CT#103 CP-240231 Presentation to TSG CT for approval 2.0.0 2024-06 CT#104 CP-241186 0012 - B Abnormal case for DC1 interface 18.1.0 2024-06 CT#104 CP-241186 0001 1 B The requirement of the IMS AS during registration 18.1.0 2024-06 CT#104 CP-241186 0006 1 F Correction to TS 24.186 18.1.0 2024-06 CT#104 CP-241186 0008 1 F Clarification on the procedure of IMS AS during session setup and session modification 18.1.0 2024-06 CT#104 CP-241186 0007 1 F Add the handling of SDP answer in the procedure of IMS AS 18.1.0 2024-06 CT#104 CP-241186 0010 1 F Support of AR media split rendering negotiation 18.1.0 2024-06 CT#104 CP-241186 0015 1 F Removal of CONF related EN 18.1.0 2024-06 CT#104 CP-241186 0009 2 F Clarification on the capability negotiation 18.1.0 2024-06 CT#104 CP-241186 0003 2 F Update the abnormal case on DC2 18.1.0 2024-06 CT#104 CP-241186 0004 3 C Solve the EN on UICC configuration 18.1.0 2024-06 CT#104 CP-241186 0005 2 C Clarification on DC setup policy 18.1.0 2024-06 CT#104 CP-241186 0027 - F Update the DC setup policy according to the new definition of DC setup option 18.1.0 2024-06 CT#104 CP-241186 0011 3 B Interaction with CH supplementary service 18.1.0 2024-06 CT#104 CP-241186 0023 1 F Correction on the procedure of IMS AS 18.1.0 2024-06 CT#104 CP-241186 0018 1 F Procedure of originating IMS AS on receiving the BDC establishment request 18.1.0 2024-06 CT#104 CP-241186 0025 1 F The remote BDC setup requested by the UE 18.1.0 2024-06 CT#104 CP-241186 0026 1 B Abnormal case for DC QoS negotiation in P2A and P2A2P scenarios 18.1.0 2024-06 CT#104 CP-241186 0017 2 F Delete MRF from the spec 18.1.0 2024-09 CT#105 CP-242191 0024 3 F DC resource release due to a CANCEL request 18.2.0 2024-09 CT#105 CP-242191 0031 1 F DC related re-INVITE request collision 18.2.0 2024-09 CT#105 CP-242191 0032 1 F Correct the IMS AS procedure on handling IP and port number 18.2.0 2024-09 CT#105 CP-242191 0028 1 F Correction to error handling 19.0.0 2024-09 CT#105 CP-242191 0033 1 F Correction on the incomplete SIP request and responses 19.0.0 2024-12 CT#106 CP-243193 0037 1 A Correction on the SDP handling for ADC setup 19.1.0 2024-12 CT#106 CP-243223 0042 1 B Support of interworking with MTSI client 19.1.0 2024-12 CT#106 CP-243223 0041 1 B Support of Standalone DC 19.1.0 2024-12 CT#106 CP-243193 0043 1 F Miscellaneous corrections 19.1.0 2024-12 CT#106 CP-243193 0035 2 A Correction on the BDCs and ADCs in a m line 19.1.0 2024-12 CT#106 CP-243223 0039 2 B Update session control and DC application related requirement to support the standalone DC 19.1.0 2024-12 CT#106 CP-243193 0049 1 F Correction on the IMS AS behaviour in CDIV 19.1.0 2024-12 CT#106 CP-243223 0050 1 B UE handling of IMS data channel in PS Data off feature 19.1.0 2024-12 CT#106 CP-243223 0051 1 B AS handling of IMS data channel in PS Data off feature 19.1.0 2024-12 CT#106 CP-243223 0054 1 B Procedure of avatar communication 19.1.0 2024-12 CT#106 CP-243193 0045 1 F Clarify the calling and called identity notified to the DCSF 19.1.0 2024-12 CT#106 CP-243223 0052 2 B Procedure of Standalone data channel 19.1.0 2024-12 CT#106 CP-243223 0053 2 B Procedure of network-initiated DC establishment 19.1.0 2025-03 CT#107 CP-250145 0002 6 B Setup local BDC on terminating side in case INVITE does not contain DC description 19.2.0 2025-03 CT#107 CP-250144 0055 - F Correction on the description of SDP handling for ADC 19.2.0 2025-03 CT#107 CP-250150 0056 2 B Update the IMS AS requirement for the enforcement of PS data off 19.2.0 2025-03 CT#107 CP-250150 0057 1 B Update the IMS AS requirement for the support of interworking with MTSI client 19.2.0 2025-03 CT#107 CP-250150 0058 3 B Support of DC multiplexing capability negotiation and indication 19.2.0 2025-03 CT#107 CP-250150 0059 2 B UE support of DC multiplexing 19.2.0 2025-03 CT#107 CP-250199 0061 2 B Network initiated standalone IMS DC session setup 19.2.0 2025-03 CT#107 CP-250150 0062 1 B Procedure of network initiated P2P application data channel establishment 19.2.0 2025-03 CT#107 CP-250150 0064 1 F Remove a EN of avatar communication 19.2.0 2025-03 CT#107 CP-250150 0065 1 B Procedure of application data channel interworking via DC AS for originating UE 19.2.0 2025-03 CT#107 CP-250172 0067 1 A ECT corrections: AS serving the transferee and blind call flow 19.2.0 2025-03 CT#107 CP-250144 0068 - F Conferencing procedure at IMS AS 19.2.0 2025-03 CT#107 CP-250150 0069 - D Editorial corrections 19.2.0 2025-03 CT#107 CP-250150 0070 1 B PS Data off support during IMS session establishment 19.2.0 |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 1 Scope | The present document identifies the requirements for operation of Uncrewed Aerial Vehicles (UAVs) via the 3GPP system.
This includes requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 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] FAA UTM Concept of Operations v1.0, Foundational Principles, Roles and Responsibilities, Use Cases and Operational Threads https://utm.arc.nasa.gov/docs/2018-UTM-ConOps-v1.0.pdf
[3] FAA Remote Identification, https://www.faa.gov/uas/research_development/remote_id/
[4] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[5] IMT 2020(5G): "Application for UAV in 5G White Paper", September 2018 |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3 Definitions, symbols and abbreviations | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Above ground level (AGL): In the context of a UAV it is the UAV altitude referenced to ground level in the vicinity.
Command and Control (C2) Communication: the user plane link to convey messages with information of command and control for UAV operation between a UAV controller and a UAV.
Uncrewed Aerial System (UAS): Composed of Uncrewed Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the controller, the UAV and the network, and for remote identification. A UAS is comprised of a UAV and a UAV controller.
NOTE: A UAV can be controlled by different UAV controllers, but at any given time, a UAV is under the control of only one UAV controller. The mechanisms to ensure which UAV controller is active and controlling the UAV is out of scope of 3GPP.
Uncrewed Aerial System Traffic Management (UTM): a set of functions and services for managing a range of autonomous vehicle operations.
UAV controller: The UAV controller of a UAS enables a drone pilot to control an UAV.
UxNB: radio access node on-board UAV. It is a radio access node providing connectivity to UEs, which is carried in the air by an Uncrewed Aerial Vehicle (UAV). |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
BVLOS Beyond Visual Line of Sight
C2 Command and Control
Remote ID Remote Identification [3]
UAS Uncrewed Aerial System
UAV Uncrewed Aerial Vehicle
UTM Uncrewed Aerial System Traffic Management [2] |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4 Overview on UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.1 General | An Uncrewed Aerial System (UAS) is the combination of an Uncrewed Aerial Vehicle (UAV), sometimes called a drone, and a UAV controller. A UAV is an aircraft without a human pilot onboard – instead, in some cases. the UAV can be controlled from an operator via a UAV controller and will have a range of autonomous flight capabilities. The communication system between the UAV and UAV controller is, within the scope of this specification and in some scenarios, provided by the 3GPP system. The UAS model considers also the scenario where the UAV controller communicates with the UAV via mechanisms outside the scope of 3GPP.
UAVs range in size and weight from small, light aircraft often used for recreational purposes to large, heavy aircraft which are often more suited to commercial applications. Regulatory requirements vary across this range and vary on a regional basis.
The communication requirements for UAS cover both the Command and Control (C2), and uplink and downlink data to/from the UAS components towards both the serving 3GPP network and network servers. The applicable C2 communication modes is depicted in clause 4.2.
Uncrewed Aerial System Traffic Management (UTM) is used to provide a number of services to support UAS and their operations including but not limited to UAS identification and tracking, authorisation, enforcement, regulation of UAS operations, and also to store the data required for UAS(s) to operate. It also allows authorised users (e.g., air traffic control, public safety agencies) to query the identity and metadata of a UAV and its UAV controller. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.2 C2 Communication | When using 3GPP network as the transport network for supporting UAS services, the following C2 communication are considered to provision UAS services by guaranteeing QoS for the C2 communication:
Direct C2 communication: the UAV controller and UAV establish a direct C2 link to communicate with each other and both are registered to the 5G network using the radio resource configured and scheduled provided by the 5G network for direct C2 communication.
Network-Assisted C2 communication: the UAV controller and UAV register and establish respective unicast C2 communication links to the 5G network and communicate with each other via 5G network. Also, both the UAV controller and UAV may be registered to the 5G network via different NG-RAN nodes. The 5G network needs to support mechanism to handle the reliable routing of C2 communication.
UTM-Navigated C2 communication: the UAV has been provided a pre-scheduled flight plan, e.g. array of 4D polygons, for autonomous flying, however UTM still maintains a C2 communication link with the UAV in order to regularly monitor the flight status of the UAV, verify the flight status with up-to-date dynamic restrictions, provide route updates, and navigate the UAV whenever necessary.
In general, Direct C2 communication and Network-Assisted C2 communication are used by a human-operator using a UAV controller. UTM-Navigated C2 communication is used by the UTM to provide cleared flying routes and routes updates. In order to ensure the service availability and reliability of the C2 communication for UAS operation, especially when the UAV is flying beyond line of sight (BLOS) of the operator, redundant C2 communication links can be established for any C2 communication links from UAV controller or UTM to a UAV.
For reliability and service availability consideration, it is possible to activate more than one C2 communication with one as a backup link for C2 communication or switch among the applicable links for C2 communication.
- For example, Direct C2 communication can be used at first and then switch to the Network-Assisted C2 communication when the UAV is flying BLOS.
- For example, UTM-navigated C2 communication can be utilized whenever needed, e.g. for air traffic control, the UAV is approaching a No Drone Zone, and detected potential security threats, etc.
There are four control modes considered in the C2 communication for the UAV operation that are with different requirements, e.g. on message intervals, sizes, and end to end latencies, etc., including steer to waypoints, direct stick steering, automatic flight by UTM and approaching autonomous navigation infrastructure.
• Steer to waypoints: the control message contains flight declaration, e.g. waypoints, sent from the UAV controller or UTM to the UAV. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
• Direct stick steering: the control message contains direction instructions sending from the UAV controller to the UAV while optionally video traffic is provided as feedback from the UAV to the UAV controller. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
• Automatic flight by UTM: the control message contains a pre-scheduled flight plan, e.g. array of 4D polygons, sent from the UTM to the UAV, which thereafter flies autonomously with periodic position reporting. The control mode is used in UTM-Navigated C2 communication.
• Approaching autonomous navigation infrastructure: the control message contains direction instructions, e.g. waypoints, altitudes and speeds from the UTM to the UAV. When the UAV is landing/departing, the UTM coordinates more closely with autonomous navigation infrastructure, e.g. vertiport or package distribution center. The control mode is used in UTM-Navigated C2 communication. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5 Requirements for Remote Identification of UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.1 General | [R-5.1-001] The 3GPP system should enable UTM to associate the UAV and UAV controller, and the UTM to identify them as a UAS.
[R-5.1-002] The 3GPP system shall be able to provide UTM with the identity/identities of a UAS.
[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.
[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.
[R-5.1-005] The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS.
NOTE 0: Subject to the regional regulation, the different authentication and authorization levels can be: the initial network access authentication and authorization, UAS identity authentication, UAV flight plan authorization, additional UTM service authentications, such as flight monitoring, collision avoidance services, so on.
[R-5.1-006] The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future.
[R-5.1-007] Based on regulations and security protection, the 3GPP system shall enable a UAS to send UTM the identifiers which can be: IMEI, MSISDN, or IMSI, or IP address.
[R-5.1-008] Void
[R-5.1-009] The 3GPP system should enable an MNO to augment the data sent to a UTM with the following: network-based positioning information of UAV and UAV controller.
NOTE 1: This augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information, such as OTDOA, cell coordinates, synchronization source, etc.
NOTE 2: This requirement will not be applied to the case which the UAS and UTM has direct control communication connection without going through MNO, such as OTDOA, cell coordinates, synchronization source, etc.
[R-5.1-010] The 3GPP system shall enable UTM to inform an MNO of the outcome of an authorisation to operate.
[R-5.1-011] The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present.
[R-5.1-012] The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller.
[R-5.1-013] The 3GPP network should be able to provide supplement location information of UAV and its controller to a UTM.
NOTE 3: This supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information.
[R-5.1-014] The 3GPP network shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
[R-5.1-014a] The 3GPP system shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
[R-5.1-015] The 3GPP system shall provide the capability for network to obtain the UAS information regarding its support of 3GPP communication capabilities designed for UAS operation.
[R-5.1-016] The 3GPP system shall support the UAS identification and subscription data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE.
NOTE 4: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS.
[R-5.1-017] The 3GPP system shall support the UTM in detection of UAV operating without authorization.
NOTE 5: the scenarios covered by the requirement above are FFS.
[R-5.1-018] The 5G system shall be able to detect that a connected UE is airborne, when the UE doesn’t have an aerial subscription.
[R-5.1-019] The 5G system shall be able to support a mechanism to enable a network operator to track an airborne connected UE which doesn’t have an aerial subscription.
[R-5.1-020] Based on operator and UTM policy, the 5G system shall be able to provide UTM with an airborne UE’s location and 3GPP identity to fulfil the UTM’s request.
NOTE 6: The 3GPP identity and UE location is expected to be used by the UTM to determine the position of airborne objects containing the UE. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2 UAS traffic management | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.1 General | NOTE: The following requirements are valid for both centralized and decentralized UTM.
[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.
[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM to a UAS with a latency of less than 500ms.
[R-5.2.1-003] The 3GPP system shall be able to deliver the notifications received from a UTM to a UAV controller with a latency of less than 500ms.
[R-5.2.1-004] Based on MNO policies and/or regulatory requirements, the 3GPP system shall enable the UTM to take over the communication used to control the UAV. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.2 Decentralized UAS traffic management | [R-5.2.2-001] The 3GPP system shall enable a UAV to broadcast the following data for identifying UAV(s) in a short-range area for collision avoidance: e.g. UAV identities if needed based on different regulation requirements, UAV type, current location and time, flight route information, current speed, operating status.
[R-5.2.2-002] The 3GPP system shall be able to support a UAV to transmit a message via network connection for identifying itself as an UAV to the other UAV(s).
[R-5.2.2-003] The 3GPP system shall enable UAV to preserve the privacy of the owner of the UAV, UAV pilot, and the UAV operator in its broadcast of identity information.
[R-5.2.2-004] The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range.
[R-5.2.2-005] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service in the coverage or out of coverage of a 3GPP network.
[R-5.2.2-006] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when the sending and receiving UAVs are served by the same or different PLMNs.
[R-5.2.2-007] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320 km/h.
[R-5.2.2-008] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s).
[R-5.2.2-009] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600m.
[R-5.2.2-010] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second.
[R-5.2.2-011] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100ms. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.3 Void | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.4 Security | [R-5.4-001] The 3GPP system shall protect the transport of data between the UAS and UTM.
[R-5.4-002] The 3GPP system shall protect against spoofing attacks of the UAS identities.
[R-5.4-003] Void.
[R-5.4-004] Void.
[R-5.4-005] The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information.
[R-5.4-006] The 3GPP system shall support regulatory requirements (e.g. Lawful Intercept) for UAS traffic. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6 Requirements for UAV usages | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.1 General | Beyond UAV related requirements, the 3GPP can be used to support for a wide range of applications and scenarios by using low altitude UAVs in various commercial and government sectors. New service level requirements and KPIs for supporting various UAV applications by the 3GPP system have been identified and specified e.g. Service requirements and KPIs related to command and control (C2), payload (e.g. camera) and the operation of radio access nodes on-board UAVs. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.2 Network exposure for UAV services | [R-6.2-001] The 3GPP system shall provide means to allow a 3rd party to request and obtain real-time monitoring the status information (e.g., location of UAV, communication link status) of a UAV.
[R-6.2-002] Based on operator 's policy, the 3GPP system shall provide means to provide a 3rd party with the information regarding the service status for UAVs in a certain geographical area and/or at a certain time.
NOTE: Service status is about the information of whether the communication service to the UAV can be provided with a certain QoS by the network.
[R-6.2-003] Based on operator’s policy, the 5G system shall be able to support a method to predict, monitor network conditions and QoS (e.g. bitrate, latency, reliability) and report to 3rd party along a continuous geographic planned flight path of a UAV at specific times of its expected flight duration. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.3 Service restriction for UEs onboard of UAV | [R-6.3-001] The 3GPP network shall be able to support network-based 3D space positioning (e.g., with altitude 30~300m) of a UE onboard UAV.
[R-6.3-002] The 3GPP system shall be able to notify the authorized third party of potential stopping of connectivity service before the UE onboard of UAV enters an area (e.g., due to altitude) where the connectivity service is not authorized for the UE. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.4 Requirements for UxNB | [R-6.4-001] The 5G system shall be able to support UxNBs to provide enhanced and more flexible radio coverage.
[R-6.4-002] The 3GPP system shall be able to provide suitable means to control the operation of the UxNBs (e.g. to start operation, stop operation, replace UxNB etc.).
[R-6.4-003] The 3GPP system shall be able to provide means to minimize power consumption of the UxNBs (e.g. optimizing operation parameter, optimized traffic delivery).
[R-6.4-004] The 3GPP system shall be able to minimize interference e.g. caused by UxNBs changing their positions. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.5 C2 communication | [R-6.5-001] The 3GPP system shall support C2 communication with required QoS for pre-defined C2 communication models (e.g. using direct ProSe Communication between UAV and the UAV controller, UTM-navigated C2 communication based on flight plan between UTM and the UAV).
[R-6.5-002] The 3GPP system shall support C2 communication with required QoS when switching between the C2 communication models.
[R-6.5-003] The 3GPP system shall support a mechanism for the UTM to request monitoring of the C2 communication with required QoS for pre-defined C2 communication models (e.g. using direct ProSe Communication between UAV and the UAV controller, UTM-navigated C2 communication between UTM and the UAV). |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.6 UAV safety | [R-6.6-001] The 5G system shall support means to determine whether UTM supports regulatory requirements e.g., maximum VLOS distance between the UAV and the UAV controller.
NOTE: The requirement applies to the case of both UAV and UAV controller connected to the 3GPP network.
[R-6.6-002] Based on operator’s policy, the 5G system shall be able to support a method to provide UTM and UAVs with the information collected or generated by the 5G system (e.g., based on sensing results), including e.g., the location or relative distance between 3GPP UAVs and other flying objects (can be drones not using 3GPP connectivity).
[R-6.6-003] The 5G system shall be able to track the UAV controller, regardless of the type of connection.
[R-6.6-004] Based on MNO policies and/or regulatory requirements, the 5G system shall be able to inform the UTM, when the 5G system detects a specific UAV condition or event, in order to enable UTM control of the UAV communication (e.g., when detecting violation of exclusion zones or maximal distance between UAVs). |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.7 Flight path and zones management | [R-6.7-001] Based on a 3rd party request and operator’s policy, the 5G system shall be able to reconfigure network resources to provide the required QoS along a UAV planned flight path, e.g. at particular geographical area(s) and time(s).
[R-6.7-002] The 5G system shall be able to support mechanisms for the UTM to configure different aerial flight zones where UAV application settings and communication QoS may be different, and provide network and UAV with means to identify those flight zones.
[R-6.7-003] The 5G system shall be able to support mechanisms for the UTM to provide network and UAV with policy information including UAV application settings and communication QoS to be applied in specific aerial flight zones, e.g. based on flight zone type indicated or available to the UAV in a certain geographical location.
[R-6.7-004] Based on operator’s policy, the 5G system shall be able to support a method to monitor and provide a 3rd party with information about deviations and violations along a UAV flight path and time.
[R-6.7-004] Based on operator’s policy, the 5G system shall be able to support a method to monitor and provide a 3rd party with information about deviations and violations along a UAV flight path and time.
NOTE: Deviations can be e.g., in location and/or time with respect to the original flight plan. Violations can be e.g., with respect to exclusion zones provided together with the flight plan or known via other means.NOTE: Deviations can be e.g., in location and/or time with respect to the original flight plan. Violations can be e.g., with respect to exclusion zones provided together with the flight plan or known via other means. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.8 UTM assistance requirements | [R-6.8-001] Based on operator’s policy, the 5G system shall be able to provide UTM with the information about geographic areas where UAV service requirements could or could not be met based on predicted network conditions and QoS (e.g. bitrate, latency, reliability).
[R-6.8-002] Based on a 3rd party request, the 5G system shall be able to assist the UTM with mechanism to provide to the 3rd party alternative UAV flight paths, e.g., based on required waypoints, QoS, and exclusion zones.
[R-6.8-003] The 5G system shall be able to support service enablement layer exposure mechanisms for the UTM or other authorized 3rd party to provide the UAV application with configuration information to route and switch traffic between one active and one standby PLMN connection, e.g. for C2 communication reliability and redundancy purpose, or to route different traffic across different PLMN connections simultaneously, e.g. C2 traffic via one PLMN and other data via the second PLMN.
NOTE 0: The above requirement specifically refers to service enablement layer exposure mechanisms. Other requirements in this document that refer to the 5G system can also mean requirements applicable to the service enablement layer.
NOTE 1: The above requirement can be extended to scenarios where one network is a PLMN and one is an NPN.
NOTE 2: There is no impact on legacy network selection.
NOTE 3: It is assumed that UAV traffic handling, over each PLMN, is subject to NW control mechanisms (e.g. in accordance with MNO routing priorities, available QoS/NW resources, etc.).
[R-6.8-004] Subject to user consent and national or regional regulation, based on operator and UTM policy, the 5G system may be able to provide aerial object location(s) derived using 5G Wireless Sensing to the UTM to fulfil the UTM’s request.
NOTE 4: The airborne object location(s) are expected to be used by the UTM to determine the position of airborne objects. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7 Performance requirements | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.1 KPIs for services provided to the UAV applications | The 5G system shall be able to provide uncrewed aerial vehicle with the service performance requirements reported in Table 7.1-1.
UAV originated QoS in the table refers to the QoS of Uplink data (e.g. from UAV to the network side). UAV terminated QoS is the QoS of downlink data (e.g. from the network side to UAV).
The data transmitted by the 5G system includes data collected by hardware devices installed on UAV such as cameras, e.g. pictures, videos and files. It is also possible to transmit some software calculation or statistical data, e.g. UAV management data. The service control data transmitted by the 5G system may be based on application triggers, such as switch, rotation, promotion and demotion control of equipment on UAV. Various UAV applications may require different uplink and downlink QoS at the same time. The 5G system may simultaneously provide services to other users on the ground (e.g., the KPIs for rural and urban scenarios as defined in 7.1 of TS 22.261 [4]) in the same area without service degradation.
Table 7.1-1 KPIs for services provided to the UAV applications
Use case
Services
Data rate
End to end Latency
Altitude AGL
service area
(note 4)
1
8K video live broadcast
100Mbps
UAV
originated
200 ms
<100 m
Urban, scenic area
600Kbps
UAV
terminated
20 ms
<100 m
2
Laser mapping/
HD patrol
Note 7
120Mbps
UAV
originated
Note 1
200 ms
30-300 m
Urban, rural area, scenic area
300Kbps
UAV
terminated
20 ms
30-300 m
3
4*4K AI surveillance
120Mbps
UAV
originated
20 ms
<200 m
Urban, rural area
50Mbps
UAV terminated
20 ms
<200 m
4
Remote UAV controller through HD video
>=25Mbps
UAV
originated
(Note 3)
100 ms
<300 m
Urban, rural area
300Kbps
UAV
terminated
20 ms
<300 m
5
Real-Time Video
0.06 Mbps w/o video
UAV
originated
100 ms
-
Urban, rural, countryside
6
Video streaming
4 Mbps for 720p video
9 Mbps for 1080p video
UAV
originated
100 ms
-
Urban, rural, countryside
7
Periodic still photos
1Mbps
UAV
originated
1S
0.1m
<120m
-
Urban, rural area
1s
<120 m
Urban, rural, countryside
NOTE 1: The flight average speed is 60km/h. The KPI is referring to [5].
NOTE 2: The latency is the time of the 5G system provide higher accuracy location information of a UAV to a third party.
NOTE 3: Referring to clause 5.2.2, the absolute flying speed of UAV in this service can be up to 160km/h.
NOTE 4: The density of active UAV is 10/200km2. The maximum altitude is 300m. The flight average speed is 60km/h. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.2 KPIs for UAV command and control | UAVs may use a variety of flight command and control modes. Command and control (C2) communications refers to the two-way communication, which may include video, required to control the operation of the UAV itself. C2 messages may be communicated with the UAV controller, the UTM or both and may or may not be periodic. UAV controller and UTM communications may happen at essentially the same time with different required QoS. Any mission specific communication (e.g. HD video for area surveillance), if required, is additional. Different modes of control and their typical KPIs are listed in this clause below. The 5G system shall support UAV operation at altitudes of at least 120m / 400ft above ground level, e.g. the services should be provided and characterized up to 3000ft AGL.
Table 7.2-1 KPIs for command and control of UAV operation
Control Mode
Function
Typical Message Interval
Max UAV ground speed
Typical message Size
(note 1)
End to end Latency
Reliability
(note 2)
Positive ACK
(note 8)
Steer to waypoints (note 3)
UAV terminated C2 message
>=1 s
300 km/h
100 byte
1 s
99.9%
Required
UAV originated C2 message
(note 4)
1 s
84-140 byte
1 s
99.9%
Not Required
Direct stick steering
(note 5)
UAV terminated C2 message
40 ms
(note 6)
60km/h
24 byte
40 ms
99.9%
Required
UAV originated C2 message
(note 7)
40 ms
84-140 byte
40 ms
99.9%
Not Required
Automatic flight on UTM
(note 10)
UAV terminated C2 message
1 s
300 km/h
<10 kbyte
5 s (note 9)
99.9%
Required
UAV originated C2 message
1 s
(note 9)
1500 byte
5 s
(note 9)
99.9%
Required
Approaching Autonomous Navigation Infrastructure
UAV terminated C2 message
500 ms
50 km/h
4 kbyte
10 ms
99%
Required
UAVoriginated C2 message
500 ms
4 kbyte
140 ms
99.99%
Required
NOTE 1: Message size is at the application layer and excludes any headers and security related load. The numbers shown are typical as message size depends on the commands sent and is implementation specific.
NOTE 2: Message reliability is defined as the probability of successful transmission within the required latency at the application layer while under network coverage.
NOTE 3: Video is neither required nor expected to be used for steering in this mode.
NOTE 4: It may be possible to transmit this message on an event driven basis (e.g. approaching a geo fence). A status message may, but is not required to, be sent as a response to a control message.
NOTE 5: A video feedback is required for this mode. The KPIs for video are defined in table 7.2-2.
NOTE 6: UAVs on-board controllers typically update at either 50Hz (20ms) or 25Hz (40ms).
NOTE 7: A status message may, but is not required to, be sent as a response to a control message A 1Hz slow mode also exists.
NOTE 8: Positive ACK is sent to the originator of the message (i.e. UAV controller and / or the UTM). The 5G system makes no assumption whether an appropriate ACK is sent by the application layer.
NOTE 9: At the application layer, the C2 communication between a UAV and UTM can be allowed to experience much longer traffic interruptions, e.g. timeouts of 30 s on the uplink and 300 s on the downlink.
NOTE 10: This only represents periodic message exchange during a nominal mission in steady state. Itdoes not represent unusual or aperiodic events such as conveying dynamic restrictions or a flight plan to the UAV on the downlink.
Table 7.2-2 KPIs for video used to aid UAV control.
Scenario
(note 2)
Data rate
End to end Latency
Reliability
(note 1)
Direction
Positive ACK required
VLOS (visual line of sight)
2 Mpbs at 480 p, 30 fps
1 s
99.9%
Sent by UAV
Not Required
Non-VLOS
4 Mbps at 720 p, 30 fps
140 ms
99.99%
Sent by UAV
Not Required
NOTE 1: Message reliability is defined as the probability of successful transmission within the required latency.
NOTE 2: Maximum UAV speed is same as control mode of direct stick steering in 7.2-1 |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.3 Positioning performance requirements | Table 7.3-1 below lists typical scenarios and the corresponding positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
NOTE: The column on "Corresponding Positioning Service Level in TS 22.261" maps the scenarios listed in Table 7.3-1 to the service levels defined in TS 22.261 [4].
Table 7.3-1: Positioning performance requirements
Scenario
Accuracy
(95 % confidence level)
Availability
Heading
Latency for position estimation of UE
UE Speed
Corresponding Positioning Service Level in TS 22.261
Horizontal accuracy
Vertical accuracy
8K video live broadcast
[0.5 m]
[1 m]
99%
1s
[<120 km/h]
5
Laser mapping/
HD patrol
[0.5 m]
[1 m]
99%
1s
[<120 km/h]
5
4*4K AI surveillance
[0.1 m]
[<60
km/h]
Remote UAV controller through HD video
[0.5 m]
[1 m]
99%
1s
[<120 km/h]
5
Periodic still photos
[0.1 m]
[1 m]
[<60 km/h]
NOTE: The positioning accuracy in this table is not related to navigation or safety. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.4 Other requirements | [R-7.4-001] The 5G system shall support a mechanism to switch between C2 communication modes for UAS operation, e.g. from indirect C2 communication to direct C2 communication, and ensure the disconnect time is below the latency requirements. [R-7.4-002] The 3GPP system shall enable concurrent communications between the UAV-controller and UAV and between the UTM and the UAV that may require different KPIs. [R-7.4-003] The 3GPP system shall be capable of switching between the KPIs, as requested by the UAV-controller or the UTM, within [500ms]. Annex A (informative): UAS Reference Model A.1 UAS Reference Model in 3GPP ecosystem Figure B.1-1: UAS model in 3GPP ecosystem. In the UAS reference model: - a UAS is composed of one UAV and one UAV controller in this illustration - UAVs are connected over cellular connectivity - a UAV can be controlled by a UAV controller connected via the 3GPP mobile network - a UAV can be controlled by a UAV controller not connected via the 3GPP mobile network, using a C2 interface not in 3GPP scope - a UAV controller connected via the 3GPP mobile network can control one or more UAV(s) - the UAS exchanges application data traffic with a UTM NOTE: Several types of UAV controllers exist, e.g. hand-held UAV controllers, PCs/WSs and automated or manual functions that are part of the UTM. The mechanisms to ensure which UAV controller is active and controlling the UAV is out of scope of 3GPP. Annex B (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 24/08/2018 SA1#83 S1-182766 - - - Skeleton created 0.1.0 16/11/2018 SA1#84 S1-183278 - - - TS22.125 v0.2.0 created to include agreements at this meeting 0.2.0 2018-12 SA#82 SP-181009 - - - Presentation for one-step approval to SA 1.0.0 2018-12 SA#82 SP-181009 - - - Raised to v.16.0.0 following SA#82’s one step approval 16.0.0 2019-03 SA#83 SP-190083 0001 2 C Removal of requirement on enforcement 16.1.0 2019-03 SA#83 SP-190083 0005 1 F Detect and report the problematic UAV controller to UTM 16.1.0 2019-03 SA#83 SP-190083 0009 1 F Clarification for identity of UAV controller data 16.1.0 2019-03 SA#83 SP-190083 0008 1 B Addition for Abbreviations 16.1.0 2019-03 SA#83 SP-190083 0003 3 F Clarification of Centralized UTM 16.1.0 2019-03 SA#83 SP-190083 0004 3 F Clarification of Decentralized UTM for Collision Avoidance 16.1.0 2019-03 SA#83 SP-190083 0002 2 F Clarification of UTM Definition 16.1.0 2019-03 SA#83 SP-190083 0006 3 B Definition and Clarification for UTM 16.1.0 2019-06 SA#84 SP-190300 0010 3 F Rewording the enforcement requirement in section 5.2 16.2.0 2019-09 SA#85 SP-190801 0021 2 F Clarifications on UAS terminology and model 16.3.0 2019-09 SA#85 SP-190809 0017 2 B Definition and introduction of C2 Communication 17.0.0 2019-09 SA#85 SP-190809 0018 2 B CR to 22.125 Network exposure requirements for UAV 17.0.0 2019-09 SA#85 SP-190809 0013 2 B Adding UxNB related requirements 17.0.0 2019-09 SA#85 SP-190809 0020 2 B Service restriction requirements for UAV 17.0.0 2019-09 SA#85 SP-190801 0024 2 F Corrections to Requirements 17.0.0 2019-12 SA#86 SP-191024 0026 2 B KPIs for UAV services 17.1.0 2019-12 SA#86 SP-191024 0027 3 F Clarification of Control Modes in C2 communication 17.1.0 2020-09 SA#89e SP-200881 0028 5 F Clarification of the definition of a UAS 17.2.0 2021-03 SA#91e SP-210197 0034 1 F Clarification of problematic UAV 17.3.0 2021-09 SA#93e SP-211034 0036 1 D UAS terminology alignment 17.4.0 2021-12 SP-94 SP-211491 0038 1 D CR Editorial to T22.125 clause 6.4 and clause 7.1 17.5.0 2021-12 SP-94 SP-211491 0039 1 D CR inclusive language correction to T22.125 clause 1 17.5.0 2021-12 SP-94 SP-211491 0040 1 C CR to T22.125 for correction and readability improvement clause 4.2 and clause 17.5.0 2021-12 SP-94 SP-211491 0041 2 C Addition of a note to [R-5.1-017] related to the applicability of the requirement 17.5.0 2022-03 SP#95e SP-220078 0043 1 D Editorial corrections to TS 22.125 on UAV 17.6.0 2023-09 SA#101 Identical to v.17.6.0 18.0.0 2023-09 SA#101 SP-231034 0047 7 B Additional requirements for UAS 19.0.0 2023-12 SA#102 SP-231410 0050 1 F Move requirement from UAV safety to flight path and zones management 19.1.0 2023-12 SA#102 SP-231410 0049 2 B Additional Requirements for Remote Identification of UAS and UTM assistance requirements 19.1.0 2024-06 SA#104 SP-240788 0052 4 F Alignment of terminology for requirements 19.2.0 2024-06 SA#104 SP-240788 0055 1 F Permanent alignment between stage 1 and stages 2/3 for UAS 19.2.0 |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 1 Scope | The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
The present document is applicable to:
- the interface between the User Equipment (UE) and the Call Session Control Function (CSCF);
- the interface between the CSCF and any other CSCF;
- the interface between the CSCF and an Application Server (AS);
- the interface between the CSCF and an ISC gateway function;
- the interface between the ISC gateway function and an Application Server (AS);
- the interface between the CSCF and the Media Gateway Control Function (MGCF);
- the interface between the S-CSCF and the Multimedia Resource Function Controller (MRFC);
- the interface between the Application Server (AS) and the Multimedia Resource Function Controller (MRFC);
- the interface between the S-CSCF and the Media Resource Broker (MRB);
- the interface between the AS and the MRB;
- the interface between the MRB and the MRFC;
- the interface between the CSCF and the Breakout Gateway Control Function (BGCF);
- the interface between the BGCF and the MGCF;
- the interface between the CSCF and an IBCF;
- the interface between the IBCF and AS, MRFC or MRB;
- the interface between the E-CSCF and the Location Retrieval Function (LRF);
- the interface between the BGCF and any other BGCF;
- the interface between the CSCF and an external Multimedia IP network;
- the interface between the E-CSCF and the EATF;
- the interface between the E-CSCF and the terminating IMS network;
- the interface between the P-CSCF and the ATCF;
- the interface between the ATCF and the I-CSCF;
- the interface between the ATCF and the IBCF; and
- the interface between the transit function and the AS.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
As the IM CN subsystem is designed to interwork with different IP-Connectivity Access Networks (IP-CANs), the IP-CAN independent aspects of the IM CN subsystem are described in the main body and annex A of this specification. Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in the annexes or in separate documents.
The document also specificies:
- HTTP for use by an AS and by an MRB in support of the provision of media resources; and
- HTTP for use by an IBCF and by an AS in support of the invocation of attestation and verification functions.
The document also specifies media-related requirements for the NAT traversal mechanisms defined in this specification.
NOTE: The present document covers only the usage of SIP and SDP to communicate with the enitities of the IM CN subsystem. It is possible, and not precluded, to use the capabilities of IP-CAN to allow a terminal containing a SIP UA to communicate with SIP servers or SIP UAs outside the IM CN subsystem, and therefore utilise the services provided by those SIP servers. The usage of SIP and SDP for communicating with SIP servers or SIP UAs outside the IM CN subsystem is outside the scope of the present document. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 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".
[1A] 3GPP TS 22.101: "Service aspects; Service principles".
[1B] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[1C] 3GPP TS 22.011: "Service accessibility".
[2] 3GPP TS 23.002: "Network architecture".
[3] 3GPP TS 23.003: "Numbering, addressing and identification".
[4] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[4A] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
[4B] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[4C] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[4D] 3GPP TS 23.140 Release 6: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[5] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model".
[6] 3GPP TS 23.221: "Architectural requirements".
[7] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".
[7A] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description".
[7B] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".
[7C] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".
[7D] 3GPP TS 23.380: "IMS Restoration Procedures".
[7E] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[7F] 3GPP TS 23.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface".
[7G] 3GPP TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3".
[8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3".
[8A] 3GPP TS 24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8B] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8C] 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3".
[8D] Void.
[8E] 3GPP TS 24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, stage 3, Release 7".
[8F] 3GPP TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8G] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".
[8H] 3GPP TS 24.173: "IMS Multimedia telephony communication service and supplementary services; Stage 3".
[8I] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8J] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[8K] 3GPP TS 24.323: "3GPP IMS service level tracing management object (MO)".
[8L] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3".
[8M] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[8N] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[8O] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3".
[8P] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[8Q] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification".
[8R] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification".
[8S] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem".
[8T] 3GPP TS 24.305: "Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO)".
[8U] 3GPP TS 24.302: "Access to the Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3".
[8V] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6".
[8W] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS".
[8X] 3GPP TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3".
[8Y] 3GPP TS 24.322: "UE access to IMS services via restrictive access networks - stage 3".
[8Z] 3GPP TS 24.371: "Web Real Time Communication (WebRTC) Access to IMS".
[8ZA] 3GPP TS 24.525: "Business trunking; Architecture and functional description".
[8ZB] 3GPP TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3".
[8ZC] 3GPP TS 24.337: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3".
[8ZD] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[8ZE] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Stage 3".
[8ZF] 3GPP TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8ZG] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8ZH] 3GPP TS 24.174: "Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3".
[8ZI] 3GPP TS 24.554: "Proximity-service (ProSe) in 5G System (5GS) protocol aspects; Stage 3"
[9] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[9A] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification".
[9B] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[9C] 3GPP TS 26.267: "eCall Data Transfer; In-band modem solution; General description".
[10] Void.
[10A] 3GPP TS 27.060: "Mobile Station (MS) supporting Packet Switched Services".
[11] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)".
[11A] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks".
[11B] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks".
[11C] 3GPP TS 29.161: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services with Wireless Local Access and Packet Data Networks (PDN)"
[11D] 3GPP TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem".
[12] 3GPP TS 29.207 Release 6: "Policy control over Go interface".
[12A] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[13] Void.
[13A] 3GPP TS 29.209 Release 6: "Policy control over Gq interface".
[13B] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[13C] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
[13D] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[14] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
[15] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol, Protocol details".
[15A] 3GPP TS 29.311: "Service Level Interworking for Messaging Services".
[15B] 3GPP TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[15C] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[15D] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".
[16] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[17] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[17A] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[18] 3GPP TS 33.102: "3G Security; Security architecture".
[19] 3GPP TS 33.203: "Access security for IP based services".
[19A] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[19B] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[19C] 3GPP TS 33.328: "IP Multimedia Subsystem (IMS) media plane security".
[19D] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[19E] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[19F] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[19G] 3GPP TS 38.331: " NR; Radio Resource Control (RRC); Protocol specification".
[20] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".
[20A] IETF RFC 2401 (November 1998): "Security Architecture for the Internet Protocol".
[20B] IETF RFC 1594 (March 1994): "FYI on Questions and Answers to Commonly asked "New Internet User" Questions".
[20C] Void.
[20D] Void.
[20E] IETF RFC 2462 (November 1998): "IPv6 Stateless Address Autoconfiguration".
[20F] IETF RFC 2132 (March 1997): "DHCP Options and BOOTP Vendor Extensions".
[20G] IETF RFC 2234 (November 1997): "Augmented BNF for Syntax Specification: ABNF".
[21] Void.
[22] IETF RFC 3966 (December 2004): "The tel URI for Telephone Numbers".
[23] IETF RFC 4733 (December 2006): "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals".
[24] IETF RFC 6116 (March 2011): "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)".
[25] IETF RFC 6086 (October 2009): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[25A] Void.
[26] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol".
[27] IETF RFC 3262 (June 2002): "Reliability of provisional responses in Session Initiation Protocol (SIP)".
[27A] IETF RFC 3263 (June 2002): "Session Initiation Protocol (SIP): Locating SIP Servers".
[27B] IETF RFC 3264 (June 2002): "An Offer/Answer Model with Session Description Protocol (SDP)".
[28] IETF RFC 6665 (July 2012): "SIP Specific Event Notification".
[28A] Void.
[29] IETF RFC 3311 (September 2002): "The Session Initiation Protocol (SIP) UPDATE method".
[30] IETF RFC 3312 (October 2002): "Integration of resource management and Session Initiation Protocol (SIP)".
[31] IETF RFC 3313 (January 2003): "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
[32] IETF RFC 3320 (March 2002): "Signaling Compression (SigComp)".
[33] IETF RFC 3323 (November 2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[34] IETF RFC 3325 (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[34A] IETF RFC 3326 (December 2002): "The Reason Header Field for the Session Initiation Protocol (SIP)".
[35] IETF RFC 3327 (December 2002): "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
[35A] IETF RFC 3361 (August 2002): "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers".
[36] IETF RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) REFER method".
[37] IETF RFC 3420 (November 2002): "Internet Media Type message/sipfrag".
[37A] IETF RFC 3605 (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)".
[38] IETF RFC 3608 (October 2003): "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
[39] IETF RFC 4566 (June 2006): "SDP: Session Description Protocol".
[40] IETF RFC 3315 (July 2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[40A] IETF RFC 2131 (March 1997): "Dynamic host configuration protocol".
[41] IETF RFC 3319 (July 2003): "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers".
[42] IETF RFC 3485 (February 2003): "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) static dictionary for Signaling Compression (SigComp)".
[43] IETF RFC 3680 (March 2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
[44] Void.
[45] Void.
[46] Void.
[47] Void.
[48] IETF RFC 3329 (January 2003): "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
[49] IETF RFC 3310 (September 2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".
[50] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[51] Void.
[52] IETF RFC 7315 (July 2014): "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP".
[52A] IETF RFC 7976 (September 2016): "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses".
[52B] draft-ietf-sipcore-rfc7976bis-00 (August 2024): "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses".
Editor's note (WI: IMSProtoc9, CR#5979): The above document cannot be formally referenced until it is published as an IETF RFC.
[53] IETF RFC 3388 (December 2002): "Grouping of Media Lines in Session Description Protocol".
[54] IETF RFC 3524 (April 2003): "Mapping of Media Streams to Resource Reservation Flows".
[55] IETF RFC 3486 (February 2003): "Compressing the Session Initiation Protocol (SIP)".
[55A] IETF RFC 3551 (July 2003): "RTP Profile for Audio and Video Conferences with Minimal Control".
[56] IETF RFC 3556 (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".
[56A] IETF RFC 3581 (August 2003): "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing".
[56B] IETF RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[56C] IETF RFC 3646 (December 2003): "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[57] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
[58] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[59] IETF RFC 3892 (September 2004): "The Session Initiation Protocol (SIP) Referred-By Mechanism".
[60] IETF RFC 3891 (September 2004): "The Session Inititation Protocol (SIP) "Replaces" Header".
[61] IETF RFC 3911 (October 2004): "The Session Inititation Protocol (SIP) "Join" Header".
[62] IETF RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[63] IETF RFC 3861 (August 2004): "Address Resolution for Instant Messaging and Presence".
[63A] IETF RFC 3948 (January 2005): "UDP Encapsulation of IPsec ESP Packets".
[64] IETF RFC 4032 (March 2005): "Update to the Session Initiation Protocol (SIP) Preconditions Framework".
[65] IETF RFC 3842 (August 2004) "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)"
[65A] IETF RFC 4077 (May 2005): "A Negative Acknowledgement Mechanism for Signaling Compression".
[66] IETF RFC 7044 (February 2014): "An Extension to the Session Initiation Protocol (SIP) for Request History Information".
[67] IETF RFC 5079 (December 2007): "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)".
[68] IETF RFC 4458 (January 2006): "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)".
[69] IETF RFC 5031 (January 2008): "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services".
[70] IETF RFC 3903 (October 2004): "An Event State Publication Extension to the Session Initiation Protocol (SIP)".
[71] Void.
[72] IETF RFC 3857 (August 2004): "A Watcher Information Event Template Package for the Session Initiation Protocol (SIP)".
[74] IETF RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[74A] IETF RFC 3603 (October 2003): "Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture".
[74B] IETF RFC 3959 (December 2004): "The Early Session Disposition Type for the Session Initiation Protocol (SIP)".
[75] IETF RFC 4662 (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".
[77] IETF RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[78] IETF RFC 4575 (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[79] IETF RFC 5049 (December 2007): "Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)".
[80] Void.
[81] Void.
[82] IETF RFC 4457 (April 2006): "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)".
[83] IETF RFC 4145 (September 2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)".
[84] IETF RFC 4320 (January 2006): "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction".
[85] 3GPP2 C.S0005-D (March 2004): "Upper Layer (Layer 3) Signaling Standard for cdma2000 Standards for Spread Spectrum Systems".
[86] 3GPP2 C.S0024-B v3.0 (September 2009): "cdma2000 High Rate Packet Data Air Interface Standard".
[86A] 3GPP2 C.S0084-000 (April 2007): "Overview for Ultra Mobile Broadband (UMB) Air Interface Specification".
[86B] 3GPP2 X.S0060-0 v1.0: "HRPD Support for Emergency Services".
[86C] 3GPP2 X.S0057-B v2.0: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[86D] 3GPP2 C.S0014-C v1.0: "Enhanced Variable Rate Codec, Speech Service Options 3, 68, and 70 for Wideband Spread Spectrum Digital Systems".
[86E] 3GPP2 X.S0059-200-A v1.0: "cdma2000 Femtocell Network: 1x and IMS Network Aspects".
[86F] 3GPP2 S.R0048-A v4.0: "3G Mobile Equipment Identifier (MEID) - Stage 1".
[87] Recommendation ITU-T J.112, "Transmission Systems for Interactive Cable Television Services"
[88] PacketCable Release 2 Technical Report, PacketCable™ Architecture Framework Technical Report, PKT-TR-ARCH-FRM.
[89] IETF RFC 6442 (December 2011): "Location Conveyance for the Session Initiation Protocol".
[90] IETF RFC 4119 (December 2005) "A Presence-based GEOPRIV Location Object Format".
[91] IETF RFC 5012 (January 2008): "Requirements for Emergency Context Resolution with Internet Technologies".
[91A] Void.
[92] IETF RFC 5626 (October 2009): "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)".
[93] IETF RFC 5627 (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".
[94] IETF RFC 5628 (October 2009): "Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs)".
[95] Void.
[96] IETF RFC 4168 (October 2005): "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)".
[97] IETF RFC 5002 (August 2007): "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)".
[98] ETSI ES 283 035 (V1.1.1): "Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol".
[99] Void.
[100] Void.
[101] Void.
[102] IETF RFC 5768 (April 2010): "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)".
[103] IETF RFC 4967 (July 2007): "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier".
[104] IETF RFC 5365 (October 2008): "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)".
[105] IETF RFC 5368 (October 2008): "Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[106] IETF RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[107] IETF RFC 5367 (October 2008): "Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)".
[108] IETF RFC 4583 (November 2006): "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams".
[109] IETF RFC 5009 (September 2007): "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media".
[110] IETF RFC 4354 (January 2006): "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service".
[111] IETF RFC 4964 (September 2007): "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular".
[112] IETF RFC 4694 (October 2006): "Number Portability Parameters for the 'tel' URI".
[113] Void.
[114] IETF RFC 4769 (November 2006): "IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information".
[115] IETF RFC 4411 (February 2006): "Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events".
[116] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[117] IETF RFC 5393 (December 2008): "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies".
[118] IETF RFC 4896 (June 2007): "Signaling Compression (SigComp) Corrections and ClarificationsImplementer's Guide for SigComp".
[119] IETF RFC 5112 (January 2008): "The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)".
[120] IETF RFC 5688 (January 2010): "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtype".
[121] IETF RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[122] Void.
[123] Void.
[124] IETF RFC 3986 (January 2005): "Uniform Resource Identifiers (URI): Generic Syntax".
[125] IETF RFC 5360 (October 2008): "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)".
[126] IETF RFC 7433 (January 2015): "A Mechanism for Transporting User-to-User Call Control Information in SIP".
[126A] IETF RFC 7434 (January 2015): "Interworking ISDN Call Control User Information with SIP".
[127] 3GPP2 X.S0011-E: "cdma2000 Wireless IP Network Standard ".
[130] IETF RFC 6432 (November 2011): "Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses".
[131] IETF RFC 6544 (March 2012): "TCP Candidates with Interactive Connectivity Establishment (ICE)".
[132] IETF RFC 3023 (January 2001): "XML Media Types".
[133] IETF RFC 5502 (April 2009): "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem".
[134] IETF RFC 7316 (July 2014): "The Session Initiation Protocol (SIP) P-Private-Network-Indication PrivateHeader (P-Header)".
[135] IETF RFC 4585 (July 2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)".
[136] IETF RFC 5104 (February 2008): "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)".
[137] IETF RFC 5939 (September 2010): "Session Description Protocol (SDP) Capability Negotiation".
[138] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1".
[139] Void.
[140] IETF RFC 8497 (November 2018): "Marking SIP Messages to Be Logged".
[141] Void.
[142] IETF RFC 6228 (May 2011): "Response Code for Indication of Terminated Dialog".
[143] IETF RFC 6223 (April 2011): "Indication of support for keep-alive".
[144] IETF RFC 4240 (December 2005): "Basic Network Media Services with SIP".
[145] IETF RFC 5552 (May 2009): "SIP Interface to VoiceXML Media Services".
[146] IETF RFC 6230 (May 2011): "Media Control Channel Framework".
[147] IETF RFC 6231 (May 2011): "An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework".
[148] IETF RFC 6505 (March 2012): "A Mixer Control Package for the Media Control Channel Framework".
[149] IETF RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[150] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)".
[151] IETF RFC 3862 (August 2004): "Common Presence and Instant Messaging (CPIM): Message Format".
[152] IETF RFC 3890 (September 2004): "A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)".
[153] IETF RFC 7254 (May 2014): "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)".
[154] IETF RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[155] IETF RFC 7195 (May 2014): "Session Description Protocol (SDP) Extension for Setting Audio Media Streams over Circuit-Switched Bearers in the Public Switched Telephone Network (PSTN)".
[156] IETF RFC 7006 (September 2013): "Miscellaneous Capabilities Negotiation in the Session Description Protocol (SDP)".
[157] IETF RFC 5438 (January 2009): "Instant Message Disposition Notification (IMDN)".
[158] IETF RFC 5373 (November 2008): "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[160] Void.
[161] IETF RFC 4288 (December 2005): "Media Type Specifications and Registration Procedures".
[162] IETF RFC 7989 (October 2016): "End-to-End Session Identification in IP-Based Multimedia Communication Networks".
[163] IETF RFC 6026 (September 2010): "Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests".
[164] IETF RFC 5658 (October 2009): "Addressing Record-Route issues in the Session Initiation Protocol (SIP)".
[165] IETF RFC 5954 (August 2010): "Essential Correction for IPv6 ABNF and URI Comparison in IETF RFC3261".
[166] IETF RFC 4117 (June 2005): "Transcoding Services Invocation in the Session Initiation Protocol (SIP) using Third Party Call Control (3pcc)".
[167] IETF RFC 4567 (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[168] IETF RFC 4568 (July 2006): "Session Description Protocol (SDP) Security Descriptions for Media Streams".
[169] IETF RFC 3711 (March 2004): "The Secure Real-time Transport Protocol (SRTP)".
[170] IETF RFC 6043 (March 2011): "MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)".
[171] IETF RFC 4235 (November 2005): "An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)".
[172] IETF RFC 6871 (February 2013): "SDP media capabilities Negotiation".
[173] IETF RFC 4488 (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[174] Void.
[175] IETF RFC 7462 (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[176] ANSI/J-STD-036-B: "Enhanced Wireless 9-1-1, Phase 2".
[177] Void.
[178] IETF RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)".
[179] IETF RFC 3859 (August 2004): "Common Profile for Presence (CPP)".
[180] IETF RFC 3860 (August 2004): "Common Profile for Instant Messaging (CPIM)".
[181] IETF RFC 2368 (July 1998): "The mailto URL scheme".
[182] IETF RFC 4745 (February 2007): "Common Policy: A Document Format for Expressing Privacy Preferences".
[183] IETF RFC 5318 (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[184] IETF RFC 4538 (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[185] IETF RFC 5547 (May 2009): "A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer".
[186] IETF RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".
[187] IETF RFC 8464 (September 2018): "A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)".
[188] IETF RFC 6679 (August 2012): "Explicit Congestion Notification (ECN) for RTP over UDP".
[189] IETF RFC 3168 (September 2001): "The Addition of Explicit Congestion Notification (ECN) to IP".
[190] IETF RFC 6809 (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[191] IETF RFC 6140 (March 2011): "Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)".
[192] IETF RFC 6917 (April 2013): "Media Resource Brokering".
[193] ETSI TS 101 454-1 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 1: Overview and System Level specification".
[194] ETSI EN 301 545-2 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 2: Lower Layers for Satellite standard".
[195] ETSI TS 101 545-3 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 3: Higher Layers Satellite Specification".
[196] Void.
[197] IETF RFC 7135 (May 2014): "IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications".
[198] IETF RFC 6357 (August 2011): "Design Considerations for Session Initiation Protocol (SIP) Overload Control".
[199] IETF RFC 7339 (September 2014): "Session Initiation Protocol (SIP) Overload Control".
[200] IETF RFC 7415 (February 2015): "Session Initiation Protocol (SIP) Rate Control".
[201] IETF RFC 7200 (April 2014): "A Session Initiation Protocol (SIP) Load-Control Event Package".
[202] Recommendation ITU-T T.38 (September 2010): "Procedures for real-time Group 3 facsimile communication over IP networks".
[203] ISO 8601 (December 2004): "Date elements and interchange formats – Information interchange – Representation of dates and times".
[204] IETF RFC 5506 (April 2009): "Support for Reduced-Size Real-Time Transport Control Protocol (RTCP)".
[205] IETF RFC 3611 (November 2003): "RTP Control Protocol Extended Reports (RTCP XR)".
[206] IETF RFC 4796 (February 2007): "The Session Description Protocol (SDP) Content Attribute".
[207] ISO 3166-1 (2006): "Codes for the representation of names of countries and their subdivisions – Part 1: Country codes".
[208] IETF RFC 8055 (January 2017): "Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm".
[209] IETF RFC 7090 (April 2014): "Public Safety Answering Point (PSAP) Callback".
[210] IETF RFC 5285 (July 2008): "A General Mechanism for RTP Header Extensions".
[211] IETF RFC 6236 (May 2011): "Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)".
[212] IETF RFC 20 (May 2011): "ASCII format for Network Interchange".
[213] IETF RFC 5280 (May 2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
[214] IETF RFC 6714 (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)".
[215] IETF RFC 6135 (February 2011): "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)".
[216] Void.
[217] IETF RFC 7345 (August 2014): "UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)".
[218] IETF RFC 4279 (December 2005): "Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)".
[219] IETF RFC 8841 (January 2021): "Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport".
[220] IETF RFC 2817 (May 2000): "Upgrading to TLS Within HTTP/1.1".
[221] IETF RFC 6062 (November 2010): "Using Relays around NAT (TURN) Extensions for TCP Allocations".
[222] IETF RFC 5763 (May 2010): "Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)".
[223] IETF RFC 5764 (May 2010): " Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)".
[224] IETF RFC 7675 (October 2015): "STUN Usage for Consent Freshness".
[225] IETF RFC 7549 (May 2015): "3GPP SIP URI Inter Operator Traffic Leg Parameter".
[226] Void.
[227] IETF RFC 4169 (November 2005): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2".
[228] IETF RFC 6947 (May 2013): "The Session Description Protocol (SDP) Alternate Connectivity (ALTC) Attribute".
[229] Void.
[230] IETF RFC 8119 (March 2017): "SIP "cause" URI Parameter for Service Number Translation".
[231] IETF RFC 7647 (September 2015): "Clarifications for the Use of REFER with RFC6665".
[232] IETF RFC 7614 (August 2015): "Explicit Subscriptions for the REFER Method".
[233] IETF RFC 7621 (August 2015): "A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework".
[234] IETF RFC 7913 (June 2016): "P-Access-Network-Info ABNF Update".
[235] IETF RFC 7519 (May 2015): "JSON Web Token (JWT)".
[236] Void.
[237] IETF RFC 5761 (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".
[237A] IETF RFC 8035 (November 2016): "Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing".
[238] IETF RFC 8864 (January 2021): " Negotiation Data Channels Using the Session Description Protocol (SDP)".
[239] IETF RFC 8498 (February 2019): "A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)".
[240] IETF RFC 8842 (January 2021): "Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)".
[241] IETF RFC 8122 (March 2017): "Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)".
[242] IETF RFC 3863 (August 2004): "Presence Information Data Format".
[243] IETF RFC 4661 (September 2006): "An Extensible Markup Language (XML) Based Format for Event Notification Filtering".
[244] IETF RFC 8147 (May 2017): "Next-Generation Pan-European eCall".
[245] CEN EN 15722:2020 (August 2020): "Intelligent transport systems - ESafety - ECall minimum set of data".
[246] IETF RFC 8858 (January 2021): "Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)".
[247] IETF RFC 7303 (July 2014): "XML Media Types".
[248] IEEE Std 802.11-2016: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[249] IETF RFC 8853 (January 2021): "Using Simulcast in Session Description Protocol (SDP) and RTP Sessions".
[250] IETF RFC 8851 (January 2021): "RTP Payload Format Restrictions".
[251] IETF RFC 7728 (February 2016): "RTP Stream Pause and Resume".
[252] IETF RFC 8224 (February 2018): "Authenticated Identity Management in the Session Initiation Protocol (SIP)".
[253] IETF RFC 5279 (July 2008): "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)".
[254] IETF RFC 8197 (July 2017): "A SIP Response Code for Unwanted Calls".
[255] IETF RFC 8606 (June 2019): "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field".
[256] IETF RFC 8262 (October 2017): "Content-ID Header Field in the Session Initiation Protocol (SIP)".
[257] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[258] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (5GS); Stage 3".
[259] IETF RFC 4715 (November 2006): "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI".
[260] 3GPP TS 38.304: " NR; User Equipment (UE) procedures in idle mode and in RRC Inactive state".
[261] IETF RFC 8588 (May 2019): "Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)".
[262] IETF RFC 8225 (February 2018): "PASSporT: Personal Assertion Token"
[263] 3GPP TS 24.502: " Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3".
[264] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
[265] IETF RFC 8946 (February 2021): "Personal Assertion Token (PASSporT) Extension for Diverted Calls".
[266] IETF RFC 8787 (May 2020): "Location Source Parameter for the SIP Geolocation Header Field".
[267] IETF RFC 5491 (March 2009): "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations".
[268] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[269] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[270] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[271] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[272] 3GPP TS 23.221: "Architectural requirements".
[273] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[274] 3GPP TS 29.562: "Home Subscriber Server (HSS) Services for Interworking with the IP Multimedia Subsystem (IMS); Stage 3".
[275] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[276] 3GPP TS 26.238: "Uplink Streaming".
[277] IETF RFC 4574 (August 2006): "The Session Description Protocol (SDP) Label Attribute".
[278] IETF RFC 9027 (June 2021): "Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services Networks".
[279] IETF RFC 8443 (August 2018): "Personal Assertion Token (PASSporT) Extension for Resource Priority Authorization".
[280] IETF RFC 9112 (June 2022): "HTTP/1.1".
[281] IETF RFC 9110 (June 2022): "HTTP Semantics".
[282] Void.
[283] Void.
[284] IETF RFC 9111 (June 2022): "HTTP Caching".
[285] Void.
[286] IETF RFC 7616 (September 2015): "HTTP Digest Access Authentication".
[287] IETF RFC 8760 (March 2020): "The Session Initiation Protocol (SIP) Digest Access Authentication Scheme".
[288] 3GPP TS 29.510: "5G System; Network function repository services; Stage 3".
[289] IETF RFC 8445 (July 2018): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal".
[290] IETF RFC 8839 (January 2021): "Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)".
[291] IETF RFC 8489 (February 2020): "Session Traversal Utilities for NAT (STUN)".
[292] IETF RFC 8656 (February 2020): "Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)".
[293] IETF RFC 8981 (February 2021): "Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6".
[294] IETF RFC 9410 (July 2023): "Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)".
[295] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[296] IETF RFC 9366 (March 2023): "Multiple SIP Reason Header Field Values".
[297] 3GPP TS 24.186: "IMS Data Channel applications; Protocol specification".
[298] 3GPP TS 29.176: "IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3".
[299] Void.
[300] CEN EN 17184:2024: “Intelligent transport systems — eSafety — eCall High level application Protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched network”.
[301] 3GPP TS 24.275: "Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service".
[302] draft-ietf-stir-passport-rcd-26 (June 2024): "PASSporT Extension for Rich Call Data".
Editor's note: [WI: NG_RTC_Ph2, CR#6714] The above document cannot be formally referenced until it is published as an IETF RFC.
[303] draft-ietf-sipcore-callinfo-rcd-12 (July 2024): "SIP Call-Info Parameters for Rich Call Data".
Editor's note: [WI: NG_RTC_Ph2, CR#6714] The above document cannot be formally referenced until it is published as an IETF RFC. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3 Definitions of terms, symbols and abbreviations | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.1 Terms | For the purposes of the present document, the following terms apply.
3GPP PS data off status: indicates state of usage of the 3GPP PS data off. 3GPP PS data off status at the UE can be either "active" or "inactive".
Country: For the purposes of emergency service URNs in the present document, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69], an ISO 3166-1 alpha-2 code as specified in ISO 3166-1 [207] is used to identify a region or a country.
Entry point: In the case that "border control concepts", as specified in 3GPP TS 23.228 [7], are to be applied in an IM CN subsystem, then these are to be provided by capabilities within the IBCF, and the IBCF acts as an entry point for this network (instead of the I-CSCF). In this case the IBCF and the I-CSCF can be co-located as a single physical node. If "border control concepts" are not applied, then the I-CSCF is considered as an entry point of a network. If the P-CSCF is in the home network, then the I-CSCF is considered as an entry point for this document. Similary, in case that "border control concepts", as specified in 3GPP TS 23.218 [5], are to be applied in an ISC interface, then these are to be provided by capabilities within the ISC gateway function, and the ISC gateway function acts as an entry point for this network.
Exit point: If operator preference requires the application of "border control concepts" as specified in 3GPP TS 23.228 [7], then these are to be provided by capabilities within the IBCF, and requests sent towards another network are routed via a local network exit point (IBCF), which will then forward the request to the other network (discovering the entry point if necessary). Similary, in case that "border control concepts", as specified in 3GPP TS 23.218 [5], are to be applied in an ISC interface, then these are to be provided by capabilities within the ISC gateway function, and requests sent towards another network are routed via a local network exit point (ISC gateway function).
Geo-local number: Either a geo-local service number as specified in 3GPP TS 23.228 [7] or a number in non-international format according to an addressing plan used at the current physical location of the user.
Home-local number: Either a home local service number as specified in 3GPP TS 23.228 [7] or a number in non-international format according to an addressing plan used in the home network of the user.
Main URI: In the case that the UE supports RFC 6140 [191] and performs the functions of an external attached network, the main URI is the URI which is used for the registration procedures in the To header of the REGISTER request as specified in RFC 6140 [191]; it represents the public user identities associated to that UE.
Newly established set of security associations: Two pairs of IPsec security associations that have been created at the UE and/or the P-CSCF after the 200 (OK) response to a REGISTER request was received.
Old set of security associations: Two pairs of IPsec security associations still in existence after another set of security associations has been established due to a successful authentication procedure.
Temporary set of security associations: Two pairs of IPsec security associations that have been created at the UE and/or the P-CSCF, after an authentication challenge within a 401 (Unauthorized) response to a REGISTER request was received. The SIP level lifetime of such created security associations will be equal to the value of reg-await-auth timer.
Integrity protected: See 3GPP TS 33.203 [19]. Where a requirement exists to send information "integrity-protected" the mechanisms specified in 3GPP TS 33.203 [19] are used for sending the information. Where a requirement exists to check that information was received "integrity-protected", then the information received is checked for compliance with the procedures as specified in 3GPP TS 33.203 [19].
Instance ID: An URN generated by the device that uniquely identifies a specific device amongst all other devices, and does not contain any information pertaining to the user (e.g., in GPRS instance ID applies to the Mobile Equipment rather than the UICC). The public user identity together with the instance ID uniquely identifies a specific UA instance. If the device has an IMEI available, it generates an instance ID based on its IMEI as defined in 3GPP TS 23.003 [3] clause 13. If the device has an MEID as defined in 3GPP2 S.R0048-A [86F] available, it generates an instance ID based on its MEID as defined in RFC 8464 [187]. If the device does not have an IMEI available and does not have an MEID available, the instance ID is generated as a string representation of a UUID as a URN as defined in RFC 4122 [154].
Resource reservation: Mechanism for reserving bearer resources that is required for certain access technologies.
Local preconditions: The indication of segmented status preconditions for the local reservation of resources as specified in RFC 3312 [30].
Alias URI, Alias SIP URI: A URI is an alias of another URI if the treatment of both URIs is identical, i.e. both URIs belong to the same set of implicitly registered public user identities, and are linked to the same service profile, and are considered to have the exact same service configuration for each and every service.
NOTE: The S-CSCF recognizes that a given URI is an alias of another URI using the grouping sent from the HSS (see 3GPP TS 29.228 [14]).
Globally Routeable SIP URI: a SIP URI of which the hostname part can be resolved to the IP address of the entry entity of the network reponsible for the identity represented by the userpart.
Initial registration: The registration procedure for a public user identity initiated by the UE in the absence of any valid registration.
Registration expiration interval: An indication on how long a registration is valid, indicated using the Expires header field, or the "expires" header field parameter within the Contact header field, according to the procedures specified in RFC 3261 [26].
Reregistration: The registration procedure initiated by the UE to refresh or update an already existing registration for a public user identity.
Registration of an additional public user identity: The registration procedure initiated by the UE to explicitly register an additional public user identity during the life time of the registration of another registered public user identity, where both public user identities have the same contact address and P-CSCF.
Emergency registration: A special registration that relates to binding of a public user identity to a contact address used for emergency service.
Initial emergency registration: An emergency registration that is also an initial registration.
Emergency reregistration: An emergency registration that is also a reregistration.
Back-to-Back User Agent (B2BUA): As given in RFC 3261 [26]. In addition, for the usage in the IM CN subsystem, a SIP element being able to handle a collection of "n" User Agents (behaving each one as UAC and UAS, according to SIP rules), which are linked by some application logic that is fully independent of the SIP rules.
UE private IP address: It is assumed that the NAT device performs network address translation between a private and a public network with the UE located in the private network and the IM CN subsystem in the public network. The UE is assumed to be configured with a private IP address. This address will be denoted as UE private IP address.
UE public IP address: The NAT device is assumed to be configured with one (or perhaps more) public address(es). When the UE sends a request towards the public network, the NAT replaces the source address in the IP header of the packet, which contains the UE private IP address, with a public IP addressed assigned to the NAT. This address will be denoted as UE public IP address.
Encapsulating UDP header: For the purpose of performing UDP encapsulation according to RFC 3948 [63A] each IPsec ESP packet is wrapped into an additional UDP header. This header is denoted as Encapsulating UDP header.
Port_Uenc: In most residential scenarios, when the NAT device performs address translation, it also performs translation of the source port found in the transport layer (TCP/UDP) headers. Following RFC 3948 [63A], the UE will use port 4500 as source port in the encapsulating UDP header when sending a packet. This port is translated by the NAT into an arbitrarily chosen port number which is denoted as port_Uenc.
Multiple registrations: An additional capability of the UE, P-CSCF and S-CSCF, such that the UE (as identified by the private user identity and instance-id), can create multiple simultaneous registration bindings (flows), associated with one or more contact addresses, to any public user identity, Without this capability, a new registration from the UE for a public user identity replaces the existing registration binding, rather than merely creating an additional binding.
IMS flow set: An IMS flow set is a set of flows as defined in RFC 5626 [92]. The flows in an IMS flow set are determined by a combination of transport protocol, IP addresses, and ports. An IMS flow set is established by a successful IMS registration procedure.
NOTE: For IPsec, the ports associated with the flow set include protected client ports and protected server ports as defined in 3GPP TS 33.203 [19] and an IMS flow set is made up of the following four flows:
- Flow 1: (IP address UE, port_uc) <--> (IP address P-CSCF, port_ps) over TCP;
- Flow 2: (IP address UE, port_uc) <--> (IP address P-CSCF, port_ps) over UDP;
- Flow 3: (IP address UE, port_us) <--> (IP address P-CSCF, port_pc) over TCP; and
- Flow 4: (IP address UE, port_us) <--> (IP address P-CSCF, port_pc) over UDP.
NOTE 3: For IPsec, according to 3GPP TS 33.203 [19], the P-CSCF can only select among flows 3 or 4 when forwarding requests towards the UE. According to 3GPP TS 33.203 [19], flow 2 is only used for UE generated requests and responses. The P-CSCF uses flow 2 to identify the correct IMS flow set.
NOTE 4: An IMS flow set can be considered as a realisation of a logical flow as used in RFC 5626 [92]. But this definition does not depend on any particular definition of a logical flow.
NOTE 5: For TLS, the ports associated with the flow set include a protected client port and a protected server port and an IMS flow set is made up of the following flow:
- (IP address UE, port) <--> (IP address P-CSCF, port) over TCP.
NOTE 6: For SIP digest without TLS, an IMS flow set is as defined in RFC 5626 [92].
IMS flow token: A IMS flow token is uniquely associated with a IMS flow set. When forwarding a request destined towards the UE, the P-CSCF selects the flow from the IMS flow set denoted by the IMS flow token as appropriate according to 3GPP TS 33.203 [19] and RFC 3261 [26].
IMS registration related signalling: Signalling carrying the SIP messages sent by the UE and the network during the IMS registration procedure, i.e., SIP REGISTER request, SIP SUBSCRIBE request, and their responses.
IP Association: A mapping at the P-CSCF of a UE's packet source IP address, the "sent-by" parameter in the Via header field, and, conditionally, the port with the identities of the UE. This association corresponds to the IP address check table specified in 3GPP TS 33.203 [19].
Authorised Resource-Priority header field: a Resource-Priority header field that is either received from another entity in the trust domain relating to the Resource-Priority header field, or which has been identified as generated by a subscriber known to have such priority privileges for the resource priority namespace and level of priority used within that namespace.
Temporarily authorised Resource-Priority header field: a Resource Priority header field that has been temporarily approved by the P-CSCF, the S-CSCF, or an IBCF. Temporarily authorised Resource-Priority heaer field appears in an INVITE request only, and is applied only in the direction P-CSCF to S-CSCF to AS, S-CSCF to AS, or IBCF to S-CSCF to AS, for the request, and the reverse direction for 1xx responses to that request. Subsequent requests in the same dialog will require an authorised Resource-Priority header field in order to obtain priority privileges. It is only valid when all entities are in the same trust domain for the Resource-Priority header field.
Network-initiated resource reservation: A mechanism of resource reservation where the IP-CAN on the behalf of network initiates the resources to the UE.
Trace depth: When SIP signalling is logged for debugging purposes, trace depth is the level of detail of what is logged.
P-CSCF restoration procedures: the procedures for the IP-CAN and the UE to handle P-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]).
HSS based P-CSCF restoration procedures: the procedures for the IP-CAN, the IM CN subsystem, the HSS and the UE to handle P-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]). In 5GS the procedure is called UDM/HSS based P-CSCF restoration (see 3GPP TS 23.380 [7D]) since the UDM participates in the procedure.
PCRF based P-CSCF restoration procedures: the procedures for the IP-CAN, the IM CN subsystem, the PCRF and the UE to handle P-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]). In 5GS the procedure is called PCF based P-CSCF restoration (see 3GPP TS 23.380 [7D]) since the PCF takes the role of the PCRF.
Public network traffic: traffic sent to the IM CN subsystem for processing according to normal rules of the NGN. This type of traffic is known as public network traffic.
Private network traffic: traffic sent to the IM CN subsystem for processing according to an agreed set of rules specific to an enterprise. This type of traffic is known as private network traffic. Private network traffic is normally within a single enterprise, but private network traffic can also exist between two different enterprises if not precluded for regulatory reasons.
NOTE 7: An IP-PBX or application functionality within the IM CN subsystem can change private network traffic to public network traffic and vice versa, by functionality known as "breakout" or "breakin" to the private network. As such a SIP transaction can be variously private network traffic and public network traffic on different hops across a SIP network.
Privileged sender: A privileged sender is allowed to send SIP messages where the identities in P-Asserted-Identity will be passed on in the P-CSCF and are not subject to further processing in the P-CSCF.
S-CSCF restoration procedures: the procedures for the IM CN subsystem and the UE to handle S-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]).
Loopback routeing: A method of routeing a SIP request back to the visited network for local breakout according to the roaming architecture for voice over IMS with local breakout as specified in 3GPP TS 23.228 [7].
UE performing the functions of an external attached network: an independent network connected to an IMS network over the Gm interface, through a single point and which is seen by the IMS network as a specific UE; e.g. an IP-PBX.
Static Mode of Operation: a mode of operation where the UE performing the functions of an external attached network does not initiate any IMS level registration procedures towards the operator IMS.
Canonical form of a SIP URI: Canoncial form of a SIP URI takes the form "sip:username@domain" as specified in RFC 3261 [26] subclause 10.3. SIP URI comparisons are performed as defined in RFC 3261 [26] subclause 19.1.4.
Originating home network: the home network of a user originating a transaction, and if applicable, the associated dialog.
Originating visited network: the visited network of a user originating a transaction, and if applicable, the associated dialog.
Terminating home network: the home network of a user terminating a transaction, and if applicable, the associated dialog.
Terminating visited network: the visited network of a user terminating a transaction, and if applicable, the associated dialog.
Type of emergency service: The type of emergency service is either an emergency call type standardized by 3GPP (see 3GPP TS 22.101 [8] subclause 10.1) or a similar capability not standardised by 3GPP and defined by national regulatory requirements. The generic (sos) service, identified by urn:service:sos, does not have a type of emergency service (even though usage of the generic (sos) service in the emergency call is defined).
Resource sharing: one dedicated EPS bearer is sharing resources among several ongoing sessions such that the highest GBR (and optionally MBR) to be shared for the set of PCC/QoS rules bound to the same bearer is used as input for the calculation of the GBR (and optionally MBR) of that bearer among the sessions sharing the resources.
Fully-Qualified Domain Name (FQDN): the syntax of the FQDN used in this specification is defined in RFC 3261 [26] subclause 25.1.
Trusted WLAN: A trusted non-3GPP access, where the non-3GPP access is a WLAN IP access.
Untrusted WLAN: An untrusted non-3GPP access, where the non-3GPP access is a WLAN IP access.
Calling number verification status determination: A feature which enables the terminating UE to determine whether number has been verified by the network as specified in RFC 8224 [252].
Calling number verification using signature verification and attestation information: A feature which enables a calling identity validation as specified in RFC 8224 [252] and uses an attestation information to vouch for the accuracy of the source of origin of the call. Attestation information consists of an attestation level and an origination identifier and may be included in the Identity header field as defined in RFC 8588 [261] and in the Attestation-Info and Origination-Id header fields as defined in subclauses 7.2.18 and 7.2.19.
RCD verification using assertion of RCD info: A functionality which enables validation of RCD info (RCD information and RCD URL) as specified in draft-ietf-stir-passport-rcd [302]. The RCD information and RCD URL may be provided in the Call-Info header field as specified in draft-ietf-sipcore-callinfo-rcd [303]. As specified in draft-ietf-stir-passport-rcd [302] the Identity header field is used for the purpose of authentication of the Call-info header field containing RCD info. The RCD verification using assertion of RCD info functionality can be implemented in two ways:
1) within the Calling number verification using signature verification and attestation information feature which can be enhanced to authenticate and verify RCD info using the PASSporT SHAKEN JSON Web Token specified in RFC 8588 [261] with rcd PASSporT claims in accordance with draft-ietf-stir-passport-rcd [302]; or
2) if the Calling number verification using signature verification and attestation information feature is not supported, a standalone feature.
Priority verification using assertion of priority information: A feature which enables validation of a priority level provided in the Resource-Priority header field as specified in RFC 8443 [279] and, by extension for emergency sessions, the header field value "psap-callback" provided in the Priority header field as specified in RFC 9027 [278]. As specified in RFC 8443 [279] the Identity header field is used for the purpose of authentication of the Resource-Priority header field and, by extension for emergency sessions, the Priority header field value "psap-callback".
For the purposes of the present document, the following terms and definitions given in RFC 3261 [26] apply (unless otherwise specified see clause 6).
Client
Dialog
Final response
Header
Header field
Loose routeing
Method
Option-tag (see RFC 3261 [26] subclause 19.2)
Provisional response
Proxy, proxy server
Recursion
Redirect server
Registrar
Request
Response
Server
Session
(SIP) transaction
Stateful proxy
Stateless proxy
Status-code (see RFC 3261 [26] subclause 7.2)
Tag (see RFC 3261 [26] subclause 19.3)
Target Refresh Request
User agent client (UAC)
User agent server (UAS)
User agent (UA)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.002 [2] subclause 4.1.1.1 and subclause 4a.7 apply:
3GPP AAA proxy
3GPP AAA server
Breakout Gateway Control Function (BGCF)
Call Session Control Function (CSCF)
Home Subscriber Server (HSS)
Location Retrieval Function (LRF)
Media Gateway Control Function (MGCF)
MSC Server enhanced for IMS centralized services
Multimedia Resource Function Processor (MRFP)
Packet Data Gateway (PDG)
Subscription Locator Function (SLF)
WLAN UE
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122 [4C] apply:
Equivalent Home PLMN (EHPLMN)
Home PLMN (HPLMN)
Visited PLMN (VPLMN)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.218 [5] subclauses 3.1, 8 and 13 apply:
Filter criteria
Initial filter criteria
Initial request
ISC gateway function
Media Resource Broker (MRB)
Multimedia Resource Function Controller (MRFC)
Standalone transaction
Subsequent request
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [7] subclauses 3.1, 4.3.3.1, 4.3.6, 4.6, 4.13, 4.15a, 5.2, 5.4.12.1, 5.10, annex U, and annex W apply:
Border control concepts
Geo-local service number
Home local service number
Implicit registration set
Interconnection Border Control Function (IBCF)
Interrogating-CSCF (I-CSCF)
IMS Application Level Gateway (IMS-ALG)
IMS application reference
IMS Application Reference Identifier (IARI)
IMS communication service
IMS Communication Service Identifier (ICSI)
IMS Services for roaming users in deployments without IMS-level roaming interfaces
Local service number
IP-Connectivity Access Network (IP-CAN)
MPS-subscribed UE
P-CSCF enhanced for WebRTC (eP-CSCF)
Policy and Charging Rule Function (PCRF)
Private user identity
Proxy-CSCF (P-CSCF)
Public Service Identity (PSI)
Public user identity
Rich Call Data (RCD) information
Rich Call Data (RCD) URL
Roaming Architecture for Voice over IMS with Local Breakout
Serving-CSCF (S-CSCF)
Statically pre-configured PSI
WebRTC IMS Client (WIC)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.292 [7C] apply:
ICS UE
SCC AS
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.167 [4B] apply:
eCall over IMS
Emergency-CSCF (E-CSCF)
Geographical location information
Location identifier
Location information
For the purposes of the present document, the following terms and definitions given in 3GPP TR 33.203 [19] apply:
GPRS-IMS-Bundled Authentication (GIBA)
Port_pc
Port_ps
Port_uc
Port_us
Protected server port
Protected client port
spi_uc
spi_us
For the purposes of the present document, the following terms and definitions given in 3GPP TR 21.905 [1] apply:
IMS Credentials (IMC)
International Mobile Equipment Identity (IMEI)
IMS SIM (ISIM)
Serial NumbeR (SNR)
Type Approval Code (TAC)
Universal Integrated Circuit Card (UICC)
Universal Subscriber Identity Module (USIM)
User Equipment (UE)
For the purposes of the present document, the following terms and definitions given in RFC 2401 [20A] Appendix A apply:
Security association
A number of different security associations exist within the IM CN subsystem and within the underlying access transport. Within this document this term specifically applies to either:
i) the security association that exists between the UE and the P-CSCF. For this usage of the term, the term "security association" only applies to IPsec. This is the only security association that has direct impact on SIP; or
ii) the security association that exists between the WLAN UE and the PDG. This is the security association that is relevant to the discussion of Interworking WLAN as the underlying IP-CAN.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.234 [7A] apply.
Interworking WLAN
For the purposes of the present document, the following terms and definitions given in ITU-T E.164 [57] apply:
International public telecommunication number
For the purposes of the present document, the following terms and definitions given in RFC 5012 [91] apply:
Emergency service identifier
Emergency service URN
Public Safety Answering Point (PSAP)
PSAP URI
For the purposes of the present document, the following terms and definitions given in RFC 5627 [93] apply:
Globally Routable User Agent URI (GRUU)
For the purposes of the present document, the following terms and definitions given in RFC 5626 [92] apply:
Flow
For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.310 [19D] annex E and documents referenced therein:
TLS session
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.292 [8O] apply:
CS media
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.301 [8J] apply:
IMS Voice over PS Session (IMSVoPS) indicator
Persistent EPS bearer context
For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.328 [19C] apply:
End-to-access edge security
For the purposes of the present document, the following terms and definitions given in 3GPP2 S.R0048-A v4.0 [86F] apply:
Mobile Equipment Identity (MEID)
Manufacturer code
Serial number
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.302 [8U] apply:
Restrictive non-3GPP access network
S2a
S2b
S2c
Trusted non-3GPP access
Untrusted non-3GPP access
Unauthenticated IMSI
Firewall traversal tunnel
For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.240 [16] apply:
Charging Data Function (CDF);
Charging Data Record (CDR)
Online Charging Function (OCF)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.260 [17] apply:
IM CN subsystem Charging Identifier (ICID)
For the purposes of the present document, the following terms and definitions given in RFC 8119 [230] apply:
Service access number
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.101 [1A] apply:
eCall
Minimum Set of Data (MSD)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.011 [1C] apply:
3GPP PS data off
3GPP PS data off exempt services
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.402 [7E] apply.
TWAN
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.604 [8ZG] apply.
Diverting user
Diverted-to party
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.221 [272] apply:
Restricted Local Operator Services
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [257] apply:
NR RedCap
Stand-alone Non-Public Network
UE-Satellite-UE (UE-SAT-UE) communication |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.2 Symbols | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
1xx A status-code in the range 101 through 199, and excluding 100
18x A status-code in the range 180 through 189
2xx A status-code in the range 200 through 299
3xx A status-code in the range 300 through 399
4xx A status-code in the range 400 through 499
5GC 5G Core Network
5GS 5G System
5G-AN 5G Access Network
5xx A status-code in the range 500 through 599
6xx A status-code in the range 600 through 699
AAA Authentication, Authorization and Accounting
ANBR Access Network Bitrate Recommendation
APN Access Point
APN Access Point Name
AS Application Server
ATCF Access Transfer Control Function
AUTN Authentication TokeN
AVP Attribute-Value Pair
B2BUA Back-to-Back User Agent
BFCP Binary Floor Control Protocol
BGCF Breakout Gateway Control Function
c conditional
BRAS Broadband Remote Access Server
BSSID Basic Service Set Identifier
CCF Charging Collection Function
CDF Charging Data Function
CDR Charging Data Record
CH Credentials Holder
CK Ciphering Key
CN Core Network
CPC Calling Party's Category
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
DHCP Dynamic Host Configuration Protocol
DNN Data Network Name
DNS Domain Name System
DOCSIS Data Over Cable Service Interface Specification
DRVCC Dual Radio Voice Call Continuity
DTD Document Type Definition
DTLS Datagram Transport Layer Security
DTMF Dual Tone Multi Frequency
DVB Digital Video Broadcast
DVB-RCS2 Second Generation DVB Interactive Satellite System
e2ae-security End-to-access edge security
EATF Emergency Access Transfer Function
EC Emergency Centre
ECF Event Charging Function
ECI E-UTRAN Cell Identity
ECN Explicit Congestion Notification
E-CSCF Emergency CSCF
EF Elementary File
eP-CSCF P-CSCF enhanced for WebRTC
ePDG Evolved Packet Data Gateway
EPS Evolved Packet System
FAP cdma2000® 1x Femtocell Access Point
FQDN Fully Qualified Domain Name
GBA Generic Bootstrapping Architecture
GBR Guaranteed Bit Rate
GCID GPRS Charging Identifier
GGSN Gateway GPRS Support Node
GPON Gigabit-capable Passive Optical Networks
GPRS General Packet Radio Service
GRUU Globally Routable User agent URI
GSTN General Switched Telephone Network
HPLMN Home PLMN
HSS Home Subscriber Server
HTTP HyperText Transfer Protocol
i irrelevant
IARI IMS Application Reference Identifier
IBCF Interconnection Border Control Function
ICE Interactive Connectivity Establishment
I-CSCF Interrogating CSCF
ICS Implementation Conformance Statement
ICID IM CN subsystem Charging Identifier
ICSI IMS Communication Service Identifier
ID Identifier
IK Integrity Key
IKEv2 Internet Key Exchange Protocol Version 2
IM IP Multimedia
IMC IMS Credentials
IMEI International Mobile Equipment Identity
IMS IP Multimedia core network Subsystem
IMS-AGW IMS Access Gateway
IMS-ALG IMS Application Level Gateway
IMSI International Mobile Subscriber Identity
IMSVoPS IMS Voice over PS Session
IOI Inter Operator Identifier
IP Internet Protocol
IP-CAN IP-Connectivity Access Network
IPsec IP security
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISC IP Multimedia Subsystem Service Control
ISIM IM Subscriber Identity Module
I-WLAN Interworking – WLAN
IWF Interworking Function
KMS Key Management Service
LEO Low Earth Orbit
LRF Location Retrieval Function
m mandatory
MAC Message Authentication Code
MBR Maximum guaranteed Bit Rate
MCC Mobile Country Code
MCPTT Mission Critical Push To Talk
MEID Mobile Equipment Identity
MEO Medium Earth Orbit
MGCF Media Gateway Control Function
MGW Media Gateway
MNC Mobile Network Code
MF Media Function
MRB Media Resource Broker
MRFC Multimedia Resource Function Controller
MRFP Multimedia Resource Function Processor
MSC Mobile-services Switching Centre
MSD Minimum Set of emergency related Data
MSRP Message Session Relay Protocol
n/a not applicable
NAI Network Access Identifier
NA(P)T Network Address (and Port) Translation
NASS Network Attachment Subsystem
NAT Network Address Translation
NCC Network Control Center
NCC_ID Network Control Center Identifier
NID Network Identifier
NP Number Portability
o optional
OCF Online Charging Function
OLI Originating Line Information
OMR Optimal Media Routeing
PCC Policy and Charging Control
PCF Policy Control Function
PCO Protocol Configuration Options
PCRF Policy and Charging Rules Function
P-CSCF Proxy CSCF
PDG Packet Data Gateway
PDN Packet Data Network
PDP Packet Data Protocol
PDU Protocol Data Unit
P-GW PDN Gateway
PICS Protocol Implementation Conformance Statement
PIDF-LO Presence Information Data Format Location Object
PLMN Public Land Mobile Network
PSAP Public Safety Answering Point
PSI Public Service Identity
PSTN Public Switched Telephone Network
QCI QoS Class Identifier
QoS Quality of Service
RAND RANDom challenge
RCD Rich Call Data
RCS Return Channel via Satellite
RCST Return Channel via Satellite Terminal
RES RESponse
RLOS Restricted Local Operator Services
RTCP Real-time Transport Control Protocol
RTP Real-time Transport Protocol
SAC Service Area Code
SAI Service Area Identifier
SBA Service Based Architecture
SBI Service Based Interface
S-CSCF Serving CSCF
SCTP Stream Control Transmission Protocol
SDES Session Description Protocol Security Descriptions for Media Streams
SDP Session Description Protocol
SDU Service Data Unit
SIP Session Initiation Protocol
SLF Subscription Locator Function
SNPN Stand-alone Non-Public Network
SNR Serial Number
SQN SeQuence Number
SRVCC Single Radio Voice Call Continuity
STUN Session Traversal Utilities for NAT
SVN Satellite Virtual Network
SVN-MAC SVN Medium Access Control label
TAC Type Approval Code
TFT Traffic Flow Template
TP Telepresence
TLS Transport Layer Security
TRF Transit and Roaming Function
TURN Traversal Using Relay NAT
TWAG Trusted WLAN Access Gateway
TWAN Trusted WLAN
UA User Agent
UAC User Agent Client
UAS User Agent Server
UDM Unified Data Management
UDPTL UDP Transport Layer
UDVM Universal Decompressor Virtual Machine
UE User Equipment
UICC Universal Integrated Circuit Card
URI Uniform Resource Identifier
URL Uniform Resource Locator
URN Uniform Resource Name
USAT Universal Subscriber Identity Module Application Toolkit
USIM Universal Subscriber Identity Module
VPLMN Visited PLMN
WebRTC Web Real-Time Communication
WIC WebRTC IMS Client
WLAN Wireless Local Area Network
x prohibited
xDSL Digital Subscriber Line (all types)
XGPON1 10 Gigabit-capable Passive Optical Networks
XMAC expected MAC
XML eXtensible Markup Language
3A Interoperability with different IP-CAN
The IM CN subsystem can be accessed by UEs resident in different types of IP-CAN. The main body of this document, and annex A, are general to UEs and IM CN subsystems that are accessed using any type of IP-CAN. Requirements that are dependent on the type of IP-CAN are covered in annexes B, E, H, L, M, O, Q, R, S, U and W.
At any given time, for a given SIP transaction or dialog, the UE sees only one type of IP-CAN, as reported to it by the lower layers. The UE follows the procedures of the IP-CAN specific annex related to the last type of IP-CAN reported, even if it is different to one used previously. In particular, handover at the radio layers between two different access technologies can result in such a change while the dialog or transaction proceeds.
At any given time, for a given SIP transaction or dialog, the P-CSCF sees only one type of IP-CAN, as determined by interface to a particular resource architecture, e.g. policy and charging control, and by the access technology reported to it over that interface, or in the absence of this, by preconfiguration in the system. The P-CSCF follows the procedures of the IP-CAN specific annex related to the last type of IP-CAN determined, even if it is different to one used previously. In particular, handover at the radio layers between two different access technologies can result in such a change while the dialog or transaction proceeds.
It is the responsibility of the IP-CAN to ensure that usage of different bearer resources are synchronised on the handover from one IP-CAN to another, e.g. so that a signalling bearer provided by one IP-CAN is a signalling bearer (if provided by that IP-CAN) after handover, and that the appropriate QoS and resource reservation exists after handover. There is no SIP signalling associated with handover at the IP-CAN, and therefore no change in SIP state at one entity is signalled to the peer SIP entity when handover occurs.
In particular the following constraints exist that can have an impact on P-CSCF usage:
1) some IP-CANs can explicitly label a bearer as a signalling bearer, while others provide a bearer that has appropriate QoS, but no explicit labelling. Therefore if handover occurs from an IP-CAN with explicit labelling, to an IP-CAN with no explicit labelling, and then back to an IP-CAN with explicit labelling, the signalling will then be on a bearer that is not explicitly labelled; and
2) some IP-CANs support signalling of grouping of media within particular bearers, while others do not. Therefore if handover occurs from an IP-CAN with grouping, to an IP-CAN with no grouping, and then back to an IP-CAN with grouping, the signalled grouping can have been lost.
When a UE supports multiple IP-CANs, but does not support handover between those IP-CANs, the annex specific to that IP-CAN applies unmodified.
Where handover between IP-CANs occurs without a reregistration in the IM CN subsystem, the same identies and security credentials for access to the IM CN subsystem are used before and after the handover.
At the P-CSCF, the access technology can variously use the PCRF or PCF or NASS in support of both signalling and media bearer provision (or indeed use neither). How to determine which applies is up to network dependent rules, but can be specific to the access technology used by each different UE. Not all access technologies are defined for use with NASS, and not all access technologies are defined for use with the PCRF or PCF. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4 General | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.1 Conformance of IM CN subsystem entities to SIP, SDP and other protocols | SIP defines a number of roles which entities can implement in order to support capabilities. These roles are defined in annex A.
Each IM CN subsystem functional entity using an interface at the Gm reference point, the Ma reference point, the Mg reference point, the Mi reference point, the Mj reference point, the Mk reference point, the Ml reference point, the Mm reference point, the Mr reference point, the Mr' reference point, the Cr reference point, the Mw reference point, the I2 reference point, the I4 reference point and the Ici reference point, and also using the IP multimedia Subsystem Service Control (ISC) Interface, shall implement SIP, as defined by the referenced specifications in Annex A, and in accordance with the constraints and provisions specified in annex A, according to the following roles.
Each IM CN subsystem entity using an interface at the Rc reference point and the Ms reference point shall implement HTTP as defined in RFC 9112 [280], RFC 9110 [281] and RFC 9111 [284].
Each IM CN subsystem entity using an interface at the W2 reference point may implement SIP as an option. The detailed procedures of W2 interface are defined in 3GPP TS 24.371 [8Z].
The Gm reference point, the W2 reference point, the Ma reference point, the Mg reference point, the Mi reference point, the Mj reference point, the Mk reference point, the Ml reference point, the Mm reference point, the Mr reference point, the Mw reference point, the Cr reference point, the I2 reference point, the I4 reference point and the ISC reference point are defined in 3GPP TS 23.002 [2]. The Ici reference point and the Ms reference point are defined in 3GPP TS 23.228 [7]. The Mr' reference point and the Rc reference point are defined in 3GPP TS 23.218 [5].
For SIP:
- The User Equipment (UE) shall provide the User Agent (UA) role, with the exceptions and additional capabilities to SIP as described in subclause 5.1, with the exceptions and additional capabilities to SDP as described in subclause 6.1, and with the exceptions and additional capabilities to SigComp as described in subclause 8.1. The UE shall also provide the access technology specific procedures described in the appropriate access technology specific annex (see subclause 3A and subclause 9.2.2). The UE may include one or several interconnected SIP elements registered as a single logical entity when the UE performs the functions of an external attached network (e.g. an enterprise network). This specification does not place any constraint on the SIP role played by each of the elements as long as the compound entity appears to the IM CM subsystem as a SIP UA with the aforementioned exceptions and additional capabilities except for the modifications defined by the UE performing the functions of an external attached network modifying role in annex A.
NOTE 1: When the UE performs the functions of an external attached network (e.g. an enterprise network), the internal structure of this UE is outside the scope of this specification. It is expected that in the most common case, several SIP elements will be connected to an additional element directly attached to the IM CN subsystem.
- The P-CSCF shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in subclause 5.2, with the exceptions and additional capabilities to SDP as described in subclause 6.2, and with the exceptions and additional capabilities to SigComp as described in subclause 8.2. Under certain circumstances, if the P-CSCF provides an application level gateway functionality (IMS-ALG), the P-CSCF shall provide the UA role with the additional capabilities, as follows:
a) when acting as a subscriber to or the recipient of event information (see subclause 5.2);
b) when performing P-CSCF initiated dialog-release, even when acting as a proxy for the remainder of the dialog (see subclause 5.2);
c) when performing NAT traversal procedures (see subclause 6.7.2);
d) when performing media plane security procedures (see subclause 5.2); and
e) when providing access update procedures (see subclause 5.2.14).
The P-CSCF shall also provide the access technology specific procedures described in the appropriate access technology specific annex (see subclause 3A and subclause 9.2.2).
- The I-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.3.
- The S-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.4, and with the exceptions and additional capabilities to SDP as described in subclause 6.3. Under certain circumstances as described in subclause 5.4, the S-CSCF shall provide the UA role with the additional capabilities, as follows:
a) the S-CSCF shall also act as a registrar. When acting as a registrar, or for the purposes of executing a third-party registration, the S-CSCF shall provide the UA role;
b) as the notifier of event information the S-CSCF shall provide the UA role;
c) when providing a messaging mechanism by sending the MESSAGE method, the S-CSCF shall provide the UA role; and
d) when performing S-CSCF initiated dialog release the S-CSCF shall provide the UA role, even when acting as a proxy for the remainder of the dialog.
- The MGCF shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.5, and with the exceptions and additional capabilities to SDP as described in subclause 6.4.
- The BGCF shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.6.
- The AS, acting as terminating UA, or redirect server (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.1), shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.7.2, and with the exceptions and additional capabilities to SDP as described in subclause 6.6.
- The AS, acting as originating UA (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.2), shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.7.3, and with the exceptions and additional capabilities to SDP as described in subclause 6.6.
- The AS, acting as a SIP proxy (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.3), shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.7.4.
- The AS, performing 3rd party call control (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.4), shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.7.5, and with the exceptions and additional capabilities to SDP as described in subclause 6.6. An AS performing media control of an MRFC shall also support the procedures and methods described in subclause 10.2.
NOTE 2: Subclause 5.7 and its subclauses define only the requirements on the AS that relate to SIP. Other requirements are defined in 3GPP TS 23.218 [5].
- The AS, receiving third-party registration requests, shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.7.
- The MRFC shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.8, and with the exceptions and additional capabilities to SDP as described in subclause 6.5. The MRFC shall also support the procedures and methods described in subclause 10.3 for media control.
- In inline aware mode, the MRB shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.8A. In inline unaware mode, the MRB shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.8A. The MRB shall also support the procedures and methods described in subclause 10.4 for media control.
- The IBCF shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in subclause 5.10. If the IBCF provides an application level gateway functionality (IMS-ALG), then the IBCF shall provide the UA role, with the exceptions and additional capabilities to SIP as described in subclause 5.10, and with the exceptions and additional capabilities to SDP as described in subclause 6.7. If the IBCF provides screening functionality, then the IBCF may provide the UA role, with the exceptions and additional capabilities to SIP as described in subclause 5.10.
- The E-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in subclause 5.11. Under certain circumstances as described in subclause 5.11, the E-CSCF shall provide the UA role in accordance with RFC 3323 [33], with the additional capabilities, as follows:
a) when operator policy (e.g. determined by national regulatory requirements applicable to emergency services) allows user requests for suppression of public user identifiers and location information, then the E-CSCF shall provide the UA role, with the exceptions and additional capabilities to SIP as described in subclause 5.11;
b) when performing E-CSCF initiated dialog release the E-CSCF shall provide the UA role, even when acting as a proxy for the remainder of the dialog, e.g. for any of the reasons specified in RFC 6442 [89] or RFC 3323 [33];
c) when acting as a notifier for the dialog event package the E-CSCF shall provide the UA role; and
d) if operator policy allows any LRF to provide a location by value using the mechanism defined in subclause 5.11.3. the E-CSCF shall provide the UA role.
- The LRF shall provide the UA role.
- The ISC gateway function shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in subclause 5.13. If the ISC gateway function provides an application level gateway functionality (IMS-ALG), then the ISC gateway function shall provide the UA role, with the exceptions and additional capabilities to SIP as described in subclause 5.13, and with the exceptions and additional capabilities to SDP as described in subclause 6.7.
- The MSC Server enhanced for ICS shall provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.292 [8O].
- The MSC server enhanced for SRVCC using SIP interface shall provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M].
- The MSC server enhanced for DRVCC using SIP interface shall provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M].
- The EATF shall provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M].
- The ATCF shall:
a) provide the proxy role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M]; and
b) provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M].
- Where access to the IM CN subsystem is provided using Web Real-Time Communication (WebRTC) in accordance with 3GPP TS 24.371 [8Z], the eP-CSCF shall act as the P-CSCF in regard to the Mw reference point. For SIP, conformance of the eP-CSCF and WIC (or whatever functionality is downloaded to the WIC) is not specified by this document unless 3GPP TS 24.371 [8Z] specifies that these entities act as specified for the interface Gm reference point, in which case existing P-CSCF and UE procedures apply, with the exceptions and additional capabilities as described in 3GPP TS 24.371 [8Z]. For SDP, these entities act as specified for the interface Gm reference point, in which case existing P-CSCF and UE procedures apply, with the exceptions and additional capabilities as described in 3GPP TS 24.371 [8Z].
In addition to the roles specified above, the P-CSCF, the I-CSCF, the IBCF, the S-CSCF, the BGCF, the E-CSCF and the ISC gateway function can act as a UA when providing server functionality to return a final response for any of the reasons specified in RFC 3261 [26].
In addition to the roles specified above the S-CSCF, AS and an entity hosting the additional routeing capabilities as specified in subclause I.3 can act as a UA when providing either client or server functionality when the event package associated with overload control is deployed.
NOTE 3: Annex A can change the status of requirements in referenced specifications. Particular attention is drawn to table A.4 and table A.162 for capabilities within referenced SIP specifications, and to table A.317 and table A.328 for capabilities within referenced SDP specifications. The remaining tables build on these initial tables.
NOTE 4: The allocated roles defined in this clause are the starting point of the requirements from the IETF SIP specifications, and are then the basis for the description of further requirements. Some of these extra requirements formally change the proxy role into a B2BUA. In all other respects other than those more completely described in subclause 5.2 the P-CSCF implements proxy requirements. Despite being a B2BUA a P-CSCF does not implement UA requirements from the IETF RFCs, except as indicated in this specification, e.g., relating to registration event subscription.
NOTE 5: Except as specified in clause 5 or otherwise permitted in RFC 3261, the functional entities providing the proxy role are intended to be transparent to data within received requests and responses. Therefore these entities do not modify message bodies. If local policy applies to restrict such data being passed on, the functional entity has to assume the UA role and reject a request, or if in a response and where such procedures apply, to pass the response on and then clear the session using the BYE method.
All the above entities are functional entities that could be implemented in a number of different physical platforms coexisting with a number of other functional entities. The implementation shall give priority to transactions at one functional entity, e.g. that of the E-CSCF, over non-emergency transactions at other entities on the same physical implementation. Such priority is similar to the priority within the functional entities themselves specified elsewhere in this document.
Additional routeing functionality can be provided to support the ability for the IM CN subsystem to provide transit functionality as specified in Annex I. The additional routeing functionality shall assume the proxy role. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.2 URI and address assignments | In order for SIP and SDP to operate, the following prerequisite conditions apply:
1) I-CSCFs used in registration are allocated SIP URIs. Other IM CN subsystem entities may be allocated SIP URIs. For example sip:pcscf.home1.net and sip:<impl-specific-info>@pcscf.home1.net are valid SIP URIs. If the user part exists, it is an essential part of the address and shall not be omitted when copying or moving the address. How these addresses are assigned to the logical entities is up to the network operator. For example, a single SIP URI may be assigned to all I-CSCFs, and the load shared between various physical boxes by underlying IP capabilities, or separate SIP URIs may be assigned to each I-CSCF, and the load shared between various physical boxes using DNS SRV capabilities.
2) All IM CN subsystem entities are allocated IP addresses. Any IM CN subsystem entities can be allocated IPv4 only, IPv6 only or both IPv4 and IPv6 addresses. For systems providing access to IM CN subsystem using a GPRS IP-CAN or an EPS IP-CAN this is specified in 3GPP TS 23.221 [6] subclause 5.1. For systems providing access to IM CN subsystem using a cdma2000® packet data subsystem IP-CAN this is specified in subclause M.2.2.1. For systems providing access to IM CN subsystem using a 5GS IP-CAN this is specified in 3GPP TS 23.501 [257], subclause 5.8.2.2.
3) The subscriber is allocated a private user identity by the home network operator. This private user identity is available to the SIP application within the UE. Depending on the network operator, various arrangements exist within the UE for retaining this information:
a) where an ISIM is present, within the ISIM, see subclause 5.1.1.1A;
b) where no ISIM is present but USIM is present, the private user identity is derived (see subclause 5.1.1.1A);
c) neither ISIM nor USIM is present, but IMC is present, within IMC (see subclause 5.1.1.1B.1);
d) when neither ISIM nor USIM nor IMC is present, the private user identity is available to the UE via other means (see subclause 5.1.1.1B.2).
NOTE 1: 3GPP TS 33.203 [19] specifies that a UE attached to a 3GPP network has an ISIM or a USIM.
NOTE 2: The SIP URIs can be resolved by using any of public DNSs, private DNSs, or peer-to-peer agreements.
4) The subscriber is allocated one or more public user identities by the home network operator. The public user identity shall take the form of SIP URI as specified in RFC 3261 [26] or tel URI as specified in RFC 3966 [22]. At least one of the public user identities is a SIP URI. All registered public user identities are available to the SIP application within the UE, after registration. Depending on the network operator, various arrangements exist within the UE for retaining this information:
a) where an ISIM is present, at least one public user identity, which is a SIP URI, within the ISIM, see subclause 5.1.1.1A;
b) where no ISIM is present but USIM is present, a temporary public user identity is derived (see subclause 5.1.1.1A);
c) neither ISIM nor USIM is present, but IMC is present, within IMC (see subclause 5.1.1.1B.1);
d) when neither ISIM nor USIM nor IMC is present, the public user identities are available to the UE via other means (see subclause 5.1.1.1B.2).
NOTE 3: 3GPP TS 33.203 [19] specifies that a UE attached to a 3GPP network has an ISIM or a USIM.
5) If the UE supports GRUU (see table A.4, item A.4/53) or multiple registrations, then it shall have an Instance ID, in conformance with the mandatory requirements for Instance IDs specified in RFC 5627 [93] and RFC 5626 [92].
6) For each tel URI, there is at least one alias SIP URI in the set of implicitly registered public user identities that is used to implicitly register the associated tel URI.
NOTE 4: For each tel URI, there always exists a SIP URI that has identical user part as the tel URI and the "user" SIP URI parameter equals "phone" (see RFC 3261 [26] subclause 19.1.6), that represents the same public user identity. If a tel URI identifies a subscriber served by the IM CN subsystem, then the hostport parameter of the respective SIP URI contains the home network domain name of the IM CN subsystem to which the subscriber belongs.
6A) Identification of the UE to a PSAP with point of presence in the CS domain is not possible if a tel URI is not included in the set of implicitly registered public user identities. If the included tel URI is associated either with the first entry in the list of public user identities provisioned in the UE or with the temporary public user identity, then a PSAP can uniquely identify the UE if emergency registration is performed.
NOTE 5: The tel URI uniquely identifies the UE by not sharing any of the implicit registered public user identities in the implicit registration set that contains this tel URI.
NOTE 6: Emergency registration is not always needed or supported.
7) The public user identities may be shared across multiple UEs. A particular public user identity may be simultaneously registered from multiple UEs that use different private user identities and different contact addresses. When reregistering and deregistering a given public user identity and associated contact address, the UE will use the same private user identity that it had used during the initial registration of the respective public user identity and associated contact address. If the tel URI is a shared public user identity, then the associated alias SIP URI is also a shared public user identity. Likewise, if the alias SIP URI is a shared public user identity, then the associated tel URI is also a shared public user identity.
8) For the purpose of access to the IM CN subsystem, UEs can be allocated IPv4 only, IPv6 only or both IPv4 and IPv6 addresses. For systems providing access to IM CN subsystem using a GPRS IP-CAN or an EPS IP-CAN this is specified in 3GPP TS 23.221 [6] subclause 5.1 (see subclause 9.2.1 for the assignment procedures). For systems providing access to IM CN subsystem using a cdma2000® network this is specified in subclause M.2.2.1. For systems providing access to IM CN subsystem using a 5GS IP-CAN this is specified in 3GPP TS 23.501 [257], subclause 5.8.2.2.
9) For the purpose of indicating an IMS communication service to the network, UEs are assigned ICSI values appropriate to the IMS communication services supported by the UE, coded as URNs as specified in subclause 7.2A.8.2.
NOTE 7: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA).
10) E-CSCFs are allocated multiple SIP URIs. The SIP URI configured in the P-CSCF, AS or IBCF to reach the E-CSCF is distinct from the one given by the E-CSCF to the EATF such that EATF can reach the E-CSCF.
11) If the UE supports RFC 6140 [191] and performs the functions of an external attached network, the subscriber is allocated one or usually more public user identities by the home network operator. The public user identity(s) shall be allocated as global numbers in the international format.
4.2A Transport mechanisms
This document makes no requirement on the transport protocol used to transfer signalling information over and above that specified in RFC 3261 [26] clause 18, unless such requirement is defined in the access technology specific annex for the current access technology (see subclause 3A). However, the UE and IM CN subsystem entities shall transport SIP messages longer than 1300 bytes according to the procedures of RFC 3261 [26] subclause 18.1.1, even if a mechanism exists of discovering a maximum transmission unit size longer than 1500 bytes.
NOTE 1: Support of SCTP as specified in RFC 4168 [96] is optional for IM CN subsystem entities implementing the role of a UA or proxy. SCTP transport between the UE and P-CSCF is not supported in the present document. Support of the SCTP transport is currently not described in 3GPP TS 33.203 [19].
For initial REGISTER requests, the UE and the P-CSCF shall apply port handling according to subclause 5.1.1.2 and subclause 5.2.2.
The UE and the P-CSCF shall send and receive request and responses other than initial REGISTER requests on the protected ports as described in 3GPP TS 33.203 [19].
In case of an emergency session if the UE does not have sufficient credentials to authenticate with the IM CN subsystem and regulations allow, the UE and P-CSCF shall send request and responses other than initial REGISTER requests on non protected ports.
NOTE 2: When TCP is used to carry SIP signalling between the UE and the P-CSCF, it is known that there is no NAT between the UE and the P-CSCF and neither TLS nor the multiple registration mechanism is used, then both the UE and the P-CSCF can decide to close an existing TCP connection subject to the conditions described in RFC 3261 [26].
4.2B Security mechanisms
4.2B.1 Signalling security
3GPP TS 33.203 [19] defines the security features and mechanisms for secure access to the IM CN subsystem. This document defines a number of access security mechanisms, as summarised in table 4-1.
Table 4-1: Summary of access security mechanisms to the IM CN subsystem
Mechanism
Authentication
Integrity protection
Use of security agreement in accordance with RFC 3329 [48]
Support (as defined in 3GPP TS 33.203 [19])
IMS AKA plus IPsec ESP (see 3GPP TS 33.203 [19] clause 6)
(NOTE 8)
IMS AKA
IPsec ESP
Yes
Mandatory for all UEs containing a UICC, else optional.
Mandatory for all P-CSCF, I-CSCF, S-CSCF.
IMS AKA using HTTP Digest AKAv2 without IPSec security association (see 3GPP TS 33.203 [19] annex X)
IMS AKA
TLS session
(NOTE 7)
No
Mandatory for all UEs containing a WIC able to access to UICC.
Mandatory for all eP-CSCF. Optional for S-CSCF.
SIP digest plus check of IP association (see 3GPP TS 33.203 [19] annex N) (NOTE 2)
SIP digest
None (NOTE 3)
No
Optional for UEs.
Optional for P-CSCF, I-CSCF, S-CSCF.
SIP digest plus Proxy Authentication (see 3GPP TS 33.203 [19] annex N) (NOTE 2)
SIP digest
None (NOTE 3)
No
Optional for UEs
Optional for P-CSCF, I-CSCF, S-CSCF
SIP digest with TLS (see 3GPP TS 33.203 [19] annex N and annex O)
SIP digest
TLS session
Yes
Optional for UEs.
Optional for P-CSCF, I-CSCF, S-CSCF.
NASS-IMS bundled authentication (see 3GPP TS 33.203 [19] annex R) (NOTE 4, NOTE 5)
not applicable (NOTE 1)
None
(NOTE 3)
No
No UE support required.
Optional for P-CSCF, I-CSCF, S-CSCF.
GPRS-IMS-Bundled authentication (see 3GPP TS 33.203 [19] annex S) (NOTE 5)
not applicable (NOTE 1)
None (NOTE 3)
No
Optional for UEs.
Optional for P-CSCF, I-CSCF, S-CSCF.
Trusted node authentication (see 3GPP TS 33.203 [19] annex U)
not applicable (NOTE 6)
None
(NOTE 3)
No
No UE support required.
Optional for I-CSCF, S-CSCF.
SIP over TLS with client certificate authentication (see 3GPP TS 33.203 [19] annex O)
TLS client certificate
TLS session
No
Mandatory for a UE performing the functions of an external attached network operating in static mode.
Optional for IBCF and P-CSCF.
NOTE 1: Authentication is not provided as part of the IM CN subsystem signalling.
NOTE 2: The term "SIP digest without TLS" is used in this specification to refer to both "SIP digest plus check of IP association" and "SIP digest plus Proxy Authentication".
NOTE 3: This security mechanism does not allow SIP requests to be protected using an IPsec security association because it does not perform a key agreement procedure.
NOTE 4: A P-Access-Network-Info aware P-CSCF is required in order to provide NASS-IMS bundled authentication.
NOTE 5: The P-CSCF is restricted to the home network when performing this security mechanism.
NOTE 6: Trusted node authentication. For example the MSC server enhanced for IMS centralized services has authenticated the UE and as a consequence S-CSCF will skip authentication.
NOTE 7: SIP requests received at the eP-CSCF are protected by a TLS session established prior registration (see 3GPP TS 33.203 [19] annex X).
NOTE 8: IMS AKA and IPsec ESP mechanism includes support of "AKAv2-SHA-256" and "AKAv1-MD5" digest algorithms, but "AKAv1-MD5" algorithm is only supported for backward compatibility.
Specification of the mechanisms identified within table 4-1 within this document are provided in clause 5. Subclauses where security procedures are required consist of a general subclause applicable whichever security mechanisms are in use, and a separate subclause for each security mechanism identified by a row within table 4-1.
For access to the IM CN subsystem different than WebRTC TLS is optional to implement and is used only in combination with SIP digest authentication. For WebRTC based access to the IM CN subsystem TLS can be used in combination with IMS AKA using HTTP Digest AKAv2 without IPSec security association. Authentication associated with registration to the IM CN subsystem is applicable to IMS AKA and SIP digest and is covered in subclause 5.1.1 for the UE, subclause 5.2.2 for the P-CSCF and subclause 5.4.1 for the S-CSCF. Additionally, SIP digest allows for authentication to also occur on an initial request for a dialog or a request for a standalone transaction, this additional capability is covered in subclause 5.1.2A and subclause 5.4.3.2.
If a UE that implements SIP digest is configured not to use TLS, then the UE does not establish a TLS session toward the P-CSCF. If a UE supports TLS, then the UE supports TLS as described in 3GPP TS 33.203 [19].
For SIP digest authentication, the P-CSCF can be configured to have TLS required or disabled:
- if TLS is required, the P-CSCF requires the establishment of a TLS session from all SIP digest UEs, in order to access IMS subsequent to registration; or
- if TLS is disabled, the P-CSCF does not allow the establishment of a TLS session from any UE.
NOTE: The mechanism to configure the P-CSCF to have TLS required or disabled is outside the scope of this specification.
SIP digest cannot be used in conjunction with the procedures of Annex F.
For emergency calls, 3GPP TS 33.203 [19] specifies some relaxations, which are further described in the subclauses of this document relating to emergency calls.
3GPP TS 33.210 [19A] defines the security architecture for network domain IP based control planes. 3GPP TS 33.210 [19A] applies for security mechanisms between entities in the IM CN subsystem.
4.2B.2 Media security
3GPP TS 33.328 [19C] defines mechanisms for support of security on the media plane.
This document defines the required elements for signalling the support of media security.
The media security mechanisms are summarised as shown in table 4-2.
Table 4-2: Summary of media security mechanisms to the IM CN subsystem
Mechanism
Applicable to media
Support required by UE
Support required by IM CN subsystem entities
Network support outside IM CN subsystem entities
End-to-access-edge media security using SDES.
RTP based media only.
Support RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/34, A.317/36 and A.317/37.
P-CSCF (IMS-ALG) is required.
P-CSCF support of RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/34, A.317/36 and A.317/37.
(NOTE)
Not applicable.
End-to-access-edge media security using DTLS-SRTP.
RTP based media only.
Support RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/51 and A.317/55.
P-CSCF (IMS-ALG) is required.
P-CSCF support of RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/51 and A.317/55.
(NOTE)
Not applicable.
End-to-access-edge media security for MSRP using TLS and certificate fingerprints.
MSRP based media only.
Support RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/40, A.317/40A, A.317/51 and A.317/37A.
P-CSCF (IMS-ALG) is required.
P-CSCF support of RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/40, A.317/40A, A.317/51 and A.317/37A.
(NOTE)
Not applicable.
End-to-access-edge media security for BFCP using TLS and certificate fingerprints.
BFCP based media only.
Support RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/28, A.317/51 and A.317/37B.
P-CSCF (IMS-ALG) is required.
P-CSCF support of RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/28, A.317/51 and A.317/37B.
(NOTE)
Not applicable.
End-to-access-edge media security for UDPTL using DTLS and certificate fingerprints.
UDPTL based media only.
Support RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/52, A.317/51 and A.317/37C.
P-CSCF (IMS-ALG) is required.
P-CSCF support of RFC 3329 additions specified in subclause 7.2A.7 and SDP extensions specified in table A.317, items A.317/52, A.317/51 and A.317/37C.
(NOTE)
Not applicable.
End-to-end media security using SDES.
RTP based media only.
Support SDP extensions specified in table A.317, items A.317/34 and A.317/36.
Not applicable.
Not applicable.
End-to-end media security using KMS.
RTP based media only.
Support SDP extensions specified in table A.317, items A.317/34 and A.317/35.
Not applicable.
GBA and KMS support required.
End-to-end media security for MSRP using TLS and KMS.
MSRP based media only.
Support SDP extensions specified in table A.317, items A.317/40, A.317/40A and A.317/35, and support RFC 4279 [218].
Not applicable.
GBA and KMS support required.
NOTE: Support of end-to-access-edge media security is determined entirely by the network operator of the P-CSCF, which need not be the same network operator as that of the S-CSCF.
For RTP media security using SDES, the UE supports the SDES key management protocol and optionally the KMS key management protocol as defined in 3GPP TS 33.328 [19C] and SRTP as defined in RFC 3711 [169] for secure transport of media.
For end-to-access-edge media security of RTP media using DTLS-SRTP, the UE supports DTLS‑SRTP as defined in RFC 5763 [222] and RFC 5764 [223] with certificate fingerprints as defined in 3GPP TS 33.328 [19C].
For end-to-access-edge media security for MSRP using TLS and certificate fingerprints, the UE supports MSRP over TLS as defined in RFC 4975 [178] and RFC 6714 [214] with certificate fingerprints as defined in 3GPP TS 33.328 [19C].
For end-to-access-edge media security for BFCP using TLS and certificate fingerprints, the UE supports BFCP over TLS as defined in RFC 4583 [108] with certificate fingerprints as defined in 3GPP TS 33.328 [19C].
For end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, the UE supports UDPTL over DTLS as defined in RFC 7345 [217] and RFC 8842 [240], with certificate fingerprints as defined in 3GPP TS 33.328 [19C].
For end-to-end media security for MSRP using TLS and KMS, the UE supports MSRP over TLS as defined in RFC 4975 [178] and RFC 6714 [214] with pre-shared key ciphersuites as defined in RFC 4279 [218] and the KMS key management protocol as defined in 3GPP TS 33.328 [19C]. The certificate fingerprints are not indicated.
There is no support for media security in the MGCF, because there would be no end-to-end media security support on calls interworked with the CS domain and the CS user. In this release of this document, there is no support for media security in the MRF. End-to-access-edge media security is not impacted by this absence of support.
For emergency calls, it is not expected that PSAPs would support end-to-end media security and therefore the procedures of this document do not allow the UE to establish such sessions with end-to-end media security. End-to-access-edge media security is not impacted and can be used on emergency calls.
When the UE performs the functions of an external attached network (e.g. an enterprise network):
- where end-to-access-edge media security is used, the UE functionality is expected to be in the gateway of the external attached network, and support for further media security is outside the scope of this document; and
- where end-to-end media security is used, the UE functionality is expected to be supported by the endpoints in the attached network. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.3 Routeing principles of IM CN subsystem entities | Each IM CN subsystem functional entity shall apply loose routeing policy as described in RFC 3261 [26], when processing a SIP request. In cases where the I-CSCF, IBCF, S-CSCF and the E-CSCF may interact with strict routers in non IM CN subsystem networks, the I-CSCF, IBCF, S-CSCF and E-CSCF shall use the routeing procedures defined in RFC 3261 [26] to ensure interoperability with strict routers. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4 Trust domain | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.1 General | A trust domain can apply for specific header fields, tel URI parameters and SIP URI parameters within the IM CN subsystem.
For the IM CN subsystem, this trust domain consists of the functional entities that belong to the same operator's network (P-CSCF, the eP-CSCF, the E-CSCF, the I-CSCF, the IBCF, the S-CSCF, the BGCF. the MGCF, the MRFC, the MRB, the EATF, the ATCF, the ISC gateway function, and all ASs that are included in the trust domain). Additionally, other nodes within the IM CN subsystem that are not part of the same operator's domain may or may not be part of the trust domain, depending on whether an interconnect agreement exists with the remote network. SIP functional entities that belong to a network for which there is an interconnect agreement are part of the trust domain. ASs outside the operator's network can also belong to the trust domain if they have a trusted relationship with the home network.
NOTE 1: Whether any peer functional entity is regarded as part of the same operator's domain, and therefore part of the same trust domain, is dependent on operator policy which is preconfigured into each functional entity.
NOTE 2: For the purpose of this document, the PSAP is typically regarded as being within the trust domain, except where indicated. National regulator policy applicable to emergency services determines the trust domain applicable to certain header fields. This means that e.g. the handling of the P-Access-Network-Info header field, P-Asserted-Identity header field and the History-Info header field can be as if the PSAP is within the trust domain, and trust domain issues will be resolved accordingly.
The trust domain can exist for a number of purposes:
a) for the protection of information specific to an operator;
b) to provide for privacy requirements of the end user; or
c) to ensure that information is only passed to another entity if certain responsibilities related to that information are met by the receiving entity, for example that the signalled requirements in the Privacy header field will be met (see subclause 4.4.2 and 4.4.4).
Within the IM CN subsystem trust domains will be applied to a number of header fields. These trust domains do not necessarily contain the same functional entities or cover the same operator domains. The procedures in this subclause apply to the functional entities in clause 5 in the case where a trust domain boundary for that header field, tel URI parameter, or SIP URI parameter, exists at that functional entity.
Where the IM CN subsystem supports business communication, different trust domains can apply to public network traffic, and to private network traffic belonging to each supported corporate network.
NOTE 3: Where an external attached network (e.g. an enterprise network) is in use, the edges of the trust domains need not necessarily lie at the P-CSCF. In this release of the specification, the means by which the P-CSCF learns of such attached devices, and therefore different trust domain requirements to apply, is not provided in the specification and is assumed to be by configuration or by a mechanism outside the scope of this release of the specification.
A trust domain applies for the purpose of the following header fields: P-Asserted-Identity, P-Access-Network-Info, History-Info, Resource-Priority, P-Asserted-Service, Reason (only in a response), P-Profile-Key, P-Private-Network-Indication, P-Served-User, P-Early-Media, Feature-Caps, Restoration-Info, Relayed-Charge, Service-Interact-Info, Cellular-Network-Info, Response-Source, Attestation-Info, Origination-Id, Additional-Identity and Priority-Verstat. A trust domain applies for the purpose of the CPC and OLI tel URI parameters. A trust domain applies for the iotl SIP URI parameter. The trust domains of these header fields and parameters need not have the same boundaries. Clause 5 defines additional procedures concerning these header fields, tel URI parameters and SIP URI parameter. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.2 P-Asserted-Identity | RFC 3325 [34] provides for the existence and trust of an asserted identity within a trust domain. A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Identity header field according to RFC 3325 [34] when SIP signalling crosses the boundary of the trust domain. The priv-value "id" shall not be removed from the Privacy header field when SIP signalling crosses the boundary of the trust domain. Subclause 5.4 identifies additional cases for the removal of the P-Asserted-Identity header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.3 P-Access-Network-Info | A functional entity at the boundary of the trust domain shall remove any P-Access-Network-Info header field according to RFC 7315 [52]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.4 History-Info | A functional entity at the boundary of the trust domain will need to determine whether to remove the History-Info header field according to RFC 7044 [66] subclause 10.1.2 when SIP signalling crosses the boundary of the trust domain. Subclause 5.4 identifies additional cases for the removal of the History-Info header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.5 P-Asserted-Service | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Service header field according to RFC 6050 [121] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.6 Resource-Priority | If Priority verification using assertion of priority information features described in subclause 3.1 is supported then a functional entity at the boundary of the trust domain will need to determine, based on the operator policy, whether to remove a Resource-Priority header field.
Otherwise, if Priority verification using assertion of priority information features described in subclause 3.1 is not supported a functional entity shall only include a Resource-Priority header field in a request or response forwarded to another entity within the trust domain. If a request or response is forwarded to an entity outside the trust domain, the functional entity shall remove the Resource-Priority header field from the forwarded request or response. If a request or response is received from an untrusted entity (with the exception requests or responses received by the P-CSCF from the UE for which procedures are defined in subclause 5.2) that contains the Resource-Priority header field, the functional entity shall remove the Resource-Priority header field before forwarding the request or response within the trust domain.
NOTE: Alternate treatments can be applied when a non-trusted Resource-Priority header field is received over the boundary of trust domain. The exact treatment (e.g. removal, modification, or passing of the Resource-Priority header field) is left to national regulation and network configuration. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.7 Reason (in a response) | A functional entity shall only include a Reason header field in a response forwarded to another entity within the trust domain (as specified in RFC 6432 [130]). If a response is forwarded to an entity outside the trust domain, the functional entity shall remove the Reason header field from the forwarded response.
NOTE: A Reason header field can be received in a response from outside the trust domain and will not be removed. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.8 P-Profile-Key | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Profile-Key header field as defined in RFC 5002 [97] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.9 P-Served-User | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Served-User header field according to RFC 5502 [133] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.10 P-Private-Network-Indication | A functional entity shall only include a P-Private-Network-Indication header field in a request forwarded to another entity within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall remove the P-Private-Network-Indication header field from the forwarded request. If a request is received from an untrusted entity that contains the P-Private-Network-Indication header field, the functional entity shall remove the P-Private-Network-Indication header field before forwarding the request within the trust domain.
NOTE 1: Other entities within the enterprise will frequently be part of this trust domain.
NOTE 2: The presence of the P-Private-Network-Indication header field is an indication that the request constitutes private network traffic. This can modify the trust domain behaviour for other header fields.
NOTE 3: If a trust domain boundary is encountered for this header field without appropriate business communication processing, then this can be an indication that misconfiguration has occurred in the IM CN subsystem. Removal of this header field changes the request from private network traffic to public network traffic. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.11 P-Early-Media | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Early-Media header field as defined in RFC 5009 [109] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.12 CPC and OLI | Entities in the IM CN subsystem shall restrict "cpc" and "oli" URI parameters to specific domains that are trusted and support the "cpc" and "oli" URI parameters. Therefore for the purpose of the "cpc" and "oli" URI parameters within this specification, a trust domain also applies.
SIP functional entities within the trust domain shall remove the "cpc" and "oli" URI parameters when the SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.13 Feature-Caps | A functional entity at the boundary of the trust domain shall remove all Feature-Caps header fields received from UEs and external networks outside the trust domain.
NOTE: A UE that is a privileged sender is considered as part of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.14 Priority | Based on local policy, a functional entity at the boundary of the trust domain shall remove all Priority header fields with a "psap-callback" header field value. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.15 iotl | Entities in the IM CN subsystem shall restrict "iotl" URI parameter to specific domains that are trusted and support the "iotl" URI parameter. Support implies that the parameter is removed before the containing request is sent over an interface of a different type. Therefore for the purpose of the "iotl" URI parameter within this specification, a trust domain also applies.
SIP functional entities within the trust domain shall remove the "iotl" URI parameter when the SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.16 Restoration-Info | A functional entity at the boundary of the trust domain will need to determine whether to remove the Restoration-Info header field when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.17 Relayed-Charge | Entities in the IM CN subsystem shall restrict the Relayed-Charge header field to specific domains that are trusted and support the Relayed-Charge header field. Trust implies that the sending domain intends the receiving domain to have the contents of this header field. Therefore for the purpose of the Relayed-Charge header field within this specification, a trust domain also applies.
SIP functional entities within the trust domain shall remove the Relayed-Charge header field when the SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.18 Service-Interact-Info | A functional entity at the boundary of the trust domain shall remove all Service-Interact-Info header fields defined in subclause 7.2.when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.19 Cellular-Network-Info | A functional entity shall only include a Cellular-Network-Info header field in a request forwarded to another entity within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall remove the Cellular-Network-Info header field from the forwarded request. If a request is received from an untrusted entity that contains the Cellular-Network-Info header field, the functional entity shall remove Cellular-Network-Info header field before forwarding the request within the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.20 Response-Source | A functional entity at the boundary of the trust domain will need to determine whether to remove the Response-Source header field according to subclause 7.2.17. when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.21 Attestation-Info header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Attestation-Info header field according to subclause 7.2.18. when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.22 Origination-Id header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Origination-Id header field according to subclause 7.2.19 when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.23 Additional-Identity header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Additional-Identity header field according to subclause 7.2.20 when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.24 Priority-Verstat header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Priority-Verstat header field according to subclause 7.2.21 when SIP signalling crosses the boundary of the trust domain. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.