Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.228  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.2.4…   4.3…   4.4…   4.13…   4.16…   5…   5.2…   5.3…   5.4…   5.4.7…   5.4.8…   5.4a…   5.5…   5.6…   5.6.3…   5.7…   5.7.3…   5.7.5…   5.8…   5.11…   5.11.3…   5.11.4…   5.11.5…   5.11.6…   5.12…   5.16…   5.19   5.20…   A…   E…   E.2.2…   G…   G.5…   H…   J…   L…   N…   Q…   Q.2.5…   R…   S…   U…   U.2…   V…   Y…   Z…   AA…   AA.3…

 

V (Normative)  IP-Connectivity Access Network specific concepts when using Untrusted WLAN to access IMS |R13|p. 320

V.1  Generalp. 320

This clause describes the main IP-Connectivity Access Network specific concepts that are used for the provisioning of IMS services over untrusted WLAN access to EPC.
Following specific considerations apply to the case of untrusted WLAN access:
  • The Mobility related procedures for untrusted WLAN access to EPC are described in TS 23.402.
  • For untrusted WLAN access, ePDG is used to interface the access network and to control relevant PDN connectivity (over S2b) towards a P-GW.
  • For untrusted WLAN access, the way the notification of the loss of IP-CAN session for a UE is triggered within an untrusted WLAN is out of scope of 3GPP specifications.
  • For untrusted WLAN access, the Reporting of User location information (i.e. UE local IP address and Network Provided WLAN Location Information) in the EPS is defined in clauses 4.5.7.2.8, 7.4.3.1, 7.9.2, 7.10 and 7.11.14 of TS 23.402 and the related PCC Access Network Information reporting procedure is defined in clause H.4 of TS 23.203. Information flows on how user location information can be further distributed within IMS can be found in Annex R.
  • In order to fulfil regulatory requirements, IMS requires in addition to the UE local IP address, the identity of the ePDG to which the UE is connected, and the UE source port (TCP port or UDP port) used by the UE to establish the IKEv2 tunnel with the ePDG.
Up

V.2  UE Provided Access Information in Untrusted WLAN accessp. 320

A UE accessing IMS via untrusted WLAN shall support the following:
  • If available, provide the identity of the WLAN AP the UE is currently associated with, and used for IMS signalling at IMS registration, IMS emergency registration, IMS session initiation, SMS over IP, and in any procedure defined in TS 24.229, where access network information is provided.
  • If available, provide geographical location coordinates during IMS emergency session setup.
  • Provide the cell information (cell-ID) for the most recent seen cell at IMS registration, IMS emergency registration, IMS emergency session initiation, and in any procedure defined in TS 24.229 where access network information is provided. The cell-ID access information shall include additional information describing when the information about the cell-ID was collected and that can be used to calculate the "age" of the information. The information about the cell-ID shall be included in an appropriate field of the SIP request that is distinguished from the information about the access network currently used to transport SIP signalling (i.e. Untrusted WLAN).
Up

W (Normative)  Support of IMS Services for roaming users in deployments without IMS-level roaming interfaces |R14|p. 322

W.1  Generalp. 322

This clause describes the functions that are used to support IMS services for roaming users in deployments without IMS-level roaming interfaces. This Annex is applicable to UEs connected to EPS and 5GS. In this roaming model the mobility anchor (i.e. PGW or UPF) is located in the home PLMN and therefore UE IMS signalling and user plane traffic are routed to home PLMN. It is assumed that confidentiality protection is not used in HPLMN and VPLMN for IMS media plane traffic.
For the LBO roaming model where P-CSCF is in VPLMN, see Annex M.
Up

W.2  Architecturep. 322

W.2.1  EPS |R18|p. 322

The architecture to support IMS services for roaming users, including Voice over IMS, in deployments without IMS-level roaming interfaces is shown in Figure W.2-1
The following architecture requirements apply:
  • P-CSCF (at HPLMN) identifies the serving network (VPLMN) where the UE is located using the procedure defined in clause W.3.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. W.2-1: IMS traffic home routed
Figure W.2-1: IMS traffic home routed
(⇒ copy of original 3GPP image)
Up
The corresponding architecture for 5GS is defined in clause Y.9.2.

W.2.2  5GS |R18|p. 322

W.3Void

W.4  Procedures related to PLMN ID change |R18|p. 323

W.4.1  Subscription to changes of PLMN ID at IMS Initial Registrationp. 323

In deployments without IMS-level roaming interfaces, the home network determines the serving PLMN of the UE using procedure defined in TS 23.203, TS 23.503 or TS 29.214, where the P-CSCF requests the PCRF/PCF to report the PLMN identifier where the UE is currently located. The received PLMN ID information is then forwarded in the SIP REGISTER request.
This procedure shall be applied by the P-CSCF at initial UE IMS registration.
The below procedure relates to EPS, the corresponding procedure for 5GS is defined in Annex Y.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. W.4.1-1: Subscription by P-CSCF to changes in PLMN ID during initial IMS Registration
Up
Step 1.
The UE sends a SIP REGISTER request to the P-CSCF.
Step 2.
If this is the initial IMS registration then the P-CSCF subscribes to the PCRF/PCF to be notified of the PLMN ID where the UE is currently attached. The subscription to PLMN changes is active as long as the UE is IMS registered.
Step 3.
The PCRF/PCF forwards the PLMN ID to the P-CSCF. The P-CSCF stores the PLMN ID.
Step 4.
The P-CSCF includes the received PLMN ID in the SIP REGISTER request before forwarding the request to the I-CSCF.
Step 5.
Normal IMS registration procedure is then completed.
Up

W.4.2  UE is not active in an IMS voice sessionp. 323

The following procedure shall be applied by IMS at reception of PLMN change when the UE is not active in an IMS voice call, and when the PDN connection/PDU session is kept at PLMN change.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. W.4.2-1: Procedure for PLMN change
Figure W.4.2-1: Procedure for PLMN change
(⇒ copy of original 3GPP image)
Up
Step 1.
EPC/5GC detects PLMN change.
Step 2.
H-PCRF/PCF notifies P-CSCF that PLMN change has occurred and indicates the new PLMN ID.
Step 3.
P-CSCF sends SIP MESSAGE with new PLMN ID to S-CSCF.
Step 4.
Based on regulatory requirements (see NOTE 2), S-CSCF sends SIP NOTIFY with re-authentication request to the UE.
Step 5.
UE initiates re-registration procedure. During the re-registration procedure, the P-CSCF may update the SIP signalling encryption depending on roaming agreements, e.g., moving from HPLMN to VPLMN can result in turning off IMS encryption while retaining integrity protection of IMS signalling.
Up

W.4.3  UE is active in an IMS voice sessionp. 324

The following procedure shall be applied by IMS at reception of PLMN change when the UE is active in an IMS voice call, and when the PDN connection/PDU session is kept at PLMN change.
Copy of original 3GPP image for 3GPP TS 23.228, Fig. W.4.3-1: PLMN change detected by EPC/5GC
Figure W.4.3-1: PLMN change detected by EPC/5GC
(⇒ copy of original 3GPP image)
Up
Step 0.
UE is active in an IMS voice call.
Step 1.
EPC/5GC detects PLMN change.
Step 2.
H-PCRF/PCF notifies the P-CSCF that PLMN change has occurred and indicates the new PLMN ID.
Step 3.
P-CSCF sends SIP MESSAGE with the new PLMN ID to the S-CSCF.
Step 3a.
P-CSCF sends SIP MESSAGE with new PLMN ID to the TAS so that the TAS may update any charging records with the new PLMN ID.
Step 4.
Based on regulatory requirements (see NOTE 1), S-CSCF sends SIP NOTIFY with re-authentication request to the UE.
Step 5.
UE initiates re-registration procedure. During the re-registration procedure, the P-CSCF may update the SIP signalling encryption depending on roaming agreements, e.g., moving from HPLMN to VPLMN can result in turning off IMS encryption while retaining integrity protection of IMS signalling.
Step 6.
Once the re-registration procedure is completed and based on regulatory requirements (see NOTE), the P-CSCF may send a SIP MESSAGE to the TAS indicating that TAS should send a re-INVITE request to the UE.
Step 7.
TAS sends SIP Re-INVITE to UE including, subject to the privacy settings associated with the original call, call related information (e.g. calling and called party information, indication whether UE was calling party or called party in the call, redirecting party information (if present), media endpoints and used codecs). Codec endpoints are translated in the P-CSCF if needed. The UE should not reveal this information to the user.
Step 8.
UE sends SIP 200 OK to TAS.
Up

X (Normative)  IMS 3GPP PS Data Off Service Accessibility |R14|p. 326

X.1  Generalp. 326

3GPP PS Data Off is an optional feature. When activated by the user and when the network supports the feature, this feature allows control of the IMS services and more broadly SIP based services using the IMS framework that the user is allowed to access, for both originating and terminating sessions.
The list of 3GPP PS Data Off Exempted Services is configured by the HPLMN in the UE and in the network for enforcement. The list of SIP based service can include any one or any combination of the following services:
  • MMTel Voice;
  • SMS over IMS;
  • MMTel Video;
  • USSI;
  • Particular IMS Services not defined by 3GPP, where each such IMS service is identified by an IMS communication service identifier.
Up

X.2  UE Behaviourp. 326

X.2.1  UE 3GPP PS Data Off Status Reportingp. 326

The UE shall include an indication that depicts the 3GPP PS Data Off status (active/inactive) at initial IMS registration, and subsequent to that, any time the end user changes the 3GPP PS Data Off status in a (re-)REGISTER request. In all these registration requests the UE shall register the SIP based services that are configured in the UE.
The UE and the network shall ensure that the proper services are enforced in accordance with the 3GPP PS Data Off status.
Up

X.2.2  UE Provisioningp. 326

The UE may be provisoned by HPLMN with up to two enumerated lists of SIP-based services that are 3GPP PS Data Off exempted either via Device Management or in the UICC, one list is valid for the UEs camping in the home PLMN and the other list is valid for any VPLMN the UE is roaming in. When the UE is configured only with a single list, without an indication to which PLMNs the list is applicable, then this list is valid for the home PLMN and any PLMN the UE is roaming in.
A UE provisioned with an updated list shall enforce the updated list immediately.
Up

X.2.3  UE Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Servicesp. 326

When the UE changes its 3GPP PS Data Off status from inactive to active, the UE shall ensure that only the 3GPP PS Data Off Exempted Services in the provisioned list are allowed to be transported, and the corresponding IP uplink packets shall be sent accordingly as follows:
  • The UE shall prevent sending of UE-originating SIP requests which are for services other than the 3GPP PS Data Off Exempted Services configured in the UE via device management or in the UICC.
  • The UE shall prevent sending of SDP offers and SDP answers with media streams for the media types other than those related to the 3GPP PS Data Off Exempted Services configured via device management or in the UICC.
  • A UE shall immediately stop sending any media packets and shall terminate all ongoing sessions for all SIP-based services that are not 3GPP PS Data Off Exempt.
  • A UE provisioned with an updated list shall enforce the updated list immediately. To that effect, the UE shall immediately stop sending any media packets and terminate all ongoing SIP-based sessions handling the 3GPP PS Data Off Exempt Service(s) removed from the list.
Up

X.3  Network Behaviourp. 327

X.3.1  Network Update to 3GPP PS Data Off Exempted Servicesp. 327

The HPLMN network shall provision in the UE either via Device Management or in the UICC the lists of 3GPP PS Data Off Exempt Services. Up to two lists are provisioned in the UE for that purpose: one list is used when the UE is at home, while the second list is used when the UE is roaming in any visited PLMN.
The information shall be provisioned in the UE prior to enabling the 3GPP PS Data Off Service. Any change to either one or both lists shall immediately be sent to the UE for enforcement.

X.3.2  Network Enforcement of SIP-Based 3GPP PS Data Off Exempted Servicesp. 327

Application Servers implementing the SIP-based services shall enforce the SIP based 3GPP PS Data Off Exempted services for all UEs.
Each Application Server shall be configured with up to two lists of 3GPP PS Data Off Exempt Services, one list for non-roaming users, and the other list for users roaming in the various VPLMNs with whom roaming agreements exist.
The AS shall become aware of the UE 3GPP Data Off status (active/inactive) at IMS (re-)Registration through third party registration. If the UE has changed its 3GPP PS Data Off status from inactive to active, the AS shall ensure that only SIP-based services which are part of the SIP-based 3GPP PS Data Off Exempt Services are permitted.
If the UE has changed its 3GPP PS Data Off status from active to inactive, the AS shall also let through the terminating requests to the UE for services that were not Data Off exempt.
Up

Up   Top   ToC