User equipment involving distributed non-access stratum

Abstract

The present disclosure provides a user equipment relating to a distributed non-access stratum. The application relates to devices and components, including apparatuses, systems, and methods, for establishing and utilizing NAS-X connections between devices and network functions of a network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 602,283, filed on November 22, 2023, entitled “User Equipment Involved Distributed Non-Access Stratum,” and U.S. Non-Provisional Application No. 18 / 923,560, filed on October 22, 2024, entitled “User Equipment Involved Distributed Non-Access Stratum,” the disclosures of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] The present application relates to the field of wireless technology, and in particular to user equipment including distributed non-access stratum arrangement and operation. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) network provides for the transmission of non-access stratum (NAS) messages between user equipment (UE) and the network. NAS messages can be exchanged between the UE and the network's access and mobility management function (AMF). If another network function (NF) is required for the NAS message, the AMF forwards the NAS message to the appropriate NF for processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 Illustrated are example network arrangements according to some embodiments.

[0006] Figure 2 Illustrated are example network arrangements according to some embodiments.

[0007] Figure 3 An example RRCreconfiguration information element that may be included in a non-access stratum (NAS) signaling message according to some embodiments is illustrated.

[0008] Figure 4 Example information elements that may be included in a NAS signaling message according to some embodiments are illustrated.

[0009] Figure 5 An example DLInformationTransfer message that may be sent as a NAS signaling message according to some embodiments is illustrated.

[0010] Figure 6An example ULInformationTransfer message that may be sent as a NAS signaling message according to some embodiments is illustrated.

[0011] Figure 7 An example NAS transmission arrangement according to some embodiments is illustrated.

[0012] Figure 8 An example system arrangement according to some embodiments is illustrated.

[0013] Figure 9 An example International Mobile Telecommunications (IMT)-2030 capability representation is illustrated in accordance with some embodiments.

[0014] Figure 10 An example legacy control plane (CP) protocol stack representation 1000 is illustrated in accordance with some embodiments.

[0015] Figure 11 A first portion of an example stack representation is illustrated according to some embodiments.

[0016] Figure 12 Illustrated according to some embodiments Figure 11 The example stack represents the second part.

[0017] Figure 13 Example message arrangements for Option 1 are illustrated according to some embodiments.

[0018] Figure 14 Example message arrangements for Option 2 are illustrated in accordance with some embodiments.

[0019] Figure 15 Example message arrangements for Option 3 are illustrated in accordance with some embodiments.

[0020] Figure 16 Example message arrangements for Option 4 are illustrated in accordance with some embodiments.

[0021] Figure 17 Example message arrangements for Option 5 are illustrated in accordance with some embodiments.

[0022] Figure 18 Example message arrangements for Option 6 are illustrated in accordance with some embodiments.

[0023] Figure 19 An example service request arrangement for option 1.1 is illustrated according to some embodiments.

[0024] Figure 20 An example service request arrangement for option 1.2 is illustrated, according to some embodiments.

[0025] Figure 21 An example service request arrangement for Option 2 is illustrated, according to some embodiments.

[0026] Figure 22 An example network function (NF) arrangement according to some embodiments is illustrated.

[0027] Figure 23 An example user equipment (UE) mobility arrangement is illustrated in accordance with some embodiments.

[0028] Figure 24 An example UE handover (HO) arrangement according to some embodiments is illustrated.

[0029] Figure 25 An example UE HO arrangement according to some embodiments is illustrated.

[0030] Figure 26 An example process for generating a NAS-X message according to some embodiments is illustrated.

[0031] Figure 27 An example process for establishing a NAS-X connection according to some embodiments is illustrated.

[0032] Figure 28 An example process for providing NAS messages to a NF according to some embodiments is illustrated.

[0033] Figure 29 An example UE according to some embodiments is illustrated.

[0034] Figure 30 An example next-generation Node B (gNB) is illustrated in accordance with some embodiments. DETAILED DESCRIPTION

[0035] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of illustration and not limitation, so as to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who have the benefit of this disclosure that the various aspects of the various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments due to unnecessary details. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B); and the phrase "based on A" means "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0036] The following is a glossary of terms that may be used in this disclosure.

[0037] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on a chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" can also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit.

[0038] As used herein, the term "processor circuitry" refers to, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, or transferring digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0039] As used herein, the term "interface circuitry" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0040] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can represent a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0041] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0042] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resource" may refer to any type of shared entity that provides a service and may include computing resources or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and can be clearly identified.

[0043] As used herein, the term "channel" refers to any tangible or intangible transmission medium for conveying data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for sending and receiving information.

[0044] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0045] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0046] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0047] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0048] As used herein, the term "based at least in part on" may indicate that one item is based only on another item and / or based on another item and one or more additional items. For example, in an embodiment, determining item 1 based at least in part on item 2 may indicate determining item 1 based only on item 2 and / or determining item 1 based on item 2 and one or more other items.

[0049] As used herein, the term "base station" may include a base station, any generation of Node B (including Node B, evolved Node B (eNB), and next generation Node B (gNB)), and / or a radio access network (RAN) node. Furthermore, the terms "gNB" and "RAN node" may refer to a base station, any generation of Node B, and / or a RAN node.

[0050] In a traditional network arrangement, the Access and Mobility Management Function (AMF) receives Non-Access Stratum (NAS) messages from User Equipment (UE) via base stations connected to the AMF. The traditional AMF determines to which Network Function (NF) each Non-Access Stratum (NAS) message is directed and forwards the NAS message to the appropriate NF. Because each AMF may be connected to multiple base stations and / or UEs, the AMF processes NAS messages from each base station and / or UE. As networks advance, the number of NAS messages continues to grow, and the AMF may become a point of delay because it may have difficulty processing all NAS messages in a timely manner.

[0051] The methods described throughout this disclosure allow NAS messages to be sent directly to a target NF via a NAS-X connection, rather than having to go through an AMF to reach the target NF. A base station in the network can receive NAS messages from a connected UE and direct them to the appropriate NAS-X connection for the target NF. Because a base station processes NAS messages for a single base station, compared to a traditional AMF that processes NAS messages for multiple base stations, using a base station to direct NAS messages to the target NF via a NAS-X connection can result in faster NAS message processing and / or eliminate latency issues associated with traditional AMFs.

[0052] NAS connection between the core network (CN) and the UE

[0053] Fifth Generation (5G): Radio Resource Control (RRC) aspects for NAS signaling

[0054] The traditional access stratum (AS) RRC message design may include the following features: UE-specific NAS messages are delivered via signaling radio bearer 1 (SRB1) or signaling radio bearer 2 (SRB2). UE-specific NAS messages are transparent to RRC. Figure 1 and Figure 2 The message illustrated in can be used to carry NAS signaling.

[0055] Figure 1 An example network arrangement 100 according to some embodiments is illustrated. The network arrangement 100 includes a UE 102. The UE 102 may include a UE 2900 ( Figure 29 ) features. The network arrangement 100 includes a network 104. The network 104 may include a base station (such as a gNB 3000 ( Figure 30 )) and / or core network. UE 102 may send an uplink (UL) information transfer message 106 to network 104. UL information transfer message 106 may be used to carry NAS signaling.

[0056] Figure 2 An example network arrangement 200 according to some embodiments is illustrated. The network arrangement 200 includes a UE 202. The UE 202 may include a UE 2900 ( Figure 29 ) features. The network arrangement 200 includes a network 204. The network 204 includes a base station (such as a gNB 3000 ( Figure 30 )) and / or core network. UE 202 may send a downlink (DL) information transfer message 206 to network 204. DL information transfer message 206 may be used to carry NAS signaling.

[0057] Figures 3 to 6 Example information elements that may be included in a NAS signaling message are illustrated. Figure 3 Illustrated is an example RRCreconfiguration information element 300 that may be included in a NAS signaling message according to some embodiments. Figure 4 Illustrated are example information elements 400 that may be included in a NAS signaling message according to some embodiments. The information elements 400 include an RRCSetupComplete information element 402 and an RRCResumeComplete information element 450. Figure 5 Illustrated is an example DLInformationTransfer message 500 that may be sent as a NAS signaling message according to some embodiments. Figure 6Illustrated is an example ULInformationTransfer message 600 that may be sent as a NAS signaling message according to some embodiments.

[0058] During initial access (Resume / Setup), NAS messages can be carried in the RRCResumeComplete and RRCSetupComplete messages. For example, during the UE's initial access to the network, the NAS message can be included in the RRCResumeComplete information element 450 ( Figure 4 ) and / or RRCSetupComplete information element 402 ( Figure 4 )middle.

[0059] In connected mode, NAS messages can be sent in both UL and DL directions. In the UL direction, NAS messages can be carried in ULInformationTransfer. For example, in the UL direction, NAS messages can be carried in ULInformationTransfer message 600 ( Figure 6 ) in the DL direction. In the DL direction, the NAS message can be carried in the DLInformationTransfer or in the RRCReconfiguration (no handover (HO) case). For example, in the DL direction, the NAS message can be carried in the DLInformationTransfer message 500 ( Figure 5 ) or in the RRCreconfiguration element 300 ( Figure 3 ) is carried in.

[0060] For UE operation, one or more of the following features may be implemented by the UE for NAS signaling. In idle / inactive mode, NAS signaling may not be present. For example, when the UE is in idle and / or inactive mode, the UE may not perform NAS signaling. In connected mode, in the DL direction, received signaling may be forwarded to the NAS. In the UL direction, NAS signaling may be carried in the RRC message used for transmission.

[0061] For next generation Node B (gNB) (where the gNB can be a base station) operation (in the gNB-Central Unit (CU)), NAS messages can be forwarded between the UE and the AMF. The AMF selection can be based on either the shortened fifth generation temporary mobile subscriber identity (5G-S-TMSI) or the globally unique access and mobility management function identifier (GUAMI) (TS 23.501, Technical Specification Section 6.3.5 (TS 23.501 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 18). (2023). 3GPP TS 23.501, 18.3.0)).

[0062] 5G: Control Plane (CP) Protocol Stack for NAS Transport

[0063] Characteristics of the CP protocol stack for NAS transport may include that all NAS signaling is anchored / terminated at the AMF. Other core network (CN) entities communicate indirectly with the UE via the AMF.

[0064] The details of the CP protocol stack for NAS transport may include one or more of the following. NAS signaling may be sent transparently between the UE and the AMF via the Radio Access Network (RAN). NAS proposals may consist of non-access stratum mobility management (NAS-MM) messages for registration management (RM) / connection management (CM), security, etc., and may also provide transport services for other payloads, such as session management (SM), UE policy, etc. On the CN side, the AMF may be the anchor and may terminate the NAS-MM message and transparently forward the payload to the relevant network function (NF), such as SM to session management function (SMF), UE policy to policy control function (PCF), etc. Note that the NAS-X connection may provide direct / indirect communication between the UE and the NF.

[0065] Figure 7 Illustrated is an example NAS transmission arrangement 700 according to some embodiments. The NAS transmission arrangement 700 illustrates NAS transmission for SM, Short Message Service (SMS), UE Policy and / or Location Services (LCS). Figure 8 An example system arrangement 800 is illustrated according to some embodiments.

[0066] Sixth Generation (6G): International Mobile Telecommunications (IMT)-2030 Capabilities

[0067] IMT-2030 is expected to provide enhanced capabilities compared to IMT-2020, as well as new capabilities to support the extended usage scenarios of IMT-2030. The capabilities of IMT-2030 may include one or more of the following. These capabilities may include peak data rate (values of 50, 100, 200 Gbit / s are given as possible examples applicable to specific situations), user experienced data rate (values of 300 Mbit / s and 500 Mbit / s), spectrum efficiency (values of 1.5 times and 3 times that of IMT-2020), area service efficiency (30 Mbit / s / m2), and data rate. 2 and 50Mbit / s / m 2 value), connection density (106-108 devices / kilometer (km)), mobility (500-1000km / hour (h)), latency (0.1-1 millisecond (ms)), reliability (1-10 -5 to 1-10 -7 ), coverage (coverage is defined as the cell edge distance of a single cell through link budget analysis), positioning (accuracy can be 1-10 centimeters (cm)), sensing-related capabilities (which can be measured in terms of accuracy, resolution, detection rate, false alarm rate, etc.), artificial intelligence (AI)-related capabilities (including distributed data processing, distributed learning, AI computing, AI model execution and AI model inference, etc.), security, privacy and resilience, sustainability (energy efficiency is a quantifiable measure of sustainability), and / or interoperability (referring to the radio interface based on member inclusiveness and transparency, and the functionality between different entities of the system).

[0068] Figure 9 An example IMT-2030 capability representation 900 is illustrated in accordance with some embodiments. The IMT-2030 capability representation 900 illustrates example capabilities expected to be implemented in IMT-2030. The IMT-2030 capability representation 900 illustrates new capabilities 902 expected to be included in IMT-2030 and enhanced capabilities 904 expected to be included in IMT-2030. The ranges of values given for the capabilities within the IMT-2030 capability representation 900 are estimated targets for studies and investigations into IMT-2030.

[0069] 6G Challenges to 5G NAS Signaling Transport Design

[0070] 6G trends and challenges to 5G may include one or more of the following. As a first challenge, 6G may have greater connection density (106-108 devices / km) than 5G. As an observation, the amount of NAS signaling may increase due to the increase in connection density and may be much greater than that in 5G. The challenge is that the significant increase in NAS signaling between the UE and the CN may increase the burden on the AMF.

[0071] As a second challenge, 6G can achieve lower latency (0.1-1ms) than 5G. As an observation, low latency means that transmission between the UE and the CN can be faster than in 5G. The challenge is that indirect NAS signaling between the UE and other NFs via the AMF will increase the latency of NAS signaling and processing.

[0072] As a third challenge, new 6G capabilities (e.g., AI, sensing) may introduce new NFs to handle new use cases in the core network. As an observation, new NAS procedures / signaling between the UE and NAS may be introduced to handle new use cases. The challenge remains that maintaining the AMF as the anchor for forwarding NAS signaling between the UE and the new NFs does not support new use cases well in terms of signaling latency and AMF load.

[0073] Problem Statement

[0074] Issues regarding 5G NAS signaling transport design may include the following. In 5G, the AMF is the anchor that handles all NAS messages to and from the UE (i.e., terminates NAS-MM messages) and transparently forwards the payload to the relevant NF. In order to support the 6G vision / trend, the 5G design has some issues. As a first issue, the AMF will be overloaded due to the significant increase in NAS signaling. As a second issue, the AMF will be more complex due to the introduction of more and more new NFs in 6G, which may cause problems in terms of signaling delay and AMF load.

[0075] Some 6G design considerations regarding NAS signaling transport mechanisms may include the following. One direction may be to support direct NAS signaling communication between the UE and CN functions via RAN nodes, i.e., without forwarding via the AMF. In this direction, the methods described throughout this disclosure address one or more of the following issues: 1. How can the RAN nodes identify and forward NAS messages to different NFs? 2. How is a direct NAS-X connection established between the UE and NF? 3. Are there any relationships between different NAS-X connections at the same time? 4. How is mobility of a UE with multiple NAS-X connections handled?

[0076] method

[0077] General Description

[0078] For a single UE connection, multiple NAS-X connections can be established between the UE and different NFs for different purposes. For example, a UE can establish one or more NAS-X connections with a NF within the network. A NAS-X connection can be between a UE and a NF. A NAS-X connection can be a direct connection between the UE and the NF, allowing messages sent via the NAS-X connection to be exchanged between the UE and the NF without the network's AMF acting as an intermediary. Therefore, the AMF does not need to receive and forward messages sent to different NFs via the NAS-X connection.

[0079] There are two options for multiple NAS-X connections between a UE and an NF. In the first option (which may be referred to as Option 1), NAS-X connections may be established between the UE and different NF types. In the second option (which may be referred to as Option 2), NAS-X connections may be established between the UE and different NFs belonging to the same NF type. (For example, due to the slicing concept, the network may include more than one Session Management Function (SMF) for NAS-SM functions).

[0080] For each NAS-X connection, the RAN node can distinguish the NAS-X connections and forward NAS messages to the corresponding NF. To distinguish NAS-X connections within the RAN node, the AS procedures for NAS message transmission can be redesigned. NAS messages for NAS-X connections are sent and distinguished directly between the UE and the gNB via RRC.

[0081] There can be an association between different NAS-X connections of a UE. A NAS-AMF connection (i.e., the connection between the UE and the anchor AMF) can be the anchor connection of the UE. Other NAS-X connections are associated with one NAS-AMF connection.

[0082] NF selection can be performed across multiple NFs of the same NAS-X connection type. NF selection can be performed in the UE, gNB, AMF, or based on some rules. Mobility can be based on the anchor NAS-AMF connection. If the anchor AMF changes, the associated NAS-X connection (if affected) can also change. The AMF can be aware of other NAS-X connections.

[0083] Control plane protocol stack for NAS signaling transmission

[0084] Figure 10 An example legacy CP protocol stack representation 1000 according to some embodiments is illustrated. The CP protocol stack representation 1000 illustrates the sending of NAS messages according to a legacy system.

[0085] The CP protocol stack representation 1000 may include a UE 1002, a base station 1004 (which may be a gNB), and an AMF 1006. The UE 1002 includes a UE 2900 ( Figure 29 ) one or more features. The base station 1004 may include a gNB 3000 ( Figure 30 ) features. AMF 1006 may be an AMF of a core network. UE 1002 may establish a connection with AMF 1006 via base station 1004.

[0086] The UE 1002 may include a NAS layer 1008. The UE 1002 may also include one or more other protocol layers 1010, which in the illustrated embodiment include an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical layer (PHY).

[0087] The base station 1004 may include one or more protocol layers 1012 corresponding to the one or more other protocol layers 1010 of the UE. Messages within the one or more other protocol layers 1010 and the one or more protocol layers 1012 may be exchanged between the UE 1002 and the base station 1004 so that the messages can be processed by both the UE 1002 and the base station 1004.

[0088] The AMF 1006 may include a NAS layer 1014. Messages within the NAS layer 1008 and the NAS layer 1014 may be exchanged between the UE 1002 and the AMF 1006 so that the messages may be processed by the UE 1002 and the AMF 1006. The base station 1004 may forward messages between the NAS layer 108 and the NAS layer 1014.

[0089] Figure 11 and Figure 12 An example stack representation 1100 for a distributed NAS architecture involving UEs according to some embodiments is illustrated. Specifically, Figure 11 A first portion of an example stack representation 1100 is illustrated in accordance with some embodiments. Figure 12 A second portion of an example stack representation 1100 is illustrated in accordance with some embodiments.

[0090] The stack representation 1100 may include a UE 1102, a base station 1104, and one or more NFs of a network. In the illustrated embodiment, the one or more NFs include an AMF 1202, a first SMF 1204, and a second SMF 1206. The UE 1102 may include a UE 2900 ( Figure 29 ) features. The base station 1104 may include a gNB 3000 ( Figure 30) features.

[0091] The UE 1102 may establish a NAS-X connection with a NF of the network via a base station 1104, as further described throughout this disclosure. In the illustrated embodiment, the UE 1102 may establish a NAS-AMF connection 1106 with an AMF 1202, a first NAS-SMF connection 1108 with a first SMF 1204, and a second NAS-SMF connection 1110 with a second SMF 1206. The NAS-AMF and NAS-SMF in the stack representation 1100 are not examples.

[0092] The NAS-AMF connection 1106 may be used to exchange non-access stratum mobility management (NAS-MM) messages between the UE 1102 and the AMF 1202. In the illustrated embodiment, the UE 1102 includes a NAS-AMF / MM representation 1112, and the AMF 1202 includes a NAS-AMF / MM representation 1208, to illustrate that the UE 1102 and the AMF 1202 may exchange NAS-MM messages. The AMF 1202 may process the NAS-AMF messages received from the UE 1102.

[0093] The first NAS-SMF connection 1108 may be used to exchange non-access stratum session management (NAS-SM) messages between the UE 1102 and the first SMF 1204. In the illustrated embodiment, the UE 1102 includes a NAS-SMF1 / SM representation 1114, and the first SMF 1204 includes a NAS-SMF1 / SM representation 1210 to illustrate that the UE 1102 and the first SMF 1204 may exchange NAS-SM messages. The first SMF 1204 may process NAS-SMF1 messages received from the UE 1102.

[0094] The second NAS-SMF connection 1110 may be used to exchange NAS-SM messages between the UE 1102 and the second SMF 1206. In the illustrated embodiment, the UE 1102 includes a NAS-SMF2 / SM representation 1116, and the second SMF 1206 includes a NAS-SMF2 / SM representation 1212, to illustrate that the UE 1102 and the second SMF 1206 may exchange NAS-SM messages. The second SMF 1206 may process the NAS-SMF2 messages received from the UE 1102.

[0095] The messages sent via the NAS-AMF connection 1106, the first NAS-SMF connection 1108, and the second NAS-SMF connection 1110 may be sent via the RRC layer. Therefore, these messages may be RRC messages.

[0096] UE 1102 may generate messages to be sent via NAS-AMF connection 1106, first NAS-SMF connection 1108, and second NAS-SMF connection 1110. As part of generating the messages, UE 1102 may include an indication of a target NAS-X connection and / or target NF for the messages, as further described throughout this disclosure. UE 1102 may send these messages to base station 1104.

[0097] The base station 1104 may receive these messages from the UE 1102. The base station 1104 may identify an indication of the target NAS-X connection and / or target NF of the received message. The base station 1104 may then forward the message to the appropriate one of the AMF 1202, the first SMF 1204, or the second SMF 1206 based on the indication. Since the base station 1104 can forward the message directly to the appropriate NF instead of forwarding all messages to the AMF 1202 (as in conventional methods), the demand on the AMF 1202 may be reduced compared to conventional methods.

[0098] NAS-X connection identifier in the RAN node

[0099] Different NAS-X connections can be identified between the UE and the RAN node using the following options. For example, the UE can generate a message according to any of the following options to indicate the target NAS-X connection and / or NF for the message. The UE can send the message to the base station. The base station can determine the target NAS-X connection and / or NF based on these indications and forward the message to the appropriate NF based on these indications.

[0100] In Option 1, an explicit indication can be included in an RRC message to identify the NAS-X connection. For example, the UE can generate a NAS message to be sent via one of the NAS-X connections already established between the UE and a NF of the network. The NAS message can include an indication of the target NAS-X connection and / or target NF for the NAS-X message. The NAS message can be an RRC message. One SRB can be used for all NAS messages, and the NAS-X connection identity can be explicitly indicated in the RRC message.

[0101] In Option 2, SRB-level NAS-X connection identification can be implemented. Different SRBs can be used to send NAS messages for different NAS-X connections. For example, each NAS-X connection established by a UE can have a corresponding SRB. Therefore, the SRB on which the UE sends a NAS message can indicate the target NAS-X connection and / or target NF of the NAS message. The UE can send a NAS message on an SRB, or indicate the SRB on which the NAS message is to be sent, to indicate the target NAS-X connection and / or target NF.

[0102] In option 3, radio link control (RLC) bearer and / or logical channel (LCH) level NAS-X connection identification can be implemented. Different RLC bearers and / or LCHs can be used for the transmission of NAS messages belonging to different NAS-X connections. For example, each of the NAS-X connections established by the UE can have a corresponding RLC bearer and / or LCH. Therefore, the RLC bearer and / or LCH associated with the NAS message can indicate the target NAS-X connection and / or target NF for the NAS message. The UE can send a NAS message on an RLC bearer, indicate the RLC bearer on which the NAS message is to be sent, utilize an LCH, and / or indicate the LCH to be used to indicate the target NAS-X connection and / or target NF.

[0103] Option 4 may be a combination of Option 1 and Option 2. Option 2 may be implemented by using an SRB to identify the NAS-X connection type, and Option 1 may be implemented by using an explicit indication in an RRC message to identify a special NAS-X connection of the same type. For example, the UE may generate a NAS message with an indication of a target NAS-X connection and / or a target NF indicating the NAS-X connection type, and the UE may send the NAS message on an SRB, or indicate the SRB on which the NAS message is to be sent, to indicate the NAS-X connection type.

[0104] Option 5 may be a combination of Option 1 and Option 3. Option 3 may be implemented by using the LCH to identify the NAS-X connection type, and Option 1 may be implemented by using an explicit indication in the RRC message to identify a special NAS-X connection of the same type. For example, the UE may generate a NAS message with an indication of the target NAS-X connection and / or target NF indicating the NAS-X connection type, and the UE may utilize the LCH for the NAS message, or indicate the LCH to be used for the NAS message, to indicate the NAS-X connection type.

[0105] Option 6 may be a combination of Option 2 and Option 3. Option 2 may be implemented by using an SRB to identify the NAS-X connection type, and Option 3 may be implemented by using an LCH to identify the same type of NAS-X connection. For example, the UE may utilize an LCH for a NAS message of a target NAS-X connection and / or target NF indicating the NAS-X connection type, or indicate an LCH to be used therefor, and the UE may send the NAS message on an SRB, or indicate an SRB on which the NAS message is to be sent, to indicate the NAS-X connection type.

[0106] In Option 7, different RRC connection instances can be used simultaneously for different NAS-X connections. For example, different RRC connection instances can be associated with different NAS-X connections and / or different NFs. The UE can use the RRC connection instance used to send a NAS-X message to indicate the target NAS-X connection and / or target NF of the NAS-X message.

[0107] A method for providing an NF identifier (ID) may be implemented (i.e., carrying an NF ID in an RRC message to help a RAN node identify a NAS-X connection and a target NF). The NF ID may be assigned by a RAN node, allocated in a NAS-X context, or predefined in a specification. For example, a UE may have or be provided with an NF ID that identifies a NAS-X connection and / or a NF with which the UE can establish a NAS-X connection. The NF ID may be assigned by a base station, included in a NAS-X context received by the UE, or defined by a specification associated with the UE. The UE may generate a NAS message with the NF ID to indicate the target NAS-X connection and / or target NF of the NAS message.

[0108] The RAN node operations may include the following. Based on the identifier on the NAS-X connection, the RAN node may establish a connection to the corresponding NF (if the NAS-X connection has not been previously established in the network interface) and forward the message to the NF. For example, the base station may determine the target NAS-X connection and / or target NF for the NAS message based on an indication from one or more of the options for the NAS-X connection identifier described above. The base station may forward the NAS message on the target NAS-X connection and / or forward it to the target NF based on the indication. If a NAS-X connection has not been previously established, the base station may establish a NAS-X connection with the target NF.

[0109] The options for NAS-X connection identification are further described below.

[0110] NAS-X connection identification in RAN nodes: AS impact

[0111] For Option 1, an explicit indication can be included in the RRC message to identify the NAS-X connection. In the RRC message used for NAS message transmission, the RRC message can include two fields: a NAS type field and a CN entity information field. The NAS type field can be used to distinguish NAS-X types (i.e., functions such as Mobility Management (MM) / SM / UE policy). The CN entity information field can carry specific information about a specific NF. The CN entity information field can carry the NF ID or address information of the target NF, or carry auxiliary information (e.g., slice information, service information) to help the RAN select / forward NAS messages.

[0112] Figure 13 An example message arrangement 1300 is illustrated for Option 1 according to some embodiments. For example, the message arrangement 1300 illustrates an example of NAS message content and transmission information according to Option 1. The NAS message may be an RRC message.

[0113] In the illustrated embodiment, message arrangement 1300 includes a first message arrangement 1302 and a second message arrangement 1304. First message arrangement 1302 illustrates an example of message content and transmission information of a first NAS message, and second message arrangement 1304 illustrates an example of message content and transmission information of a second NAS message.

[0114] The first message arrangement 1302 may include a NAS type field 1306, a CN entity information field 1308, and a message container field 1310 (in the illustrated embodiment, a NAS-MM message container field). The NAS type field 1306 may indicate the NAS-X type of the first NAS message (such as a mobility management (MM) type, SM type, UE policy type, and / or other types of functions). In the illustrated embodiment, the NAS type field 1306 indicates that the NAS message is an MM type message.

[0115] The CN entity information field 1308 may include information indicating the NF of the NAS message. The CN entity information field 1308 may include the NF ID of the target NF of the NAS message, address information of the target NF of the NAS message, and / or information that helps the base station determine the target NF of the NAS message. In some embodiments, the CN entity information field 1308 may include the target CN entity ID and / or the address of the target NF.

[0116] The message container field 1310 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1310 may include data related to the MM.

[0117] Second message arrangement 1304 may include a NAS type field 1312, a CN entity information field 1314, and a message container field 1316 (in the illustrated embodiment, a NAS-SM message container field). NAS type field 1312 may include characteristics of NAS type field 1306, CN entity information field 1314 may include characteristics of CN entity information field 1308, and message container field 1316 may include characteristics of message container field 1310. In the illustrated embodiment, NAS type field 1312 indicates that the NAS message is an SM type message. Additionally, message container field 1316 may include data related to the SM.

[0118] UE (such as UE 2900 ( Figure 29 )) may generate a first message corresponding to first message arrangement 1302 and a second message corresponding to second message arrangement 1304. The UE may send the first message and the second message to the base station. The UE may send the first message and the second message via the same SRB or different SRBs. In the illustrated embodiment, the first message and the second message are both sent over SRB2.

[0119] The base station may determine the target NAS-X connection and / or target NF of the first message based on the information in the NAS type field 1306 and / or the information in the CN entity information field 1308. Furthermore, the base station may determine the target NAS-X connection and / or target NF of the second message based on the information in the NAS type field 1312 and / or the information in the CN entity information field 1314. The base station may forward the first message to the determined target NAS-X connection and / or target NF of the first message, and may forward the second message to the determined target NAS-X connection and / or target NF of the second message.

[0120] For Option 2, SRB-level NAS-X connection identification can be implemented. The RAN can establish different SRBs for NAS messages for different NAS-X connections. The RAN can identify the NAS-X connection (type) based on the SRB ID. For example, SRB #2 can be used for the AMF, SRB #3 can be used for the SMF, and SRB #4 can be used for the PCF. The mapping between SRB ID and NAS connection (type) can be predefined in the specifications related to the NAS messages or configured by the network.

[0121] Figure 14 An example message arrangement 1400 is illustrated for Option 2 according to some embodiments. For example, the message arrangement 1400 illustrates an example of NAS message content and transmission information according to Option 2. The NAS message may be an RRC message.

[0122] The message arrangement 1400 may include a first message arrangement 1402. The first message arrangement 1402 illustrates an example of message content and transmission information of a first NAS message.

[0123] First message arrangement 1402 may include a CN entity information field 1404 and a message container field 1406. CN entity information field 1404 may provide information related to the NF of the first NAS message. In some embodiments, CN entity information field 1404 may include a target CN entity ID of the target NF, an address of the target NF, and / or key information used to identify the target NF of the first message. Message container field 1406 may include data to be sent via the NAS message. For example, in the illustrated embodiment, message container field 1406 may include data related to an MM.

[0124] The first message may be sent to the base station via the SRB corresponding to the target NAS-X connection and / or target NF of the first message. For example, the UE may determine the SRB to be used for sending the first message based on the target NAS-X connection and / or target NF of the first message. The mapping for determining which SRBs correspond to which NAS-X connections and / or NFs may be provided to the UE by the network (such as via the base station) or may be defined in a specification related to NAS communication. The UE may send the first message via the determined SRB or indicate the determined SRB on which the first message is to be sent. In the illustrated embodiment, the first message is shown as being sent via SRB#X.

[0125] The base station may identify the first message received from the UE and determine the SRB on which the first message was received. The base station may determine a target NAS-X connection and / or a target NF for the first message based on the SRB on which the first message was received. A mapping for determining which SRBs correspond to which NAS-X connections and / or NFs may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may forward the first message to the determined target NAS-X connection and / or the determined target NF.

[0126] For option 3, RLC bearer / LCH level NAS-X connection identification can be implemented. Similar to option 2, to save SRBID resources, the network can allocate different LCHs for different NAS connections.

[0127] Figure 15 An example message arrangement 1500 is illustrated for Option 3 according to some embodiments. For example, the message arrangement 1500 illustrates an example of NAS message content and transmission information according to Option 3. The NAS message may be an RRC message.

[0128] In the illustrated embodiment, message arrangement 1500 includes a first message arrangement 1502 and a second message arrangement 1504. First message arrangement 1502 illustrates an example of message content and transmission information of a first NAS message, and second message arrangement 1504 illustrates an example of message content and transmission information of a second NAS message.

[0129] The first message arrangement 1502 may include a CN entity information field 1506 and a message container field 1508 (in the illustrated embodiment, a NAS-MM message container field). In some embodiments, the CN entity information field 1506 may include the target CN entity ID and / or the address of the target NF. The message container field 1508 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1508 may include data related to MM. In some embodiments, the first message arrangement 1502 may include an SRB field 1510. The SRB field 1510 may include an indication of the SRB used to send the first message.

[0130] The second message arrangement 1504 may include a CN entity information field 1512 and a message container field 1514 (in the illustrated embodiment, a NAS-SM message container field). In some embodiments, the CN entity information field 1512 may include the target CN entity ID and / or the address of the target NF. The message container field 1514 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1514 may include data related to the MM. In some embodiments, the second message arrangement 1504 may include an SRB field 1516. The SRB field 1516 may include an indication of the SRB used to send the first message.

[0131] The message may be associated with an LCH corresponding to the target NAS-X connection and / or target NF of the message. For example, the UE may determine the LCH to be used for sending the message based on the target NAS-X connection and / or target NF of the message. The mapping used to determine which LCHs correspond to which NAS-X connections and / or NFs may be provided to the UE by the network (such as via a base station) or may be defined in specifications related to NAS communications. The UE may associate the message with the determined LCH or indicate the determined LCH with which the message is to be associated.

[0132] In the illustrated embodiment, the first message is associated with LCH#A, as indicated by first message arrangement 1502. In the illustrated embodiment, LCH#A corresponds to a NAS-AMF connection. Thus, the UE associating the first message with LCH#A may indicate that the first message will be sent to and / or provided to the AMF via a NAS-AMF connection.

[0133] In the illustrated embodiment, the second message is associated with LCH#B, as indicated by second message arrangement 1504. In the illustrated embodiment, LCH#B corresponds to a NAS-SMF connection. Thus, the UE associating the second message with LCH#B may indicate that the second message will be sent to and / or provided to the AMF via a NAS-AMF connection.

[0134] The UE may send the first message and the second message to the base station. The base station may determine which LCH each of the messages is associated with. For example, in the illustrated embodiment, the base station may determine that the first message is associated with LCH#A and the second message is associated with LCH#B. In addition, the base station may determine the NAS-X connection and / or NF associated with the determined LCH. The base station may forward the message via the determined NAS-X connection and / or forward the message to the determined NF. For example, in the illustrated embodiment, the base station may forward the first message via a NAS-AMF connection and / or forward the first message to the AMF, and may forward the second message via a NAS-SMF connection and / or forward the second message to the SMF.

[0135] Option 4 can be a combination of Option 1 and Option 2. Option 4 can use SRB to identify the NAS-X connection type similar to Option 2. In addition, Option 4 can use an explicit indication in the RRC message to identify a specific NAS-X connection of the same type similar to Option 1.

[0136] Figure 16 An example message arrangement 1600 is illustrated for Option 4 according to some embodiments. For example, the message arrangement 1600 illustrates an example of NAS message content and transmission information according to Option 4. The NAS message may be an RRC message.

[0137] In the illustrated embodiment, message arrangement 1600 includes a first message arrangement 1602 and a second message arrangement 1604. First message arrangement 1602 illustrates an example of message content and transmission information of a first NAS message, and second message arrangement 1604 illustrates an example of message content and transmission information of a second NAS message.

[0138] The first message arrangement 1602 may include a CN entity information field 1606 and / or a message container field 1608 (in the illustrated embodiment, a NAS-MM message container field). The CN entity information field 1606 may include information indicating the type of NAS message, a NAS-X connection, where the type matches the type indicated by the SRB associated with the NAS message (as further described below). The CN entity information field 1606 may include the NF ID of the target NF of the NAS message and / or address information of the target NF of the NAS message. In some embodiments, the CN entity information field 1606 may include the target CN entity ID and / or the address of the target NF.

[0139] The message container field 1608 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1608 may include data related to the SM.

[0140] The first message may be sent to the base station via an SRB corresponding to the target NAS-X connection type of the first message. For example, the UE may determine the SRB to be used for sending the first message based on the target NAS-X connection type of the first message. Information for determining which SRBs correspond to which NAS-X connection types may be provided to the UE by the network (such as via the base station) or may be defined in specifications related to NAS communications. The UE may send the first message via the determined SRB or indicate the determined SRB on which the first message is to be sent. In the illustrated embodiment, the first message is shown as being sent via SRB2 corresponding to the NAS-SMF1 connection.

[0141] The base station may identify the first message received from the UE and determine the SRB on which the first message was received. The base station may determine the target NAS-X connection type based on the SRB on which the first message was received. A mapping for determining which SRBs correspond to which NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may identify an indication of a target NAS-X connection type from the CN entity information field 1706 and may determine the target NAS-X connection and / or target NF based on the indication. The base station may forward the first message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the first message on a NAS-SMF1 connection and / or forward the first message to SMF1.

[0142] The second message may be sent to the base station via an SRB corresponding to the target NAS-X connection type of the second message. For example, the UE may determine the SRB to be used for sending the second message based on the target NAS-X connection type of the second message. Information for determining which SRBs correspond to which NAS-X connection types may be provided to the UE by the network (such as via the base station) or may be defined in specifications related to NAS communications. The UE may send the second message via the determined SRB or indicate the determined SRB on which the first message is to be sent. In the illustrated embodiment, the second message is shown as being sent via SRB3 corresponding to the NAS-SMF2 connection.

[0143] The base station may identify the second message received from the UE and determine the SRB on which the second message was received. The base station may determine the target NAS-X connection type based on the SRB on which the second message was received. A mapping for determining which SRBs correspond to which target NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in specifications related to NAS message transmission. The base station may identify an indication of the target NAS-X connection type from the CN entity information field 1712 and may determine the target NAS-X connection and / or target NF based on the indication. The base station may forward the second message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the second message on a NAS-SMF2 connection and / or forward the second message to SMF2.

[0144] Option 5 may be a combination of Option 1 and Option 3. Option 5 may use the LCH to identify the NAS-X connection type similar to Option 3. Option 5 may use an explicit indication in the RRC message to identify a specific NAS-X connection of the same type similar to Option 1.

[0145] Figure 17 An example message arrangement 1700 is illustrated for Option 5 according to some embodiments. For example, the message arrangement 1700 illustrates an example of NAS message content and transmission information according to Option 5. The NAS message may be an RRC message.

[0146] In the illustrated embodiment, message arrangement 1700 includes a first message arrangement 1702 and a second message arrangement 1704. First message arrangement 1702 illustrates an example of message content and transmission information of a first NAS message, and second message arrangement 1704 illustrates an example of message content and transmission information of a second NAS message.

[0147] The first message arrangement 1702 may include a CN entity information field 1706 and / or a message container field 1708 (in the illustrated embodiment, a NAS-MM message container field). The CN entity information field 1706 may include information indicating the type of NAS message, the NAS-X connection, where the type matches the type indicated by the SRB associated with the NAS message (as further described below). The CN entity information field 1706 may include the NF ID of the target NF of the NAS message and / or address information of the target NF of the NAS message. In some embodiments, the CN entity information field 1706 may include the target CN entity ID and / or the address of the target NF.

[0148] The message container field 1708 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1708 may include data related to the SM.

[0149] In some embodiments, the first message arrangement 1702 may include an SRB field 1710. The SRB field 1710 may indicate the SRB on which the first message is to be sent. In the illustrated embodiment, the SRB field 1710 indicates that the first message is to be sent on SRB2.

[0150] The second message arrangement 1704 may include a CN entity information field 1712 and a message container field 1714 (in the illustrated embodiment, a NAS-SM message container field). The CN entity information field 1712 may include information indicating the type of NAS message, which matches the type indicated by the LCH associated with the NAS message (as further described below). The CN entity information field 1712 may include the NF ID of the target NF of the NAS message and / or the address information of the target NF of the NAS message. In some embodiments, the CN entity information field 1712 may include the target CN entity ID and / or the address of the target NF.

[0151] The message container field 1714 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1714 may include data related to the SM.

[0152] In some embodiments, the second message arrangement 1704 may include an SRB field 1716. The SRB field 1716 may indicate the SRB on which the first message is to be sent. In the illustrated embodiment, the SRB field 1716 indicates that the first message is to be sent on SRB2.

[0153] The first message may be associated with an LCH corresponding to the target NAS-X connection type of the first message. For example, the UE may determine the LCH to be used for the first message based on the target NAS-X connection type of the first message. Information for determining which LCHs correspond to which NAS-X connection types may be provided to the UE by the network (such as via a base station) or may be defined in specifications related to NAS communications. The UE may associate the first message with the determined LCH or indicate the determined LCH to be associated with the first message. In the illustrated embodiment, the first message is shown as being associated with LCH#A corresponding to the NAS-SMF1 connection.

[0154] The base station may identify a first message received from a UE and determine an LCH associated with the first message. The base station may determine a target NAS-X connection type for the first message based on the LCH associated with the first message. A mapping for determining which LCHs correspond to which NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in specifications related to NAS message transmission. The base station may identify an indication of a target NAS-X connection for the NAS-X connection type from the CN entity information field 1706 and may determine a target NAS-X connection and / or a target NF based on the indication. The base station may forward the first message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the first message on a NAS-SMF1 connection and / or forward the first message to SMF1.

[0155] The second message may be associated with an LCH corresponding to the target NAS-X connection type of the second message. For example, the UE may determine the LCH to be used for the second message based on the target NAS-X connection type of the first message. Information for determining which LCHs correspond to which NAS-X connection types may be provided to the UE by the network (such as via a base station) or may be defined in specifications related to NAS communications. The UE may associate the second message with the determined LCH or indicate the determined LCH to be associated with the first message. In the illustrated embodiment, the second message is shown as being associated with LCH#B corresponding to the NAS-SMF2 connection.

[0156] The base station may identify the second message received from the UE and determine the LCH associated with the second message. The base station may determine the target NAS-X connection type for the second message based on the LCH associated with the first message. A mapping for determining which LCHs correspond to which NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in specifications related to NAS message transmission. The base station may identify an indication of a target NAS-X connection for the NAS-X connection type from the CN entity information field 1712 and may determine the target NAS-X connection and / or target NF based on the indication. The base station may forward the second message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the second message on a NAS-SMF2 connection and / or forward the second message to SMF2.

[0157] Option 6 can be a combination of Option 2 and Option 3. Option 6 can use SRB to identify the type of NAS-X connection similar to Option 2. In addition, Option 6 can use LCH to identify the same type of NAS-X connection similar to Option 3.

[0158] Figure 18 An example message arrangement 1800 is illustrated for Option 6 according to some embodiments. For example, the message arrangement 1800 illustrates an example of NAS message content and transmission information according to Option 6. The NAS message may be an RRC message.

[0159] In the illustrated embodiment, message arrangement 1800 includes a first message arrangement 1802 and a second message arrangement 1804. First message arrangement 1802 illustrates an example of message content and transmission information of a first NAS message, and second message arrangement 1804 illustrates an example of message content and transmission information of a second NAS message.

[0160] First message arrangement 1802 may include an SRB field 1806, a CN entity information field 1808, and / or a message container field 1810 (in the illustrated embodiment, a NAS-SM message container field). SRB field 1806 may include an indication of the SRB over which the first message is to be sent. The SRB indicated in SRB field 1806 may correspond to the NAS-X connection type for the first message. In the illustrated embodiment, SRB field 1806 indicates SRB2 as the SRB to be used for the first message. In the illustrated embodiment, SRB2 corresponds to a NAS-SMF type connection.

[0161] The CN entity information field 1808 may include the NF ID of the target NF of the NAS message and / or the address information of the target NF of the NAS message. In some embodiments, the CN entity information field 1808 may include the target CN entity ID and / or the address of the target NF.

[0162] The message container field 1810 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1810 may include data related to the SM.

[0163] Second message arrangement 1804 may include an SRB field 1812, a CN entity information field 1814, and / or a message container field 1816 (in the illustrated embodiment, a NAS-SM message container field). SRB field 1812 may include an indication of the SRB over which the second message is to be sent. The SRB indicated in SRB field 1812 may correspond to the NAS-X connection type for the second message. In the illustrated embodiment, SRB field 1812 indicates SRB2 as the SRB to be used for the second message. In the illustrated embodiment, SRB2 corresponds to a NAS-SMF type connection.

[0164] The CN entity information field 1814 may include the NF ID of the target NF of the NAS message and / or the address information of the target NF of the NAS message. In some embodiments, the CN entity information field 1814 may include the target CN entity ID and / or the address of the target NF.

[0165] The message container field 1816 may include data to be sent via the NAS message. For example, in the illustrated embodiment, the message container field 1816 may include data related to the SM.

[0166] The first message may be associated with an LCH corresponding to the target NAS-X connection and / or target NF of the first message. For example, the UE may determine the LCH to be used for the first message based on the target NAS-X connection and / or target NF of the first message. The mapping for determining which LCHs correspond to which NAS-X connections and / or NFs may be provided to the UE by the network (such as via a base station) or may be defined in a specification related to NAS communications. The UE may associate the first message with the determined LCH or indicate the determined LCH to be associated with the first message. In the illustrated embodiment, the first message is shown as being associated with LCH#A corresponding to the NAS-SMF1 connection.

[0167] The base station may identify a first message received from a UE and determine an SRB on which the first message is received. The base station may determine a target NAS-X connection type for the first message based on the determined SRB. A mapping for determining which SRBs correspond to which NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may determine an LCH associated with the first message. A mapping for determining which LCHs correspond to which NAS-X connections and / or NFs may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may determine a target NAS-X connection and / or a target NF based on the determined LCH. The base station may forward the first message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the first message on a NAS-SMF1 connection and / or forward the first message to SMF1.

[0168] The second message may be associated with an LCH corresponding to the target NAS-X connection and / or target NF of the second message. For example, the UE may determine the LCH to be used for the second message based on the first and second target NAS-X connections and / or target NFs. The mapping for determining which LCHs correspond to which NAS-X connections and / or NFs may be provided to the UE by the network (such as via a base station) or may be defined in a specification related to NAS communications. The UE may associate the second message with the determined LCH or indicate the determined LCH with which the second message is to be associated. In the illustrated embodiment, the second message is shown as being associated with LCH#B corresponding to the NAS-SMF2 connection.

[0169] The base station may identify the second message received from the UE and determine the SRB on which the second message was received. The base station may determine a target NAS-X connection type for the second message based on the determined SRB. A mapping for determining which SRBs correspond to which NAS-X connection types may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may determine an LCH associated with the second message. A mapping for determining which LCHs correspond to which NAS-X connections and / or NFs may be provided to the base station by the network (such as by the network's CN) or may be defined in a specification related to NAS message transmission. The base station may determine a target NAS-X connection and / or a target NF based on the determined LCH. The base station may forward the second message to the determined target NAS-X connection and / or the determined target NF. For example, in the illustrated embodiment, the base station may forward the second message on a NAS-SMF2 connection and / or forward the second message to SMF2.

[0170] NAS-X connection identifier in the RAN node: NF ID in the RRC message

[0171] In some embodiments, the use of NF IDs can be implemented in a NAS-X connection identification method. The NF ID can be carried in an RRC message to help the RAN node identify the NAS-X connection and the target NF. For example, a NAS message (which can be an RRC message) can include an NF ID, which can be used by the base station to identify the target NAS-X connection and / or target NF of the NAS message.

[0172] The UE can obtain an NF ID via any of three methods. For method 1, the NF ID may be assigned by a RAN node. When a new NAS-X connection is requested, the gNB assigns a new NF ID for the NAS-X connection. For example, the UE may send a request to the base station for a new NAS-X connection with the NF to be established. The base station may provide the UE with the NF ID corresponding to the NAS-X connection established based on the request. For example, if the UE initiates a NAS-SMF connection to the network, the UE may notify the gNB that the reason is for the NAS-SMF connection, and the gNB may assign an NF-ID in the response message to identify the NAS-SMF connection.

[0173] For method 2, the NF ID can be provided in the NAS-X context, and the UE can obtain the NF ID from the NAS-AMF connection. When the NW provides another NAS-X context to facilitate later establishment of a NAS-X connection, the NF ID can be included in that NAS-X context. When the UE initiates or sends a NAS message for a NAS-X connection, the NF ID can be included in the message. For method 3, the NF ID can be predefined in the specifications related to NAS communication.

[0174] NAS-X connection establishment

[0175] Associations can exist between different NAS-X connections for a UE. For example, a NAS-AMF connection can be the anchor connection for the UE. Other NAS-X connections of the UE can be associated with a NAS-AMF connection of the UE. If multiple NAS-AMF connections exist, the network can select one AMF as the anchor AMF function.

[0176] There may be a sequence of establishing multiple NAS-X connections for a UE. A NAS-AMF connection may be established first as an anchor connection. The context for establishing a NAS-X connection may be provided via the NAS-AMF connection.

[0177] MM-deregistered UEs can only perform NAS-AMF connections. During the NAS-AMF connection, the AMF may provide the UE with NAS contexts for other NAS-X connections via the NAS-AMF connection. In addition, during the NAS-AMF connection, the AMF may provide NAS contexts based on UE registration information and the operator's deployment (e.g., the connection between the AMF and the SMF). The UE may store the NAS-X context and may use the NAS-X context to establish subsequent NAS-X connections.

[0178] If the UE has a configured NAS-X context and a NAS event is triggered, the UE can perform a NAS-X connection to another NF. For option 1, only RRC-connected / RRC-inactive UEs with a NAS-AMF connection can initiate a NAS-X connection. When the connection is released, the UE can release the NAS-X context. For option 2, an idle UE can initiate a NAS-X connection (assuming the idle UE also maintains the previous NAS-AMF context / connection). When the connection is released, the UE can maintain the NAS-X context. The NAS-X connection can be established and / or released by itself or through a NAS-AMF connection. Options 1 and 2 for connection establishment are further described below.

[0179] Example 1 - Service Request (Option 1)

[0180] For option 1, only connected / inactive UEs with a NAS-AMF connection can initiate a NAS-X connection. When a UE initiates a connection, it may first establish a NAS-AMF connection. The AMF may provide the UE with the configuration / context of the NAS-SM connection, and the SMF identifier may be optionally included in the context. The UE may store the NAS-SM context and may provide NAS messages directly to the SMF via the NAS-SM.

[0181] The RAN node can forward the NAS-SM message to the SMF based on two options. For option 1.1, the RAN node can forward the NAS message based on the NF information in the UE RRC message. For example, in the UE NAS-SM message, the UE can explicitly indicate the SMF-Identifier information, and the RAN can forward the message to the SMF accordingly.

[0182] Figure 19 Illustrated is an example service request arrangement 1900 for option 1.1 according to some embodiments. Service request arrangement 1900 illustrates example messages and operations that may be performed to establish a NAS-X connection according to option 1.1.

[0183] The service request arrangement 1900 may include a UE 1902, a base station 1904, an AMF 1906, and / or an SMF 1908. In other embodiments, the service request arrangement 1900 may include the UE 1902, the base station 1904, and / or one or more NFs of a network to which the UE 1902 is establishing a connection. The UE 1902 may include a UE 2900 ( Figure 29 ) features. The base station 1904 may include a gNB 3000 ( Figure 30 ) features. AMF 1906 can be the AMF of the network, and SMF 1908 can be the SMF of the network.

[0184] UE 1902 may begin by establishing an RRC connection with base station 1904 via RRC connection operation 1910. UE 1902 may establish a connection with base station 1904, as indicated by connection indication 1912.

[0185] UE 1902 may send a NAS-Service Request 1914 to AMF 1906 via base station 1904. NAS-Service Request 1914 may include a request to establish a NAS-X connection with one or more NFs of the network. In the illustrated embodiment, the request may be used to establish a NAS-SMF connection with SMF 1908.

[0186] The AMF 1906 may perform authentication and key agreement (AKA) and / or security control operations 1916 with the UE 1902 to determine whether the UE 1902 is authorized to access the network and / or the requested NF. The AKA and / or security control operations 1916 may be performed in response to receiving the NAS-Service Request 1914.

[0187] The AMF 1906 may send a NAS-Accept message 1918 to the UE 1902. The NAS-Accept message 1918 may be sent in response to the AMF 1906 determining that the UE 1902 is authorized to access the network and / or the requested NF based on the AKA and / or security control operation 1916. The NAS-Accept message 1918 may cause a NAS-AMF connection to be established between the UE 1902 and the AMF 1906.

[0188] NAS-Accept message 1918 may include a NAS-X context for the NAS-X connection requested by UE 1902 in the NAS-Service Request. For example, in the illustrated embodiment, the NAS-X context includes a NAS-SM context based on UE 1902 requesting a NAS-SM connection with SMF 1908. In some embodiments, the NAS-X context may include one or more IDs of the NAS-X connection requested by UE 1902. In the illustrated embodiment, the NAS-X context may include an SMF ID corresponding to SMF 1908. UE 1902 may store the NAS-X context, as indicated by a stored NAS-SM context indication 1920.

[0189] A NAS-SMF connection 1922 may be established between the UE 1902 and the SMF 1908. NAS-SM messages 1924 may be exchanged between the UE 1902 and the base station 1904. For example, the UE 1902 may send the NAS-SM message 1924 to the base station 1904.

[0190] Base station 1904 may receive a NAS-SM message 1924 from UE 1902. Base station 1904 may determine a target NAS-X connection and / or target NF for NAS-SM message 1924 based on an option for determining a target NAS-X connection and / or target NF for a NAS message, as described throughout this disclosure. In the illustrated embodiment, the base station may determine that a NAS-SMF connection and / or SMF 1908 is the target of NAS-SM message 1924. Base station 1904 may forward NAS-SM message 1924 to SMF 1908.

[0191] UE 1902 may release the connection with base station 1904. For example, base station 1904 may send an RRCRelease message 1926 to UE 1902. UE 1902 may transition to an idle state based on the connection being released, as indicated by idle indication 1928. UE 1902 may release the NAS-SM context when it transitions to the idle state.

[0192] For option 1.2, the RAN node may be configured with the NAS-X context (e.g., NFID / address) of the UE's UE NAS-X connection. The gNB may forward this NAS-X context based on the information. For example, the UE may not need to explicitly indicate the SMF-Identifier information in the NAS-SM message.

[0193] Figure 20Illustrated is an example service request arrangement 2000 for option 1.2 according to some embodiments. Service request arrangement 2000 illustrates example messages and operations that may be performed to establish a NAS-X connection according to option 1.2.

[0194] The service request arrangement 2000 may include a UE 2002, a base station 2004, an AMF 2006, and / or an SMF 2008. In other embodiments, the service request arrangement 2000 may include a UE 2002, a base station 2004, and / or one or more NFs of a network to which the UE 2002 is establishing a connection. The UE 2002 may include a UE 2900 ( Figure 29 ) features. The base station 2004 may include a gNB 3000 ( Figure 30 )'s features. AMF 2006 is the AMF of the network, and SMF 2008 may be the SMF of the network.

[0195] UE 2002 may begin by establishing an RRC connection with base station 2004 via RRC connection operation 2010. UE 2002 may establish a connection with base station 2004, as indicated by connection indication 2012.

[0196] UE 2002 may send a NAS-Service Request 2014 to AMF 2006 via base station 2004. In the illustrated embodiment, NAS-Service Request 2014 may be a NAS-SM Request. NAS-Service Request 2014 may include a request to establish a NAS-X connection with one or more NFs of the network. In the illustrated embodiment, the request may be used to establish a NAS-SMF connection with SMF 2008.

[0197] The AMF 2006 may perform authentication and key agreement (AKA) and / or security control operations 2016 with the UE 2002 to determine whether the UE 2002 is authorized to access the network and / or the requested NF. The AKA and / or security control operations 2016 may be performed in response to receiving the NAS-Service Request 2014.

[0198] The AMF 2006 may send a NAS-Accept message 2018 to the UE 2002. The NAS-Accept message 2018 may be sent in response to the AMF 2006 determining that the UE 2002 is authorized to access the network and / or the requested NF based on the AKA and / or the security control operation 2016. The NAS-Accept message 2018 may cause a NAS-AMF connection to be established between the UE 2002 and the AMF 2006.

[0199] NAS-Accept message 2018 may include a NAS-X context for the NAS-X connection requested by UE 2002 in the NAS-Service Request. For example, in the illustrated embodiment, the NAS-X context includes a NAS-SM context based on UE 2002 requesting a NAS-SM connection with SMF 2008. In some embodiments, the NAS-X context may include one or more IDs of the NAS-X connection requested by UE 2002. In the illustrated embodiment, the NAS-X context may include an SMF ID corresponding to SMF 2008. UE 2002 may store the NAS-X context, as indicated by a store NAS-SM context indication 2020.

[0200] AMF 2006 may send a NAS-Configuration message 2022 to base station 2004. In the illustrated embodiment, NAS-X Configuration message 2022 is a NAS-SM Configuration message. NAS-X Configuration message 2022 may configure base station 2004 with a NAS-X context for UE 2002, which may include the NF ID and / or address of the NF corresponding to the established NAS-X connection. In the illustrated embodiment, the NAS-X context may be a NAS-SM context and may include the NF ID and / or address corresponding to SMF 2008. In this option, since base station 2004 is configured with the NAS-X context, UE 2002 may not need to explicitly indicate the NF ID in the NAS-X message sent to base station 2004.

[0201] A NAS-SMF connection 2024 may be established between the UE 2002 and the SMF 2008. NAS-SM messages 2026 may be exchanged between the UE 2002 and the base station 2004. For example, the UE 2002 may send the NAS-SM message 2026 to the base station 2004.

[0202] Base station 2004 may receive a NAS-SM message 2026 from UE 2002. Base station 2004 may determine the target NAS-X connection and / or target NF for NAS-SM message 2026 based on an option for determining the target NAS-X connection and / or target NF for a NAS message, as described throughout this disclosure. For example, base station 2004 may determine the target NAS-X connection and / or target NF using an option that does not require an explicit indication of the NF ID, such as an option that utilizes an SRB bearer, an RLC bearer, and / or an LCH to indicate the target NAS-X connection, target NF, and / or target NAS-X type. In the illustrated embodiment, the base station may determine that a NAS-SMF connection and / or SMF 2008 is the target of NAS-SM message 2026. Base station 2004 may forward NAS-SM message 2026 to SMF 2008.

[0203] UE 2002 may release the connection with base station 2004. For example, base station 2004 may send RRCRelease message 2028 to UE 2002. UE 2002 transitions to idle state based on the connection being released, as indicated by IDS indication 2030. UE 2002 may release the NAS-SM context when it transitions to idle state.

[0204] Example - Service Request (Option 2)

[0205] For option 2, an idle UE may initiate a NAS-X connection. The UE may have already acquired a NAS-X context via a NAS-AMF connection established in a previous connection. The UE may retain the NAS-X context when entering the idle state.

[0206] When an idle UE initiates a service request, if the UE has a valid NAS-X context (e.g., including security information), the UE can directly initiate a NAS-X connection to the network. Otherwise, the UE can initiate a NAS-AMF connection to request a NAS-SM connection. During the NAS-X connection, NF#1 may need to notify the AMF of the UE connection. During the NAS-X connection, if a UE NASMM procedure is initiated (e.g., a periodic registration procedure, a TAU procedure), the UE can send messages via the default / stored NAS-AMF connection.

[0207] Figure 21 An example service request arrangement 2100 for Option 2 is illustrated in accordance with some embodiments. The service request arrangement 2100 illustrates example messages and operations that may be performed to establish a NAS-X connection in accordance with Option 2.

[0208] The service request arrangement 2100 may include a UE 2102, a base station 2104, an AMF 2106, and / or an SMF 2108. In other embodiments, the service request arrangement 2100 includes the UE 2102, the base station 2104, and / or one or more NFs of a network to which the UE 2102 is establishing a connection. The UE 2102 may include a UE 2900 ( Figure 29 ) features. The base station 2104 may include a gNB 3000 ( Figure 30 ) features. AMF 2106 is the AMF of the network, and SMF 2108 can be the SMF of the network.

[0209] UE 2102 may begin by establishing an RRC connection with base station 2104 via RRC connection operation 2110. UE 2102 may establish a connection with base station 2104, as indicated by connection indication 2112.

[0210] UE 2102 may send a NAS-Service Request 2114 to AMF 2106 via base station 2104. In the illustrated embodiment, NAS-Service Request 2114 may be a NAS-AM Request. NAS-Service Request 2114 may include a NAS-MM message. NAS-Service Request 2114 may include a request to establish a NAS-X connection with one or more NFs of the network. In the illustrated embodiment, this request may be used to establish a NAS-SMF connection with SMF 2108.

[0211] The AMF 2106 may perform authentication and key agreement (AKA) and / or security control operations 2116 with the UE 2102 to determine whether the UE 2102 is authorized to access the network and / or the requested NF. The AKA and / or security control operations 2116 may be performed in response to receiving the NAS-Service Request 2114.

[0212] The AMF 2106 may send a NAS-Accept message 2118 to the UE 2102. The NAS-Accept message 2118 may be sent in response to the AMF 2106 determining that the UE 2102 is authorized to access the network and / or the requested NF based on the AKA and / or security control operation 2116. The NAS-Accept message 2118 may cause a NAS-AMF connection to be established between the UE 2102 and the AMF 2106.

[0213] NAS-Accept message 2118 may include a NAS-X context for the NAS-X connection requested by UE 2102 in the NAS-Service Request. For example, in the illustrated embodiment, the NAS-X context includes a NAS-SM context based on UE 2102 requesting a NAS-SM connection with SMF 2108. In some embodiments, the NAS-X context may include one or more IDs of the NAS-X connection requested by UE 2102. In the illustrated embodiment, the NAS-X context may include an SMF ID corresponding to SMF 2108. UE 2102 may store the NAS-X context, as indicated by Store NAS-AM Context Indication 2120.

[0214] AMF 2106 may send a NAS-X context transfer message 2122 to UE 2102. NAS-X context transfer message 2122 may include the NAS-X context for the NAS-X connection requested by UE 2102 in the NAS-Service Request. For example, in the illustrated embodiment, the NAS-X context includes a NAS-SM context based on UE 2102 requesting a NAS-SM connection with SMF 2108. In some embodiments, the NAS-X context may include one or more IDs of the NAS-X connection requested by UE 2102. In the illustrated embodiment, the NAS-X context may include the SMF ID corresponding to SMF 2108. UE 2102 may store the NAS-X context, as indicated by a store NAS-SM context indication 2124.

[0215] UE 2102 may release the connection with base station 2104. For example, base station 2104 may send RRCRelease message 2126 to UE 2102. UE 2102 transitions to an idle state based on the connection being released, as indicated by idle indication 2128. UE 2102 may store the NAS-SM context when it transitions to the idle state.

[0216] A NAS-SMF connection 2130 may be established between the UE 2102 and the SMF 2108. The UE 2002 may establish an RRC connection with the base station 2004 via an RRC connection operation 2132. The UE 2102 may establish a connection with the base station 2104, as indicated by a connection indication 2134.

[0217] NAS-SM messages 2136 may be exchanged between UE 2102 and base station 2104. For example, UE 2102 may send NAS-SM message 2136 to 2104.

[0218] Base station 2104 may receive NAS-SM message 2136 from UE 2102. Base station 2104 may determine the target NAS-X connection and / or target NF for NAS-SM message 2136 based on an option for determining the target NAS-X connection and / or target NF for a NAS message, as described throughout this disclosure. In the illustrated embodiment, the base station may determine that a NAS-SMF connection and / or SMF 2108 is the target of NAS-SM message 2136. Base station 2104 may forward NAS-SM message 2136 to SMF 2108.

[0219] SMF 2108 may exchange UE connection indication 2138 with AMF 2106. Specifically, SMF 2108 may provide UE connection indication 2138 to AMF 2106 to indicate that UE 2102 has established a NAS-SM connection with SMF 2108.

[0220] NF entity selection

[0221] In the 5G design, the AMF selects the target CN entity. It can select between multiple CN entities of the same NAS-X connection type. The CN entity selection can be done in the UE, gNB or AMF based on some information / rules. For example, a UE (such as UE2900( Figure 29 )), base stations (such as gNB 3000 ( Figure 30 )) and / or AMF can select which CN entity to direct the message based on information and / or rules. In an example, the network may include multiple NFs of the same type (such as multiple SMF NFs), where the UE, base station and / or AMF can select to which NF of the multiple NFs each of the messages is to be provided.

[0222] The NW can provide the association and / or mapping between NF and different services and / or slices to the UE or RAN node via the NAS-AMF connection. For example, different SMFs can be used for different services and / or slices.

[0223] For Option 1, the CN and / or AMF may provide CN entity selection rules and / or information to the RAN node. The UE may inform the gNB of the NAS connection type and the services and / or slices to be selected (e.g., Network Slice Selection Assistance Information (NSSAI)). The RAN node may select a specific CN entity for the connection.

[0224] For Option 2, the CN and / or AMF can provide the UE with CN entity selection rules and / or information. The CN can provide the selection rules and / or information via policy (UE Routing Selection Policy (URSP)) or via an AMF Connect message. The UE can select the target CN entity based on the triggering event and service and / or slice and indicate this information to the gNB. The gNB can double-check and forward this information.

[0225] For option 3, the CN and / or AMF may select the target NF#X directly themselves. For the first UE connection to the network via NAS-AMF, the network may explicitly indicate the target CN entity to the UE and gNB for subsequent NAS connections.

[0226] Figure 22 An example NF arrangement 2200 is illustrated according to some embodiments. For example, the NF arrangement 2200 illustrates an example of SMF association according to some embodiments. Although the NF arrangement 2200 is shown with SMFs, it should be understood that other NFs may be included in other embodiments.

[0227] The NF arrangement 2200 may include an AMF 2202, a first SMF 2204, a second SMF 2206, and a third SMF 2208 of the network. The first SMF 2204, the second SMF 2206, and the third SMF 2208 may be associated with the AMF 2202.

[0228] Different SMFs can be used for different services and / or slices. For example, the first SMF 2204 can be used to process a first service and / or slice, the second SMF 2206 can be used to process a second service and / or slice, and the third SMF 2208 can be used for a third service and / or slice. This association can be based on the operator's deployment. For example, the association between SMFs and services and / or slices can depend on the operator's employment.

[0229] For option 1, the CN and / or AMF 2202 may provide the base station with CN entity selection rules and / or information. The CN entity selection rules and / or information may indicate which SMF will be used for which services and / or slices. The UE may notify the base station of the NAS connection, service, and / or slice that may be used to select the SMF for processing NAS messages. The base station may determine the SMF to which the NAS message is to be provided based on the NAS connection, service, and / or slice provided by the UE, and may provide the NAS message to the SMF via the corresponding NAS-SMF connection.

[0230] For option 2, the CN and / or AMF 2202 may provide the UE with CN entity selection rules and / or information. The CN entity selection rules and / or information may indicate which SMF will be used for which services and / or slices. The CN and / or AMF 2202 may provide the UE with CN entity selection rules and / or information via the URSP or via an AMF Connect message. The UE may select the target SMF for the NAS message based on the CN entity selection rules and / or information. A triggering event may cause the UE to perform a selection, and the service and / or slice associated with the NAS message may be used to select the target SMF. The UE may indicate the target SMF for the NAS message to the base station. The base station may double-check the target SMF and forward the NAS message to the target SMF.

[0231] For option 3, the CN and / or AMF 2202 may select a target SMF for NAS messages from the UE. For the first connection where the UE connects to the network via NAS-AMF, the network may explicitly indicate the target SMF to the UE and base station for subsequent NAS connections.

[0232] Mobility

[0233] When the anchor AMF changes, the associated NAS-X connection can be updated. During the AMF change, the network can update the NAS context of other NAS connections.

[0234] Figure 23 An example UE mobility arrangement 2300 according to some embodiments is illustrated. The UE mobility arrangement 2300 illustrates an example of movement of a UE between different cells.

[0235] The UE mobility arrangement 2300 may include one or more UEs. In the illustrated embodiment, the UE mobility arrangement 2300 includes a first cell 2302 and a second cell 2304.

[0236] The first cell 2302 may be hosted by a first base station connected to a first set of NFs. In the illustrated embodiment, the first cell 2302 has a first AMF 2306, a first SMF 2308, and a second SMF 2310. A UE located in the first cell 2302 may establish a NAS-X connection with the first AMF 2306, the first SMF 2308, and / or the second SMF 2310.

[0237] The second cell 2304 may be hosted by a second base station connected to the second set of NFs. In the illustrated embodiment, the second cell 2304 has a second AMF 2312, a third SMF 2314, and a fourth SMF 2316. A UE located in the second cell 2304 may establish a NAS-X connection with the second AMF 2312, the third SMF 2314, and / or the fourth SMF 2316.

[0238] The UE mobility arrangement 2300 may include a UE 2318. The UE may include a UE 2900 ( Figure 29 ) features. The UE 2318 may initially be located within the first cell 2302 and may have established a connection with the first AMF 2306. The UE 2318 may move from the first cell 2302 to the second cell 2304. Due to the movement, a handover (HO) operation may be performed to switch the UE connection from the first AMF 2306 to the second AMF 2312. The HO operation may include Figure 24 or Figure 25 Signaling illustrated in .

[0239] Figure 24 Illustrated is an example UE HO arrangement 2400 according to some embodiments. The UE HO arrangement 2400 illustrates example signals and operations that may include HO of a UE in a connected state.

[0240] The UE HO arrangement 2400 may include a UE 2402 and a base station 2404. The UE 2402 may include a UE 2900 ( Figure 29 ) features. The base station 2404 may include a gNB 3000 ( Figure 30 ) features.

[0241] The UE HO arrangement 2400 may include a first AMF 2406 and a first SMF 2408. The first AMF 2406 and the first SMF 2408 may be connected to a first cell (such as the first cell 2302 ( Figure 23 The first SMF 2408 may be associated with the first AMF 2406, wherein the first AMF 2406 may facilitate establishment of a NAS-SMF connection with the first SMF 2408.

[0242] The UE HO arrangement 2400 may include a second AMF 2410 and a second SMF 2412. The second AMF 2410 and the second SMF 2412 may be connected to a second cell (such as the second cell 2304 ( Figure 23The second SMF 2412 may be associated with the second AMF 2410, wherein the second AMF 2410 may facilitate establishment of a NAS-SMF connection with the second SMF 2412.

[0243] UE 2402 may begin by establishing an RRC connection with base station 2404 via RRC connection operation 2414. UE 2402 may establish a connection with base station 2404, as indicated by connection indication 2416.

[0244] The UE 2402 may establish a NAS-SMF connection with the first AMF 2406 via a NAS-SMF connection operation 2418. The first AMF 2406 may be aware of the NAS-SMF connection, as indicated by 2420.

[0245] The base station 2404 and / or the first AMF 2406 may determine that the UE 2402 is to be handed over to the second AMF 2410. The base station 2404 and / or the first AMF 2406 may determine that the UE 2402 is to be handed over based on the UE 2402 moving from a first cell associated with the first AMF 2406 (such as the first cell 2302) to a second cell associated with the second AMF 2410 (such as the second cell 2304). The base station 2404 and the first AMF 2406 may exchange a HO message 2422 to indicate that an AMF HO is to be performed.

[0246] The first AMF 2406 and the second AMF 2410 may perform an AMF change operation 2424. The AMF change operation 2424 may include indicating to the second AMF 2410 that the NAS-X connection of the UE 2402 may be handed over to the second AMF 2410 and the NF associated with the second AMF 2410. In some embodiments, the AMF change operation 2424 may include information related to the UE 2402 and / or the NAS-X connection of the UE 2402.

[0247] The second AMF 2410 may exchange an information message 2426 with the second SMF 2412. The second AMF 2410 may exchange the information message 2426 based on the second AMF 2410 determining that a NAS-X connection is to be established between the UE 2402 and the second SMF 2412. The information message 2426 may include information related to the second SMF 2412, such as an NF ID corresponding to the second SMF 2412 and / or an address corresponding to the second SMF 2412.

[0248] The base station 2404 and the second AMF 2410 perform a HO request and acknowledgement (ACK) operation 2428. The HO request and ACK operation 2428 may include the base station 2404 providing a HO request to the second AMF 2410 to HO the UE 2402 to the second AMF 2410. The HO request and ACK operation 2428 may also include the second AMF 2410 providing an ACK message to the base station 2404, indicating that the second AMF 2410 will accept the HO of the UE 2402. In some embodiments, the ACK message (or another message sent from the second AMF 2410 to the base station 2404) may include a NAS context related to the second AMF 2410.

[0249] The UE 2402 and the base station 2404 may perform HO operations 2430. The HO operations 2430 may include exchanging information between the UE 2402 and the base station 2404 to hand over the UE 2402 to the second AMF 2410. The HO operations 2430 may include the base station 2404 providing the UE 2402 with a NAS context of the second AMF 2410. The NAS context may help the UE 2402 establish a NAS-X connection with the second AMF 2410 and / or the second SMF 2412.

[0250] The UE 2402 may establish a NAS-SMF connection with the second SMF 2412. The UE may establish the NAS-SMF connection based on the received NAS context. The UE may send a NAS-SM message 2432 to the second SMF 2412 via the NAS-SMF connection. The UE 2402 and / or the base station 2404 may determine, based on the NAS context, that the NAS-SM message 2432 is to be sent and / or sent to the second SMF 2412 via the NAS-SMF connection.

[0251] Figure 25 An example UE HO arrangement 2500 according to some embodiments is illustrated. The UE HO arrangement 2500 illustrates example signals and operations that may include HO of a UE in an idle or inactive state.

[0252] The UE HO arrangement 2500 may include a UE 2502 and a base station 2504. The UE 2502 may include a UE 2900 ( Figure 29 ) features. The base station 2504 may include a gNB 3000 ( Figure 30 ) features.

[0253] The UE HO arrangement 2500 may include a first AMF 2506 and a first SMF 2508. The first AMF 2506 and the first SMF 2508 may be connected to a first cell (such as the first cell 2302 ( Figure 23 The first SMF 2508 may be associated with the first AMF 2506, wherein the first AMF 2506 may facilitate establishment of a NAS-SMF connection with the first SMF 2508.

[0254] The UE HO arrangement 2500 may include a second AMF 2510 and a second SMF 2512. The second AMF 2510 and the second SMF 2512 may be connected to a second cell (such as the second cell 2304 ( Figure 23 The second SMF 2512 may be associated with the second AMF 2510, wherein the second AMF 2510 may facilitate establishment of a NAS-SMF connection with the second SMF 2512.

[0255] UE 2502 may begin by establishing an RRC connection with base station 2504 via RRC connection operation 2514. UE 2502 may establish a connection with base station 2504. UE 2502 may transition to and / or remain in an idle or inactive state upon completion of RRC connection operation 2514, as indicated by idle / inactive indication 2516.

[0256] A tracking area update (TAU) may be initiated for the UE 2502, as indicated by the TAU indication 2518. The TAU may be initiated due to the UE 2502 moving from a first cell associated with the first AMF 2506 to a second cell associated with the second AMF 2510.

[0257] The UE 2502 may establish a NAS-SMF connection with the second AMF 2510 via a NAS-SMF connection operation 2520.

[0258] The second AMF 2510 and the first AMF 2506 may perform a UE context transfer 2522. The first AMF 2506 may provide a UE context related to the UE 2502 as part of the UE context transfer 2522. The first AMF 2506 may provide an indication of the NF related to the first AMF 2506 with which the UE 2502 establishes a NAS-X connection.

[0259] The second AMF 2510 may exchange an information message 2524 with the second SMF 2512. The second AMF 2510 may exchange the information message 2524 based on the second AMF 2510 determining that a NAS-X connection is to be established between the UE 2502 and the second SMF 2512. The information message 2524 may include information related to the second SMF 2512, such as an NF ID corresponding to the second SMF 2512 and / or an address corresponding to the second SMF 2512.

[0260] The second AMF 2510 may provide an updated NAS context message 2526 to the UE 2502. The updated NAS context message 2526 may include updated NAS contexts for other NAS connections, wherein the updated NAS-X context may be for the NF associated with the second AMF 2510. As indicated by the updated NAS context indication 2528, the NAS context of the UE 2502 may be updated.

[0261] Figure 26 An example process 2600 for generating a NAS-X message according to some embodiments is illustrated. The NAS-X connection may indicate a NAS-X connection to be used to send information to the NF. The process 2600 may be performed by a UE, such as UE 2900 ( Figure 29 ))implement.

[0262] The process 2600 may include identification information at 2602. For example, the UE may identify information, where the information may be used for a NAS message to be sent to the NF.

[0263] Process 2600 may include identifying a NF of a network at 2604. For example, the UE may identify a NF of a network to which information is to be provided.

[0264] In some embodiments, process 2600 may include identifying entity selection information received from the network. The NF may be identified based at least in part on the entity selection information. In some of these embodiments, the entity selection information may be received via a URSP or AMF Connect message.

[0265] In some embodiments, identifying the NF may include identifying an indication from the network indicating that a NAS message is to be provided to the NF. The NF may be identified based at least in part on the indication.

[0266] Process 2600 may include generating a NAS message at 2606. For example, the UE may generate a NAS message to indicate a NAS-X connection to be used to send information to the NF.

[0267] In some embodiments, the NAS message may include an RRC message. The RRC message may include an indication of a NAS-X connection. In some of these embodiments, the NAS-X connection may include an NF ID corresponding to the NF. In some of these embodiments, process 2600 may include identifying the NF ID received from the base station or in the NAS-X context.

[0268] In some embodiments, generating the NAS message may include indicating to the NF an SRB for transmission. The SRB may correspond to a NAS-X connection.

[0269] In some embodiments, generating the NAS message may include indicating an RLC bearer or LCH for transmission to the NF. The RLC bearer or LCH may correspond to a NAS-X connection.

[0270] In some embodiments, generating the NAS message may include indicating to the NF an SRB for transmission. The SRB may correspond to a NAS-X type. The NAS message may include an RRC message. The RRC message may include an indication of a NAS-X connection type.

[0271] In some embodiments, generating the NAS message may include indicating to the NF an LCH for transmission. The LCH may correspond to a NAS-X connection type. The NAS message may include an RRC message. The RRC message may include an indication of a NAS-X connection of the NAS-X connection type.

[0272] In some embodiments, generating the NAS message may include indicating to the NF an SRB for transmission. The SRB may correspond to a NAS-X connection type. Generating the NAS message may also include indicating to the NF an LCH for transmission. The LCH may correspond to a NAS-X connection of the NAS-X connection type.

[0273] In some embodiments, generating the NAS message may include indicating to the NF an RRC connection instance for transmission. The RRC connection instance corresponds to a NAS-X connection.

[0274] In some embodiments, generating the NAS message may include indicating the NAS connection type corresponding to the NAS-X and the service or slice corresponding to the NAS-X connection.

[0275] Although Figure 26The order of operations of process 2600 may be arguably implied, but it should be understood that in an embodiment, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 2600.

[0276] Figure 27 An example process 2700 for establishing a NAS-X connection according to some embodiments is illustrated. The process 2700 may be performed by a UE, such as UE 2900 ( Figure 29 ))implement.

[0277] The process 2700 may include establishing a NAS-AMF connection with the AMF in 2702. For example, the UE may establish a NAS-AMF connection with the AMF of the network.

[0278] Process 2700 may include identifying a NAS context. For example, the UE may identify a NAS context received from the AMF via a NAS-AMF connection. In some embodiments, the NAS context may include the configuration of a NAS-X connection. In some embodiments, the NAS context may include an NF ID corresponding to the NF.

[0279] Process 2700 may include establishing a NAS-X connection with the NF. For example, the UE may establish a NAS-X connection with the NF of the network using a NAS context. In some embodiments, the NAS-X connection may be established when the device is in an RRC-Connected state or an RRC-Inactive state. In some embodiments, the NAS-X connection may be established when the device is in an idle state.

[0280] In some embodiments, the NAS-AMF connection may be a first NAS-AMF connection. Process 2700 may also include establishing a second NAS-AMF connection after establishing the first NAS-AMF connection. The NAS-X connection may be established via the second NAS-AMF connection.

[0281] Although Figure 27 The order of operations of process 2700 may be arguably implied, but it should be understood that in an embodiment, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 2600.

[0282] Figure 28An example process 2800 for providing NAS messages to a NF according to some embodiments is illustrated. The NAS message may be provided to the NF via a NAS-X connection. The process 2800 may be performed by a base station, such as a gNB 3000 ( Figure 30 )implement.

[0283] Process 2800 may include identifying a NAS message at 2802. For example, a base station may identify a NAS message received from a UE.

[0284] Process 2800 may include determining a NAS-X connection for providing a NAS message to a NF. For example, a base station may determine a NAS-X connection for providing a NAS message to a NF of a network based at least in part on receipt of a NAS message.

[0285] In some embodiments, the NAS-X connection may be determined based at least in part on an indication of the NAS-X connection included in the NAS message. In some embodiments, the NAS-X connection may include an NF ID corresponding to the NF. In some embodiments, the NAS-X connection may be determined based at least in part on an SRB associated with receipt of the NAS message.

[0286] In some embodiments, a NAS-X connection may be determined based at least in part on an RLC bearer or LCH associated with the receipt of a NAS message. In some embodiments, a NAS-X connection may be determined based at least in part on an SRB associated with the receipt of a NAS message indicating a NAS-X connection type and an indication of a NAS-X connection of the NAS-X connection type from the NAS message.

[0287] In some embodiments, the NAS-X connection may be determined based at least in part on an LCH associated with the receipt of a NAS message indicating a NAS-X connection type and an indication of a NAS-X connection of the NAS-X connection type from the NAS message. The NAS-X connection may be determined based at least in part on an SRB associated with the receipt of a NAS message indicating a NAS-X connection type and an LCH associated with the receipt of a NAS message indicating a NAS-X connection type.

[0288] In some embodiments, the NAS-X connection may be determined based at least in part on an RRC connection instance associated with receipt of a NAS message. In some embodiments, the NAS-X connection may be determined based at least in part on a NAS connection type and service or slice indicated by the UE for the NAS message. In some embodiments, the NAS-X connection may be determined based at least in part on an indication received from the network.

[0289] Process 2800 may include providing a NAS message to the NF at 2806. For example, the base station may provide the NAS message to the NF via a NAS-X connection.

[0290] Although Figure 28 The order of operations of process 2800 may be arguably implied, but it should be understood that in an embodiment, one or more of these operations may be performed in a different order and / or one or more of these operations may be performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted and / or one or more additional operations may be added to process 2800.

[0291] Figure 29 An example UE 2900 according to some embodiments is illustrated. UE 2900 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video monitoring / surveillance device (e.g., a camera, a camcorder, etc.), a wearable device (e.g., a smartwatch), or a loose IoT device. In some embodiments, UE 2900 can be a RedCap UE or an NR-Light UE.

[0292] UE 2900 may include a processor 2904, RF interface circuitry 2908, memory / storage 2912, a user interface 2916, sensors 2920, driver circuitry 2922, a power management integrated circuit (PMIC) 2924, antenna structures 2926, and a battery 2928. The components of UE 2900 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 29 The block diagram is intended to show a high-level view of some of the components of the UE 2900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0293] Components of the UE 2900 may be coupled to various other components via one or more interconnects 2932, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0294] The processor 2904 may include processor circuits such as a baseband processor circuit (BB) 2904A, a central processor unit circuit (CPU) 2904B, and a graphics processor unit circuit (GPU) 2904C. The processor 2904 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from the memory / storage device 2912) to cause the UE 2900 to perform operations as described herein.

[0295] In some embodiments, the baseband processor circuit 2904A can access the communication protocol stack 2936 in the memory / storage device 2912 to communicate over a 3GPP-compatible network. Generally speaking, the baseband processor circuit 2904A can access the communication protocol stack to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, PHY layer operations may be additionally / alternatively performed by components of the RF interface circuit 2908.

[0296] The baseband processor circuit 2904A may generate or process baseband signals or waveforms that carry information in 3GPP-compliant networks. In some embodiments, waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0297] The memory / storage 2912 may include one or more non-transitory computer-readable media containing instructions (e.g., the communication protocol stack 2936) that may be executed by one or more processors in the processor 2904 to cause the UE 2900 to perform various operations described herein. The memory / storage 2912 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 2900. In some embodiments, some of the memory / storage 2912 may be located on the processor 2904 itself (e.g., L1 cache and L2 cache), while other memory / storage 2912 may be external to the processor 2904 but accessible via a memory interface. The memory / storage 2912 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0298] The RF interface circuit 2908 may include transceiver circuits and a radio frequency front-end module (RFEM), which allows the UE 2900 to communicate with other devices via a radio access network. The RF interface circuit 2908 may include various components arranged in a transmit path or a receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0299] In the receive path, the RFEM receives the radiated signal from the air interface via the antenna structure 2926 and further filters and amplifies the signal (using a low-noise amplifier). This signal can be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 2904.

[0300] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the signal through a power amplifier before the RF signal is radiated across the air interface via the antenna structure 2926.

[0301] In various embodiments, the RF interface circuit 2908 may be configured to send / receive signals in a manner compatible with NR access technology.

[0302] The antenna structure 2926 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. The antenna structure 2926 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input / multiple-output communications. The antenna structure 2926 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna structure 2926 may have one or more panels designed for a specific frequency band, including a band in FR1 or FR2.

[0303] The user interface 2916 includes various input / output (I / O) devices designed to enable a user to interact with the UE 2900. The user interface 2916 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual component for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuitry includes any physical or virtual component for displaying information or otherwise communicating information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs) or more complex outputs (such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.)), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 2900.

[0304] Sensors 2920 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and to communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a fluid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0305] The driver circuit 2922 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 2900. The driver circuit 2922 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 2900. For example, the driver circuit 2922 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings from the sensor circuit 2920 and controlling and allowing access to the sensor circuit 2920, a driver for obtaining actuator positions of electromechanical components or controlling and allowing access to electromechanical components, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0306] The PMIC 2924 may manage power provided to various components of the UE 2900. Specifically, with respect to the processor 2904, the PMIC 2924 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0307] In some embodiments, the PMIC 2924 can control or otherwise be part of various power-saving mechanisms for the UE 2900. For example, if a platform UE is in the RRC_CONNECTED state, in which the platform remains connected to a RAN node because it expects to receive traffic soon, after a period of inactivity, the platform can enter a state known as discontinuous reception mode (DRX). During this state, the UE 2900 can power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 2900 can transition to the RRC_IDLE state, in which the UE is disconnected from the network and does not perform operations such as channel quality feedback or handovers. The UE 2900 enters a very low-power state and performs paging, in which the UE periodically wakes up again to listen to the network, and then powers down again. The UE 2900 may not receive data in this state; to do so, the platform must transition back to the RRC_CONNECTED state. Additional power-saving modes can prevent the device from using the network for periods exceeding the paging interval, ranging from a few seconds to several hours. During this time, the device is completely unable to connect to the network and can be completely powered off. Any data transmitted during this time will incur significant delays, assuming that the delay is acceptable.

[0308] The battery 2928 can power the UE 2900, but in some examples, the UE 2900 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 2928 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 2928 can be a typical lead-acid car battery.

[0309] Figure 30 An example gNB 3000 according to some embodiments is illustrated. The gNB 3000 may include a processor 3004, RF interface circuitry 3008, core network (CN) interface circuitry 3012, memory / storage circuitry 3016, and antenna structures 3026.

[0310] The components of the gNB 3000 may be coupled to various other components via one or more interconnects 3028.

[0311] The processor 3004, RF interface circuit 3008, memory / storage circuit 3016 (including communication protocol stack 3010), antenna structure 3026 and interconnect 3028 may be similar to those of reference Figure 29 Like-named elements are shown and described.

[0312] The CN interface circuitry 3012 can provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5GC-compatible network interface protocol, such as a Carrier Ethernet protocol, or some other suitable protocol). Network connectivity can be provided to / from the gNB 3000 via optical fiber or wireless backhaul. The CN interface circuitry 3012 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 3012 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0313] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0314] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following Examples section. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0315] Example

[0316] In the following sections, additional exemplary embodiments are provided.

[0317] Embodiment 1 may include a method of operating a device, the method comprising identifying information, identifying a network function (NF) of a network to which the information is to be provided, and generating a non-access stratum (NAS) message to indicate a NAS-X connection to be used to send the information to the NF.

[0318] Embodiment 2 may include the method of embodiment 1, wherein the NAS message comprises a radio resource control (RRC) message, and wherein the RRC message includes an indication of the NAS-X connection.

[0319] Embodiment 3 may include the method of embodiment 2, wherein the indication of the NAS-X connection includes an NF identifier (ID) corresponding to the NF.

[0320] Embodiment 4 may include the method according to embodiment 3, further comprising identifying the NF ID received from the base station or in the NAS-X context.

[0321] Embodiment 5 may include the method of embodiment 1, wherein generating the NAS message includes indicating a signaling radio bearer (SRB) for transmission to the NF, the SRB corresponding to the NAS-X connection.

[0322] Embodiment 6 may include the method of embodiment 1, wherein generating the NAS message includes indicating a radio link control (RLC) bearer or logical channel (LCH) for transmission to the NF, the RLC bearer or LCH corresponding to the NAS-X connection.

[0323] Embodiment 7 may include the method of embodiment 1, wherein generating the NAS message includes indicating a signaling radio bearer (SRB) for sending to the NF, the SRB corresponding to a NAS-X connection type, wherein the NAS message includes a radio resource control (RRC) message, wherein the RRC message includes an indication of the NAS-X connection of the NAS-X connection type.

[0324] Embodiment 8 may include the method of embodiment 1, wherein generating the NAS message includes indicating a logical channel (LCH) for sending to the NF, the LCH corresponding to a NAS-X connection type, wherein the NAS message includes a radio resource control (RRC) message, wherein the RRC message includes an indication of the NAS-X connection of the NAS-X connection type.

[0325] Embodiment 9 may include the method according to embodiment 1, wherein generating the NAS message includes indicating a signaling radio bearer (SRB) for sending to the NF, the SRB corresponding to a NAS-X connection type; and indicating a logical channel (LCH) for sending to the NF, the LCH corresponding to the NAS-X connection of the NAS-X connection type.

[0326] Embodiment 10 may include the method of embodiment 1, wherein generating the NAS message includes indicating a radio resource control (RRC) connection instance for sending to the NF, the RRC connection instance corresponding to the NAS-X connection.

[0327] Embodiment 11 may include the method according to embodiment 1, wherein generating the NAS message includes indicating the NAS connection type corresponding to the NAS-X connection and the service or slice corresponding to the NAS-X connection.

[0328] Embodiment 12 may include the method of embodiment 1, wherein the method further comprises identifying entity selection information received from the network, wherein the NF is identified based at least in part on the entity selection information.

[0329] Embodiment 13 may include the method of embodiment 12, wherein the entity selection information is received via a user equipment routing policy (URSP) or an access and mobility management function (AMF) connect message.

[0330] Embodiment 14 may include the method of embodiment 1, wherein identifying the NF comprises identifying an indication from the network indicating that the NAS message is to be provided to the NF, wherein the NF is identified based at least in part on the indication.

[0331] Embodiment 15 may include the method of any one of embodiments 1-14, further comprising one or more of the features of any one of embodiments 16-21.

[0332] Embodiment 16 may include a method of operating a device, the method comprising establishing a NAS-AMF connection with an access and mobility management function (AMF) of a network, identifying a NAS context received from the AMF via the NAS-AMF connection, and establishing a NAS-X connection with a network function (NF) of the network using the NAS context.

[0333] Embodiment 17 may include the method of embodiment 16, wherein the NAS context includes a configuration of the NAS-X connection.

[0334] Embodiment 18 may include the method of embodiment 16, wherein the NAS context includes a NF identifier (ID) corresponding to the NF.

[0335] Embodiment 19 may include the method of embodiment 16, wherein the NAS-X connection is established when the device is in a radio resource control (RRC)-connected state or an RRC-inactive state.

[0336] Embodiment 20 may include the method of embodiment 16, wherein the NAS-X connection is established when the device is in an idle state.

[0337] Embodiment 21 may include a method according to embodiment 16, wherein the NAS-AMF connection is a first NAS-AMF connection, wherein the method further comprises establishing a second NAS-AMF connection after establishing the first NAS-AMF connection, and wherein the NAS-X connection is established via the second NAS-AMF connection.

[0338] Embodiment 22 may include the method of any one of embodiments 16 to 21, further comprising one or more of the features of any one of embodiments 1 to 14.

[0339] Embodiment 23 may include a method of operating a base station, the method comprising identifying a non-access stratum (NAS) message received from a user equipment (UE), determining a NAS-X connection for providing the NAS message to a network function (NF) of a network based at least in part on receipt of the NAS message, and providing the NAS message to the NF via the NAS-X connection.

[0340] Embodiment 24 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on an indication of the NAS-X connection included in the NAS message.

[0341] Embodiment 25 may include the method of embodiment 24, wherein the indication of the NAS-X connection includes a NF identifier (ID) corresponding to the NF.

[0342] Embodiment 26 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a signaling radio bearer (SRB) associated with the receipt of the NAS message.

[0343] Embodiment 27 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a radio link control (RLC) bearer or logical channel (LCH) associated with the reception of the NAS message.

[0344] Embodiment 28 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a signaling radio bearer (SRB) associated with the reception of the NAS message indicating a NAS-X connection type and an indication of the NAS-X connection of the NAS-X connection type from the NAS message.

[0345] Embodiment 29 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a logical channel (LCH) associated with the reception of the NAS message indicating a NAS-X connection type and an indication of a NAS-X connection of the NAS-X connection of the NAS-X connection type from the NAS message.

[0346] Embodiment 30 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a signaling radio bearer (SRB) associated with the reception of the NAS message indicating a NAS-X connection type and a logical channel (LCH) of the NAS-X connection associated with the reception of the NAS message indicating the NAS-X connection type.

[0347] Embodiment 31 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a radio resource control (RRC) connection instance associated with the reception of the NAS message.

[0348] Embodiment 32 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on a NAS connection type and a service or segment indicated by the UE for the NAS message.

[0349] Embodiment 33 may include the method of embodiment 23, wherein the NAS-X connection is determined based at least in part on an indication received from the network.

[0350] Example 34 may include an apparatus comprising means for performing one or more elements of the method described in or related to any one of Examples 1 to 33, or any other method or process described herein.

[0351] Embodiment 35 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 33 or any other method or process described herein.

[0352] Embodiment 36 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 33, or any other method or process described herein.

[0353] Example 37 may include methods, techniques, or processes as described or related to any one of Examples 1 to 33, or portions or components thereof.

[0354] Embodiment 38 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any one of Embodiments 1 to 33, or a portion thereof.

[0355] Embodiment 39 may include signals as described or related to any one of Embodiments 1 to 33, or portions or components thereof.

[0356] Embodiment 40 may include a datagram, information element, packet, frame, fragment, PDU, or message, or a portion or component thereof, as described in or related to any one of embodiments 1 to 33 or otherwise described in this disclosure.

[0357] Embodiment 41 may include a signal encoded with data as described in or related to any of Embodiments 1 to 33 or otherwise described in this disclosure, or a portion or component thereof.

[0358] Embodiment 42 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message, or a portion or component thereof, as described in accordance with or in connection with any of Embodiments 1 to 33 or otherwise described in this disclosure.

[0359] Embodiment 43 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the method, technique, or process described in or related to any one of Embodiments 1 to 33, or a portion thereof.

[0360] Embodiment 44 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Embodiments 1 to 33, or a portion thereof.

[0361] Embodiment 45 may include signals in a wireless network as shown and described herein.

[0362] Embodiment 46 may include a method of communicating in a wireless network as shown and described herein.

[0363] Embodiment 47 may include a system for providing wireless communications as shown and described herein.

[0364] Embodiment 48 may include an apparatus for providing wireless communications as shown and described herein.

[0365] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0366] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: Identification information; identifying a network function (NF) of the network to which the information is to be provided; and A non-access stratum (NAS) message is generated to indicate a NAS-X connection to be used to send the information to the NF.

2. The one or more computer-readable media of claim 1, wherein the NAS message comprises a radio resource control (RRC) message, and wherein the RRC message comprises an indication of the NAS-X connection.

3. The one or more computer-readable media of claim 2, wherein the indication of the NAS-X connection comprises a NF identifier (ID) corresponding to the NF.

4. The one or more computer-readable media of any one of claims 1 to 3, wherein generating the NAS message comprises indicating a signaling radio bearer (SRB) for sending to the NF, the SRB corresponding to the NAS-X connection.

5. One or more computer-readable media according to any one of claims 1 to 3, wherein generating the NAS message includes indicating a radio link control (RLC) bearer or logical channel (LCH) for sending to the NF, the RLC bearer or LCH corresponding to the NAS-X connection.

6. One or more computer-readable media according to any one of claims 1 to 3, wherein generating the NAS message includes indicating a signaling radio bearer (SRB) for sending to the NF, the SRB corresponding to a NAS-X connection type, wherein the NAS message includes a radio resource control (RRC) message, wherein the RRC message includes an indication of the NAS-X connection of the NAS-X connection type.

7. One or more computer-readable media according to any one of claims 1 to 3, wherein generating the NAS message includes indicating a logical channel (LCH) for sending to the NF, the LCH corresponding to a NAS-X connection type, wherein the NAS message includes a radio resource control (RRC) message, wherein the RRC message includes an indication of the NAS-X connection of the NAS-X connection type.

8. One or more computer-readable media according to any one of claims 1 to 3, wherein generating the NAS message includes indicating a signaling radio bearer (SRB) for sending to the NF, the SRB corresponding to a NAS-X connection type; and indicating a logical channel (LCH) for sending to the NF, the LCH corresponding to the NAS-X connection of the NAS-X connection type.

9. One or more computer-readable media according to any one of claims 1 to 3, wherein generating the NAS message includes indicating a radio resource control (RRC) connection instance for sending to the NF, the RRC connection instance corresponding to the NAS-X connection.

10. A device for: Establish a NAS-AMF connection with the network’s access and mobility management function (AMF); identifying a NAS context received from the AMF via the NAS-AMF connection; and A NAS-X connection is established with a network function (NF) of the network using the NAS context.

11. The apparatus of claim 10, wherein the NAS context comprises a configuration of the NAS-X connection.

12. The apparatus of claim 10, wherein the NAS context includes a NF identifier (ID) corresponding to the NF.

13. The apparatus according to any one of claims 10 to 12, wherein the NAS-X connection is established when the apparatus is in a Radio Resource Control (RRC)-Connected state or an RRC-Inactive state.

14. The apparatus according to any one of claims 10 to 12, wherein the NAS-X connection is established when the apparatus is in an idle state.

15. The apparatus according to any one of claims 10 to 12, wherein the NAS-AMF connection is a first NAS-AMF connection, wherein the apparatus is further configured to establish a second NAS-AMF connection after establishing the first NAS-AMF connection, and wherein the NAS-X connection is established via the second NAS-AMF connection.

16. A method comprising: identifying a non-access stratum (NAS) message received from a user equipment (UE); determining, based at least in part on the receipt of the NAS message, a NAS-X connection for providing the NAS message to a network function (NF) of a network; as well as The NAS message is provided to the NF via the NAS-X connection.

17. The method of claim 16, wherein the NAS-X connection is determined based at least in part on an indication of the NAS-X connection included in the NAS message.

18. The method of claim 16 or claim 17, wherein the NAS-X connection is determined based at least in part on a signaling radio bearer (SRB) associated with the reception of the NAS message.

19. The method of claim 16 or claim 17, wherein the NAS-X connection is determined based at least in part on a Radio Link Control (RLC) bearer or logical channel (LCH) associated with the reception of the NAS message.

20. The method of claim 16 or claim 17, wherein the NAS-X connection is determined based at least in part on a signaling radio bearer (SRB) associated with the reception of the NAS message indicating a NAS-X connection type and the indication of the NAS-X connection of the NAS-X connection type from the NAS message.

Images