Apparatus and method of distributing non-access stratum message
By allowing UE to generate and RAN to decode NAS messages with core network function indications, the method addresses the limitations of 5G's single anchor point, improving latency and flexibility in 6G networks.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-08-18
- Publication Date
- 2026-04-02
AI Technical Summary
Current 5G networks rely on a single anchor point (AMF) for NAS message processing, which limits low-latency and flexible service demands in 6G networks with distributed network functions.
User equipment (UE) generates NAS messages with core network function indications, encapsulating them in RRC messages for direct transmission to the RAN, and the RAN decodes and forwards these messages to appropriate core network functions based on the indication, reducing reliance on the AMF as a sole anchor.
This approach reduces signaling latency and enhances routing flexibility, enabling efficient and distributed NAS message handling in 6G networks.
Smart Images

Figure US2025042427_02042026_PF_FP_ABST
Abstract
Description
Atty. Dkt. No. 10085-01-0171-PCTAPPARATUS AND METHOD OF DISTRIBUTING NON-ACCESSSTRATUM MESSAGECROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Application No. 63 / 701,241, entitled “METHOD AND APPARATUS OF DISTRIBUTING NAS MESSAGES IN 6G NETWORK,” filed on September 30, 2024, which is hereby incorporated in its entirety by this reference.TECHNICAL FIELD
[0002] The present disclosure relates to the field of communication systems, and more particularly, to apparatuses and methods of distributing non-access stratum (NAS) message.BACKGROUND
[0003] In current 5G networks, non-access stratum (NAS) messages from a user equipment (UE) are always processed and forwarded by an access and mobility management function (AMF), which serves as a sole anchor point for NAS signaling. The AMF identifies a target function and relays the NAS message to entities such as a session management function (SMF) or other network functions (NFs). However, with the evolution of 6G networks and the introduction of more distributed or edge-deployed network functions, the existing mechanism cannot effectively support low-latency and flexible service demands.
[0004] Therefore, there is a need for apparatuses and methods of distributing non-access stratum (NAS) message.SUMMARY
[0005] An object of the present disclosure is to propose apparatuses and methods of distributing non-access stratum (NAS) message, which can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0006] In a first aspect of the present disclosure, a method of distributing non-access stratum (NAS) message performed by a user equipment (UE) includes generating a NAS message including an indication of a core network (CN) function; encapsulating the NAS message in a radio resource control (RRC) message and transmitting the RRC message to a radio access network (RAN).
[0007] In a second aspect of the present disclosure, a user equipment (UE) includes a generator configured to generate a non-access stratum (NAS) message including an indication of a core network (CN) function and encapsulate the NAS message in a radio resource control (RRC)Atty. Dkt. No. 10085-01-0171-PCT message, and a transmitter configured to transmit the RRC message to a radio access network (RAN).
[0008] In a third aspect of the present disclosure, a user equipment (UE) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The UE is configured to perform the above method.
[0009] In a fourth aspect of the present disclosure, a method of distributing non-access stratum (NAS) message performed by a radio access network (RAN) includes receiving a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, decoding at least a portion of the NAS message to extract an indication of a core network (CN) function, and forwarding the NAS message to the CN function based on the indication of the CN function.
[0010] In a fifth aspect of the present disclosure, a radio access network (RAN) includes a transceiver configured to receive a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, and a decoder configured to decode at least a portion of the NAS message to extract an indication of a core network (CN) function, wherein the transceiver is further configured to forward the NAS message to the CN function based on the indication of the CN function.
[0011] In a sixth aspect of the present disclosure, a radio access network (RAN) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The RAN is configured to provide the above method.
[0012] In a seventh aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.
[0013] In an eighth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.
[0014] In a ninth aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.
[0015] In a tenth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.
[0016] In an eleventh aspect of the present disclosure, a computer program causes a computer to execute the above method.Atty. Dkt. No. 10085-01-0171-PCTBRIEF DESCRIPTION OF DRAWINGS
[0017] In order to illustrate the embodiments of the present disclosure or related art more clearly, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.
[0018] FIG. l is a block diagram of one or more user equipments (UEs), a radio access network (RAN), and one or more network functions of communication in a communication network system according to an embodiment of the present disclosure.
[0019] FIG. 2A is a block diagram of a UE according to an embodiment of the present disclosure.
[0020] FIG. 2B is a block diagram of a UE according to an embodiment of the present disclosure.
[0021] FIG. 3 is a flowchart illustrating a method of distributing non-access stratum (NAS) message performed by a UE according to an embodiment of the present disclosure.
[0022] FIG. 4A is a block diagram of a RAN according to an embodiment of the present disclosure.
[0023] FIG. 4B is a block diagram of a RAN according to an embodiment of the present disclosure.
[0024] FIG. 5 is a flowchart illustrating a method of distributing non-access stratum (NAS) message performed by a RAN according to an embodiment of the present disclosure.
[0025] FIG. 6 is a block diagram of an example of a 6G NAS signaling without relying on an AMF as anchor, according to an embodiment of the present disclosure.
[0026] FIG. 7 is a block diagram of an example of collaboration between a 6GRAN and an AMF according to an embodiment of the present disclosure.
[0027] FIG. 8 is a block diagram of an example of a computing device according to an embodiment of the present disclosure.
[0028] FIG. 9 is a block diagram of a communication system according to an embodiment of the present disclosure.DETAILED DESCRIPTION OF EMBODIMENTS
[0029] Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.
[0030] The technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple accessAtty. Dkt. No. 10085-01-0171-PCT(WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolution system of a NR system, a LTE-based access to unlicensed spectrum (LTE-U) system, a NR-based access to unlicensed spectrum (NR-U) system, an universal mobile telecommunication system (UMTS), a global interoperability for microwave access (WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (Wi-Fi), a future 5th generation (5G) system (may also be called a new radio (NR) system) or other communication systems, etc.
[0031] Optionally, a base station mentioned in the embodiments of the present application can provide a communication coverage for a specific geographic area and can communicate with a user equipment (UE) located in the coverage area. Optionally, the base station may be a gNB, a base transceiver station (BTS) in the GSM or in the CDMA system, or may be a NodeB (NB) in the WCDMA system, or may be an evolutional Node B (eNB or eNodeB) in the LTE system, or a radio controller in a cloud radio access network (CRAN).
[0032] A user equipment (UE) may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular radio telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication functions, a computing device, other processing devices coupled with a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, a terminal device in a future evolved public land mobile network (PLMN), etc.
[0033] Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where the licensed spectrum can also be considered an unshared spectrum.
[0034] In 5G networks, a non-access stratum (NAS) is responsible for signaling between a user equipment (UE) and a core network (CN), such as communication between the UE and an access and mobility management function (AMF). NAS messages handle functions including registration, mobility management, and session management. When the UE sends a NAS message (e.g., a registration request or a session management request), the message is encapsulated in a radio resource control (RRC) message and transmitted to a next generation node B (gNB). The gNB, being transparent to NAS, forwards a NAS container to the AMF without interpreting its contents. Upon receiving the NAS message, the AMF decodes and processes the NAS message. If the NASAtty. Dkt. No. 10085-01-0171-PCT message is intended for the AMF itself, the AMF performs functions such as registration and mobility management. If the NAS message relates to a session (e.g., establishing a data session), the AMF forwards the NAS message to an appropriate core network function, such as a session management function (SMF). For messages targeting other network functions (NFs), the AMF forwards the messages accordingly. This NAS signaling framework enables the UE to interact with various core network functions while supporting efficient mobility, session handling, and connection management in 5G.
[0035] The existing NAS signaling mechanism relies on the AMF as a single anchor point for the UE. All NAS messages are first sent to the AMF for processing before any further handling. In 6G networks, it is expected that more network functionalities will be introduced as new services to the UE.
[0036] FIG. 1 illustrates that, in some embodiments, one or more user equipments (UEs) 10, a radio access network (RAN) 20, and one or more network functions 30 of communication in a communication network system 40 (e.g., an NR system or 6G system) according to an embodiment of the present disclosure are provided. The communication network system 40 includes the one or more UEs 10, the RAN 20, and the one or more network functions 30. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The RAN 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The one or more network functions 30 may include a memory 32, a transceiver 33, and a processor31 coupled to the memory 32 and the transceiver 33. The processor 11, 21, or 31 may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11, 21, or 31. The memory 12, 22, or 32 is operatively coupled with the processor 11, 21, or 31 and stores a variety of information to operate the processor 11, 21, or 31. The transceiver 13, 23, or 33 is operatively coupled with the processor 11, 21, or 31, and the transceiver 13, 23, or 33 transmits and / or receives a radio signal.
[0037] The processor 11, 21, or 31 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 12, 22, or 32 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 13, 23, or 33 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 12, 22, or 32 and executed by the processor 11, 21, or 31. The memory 12, 22, or 32 can be implemented within the processor 11, 21, or 31 or external to the processor 11, 21, or 31 in which case thoseAtty. Dkt. No. 10085-01-0171-PCT can be communicatively coupled to the processor 11, 21, or 31 via various means as is known in the art.
[0038] In some embodiments, the processor 11 is configured to generate a non-access stratum (NAS) message including an indication of a core network (CN) function and encapsulate the NAS message in a radio resource control (RRC) message, and the transceiver 13 is configured to transmit the RRC message to the RAN 20. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0039] In some embodiments, the transceiver 23 is configured to receive a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, the processor 21 is configured to decode at least a portion of the NAS message to extract an indication of a core network (CN) function, and the transceiver 23 is further configured to forward the NAS message to the CN function based on the indication of the CN function. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0040] FIG. 2A illustrates an example of a UE 200A according to an embodiment of the present application. The UE 200A is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the UE 200A using any suitably configured hardware and / or software. The UE 200A includes a generator 201 A and a transmitter 202A. The generator 201A is configured to generate a non-access stratum (NAS) message including an indication of a core network (CN) function and encapsulate the NAS message in a radio resource control (RRC) message, and the transmitter 202A is configured to transmit the RRC message to a radio access network (RAN). This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0041] FIG. 2B illustrates an example of a UE 200B according to an embodiment of the present disclosure. The UE 200B is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the UE 200B using any suitably configured hardware and / or software. The UE 200B may include a memory 20 IB, a transceiver 202B, and a processor 203B coupled to the memory 20 IB and the transceiver 202B. The processor 203B may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 203B. The memory 20 IB is operatively coupled with the processor 203B and stores a variety of information to operate the processor 203B. The transceiver 202B is operatively coupled with the processor 203B, and the transceiver 202B transmits and / or receives a radio signal. The processor 203B may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 20 IB may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 202B may include baseband circuitry to process radio frequency signals. When theAtty. Dkt. No. 10085-01-0171-PCT embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 20 IB and executed by the processor 203B. The memory 20 IB can be implemented within the processor 203B or external to the processor 203B in which case those can be communicatively coupled to the processor 203B via various means as is known in the art.
[0042] In some embodiments, the processor 203B is configured to generate a non-access stratum (NAS) message including an indication of a core network (CN) function and encapsulate the NAS message in a radio resource control (RRC) message, and the transceiver 202B is configured to transmit the RRC message to a RAN. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0043] FIG. 3 is an example of a method 300 of distributing non-access stratum (NAS) message performed by a UE according to an embodiment of the present disclosure. The method 300 of distributing non-access stratum (NAS) message performed by a UE is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the method 300 of distributing non-access stratum (NAS) message performed by a UE using any suitably configured hardware and / or software. In some embodiments, the method 300 of distributing non-access stratum (NAS) message performed by a UE includes: an operation 302, generating a NAS message including an indication of a core network (CN) function; an operation 304, encapsulating the NAS message in a radio resource control (RRC) message; and an operation 306, transmitting the RRC message to a radio access network (RAN). This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0044] In some embodiments, the indication of the CN function includes a first information element (IE) in the NAS message. In some embodiments, the first IE includes a network function field indicating a network function identity. In some embodiments, the indication of the CN function is included in an extended payload container type field of the NAS message. In some embodiments, the extended payload container type field includes at least one bit used to distinguish the CN function other than an access and mobility management function (AMF) or a session management function (SMF). In some embodiments, the NAS message targeting an AMF or a SMF includes a second IE indicating a destination. In some embodiments, the NAS message is carried by a signaling radio bearer (SRB) that corresponds to the CN function. In some embodiments, the SRB is selected by a radio resource control (RRC) layer in the UE based on the CN function of the NAS message. In some embodiments, the SRB includes one of a plurality of SRBs including at least one of SRB4, SRB5, and SRB6. In some embodiments, the at least one of SRB4, SRB5, and SRB6 is mapped to a respective CN function. In some embodiments, the SRB4 is associated with a first network function, the SRB5 is associated with a second network function, and the SRB6 is associated with a third network function. In some embodiments, a mapping of the SRBs to respective CN functions is preconfigured or provided via a system configuration signaling.Atty. Dkt. No. 10085-01-0171-PCT
[0045] In some embodiments, the indication of the CN function is conveyed using a first IE in the NAS message, where the first IE includes a network function field identifying the target CN function. Alternatively, the indication may be included in an extended payload container type field of the NAS message, wherein at least one bit is used to distinguish CN functions other than the AMF or the SMF. For NAS messages targeting the AMF or SMF, a second IE may be included to explicitly indicate the destination. Additionally, the NAS message may be carried over a signaling radio bearer (SRB) that corresponds to the intended CN function. The selection of the SRB may be performed by the RRC layer in the UE based on the CN function, with SRB4, SRB5, and SRB6 respectively mapped to first, second, and third CN functions. Such mappings may be preconfigured or provided through system configuration signaling. This design advantageously enables flexible and efficient NAS message routing in distributed 6G core network environments.
[0046] FIG. 4 A illustrates an example of RAN 400 A according to an embodiment of the present application. The RAN 400A is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the RAN 400A using any suitably configured hardware and / or software. The RAN 400A includes a transceiver 401 A and a decoder 402A coupled to the transceiver 401A. The transceiver 401A is configured to receive a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, and the decoder 402A is configured to decode at least a portion of the NAS message to extract an indication of a core network (CN) function, wherein the transceiver 401 A is further configured to forward the NAS message to the CN function based on the indication of the CN function. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0047] FIG. 4B illustrates an example of a RAN 400B according to an embodiment of the present disclosure. The RAN 400B is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the RAN 400B using any suitably configured hardware and / or software. The RAN 400B may include a memory 40 IB, a transceiver 402B, and a processor 403B coupled to the memory 40 IB and the transceiver 402B. The processor 403B may be configured to implement proposed functions, procedures and / or methods described in this description. Layers of radio interface protocol may be implemented in the processor 403B. The memory 40 IB is operatively coupled with the processor 403B and stores a variety of information to operate the processor 403B. The transceiver 402B is operatively coupled with the processor 403B, and the transceiver 402B transmits and / or receives a radio signal. The processor 403B may include application-specific integrated circuit (ASIC), other chipset, logic circuit and / or data processing device. The memory 40 IB may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device. The transceiver 402B may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.Atty. Dkt. No. 10085-01-0171-PCTThe modules can be stored in the memory 40 IB and executed by the processor 403B. The memory 40 IB can be implemented within the processor 403B or external to the processor 403B in which case those can be communicatively coupled to the processor 403B via various means as is known in the art.
[0048] In some embodiments, the transceiver 402B is configured to receive a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, the processor 403B is configured to decode at least a portion of the NAS message to extract an indication of a core network (CN) function, and the transceiver 402B is further configured to forward the NAS message to the CN function based on the indication of the CN function. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0049] FIG. 5 is an example of a method 500 of distributing non-access stratum (NAS) message performed by a RAN according to an embodiment of the present disclosure. The method 500 of distributing non-access stratum (NAS) message performed by the RAN is configured to implement some embodiments of the disclosure. Some embodiments of the disclosure may be implemented into the method 500 of distributing non-access stratum (NAS) message performed by the RAN using any suitably configured hardware and / or software. In some embodiments, the method 500 of distributing non-access stratum (NAS) message performed by the RAN includes: an operation 502, receiving a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message includes a NAS message, an operation 504, decoding at least a portion of the NAS message to extract an indication of a core network (CN) function, and an operation 506, forwarding the NAS message to the CN function based on the indication of the CN function. This can solve issues in the prior art and other issues, reduce signaling latency, and / or improve routing flexibility.
[0050] In some embodiments, the indication of the CN function includes a first information element (IE) in the NAS message. In some embodiments, the first IE includes a network function field indicating a network function identity. In some embodiments, the indication of the CN function is included in an extended payload container type field of the NAS message. In some embodiments, the extended payload container type field includes at least one bit used to distinguish the CN function other than an access and mobility management function (AMF) or a session management function (SMF). In some embodiments, the NAS message targeting an AMF or a SMF includes a second IE indicating a destination. In some embodiments, the method further includes determining whether the CN function corresponds to one of an AMF, a SMF, or another CN function based on the indication of the CN function. In some embodiments, decoding performed by the RAN is limited to parsing a header or predefined field of the NAS message. In some embodiments, the RAN forwards the NAS message to the CN function without relying on an AMF as an anchor. In some embodiments, the NAS message is carried by a signaling radio bearer (SRB) that corresponds to the CN function.Atty. Dkt. No. 10085-01-0171-PCT
[0051] In some embodiments, the SRB is selected by a radio resource control (RRC) layer in the UE based on the CN function of the NAS message. In some embodiments, the SRB includes one of a plurality of SRBs including at least one of SRB4, SRB5, and SRB6. In some embodiments, at least one of SRB4, SRB5, and SRB6, is mapped to a respective CN function. In some embodiments, the SRB4 is associated with a first network function, the SRB5 is associated with a second network function, and the SRB6 is associated with a third network function. In some embodiments, a mapping of the SRBs to respective CN functions is preconfigured or provided via a system configuration signaling. In some embodiments, the method further includes querying an AMF for a forwarding decision of the NAS message; and transmitting, to the AMF, the indication of the CN function for the NAS message. In some embodiments, querying the AMF for the forwarding decision of the NAS message includes forwarding the NAS message to the AMF for decoding. In some embodiments, the method further includes transmitting, to the AMF, a response indicating the CN function after decoding the NAS message and forwarding the NAS message to the CN function based on the response. In some embodiments, querying the AMF for the forwarding decision of the NAS message includes transmitting an indicator extracted from the RRC message carrying the NAS message to the AMF. In some embodiments, the method further includes receiving from the AMF, a CN function information for routing the NAS message. In some embodiments, the AMF is deployed in proximity to the RAN in an edge cloud environment.
[0052] In some embodiments, the indication of the CN function is conveyed using a first IE in the NAS message, where the first IE includes a network function identity field. Alternatively, the indication may be included in an extended payload container type field, with at least one bit used to distinguish CN functions other than the AMF or SMF. For messages targeting the AMF or SMF, a second IE may explicitly indicate the destination. The method may further include determining whether the CN function corresponds to the AMF, SMF, or another CN function based on the indication, wherein the RAN performs only partial decoding of the NAS message, such as parsing a header or specific field, and may forward the NAS message directly to the CN function without relying on the AMF as an anchor. In some embodiments, the NAS message is carried by a signaling radio bearer (SRB) selected by the RRC layer in the UE, where SRB4, SRB5, and SRB6 are respectively mapped to different CN functions, with such mappings either preconfigured or signaled by the network. Additionally, the RAN may collaborate with the AMF by querying it for forwarding decisions, either by sending the full NAS message or only an indicator extracted from the RRC message. The AMF may decode the message and return the appropriate CN function information for routing. In some cases, the AMF is deployed near the RAN in an edge cloud configuration. This flexible architecture enables distributed NAS message handling, reduces signaling latency, and enhances routing efficiency in next-generation 6G networks.
[0053] Exemplary Technical Solutions:
[0054] FIG. 6 is an example of 6G NAS signaling without relying on an AMF as an anchor, according to an embodiment of the present disclosure. FIG. 6 illustrates that, in some examples,Atty. Dkt. No. 10085-01-0171-PCT more network functionalities are expected to be introduced in 6G networks as new services to the UE. These new functionalities, along with some existing core network (CN) functions, may be deployed closer to or co-located with the Radio Access Network (RAN) as part of an edge cloud architecture. This deployment aims to localize critical signaling processing, thereby reducing latency and improving overall performance. Accordingly, it is desirable to design a new NAS signaling transmission mechanism that enables the UE, via the RAN, to directly communicate with individual CN functions. The concept is illustrated in FIG. 6.
[0055] To enable the 6G RAN, instead of the AMF, to forward NAS signaling from the UE to a network function, the 6G RAN needs to understand the destination network function of the NAS message. In some embodiments of the present disclosure, several different design approaches are proposed to achieve this functionality.
[0056] In partial NAS decoding at the 6G RAN, the 6G RAN is equipped with the ability to partially decode the NAS message, for example, to determine the target core network (CN) function for further forwarding. The 6G RAN needs to identify the message type or destination of the NAS message before forwarding it. To do so, the 6G RAN parses and checks the NAS message header or specific fields to determine whether the message should be routed to the AMF, SMF, or another CN function. Based on this header information, the 6G RAN then forwards the message accordingly.
[0057] Proposal 1 : Use an Information Element (IE) in the NAS message to indicate which CN function the message is intended for. One example is shown as follows. A new IE, Target network function, is added to the NAS message, which the 6G RAN needs to read.
[0058] IE: Target network function.
[0059] In some examples, the process is as follows: the UE sends a NAS message to a CN function, assuming it is NFx. The UE includes NFx or the corresponding ID in the IE “target network function.” This NAS message is sent to the 6G RAN within an RRC message. The 6G RAN receives the RRC message and decodes the included NAS message solely to read the IE “target network function.” The 6G RAN then identifies the target network function and forwards the NAS message to the corresponding NF.
[0060] Proposal 2: Use an existing Information Element (IE), Payload container type, to indicate the target CN function, except for AMF or SMF. The "Payload container type" has 4 bits and needs to be extended to allow more bits for indicating the target CN function. The following shows an example of an extended Payload container type IE.
[0061] IE: Payload container type.Atty. Dkt. No. 10085-01-0171-PCT
[0062] Proposal 2.1 : For NAS messages targeting the AMF or the SMF, add a new Information Element (IE) in the NAS message to indicate the destination. The process is as follows: the UE sends a NAS message to a CN function, assuming it is NFx that is not the AMF or the SMF. The UE uses the IE “payload container type” to indicate the target network function, i.e., NFx. ThisNAS message is sent to the 6G RAN in an RRC message. The 6G RAN receives this RRC message and decodes the included NAS message solely to read the IE “payload container type.” The 6G RAN understands the target network function and forwards the NAS message to the corresponding NF. For NAS messages targeting the AMF or the SMF, the 6G RAN uses the newly added IE to determine the destination.
[0063] Route NAS messages based on SRBs that carry the NAS message: In 5G networks, NAS messages are carried by RRC messages on SRB1 or SRB2. 3GPP specifications provide detailed descriptions of how the RRC layer carries NAS messages. In 6G, to allow the 6G RAN to route NAS messages to different CN functions, it is proposed to use different SRBs to carry different types of NAS messages.
[0064] Proposal 3: Define new SRBs in 6G RRC to carry different types of NAS messages. The 6GRAN determines the target CN functions based on the SRBs that carry the NAS messages. The following is an example of newly defined SRBs as illustrated in Table 1.
[0065] Table 1 : SRBs.Atty. Dkt. No. 10085-01-0171-PCT
[0066] The process is as follows: the UE sends a NAS message to a CN function, assuming it is NFx. The NAS message is provided to the RRC. Depending on the target network function, the RRC uses a different SRB to carry the NAS message. The 6G RAN receives this RRC message on the corresponding SRB and understands the target NF. The 6G RAN then sends the NAS message to the target NF.
[0067] Route NAS message based on collaboration with the AMF: In 6G networks, it is expected that edge cloud deployments will be introduced, where many core network functions are co-located with the 6G RAN to provide services to the UE with low latency and improved performance. In that sense, some AMF functions might be deployed as a “lightweight AMF” together with the 6G RAN. Such proximity allows the 6G RAN and the AMF to work together to route NAS messages. FIG. 7 is an example of collaboration between a 6GRAN 701 and a 6G AMF 702 according to an embodiment of the present disclosure. FIG. 7 illustrates that, in some examples, the 6G RAN 701 and the 6G AMF 702 can work together to determine the appropriate core network (CN) function for forwarding NAS messages. The 6G RAN 701 receives a NAS message or a message ID / type from the 6G AMF 702. Based on this information, the 6G AMF 702 indicates a target core network (CN) function to the 6G RAN 701.
[0068] Proposal 4: Allow the 6G RAN and AMF to collaborate. The 6G RAN queries the AMF for a forwarding decision for NAS messages. The 6G RAN could then send the NAS messages to the target CN functions. Multiple methods can be used for 6G RAN-AMF collaboration.
[0069] Proposal 4.1 : In one collaboration method, the 6G RAN sends all NAS messages to the AMF, which will decode the message and identify the target CN functions. The AMF then informs the 6G RAN about the destination.
[0070] Proposal 4.2: In one collaboration method, the 6G RAN uses an indicator in the RRC message that carries the NAS message and sends this indicator to the AMF. The AMF then determines the target CN function based on the indicator and informs the 6G RAN about the destination.
[0071] In summary, some embodiments of the present disclosure provide several technical solutions for distributing NAS messages in 6G networks without relying solely on the AMF as an anchor. These include partial NAS decoding at the 6G RAN, the use of new or extended information elements (such as “Target network function” or modified “Payload container type”), SRB-based routing where different SRBs correspond to different CN functions, and collaborativeAtty. Dkt. No. 10085-01-0171-PCT routing with a co-located or edge-deployed lightweight AMF. Each approach enables the 6G RAN to identify the appropriate target CN function and forward the NAS message accordingly. An advantage of these solutions is that they support distributed and low-latency NAS message handling, which enhances scalability and performance in 6G edge cloud deployments.
[0072] Commercial interests for some embodiments are as follows. 1. Solve issues in the prior art and other issues. 2. Reduce signaling latency. 3. Improve routing flexibility. 4. Provide a good communication performance. 5. Provide high reliability. Some embodiments of the present disclosure can be used in many applications. Some embodiments of the present disclosure are used by chipset vendors, video system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR / VR / MR device maker for example gaming, conference / seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques / processes” that can be adopted in video standards to create an end product. Some embodiments of the present disclosure propose technical mechanisms. The at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure may be used for current and / or new / future standards regarding communication systems such as a UE, a base station, and / or a communication system. Compatible products follow at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure. The proposed solution, method, system, and apparatus are widely used in a UE, a base station, and / or a communication system. With the implementation of the at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure, at least one modification to methods and apparatus of wireless communication are considered for standardizing.
[0073] In some embodiments, a user equipment (UE) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The UE is configured to perform the above method. In some embodiments, a radio access network (RAN) includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The RAN is configured to provide the above method. In some embodiments, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method. In some embodiments, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method. In some embodiments, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method. In some embodiments, a computer program product includes a computer program, and the computer program causes a computer to execute the above method. In some embodiments, a computer program causes a computer to execute the above method.
[0074] In some embodiments, a user equipment (UE) or a radio access network (RAN) may be implemented using a computing platform such as the example computing device 1100 illustratedAtty. Dkt. No. 10085-01-0171-PCT in FIG. 8 or the communication system 1200 illustrated in FIG. 9. As shown in FIG. 8, the computing device 1100 may include a processor 1112, memory 1114, and input / output (VO) interfaces 1118 coupled via a bus 1116. The processor 1112 may execute program code stored in the memory 1114 to perform one or more methods described above with respect to FIGs. 1 to 7. The memory 1114 may be a non-transitory computer-readable medium storing instructions that, when executed, enable NAS message handling, partial decoding, SRB-based routing, or collaboration with the AMF. In some cases, the program code may be stored on a separate computer-readable storage medium or integrated within the device as a computer program product. As shown in FIG. 9, the communication system 1200 may include RF circuitry 1210, baseband circuitry 1220, application circuitry 1230, and memory / storage 1240, among other components such as display 1250, camera 1260, sensor 1270, and I / O interface 1280. The application circuitry 1230 and baseband circuitry 1220 may be configured to execute program instructions and perform processing functions related to NAS signaling, including determining the destination core network function, managing signaling bearers, and communicating with the AMF. These components may be integrated into a mobile or edge device, supporting edge-cloud deployment as described in earlier embodiments. The hardware and software integration in such devices enables flexible and efficient execution of the NAS message distribution mechanisms disclosed herein.
[0075] FIG. 8 is an example of a computing device 1100 according to an embodiment of the present disclosure. Any suitable computing device can be used for performing the operations described herein. For example, FIG. 8 illustrates an example of the computing device 1100 that can implement some embodiments of FIG. 1 to FIG. 7 using any suitably configured hardware and / or software. In some embodiments, the computing device 1100 can include a processor 1112 that is communicatively coupled to a memory 1114 and that executes computer-executable program code and / or accesses information stored in the memory 1114. The processor 1112 may include a microprocessor, an application-specific integrated circuit (“ASIC”), a state machine, or other processing device. The processor 1112 can include any of a number of processing devices, including one. Such a processor can include or may be in communication with a computer-readable medium storing instructions that, when executed by the processor 1112, cause the processor to perform the operations described herein.
[0076] The memory 1114 can include any suitable non-transitory computer-readable medium. The computer-readable medium can include any electronic, optical, magnetic, or other storage device capable of providing a processor with computer-readable instructions or other program code. Non-limiting examples of a computer-readable medium include a magnetic disk, a memory chip, a read-only memory (ROM), a random access memory (RAM), an application specific integrated circuit (ASIC), a configured processor, optical storage, magnetic tape or other magnetic storage, or any other medium from which a computer processor can read instructions. The instructions may include processor-specific instructions generated by a compiler and / or anAtty. Dkt. No. 10085-01-0171-PCT interpreter from code written in any suitable computer-programming language, including, for example, C, C++, C#, visual basic, java, python, perl, javascript, and actionscript.
[0077] The computing device 1100 can also include a bus 1116. The bus 1116 can communicatively couple one or more components of the computing device 1100. The computing device 1100 can also include a number of external or internal devices such as input or output devices. For example, the computing device 1100 is illustrated with an input / output (“I / O”) interface 1118 that can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. The one or more input devices 1120 and one or more output devices 1122 can be communicatively coupled to the I / O interface 1118. The communicative coupling can be implemented via any suitable manner (e.g., a connection via a printed circuit board, connection via a cable, communication via wireless transmissions, etc.). Non-limiting examples of input devices 1120 include a touch screen (e g., one or more cameras for imaging a touch area or pressure sensors for detecting pressure changes caused by a touch), a mouse, a keyboard, or any other device that can be used to generate input events in response to physical actions by a user of a computing device. Non-limiting examples of output devices 1122 include a liquid crystal display (LCD) screen, an external monitor, a speaker, or any other device that can be used to display or otherwise present outputs generated by a computing device.
[0078] The computing device 1100 can execute program code that configures the processor 1112 to perform one or more of the operations described above with respect to some embodiments of FIG. 1 to FIG. 7. The program code may be resident in the memory 1114 or any suitable computer- readable medium and may be executed by the processor 1112 or any other suitable processor.
[0079] The computing device 1100 can also include at least one network interface device 1124. The network interface device 1124 can include any device or group of devices suitable for establishing a wired or wireless data connection to one or more data networks 1128. Non limiting examples of the network interface device 1124 include an Ethernet network adapter, a modem, and / or the like. The computing device 1100 can transmit messages as electronic or optical signals via the network interface device 1124.
[0080] FIG. 9 is a block diagram of an example of a communication system 1200 according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the communication system 1200 using any suitably configured hardware and / or software. FIG. 9 illustrates the communication system 1200 including a radio frequency (RF) circuitry 1210, a baseband circuitry 1220, an application circuitry 1230, a memory / storage 1240, a display 1250, a camera 1260, a sensor 1270, and an input / output (I / O) interface 1280, coupled with each other at least as illustrated.
[0081] The application circuitry 1230 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general -purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory / storage and configured to executeAtty. Dkt. No. 10085-01-0171-PCT instructions stored in the memory / storage to enable various applications and / or operating systems running on the system. The communication system 1200 can execute program code that configures the application circuitry 1230 to perform one or more of the operations described above with respect to some embodiments of FIG. 1 to FIG. 7. The program code may be resident in the application circuitry 1230 or any suitable computer-readable medium and may be executed by the application circuitry 1230 or any other suitable processor.
[0082] The baseband circuitry 1220 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that may enable communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multimode baseband circuitry.
[0083] In various embodiments, the baseband circuitry 1220 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry 1210 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 1210 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
[0084] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to some embodiments of FIG. 1 to FIG. 7 may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and / or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmwareAtty. Dkt. No. 10085-01-0171-PCT modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and / or the memory / storage may be implemented together on a system on a chip (SOC). The memory / storage 1240 may be used to load and store data and / or instructions, for example, for system. The memory / storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and / or non-volatile memory, such as flash memory.
[0085] In various embodiments, the I / O interface 1280 may include one or more user interfaces designed to enable user interaction with the system and / or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and / or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
[0086] In various embodiments, the display 1250 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the communication system 1200 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, an AR / VR glasses, etc. In various embodiments, system may have more or less components, and / or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.
[0087] A person having ordinary skill in the art understands that each of the units, algorithm, and operations described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he / she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.
[0088] It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments areAtty. Dkt. No. 10085-01-0171-PCT exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.
[0089] The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.
[0090] If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the operations disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.
[0091] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.
Claims
Atty. Dkt. No. 10085-01-0171-PCTWhat is claimed is:
1. A method of distributing non-access stratum (NAS) message performed by a user equipment (UE), comprising: generating a NAS message including an indication of a core network (CN) function; encapsulating the NAS message in a radio resource control (RRC) message; and transmitting the RRC message to a radio access network (RAN).
2. The method of claim 1, wherein the indication of the CN function comprises a first information element (IE) in the NAS message.
3. The method of claim 2, wherein the first IE comprises a network function field indicating a network function identity.
4. The method of claim 1, wherein the indication of the CN function is included in an extended payload container type field of the NAS message.
5. The method of claim 4, wherein the extended payload container type field comprises at least one bit used to distinguish the CN function other than an access and mobility management function (AMF) or a session management function (SMF).
6. The method of claim 1, wherein the NAS message targeting an AMF or a SMF comprises a second IE indicating a destination.
7. The method of claim 1, wherein the NAS message is carried by a signaling radio bearer (SRB) that corresponds to the CN function.
8. The method of claim 7, wherein the SRB is selected by a radio resource control (RRC) layer in the UE based on the CN function of the NAS message.
9. The method of claim 8, wherein the SRB comprises one of a plurality of SRBs including at least one of SRB4, SRB5, and SRB6.
10. The method of claim 9, wherein the SRB4 is associated with a first network function, the SRB5 is associated with a second network function, and the SRB6 is associated with a third network function.
11. The method of claim 9, wherein a mapping of the SRBs to respective CN functions is preconfigured or provided via a system configuration signaling.
12. A method of distributing non-access stratum (NAS) message performed by a radio access network (RAN), comprising: receiving a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message comprises a NAS message; decoding at least a portion of the NAS message to extract an indication of a core network (CN) function; and forwarding the NAS message to the CN function based on the indication of the CN function.Atty. Dkt. No. 10085-01-0171-PCT13. The method of claim 12, wherein the indication of the CN function comprises a first information element (IE) in the NAS message.
14. The method of claim 13, wherein the first IE comprises a network function field indicating a network function identity.
15. The method of claim 12, wherein the indication of the CN function is included in an extended payload container type field of the NAS message.
16. The method of claim 15, wherein the extended payload container type field comprises at least one bit used to distinguish the CN function other than an access and mobility management function (AMF) or a session management function (SMF).
17. The method of claim 12, wherein the NAS message targeting an AMF or a SMF comprises a second IE indicating a destination.
18. The method of claim 12, further comprising: determining whether the CN function corresponds to one of an AMF, a SMF, or another CN function based on the indication of the CN function.
19. The method of claim 12, wherein decoding performed by the RAN is limited to parsing a header or predefined field of the NAS message.
20. The method of claim 12, wherein the RAN forwards the NAS message to the CN function without relying on an AMF as an anchor.
21. The method of claim 12, wherein the NAS message is carried by a signaling radio bearer (SRB) that corresponds to the CN function.
22. The method of claim 21, wherein the SRB is selected by a radio resource control (RRC) layer in the UE based on the CN function of the NAS message.
23. The method of claim 22, wherein the SRB comprises one of a plurality of SRBs including at least one of SRB4, SRB5, and SRB6.
24. The method of claim 23, wherein the SRB4 is associated with a first network function, the SRB5 is associated with a second network function, and the SRB6 is associated with a third network function.
25. The method of claim 23, wherein a mapping of the SRBs to respective CN functions is preconfigured or provided via a system configuration signaling.
26. The method of claim 12, further comprising: querying an AMF for a forwarding decision of the NAS message; and transmitting, to the AMF, the indication of the CN function for the NAS message.
27. The method of claim 26, wherein querying the AMF for the forwarding decision of the NAS message comprises forwarding the NAS message to the AMF for decoding.
28. The method of claim 27, further comprising:Atty. Dkt. No. 10085-01-0171-PCT transmitting, to the AMF, a response indicating the CN function after decoding the NAS message; and forwarding the NAS message to the CN function based on the response.
29. The method of claim 26, wherein querying the AMF for the forwarding decision of the NAS message comprises transmitting an indicator extracted from the RRC message carrying the NAS message to the AMF.
30. The method of claim 29, further comprising: receiving from the AMF, a CN function information for routing the NAS message.
31. The method of claim 12, wherein the AMF is deployed in proximity to the RAN in an edge cloud environment.
32. A user equipment (UE), comprising: a generator configured to generate a non-access stratum (NAS) message including an indication of a core network (CN) function and encapsulate the NAS message in a radio resource control (RRC) message; and a transmitter configured to transmit the RRC message to a radio access network (RAN).
33. A user equipment (UE), comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the UE is configured to perform the method of any one of claims 1 to 11.
34. A radio access network (RAN), comprising: a transceiver configured to receive a radio resource control (RRC) message from a user equipment (UE), wherein the RRC message comprises a NAS message; and a decoder configured to decode at least a portion of the NAS message to extract an indication of a core network (CN) function, wherein the transceiver is further configured to forward the NAS message to the CN function based on the indication of the CN function.
35. A radio access network (RAN), comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the RAN is configured to perform the method of any one of claims 12 to 31.