Method for opening wireless access network information

Abstract

A wireless communication method used in a network opening function is provided. The wireless communication method includes: receiving a subscription address in a wireless access network from a session management function of a core network, sending a subscription request to the subscription address in the wireless access network, and receiving wireless access network information corresponding to the subscription request from the wireless access network.

Description

Technical Field

[0001] This document generally relates to wireless communications. Background Art

[0002] Multi-access edge computing (MEC) enables running MEC applications at the edge of the network in an environment characterized by low latency, short distance, high bandwidth, and openness to location and up-to-date radio access network information. Radio access network information about the current wireless status is shared via the MEC platform through the Radio Network Information Service (RNIS). RNIS is a service that provides wireless network related information to MEC applications and the MEC platform. Typical information that can be provided by the MEC platform is as follows:

[0003] - Latest radio access network information about wireless network conditions;

[0004] - Measurement information related to the user plane (e.g. latency);

[0005] - Information about User Equipment (UE) connected to the radio nodes associated with the MEC host, the context of these UEs and the related radio access bearers;

[0006] - Changes in information related to UEs connected to the radio nodes associated with the MEC host, the context of these UEs, and the related radio access bearers.

[0007] MEC applications and MEC platforms can use radio access network information to optimize existing services and provide new services based on the latest information about radio conditions.

[0008] Figure 1 A schematic diagram of the network architecture is shown. Figure 1 In the network architecture, the network architecture includes the following network components and / or network functions:

[0009] (1) UE: User Equipment

[0010] (2) RAN: Radio Access Network

[0011] (3)SMF: Session Management Function

[0012] SMF includes the following functions: session establishment, modification and release, UE Internet Protocol (IP) address allocation and management (including optional authorization function), user plane (UP) function selection and control, downlink data notification, etc.

[0013] (4)AMF: Access and Mobility Management Function

[0014] AMF includes the following functions: registration management, connection management, reachability management and mobility management. AMF can also perform access authentication and access authorization. In addition, AMF is a non-access layer (Non-Access-Stratum, NAS) security terminal and relays session management (Session Management, SM) NAS between UE and SMF.

[0015] (5) UPF: User Plane Function

[0016] UPF includes the following functions: serving as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, UP Quality-of-Service (QoS) processing, downlink packet buffering, and downlink data notification triggering.

[0017] (6)NEF: Network Open Function

[0018] NEF supports opening network capabilities and events to application functions (AF). Third-party applications can call network services via NEF, and NEF performs authentication and authorization of third-party applications. NEF also provides conversion of information exchanged with AF and information exchanged with internal network functions. Figure 1 As shown, RNIS can be combined with the functionality of NEF.

[0019] (7) AF: Application Function

[0020] AF and core network ( Figure 1 AFs (not shown) interact with the NEF to provide services, such as supporting the impact of applications on traffic routing, accessing network open functions, interacting with the policy framework for policy control, etc. The AF can be considered to be trusted by the network operator and can be allowed to interact directly with related network functions. AFs that are not allowed to directly access related network functions by the operator can use external open frameworks to interact with related network functions via NEF. Figure 1 In the present invention, AF can be a MEC application or a MEC platform, which is a consumer of radio access network information.

[0021] (8) PCF: Policy Control Function

[0022] PCF provides policy rules to the control plane functions to implement the policy rules. Specifically, PCF provides access and mobility related policies to AMF, and AMF implements the provided policies during the mobility process. In addition, PCF can provide policies related to UE access selection and protocol data unit (PDU) session selection (such as UE policies) to AMF, and AMF forwards these policies to the UE. In addition, PCF can provide policies related to session management to SMF, and these policies are implemented by SMF. PCF can be deployed in a distributed manner, and each distributed PCF can support different functions in the same public land mobile network (PLMN). After receiving a request from AF, PCF uses the UE address or UE identity to bind the request to the associated PDU session, and updates the application management (AM) policy or session management (SM) policy accordingly.

[0023] (9) UDR: Unified Data Repository

[0024] UDR supports unified data management (UDM) Figure 1 The UDR and the NF service consumer are located in the same PLMN, and data is stored in and retrieved from the UDR by using the Nudr interface.

[0025] exist Figure 1 In the UE, RAN, AMF, SMF, UPF, PCF, NEF, AF and UDR communicate by using corresponding interfaces. For example, UE communicates with RAN via Uu interface, RAN communicates with AMF via N2 interface, etc.

[0026] In the prior art, there is no direct interface between the NEF (RNIS) and the RAN. Therefore, how the NEF (RNIS) obtains the radio access network information from the RAN has become a topic of discussion. Summary of the invention

[0027] The present invention relates to a method, system and device for opening radio access network information, and more particularly to a method, system and device for providing radio access network information from a RAN to a NEF (RNIS).

[0028] The present disclosure relates to a wireless communication method used in a network open function. The wireless communication method includes:

[0029] receiving a subscription address in the radio access network from a session management function of the core network,

[0030] sending a subscription request to a subscription address in the wireless access network, and

[0031] Radio access network information corresponding to the subscription request is received from the radio access network.

[0032] Various embodiments may preferably implement the following features:

[0033] Preferably, the wireless communication method further includes:

[0034] receiving a radio access network information request for radio access network information from an application function of the core network, and

[0035] A subscription container is sent to a unified data repository, the subscription container including a request for radio access network information and a notification address for radio access network information in a network open function.

[0036] Preferably, the radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

[0037] Preferably, the subscription request includes at least one event related to the radio access network.

[0038] Preferably, at least one event related to the wireless access network includes at least one of the following: detecting a cell change, detecting a wireless access bearer event related to a wireless access bearer, wherein the wireless access bearer event includes at least one of establishment, modification or release, measuring the wireless terminal, configuring carrier aggregation for the wireless terminal, or expiration of a subscription request.

[0039] Preferably, the wireless communication method further includes:

[0040] Receive quality of service flow binding information from the session management function,

[0041] receiving at least one quality of service flow identifier from a wireless terminal, a radio access network, or a user plane function, and

[0042] The radio access network information is sent to the application function based on the quality of service binding information and the at least one quality of service flow identifier.

[0043] Preferably, the quality of service flow binding information includes service data flow information and a quality of service flow identifier associated with the service data flow information.

[0044] The present disclosure relates to a wireless communication method used in a wireless access network. The wireless communication method includes:

[0045] sending a subscription address in the radio access network to the session management function,

[0046] Receive a subscription request from the network open function, and

[0047] The wireless access network information is sent to the network open function based on the subscription request.

[0048] Various embodiments may preferably implement the following features:

[0049] Preferably, the wireless communication method further comprises receiving a subscription container from an access and mobility management function, the subscription container comprising a radio access network information request and a notification address for radio access network information in a network open function.

[0050] Preferably, the radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

[0051] Preferably, the subscription request includes at least one event related to the radio access network.

[0052] Preferably, at least one event related to the wireless access network includes at least one of the following: detecting a cell change, detecting a wireless access bearer event related to a wireless access bearer, wherein the wireless access bearer event includes at least one of establishment, modification or release, measuring the wireless terminal, configuring carrier aggregation for the wireless terminal, or expiration of a subscription container.

[0053] Preferably, the wireless communication method further comprises sending at least one quality of service flow identifier and radio access network information to a network open function.

[0054] The present disclosure relates to a wireless communication method used in a session management function. The wireless communication method includes:

[0055] receiving a subscription address in the radio access network from the radio access network, and

[0056] The subscription address in the wireless access network is sent to the network opening function.

[0057] Various embodiments may preferably implement the following features:

[0058] Preferably, the wireless communication method further includes:

[0059] receiving a subscription container from a policy control function, the subscription container including a radio access network information request and a notification address in a network open function, and

[0060] The subscription container is sent to the wireless access network.

[0061] Preferably, the wireless communication method further comprises sending forwarding information to the user plane function, wherein the forwarding information comprises a notification address in the network open function.

[0062] Preferably, the radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

[0063] Preferably, the subscription request includes at least one event related to the radio access network.

[0064] Preferably, at least one event related to the wireless access network includes at least one of the following: detecting a cell change, detecting a wireless access bearer event related to a wireless access bearer, wherein the wireless access bearer event includes at least one of establishment, modification or release, measuring the wireless terminal, configuring carrier aggregation for the wireless terminal, or expiration of a subscription request.

[0065] Preferably, the wireless communication method further comprises sending quality of service flow binding information to a network open function.

[0066] Preferably, the quality of service flow binding information includes service data flow information and a quality of service flow identifier associated with the service data flow information.

[0067] The present disclosure relates to a wireless communication method used in a wireless access network, the wireless communication method comprising:

[0068] receiving a subscription container from an access and mobility management function, the subscription container including a notification address in a radio access network information request and a network open function, and

[0069] Based on the subscription container, the radio access network information is sent to the user plane function.

[0070] Various embodiments may preferably implement the following features:

[0071] Preferably, the radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

[0072] Preferably, at least one event related to the wireless access network includes at least one of the following: detecting a cell change, detecting a wireless access bearer event related to a wireless access bearer, wherein the wireless access bearer event includes at least one of establishment, modification or release, measuring the wireless terminal, configuring carrier aggregation for the wireless terminal, or expiration of a network information request.

[0073] Preferably, the wireless communication method further comprises sending at least one quality of service flow identifier associated with the radio access network information to a user plane function.

[0074] Preferably, the wireless communication method further comprises receiving, from a session management function, information configuring a dedicated quality of service flow for transmitting the radio access network information.

[0075] The present disclosure relates to a wireless communication method used in a user plane function. The wireless communication method includes:

[0076] receiving forwarding information from a session management function, the forwarding information including a notification address for receiving wireless access network information in a network open function;

[0077] receiving radio access network information from the radio access network, and

[0078] The wireless access network information is sent to the network open function based on the forwarding information.

[0079] Various embodiments may preferably implement the following features:

[0080] Preferably, the wireless communication method further includes:

[0081] receiving at least one quality of service flow identifier associated with the radio access network information from the radio access network, and

[0082] At least one quality of service flow identifier is sent to a network open function.

[0083] Preferably, the wireless communication method further comprises receiving, from a session management function, information configuring a dedicated quality of service flow for receiving radio access network information.

[0084] The present disclosure relates to a network device. The network device includes a communication unit, which is configured to:

[0085] receiving a subscription address in the radio access network from a session management function of the core network,

[0086] sending a subscription request to a subscription address in the wireless access network, and

[0087] Radio access network information corresponding to the subscription request is received from the radio access network.

[0088] Various embodiments may preferably implement the following features:

[0089] Preferably, the network device further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0090] The present disclosure relates to a wireless access network. The wireless access network includes a communication unit, which is configured to:

[0091] sending a subscription address in the radio access network to the session management function,

[0092] Receive a subscription request from the network open function, and

[0093] The wireless access network information is sent to the network open function based on the subscription request.

[0094] Various embodiments may preferably implement the following features:

[0095] Preferably, the radio access network further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0096] The present disclosure relates to a network device. The network device includes a communication unit, which is configured to:

[0097] receiving a subscription address in the radio access network from the radio access network, and

[0098] The subscription address in the wireless access network is sent to the network opening function.

[0099] Various embodiments may preferably implement the following features:

[0100] Preferably, the network device further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0101] The present disclosure relates to a wireless access network. The wireless access network includes a communication unit, which is configured to:

[0102] receiving a subscription container from an access and mobility management function, the subscription container including a radio access network information request and a notification address in a network open function,

[0103] Based on the subscription container, the radio access network information is sent to the user plane function.

[0104] Various embodiments may preferably implement the following features:

[0105] Preferably, the radio access network further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0106] The present disclosure relates to a network device. The network device includes a communication unit, which is configured to:

[0107] receiving forwarding information from a session management function, the forwarding information including a notification address for receiving wireless access network information in a network open function,

[0108] receiving radio access network information from the radio access network, and

[0109] The wireless access network information is sent to the network open function based on the forwarding information.

[0110] Various embodiments may preferably implement the following features:

[0111] Preferably, the network device further comprises a processor, wherein the processor is configured to execute any one of the above wireless communication methods.

[0112] The exemplary embodiments disclosed herein are intended to provide features that will become apparent with reference to the following description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example, not as a limitation, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments without departing from the scope of this disclosure.

[0113] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged without departing from the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented. BRIEF DESCRIPTION OF THE DRAWINGS

[0114] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims.

[0115] Figure 1 A schematic diagram showing the network structure.

[0116] Figure 2 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0117] Figure 3 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0118] Figure 4 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0119] Figure 5 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0120] Figure 6 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0121] Figure 7 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0122] Figure 8 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.

[0123] Fig. 9 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.

[0124] Fig.10 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.

[0125] Fig.11 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.

[0126] Fig.12 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0127] Figure 2 A schematic diagram of a wireless terminal 20 according to an embodiment of the present disclosure is provided. The wireless terminal 20 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, and this document is not limited to this. The wireless terminal 20 may include a processor 200 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 210, and a communication unit 220. The storage unit 210 may be any data storage device that stores program code 212 accessed and executed by the processor 200. Embodiments of the storage unit 210 include, but are not limited to, a subscriber identity module (Subscriber Identity Module, SIM), a read-only memory (Read-Only Memory, ROM), a flash memory, a random access memory (Random-Access Memory, RAM), a hard disk, and an optical data storage device. The communication unit 220 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 200. In one embodiment, the communication unit 220 communicates via Figure 2 At least one antenna 222 is shown for transmitting and receiving signals.

[0128] In an embodiment, the storage unit 210 and the program code 212 may be omitted, and the processor 200 may include a storage unit storing the program code.

[0129] The processor 200 may implement any one of the steps of the exemplary embodiments on the wireless terminal 20 , for example, by executing the program code 212 .

[0130] The communication unit 220 may be a transceiver. Alternatively or additionally, the communication unit 220 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless network node (eg a base station), respectively.

[0131] Figure 3A schematic diagram of a radio network node 30 according to an embodiment of the present disclosure is provided. The radio network node 30 may be a network device, a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network or a radio network controller (RNC), and this document is not limited thereto. In addition, the radio network node 30 may include (execute) at least one network function and / or at least one service, such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), an application function (AF), a network exposure function (NEF), a RAN network information service (RNIS), a multi-access edge computing (MEC), etc. The radio network node 30 may include a processor 300, such as a microprocessor or an ASIC, a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device that stores a program code 312 accessed and executed by the processor 300. Examples of the storage unit 312 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 320 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 300. In one example, the communication unit 320 communicates via Figure 3 At least one antenna 322 is shown for transmitting and receiving signals.

[0132] In one embodiment, the storage unit 310 and the program code 312 may be omitted. The processor 300 may include a storage unit having stored program code.

[0133] The processor 300 may implement any steps described in the exemplary embodiments on the radio network node 30 , for example by executing the program code 312 .

[0134] The communication unit 320 may be a transceiver. Alternatively or additionally, the communication unit 320 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless terminal (eg, a user equipment), respectively.

[0135] In one embodiment, the NEF (and / or AF (MEC)) may subscribe to at least one event and / or radio access network information (i.e., RAN information) in the RAN via control plane signaling. In this case, the RAN may send, report, or notify the NEF of the at least one event and / or RAN information directly or via the user plane. In one embodiment, after receiving the at least one event and / or RAN information, the NEF may subscribe to new events and / or adjust existing events directly to the RAN.

[0136] The following embodiments illustrate more details of how NEF subscribes to events and / or RAN information in RAN and how RAN reports the subscribed events and / or RAN information to NEF (or other network functions of the core network). It should be noted that those skilled in the art should recognize that these embodiments may be implemented individually or in any possible combination.

[0137] Embodiment 1:

[0138] In this embodiment, the AF may request the RAN information of the RAN through the core network.

[0139] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 4 In the process, the PCF subscribes to any modification of the application data in the UDR (e.g., sends a corresponding subscription request) (step 401). Typically, the UDRs that the PCF is configured to subscribe to are deployed near the PCF. For example, the PCF may only subscribe to events (e.g., modifications) in the UDRs in the same province or region.

[0140] In step 402, the UDR stores the subscription and sends a response to the PCF.

[0141] In step 403, the AF sends (e.g., transmits) an AF request (e.g., a request for RAN information, hereinafter referred to as a RAN information request) to the NEF (RNIS). The content of the AF request may include the following information:

[0142] (A) UE address (e.g., Internet Protocol (IP) address or Ethernet address), Data Network Name (DNN), Single-Network Slice Selection Assistance Information (S-NSSAI):

[0143] This information is used to identify the PDU session that is the subject of the AF request message. In one embodiment, the AF request message can target an already established PDU session. In this case, the address of the UE is included. In one embodiment, the AF request message can target a future PDU session (which does not currently exist). In this embodiment, only the DNN and S-NSSAI are included.

[0144] (B) Generic Public Subscription Identifier (GPSI) and / or External Group Identifier:

[0145] The GPSI and / or the external group identifier are used to identify a specific UE or a group of UEs. The NEF may convert the external group identifier into an internal group identifier. If neither the GPSI nor the external group identifier is provided, the AF request message targets any UE.

[0146] (C) Quality-of-service (QoS) monitoring:

[0147] The AF requests monitoring of the QoS delay between the UE and the anchor UPF. When the QoS delay reaches a threshold, the core network (e.g., 5G system) reports the packet delay to the AF. The delay request can be requested on a per-UE basis or on a per-service data flow basis. The AF can request reporting of downlink (DL) packet delay, uplink (UL) packet delay, and / or round-trip packet delay.

[0148] (D) Alternative QoS reference:

[0149] The Alternative QoS Reference is an array indicating alternative QoS requirements for each traffic filter. The PCF / SMF generates alternative QoS profiles for the associated Guaranteed Bit Rate (GBR) QoS flow. The RAN can select a suitable QoS profile for the GBR QoS flow based on the current radio conditions and notify the AF of the reference index of the selected QoS profile / QoS requirement. Therefore, the AF is able to know the current QoS conditions and adjust the application layer traffic.

[0150] (E) Wireless network information request:

[0151] The RAN information request may include information about the target RAN and / or events related to the target RAN. In one embodiment, the events related to the target RAN include at least one of the following:

[0152] -Detect cell changes:

[0153] When the RAN detects a cell change, the RAN reports its latest cell information.

[0154] -Detection of Radio Access Bearer (RAB) establishment / modification / release:

[0155] When the establishment, modification and / or release of a RAB is detected, the RAN reports the latest RAB information.

[0156] - Take measurements:

[0157] When the RAN performs a new UE measurement, the RAN reports the corresponding UE measurement report.

[0158] -Perform UE Timing Advance (TA) measurements:

[0159] When the RAN performs a new UE TA measurement, the RAN reports the corresponding UE TA measurement.

[0160] - (Re)Configure Carrier Aggregation for UE:

[0161] When the UE (re)configures carrier aggregation for the UE, the RAN reports the new carrier aggregation configuration.

[0162] - Subscription expiration

[0163] When expiration of an existing subscription is detected, the RAN reports the expiration of the subscription.

[0164] In one embodiment, the AF request (ie, RAN information request) may further include an AF transaction identifier.

[0165] In step 404: NEF ensures necessary authorization control, including AF request throttling, mapping from information provided by AF to information required by the core network (e.g., 5G core network). For example, NEF can map AF service identifier to DNN and S-NSSAI, or map external group identifier to internal group identifier.

[0166] In addition, the NEF sends AF request information to the UDR and stores the AF request information as application data in the UDR. In one embodiment, when the AF requests RAN information, the NEF stores a RAN information subscription container in the UDR. The RAN information subscription container includes information related to the target RAN and at least one of a notification target in the NEF, wherein the notification target includes a Uniform Resource Identifier (URI), which is an address for receiving the corresponding notification and associating the notification with the subscription. In one embodiment, the RAN information subscription container may also include requested events (e.g., events included in the RAN information request). Alternatively or in addition, the NEF may subscribe to events related to the target RAN at a subsequent stage.

[0167] In step 405, the NEF responds to the AF via an AF response.

[0168] In step 406, the PCF, which has subscribed to notification from the UDR in step 401, receives a notification of application data change (eg, Nudr_DM_Notify notification) from the UDR, and stores the notification of application data change locally.

[0169] Embodiment 2:

[0170] In this embodiment, the core network sends the subscription to the RAN.

[0171] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 5 In step 501, the PCF sends an SM association update notification to the SMF of the PDU session. In one embodiment, the PCF receives a notification of an application data change from the UDR, selects a PDU session associated with the application data change, and sends an SM association update notification (e.g., Figure 4 In one embodiment, the SM association update notification includes a RAN information subscription container received from the UDR.

[0172] In step 502, the SMF sends a Namf_communication_N1N2MessageTransfer message to the AMF, wherein the Namf_communication_N1N2MessageTransfer message includes the RAN information subscription container received from the PCF.

[0173] In step 503, the AMF sends an N2 PDU session request message to the RAN, wherein the N2 PDU session request message includes the RAN information subscription container received from the SMF.

[0174] In step 504, the RAN responds to the AMF with an N2 PDU Session Response message including a RAN Information Container. In one embodiment, the RAN Information Container includes a subscription address (e.g., a URI) identifying an address in the RAN for receiving further subscription requests and associating further subscription requests from the AF and / or NEF with the current subscription. In one embodiment, the subscription address may be specific to a single PDU Session or a single UE.

[0175] In step 505, AMF sends a Nsmf_PDUSession_UpdateSMContext request to SMF, wherein the Nsmf_PDUSession_UpdateSMContext request message includes a RAN information container.

[0176] In step 506, SMF returns a Nsmf_PDUSession_UpdateSMContext response message to AMF.

[0177] Then, in step 507, the SMF sends a notification to the NEF, wherein the notification includes a RAN information container. The NEF receives the notification message and stores the subscription address (e.g., URI) in the RAN. In one embodiment, for security reasons, the NEF does not forward the subscription address (e.g., URI) in the RAN to the AF (MEC) in the notification message.

[0178] After receiving the subscription address, the NEF confirms the address providing the RAN information. Therefore, the NEF can send further subscription requests for the RAN information directly to the subscription address, rather than sending the subscription request via the control plane.

[0179] In an embodiment regarding QoS monitoring, the SMF may also report to the NEF the pre-configured downlink / uplink / round trip delay (i.e., Uu delay) between the RAN and the anchor UPF. Therefore, after receiving the Uu delay, the NEF is able to calculate the total delay between the UE and the anchor UPF.

[0180] In one embodiment, the requested RAN information for the AF (MEC) may need to be based on each service data flow. For example, the requested RAN information may require the packet delay of the service data flow. However, the RAN only reports the RAN information on a per QoS flow basis. Therefore, the SMF may report the QoS flow binding information of the service data flow to the NEF. In one embodiment, the QoS flow binding information includes the service data flow information and the associated QoS flow ID (e.g., associated with the service data flow information).

[0181] In step 508, based on the QoS flow binding information received from the SMF, the NEF determines the associated service data flow and sends a notification to the AF (MEC), wherein the notification includes the RAN information associated with the service data flow.

[0182] In one embodiment, the AF(MEC) may send a further subscription request for further RAN information.

[0183] Embodiment 3:

[0184] In this embodiment, the RAN sends the notification directly to the NEF.

[0185] Figure 6 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 6 In the example, the RAN determines (e.g., detects) that an event indicated by a subscription request from the NEF (and / or AF (MEC)) is triggered (e.g., a cell change is detected) (step 601). In one embodiment, the NEF (AF (MEC)) may Figure 4 and / or Figure 5 The process shown subscribes to an event in the RAN. More specifically, for each subscription request, the RAN may send a corresponding notification to the core network (e.g., NEF) immediately, periodically, or after detecting an event in a subscription request previously received from the NEF, as follows:

[0186] -QoS Monitoring:

[0187] When the latency threshold is reached, the RAN reports the UL / DL / round trip packet delay of the Uu (air) interface in a notification. This report can be on a per QoS flow basis or on a per UE basis. The NEF calculates the total delay between the UE and the anchor UPF taking into account the UL / DL / round trip packet delay on the Uu interface. In one embodiment, the RAN can also calculate the DL packet delay between the RAN and the anchor UPF based on the information provided by the UPF, and report the DL packet delay to the NEF. In one embodiment, the DL and UL packet delays between the RAN and the anchor UPF can also be pre-configured or dynamically calculated and sent from the SMF to the NEF.

[0188] -Alternative QoS reference:

[0189] When RAN uses different QoS profiles for GBR QoS flows, RAN reports the reference index of the currently used QoS profile to NEF. Therefore, NEF knows the current QoS status and reports the QoS status to AF, and AF can adjust the packet delivery rate based on the reported QoS status.

[0190] Wireless Network Information Request:

[0191] After the RAN detects the event in the RAN information request, the RAN reports the requested RAN information according to the request.

[0192] In step 602, the RAN directly sends a notification to the notification target (ie, notification address) in the NEF, wherein the notification includes the requested RAN information. In one embodiment, the requested RAN information may also include a QoS flow ID of a service data flow associated with the requested RAN information.

[0193] In step 603, based on the QoS flow binding information received from the SMF and the QoS flow ID received from the RAN, the NEF determines the associated service data flow and sends a notification to the AF (MEC), wherein the notification includes the RAN information associated with the service data flow. That is, the NEF sends a notification to the notification target of the AF (MEC), wherein the notification includes the requested RAN information received from the RAN.

[0194] In step 604, the AF (MEC) may send a subscription request (eg, Figure 4 The wireless information request in step 403 shown) subscribes to further events or adjusts existing events.

[0195] In step 605, the NEF sends a subscription request directly to a subscription address (eg, URI) in the RAN. In this embodiment, the RAN stores the subscription event and can respond to the NEF with a confirmation message ( Figure 6 not shown).

[0196] Embodiment 4:

[0197] In this embodiment, the RAN sends a notification (ie, requested RAN information) to the NEF via the user aspect.

[0198] Figure 7 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 7 In step 701, the SMF sends an N4 session modification request to configure the UPF, wherein the N4 session modification request includes the notification address in the NEF. Based on the notification address in the NEF, the UPF can forward the notification to the associated NEF. (Step 701)

[0199] In one embodiment, the SMF may configure a dedicated QoS flow between the RAN and the UPF for each NEF to deliver the corresponding notification. In this embodiment, the SMF provides information to both the UPF and the RAN to configure the dedicated QoS flow. As a result, the RAN can send notification messages through the dedicated QoS flow, and the UPF can detect the notification message based on the QoS flow ID in the General Packet Radio Service Tunneling Protocol-U (GTP-U) header.

[0200] In step 702, the UPF returns an N4 session modification response to the SMF.

[0201] In step 703, the RAN determines (e.g., detects) that an event indicated by a subscription request from the NEF (and / or AF (MEC)) is triggered. For each subscription request, the RAN may send a corresponding notification to the core network (e.g., NEF) immediately, periodically, or after detecting an event in a subscription request previously received from the NEF, as follows:

[0202] -QoS Monitoring:

[0203] If the latency threshold is reached, the RAN reports the UL / DL / round-trip packet delay of the Uu (air) interface. The report can be based on each QoS flow or on each UE. The NEF calculates the total delay between the UE and the anchor UPF taking into account the UL / DL / round-trip packet delay on the Uu interface. In one embodiment, the RAN can also calculate the DL packet delay between the RAN and the anchor UPF based on the information provided by the UPF, and report the DL packet delay to the NEF. In one embodiment, the UPF also calculates the UL packet delay and sends the UL packet delay to the NEF in a subsequent step (e.g., step 705). In one embodiment, the DL and UL packet delays between the RAN and the anchor UPF can be pre-configured or dynamically calculated and sent from the SMF to the NEF.

[0204] -Alternative QoS reference:

[0205] When the RAN uses different QoS profiles for the GBR QoS flow, the RAN reports the reference index of the currently used QoS profile to the NEF. Accordingly, the NEF confirms the current QoS status and reports the QoS status to the AF.

[0206] Wireless Network Information Request:

[0207] After the RAN detects the event in the RAN information request, the RAN reports the requested (eg, subscribed) RAN information according to the request.

[0208] In step 704, the RAN sends a notification to the UPF via the user side of the PDU session, wherein the notification includes the requested RAN information and the associated QoS flow ID (optional).

[0209] In step 705, based on the forwarding information provided by the SMF, the UPF forwards the notification to the notification target (notification address) of the associated NEF, wherein the forwarded notification may include the requested RAN information and the associated QoS flow ID (optional).

[0210] Regarding QoS monitoring, the UPF may calculate the UL packet delay based on information provided by the RAN, and report the UL packet delay to the NEF.

[0211] In step 706, based on the QoS flow binding information received from the SMF and the QoS flow ID received from the RAN, the NEF determines the associated service data flow and sends a notification to the notification target of the AF (MEC), wherein the sent notification includes the requested RAN information received from the RAN.

[0212] In step 707, the AF (MEC) may subscribe to further events via the NEF. In one embodiment, as described in embodiments 1 and 2, the NEF may send a new subscription request to the RAN via the control plane. Alternatively or in addition, the NEF may send a new subscription request directly to the RAN, as described in embodiment 3 (e.g., steps 604 and 605).

[0213] Figure 8 A flow chart of a process according to an embodiment of the present application is shown. The process can be used for NEF (RNIS) and includes the following steps:

[0214] Step 801: receiving a subscription address in RAN from SMF;

[0215] Step 802: Send a subscription request to a subscription address in the RAN; and

[0216] Step 803: Receive RAN information corresponding to (eg, associated with) the subscription request from the RAN.

[0217] In this embodiment, the NEF may receive a subscription address in the RAN from the SMF of the core network to send a subsequent subscription request for specific RAN information. After receiving the subscription address, the NEF directly sends a subscription request to the RAN and directly receives the subscribed RAN information from the wireless network.

[0218] In one embodiment, the NEF may receive a RAN information request for specific RAN information from the AF, and send a subscription container including the RAN information request and a notification address in the NEF. In one embodiment, the RAN information request includes at least one of information related to the RAN or at least one event related to the RAN. In one embodiment, the notification address in the NEF is used to receive subscribed RAN information (e.g., notification of a subscribed event).

[0219] In one embodiment, the NEF may include at least one subscribed event in the subscription request (ie, step 802).

[0220] In one embodiment, at least one subscribed event includes at least one of the following:

[0221] Detect cell changes,

[0222] detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release,

[0223] Performing measurements on a wireless terminal (such as a UE),

[0224] Configure carrier aggregation for wireless terminals, or

[0225] The subscription request expired.

[0226] In one embodiment, the NEF receives QoS flow binding information from the SMF, wherein the QoS flow binding information may include service data flow information and a QoS flow ID associated with the service data flow information. In addition, the NEF may receive a QoS flow identifier associated with the subscribed RAN information from the RAN, SMF, or UPF. Based on the QoS flow binding information and at least one QoS flow identifier, the NEF can send the subscribed RAN information to the AF based on each service data flow identifier.

[0227] Fig. 9 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Fig. 9 The process shown may be used for RAN and comprises the following steps:

[0228] Step 901: Send the subscription address in RAN to SMF;

[0229] Step 902: Receive a subscription request from NEF; and

[0230] Step 903: Based on the subscription request, RAN information is sent to the NEF.

[0231] More specifically, the RAN sends a subscription address in the RAN to the SMF to receive a subsequent subscription request. Next, the RAN receives the subscription request from the NEF and sends the subscribed RAN information based on the subscription request.

[0232] In one embodiment, the RAN receives a subscription container from the AMF, the subscription container including a RAN information request and a notification address for RAN information in a network exposure function.

[0233] In an embodiment, the RAN information request includes at least one of information related to the RAN or at least one event related to the RAN.

[0234] In an embodiment, the subscription request includes at least one event related to the RAN.

[0235] In one embodiment, the at least one event related to the RAN includes at least one of the following:

[0236] Detect cell changes,

[0237] detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release,

[0238] Measure the wireless terminal.

[0239] Configure carrier aggregation for wireless terminals, or

[0240] The subscription container expires.

[0241] In one embodiment, the RAN also sends the NEF a QoS flow identifier associated with the subscribed RAN information.

[0242] Fig.10 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Fig.10 The process shown can be used for SMF and includes the following steps:

[0243] Step 1001: receiving a subscription address in the RAN from the RAN; and

[0244] Step 1002: Send the subscription address in the RAN to the NEF.

[0245] exist Fig.10 In the embodiment, the SMF receives a subscription address in the RAN from the RAN, wherein the subscription address is used to receive a subscription request for RAN information. Next, the SMF sends (eg, forwards) the subscription address in the RAN to the NEF.

[0246] In one embodiment, the SMF receives a subscription container from the PCF, wherein the subscription container includes a notification address in a RAN information request and a network open function, and sends the subscription container to the RAN.

[0247] In one embodiment, the SMF may send forwarding information to the UPF, wherein the forwarding information includes a notification address in the NEF. Therefore, the UPF can send a corresponding notification (eg, subscribed RAN information) to the NEF.

[0248] In an embodiment, the RAN information request includes at least one of information related to the RAN or at least one event related to the RAN.

[0249] In an embodiment, the subscription request includes at least one event related to the RAN.

[0250] In one embodiment, the at least one event related to the RAN includes at least one of the following:

[0251] Detect cell changes,

[0252] detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release,

[0253] Measure the wireless terminal.

[0254] Configure carrier aggregation for wireless terminals, or

[0255] The subscription request expired.

[0256] In one embodiment, the SMF also sends at least one QoS flow identifier (associated with the RAN information) to the NEF. For example, the SMF may send the QoS flow identifier together with the associated RAN information to the NEF.

[0257] In one embodiment, the SMF further sends QoS flow binding information to the NEF. The QoS flow binding information includes service data flow information and associated QoS flow ID.

[0258] Fig.11 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Fig.11 The process shown may be used for RAN and comprises the following steps:

[0259] Step 1101: Receive a subscription container from the AMF, the subscription container including the RAN information request and the notification address in the NEF; and

[0260] Step 1102: Send RAN information to UPF based on the subscription container.

[0261] In this embodiment, the RAN receives a subscription request (e.g., a RAN information request) via the control plane, and sends the subscribed RAN information via the user plane. More specifically, the RAN receives a subscription container including the RAN information request and a notification address in the NEF. Based on the subscription container, the RAN sends the subscribed RAN information to the UPF, so that the subscribed RAN information is sent to the NEF and / or AF via the user plane.

[0262] In an embodiment, the RAN information request includes at least one of information related to the RAN or at least one event related to the RAN.

[0263] In one embodiment, the at least one event related to the RAN includes at least one of the following:

[0264] Detect cell changes,

[0265] detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release,

[0266] Measure the wireless terminal.

[0267] Configure carrier aggregation for wireless terminals, or

[0268] Network information request expired.

[0269] In an embodiment, the RAN sends at least one QoS flow identifier associated with the subscribed RAN information to the UPF.

[0270] In one embodiment, the RAN receives information from the SMF configuring a dedicated QoS flow for sending subscribed RAN information.

[0271] Fig.12 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Fig.12 The process shown can be used for UPF and includes the following steps:

[0272] Step 1201: Receive forwarding information from the SMF, where the forwarding information includes a notification address in the NEF and at least one QoS flow ID for receiving RAN information (optional);

[0273] Step 1202: Receive RAN information from RAN; and

[0274] Step 1203: Send RAN information to NEF based on the forwarding information.

[0275] exist Fig.12In the embodiment, the UPF receives forwarding information from the SMF, wherein the forwarding information includes a notification address in the NEF for receiving the subscribed RAN information. Next, the UPF receives the subscribed RAN information from the RAN, and forwards the subscribed RAN information to the NEF based on the forwarding information.

[0276] In one embodiment, the UPF may receive at least one QoS flow identifier associated with the RAN information from the RAN. In this embodiment, the UPF may send the received QoS flow identifier together with the RAN information, etc. to the NEF.

[0277] In an embodiment, the UPF determines a QoS flow identifier associated with the RAN information, for example based on the forwarding information, and sends the determined QoS flow identifier to the NEF.

[0278] In one embodiment, the UPF receives information from the SMF configuring a dedicated QoS flow for receiving RAN information.

[0279] Although various embodiments of the present disclosure have been described above, it should be understood that these embodiments are merely examples and not intended to be limiting. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these technicians will understand that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. Additionally, as those of ordinary skill in the art will understand, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

[0280] It should also be understood that any reference to an element using names such as "first," "second," etc., herein generally does not limit the number or order of these elements. Instead, these names may be used herein as a convenient means of distinguishing two or more elements or instances of an element. Thus, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.

[0281] Additionally, those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, and symbols referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0282] Those of skill will further understand that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design codes incorporating instructions (which, for convenience, may be referred to herein as "software" or "software units"), or any combination of these techniques.

[0283] In order to clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits and steps have been generally described above according to their functions. Such functions are implemented as hardware, firmware or software, or a combination of these technologies, depending on the specific application and the design constraints on the entire system. The technician can implement the described functions in various ways for each specific application, but such implementation decisions will not lead to deviation from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions described herein. The terms "configured to" or "configured for" used herein with respect to specific operations or functions refer to that processors, devices, components, circuits, structures, machines, units, etc. are physically constructed, programmed and / or arranged to perform specific operations or functions.

[0284] In addition, the technician will understand that the various illustrative logic blocks, units, devices, components and circuits described herein can be implemented in an integrated circuit (IC) or performed by an IC, which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other suitable configuration for performing the functions described herein. If implemented by software, these functions may be stored in a computer-readable medium as one or more instructions or codes. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored in a computer-readable medium.

[0285] Computer-readable media include computer storage media and communication media, which include any media that can transfer a computer program or code from one place to another. Storage media can be any available media that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0286] In this document, the term "unit" used refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for the purpose of discussion, various units are described as discrete units; however, it is obvious to those of ordinary skill in the art that two or more units can be combined to form a single unit that performs the associated functions according to the embodiments of the present disclosure.

[0287] Additionally, in the embodiments of the present disclosure, memory or other storage devices and communication components may be used. It should be understood that, for the sake of clarity, the embodiments of the present disclosure have been described above with reference to different functional units and processors. However, it is apparent that any suitable functional distribution may be adopted between different functional units, processing logic elements or domains without departing from the present disclosure. For example, functions shown as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable devices for providing the described functions, rather than indicating a strict logical or physical structure or organization.

[0288] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be consistent with the broadest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A wireless communication method used in a network opening function, the wireless communication method comprising: receiving a subscription address in the radio access network from a session management function of the core network, sending a subscription request to the subscription address in the wireless access network, and Radio access network information corresponding to the subscription request is received from the radio access network.

2. The wireless communication method according to claim 1, further comprising: receiving a radio access network information request for the radio access network information from an application function of the core network, and A subscription container is sent to a unified data repository, wherein the subscription container includes the wireless access network information request and a notification address for the wireless access network information in the network open function.

3. The wireless communication method according to claim 2, wherein: The radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

4. The wireless communication method according to any one of claims 1 to 3, wherein: The subscription request includes at least one event related to the radio access network.

5. The wireless communication method according to claim 3, wherein: The at least one event related to the radio access network includes at least one of the following: Detect cell changes, detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release, Measure the wireless terminal. Configure carrier aggregation for wireless terminals, or The subscription request expires.

6. The wireless communication method according to any one of claims 1 to 3, further comprising: receiving quality of service flow binding information from the session management function, receiving at least one quality of service flow identifier from a wireless terminal, the radio access network or a user plane function, and The radio access network information is sent to an application function based on the quality of service binding information and the at least one quality of service flow identifier.

7. A wireless communication method used in a wireless access network, the wireless communication method comprising: sending a subscription address in the wireless access network to a session management function, Receive a subscription request from the network open function, and The wireless access network information is sent to the network open function based on the subscription request.

8. The wireless communication method according to claim 7, further comprising: A subscription container is received from an access and mobility management function, the subscription container including a request for radio access network information and a notification address for the radio access network information in the network exposure function.

9. The wireless communication method according to claim 8, wherein: The radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

10. The wireless communication method according to any one of claims 7 to 9, wherein: The subscription request includes at least one event related to the radio access network.

11. The wireless communication method according to claim 9, wherein: The at least one event related to the radio access network includes at least one of the following: Detect cell changes, detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release, Measure the wireless terminal. Configure carrier aggregation for wireless terminals, or The subscription request expires.

12. The wireless communication method according to any one of claims 7 to 9, further comprising: At least one quality of service flow identifier and the radio access network information are sent to the network open function.

13. A wireless communication method used in a session management function, the wireless communication method comprising: receiving a subscription address in the radio access network from the radio access network, and The subscription address in the wireless access network is sent to a network open function.

14. The wireless communication method according to claim 13, further comprising: receiving a subscription container from a policy control function, the subscription container including a radio access network information request and a notification address in the network open function, and The subscription container is sent to the wireless access network.

15. The wireless communication method according to claim 14, further comprising: Sending forwarding information including the notification address in the network open function to the user plane function.

16. The wireless communication method according to claim 14 or 15, wherein: The radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

17. The wireless communication method according to any one of claims 13 to 15, wherein: The subscription request includes at least one event related to the radio access network.

18. The wireless communication method according to claim 17, wherein: The at least one event related to the radio access network includes at least one of the following: Detect cell changes, detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release, Measure the wireless terminal. Configure carrier aggregation for wireless terminals, or The subscription request expires.

19. The wireless communication method according to any one of claims 13 to 15, further comprising: Sending quality of service flow binding information to the network open function.

20. A wireless communication method used in a wireless access network, the wireless communication method comprising: receiving a subscription container from an access and mobility management function, the subscription container including a notification address in a radio access network information request and a network open function, and Based on the subscription container, the radio access network information is sent to the user plane function.

21. The wireless communication method according to claim 20, wherein: The radio access network information request includes at least one of the following: information related to the radio access network or at least one event related to the radio access network.

22. The wireless communication method according to claim 21, wherein: The at least one event related to the radio access network includes at least one of the following: Detect cell changes, detecting a radio access bearer event related to a radio access bearer, wherein the radio access bearer event comprises at least one of establishment, modification or release, Measure the wireless terminal. Configure carrier aggregation for wireless terminals, or The radio access network information request expires.

23. The wireless communication method according to any one of claims 20 to 22, further comprising: At least one quality of service flow identifier associated with the radio access network information is sent to the user plane function.

24. The wireless communication method according to any one of claims 20 to 22, further comprising: Information configuring a dedicated quality of service flow for transmitting the radio access network information is received from a session management function.

25. A wireless communication method used in a user plane function, the wireless communication method comprising: receiving forwarding information from a session management function, the forwarding information including a notification address for receiving wireless access network information in a network open function; receiving the radio access network information from the radio access network, and The wireless access network information is sent to the network open function based on the forwarding information.

26. The wireless communication method according to claim 25, further comprising: receiving at least one quality of service flow identifier associated with the radio access network information from the radio access network, and The at least one quality of service flow identifier is sent to the network open function.

27. The wireless communication method according to claim 25 or 26, further comprising: Information configuring a dedicated quality of service flow for receiving the radio access network information is received from a session management function.

28. A network device comprising: A communication unit, wherein the communication unit is configured to: receiving a subscription address in the radio access network from a session management function of the core network, sending a subscription request to the subscription address in the wireless access network, and Radio access network information corresponding to the subscription request is received from the radio access network.

29. The network device according to claim 28, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 2 to 3.

30. A wireless access network, comprising: A communication unit, wherein the communication unit is configured to: sending a subscription address in the wireless access network to a session management function, Receive a subscription request from the network open function, and The wireless access network information is sent to the network open function based on the subscription request.

31. The radio access network according to claim 30, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 8 to 9.

32. A network device comprising: A communication unit, wherein the communication unit is configured to: receiving a subscription address in the radio access network from the radio access network, and The subscription address in the wireless access network is sent to a network open function.

33. The network device according to claim 32, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 14 to 15.

34. A wireless access network, comprising: A communication unit, wherein the communication unit is configured to: receiving a subscription container from an access and mobility management function, the subscription container including a radio access network information request and a notification address of a network open function, Based on the subscription container, the radio access network information is sent to the user plane function.

35. The radio access network according to claim 34, further comprising a processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 21 to 22.

36. A network device comprising: A communication unit, wherein the communication unit is configured to: receiving forwarding information from a session management function, the forwarding information including a notification address for receiving wireless access network information in a network open function; receiving the radio access network information from the radio access network, and The wireless access network information is sent to the network open function based on the forwarding information.

37. The network device according to claim 36, further comprising a processor configured to execute the wireless communication method according to claim 26.

38. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the wireless communication method according to any one of claims 1 to 27.

Images