Network function determination

Abstract

Aspects of the present disclosure relate to devices, processors, and methods for network function (NF) determination in, for example, a service-based radio access network (RAN). In one aspect, an access network device receives, from a user equipment (UE), a message associated with a network function (NF) type in a core network. And the access network device determines a first NF of the NF type used for serving the UE in the core network. And the access network equipment sends the message to the first NF of the NF type. By implementing embodiments of the present disclosure, a service-based RAN may know selected NFs for serving a UE and communicate directly with these NFs.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to devices, processors, and methods for determining network functions (NFs) in, for example, service-based radio access networks (RANs). Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, and other suitable wireless access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] One vision for future 6G evolution is to support a service-based RAN architecture. This means that a service-based RAN can provide a service-based interface from the control plane to the core network, and can communicate directly with other network functions (e.g., SMF, LMF) without requiring forwarding by the AMF as in 5G. Furthermore, in a non-split architecture, the service-based interface can be supported by any RAN node; in a CU-DU split RAN architecture, it can be supported by the CU of the RAN node; or in a CU-CP and CU-UP split RAN architecture, it can be supported by the CU-CP of the RAN node, or by the network functions of the RAN node. However, some outstanding issues related to core network functions will be studied in the future. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems for supporting, for example, network function (NF) determination in a service-based radio access network (RAN). In a first aspect of this solution, an access network device includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, a message associated with a network function (NF) type in the core network; determine a first NF of type NF in the core network used to serve the UE; and transmit the message via the transceiver to the first NF of type NF. By performing the determination of the first NF of type NF in the core network used to serve the UE, the service-based RAN can know the selected NFs used to serve the UE and communicate directly with these NFs.

[0005] In some implementations of the access network device described herein, the processor is further configured to: receive a response to the message from a first NF via a transceiver, wherein the response includes information related to the first NF; and forward the response to the UE via the transceiver.

[0006] In some implementations of the access network device described herein, determining the type of the first NF includes: sending a request for determining the type of the first NF to a second NF or a third NF in the core network via a transceiver, wherein the second NF is responsible for UE access and mobility management, and wherein the third NF is responsible for storing information related to the NF in the core network; and receiving information related to the type of the first NF from the second NF or the third NF via a transceiver.

[0007] In some implementations of the access network devices described in this document, the request includes one of the following: NF type; the requested service; or UE identifier (ID).

[0008] In some implementations of the access network devices described in this document, the information includes one of the following: NF type; identifier (ID) of the NF instance; Internet Protocol (IP) address or fully qualified domain name (FQDN) of the NF instance; or a list of service instances associated with the NF instance, wherein the service instances in the list of service instances are associated with one of the following: service name, NF service instance ID, or endpoint address.

[0009] In some implementations of the access network devices described herein, information related to the first NF of NF type is included in information related to at least one NF of NF type.

[0010] In some implementations of the access network device described herein, the information related to at least one NF of NF type includes: information related to multiple NF candidates of NF type selected by the second NF for the UE or discovered by the first NF for the UE, and the processor is further configured to: select the first NF of NF type from the multiple NF candidates.

[0011] In some implementations of the access network device described herein, the processor is further configured to receive, via a transceiver, updated information related to a first NF of type NF or updated information related to multiple NF candidates of type NF selected by the second NF for the UE from a second NF.

[0012] In some implementations of the access network device described herein, a first NF of type NF is selected from a plurality of NF candidates discovered by a third NF, and the processor is further configured to: receive, via a transceiver, a request from the first NF of type NF for providing information related to another NF, which is selected by the access network device from a plurality of NF candidates; and send, via a transceiver, the information related to the other NF to the first NF.

[0013] In some implementations of the access network devices described in this paper, the message includes messages sent to NFs in the core network, and the messages sent to NFs in the core network are carried in messages sent to base stations.

[0014] In some implementations of the access network devices described in this paper, the messages sent to the NFs in the core network include one of the following: a Protocol Data Unit (PDU) session establishment request message for the NF responsible for service management; a location service request message for the NF responsible for location management; and a sensing service request message for the NF responsible for sensing-related functions.

[0015] In some implementations of the access network devices described in this paper, the messages sent to the base station also include an indication for the destination NF.

[0016] In some implementations of the access network devices described herein, the indication specifies one of the following: the type of the NF in the form of an enumeration value; the type of the message in the form of an enumeration value; the protocol identifier of the message in the form of a bitmap; or the identifier (ID) or index of the NF in the form of an integer value.

[0017] In some implementations of the access network device described herein, the access network device is a first access network device, and the processor is further configured to: during the handover process of the UE from the first access network device to the second access network device, send information related to the first NF or information related to the second NF to the second access network device via a transceiver.

[0018] In some implementations of the access network device described herein, the access network device is a first access network device, the UE is a first UE, and the processor is further configured to: during the handover process of the second UE from the second access network device to the first access network device, receive information related to the NF serving the second UE or information related to the second NF serving the second UE via a transceiver from the second access network device.

[0019] In some implementations of the access network device described herein, the access network device is a first access network device, the UE is a first UE, and the processor is further configured to: during the handover process of the second UE from the second access network device to the first access network device, receive information related to the NF serving the second UE via a transceiver from the second NF serving the second UE.

[0020] In a second aspect of the technical solution, an apparatus for performing network functions includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, from an access network device a request for determining a first NF of a network function (NF) type for serving a user equipment (UE); determine the first NF of the NF type; and transmit, via the transceiver, information related to the first NF of the NF type to the access network device.

[0021] In some implementations of the apparatus for performing network functions described herein, the request includes one of the following: NF type; the requested service; or UE identifier (ID).

[0022] In some implementations of the apparatus described herein for performing network functions, the information includes one of the following: NF type; identifier (ID) of the NF instance; Internet Protocol (IP) address or fully qualified domain name (FQDN) of the NF instance; or a list of service instances associated with the NF instance, wherein the service instances in the list of service instances are associated with one of the following: service name, NF service instance ID, or endpoint address.

[0023] In some implementations of the apparatus for performing network functions described herein, the information associated with the first NF includes: information related to multiple NF candidates of the NF type selected by the network function for the UE.

[0024] In some implementations of the apparatus for performing network functions described herein, the processor is further configured to: send a message associated with an NF type to a first NF of type NF via a transceiver; and receive a response to the message from the first NF via a transceiver.

[0025] In some implementations of the apparatus for performing network functions described herein, the processor is further configured to send updated information related to a first NF of type NF to the access network device via a transceiver.

[0026] In a third aspect of the technical solution, a user equipment includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: send a message associated with a first network function (NF) type in the core network to an access network device via the transceiver; and receive a response to the message from the access network device via the transceiver, wherein the response includes information related to the first NF.

[0027] In some implementations of the user equipment described in this document, the information includes one of the following: the identifier (ID) of the NF instance; or the Internet Protocol (IP) address or fully qualified domain name (FQDN) of the NF instance.

[0028] In some implementations of the user equipment described in this paper, the message includes messages destined for NFs in the core network, and the messages destined for NFs in the core network are carried in messages destined for base stations.

[0029] In some implementations of the user equipment described in this paper, the messages sent to the base station also include an indication for the destination NF.

[0030] In some implementations of the user equipment described herein, the indication specifies one of the following: the type of the NF in the form of an enumeration value; the type of the message in the form of an enumeration value; the protocol identifier of the message in the form of a bitmap; or the identifier (ID) or index of the NF in the form of an integer value.

[0031] In a fourth aspect of the technical solution, a processor for wireless communication includes: at least one memory; and a controller coupled to the at least one memory and configured to cause the controller to: receive from a user equipment (UE) a message associated with a network function (NF) type in a core network; determine a first NF in the core network for serving the UE; and send the message to the first NF of the NF type.

[0032] In a fifth aspect of the technical solution, a processor for wireless communication includes: at least one memory; and a controller coupled to the at least one memory and configured to: receive from an access network device a request for determining a first NF for serving a network function (NF) type for a user equipment (UE); determine the first NF of the NF type; and send information related to the first NF of the NF type to the access network device.

[0033] In a sixth aspect of the technical solution, a processor for wireless communication includes: at least one memory; and a controller coupled to the at least one memory and configured to cause the controller to: send a message associated with a network function (NF) type in the core network to an access network device; and receive a response to the message from the access network device, wherein the response includes information related to a first NF.

[0034] In a seventh aspect of the technical solution, a method performed by an access network device includes: receiving from a user equipment (UE) a message associated with a network function (NF) type in a core network; determining a first NF of NF type used to serve the UE in the core network; and sending the message to the first NF of NF type.

[0035] In an eighth aspect of the technical solution, a method performed by a network function includes: receiving from an access network device a request for determining a first NF of a network function (NF) type for serving a user equipment (UE); determining the first NF of the NF type; and sending information related to the first NF of the NF type to the access network device.

[0036] In a ninth aspect of the technical solution, a method performed by a user equipment includes: sending a message associated with a network function (NF) type in the core network to an access network device; and receiving a response to the message from the access network device, wherein the response includes information related to a first NF.

[0037] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0038] Figure 1 An example of a wireless communication system that supports service-based NF determination in a RAN according to various aspects of this disclosure is illustrated.

[0039] Figure 2 The illustration depicts an exemplary service-based architecture in a 5G core network according to various aspects of this disclosure.

[0040] Figure 3 The illustration shows an exemplary service-based architecture in a 6G core network according to various aspects of this disclosure.

[0041] Figure 4 An example signaling procedure for determining the NF in a service-based RAN according to various aspects of this disclosure is illustrated.

[0042] Figure 5An example process for determining NFs in a service-based RAN according to various aspects of this disclosure is illustrated.

[0043] Figure 6 Another example process for determining NFs in a service-based RAN according to various aspects of this disclosure is illustrated.

[0044] Figure 7 The illustration shows yet another example process for determining NFs in a service-based RAN according to various aspects of this disclosure.

[0045] Figure 8 The illustration shows an example RRC indication of a NAS message destination in a service-based RAN architecture according to various aspects of this disclosure.

[0046] Figure 9 The illustration depicts an example process for transmitting information related to a selected NF during handover in a service-based RAN architecture, according to various aspects of this disclosure.

[0047] Figure 10 The illustration shows another example process for transmitting information related to a selected NF during handover in a service-based RAN architecture, according to various aspects of this disclosure.

[0048] Figure 11 The illustration shows another example process for transmitting information related to a selected NF during handover in a service-based RAN architecture, according to various aspects of this disclosure.

[0049] Figure 12 An example of a device is illustrated that supports the determination of an NF in a service-based RAN according to various aspects of this disclosure.

[0050] Figure 13 An example of a processor that supports service-based NF determination in a RAN according to various aspects of this disclosure is illustrated.

[0051] Figure 14 The diagram illustrates a flowchart of a method for determining the NF in a service-based RAN according to various aspects of this disclosure.

[0052] Figure 15 The diagram illustrates a flowchart of a method for determining the NF in a service-based RAN according to various aspects of this disclosure.

[0053] Figure 16 The diagram illustrates a flowchart of a method for determining the NF in a service-based RAN according to various aspects of this disclosure. Detailed Implementation

[0054] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0055] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0056] The references to "an embodiment," "example embodiment," "embodiment," and "some embodiments" in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment is required to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that, for those skilled in the art, in conjunction with other embodiments (whether explicitly described) to affect such a feature, structure, or characteristic is within the scope of knowledge of those skilled in the art.

[0057] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0058] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “containing,” when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0059] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G NR, LTE, LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, future types of communication technologies and systems may also embody this disclosure. It should not be construed as limiting the scope of this disclosure to the systems described above.

[0060] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for V2X (Vehicle-to-Everything) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header (RRH), relay, Integrated Access and Backhaul (IAB) nodes, low-power nodes (such as femtoBS, picoBS), etc., depending on the terminology and technology used.

[0061] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end-user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0062] Various aspects of this disclosure are described in the context of wireless communication systems.

[0063] Figure 1 An example of a wireless communication system 100 supporting service-based RAN (Network Functions) determination according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0064] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0065] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0066] One or more UEs 104 (such as UE 104-1 or UE 104-2) may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0067] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1The diagram illustrates some examples of UE 104. UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown in the diagram. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may act as relays in the wireless communication system 100.

[0068] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0069] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0070] In some implementations, network entity 102 can be configured in a decoupled architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: CU, DU, Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., near real-time RIC, non-real-time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0071] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional splitting among CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional splitting can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can carry upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0073] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

[0074] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the corresponding network entity 102 communicating via such communication links.

[0075] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0076] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0077] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable wireless access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0078] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. The first parameter set (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15kHz) and the normal cyclic prefix. In some implementations, the first parameter set (e.g., ) associated with the first subcarrier spacing (e.g., 15kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30kHz) and the normal cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., μ=4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0079] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0080] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0081] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other equipment or devices, for short-range, high data rate capabilities.

[0082] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the first parameter set (e.g., ...). μ =0), which includes a 15kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30kHz subcarrier spacing; the third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., μ =2), which includes a 60kHz subcarrier spacing; the fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0083] Figure 2 The illustration depicts an exemplary service-based architecture in a 5G core network according to various aspects of this disclosure. In the evolution of 5G, the service-based core network architecture represents a fundamental shift from previous generations of traditional network architectures. It introduces a service-oriented approach that makes the deployment and management of network functions and services more flexible, scalable, and efficient.

[0084] Such as combination Figure 2The Service-Based Interface (SBI) is a standardized communication interface that acts as a common language or protocol, enabling different network functions to understand and communicate with each other. First, SBI ensures interoperability and flexibility by decoupling network functions, making it easier to deploy, integrate, and modify services. Through SBI, network functions can be developed and deployed independently and easily connected to form end-to-end service chains. Second, SBI provides a standardized and well-defined set of rules, protocols, and data formats that facilitate the exchange of information, commands, and data between network functions. This enables efficient coordination and collaboration among network functions, allowing them to work harmoniously together to provide the desired services to end users.

[0085] On the other hand, for the RAN in 5G, the AMF is the only bridge connecting the RAN with other core network functions. The AMF is also responsible for discovering / selecting other network functions (e.g., SMF, LMF) to serve the UE, and any messages between the UE / RAN and other NFs are forwarded by the AMF.

[0086] Figure 3 The illustration shows an exemplary service-based architecture in a 6G core network according to various aspects of this disclosure.

[0087] As mentioned above, supporting a service-based RAN architecture is one of the visions for future 6G evolution. As a first step, the RAN control plane can adopt, for example... Figure 3 The example shown is a service-based architecture.

[0088] Since this disclosure pertains to 6G evolution (e.g., 6G computing capability networks), the term "RAN" mentioned and / or used in the proposed(s) technical solutions primarily refers to a service-based RAN, where the service-based RAN can provide a service-based interface from the control plane to the core network, and the service-based RAN can communicate directly with other network functions (e.g., SMF, LMF). Furthermore, in a non-split architecture, the service-based interface can be supported by any RAN node; in a CU-DU split RAN architecture, the service-based interface can be supported by the CU of the RAN node; or in a CU-CP and CU-UP split RAN architecture, the service-based interface can be supported by the CU-CP of the RAN node, or the service-based interface can be supported by the network functions of the RAN node.

[0089] However, if combined Figure 3The above two issues may require further investigation. Regarding the first issue, the service-based RAN may need to know the selected NFs used to serve the UE and communicate directly with these NFs. As a first option, the AMF still selects the relevant NFs (e.g., SMF / LMF / PCF), and this selection can be explicitly triggered by a request from the RAN or determined by the AMF based on NAS message interpretation. Subsequently, the AMF will notify the RAN of the selected NFs, and the RAN can communicate directly with the selected NFs. As a second option, the RAN will select the relevant NFs (e.g., SMF / LMF / PCF) and communicate directly with the NFs. However, in some cases, the selected NFs may need to know the existence of the selected AMF or other NFs. For example, the SMF may need to communicate with the AMF to subscribe to the mobility-related EventExposure service. Therefore, a process is needed to ensure that the selected NFs are aware of the existence of the selected AMF or other NFs.

[0090] Regarding the second question, for NAS messages in the UL, the service-based RAN may need to know which NF (e.g., AMF / SMF / LMF) the NAS message from the UE is to be forwarded to. In a traditional architecture, when the RAN receives a NAS message from the UE in an RRC message, the RAN will always forward it to the AMF, and the AMF is responsible for interpreting and understanding whether the NAS message is used in other NFs (e.g., SMF / LMF). Therefore, when the RAN is responsible for forwarding the NAS message to the relevant NF, the RRC message from the UE may need to include a header / indication.

[0091] Therefore, this disclosure proposes a technical solution for supporting NF determination in a service-based RAN. In some embodiments of this technical solution, at the access network device (e.g., in the RAN), a message associated with an NF type in the core network is received from the UE, and a first NF of the NF type used to serve the UE in the core network is determined. By implementing the example embodiments of this disclosure, the service-based RAN can know the selected NFs used to serve the UE and communicate directly with these NFs.

[0092] Since this disclosure pertains to 6G evolution (e.g., 6G computing power networks), the names of each network function are for illustrative purposes only. In 6G standardization, network functions providing the same functionality / service may be named differently. In this disclosure, it is assumed that the aforementioned network functions provide at least the following related functions / services.

[0093] The Network Repository Function (NRF) supports the following functions: service discovery of NRF services and their endpoint addresses by the NRF bootstrapping service; service discovery function; receiving NF discovery requests from NF instances or SCPs and providing the NF instances (discovered) information to the NF instances or SCPs; maintaining NF profiles of available NF instances and their supporting services; maintaining SCP profiles of available SCP instances; supporting SCP discovery by SCP instances; notifying subscribed NF service consumers or SCPs about newly registered / updated / deregistered NF and SCP instances and their potential NF services; and maintaining the health status of NFs and SCPs.

[0094] Access and Mobility Management (AMF) includes the following functions. Some or all of the AMF functions can be supported in a single instance of the AMF. These functions may include: registration management; connection management; reachability management; and mobility management. UE mobility event notification.

[0095] The Session Management Function (SMF) includes the following functions. Some or all of the SMF functions can be supported in a single instance of the SMF. These functions may include: session management, such as session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes; selection and control of UP functions, including controlling the UPF to proxy ARP or IPv6 neighbor discovery, or forwarding all ARP / IPv6 neighbor request traffic to the SMF for Ethernet PDU sessions; configuring traffic offloading at the UPF to route traffic to appropriate destinations; terminating the interface with policy control functions; terminating the SM portion of NAS messages; and downlink data notification.

[0096] The Radio Access Network (RAN) carries the following functions. Some or all of the RAN functions / services can be supported in a single RAN node. These functions may include: functions for radio resource management: radio bearer control, radio admission control, connection mobility control, dynamic allocation (scheduling) of resources to the UE in both uplink and downlink; IP and Ethernet header compression, uplink data decompression, data encryption and integrity protection; connection establishment and release; scheduling and transmission of paging messages; scheduling and transmission of system broadcast information (originating from AMF or OAM); and measurement and measurement report configuration for mobility and scheduling.

[0097] In addition, the Location Management Function (LMF) supports location-related functions. The Sensing Function (SF) supports sensing-related functions.

[0098] Figure 4An example signaling procedure 400 for determining NFs in a service-based RAN according to various aspects of this disclosure is illustrated. At 410, UE 104 may send a message 412 associated with an NF type in the core network to access network device 402 (e.g., RAN node). Therefore, at 414, access network device 402 can receive message 412 associated with an NF type in the core network from UE 104.

[0099] In some embodiments, message 412 includes messages destined for NFs in the core network (e.g., Non-Access Stratum (NAS) messages), and wherein the messages destined for NFs in the core network are carried within messages to base stations (e.g., Radio Resource Control (RRC) messages). In some embodiments, the messages destined for NFs in the core network include one of the following: a Protocol Data Unit (PDU) session establishment request message for an NF responsible for service management; a location service request message for an NF responsible for location management; and a sensing service request message for an NF responsible for sensing-related functions.

[0100] In some embodiments, the message sent to the base station further includes an indication for indicating the destination NF. Furthermore, in some embodiments, the indication specifies one of the following: the type of the NF in the form of an enumerated value; the type of the message in the form of an enumerated value; the protocol identifier of the message in the form of a bitmap; or the identifier (ID) or index of the NF in the form of an integer value.

[0101] For example, the UE generates a NAS message and sends it to the RAN, which is carried in an RRC message. The RRC message also indicates the destination NF. The NAS message can be, for example, a PDU session establishment request message for the SMF; a location service request message for the LMF; or a sensing service request message for the SF.

[0102] For example, upon receiving an RRC message containing a NAS message, the RAN first determines whether the destination NF already exists or is being selected / prepared. If not, the RAN generates and sends a message (e.g., Namf_NFSelection_Request / Subscribe) to the AMF to request the AMF to select one or more NFs for the RAN / UE. This message may also include, for example, the requested NF type (e.g., SMF / LMF / SF), the requested service, and the UE ID (e.g., SUPI).

[0103] In some embodiments, at 416, the access network device 402 may send a request 418 to a second NF 406 (e.g., AMF) in the core network for determining the type of the first NF used to serve UE 104, wherein the second NF 406 is responsible for UE access and mobility management.

[0104] Alternatively, in some embodiments, access network device 402 may send a request to a third NF (e.g., NRF) in the core network for a first NF to determine the NF type for serving UE 104, wherein the third NF is responsible for storing information related to NFs in the core network. For example, the RAN requests NF candidates from the NRF via an NF discovery service from the NRF, such as via an Nnrf_NFDiscovery_Request (and / or Nnrf_NFDiscovery_Request_Response) message. In some embodiments, the request includes one of the following: NF type; the requested service; or UE identifier (ID).

[0105] Therefore, at 420, the second NF 406 can receive request 418 from access network device 402. Subsequently, at 422, the second NF 406 can determine the first NF 404 of NF type. In some embodiments, the second NF 406 can send a message associated with the NF type to the first NF 404 of NF type; and receive a response to that message from the first NF 404.

[0106] Subsequently, at 424, the second NF 406 can send information 426 related to the first NF of the NF type to the access network device 402. In some embodiments, the information 426 includes one of the following: NF type; identifier (ID) of the NF instance; Internet Protocol (IP) address or fully qualified domain name (FQDN) of the NF instance; or a list of service instances associated with the NF instance, wherein the service instances in the service instance list are associated with one of the following: service name, NF service instance ID, or endpoint address.

[0107] Alternatively or additionally, in some embodiments, information 426 includes information related to multiple NF candidates of the NF type selected by the second NF 406 for UE 104. Therefore, in some embodiments, at 428, access network device 402 can receive information 426 related to a first NF of the NF type from the second NF 406. Thus, when access network device 402 previously sends a request to the third NF for determining a first NF of the NF type for serving UE 104, access network device 402 can receive information related to the first NF of the NF type from the third NF.

[0108] Alternatively or concurrently, in some embodiments, information 426 includes information relating to multiple NF candidates of the NF type selected by the second NF 406 for the UE 104. Therefore, the access network device 402 can select a first NF 404 of the NF type from the multiple NF candidates.

[0109] When access network device 402 previously sends a request to a third NF to determine a first NF of NF type for serving UE 104, the information associated with the first NF of NF type includes information related to multiple NF candidates of NF type discovered by the third NF for UE 104. Therefore, access network device 402 can select the first NF 404 of NF type from multiple NF candidates. For example, the RAN makes the NF selection decision and sends a NAS message to the selected NF, while the NRF only provides discovery services and does not provide selection services.

[0110] In some embodiments, information related to a first NF 404 of NF type is included in information related to NFs of at least one NF type. For example, the AMF selects an NF based on a request from the RAN. The AMF then generates a response message (e.g., Namf_NFSelection_Response / Notify) and sends it back to the RAN. For example, this message may also contain one or a list of the following: NF type; NF instance ID; IP address or FQND of the NF instance; a list of service instances, each associated with a service name, NF service instance ID, and optional endpoint address.

[0111] At 430, access network device 402 can determine the first NF of type NF in the core network used to serve UE 104. Subsequently, at 432, access network device 402 can send message 434 to the first NF 404 of type NF. Therefore, at 436, the first NF 404 can receive message 434 from access network device 402. For example, based on the information of the selected NF, the RAN will send a NAS message (previously received from the UE) to the corresponding NF, for example via: Nsmf_PDUSession_CreateSMContext_Request; Nlmf_Location_DetermineLocation_Request; or Nsf_Sensing_Request.

[0112] In some embodiments, at 438, the first NF 404 may send a response 440 to the access network device 402 in response to message 434, wherein the response 440 includes information related to the first NF 404. Therefore, at 442, the access network device 402 may receive the response 440 to message 434 from the first NF 404, wherein the response 440 includes information related to the first NF 404. For example, the RAN may receive the response message from the NF via, for example, Nsmf_PDUSession_CreateSMContext_Response; Nlmf_Location_DetermineLocation_Response; or Nsf_Sensing_Response.

[0113] In some embodiments, at 444, access network device 402 may forward response 446 to UE 104. Therefore, at 448, UE 104 may receive response 446 to message 412 from access network device 402, wherein the response includes information related to the first NF 404. In some embodiments, this information includes one of the following: an identifier (ID) of the NF instance; or an Internet Protocol (IP) address or Fully Qualified Domain Name (FQDN) of the NF instance. For example, the RAN will further forward a NAS message to the UE, which is carried in a RAN message, such as in a DLInformationTransfer IE. The same RRC message may also contain ID or address information about the selected NF. Therefore, the UE may indicate the ID or address of the selected NF in future UL NAS message transmissions.

[0114] Furthermore, in some embodiments, access network device 402 can receive updated information related to a first NF of NF type from second NF 406, or updated information related to multiple NF candidates of NF type selected by second NF 406 for UE 104. For example, AMF may update the selected NF information to RAN in the future, for example, via a Namf_NFSelection_Notify message. This message may also contain the aforementioned information. Updates to the selected NF information may be based on previously received subscription messages.

[0115] Furthermore, in some embodiments, when a first NF 404 of NF type is selected from a plurality of NF candidates discovered by a third NF, the access network device 402 may receive a request from the first NF 404 of NF type for providing information related to another NF, which is selected by the access network device 402 from a plurality of NF candidates; and send the information related to the other NF to the first NF 404.

[0116] For example, an NF that has been selected to serve the RAN / UE can generate and send a message (e.g., an Nran_NFInfo_Request / Subscribe message) to the RAN to query information about another selected NF. For instance, an SMF can request the RAN to provide the UE with information about a selected AMF. This message may also include the UE ID (e.g., SUPI) and the type of NF of interest. The RAN will then generate a message (e.g., an Nran_NFInfo_Response / Notify message) and send it back to the NF, providing the requested information such as the NF type, NF instance ID, the FQDN of the NF instance, or (multiple) IP addresses. In one example, an SMF may be interested in knowing which AMF serves a particular UE, and the SMF can then communicate directly with the AMF and retrieve information related to UE mobility.

[0117] Furthermore, in some embodiments, when the access network device 402 is the first access network device, and during the handover process of the UE 104 from the first access network device to the second access network device, the access network device 402 may send information related to the first NF 404 or information related to the second NF to the second access network device.

[0118] Alternatively or concurrently, in some embodiments, when access network device 402 is the first access network device, UE 104 is the first UE, and during the handover process of the second UE from the second access network device to the first access network device, access network device 402 can receive information related to a first NF serving the second UE or information related to a second NF serving the second UE from the second access network device. For example, if the source RAN and the target RAN have a direct connection, the NF information can be sent by the source RAN to the target RAN via a handover request message (e.g., Nran_Handover_Request).

[0119] Alternatively or alternatively, for example, in one possible scenario, the source RAN may only notify the target RAN of the NF information regarding the selected AMF. Then, after the target gNB notifies the AMF of the handover completion (e.g., Namf_Handover_Notify or Namf_PathSwitch_Request), the AMF provides the target gNB with additional NF information.

[0120] Alternatively, in some embodiments, when access network device 402 is the first access network device, UE 104 is the first UE, and during the handover process of the second UE from the second access network device to the first access network device, access network device 402 can receive information related to the NF serving the second UE from the second NF serving the second UE. For example, if the source RAN and the target RAN are not directly connected, the source RAN can request the AMF to assist in the handover, and the AMF can generate and send a handover request message to the target RAN, which will contain the selected NF information (other than the AMF).

[0121] Regarding the service-based NF determination in the RAN as proposed in this disclosure, two options can be supported. For option 1, the AMF still selects the relevant NF. That is, the RAN requests the AMF to select the required NF (such as...). Figure 5 and Figure 6 (As shown). Furthermore, for option 2, the RAN will select the relevant NF. That is, the RAN itself selects the required NF (such as...). Figure 7 (As shown).

[0122] For Option 1, after the registration and service request process (where the RAN selects the AMF), when the RAN receives a NAS message from the UE indicating a destination NF that is not yet ready, the service-based RAN will trigger a process to the AMF via the service-based interface to request NF selection / discovery. After the AMF selects / discovers the corresponding NF and sends the relevant information to the RAN, the RAN will communicate directly with the selected NF without the AMF's involvement. The AMF in this option supports network function selection / discovery services for RAN nodes / functions.

[0123] Figure 5 An example process 500 for determining an NF in a service-based RAN according to various aspects of this disclosure is illustrated, wherein RAN 501 requests AMF 502 to select a desired NF, and AMF 502 selects / discovers an NF for the UE / RAN based on an explicit request from RAN 501. Figure 5 In this context, it is assumed that RAN 501 has selected 508 AMF 502 to serve UE 104 during the UE registration process and service request process.

[0124] At 510, UE 104 generates a NAS message and sends it to RAN 501, which is carried in an RRC message. As explained further below, the RRC message also indicates the destination NF. The NAS message can be, for example, a) a PDU session establishment request message for SMF; b) a location service request message for LMF; or c) a sensing service request message for SF.

[0125] At point 520, after receiving an RRC message containing a NAS message, RAN 501 first determines whether the destination NF already exists or is being selected / prepared. If not, RAN 501 generates and sends a message (e.g., Namf_NFSelection_Request / Subscribe) to AMF 502 to request AMF 502 to select one or more NFs for the RAN / UE. This message may also include, for example, the requested NF type (e.g., SMF / LMF / SF), the requested service, and the UE ID (e.g., SUPI).

[0126] At 522, AMF 502 selects NFs 503-505 based on the request from RAN. Then, at 530, AMF 502 generates a response message (e.g., Namf_NFSelection_Response / Notify) and sends it back to RAN 501. For example, this message may also contain one or a list of the following: a) NF type; b) NF instance ID; c) IP address or FQND of the NF instance; d) a list of service instances, each associated with a service name, NF service instance ID, and optional endpoint address.

[0127] At 540, based on the information of the selected NF 503-505, RAN 501 will send a NAS message (received from the UE in 510) to the corresponding NF 503-505, for example via: a) Nsmf_PDUSession_CreateSMContext_Request; b) Nlmf_Location_DetermineLocation_Request; c) Nsf_Sensing_Request.

[0128] At 550, RAN 501 may receive response messages from NF 503-505, for example, via the following: a) Nsmf_PDUSession_CreateSMContext_Response; b) Nlmf_Location_DetermineLocation_Response; c) Nsf_Sensing_Response.

[0129] At 560, RAN 501 will further forward the NAS message to UE 104, which is carried in a RAN message, such as in a DLInformationTransfer IE. The same RRC message may also contain ID or address information about the selected NF. UE 104 can indicate the ID or address of the selected NF in future UL NAS message transmissions.

[0130] At 570, AMF 502 can update RAN 501 with information about the selected NF in the future, for example, via a Namf_NFSelection_Notify message. This message may also include the information listed in 530. Updates to the selected NF information can be based on previously received subscription messages.

[0131] Figure 6 The illustration shows another example process 600 for determining NFs in a service-based RAN according to various aspects of this disclosure, wherein RAN 601 requests AMF 602 to select the required NFs, and by default, AMF 602 is still responsible for NAS message transmission between RAN 601 and other NFs, while AMF 602 may decide to provide RAN 601 with information about the selected NFs to enable future direct communication between RAN 601 and the NFs. Figure 6 In this context, it is assumed that RAN 601 selected 608 AMF 602 to serve UE 104 during the UE registration process and service request process.

[0132] At 610, UE 104 generates a NAS message and sends it to RAN 601, which is carried in an RRC message. As explained further below, the RRC message also indicates the destination NF. The NAS message can be, for example, a) a PDU session establishment request message for SMF; b) a location service request message for LMF; or c) a sensing service request message for SF.

[0133] At 620, after receiving an RRC message containing a NAS message, RAN 601 first determines whether the destination NF already exists or is being selected / prepared, and whether relevant information (e.g., IP address or FQDN) is available. If not, RAN 601 sends a NAS message to AMF 602 (e.g., via a Namf_NASmessage_transfer message). Messages sent to AMF 602 can also indicate the destination NF.

[0134] At 622, if an NF has not yet been selected, AMF 602 selects NFs 603-605 based on the RAN's request. Then, at 630, AMF 602 sends NAS messages to the selected destination NFs 603-605, for example via: a) Nsmf_PDUSession_CreateSMContext_Request; b) Nlmf_Location_DetermineLocation_Request; c) Nsf_Sensing_Request.

[0135] At 640, AMF 602 can receive response messages from NF 603-605, for example via: a) Nsmf_PDUSession_CreateSMContext_Response; b) Nlmf_Location_DetermineLocation_Response; c) Nsf_Sensing_Response.

[0136] At 650, AMF 602 forwards the received NAS message to RAN 601 (e.g., via an Nran_NASmessage_transfer message). Optionally, the message may also contain information related to the selected NF, such as: a) NF type; b) NF instance ID; c) IP address or FQND of the NF instance; d) a list of service instances, each associated with a service name, NF service instance ID, and optional endpoint address.

[0137] Optionally, at 660, AMF 602 can generate and send another message to RAN 601 to notify RAN 601 of the selected NF information listed in 650. If the selected NF information is provided in 650 or 660, RAN 601 can communicate directly with NFs 603-605, for example, by sending a message to the relevant IP / FQDN. Updates to the selected NF information can be based on previously received subscription messages.

[0138] At 670, RAN 601 will further forward the NAS message to UE 104, which is carried in a RAN message, such as in a DLInformationTransfer IE. The same RRC message may also contain ID or address information about the selected NF. UE 104 can indicate the ID or address of the selected NF in future UL NAS message transmissions.

[0139] For option 2 above, the service-based RAN selects the required NF based on NF information provided by the NRF (e.g., via the NF discovery service from the NRF) and initiates direct communication with the selected NF via the service-based interface. The selected NF can also query the RAN for information about other selected NFs, so that different NFs serving the same UE or RAN can also communicate directly with each other. In this option, the RAN will provide an NF query service to provide and update the selected NF information to consumers (e.g., other NFs).

[0140] Figure 7 The illustration shows another example process 700 for determining NFs in a service-based RAN according to various aspects of this disclosure, wherein RAN 701 selects the required NFs on its own.

[0141] Figure 7 Steps 710-760 in the text are similar to Figure 5 Steps 510-560 are similar, but with the following differences: First, RAN 701 requests NF candidates from NRF 702 via NF discovery service 722, for example via Nnrf_NFDiscovery_Request (and / or Nnrf_NFDiscovery_Request_Response) messages; second, RAN 701 makes an NF selection decision and sends a NAS message to the selected NFs 703-705. In other words, NRF 702 only provides discovery services and does not provide selection services.

[0142] Furthermore, at 770, NFs 703-705 that have been selected to serve the RAN / UE can generate and send a message (e.g., an Nran_NFInfo_Request / Subscribe message) to RAN 701 to query information about another selected NF. For example, SMF 703 can request RAN 701 to provide the UE with information about the selected AMF. This message may also include the UE ID (e.g., SUPI) and the type of NF of interest.

[0143] At 780, RAN 701 will generate a message (e.g., an Nran_NFInfo_Response / Notify message) and send it back to NFs 703-705 to provide the requested information, such as the NF type, NF instance ID, NF instance FQDN, or (multiple) IP addresses. In one example, SMF 703 may be interested in knowing the AMF serving a particular UE, and then SMF 703 can communicate directly with the AMF and retrieve information related to UE mobility.

[0144] Figure 8The illustration shows an example RRC indication 800 for a NAS message destination in a service-based RAN architecture according to various aspects of this disclosure. (As combined with...) Figure 8 As described above, when a UE sends a NAS message carried in an RRC message IE in the UL, a new RRC indication will be added to the RRC message IE associated with the NAS message. This new indication specifies that the NAS message should be sent by the service-based RAN to the core network function (e.g., AMF / SMF / LMF / SF) via the service-based interface. The service-based RAN will determine the destination NF based on the RRC indication, without interpreting the NAS message octet, and will forward the NAS message to the destination NF.

[0145] Assume the UE has an end-to-end NAS protocol layer with destination network functions (e.g., AMF / SMF / LMF / SF).

[0146] In some embodiments, the indication of the target core network function can be any of the following forms: 1) NF type in the enumeration value, such as AMF, SMF, LMF, SF; 2) Message type information in the enumeration value, such as session management, mobility management, location service, sensing service; 3) Protocol identifier in the bitmap, such as 00101110 indicating a 5GS session management message for SMF; 01111110 indicating a 5GS mobility management message for AMF; 00001110 indicating a location service message for LMF; 00011110 indicating a sensing service message for SF; 4) ID or index value in integer form, wherein the association between ID / index and core network function is defined in the specification or configured by the RAN; 5) Address information, such as IP address or FQDN.

[0147] In one possible scenario, the protocol identifier is the same as the protocol identifier in the NAS message. When generating the RRC message, the UE copies and pastes the NAS protocol identifier as the RRC field.

[0148] Figures 9-11 This involves transmitting information related to the selected NF during handover in a service-based RAN architecture. For example, combining... Figures 9-11 During UE handover, the target RAN will be notified of the selected NF information of the UE being handed over. For the selected AMF / SMF / LMF / UPF, the NF message can be any of the following: NF type; NF instance ID; IP address or FQND of the NF instance; and / or a list of service instances, each associated with a service name, NF service instance ID, and optional endpoint address.

[0149] like Figure 9As shown, if the source RAN 901 and the target RAN 902 have a direct connection, the source RAN 901 can send NF information to the target RAN 902 via a handover request message (e.g., Nran_Handover_Request at 910). Therefore, at 920, the target RAN 902 can send follow-up messages to (multiple) NF AMF / SMF / UPF 903.

[0150] like Figure 10 As shown, in one possible scenario, at 1010, source RAN 1001 may only notify target RAN 1002 of the NF information regarding the selected AMF 1003. Then, at 1030, after target RAN 1002 notifies AMF 1003 of the handover completion (e.g., Namf_Handover_Notify or Namf_PathSwitch_Request at 1020), AMF 1003 provides target RAN 1002 with information about other NFs. Therefore, at 1040, target RAN 1002 may send follow-up messages to (multiple) NF SMF / LMF / UPF 1004.

[0151] like Figure 11 As shown, if the source RAN 1101 and the target RAN 1102 are not directly connected, at 1110, the source RAN 1101 can request the AMF 1103 to assist in the handover, and at 1120, the AMF 1103 can generate and send a handover request message to the target RAN 1102, which will contain the selected NF information (excluding the AMF).

[0152] Therefore, as Figure 11 As further shown, at 1130, target RAN 1102 can generate Nran_Handover_Request_Acknowledge and send it to AMF 1103; and at 1140, AMF 1103 can generate Nran_Handover_Command and send it to source RAN 1101. Subsequently, at 1150, target RAN 1102 can send follow-up messages to (multiple) NF SMF / LMF / UPF 1104.

[0153] Figure 12An example of device 1200 supporting NF determination in a service-based RAN according to various aspects of this disclosure is illustrated. Device 1200 may be an example of UE 104-1 as described herein. Device 1200 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 1200 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 1202, memory 1204, transceiver 1206, and optional I / O controller 1208). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0154] Processor 1202, memory 1204, transceiver 1206, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 1202, memory 1204, transceiver 1206, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0155] In some implementations, processor 1202, memory 1204, transceiver 1206, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 1202 and memory 1204 coupled to processor 1202 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 1204 by processor 1202).

[0156] For example, according to the examples disclosed herein, processor 1202 may support wireless communication at device 1200. Processor 1202 may be configured to operate to support: components for receiving messages associated with NF types in the core network via a transceiver; components for determining a first NF of NF type in the core network for serving the UE; and components for transmitting the message to the first NF of NF type via a transceiver.

[0157] Processor 1202 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 1202 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 1202. Processor 1202 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1204) to cause device 1200 to perform various functions of this disclosure.

[0158] Memory 1204 may include random access memory (RAM) and read-only memory (ROM). Memory 1204 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1202, cause device 1200 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 1202, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 1204 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0159] I / O controller 1208 can manage the input and output signals of device 1200. I / O controller 1208 can also manage peripheral devices not integrated into device 1200. In some implementations, I / O controller 1208 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1208 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, I / O controller 1208 can be implemented as part of a processor, such as processor 1202. In some implementations, a user can interact with device 1200 via I / O controller 1208 or via hardware components controlled by I / O controller 1208.

[0160] In some implementations, device 1200 may include a single antenna 1210. However, in other implementations, device 1200 may have more than one antenna 1210 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1206 may communicate bidirectionally via one or more antennas 1210, wired or wireless links, as described herein. For example, transceiver 1206 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1206 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1210 for transmission, and demodulating packets received from one or more antennas 1210. Transceiver 1206 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0161] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 1210 for transmitting the amplified signal into the air or wireless medium.

[0162] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 1210 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0163] Figure 13An example of a processor 1300 supporting NF determination in a service-based RAN according to various aspects of this disclosure is illustrated. Processor 1300 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1300 may include a controller 1302 configured to perform various operations according to the examples described herein. Processor 1300 may optionally include at least one memory 1304, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 1300 may optionally include one or more arithmetic logic units (ALUs) 1306. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0164] Processor 1300 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1300)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0165] Controller 1302 can be configured to manage and coordinate various operations of processor 1300 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1300 to support various operations of a base station according to the examples described herein. For example, controller 1302 can operate as a control unit of processor 1300 to generate control signals for managing the operation of various components of processor 1300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0166] Controller 1302 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1304 and determine subsequent instructions(s) to be executed, enabling processor 1300 to support various operations according to the examples described herein. Controller 1302 can be configured to track the memory addresses of instructions associated with memory 1304. Controller 1302 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1302 can be configured to interpret instructions and determine control signals to be output to other components of processor 1300, enabling processor 1300 to support various operations according to the examples described herein. Additionally or alternatively, controller 1302 can be configured to manage data flow within processor 1300. Controller 1302 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1300.

[0167] Memory 1304 may include one or more caches (e.g., memory local to or included in processor 1300, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 1304 may reside within or on the processor chipset (e.g., locally to processor 1300). In some other implementations, memory 1304 may reside outside the processor chipset (e.g., remotely from processor 1300).

[0168] Memory 1304 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1300, cause processor 1300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 1302 and / or processor 1300 may be configured to execute computer-readable instructions stored in memory 1304 to cause processor 1300 to perform various functions. For example, processor 1300 and / or controller 1302 may be coupled to or coupled to memory 1304, and processor 1300, controller 1302, and memory 1304 may be configured to perform the various functions described herein. In some examples, processor 1300 may include multiple processors, and memory 1304 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0169] One or more ALU 1306s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1306s may reside within or on a processor chipset (e.g., processor 1300). In some other implementations, one or more ALU 1306s may reside outside the processor chipset (e.g., processor 1300). One or more ALU 1306s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1306s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1306s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 1306 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1306 to handle conditional operations, comparisons, and bitwise operations.

[0170] Based on the examples disclosed herein, processor 1300 may support wireless communication. Processor 1300 may be configured or operable to support: components for receiving messages associated with NF types in the core network via a transceiver; components for determining a first NF of NF type in the core network for serving the UE; and components for transmitting the message to the first NF of NF type via a transceiver.

[0171] Figure 14 A flowchart illustrating method 1400 for determining an NF in a service-based RAN according to various aspects of this disclosure is provided. Operation of method 1400 may be implemented by the devices or components thereof described herein. For example, operation of method 1400 may be performed by access network device 402 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0172] At 1410, the method may include receiving a message associated with an NF type in the core network. The operation at 1410 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1410 can be found in the references. Figure 1 The aforementioned device is used to perform this action.

[0173] At 1420, the method may include determining a first NF of type NF in the core network used to serve the UE. The operation at 1420 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1420 may be derived from references... Figure 1The aforementioned device is used to perform this action.

[0174] At 1430, the method may include sending the message to the first NF of type NF. The operation at 1430 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1420 can be obtained from references. Figure 1 The aforementioned device is used to perform this action.

[0175] Figure 15 A flowchart illustrating method 1500 for determining an NF in a service-based RAN according to various aspects of this disclosure is provided. Operation of method 1500 may be implemented by the device or components thereof described herein. For example, operation of method 1500 may be performed by a second NF 406 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0176] At 1510, the method may include: receiving a request for a first NF to determine the NF type used to serve the UE. The operation at 1510 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1510 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0177] At 1520, the method may include: determining the first NF of type NF. The operation at 1520 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1520 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0178] At 1530, the method may include sending information related to the first NF of type NF. The operation at 1530 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1530 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0179] Figure 16 A flowchart illustrating method 1600 for determining an NF in a service-based RAN according to various aspects of this disclosure is provided. Operation of method 1600 may be implemented by the device or components thereof described herein. For example, operation of method 1600 may be performed by UE 104 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the described functions.

[0180] At 1610, the method may include sending a message associated with an NF type in the core network. The operation of 1610 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1610 can be found in the references. Figure 1 The aforementioned device is used to perform this action.

[0181] At 1620, the method may include: receiving a response to the message, wherein the response includes information related to the first NF. The operation at 1620 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1620 may be derived from references. Figure 1 The aforementioned device is used to perform this action.

[0182] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0183] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0184] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0185] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0186] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0187] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An access network device, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: Receive messages associated with network function (NF) types in the core network from the user equipment (UE) via the transceiver; Determine the first NF of the NF type in the core network used to serve the UE; and The message is sent to the first NF of the NF type via the transceiver.

2. The access network device according to claim 1, wherein the processor is further configured to: Receive a response to the message from the first NF via the transceiver, wherein the response includes information related to the first NF; and The response is forwarded to the UE via the transceiver.

3. The access network device according to claim 1, wherein the first NF determining the NF type includes: The transceiver sends a request to the second NF or the third NF in the core network to determine the type of the first NF, wherein the second NF is responsible for UE access and mobility management, and wherein the third NF is responsible for storing information related to the NFs in the core network; as well as Information related to the first NF of the NF type is received from the second NF or the third NF via the transceiver.

4. The access network device according to claim 3, wherein the request includes one of the following: The NF type; The requested service; or UE identifier (ID).

5. The access network device according to claim 3, wherein the information includes one of the following: The NF type; The identifier (ID) of an NF instance; The Internet Protocol (IP) address or Fully Qualified Domain Name (FQDN) of the NF instance; or A list of service instances associated with the NF instance, wherein each service instance in the list is associated with one of the following: service name, NF service instance ID, or endpoint address.

6. The access network device of claim 3, wherein the information related to the first NF of the NF type is included in the information related to at least one NF of the NF type.

7. The access network device according to claim 6, wherein the information associated with at least one NF of the NF type includes: Information related to multiple NF candidates of the NF type selected by the second NF for the UE or discovered by the first NF for the UE, and the processor is further configured to: Select the first NF of the NF type from the plurality of NF candidates.

8. The access network device according to claim 3, wherein the processor is further configured to: The transceiver receives, via the second NF, updated information related to a first NF of the NF type or updated information related to multiple NF candidates of the NF type selected by the second NF for the UE.

9. The network device of claim 7, wherein the first NF of the NF type is selected from the plurality of NF candidates discovered by the third NF, and the processor is further configured to: The transceiver receives, via the transceiver, a request from the first NF of the NF type for providing information related to another NF, which is selected by the access network device from a plurality of NF candidates; and The information related to the other NF is sent to the first NF via the transceiver.

10. The access network device of claim 1, wherein the message includes a message destined for an NF in the core network, and wherein the message destined for an NF in the core network is carried in a message destined for a base station.

11. The access network device of claim 10, wherein the message sent to the NF in the core network includes one of the following: A session establishment request message is sent to the Protocol Data Unit (PDU) session of the NF responsible for service management; Location service request messages for the NF responsible for location management; as well as Sensing service request message for the NF responsible for sensing-related functions.

12. The access network device of claim 10, wherein the message sent to the base station further includes an indication for indicating the destination NF.

13. The access network device of claim 12, wherein the indication specifies one of the following: The type of the NF in the form of enumeration values; The message type is in the form of an enumeration value; The protocol identifier of the message in bitmap form; or The identifier (ID) or index of the NF in integer form.

14. The access network device according to claim 1, wherein the access network device is a first access network device, and the processor is further configured to: During the handover process from the first access network device to the second access network device, the UE sends information related to the first NF or information related to the second NF to the second access network device via the transceiver.

15. The access network device according to claim 1, wherein the access network device is a first access network device, the UE is a first UE, and the processor is further configured to: During the handover process from the second access network device to the first access network device, the second UE receives information related to the first NF serving the second UE or information related to the second NF serving the second UE from the second access network device via the transceiver.

16. The access network device according to claim 1, wherein the access network device is a first access network device, the UE is a first UE, and the processor is further configured to: During the handover process from the second access network device to the first access network device, the second UE receives information related to the first NF serving the second UE from the second NF serving the second UE via the transceiver.

17. An apparatus for performing network functions, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: The transceiver receives a request from the access network device for determining a first NF for serving a network function (NF) type for a user equipment (UE); Determine the first NF of the NF type; as well as The transceiver sends information related to the first NF of the NF type to the access network device.

18. A user equipment, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: The transceiver sends messages associated with network function (NF) types in the core network to the access network equipment; and The transceiver receives a response to the message from the access network device, wherein the response includes information related to the first NF.

19. The user equipment of claim 18, wherein the message sent to the base station further includes an indication for indicating the destination NF.

20. A method performed by an access network device, the method comprising: Receive messages associated with network function (NF) types in the core network from the user equipment (UE); Determine the first NF of the NF type in the core network used to serve the UE; as well as Send the message to the first NF of the NF type.

Images