Method for centralized internet protocol address allocation for user equipment control plane

Abstract

The embodiment of the invention provides a centralized internet protocol address allocation method and device for a user equipment control plane and a computer readable medium. A method includes receiving, by a user equipment (UE), a first message from an apparatus, the first message including a first identifier of the UE, and a second identifier identifying an address of a first component in a network. The UE sends a second message to the apparatus, the second message including a request for an address of a second component of the network. The UE receives a third message from the network device, the third message including a third identifier of the address of the second component of the network, and the UE sends a fourth message to the second component of the network, the fourth message including an identifier of the address of the second component of the network.

Description

Technical Field

[0001] Various example embodiments relate generally to wireless networks, and more particularly, to centralized Internet Protocol (IP) address allocation for a user equipment (UE) control plane. Background Art

[0002] In the fifth generation (5G) wireless system, the signaling protocol between the user equipment (UE) and the core network (e.g., NAS non-access layer protocol) is carried by the radio interface, and the radio resource control (RRC) signaling on the N2 interface between the base station and the access and mobility management function (AMF) (e.g., the next generation application protocol (NGAP) on the stream control transmission protocol (SCTP)). For NAS for other network functions (e.g., session management function (SMF) for session management, policy control function (PCF) for policy management), the messages are transparently relayed by the AMF through the service-based core interface. Summary of the invention

[0003] In one aspect of the present disclosure, a method includes: receiving, by a user equipment (UE), a first message from a device, the first message including: a first identifier of the UE, and a second identifier identifying an address of a first component in a network. The UE sends a second message to the device, the second message including: a request for an address of a second component of the network. The UE receives a third message from the network device, the third message including: a third identifier of the address of the second component of the network, and the UE sends a fourth message to the second component of the network, the fourth message including: an identifier of the address of the second component of the network.

[0004] In one aspect of the method, the first identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0005] In one aspect of the method, a first component in the network is a Network Repository Function (NRF).

[0006] In one aspect of the method, the second identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0007] In one aspect of the method, the second message includes a request for a network function service IP address for NAS messaging.

[0008] In one aspect of the method, the third message includes: an IP address of the network function service for NAS message delivery.

[0009] In one aspect of the method, the fourth message is sent to a network function identified by an IP address for NAS messaging served by the network function.

[0010] In one aspect of the method, the fourth message is an Internet Protocol version 4 (IPv4) protocol message.

[0011] In one aspect of the method, the fourth message is an Internet Protocol version 6 (IPv6) protocol message.

[0012] In one aspect of the method, the first message is a Radio Resource Control (RRC) setup message.

[0013] In one aspect of the present disclosure, a method includes: receiving, by a first device, a first message from a user equipment (UE), the first message initiating communication with the first device. The first device sends a second message to a second device, the second message including: a first identifier of the UE. The first device receives a third message from the second device, the third message including: a second identifier of the UE, and a third identifier identifying an address of a first component in a network, and the first device sends a fourth message to the UE, the fourth message including: the second identifier of the UE, and the third identifier identifying the address of the first component in the network.

[0014] In one aspect of the method, the second identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0015] In one aspect of the method, a first component in the network is a Network Repository Function (NRF).

[0016] In one aspect of the method, the third identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0017] In one aspect of the method, the first identifier of the UE is a client identifier of the UE.

[0018] In one aspect of the method, the third message is an Internet Protocol version 4 (IPv4) protocol message.

[0019] In one aspect of the method, the fourth message is an IPv4 protocol message.

[0020] In one aspect of the method, the third message is an Internet Protocol version 6 (IPv6) protocol message.

[0021] In one aspect of the method, the fourth message is an IPv6 protocol message.

[0022] In one aspect of the method, the first message is a Radio Resource Control (RRC) setup message.

[0023] In one aspect of the present disclosure, a method includes: receiving, by a first device, a first message from a second device, the first message including: a first identifier of a user equipment (UE). The first device assigns a second identifier to the UE, and sends a second message to the second device, the second message including: the second identifier of the UE, and a third identifier identifying an address of a first component in a network.

[0024] In one aspect of the method, the second identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0025] In one aspect of the method, a first component in the network is a Network Repository Function (NRF).

[0026] In one aspect of the method, the third identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0027] In one aspect of the method, the first identifier of the UE is a client identifier of the UE.

[0028] In one aspect of the method, the first message is an Internet Protocol version 4 (IPv4) protocol message.

[0029] In one aspect of the method, the second message is an IPv4 protocol message.

[0030] In one aspect of the method, the first message is an Internet Protocol version 6 (IPv6) protocol message.

[0031] In one aspect of the method, the second message is an IPv6 protocol message.

[0032] In one aspect of the present disclosure, a user equipment includes: at least one processor and at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the user equipment performs at least any one of the above methods.

[0033] In one aspect of the present disclosure, an apparatus includes: at least one processor and at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the user equipment performs at least any one of the aforementioned methods.

[0034] In one aspect of the present disclosure, a processor-readable medium stores instructions, which, when executed by at least one processor of a device, cause the device to perform at least any one of the above methods.

[0035] According to some aspects, the subject matter of the independent claims is provided. Some other aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Some example embodiments will now be described with reference to the accompanying drawings.

[0037] Figure 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE) according to one illustrative aspect of the present disclosure;

[0038] Figure 2 is a diagram of example components of a network system according to one illustrative aspect of the present disclosure;

[0039] Figure 3 is a diagram of an example embodiment of signals and operations between a UE, a gNodeB, a router, and a DHCP server according to one illustrative aspect of the present disclosure;

[0040] Figure 4 is a representation of an example RRC setup message according to one illustrative aspect of the present disclosure; and

[0041] Figure 5 is a diagram of an example embodiment of components of a UE or network device according to one illustrative aspect of the present disclosure. DETAILED DESCRIPTION

[0042] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, one skilled in the relevant art will recognize that the various aspects may be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other cases, well-known structures associated with transmitters, receivers, or transceivers are not shown or described in detail to avoid unnecessarily obscuring the description of the various aspects.

[0043] In this specification, reference to "one aspect" or "aspects" indicates that a particular feature, structure, or characteristic described in conjunction with that aspect is included in at least one aspect. Thus, the appearance of the phrase "in one aspect" or "in aspects" in various places in this specification does not necessarily refer to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0044] The embodiments described in the present disclosure may be implemented in wireless network devices, such as, but not limited to, devices utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System (UMTS, 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5GNR), Advanced 5G, 6G (and higher), and 802.11ax (Wi-Fi 6) wireless network systems. The term 'eLTE' here means LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA), or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0045] The present disclosure may use the term "serving network device" to refer to a network node or network device (or a portion thereof) that serves a UE. As used herein, the terms "send to," "receive from," and "cooperate with" (and variations thereof) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes acquiring for the first time, or reacquiring after the first acquisition. The term "connect" may refer to a physical connection or a logical connection.

[0046] The present disclosure uses 5G NR as an example of a wireless network, and may use a smartphone and / or an extended reality headset as an example of a UE. It should be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0047] Figure 1 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). The network node 120 will be described in more detail below. As used herein, the term "network device" may refer to any component of the network system 100, such as a server 110, a network node 120, a network device 130, any (multiple) components of the above, and / or any (multiple) other components of the network system 100. Examples of network devices include, but are not limited to, devices that implement various aspects of 5G NR, etc. The present disclosure describes embodiments related to 5G NR, as well as embodiments involving various aspects defined by the Third Generation Partnership Project (3GPP). However, it is conceivable that embodiments related to other wireless network technologies are also covered within the scope of the present disclosure.

[0048] In various embodiments, server 110 may include an Internet Engineering Task Force (IETF) Dynamic Host Configuration Protocol (DHCP) server. Those skilled in the art will appreciate the protocol mechanisms and techniques defined by the IETF for communicating between a DHCP server and other network components. For example, in various embodiments, a router (e.g., a site router) not shown may include a DHCP server. In various embodiments, the DHCP server may be located outside the site router. Those skilled in the art will appreciate the mechanisms for communication between site routers, DHCP servers, and additional components in network 100.

[0049] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also referred to as a gNB) may include, for example, a node that provides NR user plane and control plane protocol terminations towards the UE and is connected to the 5G Core (5GC) via an NG interface, for example in accordance with 3GPP TS 38.300 V16.6.0 (2021-06) Section 3.2, which is incorporated herein by reference.

[0050] The gNB supports various protocol layers, such as Layer 1 (L1) (ie, physical layer), Layer 2 (L2), and Layer 3 (L3).

[0051] NR's Layer 2 (L2) is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where for example:

[0052] ○The physical layer provides the transport channel to the MAC sublayer;

[0053] ○The MAC sublayer provides logical channels to the RLC sublayer;

[0054] ○ The RLC sublayer provides RLC channels to the PDCP sublayer;

[0055] ○ The PDCP sublayer provides radio bearer to the SDAP sublayer;

[0056] ○The SDAP sublayer provides Quality of Service (QoS) flows to 5GC;

[0057] o Control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0058] Layer 3 (L3) includes, for example, Radio Resource Control (RRC) in accordance with 3GPP TS 38.300 V16.6.0 (2021-06) Section 6, which is incorporated herein by reference.

[0059] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) protocols of the gNB, or the RRC and PDCP protocols of the en-gNB, which controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0060] The gNB distributed unit (gNB-DU) includes, for example, a logical node that hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layers of a gNB or en-gNB, and whose operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to as a DU or distributed unit in this article.

[0061] As used herein, the term "network node" may refer to any one of a gNB, a gNB-CU, or a gNB-DU, or any combination thereof. A RAN (Radio Access Network) node or a network node (such as, for example, a gNB, a gNB-CU, or a gNB-DU, or a portion thereof) may be implemented using, for example, a device having at least one processor and / or at least one memory having processor-readable instructions ("program") configured to support and / or supply and / or process CU and / or DU related functions and / or features, and / or at least one protocol (sub) layer of a RAN (Radio Access Network), such as layer 2 and / or layer 3. There may be different functional splits between the central unit and the distributed units. The following will be combined with Figure 1 to describe examples of such devices and components.

[0062] The gNB-CU part and the gNB-DU part can be collocated or physically separated. The gNB-DU can be even further split into two parts, for example, one part includes a processing device and the other part includes an antenna. The central unit (CU) may also be referred to as a baseband unit / radio equipment controller / cloud RAN / virtual RAN (BBU / REC / C-RAN / V-RAN), an open RAN (O-RAN) or a part thereof. The distributed unit (DU) may also be referred to as a remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU) or a part thereof. Hereinafter, in various exemplary embodiments of the present disclosure, a network node supporting at least one of the central unit functions or layer 3 protocols of a radio access network may be, for example, a gNB-CU. Similarly, a network node supporting at least one of the distributed unit functions or layer 2 protocols of a radio access network may also be, for example, a gNB-DU.

[0063] A gNB-CU may support one or more gNB-DUs. A gNB-DU may support one or more cells and may therefore support a serving cell for a user equipment (UE) or a candidate cell for handover, dual connectivity and / or carrier aggregation.

[0064] User equipment (UE) 150 may be, or may include, a wireless or mobile device, a device having a radio interface for interacting with a RAN (Radio Access Network), a smartphone, an in-vehicle device, an IoT device, or an M2M device, as well as other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least perform certain operations, such as, for example, an RRC connection with a RAN. Examples of components of a UE will be combined with Figure 4 In an embodiment, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be sent to the RAN via the radio (e.g., to reach and communicate with a serving cell). In an embodiment, the UE 150 may generate and send and receive RRC messages containing one or more RRC PDUs (packet data units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0065] Continue to refer Figure 1In the example of a 5G NR network, the network system 100 provides one or more cells that define a coverage area of ​​the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network, or may include any other device configured to control radio communications and manage radio resources within a cell. As used herein, the term "resource" may refer to radio resources, such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In an embodiment, the network node 120 may be referred to as a base station.

[0066] Figure 1 An example is provided and only the network system 100 and the UE 150 are described. Those skilled in the art will appreciate that the network system 100 includes Figure 1 Components not shown in the figure, and it will be understood that other user devices can communicate with the network system 100.

[0067] Figure 2 yes Figure 1 A 5G NR network may be described as an example of a network system 100, and aspects described below should also be applicable to other types of network systems. The network system may be based on Figure 1 1 and 2. The UE 150 is operated by the signals and connections illustrated in 22 to enable the UE 150 to communicate with the network system 100 through the radio access network 225. In addition, as shown and described herein, the network system can be divided into user plane components and functions and control plane components and functions. Unless otherwise specified, the terms "component", "function" and "service" are used interchangeably herein, and they may refer to instructions executed by one or more processors and implemented by these instructions.

[0068] The following describes example functionality of these components. The example functionality is illustrative only, and it should be understood that the components described herein may perform additional operations and functionality. In addition, the connections between components may be virtual connections through service-based interfaces, such that any component may communicate with any other component. In this way, any component may act as a service "producer" for any other component that is a service "consumer" to provide services for network functions.

[0069] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a unified data repository (UDR) 224.

[0070] Additional components and functions of the core network 210 may include application functions 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analysis data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operations and management functions (OAM) 223.

[0071] The user plane includes UE 150, radio access network (RAN) 225, user plane function (UPF) 226, and data network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 may include one or more components such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides a connection for data sent through the RAN 225. For example, the DN 226 identifies services from a service provider, Internet access, and third-party services.

[0072] AMF 212 handles connection and mobility tasks. AUSF 211 receives the authentication request from AMF 212 and interacts with UDM 217 to authenticate and verify the network response to determine successful authentication. SMF 213 performs packet data unit (PDU) session management and manages the session context with UPF 226.

[0073] NSSF 214 may select a network slice instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). The selection and determination are used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create specialized network services. NRF 216 acts as a repository for storing network functions to allow these functions to register and discover each other.

[0074] UDM 217 generates authentication vectors for use by AUSF 211 and ADM 212, and provides user identification processing. UDM 217 can be connected to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services, etc.) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, and provide quality of service (QoS) and charging functions.

[0075] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analysis and provides insight into functions that utilize the analysis in service provisioning. ADRF 221 allows consumers to store, retrieve, and remove data and analysis. MDAF 222 provides additional data analysis services for network functions. OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0076] Figure 2 These are merely examples of components of a network system, and variations are considered to be within the scope of the present disclosure. In an embodiment, a network system may include Figure 2 In an embodiment, the network system may not include other components not shown in the figure. Figure 2 Each component shown. In an embodiment, components and connections can be made using Figure 2 The connections shown may be implemented in different ways. Such and other embodiments are considered to be within the scope of the present disclosure.

[0077] As mentioned above, in the 5G wireless system, the signaling protocol (NAS non-access layer protocol) between the user UE and the core network is carried in the radio interface and the RRC signaling on the N2 interface between the base station and the AMF (i.e., the next generation application protocol (NGAP) on the stream control transmission protocol (SCTP)). For NAS for other core network functions, the AMF transparently relays the message through the service-based core interface. That is, the AMF is a single point of contact and single point of failure from the UE to any network function. Each control plane message from the UE traverses through the AMF using the NAS protocol.

[0078] However, with respect to the concept of distributed NAS, service-based NAS messaging may be utilized. Thus, for example, a direct Internet Protocol (IP) connection may be enabled between the UE and any core network function, such that the IP connection (e.g., between the UE and the network function) will directly carry the NAS signaling messages. Thus, NAS messaging may not be centralized and relayed through the AMF, but may be directly signaled between the UE and the network function.

[0079] In various example embodiments, distributed NAS may use the IP protocol, i.e., the UE utilizes NAS signaling directly with any core network functions using IP. In various examples, the IP packets themselves will carry the NAS messages. Thus, in various example embodiments, a service-based NAS implementation (e.g., NAS messages defined as text-based HTTP payloads) may be utilized.

[0080] In order to achieve the above-mentioned UE core network function communication, a radio system mechanism can be utilized that enables the UE to obtain the IP address for NAS signaling. The IP address can be obtained before any NAS signaling begins (for example, during a registration request). In addition, if the UE uses PDU type IP, the control plane IP address obtained by the UE can be independent of the IP address that the UE will use for the protocol data unit (PDU) session (or equivalent session) in the user plane.

[0081] Therefore, the UE may obtain such an IP address using a combination and extension of protocol mechanisms defined, for example, by the Third Generation Partnership Project (3GPP) and / or defined by the Internet Engineering Task Force (IETF). For example, an IETF Dynamic Host Configuration Protocol (DHCP) mechanism may be used in conjunction with a 3GPP RRC protocol and a base station mechanism to obtain a control plane IP address for a network function. Those skilled in the art will understand the mechanisms for communicating using the IETF DHCP and 3GPP RRC protocols.

[0082] The terms "service" and "network function" are used interchangeably herein, and thus descriptions referring to one of these terms should be considered as also referring to the other.

[0083] As used herein, communication with a radio access network (RAN) may refer to and represent communication with a portion of the RAN, such as with a network node (e.g., DU and / or CU) or another portion of the RAN. As used herein, communication with a core network may refer to and represent communication with one or more services / network functions in the core network, such as an AMF, or another service of the core network.

[0084] Figure 3 is a diagram of an example embodiment of signals and operations between a UE, a gNodeB, a router, and a DHCP server according to one illustrative aspect of the present disclosure. The following paragraphs will describe various signals and operations. It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0085] In various embodiments, the DHCP server may reside in a site router (e.g., a router) that connects multiple network nodes (e.g., a base station) to an Internet Protocol (IP) domain network. In various embodiments, the site router may reside outside the DHCP server and be connected to the DHCP server. Those skilled in the art will appreciate various connection schemes for providing a DHCP server connection to one or more network nodes.

[0086] At operation 301, the gNodeB sends a master information block (MIB) message to the UE, and the UE receives the master information block message. In some embodiments, the master information block message may carry information about radio bearers, physical channels, and transport channels of a 5G New Radio (NR) network. In some example embodiments, the MIB may convey information such as carrier frequency, bandwidth, modulation, coding rate, and access control parameters of 5G NR.

[0087] At operation 302, the gNodeB sends a system information block type 1 to the UE, and the UE receives the system information block type 1. In some example embodiments, the system information block type 1 may include cell access related information (e.g., a list of public land mobile network (PLMN) identities, tracking area numbers, cell identities, etc.), information for cell selection (e.g., minimum required receive (Rx) level and offset in a cell), p-Max, frequency band indicator, and scheduling information. Those skilled in the art will understand the information to be sent in the master information block message and the system information block type 1 message.

[0088] After receiving the Master Information Block message and the System Information Block Type 1 message, at operation 303, the UE sends a Random Access Channel (RACH) preamble message to the gNodeB, and the gNodeB receives the RACH preamble message. In response to receiving the RACH preamble message, at operation 304, the gNodeB sends a RACH response message to the UE, and the UE receives the RACH response message. At operation 305, the UE sends an RRC setup request message to the gNodeB, and the gNodeB receives the RRC setup request message. Those skilled in the art will appreciate and understand the RACH preamble message, the RACH response message, and the RACH setup request message, and the information that can be included in the message.

[0089] After receiving the RRC SETUP REQUEST message, the gNodeB may perform one of two options.

[0090] In some example embodiments, the gNodeB may perform a first option (option 1) procedure, which in various example embodiments may be a procedure utilizing an IPv4 protocol. Thus, at operation 306, the gNodeB sends a DHCP discover message to the DHCP server (e.g., via a router), the message including a client identifier (clientID) of the UE from which the gNodeB received the RRC setup request message, and the DHCP server receives the DHCP discover message including the clientID of the UE. The client identifier may be specified in RFC 2131. There are several methods that may be used to assign a unique ID to a UE based on a unique UE ID (e.g., RAN UE NGAP ID, S-TMSI, etc.).

[0091] In response to receiving the DHCP discover message including the clientID of the UE, at operation 307, the DHCP server sends a DHCP offer message to the gNodeB, and the gNodeB receives the DHCP offer message. In various embodiments, the DHCP offer message may include the NAS IP address of the UE (UE NAS IP) and the IP address of the NRF (NRF IP). In one embodiment, the NRF IP address may be included in the DHCP offer message as part of the "options" field of the DHCP message, which may be defined as a new option type, or a vendor-specific custom option type with a currently unassigned option code. In various example embodiments, an option with an existing option code may be used to carry the NRF IP address. The UE NAS IP may be assigned by the DHCP server and may be unique to the UE associated with the clientID.

[0092] After accepting the UE NAS IP address, at operation 308, the gNodeB sends a DHCP request message to the DHCP server, and the DHCP server receives the DHCP request message. At operation 309, the DHCP server completes the process in option 1 by sending a DHCP confirmation message to the gNodeB, and the gNodeB receives the DHCP confirmation message.

[0093] Option 1 may be performed only the first time the gNodeB receives an RRC Setup Request message from the UE, or may be performed periodically by the gNodeB to obtain the UE NAS IP address. In various embodiments, after the gNodeB obtains the UE's IP address, the gNodeB may update the IP address by simply sending a DHCP request.

[0094] In various embodiments, after the gNodeB receives the RRC setup request, the gNodeB may perform a second option (option 2). In some example embodiments, option 2 may be a process utilizing the IPv6 protocol. For example, at operation 310, the gNodeB sends a router solicitation (RS) message to a router, and the router receives the RS message. The RS message discovers an available router, which includes information indicating whether the current network domain is automatically managed to assign and manage IP addresses to facilitate IP communications between the UE and the network function.

[0095] At operation 311, the router sends a router advertisement (RA) message to the gNodeB, and the gNodeB receives the RA message indicating the DHCP protocol to be used by the gNodeB. For example, the RA message may include an M flag indicating that the gNodeB will use, for example, a stateful DHCPv6 procedure.

[0096] After receiving the RA message, the gNodeB may begin looking for an available DHCP server. Thus, at operation 312, the gNodeB sends a DHCP solicit message to the DHCP server, and the DHCP server receives the DHCP solicit message. At operation 313, the available DHCP server sends a DHCP advertise message to the gNodeB, and the gNodeB receives the DHCP advertise message. In various example embodiments, the gNodeB may send multiple DHCP solicit messages to multiple potential DHCP servers. After discovering an available DHCP server, the gNodeB may send a subsequent DHCP request to the selected available DHCP server.

[0097] In some example embodiments, operations 310 to 313 may be performed only when the gNodeB first receives an RRC setup request message from any UE (the gNodeB first receives the RRC setup request message from the UE). In various example embodiments, the gNodeB may then know the DHCP server for the received subsequent RRC setup request messages.

[0098] At operation 314, the gNodeB sends a DHCP request message to the DHCP server, and the DHCP server receives the DHCP request message. The DHCP request message includes the clientID of the UE, which may be a DHCP unique identifier (DUID) in IETF terminology described in RFC8415. At operation 315, the DHCP server completes the process in option 2 by sending a DHCP reply message to the gNodeB, and the gNodeB receives the DHCP confirmation message. In various example embodiments, the DHCP reply message may include the NAS IP address of the UE (UE NAS IP) and the IP address of the NRF (NRF IP). In various embodiments, the NRF IP address may be included in the DHCP offer message as part of the "option" field of the DHCP message, which may be defined as a new option type, or a vendor-specific custom option type with a currently unassigned option code. In other various embodiments, an option with an existing option code may be used to carry the NRF IP address. The UE NAS IP may be assigned by the DHCP server and may be unique to the UE associated with the clientID.

[0099] After the gNodeB has the UE NAS IP and NRF IP, the gNodeB can transmit the information to the UE. Therefore, at operation 316, the gNodeB sends an RRC setup message to the UE, and the UE receives the RRC setup message. The RRC setup message may include the UE NAS IP and the NRF IP.

[0100] Figure 4 is a representation of an example RRC setup message 400 according to one illustrative aspect of the present disclosure. Figure 4 As shown in , the RRC setup message includes a header 410, and information elements (IEs) 420 and 430. Although those skilled in the art will appreciate the various information elements provided in the RRC setup message, the RRC setup message also includes UENASIPAddressIE, UENASIPNetmask IE, and NrfIPAddress IE. In various embodiments, the UENASIPAddress IE may include information related to the IP address of the UE to be used in NAS messaging / signaling. In various embodiments, the UENASIPNetmask IE may include an IP network mask for the UE NAS IP address. In various embodiments, the NrfIPAddress IE may include the IP address of the NRF (or equivalent core network function).

[0101] Reference again Figure 3, after receiving the RRC setup message, the UE may obtain an IP service address from the NRF (or other equivalent core network function) in order to perform NAS messaging. In various example embodiments, at operation 317, the UE sends a Get Service #N IP Address message to the NRF (e.g., via an appropriate RRC message and an IP-based NAS message), and the NRF receives the Get Service #N IP Address message. In various embodiments, the Get Service #N IP Address message may include a request for a first NAS service IP address of a network function that the UE desires to be served. The request for the NAS service IP address may be requested directly by the UE to the NRF via IP messaging. In various example embodiments, the appropriate RRC message at operation 317 may include an RRC Setup Complete message.

[0102] At operation 318, the NRF sends a receive service #N IP address message to the UE (e.g., via appropriate RRC messages and NAS messages over IP), and the UE receives the receive service #N IP address message. In various embodiments, the receive service #N IP address message includes the IP address of the network function requested by the UE.

[0103] Thus, at operation 319, IP-based NAS messaging may begin directly between the UE and the network function (service #N) (e.g., via the gNodeB). Operations 316 to 319 may be performed any number of times so that the UE performs service IP address discovery and NAS messaging for additional network function #N.

[0104] therefore, Figure 3 Signals and operations involving, for example, a UE, a gNodeB, and a DHCP server are described. Operations will be described below from the perspective of each of the UE, gNodeB, and DHCP server.

[0105] The following describes the operations from the perspective of the UE. From such a perspective, a method may include: receiving a first message from a gNodeB (e.g., at the above operation 316), the first message including: a first identifier of the UE, and a second identifier identifying an address of a first component in a network. The UE sends a second message to the gNodeB (e.g., at the above operation 317), the second message including: a request for an address of a second component of the network. The UE receives a third message from the gNodeB (e.g., at the above operation 318), the third message including: a third identifier of the address of the second component of the network, and the UE sends a fourth message to the second component of the network (e.g., at the above operation 319.), the fourth message including: an identifier of the address of the second component of the network.

[0106] The operations are described below from the perspective of the gNodeB. From such a perspective, a method may include: receiving, by the gNodeB, a first message from a UE (e.g., at operation 305 described above), the first message initiating communication with the gNodeB. The gNodeB sends a second message to a DHCP server (e.g., at operation 306 or operation 314), the second message including: a first identifier of the UE. The gNodeB receives a third message from the DHCP server (e.g., at operation 307 or operation 315), the third message including: a second identifier of the UE, and a third identifier identifying an address of a first component in the network, and the gNodeB sends a fourth message to the UE (e.g., at operation 316), the fourth message including: a second identifier of the UE, and a third identifier identifying an address of the first component in the network.

[0107] The operations are described below from the perspective of DHCP. From such a perspective, a method may include: a DHCP server receives a first message from a gNodeB (e.g., at operation 306 or operation 314), the first message including: a first identifier of the UE. The DHCP server assigns a second identifier to the UE and sends a second message to the gNodeB (e.g., at operation 307 or operation 315), the second message including: a second identifier of the UE, and a third identifier identifying an address of a first component in the network.

[0108] Reference now Figure 5 , a block diagram of example components of a UE or network device (e.g., a RAN or core network) is shown. The device includes an electronic storage device 510, a processor 520, a network interface 540, and a memory 550. The various components can be communicatively coupled to each other. The processor 520 can be, and can include, any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system on a chip (SoC), or any other type of processor. The memory 550 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 550 includes processor-readable instructions that are executable by the processor 520 to cause the device to perform various operations, including the operations described herein, such as Figure 3 to Figure 4 operation.

[0109] Electronic storage 510 may be and include any type of electronic storage for storing data, such as a hard drive, a solid state drive, an optical disk, and / or other non-transitory computer-readable medium, as well as other types of electronic storage. Electronic storage 510 stores processor-readable instructions for causing, or configured to cause, the device to perform its operations, and also stores data associated with such operations, such as storing data related to the 5G NR standard and other data. Network interface 540 may implement wireless network technologies, such as 5G NR and / or other wireless network technologies. For example, in various example embodiments, the network interface may include a transceiver, and one or more antennas.

[0110] Figure 5 The components shown in are examples only, and those skilled in the art will appreciate that the apparatus includes other components not shown, and may include a plurality of any of the components shown. For example, in various example embodiments, the UE may include a user interface, such as a display and / or a keyboard communicatively coupled to other components of the UE. Such and other embodiments are considered within the scope of the present disclosure.

[0111] Other embodiments of the present disclosure include the following examples.

[0112] Example 1.1. An apparatus comprising:

[0113] means for receiving, by a user equipment (UE), a first message from an apparatus, the first message comprising: a first identifier of the UE, and a second identifier identifying an address of a first component in a network;

[0114] means for sending, by the UE to the apparatus, a second message, the second message comprising: a request for an address of a second component of the network;

[0115] means for receiving, by the UE, a third message from the network device, the third message comprising: a third identifier of an address of a second component of the network; and

[0116] A component for sending, by the UE, a fourth message to a second component of the network, the fourth message comprising: an identifier of an address of the second component of the network.

[0117] Example 1.2. The apparatus of Example 1.1, wherein the first identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0118] Example 1.3. The apparatus of Example 1.2, wherein the first component in the network is a network repository function (NRF).

[0119] Example 1.4. The apparatus of Example 1.3, wherein the second identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0120] Example 1.5. An apparatus as described in any of Examples 1.1 to 1.4, wherein the second message includes: a request for a network function service IP address for NAS messaging.

[0121] Example 1.6. The apparatus of Example 1.5, wherein the third message includes: an IP address of the network function service for NAS messaging.

[0122] Example 1.7. The apparatus of Example 1.6, wherein the fourth message is sent to a network function identified by an IP address for NAS messaging served by the network function.

[0123] Example 1.8. The apparatus of Example 1.1, wherein the fourth message is an Internet Protocol version 4 (IPv4) protocol message.

[0124] Example 1.9. The apparatus of Example 1.1, wherein the fourth message is an Internet Protocol version 6 (IPv6) protocol message.

[0125] Example 1.10. The apparatus of Example 1.1, wherein the first message is a radio resource control (RRC) setup message.

[0126] Embodiment 2.1. A device comprising:

[0127] means for receiving, by the apparatus, a first message from a user equipment (UE), the first message initiating communication with a first apparatus;

[0128] means for sending, by the apparatus, a second message to a second apparatus, the second message comprising: a first identifier of the UE;

[0129] means for receiving, by the apparatus, a third message from a second apparatus, the third message comprising: a second identifier of the UE, and a third identifier identifying an address of a first component in a network; and

[0130] A component for sending, by the apparatus, a fourth message to the UE, the fourth message comprising: a second identifier of the UE and a third identifier identifying an address of a first component in a network.

[0131] Example 2.2. The apparatus of Example 2.1, wherein the second identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0132] Example 2.3. The apparatus of Example 2.2, wherein the first component in the network is a network repository function (NRF).

[0133] Example 2.4. The apparatus of Example 2.3, wherein the third identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0134] Example 2.5. The apparatus of Example 2.1, wherein the first identifier of the UE is a client identifier of the UE.

[0135] Example 2.6. The apparatus of Example 2.1, wherein the third message is an Internet Protocol version 4 (IPv4) protocol message.

[0136] Example 2.7. The apparatus of Example 2.6, wherein the fourth message is an IPv4 protocol message.

[0137] Example 2.8. The apparatus of Example 2.1, wherein the third message is an Internet Protocol version 6 (IPv6) protocol message.

[0138] Example 2.9. The apparatus of Example 2.8, wherein the fourth message is an IPv6 protocol message.

[0139] Example 2.10. The apparatus of Example 2.1, wherein the first message is a radio resource control (RRC) setup message.

[0140] Example 3.1. An apparatus comprising:

[0141] means for receiving, by the apparatus, a first message from a second apparatus, the first message comprising: a first identifier of a user equipment (UE);

[0142] means for assigning, by the apparatus, a second identifier to the UE; and

[0143] A means for sending, by the apparatus, a second message to a second apparatus, the second message comprising: a second identifier of the UE, and a third identifier identifying an address of a first component in a network.

[0144] Example 3.2. The apparatus of Example 3.1, wherein the second identifier is an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging.

[0145] Example 3.3. The apparatus of Example 3.2, wherein the first component in the network is a network repository function (NRF).

[0146] Example 3.4. The apparatus of Example 3.3, wherein the third identifier is an Internet Protocol (IP) address of the NRF for non-access stratum (NAS) messaging.

[0147] Example 3.5. The apparatus of Example 3.1, wherein the first identifier of the UE is a client identifier of the UE.

[0148] Example 3.6. The apparatus of Example 3.1, wherein the first message is an Internet Protocol version 4 (IPv4) protocol message.

[0149] Example 3.7. The apparatus of Example 3.6, wherein the second message is an IPv4 protocol message.

[0150] Example 3.8. The apparatus of Example 3.1, wherein the first message is an Internet Protocol version 6 (IPv6) protocol message.

[0151] Example 3.9. The apparatus of Example 3.8, wherein the second message is an IPv6 protocol message.

[0152] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be interpreted as limitations, but as the basis for the claims, and those skilled in the art use the representative basis of the present disclosure in various ways in almost any appropriately detailed structure as a teaching. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0153] For example, the RRC setup message sent by the base station depicts an information element for providing UE IP address and NRF IP address information. However, this information may be provided in other fields of the RRC setup message.

[0154] In addition, the components for performing the functions and methods described herein may be used in conjunction with Figure 5 The components described are associated, and in various example embodiments may include hardware, software, circuitry, or other aspects of these components.

[0155] According to the present disclosure, the phrases "in one aspect", "in certain aspects", "in various aspects", "in some aspects" or "in other aspects" may each refer to one or more of the same or different aspects. The phrase "plurality" may refer to two or more.

[0156] According to the present disclosure, the phrases "in one embodiment," "in an embodiment," "in various embodiments," "in some embodiments," or "in other embodiments" may each refer to one or more of the same or different embodiments. A phrase of the form "A or B" means "(A), (B), or (A and B)." A phrase of the form "at least one of A, B, or C" means "(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C)."

[0157] Any method, program, algorithm or code described herein can be converted into a programming language or computer program, or represented by a programming language or computer program. The terms "programming language" and "computer program" used herein each include any language for specifying computer instructions, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command language, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, the metalanguage of the program itself, and all first generation, second generation, third generation, fourth generation, fifth generation or subsequent computer languages. Also include databases and other data patterns, and any other metalanguage. The language of the interpreted, compiled or compiled and interpreted methods is not distinguished. The compiled version of the program is not distinguished from the source code version. Therefore, if the programming language can exist in more than one state (such as source, compilation, object or link), the reference to the program is a reference to any and all such states. The reference to the program can cover the intention of actual instructions and / or these instructions.

[0158] Although various aspects of the present disclosure are shown in the accompanying drawings, it is not intended that the present disclosure is limited thereto, as the scope of the present disclosure should be as broad as possible and the specification should be read in the same manner. Therefore, the above description should not be interpreted as limiting, but only as an example of specific aspects. Those skilled in the art will be able to envision other modifications within the scope and spirit of the appended claims.

Claims

1. A method of a user equipment (UE), the method comprising: A radio resource control (RRC) setup message is received from a radio access network (RAN) node, the RRC message comprising: an Internet Protocol (IP) address of the UE for Non-Access Stratum (NAS) messaging, and The IP address of the Network Repository Function (NRF) used for NAS messaging in the network; Sending a get service message to the NRF, the get service message including: a request for a NAS service IP address of a network function that the UE expects to be served; Receive a receive service message from the NRF, the receive service message including: the NAS service IP address of the network function; and An IP-based NAS message is sent to the network function to obtain the service, wherein the IP-based NAS message includes: the NAS service IP address of the network function.

2. The method of claim 1, wherein the get service message is sent to the NRF via an RRC message and an IP-based NAS message.

3. The method according to claim 1, wherein the obtaining service message comprises: RRC establishment complete message.

4. The method of claim 1, wherein the receive service message is received from the NRF via an RRC message and an IP-based NAS message.

5. The method of claim 1, wherein the IP-based NAS message is an Internet Protocol version 4 (IPv4) protocol message.

6. The method of claim 1, wherein the IP-based NAS message is an Internet Protocol 6 (IPv6) protocol message.

7. The method of claim 1, wherein the radio access network (RAN) node comprises a gNodeB.

8. A method of a Radio Access Network (RAN) node, the method comprising: receiving a radio resource control (RRC) setup request message from a user equipment (UE), the RRC setup request message initiating communication with the RAN node; sending a second message to a Dynamic Host Configuration Protocol (DCHP) server, wherein the second message includes: a client identifier of the UE; receiving a third message from the DHCP server, the third message including: an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging, and an IP address of a network repository function (NRF) in a network for NAS messaging; and An RRC setup message is sent to the UE, the RRC setup message including: the Internet Protocol (IP) address of the UE for NAS message delivery, and the IP address of the NRF in the network for NAS message delivery.

9. The method of claim 8, wherein the third message comprises a DHCP offer message, the DHCP offer message being an Internet Protocol version 4 (IPv4) protocol message.

10. The method of claim 9, wherein the second message comprises a DHCP discover message, the DHCP discover message being an IPv4 protocol message.

11. The method of claim 8, wherein the third message comprises a DHCP reply message, the DHCP reply message being an Internet Protocol version 6 (IPv6) protocol message.

12. The method of claim 11, wherein the second message comprises a DHCP request message, the DHCP request message being an IPv6 protocol message.

13. A method of a Dynamic Host Configuration Protocol (DHCP) server, the method comprising: receiving a first message from a radio access network (RAN) node, the first message comprising a client identifier of a user equipment (UE); assigning the UE an Internet Protocol (IP) address of the UE for non-access stratum (NAS) messaging; as well as A second message is sent to the RAN node, the second message including: the IP address of the UE for NAS message delivery and an IP address of a network repository function (NRF) in a network for NAS message delivery.

14. The method of claim 13, wherein the first message comprises a discovery message, the discovery message being an Internet Protocol version 4 (IPv4) protocol message.

15. The method of claim 14, wherein the second message comprises an offer message, the offer message being an IPv4 protocol message.

16. The method of claim 13, wherein the first message comprises a request message, the request message being an Internet Protocol version 6 (IPv6) protocol message.

17. The method of claim 16, wherein the second message comprises a reply message, the reply message being an IPv6 protocol message.

18. A user equipment (UE), comprising: at least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the user equipment to at least perform the method according to any one of claims 1 to 7.

19. A radio access network node, comprising: at least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the radio access network node to at least perform the method according to any one of claims 8 to 12.

20. A dynamic host configuration protocol server, comprising: at least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the dynamic host configuration protocol server to at least perform the method according to any one of claims 13 to 17.

Images