Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.632  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…   5.3…   5.4…   5.5…   5.6…   6…

 

1  ScopeWord‑p. 6

The present document defines the Stage 2 architecture, procedures, flows and Network Function Services for User Data Interworking, Coexistence and Migration within the 5G System.

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.002: "Network Architecture".
[4]
TS 23.380: "IMS Restoration Procedures".
[5]
TS 23.502: "Procedures for the 5G System; Stage 2".
[6]
TS 33.501: "Security Architecture and Procedures for 5G System".
[7]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[8]
TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[9]
TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses".
[10]
TS 33.203: "3G security; Access security for IP-based services".
[11]
TS 33.220: "3G security; Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA)".
[12]
TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding".
[13]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity".
[14]
TS 23.008: "Organization of subscriber data".
[15]
TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents".
[16]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications; Stage 2".
[17]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[18]
TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
Up

3  Definitions of terms, symbols and abbreviationsWord‑p. 7

3.1  Terms

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  Symbols

Void

3.3  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GS UDR
5G Unified Data Repository
EPS UDR
EPS User Data Repository

4  System architecture

4.1  Architecture for direct UDM-HSS interworking

Figure 4.1-1 shows the reference architecture for direct UDM-HSS interworking.
Reproduction of 3GPP TS 23.632, Figure 4.1-1: Architecture for Direct UDM-HSS interworking
Up
Non-SBA interfaces between the HSS and non-SBA network nodes include interfaces to / from the SMS-GMSC/IWMSC and SMS Router. In the Architecture for direct UDM-HSS interworking , as a deployment option, these Non-SBA interfaces may either be supported by the HSS or by the UDM.
Figure 4.1-2 shows the reference architecture for direct UDM-HSS interworking using the reference point representation.
Reproduction of 3GPP TS 23.632, Figure 4.1-2: Architecture for Direct UDM-HSS interworking in reference point representation
Up
The 5GS-UDR (Unified Data Repository) and EPS-UDR (User Data Repository) may be collocated, forming a common repository.

4.2  Reference points for direct UDM-HSS interworkingWord‑p. 8

The following reference points are realized by service-based interfaces:
NU1:
Reference point between the HSS and the UDM.
NU2:
Reference point between the HSS and the 5GS-UDR.
For a list of other SBA reference points supported in 5GC see TS 23.501.
For a list of IMS reference points, including SBA IMS reference points, see TS 23.228.
For a list of Non-SBA reference points and Network Nodes interfacing the HSS see TS 23.002.
The HSS makes use of the Ud reference point to interact with the EPS-UDR. The UDM makes use of the N35 reference point to interact with the 5GS-UDR.
Up

4.3  Service based interfaces for direct UDM-HSS interworking

Nudm:
Service-based interface exhibited by UDM.
Nhss:
Service-based interface exhibited by HSS.
The HSS shall make use of Nudm services as described in clause 6.2 and may make use of Nudr services as described in clause 6.3.
The UDM shall make use of Nhss services and Nudr services as described in clause 6.1 and clause 6.3.
Up

4.4  Subscription Identifiers

As defined in TS 23.501, for interworking with the EPC, the SUPI allocated to the 3GPP UE shall always be based on an IMSI to enable the UE to present an IMSI to the EPC.
The subscription identifier used over NU1 reference point in Nhss services shall be an IMSI. The UDM extracts the IMSI from the user's SUPI.
The subscription identifier used over NU1 reference point in Nudm services shall be a SUPI based on an IMSI. The HSS creates a SUPI from the user's IMSI or the IMSI associated to the user's public identifier in the EPS or IMS domain (e.g. user's MSISDN or IMPU).
Up

4.5  HSS Discovery and SelectionWord‑p. 9

This clause defines the procedures for HSS discovery and selection by the UDM. The procedures for HSS discovery and selection by SBI capable IMS entities is defined in TS 23.228.
The UDM performs HSS discovery to discover an HSS that manages the user subscriptions in EPC.
The UDM shall utilize the NRF to discover the HSS instance(s) unless the information about HSS instances is available by other means, e.g. locally configured on the UDM. The HSS selection function in UDM selects an HSS instance based on the available HSS instances (obtained from the NRF or locally configured).
When the NRF is used for HSS discovery, the HSS registers in the NRF using the Nnrf_NFManagement_NFRegister Request message as defined in TS 23.502.
Different HSS instances managing different sets of IMSI/MSISDN ranges may be deployed in a given PLMN. In this case, the HSS instances register in NRF using either different ranges of IMSI/MSISDN and/or HSS Group IDs.
When NRF is used for HSS discovery, the UDM sends a Nnrf_NFDiscovery_Request to NRF as defined in TS 23.502 to discover HSS instances within a given PLMN. The UDM may store all returned HSS instances and their NF profiles for subsequent use, including, if applicable, supported IMSI/MSISDN ranges, and/or HSS Group IDs.
The UDM may use Nnrf_NFStatusSubscribe/Unsubscribe service operations with NRF as defined in TS 23.502 to receive Nnrf_NFStatusNotify service operation for updates to the NF profiles of HSS instances registered in NRF.
The UDM always selects an HSS within its own PLMN. The HSS selection should consider one of the following factors when available to the UDM entity:
  1. HSS Group ID of the UE's IMSI.
  2. IMSI; the UDM selects an HSS instance based on the IMSI range the UE's IMSI belongs to or based on the results of a discovery procedure with NRF using the UE's IMSI as input for HSS discovery.
Up

4.6  UDM Discovery and Selection

The HSS performs UDM discovery and selection as described in TS 23.501.

4.7  Subscription Profiles

In the context of Mobility, IMS and SMS use cases, the HSS initiates interworking with the UDM only for UEs which have a 5G subscription that is known to be active in 5GC.
Additionally, the HSS may be aware that a UE for which 5G subscription data exist is not active in 5GC e.g. when the HSS has not yet received an Nhss_UECM_SNDeregistration request from the UDM for that UE (see clause 5.3.3 step 3).
Up

Up   Top   ToC