3GPP TS 23.502: 5G系统程序规范

需积分: 10 41 浏览量更新于2024-07-17 收藏 2.7MB PDF 举报

"TS_123502v150300p_5G系统程序" 3GPP技术规范TS_123502v150300p是关于5G系统（第五代移动通信系统）的程序详细说明。此文档由欧洲电信标准协会（ETSI）3rd Generation Partnership Project（3GPP）制定。3GPP是一个国际组织，负责制定全球移动通信标准，包括UMTS（第三代合作伙伴项目）和GSM（全球系统移动通信）等身份的技术规范和报告。本技术规范可能引用了具有3GPP标识、UMTS标识或GSM标识的其他技术规范或报告。这些引用应理解为对应于ETSI交付物的参考。TS123502V15.3.0是2018年9月发布的一个版本，属于3GPP Release 15系列，这标志着5G技术的一个关键阶段，该阶段着重于5G网络的初始部署和功能定义。关键词“5G”表明，这份文档的核心内容涉及5G网络的操作流程和规范，涵盖了与5G系统相关的各种协议和交互过程。这些流程可能包括但不限于网络接入、会话管理、移动性管理、数据传输以及与其他网络（如4G LTE）的互操作性。文档中可能详细描述了以下方面： 1. **网络接入**：用户设备（UE）如何与5G网络建立连接，包括初始接入过程、认证和授权机制。 2. **会话管理**：如何建立、修改和释放会话，支持不同类型的业务和服务。 3. **移动性管理**：UE在不同5G小区间的移动时，如何进行无缝切换，保持连接稳定。 4. **服务连续性**：确保在不同网络技术之间（如4G到5G）的服务连续性。 5. **网络切片**：5G引入了网络切片的概念，允许为不同的服务类型创建定制的虚拟网络，这部分可能会详细说明切片的管理和配置。 6. **控制面和用户面协议**：定义了5G系统中的控制层面和用户面的通信规则。 7. **频谱效率**：如何高效利用5G频谱资源，包括载波聚合、多址接入技术等。 8. **安全**：包括用户数据保护、网络间的信任模型以及安全认证流程。由于3GPP Release 15是5G标准化过程中的一个关键里程碑，因此这份技术规范对于理解5G网络的运作原理和设计原则至关重要。对于开发者、网络运营商、设备制造商和研究人员来说，它是深入研究5G技术的必要参考资料。任何对本规范内容的修改或更新都需要ETSI的书面许可，以确保技术的一致性和可靠性。

ETSI

ETSI TS 123 502 V15.3.0 (2018

09)

3GPP TS 23.502 version 15.3.0 Release 15

[22] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".

[23] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data

networks and applications".

[24] 3GPP TS 23.203: "Policy and charging control architecture".

[25] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".

[26] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".

[27] OMA-TS-ULP-V2_0_3: "UserPlane Location Protocol".

[28] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".

[29] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".

[30] 3GPP TS 36.355: "LTE Positioning Protocol (LPP)".

[31] 3GPP TS 38.455: "NR Positioning Protocol A (NRPPa)".

[32] 3GPP TS 29.507: "Access and Mobility Policy Control Service; Stage 3".

[33] 3GPP TS 23.003: "Numbering, Addressing and Identification".

[34] 3GPP TS 32.240: "Charging management; Charging architecture and principles".

[35] 3GPP TS 23.251: "Network sharing; Architecture and functional description".

[36] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3".

[37] 3GPP TS 29.510: "5G System; Network function repository services; Stage 3".

[38] 3GPP TS 23.380: "IMS Restoration Procedures".

[39] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace

concepts and requirements".

[40] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".

3 Definitions, symbols and abbreviations

3.1 Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2] and

TS 23.503 [20] apply. A term defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the

same term, if any, in any other specifications.

3.2 Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [20]

apply. An abbreviation defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the same

abbreviation, if any, in any other specifications.

4 System procedures

4.1 General

The clause 4 describes the procedures and Network Function services for the 5GS by end-to-end information flows, and

these information flows make use of NF service operations, defined in clause 5, for the communication within the 5GC

Control Plane.

ETSI

ETSI TS 123 502 V15.3.0 (2018

09)

3GPP TS 23.502 version 15.3.0 Release 15

4.2 Connection, Registration and Mobility Management

procedures

4.2.1 General

The Connection Management is used to establish and release the Control Plane signalling connection between the UE

and the AMF. The Registration Management is used to register or deregister a UE/user with the 5GS, and establish the

user context in the 5GS. The Mobility Management functions are used to keep track of the current location of a UE. The

procedures in clause 4.2 provides Connection, Registration and Mobility Management functionality.

4.2.2 Registration Management procedures

4.2.2.1 General

The Registration and Deregistration procedures in clause 4.2.2 provides the required functionality to register or

deregister a UE/user with the 5GS. Additional functionality to support Registration Management for non-3GPP access

is defined in clause 4.12. Additional functionality to support Registration Management for specific services such as

SMS over NAS is defined in clause 4.13.

4.2.2.2 Registration procedures

4.2.2.2.1 General

A UE needs to register with the network to get authorized to receive services, to enable mobility tracking and to enable

reachability. The Registration procedure is used when the UE needs to perform:

- Initial Registration to the 5GS;

- Mobility Registration Update upon changing to a new Tracking Area (TA) outside the UE's Registration Area in

both CM-CONNECTED and CM-IDLE state, or when the UE needs to update its capabilities or protocol

parameters that are negotiated in Registration procedure with or without changing to a new TA;

- Periodic Registration Update (due to a predefined time period of inactivity); or

- Emergency Registration.

The General Registration call flow in clause 4.2.2.2.2 applies on all these Registration procedures, but the periodic

registration need not include all parameters that are used in other registration cases.

Aspects related to dual registration in 3GPP and non-3GPP access are described in clause 4.12. The general Registration

call flow in clause 4.2.2.2.2 is also used for the case of registration in 3GPP access when the UE is already registered in

a non-3GPP access, and vice versa. Registration in 3GPP access when the UE is already registered in a non-3GPP

access scenario may require an AMF change, as further detailed in clause 4.12.8.

The general Registration call flow in clause 4.2.2.2.2 is also used by UEs in limited service state (see TS 23.122 [22])

registering for emergency services only (referred to as Emergency Registration), see TS 23.501 [2] clause 5.16.4.

During the initial registration the PEI is obtained from the UE. The AMF operator may check the PEI with an EIR. The

AMF passes the PEI (IMEISV) to the UDM, to the SMF and the PCF, then UDM may store this data in UDR by

Nudr_SDM_Update.

NOTE 1: The use of NSI ID in the 5GC is optional and depends on the deployment choices of the operator.

During the registration the Home Network can provide Steering of Roaming information to the UE via the AMF (i.e. a

list of preferred PLMN/access technology combinations or HPLMN indication that 'no change of the "Operator

Controlled PLMN Selector with Access Technology" list stored in the UE is needed). The Home Network can include

an indication for the UE to send an acknowledgement of the reception of this information. Details regarding the

handling of Steering of Roaming information including how this information is managed between the AMF and the UE

are defined in TS 23.122 [22].

ETSI

ETSI TS 123 502 V15.3.0 (2018

09)

3GPP TS 23.502 version 15.3.0 Release 15

1. UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI,

last visited TAI (if available), Security parameters, Requested NSSAI, [Mapping Of Requested NSSAI], Default

Configured NSSAI Indication, UE Radio Capability Update, UE MM Core Network Capability, PDU Session

status, List Of PDU Sessions To Be Activated, Follow-on request, MICO mode preference, Requested DRX

parameters, [LADN DNN(s) or Indicator Of Requesting LADN Information]) and UE Policy Container (the list

of PSIs, indication of UE support for ANDSP)).

In the case of NG-RAN, the AN parameters include e.g. SUCI or the 5G-GUTI, the Selected PLMN ID and

Requested NSSAI, the AN parameters also include Establishment cause. The Establishment cause provides the

reason for requesting the establishment of an RRC connection.

The Registration type indicates if the UE wants to perform an Initial Registration (i.e. the UE is in RM-

DEREGISTERED state), a Mobility Registration Update (i.e. the UE is in RM-REGISTERED state and initiates

a Registration procedure due to mobility or due to the UE needs to update its capabilities or protocol parameters,

or to request a change of the set of network slices it is allowed to use), a Periodic Registration Update (i.e. the

UE is in RM-REGISTERED state and initiates a Registration procedure due to the Periodic Registration Update

timer expiry, see clause 4.2.2.2.1) or an Emergency Registration (i.e. the UE is in limited service state).

When the UE is performing an Initial Registration the UE shall indicate its UE identity in the Registration

Request message as follows, listed in decreasing order of preference:

- a native 5G-GUTI assigned by the PLMN to which the UE is attempting to register, if available;

- a native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register,

if available;

- a native 5G-GUTI assigned by any other PLMN, if available.

NOTE 1: This can also be a 5G-GUTIs assigned via another access type.

- Otherwise, the UE shall include its SUCI in the Registration Request as defined in TS 33.501 [15].

When the UE is performing an Initial Registration (i.e., the UE is in RM-DEREGISTERED state) with a native

5G-GUTI then the UE shall indicate the related GUAMI information in the AN parameters. When the UE is

performing an Initial Registration with its SUCI, the UE shall not indicate any GUAMI information in the AN

parameters.

If the UE previously received a UE Configuration Update Command indicating that the UE needs to re-register

and that it shall not provide the 5G-GUTI in access stratum signalling when performing the Registration

procedure, the UE performs a Mobility Registration and shall not include any GUAMI information in the AN

parameters. For an Emergency Registration, the SUCI shall be included if the UE does not have a valid 5G-

GUTI available; the PEI shall be included when the UE has no SUPI and no valid 5G-GUTI. In other cases, the

5G-GUTI is included and it indicates the last serving AMF.

The UE may provide the UE's usage setting based on its configuration as defined in TS 23.501 [2]

clause 5.16.3.7. In case of Initial Registration or Mobility Registration Update, the UE includes the Mapping Of

Requested NSSAI (if available), which is the mapping of each S-NSSAI of the Requested NSSAI to the HPLMN

S-NSSAIs, to ensure that the network is able to verify whether the S-NSSAI(s) in the Requested NSSAI are

permitted based on the Subscribed S-NSSAIs.

The UE includes the Default Configured NSSAI Indication if the UE is using a Default Configured NSSAI, as

defined in TS 23.501 [2].

In the case of Mobility Registration Update, the UE includes in the List Of PDU Sessions To Be Activated the

PDU Sessions for which there are pending uplink data. When the UE includes the List Of PDU Sessions To Be

Activated, the UE shall indicate PDU Sessions only associated with the access the Registration Request is related

to. In some cases (see TS 24.501 [25]) the UE may include PDU Sessions in the List Of PDU Sessions To Be

Activated even if there are no pending uplink data for those PDU Sessions.

NOTE 2: A PDU Session corresponding to a LADN is not included in the List Of PDU Sessions To Be Activated

when the UE is outside the area of availability of the LADN.

The UE MM Core Network Capability is provided by the UE and handled by AMF as defined in TS 23.501 [2]

clause 5.4.4a The UE includes in the UE MM Core Network Capability an indication if it supports Request Type

ETSI

ETSI TS 123 502 V15.3.0 (2018

09)

3GPP TS 23.5

02 version 15.3.0 Release 15

flag "handover" for PDN connectivity request during the attach procedure as defined in clause 5.17.2.3.1 of

TS 23.501 [2].

The UE may provide either the LADN DNN(s) or an Indication Of Requesting LADN Information as described

in TS 23.501 [2] clause 5.6.5.

If available, the last visited TAI shall be included in order to help the AMF produce Registration Area for the

UE.

The Security parameters are used for Authentication and integrity protection, see TS 33.501 [15]. Requested

NSSAI indicates the Network Slice Selection Assistance Information (as defined in clause 5.15 of

TS 23.501 [2]). The PDU Session status indicates the previously established PDU Sessions in the UE. When the

UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the

PDU Session status indicates the established PDU Session of the current PLMN in the UE.

The Follow-on request is included when the UE has pending uplink signalling and the UE doesn't include List Of

PDU Sessions To Be Activated, or the Registration type indicates the UE wants to perform an Emergency

Registration. In Initial Registration and Mobility Registration Update, UE provides the UE Requested DRX

parameters, as defined in clause 5.4.5 of TS 23.501 [2].

The UE provides UE Radio Capability Update indication as described in TS 23.501 [2].

The UE access selection and PDU session selection identifies the list of UE access selection and PDU session

selection policy information stored in the UE, defined in clause 6.6 of TS 23.503 [20]. They are used by the PCF

to determine if the UE has to be updated with new PSIs or if some of the stored ones are no longer applicable

and have to be removed.

2. If a 5G-GUTI is not included or the 5G-GUTI does not indicate a valid AMF the (R)AN, based on (R)AT and

Requested NSSAI, if available, selects an AMF

The (R)AN selects an AMF as described in TS 23.501 [2], clause 6.3.5. If UE is in CM-CONNECTED state, the

(R)AN can forward the Registration Request message to the AMF based on the N2 connection of the UE.

If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request to an AMF which has been

configured, in (R)AN, to perform AMF selection.

3. (R)AN to new AMF: N2 message (N2 parameters, Registration Request (as described in step 1) and UE Policy

Container.

When NG-RAN is used, the N2 parameters include the Selected PLMN ID, Location Information and Cell

Identity related to the cell in which the UE is camping, UE Context Request which indicates that a UE context

including security information needs to be setup at the NG-RAN.

When NG-RAN is used, the N2 parameters also include the Establishment cause.

Mapping Of Requested NSSAI is provided only if available.

If the Registration type indicated by the UE is Periodic Registration Update, then steps 4 to 20 may be omitted.

4. [Conditional] new AMF to old AMF: Namf_Communication_UEContextTransfer (complete Registration

Request) or new AMF to UDSF: Nudsf_Unstructured Data Management_Query().

(With UDSF Deployment): If the UE's 5G-GUTI was included in the Registration Reqest and the serving AMF

has changed since last Registration procedure, new AMF and old AMF are in the same AMF Set and UDSF is

deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using

Nudsf_UnstructuredDataManagement_Query service operation or they can share stored UE context via

implementation specific means if UDSF is not deployed. This includes also event subscription information by

each NF consumer for the given UE. In this case, the new AMF uses integrity protected complete Registration

request NAS message to perform and verify integrity protection.

(Without UDSF Deployment): If the UE's 5G-GUTI was included in the Registration Request and the serving

AMF has changed since last Registration procedure, the new AMF may invoke the

Namf_Communication_UEContextTransfer service operation on the old AMF including the complete

Registration Request NAS message, which may be integrity protected, to request the UE's SUPI and UE

Context. See clause 5.2.2.2.2 for details of this service operation. In this case, the old AMF uses either 5G-GUTI

剩余328页未读，继续阅读

黎翔

粉丝: 73
资源: 25

3GPP TS 23.502: 5G系统程序规范

5G通信流程3gpp标准文档23502-g00，包含中英文对照翻译

5G系列规范列表

23502-g20.zip

ts_123501v150300p_SystemArchitectureforthe5GSystem

TEAM Gsystem游戏发布系统 v1.0.rar

5G系统最新规范

潮流计算+二阶锥松弛+对偶形式的matlab源码+对偶理论说明文档.zip

Java贪吃蛇小游戏.zip学习资料资源

计算机网络常用命令详解及实验指导

MC-我的世界Python最佳实践！

最新资源