hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.34 Kseaf | The Kseaf is defined in 3GPP TS 33.501 [116]. It is a key provided by the AUSF to the AMF acting as an SEAF.
NOTE: For 5G-AKA, the Kseaf is provided if confirmation from AUSF is successful. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.35 AuthenticationMethod | The AuthenticationMethod is described in 3GPP TS 33.501 [116].
The AuthenticationMethod is permanent data mandatory stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.36 PermanentKey | The PermanentKey is described in 3GPP TS 33.501 [116]. The permanent key shall be stored encrypted.
The PermanentKey is permanent data contitionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.37 SequenceNumber | The SequenceNumber is described in 3GPP TS 33.102 [52].
The SequenceNumber is temporary data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.38 AuthenticationManagementField | The AuthenticationManagementField is described in 3GPP TS 33.501 [116].
The AuthenticationManagementField is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.39 VectorAlgorithm | The VectorAlgorithm the algorithm used for the generation of authentication vectors see 3GPP TS 29.505 [119].
The VectorAlgorithm is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.40 Milenage | The Milenage described in 3GPP TS 35.206 [117].
The Milenage is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.41 Tuak | The Tuak described in 3GPP TS 35.231 [118].
The Tuak is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.42 Opc | The Opc described in 3GPP TS 35.205 [117].
The Opc is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.43 Topc | The Topc described in 3GPP TS 35.231 [118].
The Topc is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.44 Authentication Status | The authentication status of the UE contains authentication result, timestamp, and the serving network name.
The Authentication Status is temporary data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.45 SoR-XMAC-IUE | The SoR-XMAC-IUE of the UE contains the expected SoR-XMAC-IUE as specified in 3GPP TS 33.501 [116].
The SoR-XMAC-IUE is temporary data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.46 Shared Data Ids | The Shared Data Id is defined in 3GPP TS 29.503 [114].
Shared Data Ids are permanent data and are conditionally stored in the UDM, AMF, SMSF and SMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.47 Access Restriction Data | The use of this data is described in 3GPP TS 23.501 [112] clause 5.3.4.1.1.
The Access Restriction Data is permanent subscriber data and is conditionally stored per PLMN in the UDM and the AMF.
The parameter takes either of the following values:
- NR not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access. Valid for Idle and Connected mode;
- NR not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access as secondary RAT. Valid for Connected mode;
NOTE: As specified in clause 4.11.1.2.1 of 3GPP TS 23.502 [113], this restriction can also be applied when attached to EPC depending on operator policy, and in this case AMF will send this information to MME during handover from 5GC to EPC in order to allow MME to make appropriate handling, e.g. SGW selection based on access restriction, or whether or not to allocate resources for secondary RAT during inter RAT handover.
- NR in unlicensed bands not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access in unlicensed bands. Valid for Idle and Connected mode;
- NR in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access in unlicensed bands as secondary RAT. Valid for Connected mode;
- E-UTRA not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using E-UTRA radio access. Valid for Idle and Connected mode;
- E-UTRA not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access as secondary RAT. Valid for Connected mode;
- E-UTRA in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access in unlicensed bands as secondary RAT. Valid for Connected mode;
- NB-IoT not allowed, the subscriber shall not be allowed to access the network in TAs using NB-IoT radio access. Valid for Idle and Connected mode;
- LTE-M not allowed, the subscriber shall not be allowed to access the network in TAs using LTE-M radio access. Valid for Idle and Connected mode;
- NR(LEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(LEO) satellite access. Valid for Idle and Connected mode;
- NR(MEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(MEO) satellite access. Valid for Idle and Connected mode;
- NR(GEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(GEO) satellite access. Valid for Idle and Connected mode;
- NR(OTHERSAT) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(OTHERSAT) satellite access. Valid for Idle and Connected mode;
- NR RedCap not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access with reduced radio capability (RedCap). Valid for Idle and Connected mode.
- NR eRedCap not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access with enhanced reduced radio capability (eRedCap). Valid for Idle and Connected mode.
Only the access restriction for WB-E-UTRA and NB-IoT may include a different value per PLMN.
The use of this parameter for TA update procedures is described in 3GPP TS 23.501 [112]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.48 IAB-Operation Allowed indication | The IAB-Operation Allowed indication defines if the subscriber is allowed for IAB node operation as specified in 3GPP TS 23.501 [112].
The IAB-Operation Allowed indication is permanent subscriber data and is conditionally stored in the UDM and the AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.49 UE radio capability ID | The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.501 [112].
The UE radio capability ID is temporary subscriber data and is conditionally stored in the AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.50 RG Level Wireline Access Characteristics | RG Level Wireline Access Characteristics (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.51 RG-TMBR | RG-TMBR (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.52 List of 5GS Broadcast Location Assistance Data Types | This data contains information used to determine which ciphering key data should be provided to the UE if requested by the UE, when location assistance data is broadcast in NG-RAN using ciphering. For a detailed definition of this data, refer to 3GPP TS 23.273 [121].
The list of 5GS Broadcast Location Assistance Data Types is permanent subscriber data and is conditionally stored in the UDM and the AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3 Definition of data for IP Multimedia domain | This clause describes the IMS data for IMS subscribers and PSI users. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1 Data related to subscription, identification and numbering | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.1 Private User Identity | The Private User Identity is applicable to IMS subscribers only. The Private User Identity is in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48].
If the GAA bootstrapping is based on authentication data from the IM domain, the corresponding Private User Identity from the IM d omain (IMPI) is used as it is. If the GAA bootstrapping is based on the authentication data from the CS/PS domain, a Private User Identity is derived from user's IMSI according 3GPP TS 23.003 [5] is used.
The Private User Identity is permanent subscriber data and is stored in HSS and in S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.2 Public User Identities | The Public User Identities of an IMS subscriber contain one or several instances of Public User Identity or Wildcarded Public User Identity, which are defined in 3GPP TS 23.003 [5].
The Public User Identities are permanent subscriber data and are stored in HSS, S-CSCF and BSF.
3.1.2A Private Service Identity
The Private Service Identity is applicable to a PSI user and is similar to a private user identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48]. The Private Service Identity is operator defined.
The Private Service Identity is permanent data and is stored in HSS and S-CSCF.
3.1.2B Public Service Identity
The Public Service Identity hosted by an application server may match either to a distinct PSI or a wilcarded PSI that is stored in the HSS. The PSI is defined in 3GPP TS 23.003 [5].
The relationship between Wildcarded Public Service Identities and Private Service Identities is one-to-one.
A Public Service Identity (distinct PSI or Wildcarded PSI) cannot be shared by more than one Private Service Identity.
The Public Service Identity is permanent data and is stored in HSS and S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.3 Barring indication | Flag associated to each Public User Identity to indicate that the identity is barred from any IMS communication. A Public User Identity that is barred is allowed to register with the IMS.
The Barring indication is permanent subscriber data and is stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.4 List of authorized visited network identifiers | The list of authorized visited network identifiers is associated with the Public User Identity to indicate which visited network identifiers are allowed for roaming. If the Public User Identity is part of a set of implicitly registered Public User Identities, the list of authorized visited network identifiers shall be the same for the whole set.
The list of authorized visited network identifiers is permanent subscriber data and is stored in the HSS. This list can be a linear list of visited network identifiers or a compound list of network identifier types e.g. home PLMN or home country; however the exact structure of the list is an implementation option. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.5 Services related to Unregistered State | The Services related to Unregistered State is a parameter associated to each Public User Identity and Public Service Identity and it indicates whether the identity has services related to unregistered state or not. For a Public Service Identity the parameter shall always be set to value indicating that the identity has services related to unregistered state.
The Services related to Unregistered State is permanent subscriber data stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.6 Implicitly Registered Public User Identity Sets | The Implicitly Registered Public User Identity Set contains one or several instances of Public User Identity of an IMS subscriber, and is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.228 [42]. Several Implicitly Registered Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Implicitly Registered Public User Identity Set.
The Implicitly Registered Public User Identity Sets are permanent subscriber data and are conditionally stored in HSS and in S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.7 Default Public User Identity indicator | The Default Public User Identity indicator marks the Public User Identity to be used as default Public User Identity in each Implicitly Registered Public User Identity Set, and is defined in 3GPP TS 29.228 [43]. There shall be one Default Public User Identity per Implicitly Registered Public User Identity Set.
The Default Public User Identity indicator is permanent subscriber data and is conditionally stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.8 PSI Activation State | The PSI Activation State is specific for Public Service Identities and is defined in 3GPP TS 29.328 [54].
The PSI Activation State indicator for distinct PSIs is temporary subscriber data and is stored in the HSS. The PSI Activation State indicator for wildcarded PSIs is permanent subscriber data and is stored in the HSS. A wildcarded PSI or a distinct PSI that matches a wildcarded PSI shall not be activated/deactivated via the Sh interface. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.9 Display Name | The Display Name is a string associated with a Public Identity
The Display Name is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.10 Alias Public User Identity Sets | The Alias Public User Identity Set contains two or more Public User Identities of an IMS subscriber, and these Public User Identities in the set are aliases of each other and their treatment is identical. Several Alias Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Alias Public User Identity Set. All the Public User Identities in every Alias Public User Identity Set shall be included in the same Implicitly Registered Public User Identity Set, and shall be linked to the same Service Profile and share the same service data for each and every service, but there can be more than one Alias Public User Identity Set per Implicitly Registered Public User Identity Set and Service Profile.
The Alias Public User Identity Sets are permanent subscriber data and are conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.11 Loose-Route Indication | The Loose-Route Indication indicates if the loose-route mechanism is required for all the Public User Identities belonging to a Private User Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
The Loose-Route Indication shall have the same value for all the Private Identities of the IMS subscription if at least one Public User Identity is shared by the multiple Private Identities; otherwise, each Private User Identity may have a different Loose-Route Indication value.
The Loose-Route Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.12 Service Priority Level | The Service Priority Level indicates the Priority Level allowed for the Public Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
The Service Priority Level is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.13 Extended Priority | The Extended Priority provides priority information for the Public Identity. It provides support for more than one subscribed namespaces in an operator's network, as included in priority mechanisms described in 3GPP TS 24.229 [68] and it is defined in 3GPP TS 29.228 [43].
The Extended Priority is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.14 Reference Location Information | The Reference Location Information contains the reference location for the Private User Identity (e.g. line identification in the case of fixed line access). It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.167 [89].
The Reference Location Information is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.15 Priviledged-Sender Indication | The Priviledged-Sender Indication indicates if the corresponding Private User Identity shall be considered a priviledged sender. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
If for an IMS subscription at least one Public User Identity is shared by more than one Private Identity, then all these Private Identities shall have the same value for the Priviledged-Sender Indication; otherwise, each Private User Identity may have a different Priviledged-Sender Indication value.
The Priviledged-Sender Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.16 Additional MSISDN (A-MSISDN) | An Additional MSISDN (A-MSISDN) is an MSISDN optionally assigned in addition to the already assigned MSISDN(s) to a user with PS subscription. For the definition of A-MSISDN see 3GPP TS 23.003 [5].
It is a permanent subscriber data stored in the HSS/HLR. It is temporarily stored in the MME, SGSN and AS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2 Data related to registration | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.1 Registration Status | The Registration Status, specified in 3GPP TS 29.228 [43], contains the status of registration of a Public User Identity or a Public Service Identity (i.e. registered, not registered, unregistered). A Public Service Identity shall have only the registration status not registered or unregistered.
The Registration Status is temporary subscriber data and is stored in HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.2 S-CSCF Name | For an IMS subscriber, the S-CSCF Name identifies the S-CSCF allocated to the IMS subscriber when the subscriber is registered to IP Multimedia Services. It is used during mobile terminated sessions set-up and re-registrations.
For a Public Service Identity the S-CSCF Name identities the S-CSCF allocated to the PSI for basic IMS routing. It is used during terminated call set-up for a PSI user.
The S-CSCF Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46].
For an IMS subscriber and PSI user, the S-CSCF Name is temporary data and is stored in HSS.
3.2.2A AS Name
For a PSI user the AS Name identifies the application server hosting the Public Service Identity and is used for direct routing of a Public Service Identity.
The AS Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46].
The AS Name is permanent data and is stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.3 Diameter Client Identity of S-CSCF | The Diameter Client Identity of the S-CSCF identifies the Diameter client in the S-CSCF when the IMS subscriber is registered to IP Multimedia Services or a PSI user has an assigned S-CSCF. It is used in requests sent by the HSS to the S-CSCF. The format of the Diameter Client Identity is the Diameter Identity defined in IETF RFC 3588 [51].
The Diameter Client Identity of the S-CSCF is temporary data and is stored in HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.4 Diameter Server Identity of HSS | The Diameter Server Identity of HSS identifies the Diameter Server in the HSS when the IMS subscriber is registered to IP Multimedia Services or the identity of HSS holding the IMS data of a PSI user. It is used in requests send by the S-CSCF to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51].
For an IMS subscriber and PSI user, the Diameter Server Identity of the HSS is temporary data and is stored in S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.5 UE Not Reachable via IP-SM-GW Flag (UNRI) | The UNRI is temporary subscriber data stored in the HLR/HSS and in the IP-SM-GW (AS). It indicates whether the UE is marked not reachable for short message delivery via the IMS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.6 UE Not Reachable via IP-SM-GW Reason (UNRR) | The UNRR is temporary subscriber data stored in the HLR/HSS. It indicates the reason why MT short message delivery failed at the IP-SM-GW. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.7 S-CSCF Restoration Information | The S-CSCF Restoration Information, specified in 3GPP TS 29.228 [43], contains information for the S-CSCF to restore services for the user, including the list of SIP Proxies in the Path header, the Contact information and the UE's subscription information.
The S-CSCF Restoration Information is temporary subscriber data and is stored in the HSS and S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.8 Maximum Number Of Allowed Simultaneous Registrations | The Maximum Number Of Allowed Simultaneous Registrations per public user identity is specified in 3GPP TS 29.228 [43].
It is permanent subscriber data and is stored in the HSS and S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3 Data related to authentication and ciphering | The Data related to authentication and ciphering are applicable to IMS subscribers only. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.1 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) | For contents of Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token (AUTN) see clause 2.3.2.
A set of quintuplet vectors are calculated in the HSS, and sent from the HSS to the S-CSCF (see 3GPP TS 29.228 [43]).
These data are temporary subscriber data conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2 Data related to SIP Digest Authentication | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2.1 Digest Nonce | The Digest Nonce is a random (non-predictable) value selected by the S-CSCF (see 3GPP TS 29.228 [43]) and used by the client to calculate the authentication response (see IETF RFC 7616 [122]).
The Digest Nonce is temporary subscriber data and is stored in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2.2 Digest HA1 | Digest HA1 is the value calculated as defined in IETF RFC 7616 [122]. It is calculated by the HSS and used by the S-CSCF to create the Expected Response (see 3.3.2.14). It is also used to create the Response-Auth (see 3.3.2.15) after a successful authentication verification has occurred.
HA1 is permanent subscriber data and is stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2.3 Digest Nextnonce | Nextnonce is the nonce the server wishes the client to use for a future authentication response (see IETF RFC 7616 [122]).
Digest Nextnonce is temporary subscriber data and is stored in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2.4 Void | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.2.5 Authentication Pending Flag | The Authentication Pending flag, described in 3GPP TS 29.228 [43], indicates that the authentication of a Public User Identity - Private User Identity pair is pending and waiting for confirmation.
The Authentication Pending Flag is temporary data and is stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.1 Data related to NASS Bundled Authentication | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.3.3.1 Line Identifier List | Line Identifier List contains a list of fixed broadband access line identifiers associated to the user and used by the S-CSCF to authenticate the user.
Line Identifier List is permanent subscriber data and is stored in HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.4 Data related S-CSCF selection information | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.4.1 Server Capabilities | The Server Capabilities contains information to assist the I-CSCF in the selection of a S-CSCF for an IMS subscriber or a PSI user. For definition and handling of the data see 3GPP TS 29.228 [43] and 3GPP TS 29.229 [44].
The Server Capabilities information is permanent data and is stored in HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.4.2 S-CSCF Reassignment Pending Flag | The S-CSCF Reassignment Pending Flag, described in 3GPP TS 29.228 [43] indicates that the subscription can be reassigned to a new S-CSCF (i.e. the current S-CSCF is not responding).
The S-CSCF Reassignment Pending Flag is temporary data and is stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5 Data related to Application and service triggers | For definition and handling of these data see 3GPP TS 23.218 [53]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.1 Void | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.2 Initial Filter Criteria | A set of Initial Filter Criteria are stored for each user, for each application or service that the user request may invoke. The relevant service points of interest are defined in 3GPP TS 23.218 [53] clause 5.2.
Each set of filter criteria includes the Application Server Address, AS priority, Default Handling, Subscribed Media, Trigger Points and Optional Service Information.
For a PSI that is routed according to the basic IMS routing principles, Initial Filter criteria is mandatory in order to route towards the AS hosting the PSI. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.3 Application Server Information | The HSS may store Application Server specific information for each user. This information may include Service Key, Trigger Points, and Service Scripts etc. (see 3GPP TS 23.218 [53] clause 9.3.1) |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.4 Service Indication | The Service Indication, associated with a public user identity, identifies exactly one set of service related transparent data (see 3GPP TS 29.328 [54]), which is stored in an HSS in an operator network. It is defined in 3GPP TS 29.328 [54].
The Service Indication is permanent subscriber data and is stored in the HSS and one or more ASs. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.5 Shared iFC Set Identifier | Shared iFC Set Identifier identify sets of Initial Filter Criteria that may be shared by more than one IMS subscriber or PSI user. The translation from a Shared iFC Set Identifier to the set of initial Filter Criteria is performed in the S-CSCF based on operator configuration.
The Shared iFC Set Identifier are permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.6 Transparent Data | The Transparent Data is information stored in the HSS by the AS per Service Indication and Public User Identity or Public Service Identity (Repository Data). It is defined in 3GPP TS 29.328 [54]. If the Public Service Identity matches a Wildcarded Public Service Identity, the transparent data shall be stored per Wildcarded PSI, and not for each specific Public Service Identity matching that Wildcarded PSI. Transparent Data for Wildcarded Public User Identities shall also be stored per Wildcarded Public User Identity, and not for each identity matching that Wildcarded Public User Identity. Transparent data for an Alias Public User Identity Set shall be stored and shared by each and every Public User Identity within the same Public User Identity Set.
The Transparent Data is temporary subscriber data and is stored in the HSS and one or more ASs. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.5.7 Application Server Identity List | The Application Server Identity List is stored in the HSS per Public User Identity or Public Service Identity and per requested user data (data-reference) for a given expiration time. It identifies the application servers which subscribed to notifications of the user data updates and need to be notified when the data subscribed changes.
Application Server Identity List is temporary data and is stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.6 Data related to Core Network Services Authorization | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.6.1 Subscribed Media Profile Identifier | The Subscribed Media Profile Identifier identifies a set of session description parameters that the IMS subscriber or PSI user is authorized to request. The translation from the Profile Identifier to the set of subscribed media is performed in the S-CSCF based on operator configuration.
The Subscribed Media Profile Identifier is permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.6.2 List of Subscribed IMS Communication Service Identifiers | The list of subscribed IMS Communication Service Identifiers is associated with the IMS Public Identity and identifies the list of IMS communication services that the subscriber is authorized to use as specified in 3GPP TS 23.228 [42]. The syntax of the IMS Communication Service Identifier is defined in 3GPP TS 24.229 [68]. The usage of IMS Communication Service Identifier for policing the allowed IMS communication service is performed in the S-CSCF and in the AS based on operator configuration.
The List of Subscribed IMS Communication Service Identifiers is permanent data stored in the HSS and conditionally in the S-CSCF and AS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.7 Data related to Charging | The following charging function names shall be common to the entire IMS Subscription i.e. the same set of charging function names shall be returned for all the identities inside the same IMS Subscription. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.7.1 Primary Event Charging Function Name | The Primary Event Charging Function Name identifies the primary Online Charging Function, which performs on-line charging. The format is specified in 3GPP TS 29.229 [44].
The Primary Event Charging Function Name is permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.7.2 Secondary Event Charging Function Name | The Secondary Event Charging Function Name identifies the secondary Online Charging Function, which performs on-line charging. The format is specified in 3GPP TS 29.229 [44].
The Secondary Event Charging Function Name is permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.7.3 Primary Charging Collection Function Name | The Primary Charging Collection Function Name identifies the primary Charging Data Function, which provides off-line charging support for IMS subscribers and PSIs. The format is specified in 3GPP TS 29.229 [44].
The Primary Charging Collection Function Name is permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.7.4 Secondary Charging Collection Function Name | The Secondary Charging Collection Function Name identifies the secondary Charging Data Function, which provides off-line charging support for IMS subscribers and PSIs. The format is specified in 3GPP TS 29.229 [44].
The Secondary Charging Collection Function Name is permanent data stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8 Data related to CAMEL Support of IMS Services | The Data related to CAMEL Support of IMS Services are applicable to IMS subscribers only. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8.1 Originating IP Multimedia CAMEL Subscription Information (O‑IM‑CSI) | This data defines the contents of the Originating IP Multimedia CAMEL subscription information used to interwork with the gsmSCF for originating IP multimedia sessions. It consists of:
- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the O-IM-BCSM where service triggering may take place. For O-IM-CSI, the allowed DP values are DP Collected_info, DP Route_Select_Failure.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria. The DP criteria indicates on which criteria the IM-SSF shall access the gsmSCF. DP criteria is associated to each TDP.
TDP
Triggering Criteria (*)
ServiceKey
gsmSCF address
Default Call Handling
DP Collected_ Info
No Criterion
Number criteria
One ServiceKey
One E.164 gsmSCF address
One Default call handling
DP Route_Select_
Failure
No criterion
Cause value criteria
One ServiceKey
One E.164 gsmSCF address
One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.
- CAMEL capability handling. It gives the CAMEL phase associated to the O-IM-CSI (phase 4).
- The CSI state. The CSI state indicates whether the O-IM-CSI is active or not. The CSI state is not sent to the IM-SSF.
- The notification flag, the notification flag indicates whether changes of the O-IM-CSI shall trigger Notification on Change of Subscriber Data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8.2 Terminating IP Multimedia CAMEL Subscription Information (VT‑IM‑CSI) | This data defines the contents of the terminating IP Multimedia CAMEL subscription information used to interwork with the gsmSCF for terminating IP multimedia sessions. It consists of:
- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:
1. DP Value. The DP value identifies the DP in the T-IM-BCSM where service triggering may take place. For VT-IM-CSI, the allowed DP values are DP Terminating_Attempt_Authorised, DP T_Busy, DP T_No_Answer.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.
4. A default Call Handling. The default call handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SFF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.
5. DP criteria. The DP criteria indicates on which criteria the IM-SSF shall access the gsmSCF. DP criteria is associated to each TDP.
TDP
Triggering Criteria (*)
ServiceKey
gsmSCF address
Default Call Handling
DP Terminating_ Attempt_Authorised
No Criterion
One serviceKey
One E.164 gsmSCF address
One Default call handling
DP T_Busy
No criterion
Cause value criteria
One serviceKey
One E.164 gsmSCF address
One Default call handling
DP T_No_Answer
No criterion
Cause value criteria
One
service Key
One E.164 gsmSCF address
One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.
- CAMEL capability handling. It gives the CAMEL phase associated to the VT-IM-CSI (CAMEL phase 4).
- The CSI state indicates whether the VT-IM-CSI is active or not. The CSI state is not sent to the IM-SSF.
- Notification flag. The notification flag indicates whether the change of the VT-IM-CSI shall trigger Notification on Change of Subscriber data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8.3 Dialled Services IP Multimedia CAMEL Subscription Information (D‑IM-CSI) | This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for originating and forwarded IP Multimedia sessions. It is applicable at TDP Analysed Info. It consists of:
- DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items:
1. DP Criterion. It indicates when the IM-SSF shall request gsmSCF for instructions. It is a destination number.
2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.
3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.
4. A default Call Handling. It indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.
- CAMEL capability handling. It indicates the CAMEL phase associated to the D-IM-CSI (CAMEL phase 4).
- CSI state: indicates whether the D-IM-CSI is active or not. The CSI state is not sent to the IM-SSF.
- Notification Flag. It indicates whether the change of the D-IM-CSI shall trigger the Notification on Change of Subscriber Data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8.4 gsmSCF address for IM CSI | This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.8.5 IM-SSF address for IM CSI | This information element contains the IM-SSF address to which Notification on Change of Subscriber Data is to be sent. The IM-SSF address is entered in the HSS/HLR at UE registration and is deleted when the HSS/HLR initiates or is notified of the UE deregistration. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.9 Data related to IMS Service Level Trace | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.9.1 IMS Service Level Trace Information | The IMS Service Level Trace Information is utilised by the S-CSCF and the Application Server to enable service level tracing within the IMS Core Network. The content of the IMS Service Level Trace Information is defined in the management object specified in 3GPP TS 24.323 [111].
The IMS Service Level Trace Information is temporary subscriber data and is stored in the HSS, S-CSCF and Application Server. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10 Data related to Generic Authentication Architecture | The Generic Authentication Architecture (GAA) is independent from CS/PS and IM domains, but it requires a subscription in the HSS for every its users at least in one of the domains for generation of authentication vectors. The need for a GAA specific subscription data in the HSS for GAA specific user identities and/or authorization controls is GAA application dependent. At the same time, GAA shall not be considered as a separate domain in the same sense as the notion of a "domain" is considered for CS and PS.
The Generic Authentication Architecture is defined in 3GPP TS 33.220 [58] and 3GPP TS 29.109 [59]. For data related to GAA, see also the definition of Private User Identity in clause 3.1.1. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.1 GAA Service Type | The GAA Service Type is an enumerated integer, which is defined in 3GPP TS 29.109 [58].
The GAA Service Type is permanent subscriber data and is stored in the HSS, BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.2 GAA Service Identifier | The GAA Service Identifier (GSID) is an integer, which uniquely identifies a GAA Service. For example a set of NAFs belonging to a certain GAA Service Type and owned or managed by a certain operator may provide the same operator specific service and they may use the same GAA Service Identifier to identify their services to BSF. The owner of the user's home HSS may define different GAA Authorization flags and allowed Private User Identities for each GAA Service Identifiers separately.
The GAA Service Identifier is permanent subscriber data and is stored in the HSS, BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.3 GBA User Security Settings | The GBA User Security Settings (GUSS) is identified by a Private User Identity. The GBA User Security Settings contains optional BSF control information (i.e., UICC Security Type and optional Key Lifetime) and a set of User Security Setting (USS).
The GBA User Security Settings is permanent subscriber data and is stored in the HSS, and the BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.4 User Security Setting | The User Security Setting (USS) is unique identified by a combination of Private User Identifiers (IMPI) and GAA Service Identifiers (GSID). The User Security Setting contains a list of allowed public identities for the service and possible authorization flags. No duplicates are allowed.
The User Security Setting is permanent subscriber data and is stored in the HSS, BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.5 User Public Identity | The User Public Identity (UID) is a freely defined string that can be used as user's public identity in a GAA application. A list of allowed User Public Identities is stored for each GAA Service Subscription. A User Public Identity may be connected to several GAA Service Subscription.
The User Public Identity is permanent subscriber data and is stored in the HSS, BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.6 GAA Authorization flag | The GAA Authorization flag is a GAA Service type specific integer code, which authorizes a defined security operation in the GAA service. A list of allowed operations is stored for each GAA Service Subscription.
The values of the authorization flags for each application type using them are listed in TS 29.109 [59]
The Authorization Flag is permanent subscriber data and is stored in the HSS, BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.7 Bootstrapping Transaction Identifier | The Bootstrapping Transaction Identifier (B-TID) identifies the security association between a BSF and a UE after a bootstrapping procedure in GAA. According to 3GPP TS 33.220 [58], the B-TID value shall be also generated in format of NAI by taking the base64 encoded RAND value (see IETF RFC 4648 [123] for description of the base64 encoding scheme) and the BSF server name, i.e. base64 encoded (RAND)@BSF_servers_domain_name.
The Bootstrapping Transaction Identifier is temporary subscriber data and is stored in the BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.8 Key Lifetime | Key Lifetime is an integer which defines the length of the validity period of bootstrapping information in BSF in seconds.
The Key Lifetime is permanent subscriber data and is stored in the HSS, and the BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.9 UICC Security Type | The UICC Security Type indicates the allocation of security procedure inside a User Equipment i.e. are security applications executed entirely inside mobile equipment or also in UICC .
The values of UICC Security Type are defined in TS 29.109 [59]
The UICC Security Type is permanent subscriber data and is stored in the HSS and BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.10 NAF Group | The NAF Group contains one or more NAF Address elements (cf. clause 3.9.12) defining the NAFs that belong to the NAF Group. The NAF Group is identified by NAF Group Identity (cf. clause 3.9.11).
NOTE: The grouping of NAFs is done in each home network separately, i.e. one NAF contacting BSFs in different home networks belongs to different groups in every home network.
The NAF Group Setting is permanent subscriber data and is stored in the BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.11 NAF Group Identity | The NAF Group Identity is a freely defined string that the home operator can uses as a name of a group of NAFs.
The NAF Group Identity is permanent subscriber data and is stored in the HSS and BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.12 NAF Address | The NAF Address is a freely defined string that can be used identify one or more NAFs. The NAF Address may contain a fully qualified domain identifying a single NAF. The NAF Address may also contain a domain name with wildcards "*" and it can be used to identity multiple NAFs.
The NAF Address is permanent subscriber data and is stored in the BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.13 Key Expirytime | Key Expirytime is an integer which defines the expiry time of bootstrapping information in BSF in seconds according to Diameter Time format as specified in IETF RFC 3588[51].
The Key Expirytime is temporary subscriber data and is stored in the BSF and NAF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.14 Boostrapping Info Creation Time | Boostrapping Info Creation Time is an integer which defines the point of time when the corresponding boostrapping information is created in BSF in seconds according. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.10.15 Diameter Server Identity of HSS | The Diameter Server Identity of HSS identifies the HSS storing the GAA specific subscription data for a subscriber. It is used in requests send by the BSF to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51].
The Diameter Server Identity of the HSS is temporary data and is stored in BSF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.11 Definition of subscriber data I-WLAN domain | NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN subscriber data specified in the present Clause are no longer maintained. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.