Capability negotiation in hybrid ran architecture

Abstract

Example embodiments of the present disclosure relate to capability negotiation in hybrid radio access network (RAN) architecture. A method includes sending, to an access and mobility management function (AMF) or a network repository function (NRF), capability information of a first device, the capability information indicating service-based architecture (SBA) capability of the first device and at least one service of the first device, the at least one service being supported via a service-based interface (SBI) based on the SBA capability; establishing a peer-to-peer (P2P) interface between the first device and the AMF; and establishing, based on the SBA capability, a SBI between the first device and a network function (NF) in a core network, wherein the NF is configured to request a service of the at least one service that is associated with the SBA capability, and the SBI enables direct communication between the first device and the NF.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and particularly to methods, apparatus, devices, and computer-readable storage media for capability negotiation in a radio access network (RAN) architecture that enables a hybrid of different communication mechanisms toward the core network (CN). Background Technology

[0002] Examples of mobile or wireless telecommunications systems can include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved LTE UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, 5G radio access technology or 5G New Radio (NR) access technology, Advanced 5G and / or 6G mobile communication technology. 5G radio systems refer to next-generation (NG) radio systems and network architectures. While most 5G network technologies are based on NR technology, 5G (or NG) networks can also be built on E-UTRAN radio. It is estimated that NR can provide bit rates of approximately 10-20 Gbit / s or higher and can support at least Enhanced Mobile Broadband (eMBB) and Ultra-Reliable Low Latency Communication (URLLC) as well as Massive Machine-Type Communication (mMTC). NR promises to provide ultra-wideband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT). Summary of the Invention

[0003] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the first apparatus to at least: transmit capability information of the first apparatus to an Access and Mobility Management Function (AMF) or a Network Repository Function (NRF), the capability information indicating the first apparatus's Service-Based Architecture (SBA) capabilities and at least one service of the first apparatus, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI); establish a peer-to-peer (P2P) interface between the first apparatus and the AMF; and establish an SBI between the first apparatus and a Network Function (NF) in the core network based on the SBA capabilities, wherein the NF is configured to request the service associated with the SBA capabilities among the at least one service, and the SBI enables direct communication between the first apparatus and the NF.

[0004] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the second apparatus to at least: receive capability information of a Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; send a first establishment response to the RAN node, indicating whether the RAN node's SBA capabilities are supported, based on a determination received from the RAN node in a first establishment request of the capability information, to establish a peer-to-peer (P2P) interface between the RAN node and the second apparatus; and send a second service response, including the RAN node's capability information, to the NF, based on a determination received from the RAN node in a first service response to a first service request for a Network Function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capabilities among the at least one services.

[0005] In a third aspect of this disclosure, a third apparatus is provided. The third apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the third apparatus to at least: receive from a Radio Access Network (RAN) node or an Access and Mobility Management Function (AMF) a Network Function (NF) registration request for at least one service registered at the third apparatus by the RAN node, wherein the at least one service is supported based on the RAN node's Service-Based Architecture (SBA) capability via a Service-Based Interface (SBI); and send an NF registration response to the RAN node or AMF to the NF registration request.

[0006] In a fourth aspect of this disclosure, a fourth apparatus is provided. The fourth apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the fourth apparatus to at least: send a service request for a service to an Access and Mobility Management Function (AMF); receive a service response from the AMF, the service response including capability information of a Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; and, based on the determination that the at least one service includes the requested service, establish an SBI between the third apparatus and the RAN node, wherein the SBI enables direct communication between the third apparatus and the RAN node.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: sending capability information of a first device to an Access and Mobility Management Function (AMF) or a Network Repository Function (NRF), the capability information indicating a Service-Based Architecture (SBA) capability of the first device and at least one service of the first device, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capability; establishing a peer-to-peer (P2P) interface between the first device and the AMF; and establishing an SBI between the first device and a Network Function (NF) in the core network based on the SBA capability, wherein the NF is configured to request a service associated with the SBA capability from the at least one service, and the SBI enables direct communication between the first device and the NF.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving capability information from a Radio Access Network (RAN) node, the capability information indicating a Service-Based Architecture (SBA) capability of the RAN node and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capability; sending a first establishment response to the RAN node, indicating whether the SBA capability of the RAN node is supported, based on a determination received from the RAN node in a first establishment request of the capability information, to establish a peer-to-peer (P2P) interface between the RAN node and a second device; and sending a second service response, including the capability information of the RAN node, to the NF, based on a determination received from the RAN node in a first service response to a first service request for a Network Function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capability among the at least one services.

[0009] In a seventh aspect of this disclosure, a method is provided. The method includes: receiving from a Radio Access Network (RAN) node or an Access and Mobility Management Function (AMF) a Network Function (NF) registration request for registering at a third device for at least one service of the RAN node, wherein the at least one service is supported by the RAN node's Service-Based Architecture (SBA) capability via a Service-Based Interface (SBI); and sending an NF registration response to the RAN node or AMF in response to the NF registration request.

[0010] In an eighth aspect of this disclosure, a method is provided. The method includes: sending a service request for a service to an Access and Mobility Management Function (AMF); receiving a service response from the AMF, the service response including capability information of a Radio Access Network (RAN) node, the capability information indicating a Service-Based Architecture (SBA) capability of the RAN node and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capability; and establishing an SBI between a third device and the RAN node based on the determination that the at least one service includes the requested service, according to the SBA capability of the RAN node, wherein the SBI enables direct communication between the third device and the RAN node.

[0011] In a ninth aspect of this disclosure, a first apparatus is provided. The first apparatus includes components for transmitting capability information of the first apparatus to an Access and Mobility Management Function (AMF) or a Network Repository Function (NRF), the capability information indicating a Service-Based Architecture (SBA) capability of the first apparatus and at least one service of the first apparatus, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capability; components for establishing a peer-to-peer (P2P) interface between the first apparatus and the AMF; and components for establishing an SBI between the first apparatus and a Network Function (NF) in the core network based on the SBA capability, wherein the NF is configured to request a service associated with the SBA capability from at least one service, and the SBI enables direct communication between the first apparatus and the NF.

[0012] In a tenth aspect of this disclosure, a second apparatus is provided. The second apparatus includes components for receiving capability information of a Radio Access Network (RAN) node from the RAN node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; components for sending a first establishment response to the RAN node, indicating whether the RAN node's SBA capabilities are supported, to establish a peer-to-peer (P2P) interface between the RAN node and the second apparatus, based on a determination received from the RAN node in a first establishment request of the capability information; and components for sending a second service response, including the RAN node's capability information, to the NF based on a determination received from the RAN node in a first service response to a first service request for a Network Function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capabilities among the at least one services.

[0013] In the eleventh aspect of this disclosure, a third apparatus is provided. The third apparatus includes components for receiving, from a Radio Access Network (RAN) node or an Access and Mobility Management Function (AMF), a Network Function (NF) registration request for registering at the third apparatus at at least one service of the RAN node, wherein the at least one service is supported by the RAN node’s Service-Based Architecture (SBA) capability via a Service-Based Interface (SBI); and components for sending an NF registration response to the RAN node or AMF to the NF registration request.

[0014] In a twelfth aspect of this disclosure, a fourth apparatus is provided. The fourth apparatus includes components for sending a service request for a service to an Access and Mobility Management Function (AMF); components for receiving a service response from the AMF, the service response including capability information of a Radio Access Network (RAN) node indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; and components for establishing an SBI between the third apparatus and the RAN node based on the determination of at least one service including the requested service and the RAN node's SBA capabilities, wherein the SBI enables direct communication between the third apparatus and the RAN node.

[0015] In a thirteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fifth aspect.

[0016] In a fourteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a sixth aspect.

[0017] In a fifteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a seventh aspect.

[0018] In a sixteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to an eighth aspect.

[0019] It should be understood that the summary portion 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

[0020] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0021] Figure 1 The illustration shows an example communication environment in which example embodiments of the present disclosure may be implemented;

[0022] Figures 2A-2E The illustration shows an example signaling flow for capability negotiation in a hybrid RAN architecture according to some example embodiments of the present disclosure;

[0023] Figure 3 The illustration shows a signaling flow for a RAN node to send a configuration update according to some example embodiments of the present disclosure;

[0024] Figures 4A-4B The illustration shows an example signaling flow for sending configuration updates in the core network according to some example embodiments of the present disclosure;

[0025] Figure 5 The illustration shows a flowchart of a method implemented at a first device according to some exemplary embodiments of the present disclosure;

[0026] Figure 6 The illustration shows a flowchart of a method implemented at a second device according to some exemplary embodiments of the present disclosure;

[0027] Figure 7 The illustration shows a flowchart of a method implemented at a third device according to some exemplary embodiments of the present disclosure;

[0028] Figure 8 The illustration shows a flowchart of a method implemented at a fourth device according to some other exemplary embodiments of the present disclosure;

[0029] Figure 9 A simplified block diagram of a device suitable for implementing exemplary embodiments of the present disclosure is illustrated; and

[0030] Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is illustrated.

[0031] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0032] The principles of this disclosure will now be described with reference to some exemplary 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 constitute any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0033] 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.

[0034] In this disclosure, references to "an embodiment," "embodiment," and "example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will understand that, whether explicitly described or not, combining it with other embodiments to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0035] It should be understood that although the terms "first," "second," etc., preceding the nouns(s) herein may be used to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns(s). For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may 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.

[0036] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0037] As used herein, unless explicitly stated otherwise, “responding to A” does not mean that the step is performed immediately after “A” occurs, but rather that the step may include one or more intermediate steps.

[0038] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein also include the plural forms unless the context clearly indicates otherwise. Further understanding, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” as 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.

[0039] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including digital signal processors), software, and memory (including multiple memory), which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0040] The definition of "circuit system" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors) or portions thereof, and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0041] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), 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 of 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), sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems that can be utilized to embody the nature of this disclosure. The scope of this disclosure should not be construed as limited to the systems described above.

[0042] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. A network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a Radio Access Backhaul (WAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN), or a non-terrestrial network device (such as satellite network equipment, low Earth orbit (LEO) satellites and geostationary orbit (GEO) satellites, aircraft network equipment, etc.), depending on the terminology and technology applied. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes: the mobile terminal (IAB-MT) portion, which behaves like a UE to the parent node, and the DU portion of the IAB node, which behaves like a base station to the next-hop IAB node.

[0043] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (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 (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0044] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including time-domain resources, frequency-domain resources, spatial-domain resources, code-domain resources, or any other combination of time-domain resources, frequency-domain resources, spatial-domain resources, and / or code-domain resources that enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0045] Figure 1 An example communication environment 100 in which example embodiments of the present disclosure may be implemented is shown. For example... Figure 1 As shown, the communication environment 100 may involve one or more RAN nodes 110-1 and 110-2, through which terminal devices (e.g., UEs) can obtain access to the communication system. RAN nodes 110-1 and 110-2 may be collectively referred to as RAN node 110 or individually. It should be understood that although two RAN nodes are illustrated, there may be any suitable number of RAN nodes in the RAN of the communication environment 100.

[0046] The communication environment 100 may also involve a core network (CN), which may include network functions (NFs), such as Access and Mobility Management Functions (AMF) 120. AMF 120 may be configured to provide various functions related to security and access management and authorization for terminal devices (e.g., UEs). The CN may also include a Session Management Element (SMF) 135, which is configured to implement session management functions within the CN. SMF 135 is also configured to interact with a decoupled data plane, create, update, and delete Protocol Data Unit (PDU) sessions, and utilize User Plane Functions (UPFs) to manage session contexts for terminal devices (e.g., UEs).

[0047] The CN may also include a Network Repository Function (NRF) 130. The NRF 130 acts as a central repository, maintaining information about available network functions and services within the core network or radio access network. The NRF 130 allows network functions and services to register their capabilities and addresses during network initialization or upon emergence. The NRF 130 also allows network functions and services to update their registered capabilities and addresses at any time during network operation. Each network function provides the NRF 130 with information about its capabilities, supported features, and available resources, which may be in the form of a network function profile. This information is used for service discovery and dynamic network function selection. Therefore, the NRF 130 can maintain an up-to-date repository of network function information, enabling dynamic service discovery. When a service request is issued, the NRF identifier can satisfy the appropriate network function or service for the requested service.

[0048] In some example embodiments, NRF 130 may be included in the RAN to serve as a RAN NRF. In this case, NRFs may exist in both the CN and the RAN.

[0049] The CN can include other NFs, such as NF 140-1, 140-2, and 140-3 (collectively or individually referred to as NF 140 or CN NF140). These NFs can be configured to provide certain services and / or services that may require RAN node 110. NF 140 can provide services such as network slice management, policy and accounting rules, authentication and authorization, etc.

[0050] In some example scenarios, the NF 140 can receive and transmit user plane data from and to RAN nodes (such as gNodeBs (gNBs)) to support data services for the UE. In some example scenarios, the NF 140 can exchange control signaling with RAN node 110 to manage radio resources, perform handovers, and maintain network connectivity. In some example scenarios, the NF 140 can consume services provided by the RAN node, which provides information about the radio environment, such as neighbor cell information and radio link status. In some other scenarios, RAN node 140 can provide the NF 140 with auxiliary information for mobility procedures, including measurement and handover decisions. These interactions between the NF and RAN nodes are crucial for the seamless operation of the communication system, ensuring efficient resource management, optimal user experience, and reliable service delivery.

[0051] It should be understood that Figure 1 The number of network nodes and terminal devices depicted is for illustrative purposes and does not imply any limitation. The communication environment 100 may include any suitable number of network nodes and terminal devices.

[0052] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), 5G, and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), FDD, TDD, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0053] The current 5G RAN-CN architecture assumes a peer-to-peer (P2P) interface between the RAN node (e.g., gNB or CU control plane CU-CP) and the core network (e.g., AMF), where all signaling messages should pass through the AMF, even if they are not sent to the AMF itself, such as session management-related signaling. The P2P interface is based on the Next Generation Application Protocol (NGAP) for the application layer and the Flow Control Transport Protocol (SCTP) for the transport layer.

[0054] In some scenarios, introducing a RAN-CN service-based architecture (SBA) to provide service-based interfaces (SBIs) for future applications (sensing, analytics, etc.) can allow certain RAN nodes to communicate directly with specific CN NFs (bypassing the AMF). In hybrid scenarios, as described in this paper, SBIs can be used in parallel with P2P interfaces, allowing services to be defined only for specific use cases. RAN and CN architectures with both SBIs and P2P interfaces are referred to as "hybrid RAN and CN architectures" or "hybrid scenarios" in this paper.

[0055] SBI can optionally be supported by RAN nodes, such as by a set of RAN nodes. For example, as Figure 1 As shown, depending on the deployment scenario, some RAN nodes (such as RAN node 110-2) may not require SBA functionality because, in this case, corresponding services dependent on SBI are not needed or deployed. In this scenario, RAN node 110-2 can still communicate with NFs via the N2 interface using the NGAP protocol (i.e., peer-to-peer P2P interface). Other RAN nodes (such as RAN node 110-1) may need to communicate directly with certain NFs (such as NRF 130, NF 140-2, and NF 140-3) via SBI.

[0056] Currently, hybrid communication between RAN nodes and CN network functions (i.e., NFs) is not enabled. Therefore, it is unclear how NF service consumers in the CN can be informed which services the RAN node supports on the alternative SBI, and for which services to use the AMF as a relay (i.e., via the peering interface between the RAN node and the AMF). Furthermore, in hybrid scenarios, the RAN node lacks a solution to selectively populate SBA-specific services and inform CN NFs (e.g., AMF or NRFs) of RAN capabilities.

[0057] According to an example embodiment of this disclosure, a solution is provided for negotiating SBA capabilities of one or more RAN nodes in a hybrid scenario, wherein SBA may be partially or fully supported, or not supported at all. In this case, the RAN node (e.g., gNB or CU-CP) notifies the CN node (e.g., AMF) whether and which services are exposed through the RAN node's SBA capabilities. Therefore, the RAN node and CN node can negotiate which services to use for SBI and which services to use for default interfaces (e.g., core network-RAN peer interfaces). When the RAN node supports SBI and the CN node allows SBI, an SBI can be established between the RAN node and the NF that requires the services of the RAN node, allowing direct communication between the RAN node and the NF and allowing bypassing the AMF in the core network. Furthermore, the RAN node can also establish a P2P interface between RAN node 110 and AMF 120.

[0058] It should be noted that AMF is used for illustrative purposes. However, in network architectures (e.g., 6G), new network functions can be used for similar functions, such as mobility management (MM) functions. In the example embodiments of this disclosure, actions implemented by AMF can be similarly implemented at the MM function.

[0059] In some example implementations, RAN nodes can register their SBA capabilities (e.g., support for certain services, such as analytics collection, sensing, location, and / or RAN instance IDs used to access the RAN node) in the NRF. In the following, the CN network function can identify RAN nodes with SBA capabilities from the NRF.

[0060] In some example implementations, as an alternative, the CN network function can query the AMF to receive SBA-related information, such as SBA capabilities and the RAN instance ID. If a RAN node with SBA capabilities is discovered, the CN network function can communicate directly with the RAN node for the requested service.

[0061] In some example embodiments, as an alternative, the RAN node may establish a connection to the NRF to register its(multiple) identifiers and supported services via SBA capabilities, and may also establish a peer connection to the AMF in parallel to exchange messages via the AMF.

[0062] Through the example embodiments of this disclosure, a RAN node with SBA capability can communicate with certain CN NFs using SBI and with AMFs using a P2P interface.

[0063] Figures 2A-2E The illustrations depict example signaling flows 200A-200E for capability negotiation in a hybrid RAN architecture according to some example embodiments of this disclosure. Signaling flows 200A-200D may involve... Figure 1 The RAN nodes 110, AMF 120, and NRF 130 are involved, and in some example embodiments, signaling flows 200C and 200D may involve NF 140 in the core network. Signaling flows 200A-200D provide different solutions for RAN nodes to provide their SBA capabilities in the core network. Figures 2A-2E In the example embodiment, it is assumed that RAN node 110 supports SBA capabilities for at least some of its services and / or functions.

[0064] exist Figure 2A In signaling flow 200A, RAN node 110 and AMF 120 perform an interface establishment process to establish a P2P interface between RAN node 110 and AMF 120. During interface establishment, RAN node 110 sends (202) a request to AMF 120 to establish a P2P interface between RAN node 110 and AMF 120. The establishment request is to establish a P2P interface with AMF 120.

[0065] exist Figure 2A In an example embodiment, the request to initiate a P2P interface establishment request with AMF 120 can be extended to include capability information of RAN node 110, which indicates the SBA capability of RAN node 110 and at least one service of RAN node 110, which is supported by SBI based on the SBA capability.

[0066] In some example embodiments, the establishment request can be extended to include an Information Element (IE), in which RAN node 110 provides its SBA capabilities. The IE may be referred to as "RAN SBA Capability".

[0067] AMF 120 receives (204) an establishment request with capability information of RAN node 110 and sends (208) an establishment response to RAN node 110, which indicates whether the SBA capability of RAN node 110 is supported in the core network and confirms the establishment of a P2P interface between RAN node 110 and AMF 120.

[0068] RAN node 110 receives (210) an establishment response to the establishment request from AMF 120 to confirm the establishment of a P2P interface between RAN node 110 and AMF 120. In some example embodiments, the establishment response indicates whether SBA capability of RAN node 110 is supported in the core network. Typically, the P2P interface between RAN node 110 and AMF 120 is always supported, so the establishment response may indicate whether a hybrid P2P interface and SBI are supported.

[0069] A P2P interface is established between RAN node 110 and AMF 120 through a setup request and setup response. In some example embodiments, the P2P interface may be based on the Next Generation Application Protocol (NGAP) and the Flow Control Transmission Protocol (SCTP). In some example embodiments, the P2P interface between RAN node 110 and AMF 120 includes a next-generation P2P interface, also known as an NG-C interface. In some examples, the setup request may be referred to as an NG setup request, and the setup response discussed below may be referred to as an NG setup response.

[0070] In some example embodiments, if the establishment request from RAN node 110 does not include capability information about SBA capabilities, the AMF and RAN node may assume that all RAN-CN interactions will be performed via the P2P interface.

[0071] exist Figure 2A In an example embodiment, in response to receiving an establishment response from AMF 120, RAN node 110 also sends an (212) NF registration request to NRF 130 based on predetermined NRF access information. In some example embodiments, RAN node 110 may perform registration with the NRF based on an establishment response from AMF indicating that the core network supports the SBA capability of RAN node 110.

[0072] RAN node 110 can register in NRF 130 using its SBA capabilities. The NF registration request may include at least information indicating at least one service supported via SBI. The NF registration request may indicate support for certain services, such as analytics collection, artificial intelligence / machine learning (AI / ML), sensing, location, and / or the RAN instance ID used to access RAN node 110. In some example embodiments, the NF registration request may include the NF type (for RAN), the NF instance ID, the Public Land Mobile Network (PLMN) ID, and a list of services exposed via SBI.

[0073] In some example embodiments, the pre-defined access information for NRF 130 may include the NRF address and / or identifier information of the NRF (which may be an instance ID, such as a global RAN ID or a RAN NF instance ID), which may be provided to the RAN via AMF 120 in setup response 210, or configured in the RAN node by Operations, Administration and Maintenance (OAM). The RAN node can then use the NRF access information (provided by AMF 120 or configured by OAM) to enable communication with NRF 130 via SBI.

[0074] In some example embodiments, the pre-configured NRF access information for NRF 130 can be pre-configured for RAN node 110. For example, when RAN node 110 is deployed via an Operation, Administration and Maintenance (OAM) platform, the NRF Fully Qualified Domain Name (FQDN) or Internet Protocol (IP) address and Resource Locator (NRF ID) can be hard-coded at the RAN node.

[0075] In some example embodiments, AMF 120 may select (206) an NRF for RAN node 110 in response to receiving an establishment request. NRF access information for NRF 130 may be included in the establishment response sent to RAN node 110. For example, AMF 120 may include access information for a preferred NRF in the establishment response to help RAN node 110 find the best NRF to register with. AMF 120 may provide RAN node 110 with an authorization token or certificate to access the selected NRF instance. Therefore, the RAN node may receive NRF access information for NRF 130 from AMF 120 in the establishment response and may perform registration with the NRF 130 selected by AMF 120.

[0076] When AMF 120 provides NRF access information, AMF 120 may include NRF profile information about the NRF selected for RAN node 110 in the setup response. NRF 130 receives (214) an NF registration request from RAN node 110 and sends (216) an NF registration response to RAN node 110. The NF registration response indicates confirmation of the registration of the SBA capability of the RAN node in NRF 130.

[0077] RAN node 110 receives an (218) NF registration response from NRF 130. After registering the services provided based on SBA capabilities with NRF 130, RAN node 110 may establish an SBI between RAN node 110 and NF 140 in the core network, if necessary, based on SBA capabilities. NF 140 may be an NF configured to request at least one service supported by SBA capabilities. The established SBI enables the RAN node (e.g., RAN node 110-1) and NF (e.g., such as...) to... Figure 1 Direct communication between NF 140-2 or 140-3 (as shown).

[0078] In some examples, an NF registration request may include an Nnrf_NFManagement_NFRegister request, and an NF registration response may include an Nnrf_NFManagement_NFRegister response.

[0079] Although a registration process is performed, RAN node 110 can complete its registration in NRF 130 using its SBA capabilities (e.g., supporting certain services such as analytics collection, sensing, location, and / or the RAN instance ID used to access RAN node 110). After RAN node 110 registers, one or more CN NFs can identify RAN node 110 with SBA capabilities from NRF 130 and establish an SBI with RAN node 110 for direct communication.

[0080] Further reference Figure 2B .exist Figure 2B In signaling flow 200B, RAN node 110 and AMF 120 perform an interface establishment procedure to establish a P2P interface between RAN node 110 and AMF 120. RAN node 110 sends (220) a request to AMF 120 to establish the P2P interface between RAN node 110 and AMF 120. Figure 2B In an example embodiment, the establishment request includes capability information of RAN node 110, which indicates the SBA capability of the RAN node and at least one service of RAN node 110, which is supported via SBI based on the SBA capability.

[0081] AMF 120 receives (222) an establishment request with SBA capability information of RAN node 110. Unlike the example embodiment of signaling flow 200A, in the example embodiment of signaling flow 200B, AMF 120 may act as a proxy between RAN node 110 and NRF 130, wherein if RAN node 110 has the SBA capability indicated in the establishment request, AMF 120 registers RAN node 110 with NRF 130.

[0082] AMF 120 sends (224) an NF registration request to NRF 130 for RAN node 110. The NF registration request may include at least information indicating at least one service of RAN node 110 supported via SBI.

[0083] NRF 130 receives an NF registration request (226) from AMF 120 and can register at least one service of RAN node 110 supported via SBI. NRF 130 sends an NF registration response (228) to AMF 120. The NF registration response indicates confirmation of the registration of the SBA capability of the RAN node in NRF 130.

[0084] The AMF receives an NF registration response (230) from NRF 130. In response to receiving the NF registration response from the NRF, AMF 120 sends an establishment response (232) to RAN node 110, indicating whether SBA capability of RAN node 110 is supported in the core network. RAN node 110 receives an establishment response (234) from AMF 120 in response to the establishment request, thus establishing a P2P interface between RAN node 110 and AMF 120. In some example embodiments, the establishment response may indicate whether SBA capability of RAN node 110 is supported in the core network.

[0085] In some example embodiments, the establishment request from RAN node 110 to AMF 120 may be similar to the establishment request sent in signaling stream 200A, including SBA-related capability information of RAN node 110. In some example embodiments, the establishment response from AMF 120 to RAN node 110 may also be similar to the establishment request sent in signaling stream 200A, to include NRF access information about NRF 130, using which the SBA capabilities of RAN node 110 are registered.

[0086] In some example embodiments, AMF 120 may provide NRF access information to RAN node 110 and confirm successful NF registration. The NRF access information and confirmation may be indicated in the establishment response sent to RAN node 110. In some example embodiments, RAN node 110 may have already created the RAN profile required for registration at NRF 130 and indicate the NRF access information in the establishment request to AMF 120. In some example embodiments, AMF 120 may use input from RAN node 110, transform it to create a RAN profile, and send the created profile to NRF 130 for registration.

[0087] In some example embodiments, RAN node 110 may register its SBA capabilities (e.g., support for certain services, such as analysis of collection, sensing, location, and / or RAN instance IDs used to access RAN node 110) in NRF 130. Hereinafter, one or more CN NFs may identify RAN node 110 with SBA capabilities from NRF 130 and establish an SBI with RAN node 110 for direct communication.

[0088] In some example embodiments, as an alternative, the CN network function can query the AMF 120 to receive SBA-related information, such as SBA capabilities and the RAN instance ID. If a RAN node 110 supporting SBA capabilities is discovered, the CN NF can communicate directly with the RAN node 110 for the requested service. Figure 2C The signaling flow 200C illustrates such an example embodiment.

[0089] In the example embodiment of Signaling Flow 200C, it is assumed that RAN node 110 provides the same service to the core network, regardless of whether it supports SBA capabilities. In this solution, a CN NF that wants to consume RAN services can send a service request to AMF 120. The Signaling Flow 200C solution introduces a fallback mechanism to the first two mechanisms of Signaling Flows 200A and 200B when the CN NF cannot perform service discovery via NRF 130 and still uses the AMF as a proxy to transmit service requests via P2P communication established between the RAN node and the AMF.

[0090] exist Figure 2CIn signaling flow 200C, NF 140 sends a service request (240) to AMF 120. AMF 120 receives the service request (242) from NF 140 and forwards it (244) to RAN node 110. In some examples, the service request from NF 140 may be an N2 service request. Communication between AMF 120 and RAN node 110 can be conducted through a peer interface established between them (e.g., an NG-C P2P interface using NGAP messages).

[0091] RAN node 110 receives (246) a service request related to NF 140 from AMF 120. Since RAN node 110 supports SBA capabilities, it sends (248) a service response to the service request to AMF 120. RAN node 110 may provide SBA capabilities in the service response message to allow for future direct communication with CN NF 140. Where the service request corresponds to a service supported by the RAN node as part of its SBA capabilities, the service response may include capability information of RAN node 110, which may indicate the SBA capabilities of RAN node 110 and at least one service of RAN node 110 supported via SBI based on the SBA capabilities.

[0092] In some examples, if the service response from RAN node 110 does not include capability information about SBA capabilities, the AMF and RAN nodes may assume that all RAN-CN interactions will be performed via NGAP.

[0093] AMF 120 receives (250) a service response with the SBA capabilities indicated therein from RAN node 110. AMF 120 forwards (252) the service response to NF 140. The service response may also include capability information indicating the SBA capabilities of RAN node 110 and at least one service of RAN node 110, which is supported via SBI based on the SBA capabilities.

[0094] NF 140 receives a service response (254) from AMF 120, which includes capability information of RAN node 110. Therefore, NF 140 can know at least one service supported by RAN node 110 via an SBI. If needed, NF 140 can establish an SBI (256) between RAN node 110 and NF 140 in the core network based on SBA capabilities. NF 140 can be an NF configured to request at least one service supported by SBA capabilities. The established SBI enables direct communication between RAN node 110 and NF 140.

[0095] NF 140 can establish an SBI (also known as an SBA connection) with RAN node 110 (either through NRF discovery or through information sent by AMF 120 in a service response).

[0096] In some example embodiments, as an alternative, the peering and SBI establishment processes can be decoupled. RAN node 110 can perform SBI establishment with NRF 130 and peer interface establishment with AMF 120. RAN node 110 can establish a connection to NRF 130 to register its identifier(s) and the supported services associated with its SBA capabilities, and can also establish a connection to AMF 120 in parallel to exchange messages via AMF 120. RAN node 110 can provide AMF 120 with RAN access information and NRF access information corresponding to the access information registered with NRF. Figure 2D The signaling flow 200D illustration shows such an example embodiment.

[0097] exist Figure 2D In signaling flow 200D, RAN node 110 sends an (260) NF registration request to NRF 130 (which may be pre-configured to RAN node 110 or received from AMF 120). The NF registration request may include capability information of RAN node 110 indicating RAN node 110's SBA capabilities and at least one service of RAN node 110 supported via SBI based on SBA capabilities.

[0098] NRF 130 receives an NF registration request (262) from RAN node 110 and sends an NF registration response (264) to RAN node 110. The NF registration response indicates confirmation of the registration of SBA capabilities in NRF 130.

[0099] RAN node 110 receives (266) from NRF 130. With successful registration at NRF 130, RAN node 110 can discover one or more NFs in the core network and establish SBI with one or more NFs in the core network when needed to enable direct communication with these NFs without going through the peer interface via AMF 120.

[0100] RAN node 110 also sends (268) a request to AMF 120 to establish a P2P interface between RAN node 110 and AMF 120. In some example embodiments, the establishment request may include RAN node 110's access information corresponding to access information registered with the NRF, and NRF access information. AMF 120 receives (270) the establishment request from RAN node 110 and sends (272) an establishment response to RAN node 110. RAN node 110 receives (274) an establishment response from AMF 120 in response to the establishment request to confirm the establishment of a P2P interface between RAN node 110 and AMF 120.

[0101] It should be understood that in signaling flow 200D, the registration process between RAN node 110 and NRF 130, and the establishment process between RAN node 110 and AMF 120, can be executed in any suitable order. For example, the registration process can be executed first, followed by the establishment process, or vice versa. In some other examples, the registration and establishment processes can be executed in parallel.

[0102] In some example embodiments, the SBI establishment using NRF 130 may also include other information, such as one or more services supported by the RAN node based on SBA capabilities, the location of the supported services, etc. If CN NF 140 requires services(s) from RAN node 110, AMF 120 may forward RAN access information (such as the global RAN ID or RAN NF instance ID) to CN NF 140. AMF 120 may also forward NRF access information registering the SBA capabilities of the RAN node to CN NF 140. CN NF 140 can then communicate directly with RAN node 110 via SBI.

[0103] In some examples, such as Figure 2D As shown, NF 140 can send a service request (276) to AMF 120. AMF 120 receives the service request (278) from NF 140 and sends a service response (280) to NF 140. The service response may also include the RAN ID and SBI of RAN node 110. NF 140 and RAN node 110 can then establish a direct SBI (284) between them for direct communication.

[0104] In some example embodiments, NRF 130 may need to notify AMF 120 and other CN NFs 140 that RAN node 110 has registered its profile in NRF 130. In some example embodiments, RAN node 110 may have already notified AMF 120 in the setup request that it has a profile and a list of services supported based on SBA capabilities. Then, instead of sending a service request to AMF 120, CN NF 140 may discover RAN node 110 via NRF 130 before sending the service request in signaling flow 200D.

[0105] Figure 2E The signaling flow 200E shown relates to some embodiments in which the peer-to-peer and SBI establishment processes can be decoupled. In some example embodiments, operations 260 to 274 in signaling flow 200E for NF registration and for the establishment of P2P and SBI interfaces... Figure 2D The same as described in signaling flow 200D. In some example embodiments, such as Figure 2E As shown, after registration and establishment for the two interfaces, NRF 130 sends a (286) RAN Registry Notification to NF 140, and NF 140 receives a (288) RAN Registry Notification from NRF 130. In this case, NF 140 and RAN Node 110 can also establish a (290) Direct SBI between them for direct communication.

[0106] In some examples, for RAN nodes that are already operationally P2P-capable, at some point in time, the SBA capability can be used to update the RAN node to provide SBI for certain services. In some example embodiments, it is also proposed that RAN nodes can use the RAN configuration update process to notify the AMF about newly introduced SBA capabilities. This allows for the flexible and gradual introduction of new capabilities or features. Figure 3 The illustration shows a signaling flow 300 of a RAN node 110 sending a configuration update message according to some example embodiments of the present disclosure.

[0107] exist Figure 3 In the example embodiment, it is assumed that RAN node 110 does not support SBA capability when establishing a peer interface with AMF 120.

[0108] In signaling flow 300, RAN node 110 can send an establishment request (302) to AMF 120. Since RAN node 110 may not support SBA capabilities at this time, the establishment request may not include SBA-related capability information. AMF 120 can receive the establishment request (304) and send an establishment response (306) to RAN node 110. RAN node 110 receives the establishment response (308) to complete the establishment of a peer interface with AMF 120.

[0109] After the P2P interface is established between RAN node 110 and AMF 120, RAN node 110 determines (310) that it now supports SBA capabilities. In this case, RAN node 110 may send (312) configuration update information to AMF 120 via the P2P interface, indicating that RAN node 110 supports SBA capabilities. In some example embodiments, the configuration update information may include capability information of RAN node 110 indicating the SBA capabilities of RAN node 110 and at least one service of RAN node 110 supported via SBI based on SBA capabilities. In some example embodiments, the configuration update information may be RAN configuration update information used to notify one or more RAN nodes 110 of updates.

[0110] In some examples, configuration update information directed from the RAN to the AMF may include an IE indicating SBA capability. AMF 120 receives (314) the configuration update information and sends (316) an acknowledgment (ACK) of the configuration update information to RAN node 110. RAN node 110 receives (318) the acknowledgment of the configuration update information from AMF 120.

[0111] In response to the configuration update confirmation, RAN node 110 can send capability information to AMF 120 or NRF 130, according to... Figure 2A Signaling stream 200A, Figure 2B Signaling stream 200B or Figure 2D The signaling flow 200D is executed (320) SBI is established.

[0112] In some cases, the core network may initially support the SBA capability of the RAN nodes, and then subsequently not support it. The following will refer to... Figures 4A-4B This section discusses configuration updates initiated by the AMF. For example, due to performance issues or any other reason, the AMF or other core network nodes may no longer support (multiple) RAN SBA capabilities. In this case, core network entities such as the AMF can send configuration update messages to the RAN nodes.

[0113] Figures 4A-4B The illustration shows an example signaling flow for CN to send configuration updates according to some example embodiments of the present disclosure. Figures 4A-4B The signaling flows 400A and 400B can involve RAN node 110, AMF 120 and NRF 130. The RAN node has registered its SBA capability at NRF 130 and established a peer interface with AMF 120. AMF has established a peer interface with RAN node 110. NRF has the SBA registration capability of RAN node 110.

[0114] exist Figure 4A In signaling flow 400A, AMF 120 determines (402) an update regarding or affecting support for SBA capabilities, which could disable support for SBA capabilities on RAN node 110. AMF 120 sends (404) configuration update information to RAN node 110, indicating an update regarding or affecting support for SBA capabilities. This update can then trigger other actions in the RAN or AMF, which could be updating or deleting entries in the registry at the NRF. In some examples, the configuration update information may include an implicit indication that SBA capabilities are not supported, or it may include other configuration updates that could trigger failures to support SBA capabilities.

[0115] RAN node 110 receives a configuration update message (406) from AMF 120. In response to the configuration update message from AMF 120, RAN node 110 sends an NF deregistration request (408) to NRF 130 to deregister at least one service supported by RAN node 110 via SBI from NRF 130. NRF 130 receives the NF deregistration request (410) and performs the deregistration on RAN node 110. NRF 130 sends an NF deregistration response (412) to RAN node 110.

[0116] RAN node 110 receives (414) the NF deregistration response to the NF deregistration request and can therefore determine that the deregistration is complete.

[0117] RAN node 110 sends (416) an acknowledgment of the configuration update information to AMF 120. AMF 120 receives (418) the acknowledgment of the configuration update information and can therefore determine that the configuration update process is complete.

[0118] exist Figure 4B In signaling flow 400B, the AMF 120 performs the deregistration of RAN node 110 from NRF 130. AMF 120 can act as a proxy between RAN node 110 and NRF 130.

[0119] Specifically, such as Figure 4B As shown, AMF 120 determines (420) that it cannot support the SBA capability of RAN node 110. AMF 120 sends (422) configuration update information to RAN node 110, which indicates updates regarding or affecting support for the SBA capability.

[0120] RAN node 110 receives (424) configuration update information from AMF 120. In response to the configuration update information from AMF 120, RAN node 110 sends (426) an acknowledgment of the configuration update information. AMF 120 receives (428) the acknowledgment of the configuration update information and can therefore determine that the configuration update of RAN node 110 is complete.

[0121] Then, AMF 120 sends an (430) NF deregistration request to NRF 130 to deregister at least one service of RAN node 110 supported via SBI from NRF 130. NRF 130 receives the (432) NF deregistration request and performs deregistration on RAN node 110. NRF 130 sends an (434) NF deregistration response to AMF 120. By receiving the (438) NF deregistration response from NRF 130, AMF 120 can determine that the deregistration of (multiple) SBA-specific services of RAN node 110 in NRF 130 is complete.

[0122] Figure 5 A flowchart illustrating an example method 500 implemented at a first device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 500 will be described from the perspective of a first device, wherein the first device may be... Figure 1 RAN node 110 in the RAN may be included in it.

[0123] At box 510, the first device sends capability information of the first device to the Access and Mobility Management Function (AMF) or the Network Repository Function (NRF), the capability information indicating the first device's Service-Based Architecture (SBA) capability and at least one service of the first device, the at least one service being supported via SBI based on the SBA capability.

[0124] At frame 520, the first device establishes a P2P NG-C P2P interface between the first device and the AMF.

[0125] At box 530, the first device establishes an SBI between the first device and a network function NF in the core network based on the SBA capability, wherein the NF is configured to request at least one service associated with the SBA capability, and the SBI enables direct communication between the first device and the NF.

[0126] In some example embodiments, sending capability information includes sending a first establishment request to the AMF to establish a P2P interface between the first device and the AMF, the first establishment request including capability information. In some example embodiments, method 500 further includes receiving from the AMF a first establishment response to the first establishment request to establish a P2P interface between the first device and the AMF, the first establishment response indicating whether the SBA capability of the first device is supported in the core network.

[0127] In some example embodiments, the P2P interface between the first device and the AMF includes a next-generation P2P NG-C P2P interface.

[0128] In some example embodiments, method 500 further includes: in response to a first establishment response from the AMF, sending an NF registration request to the NRF based on predetermined NRF access information, wherein the NF registration request includes at least information indicating at least one service supported via the SBI; and receiving an NF registration response from the NRF.

[0129] In some example embodiments, the predetermined NRF access information includes the address or identifier information of the NRF. In some example embodiments, the predetermined NRF access information is pre-configured to the first device or received from the AMF in the first establishment response.

[0130] In some example embodiments, sending capability information includes sending a second establishment request for the SBI to the NRF, the second establishment request including the capability information. In some example embodiments, method 500 further includes receiving a second establishment response to the second establishment request from the NRF.

[0131] In some example embodiments, method 500 further includes: sending a third establishment request to the AMF for a P2P interface between the first device and the AMF, the third establishment request including an identifier of the SBI of the first device; and receiving a third establishment response from the AMF for the third establishment request to establish a P2P interface between the first device and the AMF.

[0132] In some example embodiments, method 500 further includes: receiving a service request related to the NF from the AMF; and wherein the first device is configured to send capability information by sending a service response to the service request to the AMF, the service response including the capability information.

[0133] In some example embodiments, method 500 further includes: in response to the establishment of a P2P interface between the first device and the AMF, and based on the determination that the first device supports SBA capability, sending first configuration update information to the AMF via the P2P interface, the first configuration update information indicating that the first device supports SBA capability; and receiving a first acknowledgment of the first configuration update information from the AMF, wherein capability information is sent to the AMF or the NRF.

[0134] In some example embodiments, method 500 further includes: receiving second configuration update information from the AMF, the second configuration update information indicating an update regarding or affecting support for SBA capabilities; and sending a second acknowledgment of the second configuration update information to the AMF.

[0135] In some example embodiments, method 500 further includes: in response to second configuration update information, sending an NF deregistration request to the NRF to deregister at least one service supported by the SBI from the NRF; and receiving an NF deregistration response from the NRF to the NF deregistration request.

[0136] In some example embodiments, the first device is a radio access network (RAN) node, or is included therein.

[0137] Figure 6 A flowchart illustrating an example method 600 implemented at a second device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 600 will be described from the perspective of a second device, wherein the second device may be... Figure 1 AMF 120 in it may be included in it.

[0138] At box 610, the second device receives capability information of the RAN node from the RAN node, the capability information indicating the RAN node’s service-based architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via SBI based on the SBA capabilities.

[0139] At box 620, based on the determination received from the RAN node in the first establishment request regarding capability information, the second device sends a first establishment response to the RAN node indicating whether the RAN node's SBA capability is supported, in order to establish a P2P interface between the RAN node and the second device.

[0140] At box 630, based on the determination received from the RAN node in the first service response to the first service request of the network function NF in the core network, a second service response including the capability information of the RAN node is sent to the NF, wherein the NF is configured to request at least one service associated with the SBA capability.

[0141] In some example embodiments, the first establishment response includes a Network Repository Function (NRF) identifier selected for the RAN node for registering at least one service.

[0142] In some example embodiments, method 600 further includes: in response to receiving a first establishment request including capability information from the RAN node, sending an NF registration request to the NRF for the RAN node, wherein the NF registration request includes at least information indicating at least one service supported via SBI; and receiving an NF registration response from the NRF, wherein the second means is caused to send a first establishment response to the RAN node in response to receiving the NF registration response from the NRF.

[0143] In some example embodiments, method 600 further includes: receiving a second service request from the NF requesting services from the RAN node; and in response to receiving the second service request from the NF, sending a first service request to the RAN node.

[0144] In some example embodiments, method 600 further includes: in response to the establishment of a P2P interface between the RAN node and the second device, receiving first configuration update information from the RAN node, the first configuration update information indicating that the RAN node supports SBA capability; and sending a first acknowledgment to the RAN node regarding the first configuration update information.

[0145] In some example embodiments, method 600 further includes: determining, based on an update regarding or affecting support for SBA capabilities, second configuration update information indicating an update regarding or affecting support for SBA capabilities; and receiving a second acknowledgment of the second configuration update information from the RAN node.

[0146] In some example embodiments, method 600 further includes: in response to receiving a second confirmation, sending an NF deregistration request to the NRF to deregister at least one service supported by the SBI from the NRF; and receiving an NF deregistration response from the NRF to the NF deregistration request.

[0147] In some example embodiments, the second device is an Access and Mobility Management Function (AMF), or is included therein.

[0148] Figure 7 A flowchart illustrating an example method 700 implemented at a third device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 700 will be described from the perspective of a third device, wherein the third device may be... Figure 1 The NRF 130 in the text may be included therein.

[0149] At box 710, the third device receives from a Radio Access Network (RAN) node or Access and Mobility Management Function (AMF) a Network Function (NF) registration request for at least one service registered at the third device for the RAN node, wherein the at least one service is supported via the SBA interface based on the RAN node's Service-Based Architecture (SBA) capability.

[0150] At box 720, the third device sends an NF registration response to the RAN node or AMF in response to the NF registration request.

[0151] In some example embodiments, method 700 further includes: receiving from a RAN node or AMF an NF deregistration request from a third device to deregister at least one service supported via SBI; and sending an NF deregistration response to the NF deregistration request to the RAN node or AMF.

[0152] In some example embodiments, the third device is a Network Repository Function (NRF) in the core network or RAN, or is included therein.

[0153] Figure 8 A flowchart illustrating an example method 800 implemented at a fourth device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 800 will be described from the perspective of a fourth device, wherein the fourth device may be... Figure 1 NF 140 in it, or may be included in it.

[0154] At box 810, the fourth device sends a service request for the service to the Access and Mobility Management Function (AMF).

[0155] At box 820, the fourth device receives a service response from the AMF, the service response including capability information of the Radio Access Network (RAN) node, the capability information indicating the RAN node's service-based architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via SBI based on the SBA capabilities.

[0156] At box 830, based on the determination that at least one service includes the requested service, an SBI is established between the third device and the RAN node based on the SBA capability of the RAN node, wherein the SBI enables direct communication between the third device and the RAN node.

[0157] In some example embodiments, the fourth device is a network function (NF) in the core network, or is included therein.

[0158] In some example embodiments, a first device capable of performing any of method 500 (e.g., a first device, wherein the first device may be...) Figure 1 The RAN node 110 (or may be included therein) may include components for performing the corresponding operations of method 500. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit system or a software module. The first device can be implemented as... Figure 1 RAN node 110 in the RAN may be included in it.

[0159] In some example embodiments, the first device includes components for sending capability information of the first device to an Access and Mobility Management Function (AMF) or a Network Repository Function (NRF), the capability information indicating the first device's Service-Based Architecture (SBA) capabilities and at least one service of the first device supported via an Service-Based Interface (SBI) based on the SBA capabilities; components for establishing a P2P NG-C P2P interface between the first device and the AMF; and components for establishing an SBI between the first device and a Network Function (NF) in the core network based on the SBA capabilities, wherein the NF is configured to request the service associated with the SBA capabilities from at least one service, and the SBI enables direct communication between the first device and the NF.

[0160] In some example embodiments, the first device further includes: receiving from the AMF a first establishment response to a first establishment request for establishing an NG-C P2P interface between the first device and the AMF, the first establishment response indicating whether the SBA capability of the first device is supported in the core network.

[0161] In some example embodiments, the P2P interface between the first device and the AMF includes a next-generation P2P (NG-C P2P) interface.

[0162] In some example embodiments, the first apparatus further includes: a component for sending an NF registration request to the NRF based on predetermined NRF access information in response to a first establishment response from the AMF, wherein the NF registration request includes at least information indicating at least one service supported via the SBI; and a component for receiving an NF registration response from the NRF.

[0163] In some example embodiments, the predetermined NRF access information includes the address or identifier information of the NRF. In some example embodiments, the predetermined NRF access information is pre-configured to the first device or received from the AMF in the first establishment response.

[0164] In some example embodiments, the first device further includes a component for receiving a second establishment response to a second establishment request from the NRF.

[0165] In some example embodiments, the first device further includes: a component for sending a third establishment request to the AMF for a P2P interface between the first device and the AMF, the third establishment request including an identifier of the SBI of the first device; and a component for receiving from the AMF a third establishment response to the third establishment request for establishing a P2P interface between the first device and the AMF.

[0166] In some example embodiments, the first apparatus further includes: a component for receiving a service request related to the NF from the AMF; and a component for sending capability information including: a component for sending a service response to the service request to the AMF, the service response including capability information.

[0167] In some example embodiments, the first device further includes: a component for sending first configuration update information to the AMF via the P2P interface in response to the establishment of a P2P interface between the first device and the AMF, and based on the determination that the first device supports SBA capability, the first configuration update information indicating that the first device supports SBA capability; and a component for receiving a first acknowledgment of the first configuration update information from the AMF, wherein after receiving the first acknowledgment, capability information is sent to the AMF or the NRF.

[0168] In some example embodiments, the first apparatus further includes: a component for receiving second configuration update information from the AMF, the second configuration update information indicating an update regarding or affecting support for SBA capabilities; and a component for sending a second acknowledgment of the second configuration update information to the AMF.

[0169] In some example embodiments, the first apparatus further includes: components for sending an NF deregistration request to the NRF in response to second configuration update information, requesting the deregistration of at least one service supported by the SBI from the NRF; and components for receiving an NF deregistration response to the NF deregistration request from the NRF.

[0170] In some example embodiments, the first device is a radio access network (RAN) node, or is included therein.

[0171] In some example embodiments, a second means capable of performing any of method 600 (e.g., a second means, wherein the second means may be...) Figure 1 The AMF 120 (or may be included therein) may include components for performing the corresponding operations of method 600. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit system or a software module. The second device can be implemented as... Figure 1 The AFM 120 may be included in it.

[0172] In some example embodiments, the second apparatus includes components for receiving capability information of a Radio Access Network (RAN) node from the RAN node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via SBI based on the SBA capabilities; components for sending a first establishment response to the RAN node indicating whether the RAN node's SBA capabilities are supported, based on a determination received from the RAN node in a first establishment request of the capability information, to establish a P2P interface between the RAN node and the second apparatus; and components for sending a second service response including the RAN node's capability information to the NF, based on a determination received from the RAN node in a first service response to a first service request for a Network Function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capabilities among the at least one services.

[0173] In some example embodiments, the first establishment response includes a Network Repository Function (NRF) identifier selected for the RAN node for registering at least one service.

[0174] In some example embodiments, the second means further includes: a component for sending an NF registration request to the RAN node to the NRF in response to receiving a first establishment request including capability information from the RAN node, wherein the NF registration request includes at least information indicating at least one service supported via the SBI; and a component for receiving an NF registration response from the NRF, wherein the second means is configured to send a first establishment response to the RAN node in response to receiving the NF registration response from the NRF.

[0175] In some example embodiments, the second apparatus further includes: a component for receiving a second service request from the NF requesting services from the RAN node; and a component for sending a first service request to the RAN node in response to receiving the second service request from the NF.

[0176] In some example embodiments, the second device further includes: a component for receiving first configuration update information from the RAN node in response to the establishment of a P2P interface between the RAN node and the second device, the first configuration update information indicating that the RAN node supports SBA capability; and a component for sending a first acknowledgment of the first configuration update information to the RAN node.

[0177] In some example embodiments, the second apparatus further includes: a component for sending second configuration update information to the RAN node based on a determination of an update regarding or affecting support for SBA capabilities, the second configuration update information indicating an update regarding or affecting support for SBA capabilities; and a component for receiving a second acknowledgment of the second configuration update information from the RAN node.

[0178] In some example embodiments, the second apparatus further includes: components for sending an NF deregistration request to the NRF from the NRF for deregistering at least one service supported by the SBI in response to receiving a second confirmation; and components for receiving an NF deregistration response from the NRF to the NF deregistration request.

[0179] In some example embodiments, the second device is an Access and Mobility Management Function (AMF), or is included therein.

[0180] In some example embodiments, a third means capable of performing any of the methods 700 (e.g., a third means, wherein the third means may be...) Figure 1 The NRF 130 (or may be included therein) may include components for performing the corresponding operations of method 700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The third device may be implemented as... Figure 1 NRF 130, or may be included in it.

[0181] In some example embodiments, the third device includes components for receiving, from a Radio Access Network (RAN) node or an Access and Mobility Management Function (AMF), a Network Function (NF) registration request for registering at the third device at at least one service of the RAN node, wherein the at least one service is supported via an SBA interface based on the RAN node's Service-Based Architecture (SBA) capability; and components for sending an NF registration response to the RAN node or AMF to the NF registration request.

[0182] In some example embodiments, the third device further includes: components for receiving from the RAN node or AMF an NF deregistration request from the third device for deregistering at least one service supported via SBI; and components for sending an NF deregistration response to the NF deregistration request to the RAN node or AMF.

[0183] In some example embodiments, the third device is a Network Repository Function (NRF) in the core network or RAN, or is included therein.

[0184] In some example embodiments, a fourth means capable of performing any of the methods 800 (e.g., a fourth means, wherein the fourth means may be...) Figure 1 NF 140 (or may be included therein) may include components for performing the corresponding operations of method 800. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The fourth device may be implemented as... Figure 1 NF 140 in, or may be included in it.

[0185] In some example embodiments, the fourth device includes components for sending a service request for a service to the Access and Mobility Management Function (AMF); components for receiving a service response from the AMF, the service response including capability information of a Radio Access Network (RAN) node indicating the RAN node's service-based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via an SBI based on the SBA capabilities; and components for establishing an SBI between the third device and the RAN node based on the determination of at least one service including the requested service and the RAN node's SBA capabilities, wherein the SBI enables direct communication between the third device and the RAN node.

[0186] In some example embodiments, the fourth device is a network function (NF) in the core network, or is included therein.

[0187] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. The device 900 can be provided to implement a communication device, for example, such as... Figure 1 The RAN node 110, AMF 120, NRF 130, or NF 140 are shown. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

[0188] Communication module 940 is used for bidirectional communication. Communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 940 may include at least one antenna.

[0189] Processor 910 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0190] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that do not persist during power outages.

[0191] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 930 may be stored in memory, such as ROM 924. Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0192] The exemplary embodiments of this disclosure can be implemented by program 930, such that device 900 can execute the reference Figures 2A to 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0193] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (such as memory 920) or other storage devices accessible by device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transient storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transient" as used herein refers to a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0194] Figure 10 An example of a computer-readable medium 1000, which may be in the form of a CD, DVD, or other optical storage disc, is shown. The computer-readable medium 1000 has a program 930 stored thereon.

[0195] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0196] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in a program module, which execute in a device on a target physical or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0197] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0198] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0199] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0200] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order or sequential sequence shown, or to perform all of the shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0201] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the first device to at least: The first device's capability information is sent to the Access and Mobility Management Function (AMF) or the Network Repository Function (NRF), the capability information indicating the first device's Service-Based Architecture (SBA) capabilities and at least one service of the first device, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI); Establish a peer-to-peer (P2P) interface between the first device and the AMF; as well as Based on the SBA capability, the SBI is established between the first device and the network function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capability from the at least one service, and the SBI enables direct communication between the first device and the NF.

2. The first device according to claim 1, wherein the first device is configured to transmit the capability information by means of: Send a first establishment request to the AMF to establish a P2P interface between the first device and the AMF, the first establishment request including the capability information; and The first device is configured such that: The first establishment response is received from the AMF in response to the first establishment request to establish the P2P interface between the first device and the AMF. The first establishment response indicates whether the SBA capability of the first device is supported in the core network.

3. The first device according to claim 1 or 2, wherein the P2P interface between the first device and the AMF includes a next-generation P2P interface.

4. The first device according to claim 2 or 3, wherein the first device is further configured to: In response to the first establishment response from the AMF, an NF registration request is sent to the NRF based on predetermined NRF access information, wherein the NF registration request includes at least information indicating the at least one service supported via the SBI; and Receive the NF registration response from the NRF.

5. The first apparatus according to claim 4, wherein the predetermined NRF access information includes the address of the NRF or the identifier information of the NRF.

6. The first apparatus of claim 4, wherein the predetermined NRF access information is pre-configured to the first apparatus or received from the AMF in the first establishment response.

7. The first device according to claim 1, wherein the first device is configured to transmit the capability information by: A second establishment request for the SBI is sent to the NRF, the second establishment request including the capability information; and The first device is further configured to: Receive a second establishment response to the second establishment request from the NRF.

8. The first apparatus of claim 7, wherein the second establishment request includes an NF registration request, and the second establishment response includes an NF registration response; and The first device is further configured to: Send a third establishment request to the AMF for the P2P interface between the first device and the AMF, the third establishment request including the identifier of the SBI of the first device; and Receive a third establishment response from the AMF for the third establishment request to establish the P2P interface between the first device and the AMF.

9. The first device according to claim 1, wherein the first device is further configured to: Receive service requests related to the NF from the AMF; and The first device is configured to transmit the capability information via the following: Send a service response to the service request to the AMF, the service response including the capability information.

10. The first device according to any one of claims 1 to 8, wherein the first device is further configured to: In response to the establishment of the P2P interface between the first device and the AMF, and based on the determination that the first device supports the SBA capability, Sending first configuration update information to the AMF via the P2P interface, the first configuration update information indicating that the first device supports the SBA capability; and Receive a first confirmation of the first configuration update information from the AMF, and The capability information is sent to the AMF or the NRF.

11. The first device according to any one of claims 1 to 10, wherein the first device is further configured to: Receive second configuration update information from the AMF, the second configuration update information indicating an update regarding or affecting support for the SBA capability; and Send a second confirmation of the second configuration update information to the AMF.

12. The first device according to claim 11, wherein the first device is further configured to: In response to the second configuration update information, a request is sent to the NRF to deregister the NF from the NRF for at least one service supported via the SBI; and Receive an NF deregistration response to the NF deregistration request from the NRF.

13. The first apparatus according to any one of claims 1 to 12, wherein the first apparatus is a radio access network (RAN) node, or is included in a RAN node.

14. A second means for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the second device to at least: Receive capability information from the Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; Based on the determination received from the RAN node in the first establishment request, the capability information is... Send a first establishment response to the RAN node indicating whether the SBA capability of the RAN node is supported, in order to establish a peer-to-peer P2P interface between the RAN node and the second device; as well as Based on the determination that the capability information is received from the RAN node in the first service response to the first service request of the network function NF in the core network, a second service response including the capability information of the RAN node is sent to the NF, wherein the NF is configured to request the service associated with the SBA capability among the at least one services.

15. The second apparatus of claim 14, wherein the first establishment response includes Network Repository Function (NRF) access information selected for the RAN node for registering the at least one service.

16. The second device according to claim 14, wherein the second device is further configured to: In response to receiving a first establishment request including the capability information from the RAN node, an NF registration request for the RAN node is sent to the NRF, wherein the NF registration request includes at least information indicating the at least one service supported via the SBI; and Receive NF registration response from the NRF, and The second device is configured to send the first establishment response to the RAN node in response to receiving the NF registration response from the NRF.

17. The second device according to claim 14, wherein the second device is further configured to: Receive a second service request from the NF requesting the service of the RAN node; and In response to receiving the second service request from the NF, the second service request is sent to the RAN node.

18. The second device according to any one of claims 14 to 17, wherein the second device is further configured to: In response to the establishment of the P2P interface between the RAN node and the second device, first configuration update information is received from the RAN node, the first configuration update information indicating that the RAN node supports the SBA capability; and Send a first acknowledgment of the first configuration update information to the RAN node.

19. The second device according to any one of claims 14 to 18, wherein the second device is further configured to: Based on the determination of an update regarding or affecting support for the SBA capability, a second configuration update message is sent to the RAN node, the second configuration update message indicating an update regarding or affecting support for the SBA capability; and Receive a second confirmation of the second configuration update information from the RAN node.

20. The second device according to claim 19, wherein the second device is further configured to: In response to receiving the second confirmation, a request to the NRF is sent to deregister the NF from the NRF for the at least one service supported via the SBI; and Receive an NF deregistration response to the NF deregistration request from the NRF.

21. The second device according to any one of claims 14 to 20, wherein the second device is an Access and Mobility Management Function (AMF) or is included in an AMF.

22. A third means for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the third device to at least: The network function (NF) registration request is received from the radio access network (RAN) node or the access and mobility management function (AMF) at the third device for registering at least one service of the RAN node, wherein the at least one service is supported via the service-based interface (SBI) based on the service-based architecture (SBA) capability of the RAN node. as well as Send an NF registration response to the RAN node or the AMF in response to the NF registration request.

23. The third device according to claim 22, wherein the third device is further configured to: Receive from the RAN node or the AMF an NF deregistration request from the third device for at least one service supported via the SBI; and Send an NF deregistration response to the RAN node or the AMF in response to the NF deregistration request.

24. The third device according to claim 22 or 23, wherein the third device is a network repository function (NRF) in the core network or RAN, or is included in the NRF.

25. A fourth means for communication, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the first device to at least: Send a service request for the service to the Access and Mobility Management Function (AMF); Receive a service response from the AMF, the service response including capability information of the Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI); as well as Based on the determination that the at least one service includes the requested service, and based on the SBA capability of the RAN node, the SBI is established between the third device and the RAN node, wherein the SBI enables direct communication between the third device and the RAN node.

26. The fourth device according to claim 25, wherein the fourth device is a network function (NF) in the core network, or is included in an NF in the core network.

27. A method for communication, comprising: The first device's capability information is sent to the Access and Mobility Management Function (AMF) or the Network Repository Function (NRF), the capability information indicating the first device's Service-Based Architecture (SBA) capabilities and at least one service of the first device, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI); Establish a peer-to-peer (P2P) interface between the first device and the AMF; as well as Based on the SBA capability, the SBI is established between the first device and the network function (NF) in the core network, wherein the NF is configured to request the service associated with the SBA capability from the at least one service, and the SBI enables direct communication between the first device and the NF.

28. A method for communication, comprising: Receive capability information from the Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported via a Service-Based Interface (SBI) based on the SBA capabilities; Based on the determination received from the RAN node in the first establishment request, the capability information is... Send a first establishment response to the RAN node indicating whether the SBA capability of the RAN node is supported, in order to establish a peer-to-peer P2P interface between the RAN node and the second device; as well as Based on the determination that the capability information is received from the RAN node in the first service response to the first service request of the network function NF in the core network, a second service response including the capability information of the RAN node is sent to the NF, wherein the NF is configured to request the service associated with the SBA capability among the at least one services.

29. A method for communication, comprising: The network function (NF) registration request is received from the radio access network (RAN) node or the access and mobility management function (AMF) at the third device for registering at least one service of the RAN node, wherein the at least one service is supported via the service-based interface (SBI) based on the service-based architecture (SBA) capability of the RAN node. as well as Send an NF registration response to the RAN node or the AMF in response to the NF registration request.

30. A method for communication, comprising: Send a service request for the service to the Access and Mobility Management Function (AMF); Receive a service response from the AMF, the service response including capability information of the Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI); as well as Based on the determination that the at least one service includes the requested service, and based on the SBA capability of the RAN node, the SBI is established between the third device and the RAN node, wherein the SBI enables direct communication between the third device and the RAN node.

31. A first device for communication, comprising: Components for sending capability information of the first device to the Access and Mobility Management Function (AMF) or the Network Repository Function (NRF), the capability information indicating the service-based architecture (SBA) capabilities of the first device and at least one service of the first device, the at least one service being supported based on the SBA capabilities via a service-based interface (SBI); Components used to establish a peer-to-peer (P2P) interface between the first device and the AMF; as well as Components for establishing the SBI between the first device and a network function (NF) in the core network based on the SBA capability, wherein the NF is configured to request a service associated with the SBA capability from at least one service, and the SBI enables direct communication between the first device and the NF.

32. A second means for communication, comprising: Components for receiving capability information of a Radio Access Network (RAN) node from the RAN node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI). Based on the determination received from the RAN node in the first establishment request, the capability information is... Components for sending a first establishment response to the RAN node indicating whether the SBA capability of the RAN node is supported, in order to establish a peer-to-peer P2P interface between the RAN node and the second device; as well as A component for determining, based on the capability information received from the RAN node in a first service response to a first service request for a network function NF in the core network, and sending a second service response including the capability information of the RAN node to the NF, wherein the NF is configured to request a service associated with the SBA capability among the at least one services.

33. A third means for communication, comprising: A component for receiving a network function (NF) registration request from a radio access network (RAN) node or an access and mobility management function (AMF) to register at the third device at at least one service of the RAN node, wherein the at least one service is supported via a service-based architecture (SBA) interface based on the service-based architecture (SBA) capability of the RAN node. as well as A component for sending an NF registration response to the RAN node or the AMF in response to the NF registration request.

34. A fourth means for communication, comprising: Component used to send service requests for services to the Access and Mobility Management Function (AMF); Components for receiving service responses from the AMF, the service responses including capability information of a Radio Access Network (RAN) node, the capability information indicating the RAN node's Service-Based Architecture (SBA) capabilities and at least one service of the RAN node, the at least one service being supported based on the SBA capabilities via a Service-Based Interface (SBI). as well as A component for establishing the SBI between the third device and the RAN node based on the determination of the requested service, according to the SBA capability of the RAN node, wherein the SBI enables direct communication between the third device and the RAN node.

35. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device to perform at least the method of claim 27, or the method of claim 28, or the method of claim 29, or the method of claim 30.

Images