Service discovery in a wireless communication network

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and send, to the second network entity, a first response message comprising the RAN profile.

Description

SERVICE DISCOVERY IN A WIRELESS COMMUNICATIONNETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of implementing service discovery in a wireless communication network. In particular, this document defines a first network entity and a second network entity apparatus and methods thereof.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on”shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] There is provided a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and send, to the second network entity, a first response message comprising the RAN profile.

[0005] There is further provided a method performed by a first network entity, the method comprising: receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a first response message comprising the RAN profile.

[0006] There is further provided a second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receive, from the first network entity, a first response message comprising the RAN profile.

[0007] There is further provided a method performed by a second network entity, the method comprising: sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein aRAN profile relating to the RAN service; and receiving, from the first network entity, a first response message comprising the RAN profile.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0009] Figure 2 illustrates a flow diagram of a service-based architecture in a wireless communications network in accordance with aspects of the present disclosure.

[0010] Figure 3 illustrates a service-based architecture in a wireless communications network in accordance with aspects of the present disclosure.

[0011] Figure 4 illustrates a signalling diagram for a service registration process in accordance with aspects of the present disclosure.

[0012] Figure 5 illustrates a signalling diagram for a service discovery process in accordance with aspects of the present disclosure.

[0013] Figure 6 illustrates a signalling diagram for a profile replacement process in accordance with aspects of the present disclosure.

[0014] Figure 7 illustrates a signalling diagram for a profile partial update process in accordance with aspects of the present disclosure.

[0015] Figure 8 illustrates a signalling diagram for a notification process in accordance with aspects of the present disclosure.

[0016] Figure 9 illustrates an example of a user equipment (UE) 900 in accordance with aspects of the present disclosure.

[0017] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure.

[0018] Figure 11 illustrates an example of a network equipment (NE) 1100 in accordance with aspects of the present disclosure.

[0019] Figure 12 illustrates a flowchart of a method 1200 performed by a NE in accordance with aspects of the present disclosure.

[0020] Figure 13 illustrates a flowchart of a method 1300 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0021] A core network in a wireless communication network (or wireless communication system) may comprise a service-based architecture (SBA). An SBA typically comprises a Network Repository Function (NRF) (or Network function Repository Function) that enables a Network Function (NF) service consumer to discover and select an NF service producer.

[0022] Examples described herein relate to the extension of SBA to include a Radio Access Network (RAN) in the wireless communication network.

[0023] Aspects of the present disclosure are described in the context of a wireless communications system.

[0024] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multipleaccess (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0025] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0026] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0027] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0028] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D)communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0029] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0030] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0031] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and theapplication server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0032] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0033] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0034] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations,each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0035] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0036] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data).In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0037] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0038] Figure 2 illustrates a flow diagram 200 of an SB A in a wireless communications network in accordance with aspects of the present disclosure. The flow diagram 100 may illustrate an overview of the service registration and discovery process within 5G SBA. The flow diagram 200 illustrates service registration 271 between an NF service producer 210 and a Network Repository Function (NRF) 211. The flow diagram 200 illustrates service request / response 272 between the NF service producers 210 and an NF service consumer 212. The flow diagram 200 illustrates service discovery 273 between the NRF 211 and an NF service consumer 212.

[0039] A 5G core leverages the benefits of an SBA, which is based on a consumerproducer model in where NFs can select, request, and receive or offer a service upon a specified condition or event. In SBA, each NF may be registered in a repository, for example, in an NRF 211. The NRF 211 assists other NFs (e.g., NF service consumer 212) to identify and select a service from another NF (e.g., NF service producer 210) as illustrated in Figure 2.

[0040] Step 271 in flow diagram 200 illustrates service registration. In service registration, the NF service producer 210 may initially register its available services when activated in the NRF 211.

[0041] Step 272 shows service discovery. In service discovery, an NF service consumer 212 may discover a service when needed by issuing a query to the NRF 211, whichresponds with the available service(s) that match the desired requirements and the corresponding NF address(es).

[0042] Step 273 shows service request / response. In service request / response, the NF service consumer 212 selects an NF service producer 210 that matches best its requirements from the ones provided by the NRF 211 and issues a service request to receive a service response.

[0043] Service discovery may be based on at least one of:• NF capabilities, e.g., offered NF services;• NF allocated priority relative to other NFs of the same type;• NF static capacity and NF dynamic load information;• NF serving scope (e.g., geographical operation scope of a NF);• locality related to the location of the NF (e.g., geographic location, data center, etc.);• NF slice related information (e.g., Single Network Slice Selection Assistance Information (S-NSSAI) or Network Slice Instance (NSI));• NF access permissions (e.g., type of NF(s) or Public Land Mobile Network(s) (PLMN(s)) identity allowed to access); and / or• NF vendor specific information.

[0044] Examples described herein relate to the extension of SBA to a Radio Access Network (RAN). Examples described herein tend to:

[0045] Enable core NFs (for example, NF service consumer 212) to consume RAN services, for example: a Network Data Analytics Function (NWDAF) may consume RAN performance measurements or analytics instead of RAN-related measurements that may be averaged provided by an Operations, Administration, and Maintenance (0AM).• a Session Management Function (SMF), for session management and Quality of Service (QoS) related decisions, that may consume Data Radio Bearer (DRB) load information by the RAN entity, for example, this may allow for pro-active actions related to a possible RAN QoS downgrade.

[0046] Enable RAN functions to consume Core NF services (for example, services provided by NF service producer 210). For example:• the NWDAF may provide User Equipment (UE) analytics or QoS analytics for a RAN consumer. For example, for a Radio Resource Management (RRM) or a SelfOrganising Network (SON) function, to optimize the decisions based on the mobile core perspective.• Location services, e.g., Location Management Function (LMF) services, may be consumed by RAN functions to optimize decisions related to the flow to bearer mapping and scheduling.• Enable direct exposure of RAN control services to an Application Function (AF). In the past, AF (for example, 3rd party or Mobile Network Operator (MNO) apps) may not consume RAN services; for example, for measurements or scheduling decisions. In examples described herein, the extension of SBA to RAN tends to enable RAN services to be consumed by authorized AFs. Such exposure tends to simplify interactions with vertical customers, application developers and 3rd parties.

[0047] Figure 3 illustrates an SBA 300 in a wireless communications network in accordance with aspects of the present disclosure.

[0048] The SBA 300 comprises the following network entities connected to each other via a network: an NWDAF 321, NRF 311, PCF, 322, Unified Data Management (UDM) / Unified Data Repository (UDR) 323, Access and Mobility Management Function (AMF) 324, SMF 325, Network Exposure Function (NEF) 326, Service Capability Server (SCP) 327, UE 340, RAN Function 330, User Plane Function (UPF) 328, Data Network (DN) 329.

[0049] SB A 300 illustrates the extension of the SB A into the RAN by extending the SBA into the N2 interface between the 5G core and a gNodeB (gNB).

[0050] In SBA 300, the RAN appears as a RAN Function either as RAN Function- Option 1 331 or alternatively RAN Function-Option 2 332. In RAN Function-Option 1 331, a Centralized Unit (CU) 333 is connected to the SBA 300 and a Distributed Unit (DU) 335 is part of a user plane. In RAN Function-Option 2 332, a RAN control plane (CP) 336 is part of the SBA 300 and the RAN User Plane (UP) 337 is connected to the user plane. In either option the RAN Function may connect to the SBA directly (Option A) or via the AMF (Option B).

[0051] Examples described herein relate to discovery mechanisms and selection processes that consider information related to RAN functions to facilitate a core entity, e.g., a core NF, to select a RAN NF or a specific RAN service.

[0052] Examples described herein relate to the adoption of SBA into the RAN as an extension of the core network SBA. Examples described herein relate a new RAN NF or RAN Function (these terms may be used interchangeably to describe the same entity), which can appear into the SBA of the core network. Examples described herein enable discovery and selection mechanisms of a RAN NF in 5G core network that tend to facilitate an effective and efficient interaction between RAN and core network services. The RAN NF may be an individual NF, or a logical NF collocated with other core NFs depending on deployment.

[0053] A RAN service may comprise at least one of:• Radio resource management (RRM) related services such as: (i) inter-cell RRM, (ii) connection mobility control, (iii) radio bearer control, (iv) scheduling, (v) measurements, (vi) energy saving, e.g., discontinuous transmission and reception.• Radio connection control services such as: (i) radio bear management, (ii) UE radio connectivity.• Distributed Self-Organizing Network (D-SON) services executed in the base station, such as: (i) handover and mobility robustness optimization, (ii) mobilityload balancing, (iii) coverage and capacity optimization, (iv) cell degradation detection, (v) Time Division Duplex (TDD) optimization, e.g., UL / DL data rate tuning, (vi) QoS optimization.• Artificial Intelligence (Al) / Machine Learning (ML) services such as: (i) RAN analytics, i.e., inference RAN “Analytics IDs”, equivalent to 5G core as per TS 23.288 V18.6.0, (ii) training services based on RAN data, (iii) ML model split, e.g., deep learning ML models, for inference and / or training, (iv) ML model feature, e.g., for deep federated learning ML models.• RAN exposure services: (i) RAN abstraction, (ii) RAN parameter configuration, (iii) RAN exposure or gateway.

[0054] A RAN service may be perceived as per type of service; for example, irrespective of the RAN technology, while other new RAN services may also emerge.

[0055] The discovery and selection of RAN services into the mobile core network may involve a new RAN NF entry in the NRF. The RAN NF entry may comprise respective RAN service information. The RAN NF entry may comprise a RAN NF profile. The RAN NF profile may comprise at least one of:• Mobile network operator information; for example, a PLMN ID that the RAN NF belongs to.• Status information related to the availability of certain functionalities and / or services, e.g., to reflect faults or energy saving conditions.• Authorization and / or permissions related to the: o Type of mobile core NFs that can or are allowed to access the RAN NF. o Domain information from which entities can or are allowed to access the RAN NF. o Slice information related to access allowance, including slice per PLMN ID. o List PLMN IDs that can share the RAN NF and / or can access the RAN NF.o Standalone Non-Public Network (SNPN) IDs allowed to access the RAN NF. o Information related to trusted AFs related to accessing RAN NF.• Set of rules specifying the consumers allowed or denied accessing the RAN NF.• Address information including IPv4 or IPv6 address and / or Fully Qualified Domain Name (FQDN).• Serving scope, e.g., the area of interest in which the radio access points related to a specific RAN NF provide coverage and RAN services.• Locality information related to the location, e.g., the data centre location, of the RAN NF instance.• Priority information, to assist in selecting the appropriate RAN NF; for example, in case of overlapping coverage with more than one responsible RAN NF.• Capacity information, a static indicator expressed as a weight related to RAN NF relative to other RAN NFs; for example, the static indicator may express the amplitude of a RAN NF to offer related services.• Load information that indicates how loaded the RAN NF is at a specified point in time.• Radio Access Technology (RAT) information, e.g., Long-Term Evolution (LTE), New Radio (NR), Next Generation Radio Access Network (NG-RAN), 6G Radio, related to the radio access points served and associated with a specific RAN NF including an indication of coverage overlapping among Radio Access Technology (RAT).Spectrum range related to the radio access points contained in a RAN NF, including spectrum type indicator; for example, licensed, or unlicensed spectrum.• Antenna characteristics of the radio access points associated with a specific RAN NF; for example, including directional, omnidirectional, beamforming, and / or antenna arrays.• Radio connectivity characteristics, e.g., radio bearer control or radio connectivity.• Radio transmission features of the radio access points associated with a specific RAN NF including e.g., carrier aggregation, coordinated multipoint operation (ComP), support for reflective surfaces, support of fixed mobile convergence and / or dual steering.• Radio medium characteristics of the radio access points associated with a specific RAN NF including support of e.g., TDD or Frequency Division Duplex (FDD), simplex and / or fully duplex, etc.• Handover configuration parameters among neighbouring cells which can be used, e.g., for mobility robustness and optimization or load balancing or energy saving, etc.• Type of radio access point and coverage characteristics of the radio access points associated with a specific RAN NF including for example:• static coverage provided by a fixed base station.• opportunistic coverage from a moving relay that stores and forwards data.• Interoperability information; for example, a vendor identifier.• Vendor specific features information, e.g., a list of vendor specific feature objects.

[0056] A RAN NF may provide one or more RAN service(s) (or RAN NF service(s)). Each RAN service may include at least one of:• Service information including the Service ID and Service name, Service version(s), Service status, (e.g., availability, fault, energy saving), Service Data, Service features, Service grouping, e.g., per PLMN or SNPN or Service grouping per potential conflicts (i.e., services that may impact one another, e.g., D-SON handoverand mobility robustness optimization may configure mobility parameters in contrast with the D-SON mobility load balancing), Service schedule or time availability. Examples of a RAN service may include at least one of: (i) Radio resource management, (ii) D-SON and / or (iii) RAN analytics service, e.g., RAN Analytics ID, (iv) RAN exposure.• Preference of service address information; for example, if the RAN NF profile supports several options, e.g., FQDN, Internet Protocol (IP) end points, and / or end point for different notification types.• Authorization and / or permissions related to at least one of: o Type of mobile core NFs that can or are allowed to access a specified RAN NF Service(s). o Domain information from which entities can or are allowed to access a specified RAN NF Service(s). o Slice information related to access allowance for a specified RAN NF Service(s). o List PLMN IDs that can access a specified RAN NF Service(s). o SNPN IDs allowed to access a specified RAN NF Service(s). o Allowed RAN NF Service operations per specific consumer.• Set of rules specifying the consumers allowed or denied accessing specified RAN NF Services.• Priority information to assist in selecting the appropriate RAN NF Service; for example, in case of more than one identical RAN NF Service is available in an overlapping coverage area.• Capacity information, a static indicator expressed as a weight related to a RAN NF Service relative to other RAN NF Services; for example, the static indicator may express an amplitude of a RAN NF Service.• Load information that indicates how loaded the RAN NF Service is at a specified point in time.• RAT information, e.g., LTE, NR, NG-RAN, 6G Radio, related to the radio access points that can offer a RAN NF Service including an indication of coverage overlapping among specified RATs.• Spectrum range related to the radio access points that can offer a RAN NF Service, including spectrum type indicator; for example, licensed, or unlicensed spectrum.• Antenna characteristics of the radio access points that can offer a RAN NF Service including e.g., directional, omnidirectional, beamforming and / or antenna arrays.• Radio connectivity characteristics, e.g., radio bearer control and / or radio connectivity.• Radio transmission features of the radio access points that can offer a RAN NF Service including e.g., carrier aggregation, coordinated multipoint operation (ComP), support for reflective surfaces, support of fixed mobile convergence and / or dual steering.• Radio medium characteristics of the radio access points that can offer a RAN NF Service including support of e.g., TDD or FDD, simplex or fully duplex, etc.• Type of radio access point and coverage characteristics of the radio access points that can offer a RAN NF Service including for example: o static coverage provided by a fixed base station. o opportunistic coverage from a moving relay that stores and forwards data.• Slice identifier, optionally per PLMN, where a RAN NF Service is available.• Interoperability information; for example, vendor identifier, per RAN NF Service.Vendor specific features information, e.g., a list of vendor specific feature objects, per RAN NF Service.

[0057] In some examples described herein, the NF profile may be as described in the table 6.1.6.2.2-1 TS 29.510 V18.7.0 and the NF service may be as described in the table 6.1.6.2.3-1 TS 29.510 18.7.0.

[0058] The NF profile may include a new field that may be referred to as RANNFInfo. RANNFInfo may be related to radio features of a specific RAN NF, which may be used by other core NFs or may be exposed to external entities, e.g., AFs. A consumer may then discover and select the appropriate RAN NF and respective service.

[0059] Table 1 below lists the attribute name, data type, cardinality and description of parameters related to RANNFInfo.Table 1 Example of parameters related to RANNFInfo

[0060] In some examples described herein, NRF procedures that may be affected because of the RAN NF related issues may include at least one of:• Nnrf_NFManagement_Register: this procedure may allow a RAN NF Instance to register its profile in the NRF.• Nnrf_NFDiscovery_Request: this procedure may allow a NF or external entity, e.g., an untrusted AF outside the MNO, to discover and select a RAN NF Instance or service.• Nnrf_NFManagement_NFUpdate: this procedure may allow a RAN NF Instance to replace, or update partially, the parameters of its profile in the NRF; it also allows to add or delete individual services offered by the RAN NF Instance.• Nnrf_NFManagement_NFStatusNotify: this procedure may allow the NRF to notify subscribed NF or SCP Instances of changes on the RAN NF Instances. This service operation can be invoked directly between the NRF and an NF Instance in a different PLMN (without involvement of the local NRF in that PLMN) for changes on a RAN NF Instance.

[0061] In the following examples, the NF Service Producer and NF Service Consumer may reflect the role of each NF in the context of SBA. Both of the NF Service Producer and / or NF Service Consumer may be consumers of NRF services.

[0062] Figure 4 illustrates a signalling diagram for a service registration process 400 in accordance with aspects of the present disclosure. The service registration process 400 may be an NF service registration procedure including RAN NF Information (for example, RANNFInfo). The service registration process 400 involves an NF service producer 410 and an NRF 411.

[0063] In step 471, the NF service producer 410 (for example, a RAN NF service producer) sends an Nnrf_NFManagement_NFRegister Request message to NRF 411 to inform the NRF 411 of its NF profile (which may be referred to as a RAN NF profile). The NF profile comprises RAN NF Info. The Nnrf_NFManagement_NFRegister Requestmessage may be sent when the NF service producer 410 becomes operative for the first time.

[0064] The NF service producer's 410 NF profile is configured by an 0AM system (not shown). The 0AM may alternatively configure the NF profile, including the RAN NF Info to the NRF 411.

[0065] In step 472, the NRF 411 stores the NF profile of NF service producer 410 and marks the NF service producer 410 as available. Then, the NRF 411 acknowledges NF Registration is accepted via an Nnrf_NFManagement_NFRegister response.

[0066] For deregistering, the NF service producer 410 sends an Nnrf_NFManagement_NFDeregister Request to NRF 411 to inform it about its unavailability. The NRF 411 removes it according to NF management policy and acknowledges that the NF deregistration is accepted via a Nnrf_NFManagement_NFDeregister response message.

[0067] Figure 5 illustrates a signalling diagram for a service discovery process 500 in accordance with aspects of the present disclosure. The service discovery process 571a may be an NF and NF service discovery by NF service consumer 510 in the same PLMN. The service discovery process 500 may be an NF / NF service discovery in the same PLMN. The service discovery process 500 involves an NF service consumer 510 and an NRF 511.

[0068] In step 571a, the NF service consumer 510, which may be an NF, or an AF, intends to discover services available in the network based on a service name including RAN services and target NF type, e.g., RAN NF, invoking an Nnrf_NFDiscovery_Request message. Parameters that may be included in the Nnrf_NFDiscovery_Request message include NF profile and / or NF service parameters as per table 6.1.6.2.2-1 and / or table 6.1.6.2.3-1 of TS 29.510 VI 8.7.0, respectively.

[0069] In the Nnrf_NFDiscovery_Request message, the NF service consumer 510 may indicate a preference, e.g., for target RAN NF location or coverage etc., or a preference for a particular RAN service, e.g., RAN exposure.

[0070] If the NF service consumer 510 is an untrusted AF, then the request may be handled and authorized by an NEF (not shown).

[0071] In step 571b, the NRF 511 authorizes the Nnrf_NFDiscovery_Request considering the profile of the expected NF / NF service and the type of the NF service consumer. If the expected NF or NF service instance(s) are deployed in a network slice, NRF 511 authorizes the discovery request according to the discovery configuration of the Network Slice.

[0072] In step 572, if allowed, the NRF 511 determines a set of NF instance(s) matching the Nnrf_NFDiscovery_Request and sends the NF profile(s) of the determined NF instances to the NF service consumer 510.

[0073] NF instance(s) may reside in a target PLMN as specified in clause 4.2.3 and clause 6.2.6.1 of TS 23.501 V19.0.0, the NRF 511 in a Home Public Land Mobile Network (HPLMN) may query an NRF 511 in a target PLMN.

[0074] NF / NF service discovery by an NF service consumer 510 in the same Standalone Non-Public Network (SNPN) may follow the same principles as NF / NF service discovery by an NF service consumer 510 in the same PLMN.

[0075] Figure 6 illustrates a signalling diagram for a profile replacement process 600 in accordance with aspects of the present disclosure. The profile replacement process 600 may be an NF profile full update. The profile replacement process 600 may comprise a profile complete replacement including RAN NF Info related updates. The profile replacement process 600 involves an NF service producer 610 and an NRF 611.

[0076] In step 671, the NF Service Producer 610 (for example, the RAN NF Service Producer) sends a PUT request to the resource Uniform Resource Identifier (URI) representing the NF Instance. The pay load body of the PUT request shall contain a representation of the NF Instance to be completely replaced in the NRF 611. The replaced NF instance contains RAN NF Info parameter changes.

[0077] In step 672, on success, the NRF 611 sends an "200 OK" message to the NF service producer 610, the pay load body of the PUT response may contain the representation of the replaced resource following the operations specified in TS 29.510 V18.7.0.

[0078] On failure, the NRF 611 may provide the problem details, e.g., in case of errors in the encoding of the NF Profile JavaScript Object Notation (JSON) object, the NRF 611 may return a Bad Request or in case of NRF 611 internal errors, the NRF 611 may return an Internal Server Error. In the case of redirection, the NRF 611 may return a Location header with a URI pointing to the endpoint of another NRF service instance as specified in TS 29.510 VI 8.7.0.

[0079] Figure 7 illustrates a signalling diagram for a profile partial update process 700 in accordance with aspects of the present disclosure. The profile partial update process 700 may be an NF profile partial update process. The profile partial update process 700 may comprise NF Profile partial updates focusing on RAN NF related information. The profile partial update process 700 involves an NF service producer 710 and an NRF 711.

[0080] For the case of partial update of the NF Profile, the NF Service Producer 710 may issue a Hypertext Transfer Protocol (HTTP) PATCH request, as shown in the profile partial update process 700. This partial update may be used to add / delete / replace individual parameters of the NF Instance, and services (and their parameters) offered by the NF Instance (including RAN NF Info related parameters).

[0081] In step 771, the NF Service Producer 710 may send a PATCH request to the resource URI representing the NF Instance. The payload body of the PATCH request may contain the list of operations (for example, add, delete, or replace) to be applied to the NF Profile of the NF Instance; these operations may be directed to individual parameters (that may contain potential RAN NF Info parameters changes) of the NF Profile or to the list of services (and their parameters) offered by the NF Instances. The list of services may include RAN parameters changes. To leave the NF Profile in a consistent state, all the operations specified by the PATCH request body may be executed atomically.

[0082] The NF Service Producer 710 may include an "If-Match" HTTP header carrying the latest entity-tag received from NRF 711 for the NF profile to which the PATCH document may be applied.

[0083] In step 772, on success, if all update operations are accepted by the NRF 711, a "204 No Content" may be returned; the NRF 711 may instead return a "200 OK" with the payload body of the PATCH response containing the representation of the replaced resource following the operations specified in TS 29.510 VI 8.7.0.

[0084] On failure, the NRF 711 may provide the problem details, e.g., in case the "nflnstancelD" is not found in the list of registered NF Instances in the NRF's 711 database, the NRF 711 may return a "404 Not Found" status code.

[0085] In the case of redirection, the NRF 711 shall return a Location header with an URI pointing to the endpoint of another NRF service instance as specified in TS 29.510 VI 8.7.0. If the "If-Match" header is received with an entity tag different from the entity -tag in NRF 711 for NF profile of the target NF instance, the NRF 711 may return precondition failed status. If no precondition was defined in the request and another confliction has been detected (e.g., to change value of a non-existing IE), the NRF 711 may return a conflicting status.

[0086] The NRF 711 may allow updating Vendor-Specific attributes (see3GPP TS 29.500 V18.6.1, clause 6.6.3) that may exist in the NF Profile of a registered NF Instance.

[0087] Figure 8 illustrates a signalling diagram for a notification process 800 in accordance with aspects of the present disclosure. The notification process 800 may comprise an NRF notification in the same PLMN. The notification process 800 may comprise a Notification from NRF in the same PLMN including on RAN related updates. The notification process 800 involves an NF service consumer 810 and an NRF 811.

[0088] In step 871, the NRF 811 may send a POST request to the callback URI. For notifications of newly registered NF Instances, the request body may include the data associated to the newly registered NF, and its services, according to the criteria indicated by the NF Service Consumer 810 during the subscription operation, as specified in TS 29.510VI 8.7.0. For notifications of changes of the profile of a NF Instance, the request body may include the NFInstancelD of the NF Instance whose profile was changed, an indication of the event being notified (for example, "profile change"), and the new profile data including RAN related data.

[0089] For notifications of deregistration of the NF Instance from NRF 811, the request body may include the NFInstancelD of the deregistered NF Instance, and an indication of the event being notified (for example, "deregistration").

[0090] When the NF Service Consumer 810 subscribes to a set of NFs, using the subscription conditions specified in clause 6.1.6.2.35 TS 29.510 V18.7.0, in case of a change of profile(s) of NFs potentially related to those subscription conditions, the NRF 811 may send notification to subscribing NF Service Consumer(s) 810 to those NFs no longer matching the subscription conditions, and to subscribing NF Service Consumer(s) 810 to NFs that start matching the subscription conditions, as specified in TS 29.510 V18.7.0.

[0091] The notification of changes of the profile may be done by the NRF 811 either by sending the entire new NF Profile, or by indicating a number of "delta" changes (for example, see clause 6.1.6.2.17 TS 29.510 VI 8.7.0) from an existing NF Profile that might have been previously received by the NF Service Consumer during an NFDiscovery search operation (for example, see clause 5.3.2.2 TS 29.510 V18.7.0).

[0092] Change of authorization attributes (allowedNfTypes, allowedNfDomains, allowedNssais, allowedPlmns etc.) shall trigger a "NF PROFILE CHANGED" notification from NRF 811, if the change of the NF Profile results in that the NF Instance starts or stops being authorized to be accessed by an NF having subscribed to be notified about NF profile changes.

[0093] On success, "204 No content" may be returned by the NF Service Consumer 810. On failure if the NF Service Consumer 810 does not consider the "nfStatusNotificationUri" as a valid notification URI, the NF Service Consumer 810 may return "404 Not Found" status code with the problem details as specified in TS 29.510 V18.7.0. In the case of redirection, the NF service consumer 810 shall return 3xx statuscode, which shall contain a Location header with an URI pointing to the endpoint of another NF service consumer 810 endpoint.

[0094] In any of processes 400, 500, 600, 700 or 800 described above, the RAN NF may either: (i) interact with other core NFs including the NRF directly via the SB A medium (for example, if the RAN NF includes some AMF functionality e.g., if the RAN NF is collocated with the AMF), or (ii) interact with other core NFs including the NRF via the AMF.

[0095] Figure 9 illustrates an example of a UE 900 in accordance with aspects of the present disclosure. The UE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0096] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0097] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the UE 900 to perform various functions of the present disclosure.

[0098] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the UE 900 to perform various functions describedherein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0099] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the UE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the UE 900 in accordance with examples as disclosed herein. The UE 900 may be configured to support a means for receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a first response message comprising the RAN profile.

[0100] The controller 906 may manage input and output signals for the UE 900. The controller 906 may also manage peripherals not integrated into the UE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0101] In some implementations, the UE 900 may include at least one transceiver 908. In some other implementations, the UE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

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

[0104] Figure 10 illustrates an example of a processor 1000 in accordance with aspects of the present disclosure. The processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein. The processor 1000 may optionally include at least one memory 1004, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0105] The processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) orother memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0106] The controller 1002 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. For example, the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0107] The controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction(s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein. The controller 1002 may be configured to track memory address of instructions associated with the memory 1004. The controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1002 may be configured to manage flow of data within the processor 1000. The controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1000.

[0108] The memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000). In some otherimplementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000).

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

[0110] The one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000). In some other implementations, the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000). One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.

[0111] The processor 1000 may support wireless communication in accordance with examples as disclosed herein. The processor 1000 may be configured to support a meansfor receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a first response message comprising the RAN profile. Alternatively, the processor 1000 may be configured to or operable to support a means for sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receiving, from the first network entity, a first response message comprising the RAN profile. Alternatively, the processor 1000 may be configured to or operable to support a means for sending, to a first network function, a second request message for registration of a RAN profile or deregistration of the RAN profile

[0112] Figure 11 illustrates an example of a NE 1100 in accordance with aspects of the present disclosure. The NE 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces. The NE 1100 may be a first network entity or a second network entity as described herein.

[0113] The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0114] The processor 1102 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). Insome implementations, the processor 1102 may be configured to operate the memory 1104. In some other implementations, the memory 1104 may be integrated into the processor 1102. The processor 1102 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the NE 1100 to perform various functions of the present disclosure.

[0115] The memory 1104 may include volatile or non-volatile memory. The memory 1104 may store computer-readable, computer-executable code including instructions when executed by the processor 1102 cause the NE 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1104 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0116] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the NE 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the NE 1100 in accordance with examples as disclosed herein. The NE 1100 may be configured to support a means for receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a first response message comprising the RAN profile. Alternatively, the NE 1100 may be configured to or operable to support a means for sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receiving, from the first network entity, a first response message comprising the RAN profile. Such a method tends to improve discovery of a RAN service by the second network entity. Alternatively,the NE 1100 may be configured to or operable to support a means for sending, to a first network function, a second request message for registration of a RAN profile or deregistration of the RAN profile.

[0117] The controller 1106 may manage input and output signals for the NE 1100. The controller 1106 may also manage peripherals not integrated into the NE 1100. In some implementations, the controller 1106 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1106 may be implemented as part of the processor 1102.

[0118] In some implementations, the NE 1100 may include at least one transceiver 1108. In some other implementations, the NE 1100 may have more than one transceiver 1108. The transceiver 1108 may represent a wireless transceiver. The transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or a combination thereof.

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

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

[0121] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a first network entity as described herein. In some implementations, the first network entity may execute a set of instructions to control the function elements of the first network entity to perform the described functions.

[0122] At 1202, the method 1200 may include receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a NE as described with reference to Figure 11.

[0123] At 1204, the method 1200 may include sending, to the second network entity, a first response message comprising the RAN profile. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a NE as described with reference to Figure 11.

[0124] It should be noted that the method 1200 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0125] Figure 13 illustrates a flowchart of a method 1300 in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a second network entity as described herein. In some implementations, the second network entity may execute a set of instructions to control the function elements of the second network entity to perform the described functions.

[0126] At 1302, the method 1300 may include sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RANservice is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a NE as described with reference to Figure 11.

[0127] At 1304, the method 1300 may include receiving, from the first network entity, a first response message comprising the RAN profile. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a NE as described with reference to Figure 11.

[0128] It should be noted that the method 1300 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0129] There is provided a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and send, to the second network entity, a first response message comprising the RAN profile. Such a first network entity tends to provide discovery of a RAN service by the second network entity.

[0130] The first network entity may be a network repository function (NRF). The first network entity may be part of a core network. The second network entity may be an NF service consumer. The RAN NF may be part of the core network. The core network may be a 5G core network. The RAN NF may provide one or more RAN services.

[0131] The RAN profile may relate to the RAN NF. The RAN profile may comprise a RAN NF profile. The RAN NF profile may comprise information relating to the RAN NF. The RAN profile may comprise a RAN NF service profile. The RAN NF service profilemay comprise information relating to the RAN NF service. The first network entity may contain the RAN NF profile. The first network entity may contain the RAN NF service profile. The first network entity may contain the RAN NF profile and the RAN NF service profile.

[0132] The first request message for discovering a RAN service may be a first request message for discovering the RAN service based on a RAN service requirement. The first request message may comprise an indication of configuration information for the RAN service. The first request message may be an NnrfNFDiscovery_Request message. The first response message may be an NnrfNFDiscovery_RequestResponse message.

[0133] Discovering the RAN service may comprise identifying the RAN service via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise identifying the RAN NF via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise identifying the RAN NF and the RAN service via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise selecting the RAN service via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise selecting the RAN NF via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise selecting the RAN service and RAN NF via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise identifying and selecting the RAN service via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise identifying and selecting the RAN NF via the first network entity based on a RAN service requirement. Discovering the RAN service may comprise identifying and selecting the RAN service and RAN NF via the first network entity based on a RAN service requirement.

[0134] The RAN service requirement may comprise at least one of: RAN NF capabilities, RAN NF allocated priority relative to other RAN NFs, RAN NF static capacity, RAN NF dynamic load information, RAN NF serving scope, locality related to the location of the RAN NF, RAN NF slice related information, RAN NF access permissions, and / or RAN NF vendor specific information. RAN NF serving scope may comprise a geographical operation scope of the RAN NF.

[0135] The RAN profile may be a RAN entry in the first network entity. The RAN profile may be a RAN NF entry in the first network entity. The RAN profile may be a RAN NF entry in a database of the first network entity. The RAN NF service may be a RAN NF instance.

[0136] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: receive, from the RAN NF, a second request message for registration of the RAN profile or deregistration of the RAN profile. The second request message may be an NnrfManagement_NFRegister_request message. The second request message may comprise an indication of configuration information for the RAN service.

[0137] The configuration information for the RAN service may comprise RAN NF information. The configuration information for the RAN service may comprise RAN NF information related data. RAN NF information may be information relating to the RAN NF that may assist a NF service consumer to use the RAN service.

[0138] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: send, to the RAN NF, a second response message comprising an indication of a successful registration the RAN profile or an indication of a successful deregistration the RAN profile. The second response message may be an NnrfManagement_NFRegister_response message.

[0139] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: receive, from the RAN NF, a third request message for replacement of an NF instance in the RAN profile.

[0140] The NF instance may contain at least a RAN service. The third request message may be a PUT request to the resource uniform resource identifier (URI) representing the NF instance. The third request message may comprise an indication of changes to the configuration information for the RAN service. A RAN instance may be a specific deployment or configuration of the RAN NF. The RAN NF may deploy one or more RAN instance.

[0141] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: send, to the RAN NF, a third response message comprising an indication of a successful replacement of the NF instance in the RAN profile.

[0142] The indication of a successful replacement of the NF instance in the RAN profile may comprise a 200 OK message. The indication of a successful replacement of the NF instance in the RAN profile may comprise a Bad Request. The indication of a successful replacement of the NF instance in the RAN profile may comprise a Internal Server Error.

[0143] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: receive, from the RAN NF, a fourth request message for updating a parameter of an NF instance in the RAN profile. The fourth request message may be a PATCH request to the resource URI representing the NF instance. The fourth request message may comprise an indication of changes to a parameter of the configuration information for the RAN service.

[0144] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: send, to the RAN NF, a fourth response message comprising an indication of a successful updating to the parameter of the NF instance in the RAN profile. The indication of a successful updating to the parameter of the NF instance in the RAN profile may comprise a 204 No Content message. The indication of a successful updating to the parameter of the NF instance in the RAN profile may comprise a 200 OK message. The indication of a successful updating to the parameter of the NF instance in the RAN profile may comprise a 404 Not Found message.

[0145] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: send, to the second network entity, a fifth request message comprising a notification of an update to the RAN profile. The fifth request message may be a POST request message. The fifth request message may be a POST request message to the callback URI. The fifth request message may comprise an indication of an update to the configuration information for the RAN service.

[0146] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: receive, from the second network entity, a fifth response message comprising an acknowledgment of the update to the RAN profile. The acknowledgement of the update to the RAN profile may comprise a 204 No content message. The acknowledgement of the update to the RAN profile may comprise a 404 Not Found message. The acknowledgement of the update to the RAN profile may comprise a 3xx message.

[0147] The RAN service may comprise at least one of: a radio resource management service; a self-organized network service executed by a base station; an Artificial Intelligence / Machine Learning, AI / ML, service and / or a RAN exposure service.

[0148] The RAN profile may comprise a parameter relating to the RAN NF or RAN service, wherein the parameter corresponds to at least one of: an offered service type; a permission, authentication and / or policy rule; a serving scope; a radio technology or a radio access characteristic; a spectrum or a coverage characteristic; a radio characteristic or a radio feature; a radio configuration parameter; and / or a type of radio access point.

[0149] The RAN profile may comprise a field for configuration information for the RAN service. The field for configuration information for the RAN service may be a RANNFInfo field. The configuration information for the RAN service may comprise a radio feature of the RAN NF. The field for configuration information for the RAN service may comprise at least one of: a ranfRegionld, an NfGroupId, an array(ServScope), an array(Rat), an array(Spect), a SpectrumTypeld, an array(Antenna), an array (RadioFeat), an array(RM), an array(RMode), an array(Coverage), an array(HOparam) and / or an array(Access). The RAN profile may comprise a RAN NF profile and / or a RAN NF service profile.

[0150] There is further provided a method performed by a first network entity, the method comprising: receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a firstresponse message comprising the RAN profile. Such a method tends to provide discovery of a RAN service by the second network entity.

[0151] The method may further comprise receiving, from the RAN NF, a second request message for registration of the RAN profile or deregistration of the RAN profile. The second request message may comprise an indication of configuration information for the RAN service.

[0152] The method may further comprise receiving, from the RAN NF, a third request message for replacement of an NF instance in the RAN profile. The method may further comprise receiving, from the RAN NF, a fourth request message for updating a parameter of an NF instance in the RAN profile.

[0153] The method may further comprise sending, to the second network entity, a fifth request message comprising a notification of an update to the RAN profile. The fifth request message may comprise an indication of an update to the configuration information for the RAN service.

[0154] The RAN service may comprise at least one of: a radio resource management service; a self-organized network service executed by a base station; an Artificial Intelligence / Machine Learning, AI / ML, service and / or a RAN exposure service.

[0155] The RAN profile may comprises a parameter relating to the RAN NF or RAN service, wherein the parameter corresponds to at least one of: an offered service type; a permission, authentication and / or policy rule; a serving scope; a radio technology or a radio access characteristic; a spectrum or a coverage characteristic; a radio characteristic or a radio feature; a radio configuration parameter; and / or a type of radio access point. The RAN profile may comprise a field for configuration information for the RAN service. The RAN profile may comprise a RAN NF profile and / or a RAN NF service profile.

[0156] There is further provided a second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the firstnetwork entity has stored therein a RAN profile relating to the RAN service; and receive, from the first network entity, a first response message comprising the RAN profile. Such a second network entity tends to improve discovery of a RAN service by the second network entity.

[0157] The at least one processor coupled with the at least one memory may be further configured to cause the second network entity to: receive, from the first network entity, a fifth request message comprising a notification of an update to the RAN profile. The fifth request message may comprise an indication of an update to the configuration information for the RAN service.

[0158] There is further provided a method performed by a second network entity, the method comprising: sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receiving, from the first network entity, a first response message comprising the RAN profile. Such a method tends to provide discovery of a RAN service by the second network entity.

[0159] There is further provided a method performed by a radio access network, RAN, network function, NF, the method comprising: sending, to a first network function, a second request message for registration of a RAN profile or deregistration of the RAN profile. The method may further comprise sending, to the first network function, a third request message for replacement of an NF instance in the RAN profile. The method may further comprise receiving, from the first network function, a third response message comprising an indication of a successful replacement of the NF instance in the RAN profile. The method may further comprise sending, to the first network function, a fourth request message for updating a parameter of an NF instance in the RAN profile. The method may further comprise receiving, from the first network function, a fourth response message comprising an indication of a successful updating to the parameter of the NF instance in the RAN profile.

[0160] Examples described herein relate to the SB A adoption for the RAN, in where there are no mechanisms for service discovery and selection that consider informationrelated to RAN functions for facilitating a core NF or an external entity, e.g., an AF, to select a RAN NF or a specific RAN service.

[0161] Examples described herein introduce the notion of a new RAN NF, which can appear into the SBA of the core network. Examples described herein enable discovery and selection mechanisms of a RAN NF including specific RAN services in 5G core network which tends to facilitate an effective and efficient interaction between RAN and core network.

[0162] In the past, SB As have not provided a means to discover and select RAN services from the mobile core network. Examples described herein relate to NF discovery and selection of a RAN NF or RAN NF Service; NF Profile Full or Partial Update when RAN NF Info parameters changes; and / or NRF Notification in the same PLMN related to RAN NF updates towards NF Service consumer.

[0163] There is further provided a network entity [repository function - NRF] for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: allow the discovery and selection of a second entity [RAN NF] and / or a service related to the said second entity [RAN NF Service]; receive configuration and / or updates related to radio parameters or other profile parameters that can assist in selecting a service offered by the said second entity of a wireless communication network; notify at least a third network entity [a subscribed NF to the NRF] that subscribed to receive updates regarding profile changes with respect to radio issues related to a second entity [RAN NF] and / or to at least a service related to the said second entity.

[0164] A second entity [RAN NF] may provide at least one of the following types of radio services that can offer to a third network entity [a core network NF - a subscribed NF to the NRF]: a radio resource management related service; a self-organized network related service; an artificial intelligence and / or machine learning related service; a radio exposure related service;

[0165] The network entity [NRF] may enable the discovery and selection of a second network entity by a third network entity based on at least one of the following parametersrelated to a second network entity: offered service types; permission and / or authentication and / or policy rules; serving scope; radio technology and radio access / connectivity characteristics; spectrum and coverage characteristics; radio characteristics and / or radio features; radio configuration parameters; type of radio access point.

[0166] The network entity [NRF] may enable the discovery and selection of a second network entity by a third network entity based on at least one of the following parameters related to the service offered by the second network entity: offered service information; permission and / or authentication and / or policy rules; serving scope; radio technology and radio access / connectivity characteristics; spectrum and coverage characteristics; radio characteristics and / or radio features; radio configuration parameters; type of radio access point.

[0167] The second entity [RAN NF] may be allowed to: register and / or register its radio services including the related parameters to the network entity to make them available; to fully update or partially update its radio services and the related parameters.

[0168] The third entity [RAN NF] may be allowed to: discover a second network entity and / or the radio services related to the second network entity; receive an update notification if the second network entity and / or the radio services related to the second network entity are updated in the network entity.

[0169] There is further provided a method that allows a service discovery and selection across the radio access network and core network by: introducing a radio network function in the core network repository function that contains the related service and other operation related parameters.

[0170] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0171] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0172] The following abbreviations are relevant in the field addressed by this document: 6G - 6th Generation of Mobile Communications, AF - Application Function, AI / ML - Artificial Intelligence / Machine Learning, AMF - Access Management Function, ComP - Coordinated multipoint oPeration, CP - Control Plane, CU / CU - Centralized Unit / Distributed Unit, DN - Data Network, DRB - Data Radio Bearer, D-SON - Distributed-SON, FDD - Frequency Division Duplexing, FQDN - Fully Qualified Domain Name, gNB - general Node B, HTTP - Hypertext Transfer Protocol, JSON - JavaScript Object Notation, LMF - Location Management Function, LTE - Long Term Evolution, MNO - Mobile Network Operator, NEF - Network Exposure Function, NF - Network Function, NG-RAN - Next Generation RAN, NR - New Radio, NRF - Network Repository Function, NSI - Network Slice Instance, NWDAF - Network Data Analytics Function, 0AM - Operations, Administration and Maintenance, PCF - Policy Control Function, PLMN - Public Land Mobile Network, QoS - Quality of Service, RAN - Radio Access Network, RAT - Radio Access Technology, RRM - Radio Resource Management, SBA - Service Based Architecture, SCP - Service Communication Proxy, SMF - Session Management Function, SNPN - Standalone Non-Public Network, S-NSSAI - Single Network Slice Selection Assistance Information, SON - Self-Organized Networks, TDD - Time Division Duplexing, UDM / UDR - User Data Management / Unified Data Repository, UE - User Equipment, UL / DL - Uplink / Downlink, UP - User Plane, UPF - User Plane Function, URI - Uniform Resource Identifier.

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and send, to the second network entity, a first response message comprising the RAN profile.

2. The first network entity of claim 1 , wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to: receive, from the RAN NF, a second request message for registration of the RAN profile or deregistration of the RAN profile.

3. The first network entity of claim 2, wherein the second request message comprises an indication of configuration information for the RAN service.

4. The first network entity of claim 1 , wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to: receive, from the RAN NF, a third request message for replacement of an NF instance in the RAN profile.

5. The first network entity of claim 1, wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to: receive, from the RAN NF, a fourth request message for updating a parameter of an NF instance in the RAN profile.

6. The first network entity of any one of claims 1 to 5, wherein the at least one processor coupled with the at least one memory is further configured to cause the first network entity to: send, to the second network entity, a fifth request message comprising a notification of an update to the RAN profile.

7. The first network entity of claim 6, wherein the fifth request message comprises an indication of an update to the configuration information for the RAN service.

8. The first network entity of any one of claims 1 to 7, wherein the RAN service comprises at least one of: a radio resource management service; a self-organized network service executed by a base station; an Artificial Intelligence / Machine Learning, AI / ML, service and / or a RAN exposure service.

9. The first network entity of any one of claims 1 to 8, wherein the RAN profile comprises a parameter relating to the RAN NF or RAN service, wherein the parameter corresponds to at least one of: an offered service type; a permission, authentication and / or policy rule; a serving scope; a radio technology or a radio access characteristic; a spectrum or a coverage characteristic; a radio characteristic or a radio feature; a radio configuration parameter; and / or a type of radio access point.

10. The first network entity of any one of claims 1 to 9, wherein the RAN profile comprises a field for configuration information for the RAN service.

11. The first network entity of any one of claims 1 to 10, wherein the RAN profile comprises a RAN NF profile and / or a RAN NF service profile.

12. A method performed by a first network entity, the method comprising: receiving, from a second network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and sending, to the second network entity, a first response message comprising the RAN profile.

13. A second network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network entity to: send, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN network function, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receive, from the first network entity, a first response message comprising the RAN profile.

14. The second network entity of claim 13, wherein the at least one processor coupled with the at least one memory is further configured to cause the second network entity to: receive, from the first network entity, a fifth request message comprising a notification of an update to the RAN profile.

15. A method performed by a second network entity, the method comprising: sending, to a first network entity, a first request message for discovering a radio access network, RAN, service, wherein the RAN service is provided by a RAN networkfunction, NF, and wherein the first network entity has stored therein a RAN profile relating to the RAN service; and receiving, from the first network entity, a first response message comprising the RAN profile.

Images