name: SOR
full_form: Service Oriented Radio
context: A 5GS session management (5GSM) message is piggybacked in specific 5GS mobility management (5GMM) transport messages. To this purpose, the 5GSM messages can be transmitted in an information element in the 5GMM transport messages. In this case, the UE, the AMF and the SMF execute the 5GMM procedure and the 5GSM procedure in parallel. The success of the 5GMM procedure is not dependent on the success of the piggybacked 5GSM procedure. The UE can only initiate the 5GSM procedure when there is a 5GMM context established at the UE. During 5GMM procedures, the UE and the AMF shall suspend the transmission of 5GSM messages, except when: a) the 5GMM procedure is piggybacking 5GSM messages; or b) the UE is in 5GMM-CONNECTED mode and a service request procedure for re-establishing user-plane resources of PDU session(s) is initiated without including PDU session status IE or Allowed PDU session status IE. In this case, the UE and the AMF need not suspend the transmission of 5GSM messages related to other PDU session(s) than the one(s) for which the user- plane resources re-establishment is requested. If the UE determines to locally release the N1 NAS signalling connection upon receiving an SOR transparent container during a registration procedure as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ]  [5] Annex C.2, the UE shall suspend the transmission of 5GSM messages after sending the REGISTRATION COMPLETE message and until the N1 NAS signalling connection is released to obtain service on a higher priority PLMN, with the exception of the case when the UE has an emergency PDU session. A 5GMM message piggybacking a 5GSM message for a PDU session shall be delivered via the access associated with the PDU session, if any, with the following exceptions: a) the AMF shall send, via 3GPP access, a DL NAS TRANSPORT message piggybacking a downlink 5GSM message of a network-requested 5GSM procedure for a PDU session associated with non-3GPP access if the conditions specified in subclause 5.5.1.3.4 or subclause 5.6.1.4 are met; b) the UE shall send an UL NAS TRANSPORT message piggybacking a response message to the 5GSM message described in a) via either: 1) 3GPP access; or 2) non-3GPP access if the UE is in 5GMM-CONNECTED mode over non-3GPP access; and NOTE: The interaction between the 5GMM sublayer and the 5GSM sublayer to enable the UE to send the UL NAS TRANSPORT message containing the response message via 3GPP access is required. This is achieved via UE implementation. c) the UE shall send, via the target access, an UL NAS TRANSPORT message piggybacking a 5GSM message associated with a request type set to "existing PDU session" or "existing emergency PDU session" for handover of an existing PDU session between 3GPP access and non-3GPP access. A 5GMM message piggybacking a 5GSM message as a response message to a request message associated with an MA PDU session, shall be delivered via the same access that the initial message was received.
description: SOR stands for Service Oriented Radio. However, in this context, SOR refers to a transparent container used during registration procedures as specified in 3GPP TS 23.122. The UE determines to locally release the N1 NAS signalling connection upon receiving an SOR transparent container, which leads to suspending the transmission of 5GSM messages until the N1 NAS signalling connection is released.
explanation: SOR is classified as a Message because it refers to a specific type of information element or container used in the communication between network components. In this context, the SOR transparent container plays a role in the registration procedure and affects the transmission of 5GSM messages.
section_title: 4.2 Coordination between the protocols for 5GS mobility management and 5GS session management
biotag_Context: O,B-Technology,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,B-Message,O,O,B-Connection,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,B-Procedure,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Organization,O,O,B-Connection,B-Protocol,O,O,O,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,B-Device,O,O,O,B-Device,O,O,O,O,O,O,O,B-Connection,B-Protocol,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,B-Organization,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Message,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,B-Device,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Interface,B-Protocol,O,O,O,O