个人在学习5G标准3GPP TS 23501-g51过程中，也发现google的机器翻译实在晦涩难懂，所以个人在借助百度翻译（中国人更懂中文）的同时，人工对每句话进行了校对。
在自己学习的同时，也将翻译内容分享给给广大网友。由于个人能力有限，翻译不到位的地方还请各位网友们指正。
A UE/user needs to register with the network to receive services that requires registration. Once registered and if applicable the UE updates its registration with the network (see TS 23.502 [3]):
UE/用户需要向网络注册以接收需要注册的服务。一旦注册并且如果可用，UE更新其在网络中的注册：
- periodically, in order to remain reachable (Periodic Registration Update); or
- upon mobility (Mobility Registration Update); or
- to update its capabilities or re-negotiate protocol parameters (Mobility Registration Update).
The Initial Registration procedure involves execution of Network Access Control functions as defined in clause 5.2 (i.e. user authentication and access authorization based on subscription profiles in UDM). As result of the Registration procedure, the identifier of the serving AMF serving the UE in the access through which the UE has registered will be registered in UDM.
Initial Registration程序涉及执行Network Access Control功能（即基于UDM中的订阅配置文件的用户身份验证和访问授权）。作为Registration过程的结果，在UE已注册的接入中为UE服务的服务AMF的标识符将注册在UDM中。
The registration management procedures are applicable over both 3GPP access and Non-3GPP access. The 3GPP and Non-3GPP RM states are independent of each other, see clause 5.3.2.4.
注册管理程序适用于3GPP接入和Non-3GPP接入。3GPP和Non-3GPP RM状态相互独立。
Two RM states are used in the UE and the AMF that reflect the registration status of the UE in the selected PLMN:
在UE和AMF中使用两种RM状态，它们反映了UE在所选PLMN中的注册状态：
- RM-DEREGISTERED.
- RM-REGISTERED.
In the RMDEREGISTERED state, the UE is not registered with the network. The UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF. However, some parts of UE context may still be stored in the UE and the AMF e.g. to avoid running an authentication procedure during every Registration procedure.
在RMDEREGISTERED状态下，UE未向网络注册。AMF中的UE上下文不包含UE的有效位置或路由信息，因此AMF无法访问UE。然而，UE上下文的一些部分仍然可以存储在UE和AMF中，例如，以避免在每个注册过程期间运行认证过程。
In the RM-DEREGISTERED state, the UE shall:
- attempt to register with the selected PLMN using the Initial Registration procedure if it needs to receive service that requires registration (see TS 23.502 [3] clause 4.2.2.2).
-如果所选PLMN需要接收需要注册的服务，则尝试使用初始注册过程向其注册。
- remain in RM-DEREGISTERED state if receiving a Registration Reject upon Initial Registration (see TS 23.502 [3] clause 4.2.2.2).
-如果在初始注册时收到注册拒绝，则保持RM-DEREGISTERED状态。
- enter RM-REGISTERED state upon receiving a Registration Accept (see TS 23.502 [3] clause 4.2.2.2).
-收到注册接受后进入RM-REGISTERED状态。
When the UE RM state in the AMF is RM-DEREGISTERED, the AMF shall:
- when applicable, accept the Initial Registration of a UE by sending a Registration Accept to this UE and enter RM-REGISTERED state for the UE (see TS 23.502 [3] clause 4.2.2.2); or
-在适用时，通过向该UE发送Registration Accept来接受UE的Initial Registration，并使该UE进入RM-REGISTERED状态；或者
- when applicable, reject the Initial Registration of a UE by sending a Registration Reject to this UE (see TS 23.502 [3] clause 4.2.2.2).
-在适用时，通过向该UE发送Registration Reject来拒绝UE的Initial Registration。
In the RMREGISTERED state, the UE is registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network.
在RM-REGISTERED状态下，UE在网络中注册。在RM-REGISTERED状态下，UE可以接收需要向网络注册的服务。
In the RM-REGISTERED state, the UE shall:
- perform Mobility Registration Update procedure if the current TAI of the serving cell (see TS 37.340 [31]) is not in the list of TAIs that the UE has received from the network in order to maintain the registration and enable the AMF to page the UE;
-如果服务小区的当前TAI不在UE从网络接收到的TAI列表中，则执行Mobility Registration Update过程，以维持注册并使AMF能够寻呼UE；
- perform Periodic Registration Update procedure triggered by expiration of the periodic update timer to notify the network that the UE is still active.
-执行由周期更新定时器到期触发的Periodic Registration Update过程，以通知网络UE仍然处于活动状态。
- perform a Mobility Registration Update procedure to update its capability information or to re-negotiate protocol parameters with the network;
-执行Mobility Registration Update过程以更新其能力信息或与网络re-negotiate协议参数；
- perform Deregistration procedure (see TS 23.502 [3] clause 4.2.2.3.1), and enter RM-DEREGISTERED state, when the UE needs to be no longer registered with the PLMN. The UE may decide to deregister from the network at any time.
-当UE不再需要向PLMN注册时，执行Deregistration过程，并进入RM-DEREGISTERED状态。UE可以随时决定从网络注销。
- enter RM-DEREGISTERED state when receiving a Registration Reject message or a Deregistration message. The actions of the UE depend upon the 'cause value' in the Registration Reject or Deregistration message. See TS 23.502 [3] clause 4.2.2.
-收到Registration Reject消息或Deregistration消息时，进入RM-DEREGISTERED状态。UE的动作取决于Registration Reject或Deregistration消息中的“原因值”。
When the UE RM state in the AMF is RM-REGISTERED, the AMF shall:
- perform Deregistration procedure (see TS 23.502 [3] clauses 4.2.2.3.2, 4.2.2.3.3), and enter RM-DEREGISTERED state for the UE, when the UE needs to be no longer registered with the PLMN. The network may decide to deregister the UE at any time;
-当UE不再需要向PLMN注册时，执行Deregistration过程，并为UE进入RM-DEREGISTERED状态。网络可以随时决定注销UE；
- perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration;
-Implicit Deregistration计时器过期后，随时执行Implicit Deregistration。AMF应在Implicit Deregistraion后为UE进入RM-DEREGISTERED状态；
- when applicable, accept or reject Registration Requests or Service Requests from the UE.
Figure 5.3.2.2.4-1: RM state model in UE
Figure 5.3.2.2.4-2: RM state model in AMF
Registration Area management comprises the functions to allocate and reallocate a Registration area to a UE. Registration area is managed per access type i.e., 3GPP access or Non-3GPP access.
Registration Area管理包括向UE分配和重新分配Registration区域的功能。注册区域按访问类型管理，即3GPP访问或Non-3GPP访问。
When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE. When the AMF allocates registration area, i.e. the set of tracking areas in TAI List, to the UE it may take into account various information (e.g. Mobility Pattern and Allowed/Non-Allowed Area (refer to clause 5.3.4.1)). An AMF which has the whole PLMN as serving area may alternatively allocate the whole PLMN ("all PLMN") as registration area to a UE in MICO mode (refer to clause 5.4.1.3).
当UE通过3GPP接入向网络注册时，AMF将TAI List中的一组跟踪区域分配给UE。当AMF将注册区域（即TAI列表中的跟踪区域集）分配给UE时，它可以考虑各种信息（例如Mobility Pattern和Allowed/Non-Allowed区域）。将整个PLMN作为服务区域的AMF可以选择将整个PLMN（“所有PLMN”）作为注册区域以MICO模式分配给UE。
The 5G System shall support allocating a Registration Area using a single TAI List which includes tracking areas of any NG-RAN nodes in the Registration Area for a UE.
5G System应支持使用单个TAI List列表分配Registration Area，该列表包括UE Registration Area中任何NG-RAN节点的跟踪区域。
A single TAI dedicated to Non-3GPP access, the N3GPP TAI, is defined in a PLMN and applies within the PLMN.
专用于Non-3GPP接入的单个TAI，即N3GPP TAI，在PLMN中定义并应用于PLMN中。
When a UE registers with the network over the Non-3GPP access, the AMF allocates a registration area that only includes the N3GPP TAI to the UE.
当UE通过Non-3GPP接入向网络注册时，AMF将仅包括N3GPP TAI的注册区域分配给UE。
When generating the TAI list, the AMF shall include only TAIs that are applicable on the access type (i.e. 3GPP access or Non-3GPP access) where the TAI list is sent.
生成TAI列表时，AMF应仅包括适用于发送TAI列表的访问类型（即3GPP访问或Non-3GPP访问）的TAI。
NOTE 1: To prevent extra signalling load resulting from Mobility Registration Update occurring at every RAT change, it is preferable to avoid generating a RAT-specific TAI list for a UE supporting more than one RAT.
注1：为了防止在每次RAT改变时发生由Mobility Registration Update引起的额外信令负载，优选避免为支持多个RAT的UE生成RAT-specific的TAI列表。
For all 3GPP Access RATs in NG-RAN and for Non-3GPP Access, the 5G System supports the TAI format as specified in TS 23.003 [19] consisting of MCC, MNC and a 3-byte TAC only.
对于NG-RAN中的所有3GPP Access RAT和Non-3GPP接入，5G System支持TS 23.003[19]中规定的TAI格式，仅包括MCC、MNC和3字节TAC。
The additional aspects for registration management when a UE is registered over one access type while the UE is already registered over the other access type is further described in clause 5.3.2.4.
第5.3.2.4条进一步描述了当UE通过一种接入类型注册而UE已经通过另一种接入类型注册时，注册管理的其他方面。
To ensure a UE initiates a Mobility Registration procedure when performing inter-RAT mobility to or from NB-IoT, a Tracking Area shall not contain both NB-IoT and other RATs cells (e.g. WB-E-UTRA, NR), and the AMF shall not allocate a TAI list that contains both NB-IoT and other RATs Tracking Areas.
为确保UE在执行往返于NB IoT的inter-RAT移动性时启动Mobility Registration程序，Tracking Area不得同时包含NB-IoT和其他RAT单元（例如WB-e-UTRA、NR），并且AMF不得分配同时包含NB IoT和其他RAT跟踪区域的TAI列表。
For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs associated with the N2 interface and additionally the Tracking Area indicated by NG-RAN. When the UE is accessing NR using unlicensed bands, as defined in clause 5.4.8, an indication is provided in N2 interface as defined in TS 38.413 [34].
对于3GPP接入，AMF基于与N2接口相关联的Global RAN Node ID以及NG-RAN指示的Tracking Area来确定UE所驻留的RAT类型。当UE使用未授权的频带访问NR时，在N2接口中提供了指示。
The AMF may also determine more precise RAT Type information based on further information received from NG-RAN:
AMF还可根据从NG-RAN收到的进一步信息确定更精确的RAT Type：
- The AMF may determine the RAT Type to be LTE-M as defined in clause 5.31.20; or
- The AMF may determine the RAT Type to be NR using unlicensed bands, as defined in clause 5.4.8.
For Non-3GPP accesses the AMF determines the RAT type the UE is camping based on the 5G-AN node associated with N2 interface as follows:
对于Non-3GPP访问，AMF根据与N2接口相关联的5G-AN节点确定UE驻留的RAT类型，如下所示：
- The RAT type is Untrusted Non-3GPP if the 5G-AN node has a Global N3IWF Node ID;
- The RAT type is Trusted Non-3GPP if the 5G-AN node has a Global TNGF Node ID or a Global TWIF Node ID; and
-如果5G-AN节点具有Global TNGF Node ID或Global TWIF Node ID，则RAT类型是Trusted Non-3GPP；并且
- The RAT type is Wireline -BBF if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline BBF Access Network. The RAT type is Wireline-Cable if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline Cable Access Network. If not possible to distinguish between the two, the RAT type is Wireline.
-如果5G-AN节点具有与支持Wireline BBF Access Network的W-AGF对应的Global W-AGF Node ID，则RAT类型为Wireline-BBF。如果5G-AN节点具有对应于支持Wireline Cable Access Network的W-AGF的 Global W-AGF Node ID，则RAT类型为Wireline-Cable。如果无法区分两者，则RAT类型为Wireline。
NOTE 2: How to differentiate between W-AGF supporting either Wireline BBF Access Network or the Wireline (e.g. different Global W-AGF Node ID IE or the Global W-AGF Node ID including a field to distinguish between them) is left to Stage 3 definition.
注2：如何区分支持Wireline BBF Access Network或Wireline的W-AGF（例如，不同的Global W-AGF Node ID IE或Global W-AGF Node ID，包括用于区分它们的字段），留待Stage 3定义。
NOTE 3: If an operator supports only one kind of Wireline Access Network (either Wireline BBF Access Network or a Wireline Cable Access Network) the AMF may be configured to use RAT type Wireline or the specific one.
注3：如果运营商仅支持一种Wireline Access Network（Wireline BBF Access Network或Wireline Cable Access Network），则AMF可配置为使用RAT类型的Wireline或特定的Wireline。
For Non-3GPP access the AMF may also use the User Location Information provided at N2 connection setup to determine a more precise RAT Type, e.g. identifying IEEE 802.11 access, Wireline-Cable access, Wireline-BBF access.
对于Non-3GPP接入，AMF还可以使用在N2连接设置中提供的User Location Information来确定更精确的RAT Type，例如识别IEEE 802.11接入、Wireline-Cable接入、Wireline-BBF 接入。
When the 5G-AN node has either a Global N3IWF Node ID, or a Global TNGF Node ID, or a Global TWIF Node ID, or a Global W-AGF Node ID, the Access Type is Non-3GPP Access.
当5G-AN节点具有Global N3IWF Node ID、Global TNGF Node ID、Global TWIF Node ID或Global W-AGF Node ID时，Access Type为Non-3GPP Access。
This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to the 5G-RG.
本条款适用于与Untrusted Non-3GPP接入网络相对应的Non-3GPP接入网络、Trusted Non-3GPP和W-5CAN。在W-5GAN的情况下，本条中提到的UE对应于5G-RG。
For a given serving PLMN there is one RM context for a UE for each access, e.g. when the UE is consecutively or simultaneously served by a 3GPP access and by a non-3GPP access (i.e. via an N3IWF, TNGF and W-AGF) of the same PLMN. UDM manages separate/independent UE Registration procedures for each access.
对于给定的服务PLMN，对于每个接入，UE有一个RM上下文，例如，当UE连续或同时由同一PLMN的3GPP接入和non-3GPP接入（即，经由N3IWF、TNGF和W-AGF）服务时。UDM为每个访问管理单独/独立的UE Registration过程。
When served by the same PLMN for 3GPP and non-3GPP accesses, an UE is served by the same AMF except in the temporary situation described in clause 5.17 i.e. after a mobility from EPS while the UE has PDU Sessions associated with non-3GPP access.
当由相同的PLMN为3GPP和non-3GPP接入服务时，UE由相同的AMF服务，除非在第5.17条中描述的临时情况下，即在从EPS移动性之后，而UE具有与non-3GPP接入相关联的PDU Session。
An AMF associates multiple access-specific RM contexts for an UE with:
- a 5G-GUTI that is common to both 3GPP and Non-3GPP accesses. This 5G-GUTI is globally unique.
- a Registration state per access type (3GPP / Non-3GPP)
- a Registration Area per access type: one Registration Area for 3GPP access and another Registration Area for non 3GPP access. Registration Areas for the 3GPP access and the Non-3GPP access are independent.
-每个访问类型的Registration Area：一个Registration Area用于3GPP访问，另一个Registration Area用于非3GPP访问。3GPP接入和非3GPP接入的Registration Area是独立的。
- timers for 3GPP access:
- a Periodic Registration timer; and
- a Mobile Reachable timer and an Implicit Deregistration timer.
- timers for non-3GPP access:
- a UE Non-3GPP Deregistration timer; and
- a Network Non-3GPP Implicit Deregistration timer.
The AMF shall not provide a Periodic Registration Timer for the UE over a Non-3GPP access. Consequently, the UE need not perform Periodic Registration Update procedure over Non-3GPP access. Instead, during the Initial Registration procedure and Re-registration, the UE is provided by the network with a UE Non-3GPP Deregistration timer that starts when the UE enters non-3GPP CM-IDLE state.
AMF不应通过Non-3GPP接入为UE提供Periodic Registration Timer。因此，UE不需要在Non-3GPP接入上执行Periodic Registration Update过程。相反，在Initial Registration过程和Re-registration期间，网络向UE提供UE Non-3GPP Deregistration定时器，该定时器在UE进入non-3GPP CM-IDLE状态时启动。
When the 3GPP access and the non-3GPP access for the same UE are served by the same PLMN, the AMF assigns the same 5G-GUTI for use over both accesses. Such a 5G-GUTI may be assigned or re-assigned over any of the 3GPP and Non-3GPP accesses. The 5G-GUTI is assigned upon a successful registration of the UE, and is valid over both 3GPP and Non-3GPP access to the same PLMN for the UE. Upon performing an initial access over the Non-3GPP access or over the 3GPP access while the UE is already registered with the 5G System over another access of the same PLMN, the UE provides the native 5G-GUTI for the other access. This enables the AN to select an AMF that maintains the UE context created at the previous Registration procedure via the GUAMI derived from the 5G-GUTI, and enables the AMF to correlate the UE request to the existing UE context via the 5G-GUTI.
当相同的PLMN为同一UE的3GPP接入和non-3GPP接入提供服务时，AMF分配相同的5G-GUTI用于两个接入。这样的5G-GUTI可以通过任何3GPP和Non-3GPP接入被分配或re-assigned。5G-GUTI在UE成功注册时被分配，并且对于UE的相同PLMN的3GPP和Non-3GPP接入都有效。当UE已经通过同一PLMN的另一接入向5G System注册时，在Non-3GPP接入或3GPP接入上执行初始接入时，UE为另一接入提供本地5G-GUTI。这使得AN能够选择维护在先前的Registration过程中通过从5G-GUTI派生的GUAMI创建的UE上下文的AMF，并且使得AMF能够通过5G-GUTI将UE请求与现有UE上下文相关联。
If the UE is performing registration over one access and intends to perform registration over the other access in the same PLMN (e.g. the 3GPP access and the selected N3IWF, TNGF or W-AGF are located in the same PLMN), the UE shall not initiate the registration over the other access until the Registration procedure over first access is completed.
如果UE在一个接入上执行注册，并且打算在同一PLMN中在另一个接入上执行注册（例如，3GPP接入和选定的N3IWF、TNGF或W-AGF位于同一PLMN中），则在完成第一个接入上的Registration过程之前，UE不得在另一个接入上发起注册。
NOTE: To which access the UE performs registration first is up to UE implementation.
When the UE is successfully registered to an access (3GPP access or Non-3GPP access respectively) and the UE registers via the other access:
当UE成功注册到接入（分别为3GPP接入或Non-3GPP接入）并且UE通过另一接入注册时：
- if the second access is located in the same PLMN (e.g. the UE is registered via a 3GPP access and selects a N3IWF, TNGF or W-AGF located in the same PLMN), the UE shall use for the registration to the PLMN associated with the new access the 5G-GUTI that the UE has been provided with at the previous registration or UE configuration update procedure for the first access in the same PLMN. Upon successful completion of the registration to the second access, if the network included a 5G-GUTI in the Registration Accept, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration.
-如果第二接入位于同一PLMN中（例如，UE通过3GPP接入注册，并选择位于同一PLMN中的N3IWF、TNGF或W-AGF），UE应使用在相同PLMN中的第一次接入的先前注册或UE配置更新过程中提供给UE的5G-GUTI来注册到与新接入相关联的PLMN。在成功完成对第二接入的注册后，如果网络在Registration Accept中包括5G-GUTI，则UE应将在Registration Accept中接收的5G-GUTI用于两个注册。如果Registration Accept中不包括5G-GUTI，则UE将为现有注册分配的5G-GUTI也用于新注册。
- if the second access is located in a PLMN different from the registered PLMN of the first access (i.e. not the registered PLMN), (e.g. the UE is registered to a 3GPP access and selects a N3IWF, TNGF or W-AGF located in a PLMN different from the PLMN of the 3GPP access, or the UE is registered over Non-3GPP and registers to a 3GPP access in a PLMN different from the PLMN of the N3IWF, TNGF or W-AGF), the UE shall use for the registration to the PLMN associated with the new access a 5G-GUTI only if it has got one previously received from a PLMN that is not the same as the PLMN the UE is already registered with. If the UE does not include a 5G-GUTI, the SUCI shall be used for the new registration. Upon successful completion of the registration to the second access, the UE has the two 5G-GUTIs (one per PLMN).
-如果第二接入位于与第一接入的注册PLMN不同的PLMN中（即，非注册PLMN），（例如，UE注册到3GPP接入，并选择位于与3GPP接入的PLMN不同的PLMN中的N3IWF、TNGF或W-AGF，或者UE通过Non-3GPP注册并注册到与N3IWF、TNGF或W-AGF的PLMN不同的PLMN中的3GPP接入），UE应仅在其之前从PLMN接收到一个与UE已注册的PLMN不同的PLMN时，才用于注册到与新接入5G-GUTI相关联的PLMN。如果UE不包括5G-GUTI，则SUCI将用于新注册。在成功完成对第二接入的注册后，UE具有两个5G -GUTI（每个PLMN一个）。
A UE supporting registration over both 3GPP and Non-3GPP access to two PLMNs shall be able to handle two separate registrations, including two 5G-GUTIs, one per PLMN, and two associated equivalent PLMN lists.
支持通过3GPP和Non-3GPP接入两个PLMN进行注册的UE应能够处理两个单独的注册，包括两个5G-GUTI，每个PLMN一个，以及两个相关的等效PLMN列表。
When a UE 5G-GUTI assigned during a Registration procedure over 3GPP (e.g. the UE registers first over a 3GPP access) is location-dependent, the same UE 5G-GUTI can be re-used over the Non-3GPP access when the selected N3IWF, TNGF or W-AGF function is in the same PLMN as the 3GPP access. When an UE 5G-GUTI is assigned during a Registration procedure performed over a Non 3GPP access (e.g. the UE registers first over a non-3GPP access), the UE 5G-GUTI may not be location-dependent, so that the UE 5G-GUTI may not be valid for NAS procedures over the 3GPP access and, in this case, a new AMF is allocated during the Registration procedure over the 3GPP access.
当在通过3GPP的Registration过程期间分配的UE 5G-GUTI（例如，UE首先通过3GPP接入注册）是location-dependent时，当所选择的N3IWF、TNGF或W-AGF功能与3GPP接入在同一PLMN中时，相同的UE 5G-GUTI可在Non-3GPP接入上re-used。当在通过Non 3GPP接入执行的Registration过程中分配UE 5G-GUTI时（例如，UE首先通过non-3GPP接入注册），UE 5G-GUTI可能不location-dependent，因此UE 5G-GUTI可能对通过3GPP接入的NAS过程无效，并且在这种情况下，在3GPP接入的Registration过程中分配新的AMF。
When the UE is registered first via 3GPP access, if the UE registers to the same PLMN via Non-3GPP access, the UE shall send the GUAMI obtained via 3GPP access to the N3IWF, TNGF or W-AGF, which uses the received GUAMI to select the same AMF as the 3GPP access.
当UE首先通过3GPP接入注册时，如果UE通过Non-3GPP接入注册到相同的PLMN，则UE应将通过3GPP接入获得的GUAMI发送到N3IWF、TNGF或W-AGF，其使用接收到的GUAMI选择与3GPP接入相同的AMF。
The Deregistration Request message indicates whether it applies to the 3GPP access the Non-3GPP access, or both.
Deregistration Request消息指示它是应用于3GPP接入还是应用于Non-3GPP接入，或者两者都适用。
If the UE is registered on both 3GPP and Non-3GPP accesses and it is in CM-IDLE over Non-3GPP access, then the UE or AMF may initiate a Deregistration procedure over the 3GPP access to deregister the UE only on the Non-3GPP access, in which case all the PDU Sessions which are associated with the Non-3GPP access shall be released.
如果UE在3GPP和Non-3GPP接入上都注册并且在Non-3GPP接入上处于CM-IDLE，则UE或AMF可以在3GPP接入上发起Deregistration程序，以仅在Non-3GPP接入上注销UE，在这种情况下，应释放与Non-3GPP接入相关联的所有PDU Session。
If the UE is registered on both 3GPP and non-3GPP accesses and it is in CM-IDLE over 3GPP access and in CM-CONNECTED over non-3GPP access, then the UE may initiate a Deregistration procedure over the non-3GPP access to deregister the UE only on the 3GPP access, in which case all the PDU Sessions which are associated with the 3GPP access shall be released.
如果UE在3GPP和non-3GPP接入上都注册，并且它在3GPP接入上处于CM-IDLE，在non-3GPP接入上处于CM-CONNECTED，则UE可以在non-3GPP接入上发起Deregistration程序，以仅在3GPP接入上注销UE，在这种情况下，应释放与3GPP接入相关的所有PDU Session。
Registration Management over Non-3GPP access is further defined in clause 5.5.1.
3GPP TS 23501-g51 中英文对照 | 5.3.2 Registration Management相关推荐
- 3GPP TS 23501-g51 中英文对照 | 5.3.3 Connection Management
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
- 3GPP TS 29244-g30 中英文对照 | 5.4.9 Provisioning of Predefined PCC/ADC Rules
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 29244-g30过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
- 3GPP TS 29244-g30 中英文对照 | 5.11 User plane inactivity detection and reporting
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 29244-g30过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
- 3GPP TS 23501-g51 中英文对照 | 4.4.5 Application Triggering Services
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
- 3GPP TS 23501-g51 中英文对照 | 4.2.1 General
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
- 3GPP TS 23501-g51 中英文对照 | 5.2.1 General
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
- 3GPP TS 23501-g51 中英文对照 | 4.1 General concepts
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
- 3GPP TS 23501-g51 中英文对照 | 4.3.2 Roaming architecture
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
- 3GPP TS 23501-g51 中英文对照 | 4.4.4 Location services
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
最新文章
- 2022-2028年中国抗盐粘土行业发展现状调查及前景战略分析报告
- 反编译得到的java文件好多错误 val$query什么意思_这部分代码有错么？一直提示输入框$(#msg).val()得到的值未定义...
- Leet Code OJ 206. Reverse Linked List [Difficulty: Easy]
- ES6-18/19 异步的开端-promise
- python设计模式之猴子补丁模式
- iOS核心动画高级技术(九) 图层时间
- 查看linux cpu和内存利用率__linux top命令
- centos7下kubernetes（1。kubernetes---start）
- C# 使用Newtonsoft.Json读写Json文件
- .NET Reflector 反射下载
- Excel数据分析项目——电商数据分析实战
- android 项目交接文档,产品交付规范文档
- 递归下降分析程序 java_递归下降语法分析程序
- SCDM学习笔记（2）
- 使用官方APi获取Youtube视频资源
- 串操作指令---movs，stos，rep
- 大司、小司、外包公司
- logback配置文件---logback.xml详解
- 杭州ALIENWARE外星人电脑（大悦城旗舰店），玩起来就是不一样
- 阿里云域名申请 + 七牛云CDN加速
热门文章
- 简单粗暴的更换固态硬盘及WIN10 Ubuntu双系统
- ESP32ADC采样率配置（基于ESP-IDF）
- OpenCV—python 自动色彩均衡（ACE）
- [Java] Node和Entry
- RASA如何处理多意图
- FPGA中如何使用加法器IP核设计累加器
- 虚拟机运行macOS10.15Catalina拓展apfs卷宗（拓展分区）
- Mac磁盘工具无法将APFS硬盘转化为txFAT格式的解决办法
- java连接数据库用户 'sa' 登录失败。 ClientConnectionId：解决方法
- 【代码阅读】云E办项目后端技术栈总结及源码分析
