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

Content for  TS 33.127  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   5…   5.4…   5.6…   5.7…   6…   6.2.2…   6.2.3…   6.2.5…   6.3…   6.3.3…   6.3.4…   6.4…   7…   7.3…   7.4…   7.4.7…   7.5…   7.6…   7.7…   7.8…   7.9…   7.10…   7.11…   7.12…   7.13…   7.14…   7.15…   7.16…   8…   A…   A.2…   A.3…   A.4…   B…   D…   E… 
7.7 Identity Caching Function  7.7.1 General  7.7.2 ICF Query Identities  7.7.3 ICF Response parameters  7.7.4 Network topologies 
...

 

7.7  Identity Caching Function  p. 104

7.7.1  General  p. 104

The ICF is responsible for receiving identity caching events from all IEFs in the network over the LI_XER interface and handling queries from the IQF over the LI_XQR interface to the IQF as defined in clause 5.7.
The temporary cache duration shall be configurable by the LICF on a per CSP network basis.

7.7.2  ICF Query Identities  p. 104

The IQF present in the ADMF shall be able to query the records held by the ICF using one of the following target identifiers:
  • SUPI.
  • SUCI.
  • 5G-S-TMSI.
  • 5G-GUTI.
The list of event parameters is specified in TS 33.128. Each event shall include at the minimum the following information:
  • Query target identifier.
  • Time of target identifier observation.
For queries based on temporary identifiers the following additional information shall be included:
  • Tracking area identifier.
  • Cell identity.
Up

7.7.3  ICF Response parameters  p. 105

The list of event parameters is specified in TS 33.128. Each event shall include at the minimum the following information:
  • Subscription permanent identifier.
  • Related temporary identifier(s).
  • Start of validity timestamp(s).
  • End of validity timestamp(s).
The following additional information shall be included if it was available in the IEF records provided to the ICF:
  • Permanent equipment identifier (PEI).
  • Generic Public Subscription Identifier (GPSI).
The following additional information shall be included when available and if requested in the IQF to ICF query:
  • Location information (i.e. Cell identity and tracking area identifier).
Up

7.7.4  Network topologies  p. 105

Since the ICF caches events independently of network topology for individual service usage UEs, no specific network topology handling is provided by the ICF. The IQF shall be responsible for handling any network topology requirements that may be applied by the LEA in an individual warrant.

Up   Top   ToC