3 Definition of data for IP Multimedia domain

23.0083GPPOrganization of subscriber dataRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

This clause describes the IMS data for IMS subscribers and PSI users.

3.1 Data related to subscription, identification and numbering

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

3.2 Data related to registration

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.

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.

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.

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.

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.

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.

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.

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.

3.3 Data related to authentication and ciphering

The Data related to authentication and ciphering are applicable to IMS subscribers only.

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.

3.3.2 Data related to SIP Digest Authentication

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.

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.

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.

3.3.2.4 Void

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.

3.3.1 Data related to NASS Bundled Authentication

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.

3.4 Data related S-CSCF selection information

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.

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.

3.5 Data related to Application and service triggers

For definition and handling of these data see 3GPP TS 23.218 [53].

3.5.1 Void

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.

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)

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.

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.

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.

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.

3.6 Data related to Core Network Services Authorization

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

3.9 Data related to IMS Service Level Trace

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

3.11.1 Data related to subscription, identification and numbering

3.11.1.1 IMSI

The International Mobile Subscriber Identity (IMSI) is defined in 3GPP TS 23.003 [5]. The IMSI serves as the root of the subscriber data pseudo-tree.

3.11.1.2 Mobile Subscriber ISDN Number (MSISDN)

Mobile Subscriber ISDN Number (MSISDN) is defined in 3GPP TS 23.003 [5]. One MSISDN is used for WLAN-IW subscription. If the multinumbering option applies, the MSISDN used is the Basic MSISDN (see clause 2.1.3 for more information on MSISDNs for multinumbering option).

3.11.1.3 W-APN

The WLAN Access Point Name (W-APN) is defined in 3GPP TS 23.003 [5]. This parameter identifies a data network and a point of interconnection to that network (Packet Data Gateway).

3.11.1.4 List of authorized visited network identifiers

The list of authorized visited network identifiers field indicates which 3GPP visited network identifiers are allowed for roaming.

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.

3.11.1.5 3GPP AAA Proxy Name

The 3GPP AAA Proxy Name, specified in 3GPP TS 29.234 [63], defines the Diameter or RADIUS Identity of the 3GPP AAA Proxy node.

3.11.1.6 3GPP AAA Server Name

The 3GPP AAA Server Name, specified in 3GPP TS 29.234 [63], defines the Diameter or RADIUS Identity of the 3GPP AAA Server node.

3.11.1.7 Serving PDG List

The Serving PDG List field contains the addresses of the PDGs to which the WLAN UE is connected.

3.11.1.8 Serving WAG

The Serving WAG field contains the WAG address information obtained through the successful user authentication procedure.

3.11.1.9 WLAN UE Local IP Address

The WLAN UE Local IP Address field, specified in 3GPP TS 23.234 [62], represents the IPv4/IPv6 address of the WLAN UE in the WLAN AN. It is an address used to deliver the packet to a WLAN UE in a WLAN AN.

3.11.1.10 WLAN UE Remote IP Address

The WLAN UE Remote IP Address field, specified in 3GPP TS 23.234 [62], represents the IPv4/IPv6 address of the WLAN UE in the network which the WLAN UE is accessing. It is an address used in the data packet encapsulated by the WLAN UE-initiated tunnel and is the source address used by applications in the WLAN UE. The WLAN UE Remote IP address is per W-APN, see clause 3.11.5.1.4.

3.11.2 Data related to registration

3.11.2.1 User Status

The User Status field identifies the registration status of the I-WLAN User. The User Status shall be either REGISTERED, in which case there is an associated Serving 3GPP AAA Server Name stored at the HSS, or NOT_REGISTERED, in which case there may or may not be a 3GPP AAA Server Name stored.

3.11.2.2 Emergency Access Flag

The Emergency Access flag is specified in 3GPP TS 29.234 [63]. It enables operators to control the access to I-WLAN for emergency purposes. The parameter takes either of the following values:

– Access is for emergency purposes.

– Access is not for emergency purposes.

The flag is set in the 3GPP AAA Server if the WLAN Direct IP access is indicated to be for emergency purposes.

3.11.2.3 Diameter Server Identity of HSS

The Diameter Server Identity of HSS identifies the identity of HSS storing the I-WLAN specific subscription data for a subscriber. It is used in requests send by the 3GPP AAA Server 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 3GPP AAA Server.

3.11.3 Data related to authentication and ciphering

3.11.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc)

Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) fields form a triplet vector used for authentication and encryption as defined in 3GPP TS 43.020 [31].

In I-WLAN for SIM based users, triplet vectors are calculated in the 2G AuC and provided to the 2G HLR/HSS (see GSM 12.03 [36]). For USIM based users, triplet vectors are derived from quintuplet vectors in the 3G HLR/HSS if needed (see 3GPP TS 33.102 [52]).

A set of up to 5 triplet values are sent from the 2G HLR/HSS to the 3GPP AAA Server upon request. These data are temporary subscriber data stored in the 3GPP AAA Server.

3.11.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN)

Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) fields form a quintuplet vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.102 [52].

In I‑WLAN, a set of quintuplet vectors are calculated in the AuC, and up to 5 quintuplets are sent from the HLR/HSS to the 3GPP AAA Server upon request (see 3GPP TS 29.002 [27]).

These data are temporary subscriber data stored in the HSS and 3GPP AAA Server.

3.11.3.3 Master Key (MK)

The Master Key (MK) field is defined in 3GPP TS 33.234 [92]. It enables keys to be derived.

3.11.3.4 Transient EAP Keys (TEKs)

The Transient EAP Keys (TEKs) field is defined in 3GPP TS 33.234 [92] and are used to protect the EAP packets.

3.11.3.5 Master Session Key (MSK)

The Master Session Key (MSK) field is defined in 3GPP TS 33.234 [92] and is used to obtain the key material required for the link layer confidentiality mechanism and IPsec confidentiality mechanism.

3.11.4 Data related to session

3.11.4.1 Session Identifier

The Session Identifier field, specified in 3GPP TS 29.234 [63], indicates a unique Diameter signalling session specific to the user.

3.11.4.2 Session-Timeout

The Session-Timeout field, specified in 3GPP TS 29.234 [63], indicates the maximum period for a session measured in seconds. It is used for re-authentication purposes. If this field does not appear, the WLAN AN shall apply default time intervals.

3.11.5 Operator Determined Barring general data

3.11.5.1 W-APN Authorised List

The W-APN Authorised field is specified in 3GPP TS 29.234 [63]. It contains authorization information for each W-APN. This parameter indicates the list of allowed W-APNs, the environment where the access is allowed and optionally the charging data specific for that W-APN and the Static IP address.

3.11.5.1.1 W-APN Identifier List

See clause 3.11.1.3.

3.11.5.1.2 W-APN Barring Type List

The W‑APN Barring Type field is specified in 3GPP TS 29.234 [63]. It indicates the subscriber access type to the home and visited network’s services. The parameter takes either of the following values:

– Allow access to this W‑APN regardless of whether the subscriber is located in a VPLMN or in the HPLMN;

– Prohibit access to this W-APN within the HPLMN when the subscriber is located in a VPLMN;

– Prohibit access to this W-APN within the VPLMN when the subscriber is located in a VPLMN;

– Prohibit access to this W-APN within the HPLMN when the subscriber is located in the HPLMN;

– Prohibit access to public Internet through any W-APN regardless of whether the subscriber is located in a VPLMN or in the HPLMN.

3.11.5.1.3 W-APN Charging Data List

The W‑APN Charging Data field is specified in 3GPP TS 29.234 [63]. When this parameter is present, it supersedes the general charging information to be applied for the subscriber. See clause 3.11.7.

3.11.5.1.4 Static WLAN UE Remote IP Address List

WLAN UE IP Address field identifies the IPv4/IPv6 address that the operator has statically assigned to the WLAN UE. See clause 3.11.1.10.

3.11.5.1.5 Maximum Number of Accesses List

The Maximum Number of Accesses is specified in 3GPP TS 29.234[63]. It enables operators to specify the maximum number of concurrent accesses per W-APN.

3.11.5.1.6 Access Number List

Access Number is an integer counter kept at the 3GPP AAA Server per W-APN.

3.11.5.2 Access Dependence Flag

The Access Dependence Flag is specified in 3GPP TS 29.234 [63]. It enables operators to authenticate a subscriber accessing the I-WLAN by WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access. The parameter takes either of the following values:

– Allow access to WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access.

– Prohibit access to WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access.

3.11.5.3 I-WLAN Access Type

The I-WLAN Access Type field is specified in 3GPP TS 29.234 [63]. It indicates the types of access the subscriber has used to access to the IWLAN. The parameter takes either of the following values:

– WLAN 3GPP IP Access;

– WLAN Direct IP Access.

3.11.5.4 WLAN Direct IP Access

WLAN Direct IP Access (see 3GPP TS 29.234 [63]) is permanent data conditionally stored in HSS. It indicates whether the user is allowed to have WLAN direct IP access to external IP networks from the WLAN Access Network. The WLAN Direct IP Access is stored as temporary data also in the 3GPP AAA Server.

3.11.6 QoS general data

3.11.6.1 Max Subscribed Bandwidth

The Max Subscribed Bandwidth field, specified in 3GPP TS 29.234 [63], indicates the Max subscribed bandwidth.

3.11.6.2 Routing Policy

The Routing Policy field, specified in 3GPP TS 29.234 [63], defines a packet filter for an IP flow.

3.11.6.3 Subscribed 3GPP WLAN QoS Profile

The Subscribed 3GPP WLAN QoS Profile field, specified in 3GPP TS 29.234 [63], defines a subscribed 3GPP WLAN QoS profile per W-APN.

3.11.6.4 Authorized 3GPP WLAN QoS Profile

The Authorized 3GPP WLAN QoS Profile field, specified in 3GPP TS 29.234 [63], defines the authorized 3GPP WLAN QoS profile per W-APN for a user.

3.11.7 Data related to Charging

3.11.7.1 Charging Data

The Charging Data field identifies the Charging Characteristics plus the Charging Nodes to be applied per user for all W‑APNs or per user for individual W‑APNs.

3.11.7.1.1 Charging Characteristics

Charging Characteristics field is defined in 3GPP TS 32.252 [66]. It indicates the charging type to be applied to the user tunnel.

3.11.7.2 Primary OCS Charging Function Name

The Primary OCS Charging Function Name field identifies the Primary OCS Function node that performs on-line based charging. The format is specified in 3GPP TS 29.234 [63].

3.11.7.3 Secondary OCS Charging Function Name

The Secondary OCS Charging Function Name field identifies the Secondary OCS Charging Function node that performs on-line based charging. The format is specified in 3GPP TS 29.234 [63].

3.11.7.4 Primary Charging Collection Function Name

The Primary Charging Collection Function Name field identifies the primary Charging Collection Function node that provides off-line charging support for the IMS subscribers. The format is specified in 3GPP TS 29.234 [63].

3.11.7.5 Secondary Charging Collection Function Name

The Secondary Charging Collection Function Name field identifies the secondary Charging Collection Function node that provides off-line charging support for the IMS subscribers. The format is specified in 3GPP TS 29.234 [63].

3.11.7.6 WLAN Session Identifier

The WLAN Session Identifier is the identifier generated by 3GPP AAA Server and sent to PDG. Togther with PDG Charging Identifier, it is used for correlating WLAN AN and PDG charging data. The format is specified in 3GPP TS 32.299 [67].

3.11.7.7 PDG Charging Identifier

The PDG Charging Identifier is the identifier generated by PDG and sent to 3GPP AAA Server. Togther with WLAN Session Identifier, it is used for correlating WLAN AN and PDG charging data. The format is specified in 3GPP TS 32.299 [67].

3.12 Data related to Access Network Discovery and Selection Function (ANDSF)

3.12.1 General

Following clauses describe the Data that is defined on per user basis and is related to Access Network Discovery and Selection Function (ANDSF).

3.12.2 Policy Information

This set and contains a list of inter-system mobility policies. Each policy contains the following information while the corresponding coding is defined in 3GPP TS 24.312 [86]:

– Rule Priority: indicates the priority of the correspondent intersystem mobility policy;

– Prioritized Access: a set of information providing lists of possible technologies the UE can access. The technologies are prioritized based on operator preferences. It is also possible to indicate an access technology as forbidden or as restricted;

– Validity Area and Time of the Day: these two sets of information indicate where and when the policy can be applied by the UE. Different ways to describe the area of validity of the policy are provided and described in 3GPP TS 24.312 [86]. There can be multiple policies valid (e.g. overlapping validity areas): in this case, the value of Rule Priority is used as discriminator;

– Roaming: it indicates if the policy is also valid if the UE is roaming.

This set is permanent data conditionally stored in the ANDSF.

3.12.3 Discovery Information

This set contains the information regarding the access networks the UE can discover.

It contains the following information while the corresponding coding is defined in 3GPP TS 24.312 [86]:

– Access Network Type: indicates the type of the network for which discovery assistance information is provided;

– Access Network Area: describes the location where the access network indicated in the correspondent Access Network Type is expected to be available. Different ways to describe the area of validity of the policy are provided in 3GPP TS 24.312 [86];

– Access Network Information Reference: is a pointer to a set containing the relevant information for the networks the UE can discover (e.g. SSIDs and correspondent channels in case of WLAN access).

This set is permanent data conditionally stored in the ANDSF.

3.12.4 UE Location

This set provides information about the UE location, i.e. it is a way to indicate the position of the UE. This information can be used by ANDSF to limit the number of information sent to the UE. Different ways to describe the UE location are provided in 3GPP TS 24.312 [86].

This set is temporary data conditionally stored in the ANDSF.

3.13 Proximity Services (ProSe)

3.13.1 General

Following clauses describe the data that are defined on per user basis and are related to Proximity Services (ProSe).

3.13.2 ProSe Subscription data

3.13.2.1 ProSe-Permission

The ProSe-permision is part of the ProSe Subscription data information and is specified in 3GPP TS 29.344 [99].

ProSe-permission is permanent data conditionaly stored in HSS, MME and ProSe Function.

3.13.2.2 PLMN-Allowed-ProSe

The PLMN-Allowed-ProSe is part of the ProSe Subscription data and is specified in 3GPP TS 29.344 [99].

PLMN-Allowed-ProSe is permanent data conditionally stored in HSS, MME and ProSe Function.

3.13.3 Application layer user ID

The Application layer user ID is specified in 3GPP TS 23.303 [98].

Application layer user ID is permanent data conditionally stored in ProSe Function and ProSe Application Server.

3.13.4 EPC ProSe User ID

The EPC ProSe User user ID is specified in 3GPP TS 23.003 [5].

EPC ProSe User ID is temporary data conditionally stored in ProSe Function, ProSe Application Server

3.13.5 ProSe Application ID

The ProSe Application ID is specified in 3GPP TS 23.003 [5].

ProSe Application ID is permanent data conditionally stored in ProSe Function.

3.13.6 ProSe Application Code

The ProSe Application Code is specified in 3GPP TS 23.003 [5].

ProSe Application Code is temporary data conditionally stored in ProSe Function.

3.13.7 Discovery Filter

3.13.7.1 Filter ID

The Filter ID part of the Discovery Filter is specified in 3GPP TS 24.334 [100].

Filter ID is permanent data conditionally stored in ProSe Function.

3.13.7.2 ProSe Application Code

The ProSe Application Code as part of the Discovery Filter is specified in 3GPP TS 23.003 [5].

ProSe Application Code is permanent data conditionally stored in ProSe Function.

3.13.7.3 ProSe Application Mask

The ProSe Application Mask as part of the Discovery Filter is specified in 3GPP TS 24.334 [100].

ProSe Application Mask as part of the discovery filter is permanent data conditionally stored in ProSe Function.

3.13.7.4 TTLTimer T4002

The TTLTimer T4002 as part of the Discovery Filter is specified in 3GPP TS 24.334 [100].

The TTLTimer T4002 as part of the discovery filter is permanent data conditionally stored in ProSe Function.

3.13.8 ProSe Function Identity

ProSe Function Identity is specified in 3GPP TS 29.344 [99].

The ProSe Function Identity is temporary subscriber data and is conditionaly stored in the HSS and in the ProSe Application Server.

3.13.9 ProSe Metadata Index Mask

The ProSe Metadata Index Mask indicates which part of the ProSe Application Code contains the metadata index. It is specified in 3GPP TS 24.334 [100].

ProSe Metadata Index Mask is permanent data conditionally stored in ProSe Function.

3.13.10 PC5-tech

The PC5-tech indicates the PC5 radio technology in order to enable co-ordination between the announcing and monitoring side. It is specified in 3GPP TS 24.334 [100].

PC5-tech is temporary data conditionally stored in ProSe Function.

3.14 Architecture Enhancements for Service Exposure (AESE)

3.14.1 General

Following clauses describe the data that are defined on a per user basis and are related to Architecture Enhancements for Service Exposure (AESE).

3.14.2 SCEF-Reference-ID

SCEF-Reference-ID is defined in 3GPP TS 29.336 [103].

SCEF-Reference-ID is used to uniquely identify an event created by an SCEF.

SCEF-Reference-ID is temporary data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.3 SCEF-ID

SCEF-ID is defined in 3GPP TS 29.336 [103].

SCEF-ID is used to uniquely identify an SCEF.

SCEF-ID is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.4 Monitoring-Type

Monitoring-Type is defined in 3GPP TS 29.336 [103].

Monitoring-Type is used to identify type the event to be monitored.

Monitoring-Type is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.5 Maximum-Number-of-Reports

Maximum-Number-of-Reports is defined in 3GPP TS 29.336 [103].

Maximum-Number-of-Reports is used to indicate the number of reports to be delivered to the SCEF.

Maximum-Number-of-Reports is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.6 UE-Reachability-Configuration

UE-Reachability-Configuration number is defined in 3GPP TS 29.336 [103].

UE-Reachability-Configuration contain details for configuration for UE reachability.

UE-Reachability-Configuration is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.7 Monitoring-Duration

Monitoring-Duration is defined in 3GPP TS 29.336 [103].

Monitoring-Duration indicates the time for which the SCEF request to perform the monitoring.

Monitoring-Duration is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.8 Maximum-Detection-Time

Maximum-Detection-Time is defined in 3GPP TS 29.336 [103].

Maximum-Detection-Time contains the maximum number of time without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable.

Maximum-Detection-Time is permanent data conditionaly stored in the SCEF and HSS.

3.14.9 Reachability-Type

Reachability-Type is defined in 3GPP TS 29.336 [103].

Reachability-Type indicates for which kind of reachability of the subscriber needs to be reported i.e. reachable for SMS or data.

Reachability-Type is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.10 Maximum-Latency

Maximum Latency is defined in 3GPP TS 29.336 [103].

Maximum Latency contains the maximum acceptable delay time for downlink data transfer.

Maximum Latency is permanent data conditionaly stored in the SCEFand HSS.

3.14.11 Maximum-Response-Time

Maximum Response Time is defined in 3GPP TS 29.336 [103].

Maximum Response Time contains the maximum time for which the UE stays reachable.

Maximum Response Time is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.12 MONTE-Location-Type

MONTE-Location-Type is defined in 3GPP TS 29.336 [103].

MONTE-Location-Type indicates how actual the location information should be.

Location-Type is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.13 Accuracy

Accuracy is defined in 3GPP TS 29.336 [103].

Accuracy is used to indicate in which form geographic location information has to be provided in the report. Accuracy is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.14 Association-Type

Association-Type is defined in 3GPP TS 29.336 [103].

Association-Type indicates which kind (IMEI or SV) of change of the IMEI has to be reported. Association-Type is permanent data conditionaly stored in the SCEF and HSS.

3.14.15 Charged-Party

Charged-Party is defined in 3GPP TS 32.299 [67].

Charged-Party holds the address (Public User ID: SIP URI, Tel URI, etc.) of the party to be charged.

Charged-Party is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.16 Remaining-number-of-reports

Remaining number of reports is defined in 3GPP TS 29.336 [103].

Remaining number of reports holds the number of reports which are outstanding to be sent to the SCEF. Remaining number of reports is temporary data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.17 Communication Pattern set

3.14.17.1 Periodic-Communication-Indicator

Periodic-Communication-Indicator is defined in 3GPP TS 29.336 [103].

Periodic-Communication-Indicator provides information if the CP occurs periodically or on demand.

Periodic-Communication-Indicator is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.17.2 Communication-Duration-Time

Communication-duration-time is defined in 3GPP TS 29.336 [103].

Communication-duration-time contains the time in seconds of the duration of the periodic communication.

Communication-duration-time is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.17.3 Periodic-Time

Periodic-Time is defined in 3GPP TS 29.336 [103].

Periodic-Time contains the time in seconds of the interval for periodic communication.

Periodic-Time is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.17.4 Scheduled-Communication-Time

Scheduled-Communication-Time is defined in 3GPP TS 29.336 [103].

Scheduled-Communication-Time contains start and end times and repetion during a week for periodic communication.

Scheduled-Communication-Time is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.17.5 Stationary-Indication

Stationary-Indication is defined in 3GPP TS 29.336 [103].

Stationary-Indication contains the information if the subscriber is stationary or mobile.

Stationary-Indication is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.17.6 Validity-Time

Validity-Time is defined in 3GPP TS 29.336 [103].

Validity-Time provides the expiration time at which the CP sets shall be deleteted.

Validity-Time is permanent data conditionaly stored in the SCEF, HSS and MME.

3.14.18 AESE-Subscription-Data

AESE-Subscription-Data contains details on subscription information of the allowed services such as:

-allowed service (e.g. monitoring, CP set);

-allowed service types (e.g. allowed Monitoring events).

AESE-Subscription-Data is permanent data conditionally stored in the HSS.

3.14.19 SCEF-Realm

SCEF-Realm is defined in 3GPP TS 29.272 [81].

SCEF-Realm is used to identify the realm of the SCEF.

SCEF-Realm is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN.

3.14.20 External Identifier for Monitoring Event Configuration

The External Identifier for Monitoring Event Configuration contains an External Identifier as defined in 3GPP TS 23.003 [5] and identifies the External Identifier in the subscription that is associated to each Monitoring Event Configuration (MONTE) data instance.

The External Identifier for each Monitoring Event Configuration is permanent subscriber data and is stored in the HSS and conditionally in the SCEF, MME and SGSN.

3.14.21 External Group Identifier

The External Group Identifier contains an External Group Identifier as defined in 3GPP TS 23.003 [5].

The External Group Identifier for Monitoring Event Configuration is permanent subscriber data and is stored in the HSS and conditionally in the SCEF.

3.15 Data related to WebRTC

3.15.1 Allowed WAF and/or WWSF Identity List

An Allowed WAF or WWSF Identity identifies a WebRTC Authentication Function or WebRTC Web Server Function the subscription is allowed to use. See 3GPP TS 33.203 [49]. Multiple WAF or WWSF identities may be stored within the Allowed WAF and/or WWSF Identity List.

The Allowed WAF and/or WWSF Identity List is permanent data stored in the HSS and in the S-CSCF.

3.16 V2X Service (V2X)

3.16.1 General

Following clauses describe the data that are defined on per user basis and are related to V2X Service (V2X).

3.16.2 V2X Subscription data for the network scheduled LTE sidelink communication

3.16.2.1 V2X-Permission

The V2X-Permision is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81].

V2X-Permission is permanent data conditionally stored in HSS and MME.

3.16.2.2 UE-PC5-AMBR

The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81].

UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.

3.16.2.3 V2X-PC5-Allowed-PLMN

The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108].

V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function.

3.16.3 V2X Authorization data

3.16.3.1 V2X-Permission-in-VPLMN

The V2X-Permision-VPLMN is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].

V2X-Permission-in-VPLMN is permanent data conditionally stored in V2X Control Function.

3.16.3.2 V2X-Application-Server

The V2X-Application-Server is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].

V2X-Application-Server is permanent data conditionally stored in V2X Control Function.

3.16.3.3 PC5-RAT-Type

The PC5-RAT-Type is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].

PC5-RAT-Type is permanent data conditionally stored in HSS and V2X Control Function.

3.16.4 V2X Control Function Identity

V2X Function Identity is specified in 3GPP TS 29.388 [108].

The V2X Control Function Identity is temporary subscriber data and is conditionally stored in the HSS.

3.16.5 V2X Subscription data for the network scheduled NR sidelink communication

3.16.5.1 V2X-Permission

The V2X-Permision is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].

V2X-Permission is permanent data conditionally stored in HSS and MME.

3.16.5.2 UE-PC5-AMBR

The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].

UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.

3.16.5.3 V2X-PC5-Allowed-PLMN

The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108].

V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function.

3.16.5.4 UE-PC5-QoS

The UE-PC5-QoS is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].

UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.