Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 24.229  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.5…   5…   5.1.1.4…   5.1.2…   5.1.4…   5.2…   5.2.3…   5.2.6…   5.2.7…   5.3…   5.4…   5.4.1.2.2…   5.4.1.3…   5.4.2   5.4.3…   5.4.3.3…   5.4.4…   5.5…   5.7…   5.7.2…   5.8…   5.11…   6…   6.6…   7…   7.2A…   7.2A.6…   7.3…   7.9A…   8…   A…   B…   C…   E…   F…   H…   I…   K…   L…   L.2A…   M…   N…   O…   Q…   R…   S…   U…   U.2A…   V…   W…

 

C (Normative)  UICC and USIM Aspects for access to the IM CN subsystem |R6|Word‑p. 802

C.1  Scope

This clause describes the UICC and USIM aspects for access to the IM CN subsystem. Additional requirements related to UICC usage for access to the IM CN subsystem are described in TS 33.203.

C.2  Derivation of IMS parameters from USIM

In case the UE is loaded with a UICC that contains a USIM but does not contain an ISIM, the UE shall:
  • generate a private user identity;
  • generate a temporary public user identity; and
  • generate a home network domain name to address the SIP REGISTER request to.
All these three parameters are derived from the IMSI parameter in the USIM, according to the procedures described in TS 23.003. Also in this case, the UE shall derive new values every time the UICC is changed, and shall discard existing values if the UICC is removed.
Up

C.3  ISIM Location in 3GPP Systems

For 3GPP systems, if ISIM is present, it is contained in UICC.

C.3A  UICC access to IMS |R10|

If the UE supports the UICC access to IMS USAT feature defined in TS 31.111 the following procedures in addition to the UE procedures in this specification apply.
If the EF UICCIARI contains a list of IARIs associated with active applications installed on the UICC in either the USIM or the ISIM, then when performing the user-initiated registration procedure as described in subclause 5.1.1.2 the UE shall include in the REGISTER request the list of IARIs associated with active applications installed on the UICC in addition to any IARI values for active applications installed on the ME in g.3gpp.iari-ref media feature tag(s) in the Contact header field of the REGISTER request as defined in subclause 7.9.3 and RFC 3840.
If the UE receives from the UICC an initial request for a dialog or a standalone transaction then after decapsulating the request as specified in TS 31.111 the UE shall send the request to the IM CN subsystem as specified in subclause 5.1.2A. When the UE receives from the UICC subsequent requests or responses related to dialogs or transactions already established for UICC applications then after decapsulating the request or response as specified in TS 31.111 the UE shall send the request or response to the IM CN subsystem as specified in subclause 5.1.2A.
When sending requests or responses received from the UICC to the IM CN subsystem the UE shall modify or include any header fields necessary (such as Route, Via, Contact) in order to conform with the procedures in this specification.
Up

C.4  Update of IMS parameters on the UICC |R7|Word‑p. 803
3GPP TS 31.102 and TS 31.103 specify the file structure and contents for the preconfigured parameters stored on the USIM and ISIM, respectively, necessary to initiate the registration to the IM CN subsystem. Any of these parameters can be updated via Data Download or a USAT application, as described in TS 31.111. If one ore more EFs are changed and a REFRESH command is issued by the UICC, then the UE reads the updated parameters from the UICC as specified for the REFRESH command in TS 31.111.
If the UE supports the UICC access to IMS USAT feature defined in TS 31.111 and the EF UICCIARI changes in either the USIM or the ISIM, the UE shall perform the user-initiated reregistration procedure as described in subclause 5.1.1.4 with the new values of the IARI parameter(s) residing on the UICC.
In case of changes to EFs other than the EF UICCIARI, the UE is not required to perform deregistration but it shall wait for the network-initated deregistration procedures to occur as described in subclause 5.4.1.5 unless the user initiates deregistration procedures as described in subclause 5.1.1.6. From this point onwards the normal initial registration procedures can occur.
Up

DVoid


Up   Top   ToC