Tech-invite  3GPPspace  IETF RFCs  SIP
index  N  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 31.102  Word version:  18.1.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M… 
5.9 ProSe related procedures  5.10 ePDG Selection related procedures  5.11 ACDC related procedures  5.12 MCS related procedures  5.13 ePDG Selection for Emergency Services related procedures  5.14 V2X related procedures  5.15 UAC Access Identities related procedures  5.16 CAG selection related procedures  5.17 5G ProSe related procedures  5.18 Disaster roaming related procedures  5.19 SNPN (Standalone NPN) related procedures  5.20 NG-RAN satellite access related procedures  5.21 SENSE related procedures 
...

 

5.9  ProSe related procedures  p. 294

5.9.1  ProSe Direct Discovery Provisioning parameters  p. 294

Requirement:
service No. 1 is "available" in the ProSe Service Table.
Request:
The ME performs the reading procedure with EFPROSE_MON and EFPROSE_ANN.

5.9.2  HPLMN ProSe Function address  p. 294

Requirement:
service No. 2 is "available" in the ProSe Service Table.
Request:
The ME performs the reading procedure with EFPROSEFUNC.

5.9.3  ProSe direct communication related Procedures  p. 294

Requirement:
service No. 3 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_RADIO_COM.

5.9.4  ProSe direct discovery related Procedures  p. 294

Requirement:
service No. 4 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_RADIO_MON.
Requirement:
service No. 5 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_RADIO_ANN.

5.9.5  ProSe direct communication related Procedures  p. 294

Requirement:
service No. 6 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_POLICY.

5.9.6  ProSe direct communication related Procedures  p. 294

Requirement:
service No. 3 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function
Request:
The ME performs the reading procedure with EFPROSE_PLMN.

5.9.7  ProSe Group Counter related Procedures  p. 295

Requirement:
service No. 7 is "available" in the ProSe Service Table.
Request:
The ME performs the reading procedure with EFPROSE_GC. The content from the USIM shall be combined with that one from the non-volatile memory on the ME, with USIM taking precedence in case the same group is available in both.
Update:
The ME performs the updating procedure with EFPROSE_GC. If the EF does not have free space, the ME shall use the non-volatile memory on the ME.
The ME is responsible to remove entries no longer used from the EFPROSE_GC in order to guarantee that EF is not filled with unnecessary entries.
Up

5.9.8  ProSe Usage Information Reporting Configuration related Procedures  p. 295

Requirement:
service No. 8 is "available" in the ProSe Service Table.
Request:
The ME performs the reading procedure with EFPROSE_UIRC. The content from the USIM shall be used by the ME to construct the content of the usage information report according the procedures defined in TS 24.334, with the USIM configuration parameters taking precedence in case the usage information reporting configuration parameters have also been provisioned in the ME.

5.9.9  ProSe Group Member Discovery related Procedures  p. 295

Requirement:
service No. 10 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_GM_DISCOVERY.

5.9.10  ProSe Relay related Procedures  p. 295

Requirement:
service No. 11 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EFAD or the ME received service authorization from the ProSe Function.
Request:
The ME performs the reading procedure with EFPROSE_RELAY and EFPROSE_RELAY_DISCOVERY.

5.10  ePDG Selection related procedures  p. 295

5.10.1  Home ePDG Identifier  p. 295

Requirement:
service No. 106 and No. 107 are "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFePDGId. The UE then shall use the Home ePDG identifier(s) present in the EFePDGId to perform the ePDG selection procedure as defined in TS 24.302.
If EFePDGId and EFePDGSelection are empty, the UE shall consider "ePDG configuration information is configured but empty", then the UE shall follow the procedure specified in the "Selection of the ePDG" UE procedure as defined in TS 24.302.
Up

5.10.2  ePDG Selection Information  p. 295

Requirement:
service No. 106 and No. 107 are "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFePDGSelection. The UE then shall use the ePDG selection information present in the EFePDGSelection to perform the ePDG selection procedure as defined in TS 24.302.
If EFePDGId and EFePDGSelection are empty, the UE shall consider "ePDG configuration information is configured but empty", then the UE shall follow the procedure specified in the "Selection of the ePDG" UE procedure as defined in TS 24.302.
Up

5.10.3  ePDG configuration information configured but empty  p. 296

Requirement:
service No. 106 is "available" and service No. 107 is not "available" in the USIM Service Table.
Request:
The UE shall consider "ePDG configuration information is configured but empty", then the UE shall follow the procedure specified in the "Selection of the ePDG" UE procedure as defined in TS 24.302.

5.11  ACDC related procedures  p. 296

5.11.1  ACDC Configuration  p. 296

Requirement:
service No. 108 is "available".
Request:
The ME performs the reading procedure with EFACDC.

5.12  MCS related procedures  p. 296

5.12.1  MCS configuration  p. 296

Requirement:
At least one of the services is "available" in the MCS Service Table.
Request:
The ME performs the reading procedure with EFMCS_CONFIG.

5.12.2  Void

5.12.3  Void

5.12.4  Void

5.13  ePDG Selection for Emergency Services related procedures  p. 296

5.13.1  Emergency ePDG Identifier  p. 296

Requirement:
service No. 110 and No. 111 are "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFePDGIdEm. The UE then shall use the Emergency ePDG identifier(s) present in the EFePDGIdEm to perform the ePDG selection procedure.
If EFePDGIdEm and EFePDGSelectionEm are empty, the UE shall consider that the ePDG configuration information for Emergency Services is configured but empty.
Up

5.13.2  ePDG Selection Information for Emergency Services  p. 297

Requirement:
service No. 110 and No. 111 are "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFePDGSelectionEm. The UE then shall use the ePDG selection information for Emergency Services present in the EFePDGSelectionEm to perform the ePDG selection procedure.
If EFePDGIdEm and EFePDGSelectionEm are empty, the UE shall consider that the ePDG configuration information for Emergency Services is configured but empty.
Up

5.13.3  ePDG configuration information for Emergency Services configured but empty  p. 297

Requirement:
service No. 111 is "available" and service No. 110 is not "available" in the USIM Service Table.
Request:
The UE shall consider the ePDG configuration information is configured but empty.

5.13.4  From Preferred related procedures  p. 297

Requirement:
service No. 114 is "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFFromPreferred. The UE then shall use the From Preferred value in the EFFromPreferred as described in clause 4.5.2.12 of TS 24.607.

5.13.5  IMS Configuration Data related procedures  p. 297

Requirement:
service No. 115 is "available" in the USIM Service Table.
Request:
The ME may perform the reading procedure with EFIMSConfigData. If the ME performs the reading procedure with EFIMSConfigData, the UE shall use the IMS Configuration Data in the EFIMSConfigData as described in clause L.2.2.5.1D of TS 24.229 and clause 6.1.1 of TS 24.229.

5.13.6  XCAP Configuration Data related procedures  p. 297

Requirement:
service No. 120 is "available" in the USIM Service Table.
Request:
The ME may perform the reading procedure with EFXCAPConfigData . If the ME performs the reading procedure with EFXCAPConfigData, the UE shall use the EFXCAPConfigData as described in clause 5.2.1.3 of TS 24.623z, and clause B.2 of TS 24.623.

5.13.7  Multi-device and multi-identity related procedures  p. 297

Requirement:
service No. 134 is "available" in the USIM Service Table.
Request:
The ME performs the reading procedure with EFMuDMiDConfigData. The UE shall use the EFMuDMiDConfigData as described in clauses 4.5.3.1 and 4.5.3.6 of TS 24.174.

5.14  V2X related procedures  p. 297

5.14.1  V2X configuration  p. 297

Requirement:
service No. 1 is "available" in the V2X Service Table.
Request:
The ME performs the reading procedure with EFV2X_CONFIG.

5.14.2  V2X data policy over PC5  p. 298

Requirement:
service No. 2 is "available" in the V2X Service Table.
Request:
The ME performs the reading procedure with EFV2XP_PC5.

5.14.3  V2X data policy over Uu  p. 298

Requirement:
service No. 3 is "available" in the V2X Service Table.
Request:
The ME performs the reading procedure with EFV2XP_Uu.

5.15  UAC Access Identities related procedures  p. 298

5.15.1  UAC Access Identities Configuration  p. 298

Requirement:
Service No. 126 is "available".
Request:
The ME performs the reading procedure with EFUAC_AIC.

5.16  CAG selection related procedures  p. 298

5.16.1  Pre-configured CAG information list reading procedure for ME  p. 298

Requirement:
Service No. 137 is "available".
Request:
The ME performs the reading procedure with EFCAG as specified in 3GPP TS 21.322 [31] clause 3.8.

5.17  5G ProSe related procedures  p. 298

5.17.1  5G ProSe configuration data for direct discovery  p. 298

Requirement:
service No. 139 is "available" in the USIM Service Table and service No. 1 is "available" in the 5G ProSe Sepstrvice Table.
Request:
The ME performs the reading procedure with EF5G_PROSE_DD.

5.17.2  5G ProSe configuration data for direct communication  p. 298

Requirement:
service No. 139 is "available" in the USIM Service Table and service No. 2 is "available" in the 5G ProSe Service Table.
Request:
The ME performs the reading procedure with EF5G_PROSE_DC.

5.17.3  5G ProSe configuration data for UE-to-network relay UE  p. 298

Requirement:
service No. 139 is "available" in the USIM Service Table and service No. 3 is "available" in the 5G ProSe Service Table.
Request:
The ME performs the reading procedure with EF5G_PROSE_U2NRU.

5.17.4  5G ProSe configuration data for remote UE  p. 298

Requirement:
service No. 139 is "available" in the USIM Service Table and service No. 4 is "available" in the 5G ProSe Service Table.
Request:
The ME performs the reading procedure with EF5G_PROSE_RU.

5.17.5  5G ProSe configuration data for usage information reporting  p. 299

Requirement:
service No. 139 is "available" in the USIM Service Table and service No. 5 is "available" in the 5G ProSe Service Table.
Request:
The ME performs the reading procedure with EF5G_PROSE_UIR.

5.18  Disaster roaming related procedures  p. 299

5.18.1  Disaster roaming information reading procedure for ME  p. 299

Requirement:
Service No. 140 is "available".
Request:
If the ME supports MINT (see TS 23.122), the ME performs the reading procedure with EFDRI.

5.19  SNPN (Standalone NPN) related procedures  p. 299

5.19.1  PWS configuration in SNPN.  p. 299

Requirement:
Service No. 143 is "available".
Request:
The ME performs the reading procedure with EFPWS_SNPN.

5.19.2  KAUSF derivation configuration  p. 299

Requirement:
Service No. 145 is "available".
Request:
The ME performs the reading procedure with EFKAUSF_DERIVATION.

5.20  NG-RAN satellite access related procedures  p. 299

5.20.1  Multiplier coefficient for Higher Priority PLMN search via NG-RAN satellite access for ME  p. 299

Requirement:
Service No. 144 is "available".
Request:
If the ME supports the NG-RAN via satellite access (see TS 23.122), the ME performs the reading procedure with EFMCHPPLMN.

5.21  SENSE related procedures  p. 299

5.21.1  SENSE parameter related procedure  p. 299

Requirement:
Service No. 148 is "available".
Request:
The ME performs the reading procedure with EFOCST.
The ME shall follow the procedures as specified in TS 23.122 for the "Operator controlled signal threshold per access technology".

Up   Top   ToC