Communication method, communication device, and storage medium

Abstract

The present application provides a communication method, a communication device, and a storage medium. The communication method is applied to a first network element and comprises: sending a RAN data exposure subscription request message to a second network element; and receiving a RAN data exposure subscription response message sent by the second network element.

Description

Communication methods, communication equipment and storage media Technical Field

[0001] This application relates to the field of communication technology, specifically to a communication method, communication device, and storage medium. Background Technology

[0002] With the rapid development of wireless communication technology, the opening up of network capabilities has become an important trend for achieving more flexible and efficient network architectures. In 5G networks, the core network already possesses relatively mature capability opening functions, providing operators and third-party service providers with more flexible business deployment and innovation space. However, with the advent of next-generation mobile wireless networks, network architecture and application requirements will become more complex and diverse, and existing core network capability opening may not be able to fully meet the requirements of the 6G era. Summary of the Invention

[0003] In view of this, embodiments of this application provide a communication method, a communication device, and a storage medium, which realize the signaling interaction process that supports radio access network capabilities in a 6G network architecture.

[0004] This application provides a communication method applied to a first network element, including:

[0005] Send a RAN data open subscription request message to the second network element;

[0006] Receive the RAN data open subscription response message sent by the second network element.

[0007] This application provides a communication method applied to a second network element, including:

[0008] Receive the RAN data open subscription request message sent by the first network element;

[0009] Return a RAN data open subscription response message to the second network element.

[0010] This application provides a communication device applied to a first network element, comprising:

[0011] The sending module is configured to send a RAN data open subscription request message to the second network element;

[0012] The receiving module is configured to receive the RAN data open subscription response message sent by the second network element.

[0013] This application provides a communication device applied to a second network element, comprising:

[0014] The receiving module is configured to receive RAN data open subscription request messages sent by the first network element;

[0015] The sending module is configured to send a RAN data open subscription response message to the second network element.

[0016] This application provides a communication device, including: a memory, and one or more processors;

[0017] The memory is configured to store one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0019] This application provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in any of the above embodiments. Attached Figure Description

[0020] Figure 1 is a schematic diagram of the implementation of a network architecture 1 provided in an embodiment of this application;

[0021] Figure 2 is a schematic diagram of the implementation of a network architecture 2 provided in an embodiment of this application;

[0022] Figure 3 is a schematic diagram of the implementation of a network architecture 3 provided in an embodiment of this application;

[0023] Figure 4 is a schematic diagram of the implementation of a network architecture 4 provided in an embodiment of this application;

[0024] Figure 5 is a flowchart of a communication method provided in an embodiment of this application;

[0025] Figure 6 is a flowchart of another communication method provided in an embodiment of this application;

[0026] Figure 7 is a schematic diagram illustrating the configuration of the number of bytes contained in a GTP-U extension header according to an embodiment of this application;

[0027] Figure 8 is a flowchart of a UE data open capability information acquisition method provided in an embodiment of this application;

[0028] Figure 9 is a structural block diagram of a communication device provided in an embodiment of this application;

[0029] Figure 10 is a structural block diagram of another communication device provided in an embodiment of this application;

[0030] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0031] The embodiments of this application will be described below with reference to the accompanying drawings. The examples given are for illustrative purposes only and are not intended to limit the scope of this application.

[0032] In 5G networks, open capabilities are concentrated on the core network side. Standardized interfaces and open platforms allow third parties to access and invoke certain network functions on the core network side, thus enabling business innovation and service customization. However, with the development of next-generation mobile wireless networks, simply opening up the core network's capabilities is insufficient to meet future complex demands. In 6G networks, further breakthroughs are possible in areas such as ultra-high speeds, ultra-low latency, massive connectivity, and intelligence. This means that the capabilities of the Radio Access Network (RAN) will also become crucial.

[0033] Therefore, in 6G networks, it is necessary not only to open up the relevant capabilities of the core network, but also to further open up more radio access network capabilities. Opening up RAN capabilities will help achieve more flexible network management, more efficient resource scheduling, and more intelligent service delivery. Especially in the 6G era, the network will support more vertical industry applications, such as autonomous driving, smart manufacturing, and telemedicine. These applications have extremely high requirements for network real-time performance, reliability, and customization, which cannot be met by relying solely on the relevant open capabilities of the core network.

[0034] Therefore, researching the architecture and interaction processes that support open RAN capabilities has become a key issue in the current 6G network architecture design. Through open RAN capabilities, operators can achieve more granular network control, and third-party developers can also develop more innovative applications and services based on these capabilities. Furthermore, open RAN may also promote interoperability between equipment from multiple vendors, breaking the traditional monopoly of a single vendor and driving the prosperity and development of the entire communications ecosystem.

[0035] The existing core network capability open architecture will be used, with the network exposure function (NEF) as the only external interface and the network data analytics function (NWDAF) responsible for performing data analysis tasks.

[0036] The specific process for requesting data includes the following steps:

[0037] Step 1. The third-party application / service sends a data access request to NEF;

[0038] Step 2. NEF analyzes the request message. If the request content involves data related to RAN;

[0039] Step 3. NEF sends a data open request to the RAN node;

[0040] Step 4. After verification, the RAN node collects relevant data;

[0041] Step 5. The RAN node replies the data to NEF.

[0042] The specific process for requesting data analysis includes the following steps:

[0043] Step 1. The third-party application / service sends a data analysis request to NEF;

[0044] Step 2. NEF analyzes the request message and selects the appropriate NWDAF to execute the task;

[0045] Step 3. NWDAF sends a data open request to the RAN node;

[0046] Step 4. After verification, the RAN node collects relevant data;

[0047] Step 5. The RAN node replies with data to the NWDAF;

[0048] Step 6. NWDAF restores the data to NEF.

[0049] It should be noted that the embodiments of this application are implemented in the following four architectures.

[0050] In one example, Figure 1 is a schematic diagram of a network architecture 1 provided in an embodiment of this application. As shown in Figure 1, NEF / NWDAF establishes a connection with AMF through a Service-Based Interface (SBI), and AMF establishes a connection with RAN nodes through a traditional peer-to-peer (P2P) method. This embodiment includes a pre-preparation process and a RAN data opening process. The specific process is as follows:

[0051] Firstly, the pre-preparation process includes the following steps:

[0052] Step 1. The RAN reports RAN Exposure Capabilities to the AMF;

[0053] Step 2. RAN interacts with other RAN nodes. RAN Exposure Capabilities.

[0054] Secondly, the RAN data opening process includes the following steps:

[0055] Step 1. NEF / NWDAF sends a RAN Exposure Info Request to AMF, informing AMF of the requested RAN exposure information;

[0056] Step 2. The AMF forwards the RAN data open request to the NG-RAN;

[0057] Step 3. The RAN node collects the requested open data:

[0058] (1) If the open data is related to the UE, the RAN node sends a RAN data open request to the UE.

[0059] (2) If the open data is related to other RAN nodes, then send a RAN data open request to the other RAN nodes.

[0060] Step 4. The RAN node reports the RAN open data content to the AMF;

[0061] Step 5. AMF forwards RAN open data content to NEF / NWDAF.

[0062] In one example, Figure 2 is a schematic diagram of a network architecture 2 provided in an embodiment of this application. As shown in Figure 2, NEF / NWDAF establishes a connection with AMF and UPF through the SBI interface. AMF and UPF establish a connection with the RAN node through a traditional P2P method. Specifically, the RAN data opening request message of NEF / NWDAF is forwarded to the RAN node through AMF, and the RAN-opened data information is reported to NEF / NWDAF by UPF through the GTP-U header. This embodiment includes a pre-preparation process and a RAN data opening process. The specific process is as follows:

[0063] Firstly, the pre-preparation process includes the following steps:

[0064] Step 1. The RAN node reports RAN Exposure Capabilities to the AMF;

[0065] Step 2. RAN nodes interact with other RAN nodes to exchange RAN node data exposure capability information (i.e., RAN Exposure Capabilities).

[0066] Secondly, the RAN data opening process includes the following steps:

[0067] Step 1. NEF / NWDAF sends a RAN Exposure Info Request to AMF, informing AMF of the requested RAN exposure information;

[0068] Step 2. NEF / NWDAF sends a RAN data subscription request / RAN data reporting request to UPF, informing UPF of the RAN open data content to be subscribed to / reported;

[0069] Step 3. The AMF forwards the RAN data open request to the NG-RAN;

[0070] Step 4. The RAN node collects the requested open data:

[0071] (1) If the open data is related to the UE, the RAN node sends a RAN data open request to the UE;

[0072] (2) If the open data is related to other RAN nodes, then send a RAN data open request to the other RAN nodes;

[0073] Step 5. The RAN node reports the RAN open data content to the User Plane Function (UPF) through the General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header;

[0074] Step 6. UPF forwards the RAN open data content to NEF / NWDAF.

[0075] In one example, Figure 3 is a schematic diagram of a network architecture 3 provided in an embodiment of this application. As shown in Figure 3, NEF / NWDAF establishes connections with AMF and SMF through the SBI interface, SMF establishes connections with UPF through a traditional P2P method, and AMF and UPF establish connections with RAN nodes through a traditional P2P method. Specifically, the RAN data opening request message from NEF / NWDAF is forwarded to the RAN node through AMF, and the RAN-opened data information is reported to SMF by UPF through the GTP-U header, and then forwarded to NEF / NWDAF by SMF. This embodiment includes a pre-preparation process and a RAN data opening process. The specific process is as follows:

[0076] Firstly, the pre-preparation process includes the following steps:

[0077] Step 1. The RAN reports RAN Exposure Capabilities to the AMF;

[0078] Step 2. RAN interacts with other RAN nodes. RAN Exposure Capabilities.

[0079] Secondly, the RAN data opening process includes the following steps:

[0080] Step 1. NEF / NWDAF sends a RAN Exposure Info Request to AMF, informing AMF of the requested RAN exposure information;

[0081] Step 2. NEF / NWDAF sends a RAN data subscription request / RAN data reporting request to SMF, and SMF informs UPF of the RAN open data content to be subscribed to / reported;

[0082] Step 3. The AMF forwards the RAN data open request to the NG-RAN;

[0083] Step 4. The RAN node collects the requested open data:

[0084] (1) If the open data is related to the UE, the RAN node sends a RAN data open request to the UE.

[0085] (2) If the open data is related to other RAN nodes, then send a RAN data open request to the other RAN nodes.

[0086] Step 5. The RAN node reports the RAN open data content to the UPF via the GTP-U header;

[0087] Step 6. The UPF forwards the RAN open data content to the NEF / NWDAF via the SMF.

[0088] In one example, Figure 4 is a schematic diagram of a network architecture 4 provided in an embodiment of this application. As shown in Figure 4, NEF / NWDAF establishes connections with AMF and SMF through the SBI interface, SMF establishes connections with UPF through a traditional P2P method, and AMF and UPF establish connections with RAN nodes through a traditional P2P method. Specifically, the RAN data opening request message from NEF / NWDAF is forwarded to the RAN node through AMF, and the RAN-opened data information is reported to SMF by UPF through the GTP-U header, and then forwarded to NEF / NWDAF by SMF. This embodiment includes a pre-preparation process and a RAN data opening process. The specific process is as follows:

[0089] Firstly, the pre-preparation process includes the following steps:

[0090] Step 1. The RAN reports RAN Exposure Capabilities to the AMF;

[0091] Step 2. RAN interacts with other RAN nodes. RAN Exposure Capabilities.

[0092] Secondly, the RAN data opening process includes the following steps:

[0093] Step 1. NEF / NWDAF sends a RAN Exposure Info Request to SMF, informing SMF of the requested RAN exposure information;

[0094] Step 2. Based on the request message sent by NEF / NWDAF, SMF forwards the RAN data access request to AMF;

[0095] Step 3. Based on the request sent by NEF / NWDAF, SMF sends a RAN Open Data Reporting Request / RAN Open Data Subscription Request to UPF;

[0096] Step 4. The AMF forwards the RAN data open request to the NG-RAN;

[0097] Step 5. RAN nodes collect the requested open data:

[0098] (1) If the open data is related to the UE, the RAN node sends a RAN data open request to the UE;

[0099] (2) If the open data is related to other RAN nodes, then send a RAN data open request to the other RAN nodes;

[0100] Step 6. The RAN node reports the RAN open data content to the UPF via the GTP-U header;

[0101] Step 7. The UPF forwards the RAN open data content to the NEF / NWDAF via the SMF.

[0102] In one embodiment, FIG5 is a flowchart of a communication method provided by an embodiment of this application. This embodiment can be executed by a first network element. Exemplarily, the first network element can be a Network Function (NF) consumer, such as, including but not limited to, one of the following: NEF; NWDAF. As shown in FIG5, this embodiment includes: S110-S120.

[0103] S110, Send a RAN data open subscription request message to the second network element.

[0104] In one example, the second network element refers to the relevant network function on the core network side. For example, the second network element can be the Access and Mobility Management Function (AMF) or the Session Management Function (SMF). The first network element can send a Data Open Subscription Request message to the second network element to request and obtain relevant RAN data.

[0105] S120: Receive the RAN data open subscription response message sent by the second network element.

[0106] In one example, after the second network element receives the RAN data open subscription request message sent by the first network element, the second network element can return a RAN data open subscription response message to the first network element, so that the first network element can obtain the relevant RAN open data based on the RAN data open subscription response message.

[0107] In one embodiment, the enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; resident terminal list; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; historical response time. In one example, the enhanced configuration file of the second network element carries data open capability information of at least one RAN node in the area associated with the second network element. In one example, the radio access network node identifier refers to the unique identification information of the radio access network node, for example, the RAN node identifier can be the RAN node ID. In one example, the supported open types refer to the open types supported by the RAN node, which may include, but are not limited to, at least one of the following: supporting raw data, supporting reporting analysis data, and supporting aggregating data from other NG-RAN nodes. In one example, supported open data types refer to the data types that the RAN node supports exposing, which may include, but are not limited to, at least one of the following: RAN-side parameters (such as RAN configuration parameters or RAN measurement parameters) and predefined open event IDs; wherein, some possible open events are predefined, each open event corresponds to an event ID, and each event corresponds to a series of open data types. In one example, the analysis data reporting latency may include RAN data collection time and analysis report generation time. In one example, analysis function accuracy refers to the RAN node configuring different accuracy parameters for different open analysis tasks. The difference between the quantitative analysis results of this accuracy parameter and the true value can help consumers assess the reliability of the Next Generation Radio Access Network (NG-RAN) openness to select an NG-RAN node suitable for their needs; wherein, open analysis tasks may include at least one of the following tasks: signal strength assessment task, user experience analysis task, and classification task; the parameters for measuring accuracy parameters may include at least one of the following: error range, mean squared error (MSE), root mean squared error (RMSE), and relative error. In one example, the analysis processing capacity is used to describe the load information, available computing resources, and storage resources of the current NG-RAN node that can be used for open processing; wherein, the load information may include, but is not limited to, one of the following: the number of open analysis tasks in progress, the central processing unit (CPU) or memory utilization, etc.In one example, "Green Computing Support" indicates whether the open functions of the NG-RAN node utilize green computing technologies. If the open functions of the NG-RAN node utilize green computing technologies, this "Green Computing Support" indicator can be used to reflect this, helping consumers consider energy efficiency when selecting NFs. In another example, "Service Area Information" describes the geographical area or cell range covered by the open functions of the NG-RAN node; it can be represented as a Tracking Area Identity (TAI), Cell ID, Cell ID List, or location coordinates. In another example, "Resident Terminal List" describes the list of resident UE IDs associated with the NG-RAN node. In yet another example, "Supported Cell Types" describes the cell types that the NG-RAN node supports for analysis; for example, cell types can include, but are not limited to, macro cells, micro cells, or indoor cells. In one example, the network slice support terminology describes the Single-Network Slice Selection Assistance Information (S-NSSAI) supported by the open functions of the NG-RAN node, which helps consumers select the NG-RAN instance suitable for a specific network slice. In another example, machine learning support describes whether the open functions of the NG-RAN node support the training and deployment of machine learning (ML) models. In yet another example, machine learning model accuracy monitoring capability describes whether the open functions of the Measurement Gap-Radio Access Network (MG-RAN) node can monitor the accuracy of machine learning models and the accuracy of analysis tasks. In one example, federated learning support describes whether the open functions of the NG-RAN node support federated learning. In one example, metadata provision capability provides attribute information such as the source, timestamp, and format of RAN data. In yet another example, historical analysis performance describes the accuracy of the NG-RAN's open functions in performing similar analysis tasks in the past, allowing consumers to assess the reliability of the NG-RAN's open functions. In one example, historical response time is used to record the average response time of the NG-RAN node's open functions in the past when performing analysis tasks, which can help consumers select NG-RAN nodes with faster response times.

[0108] In one embodiment, the communication method applied to the first network element further includes: sending a first discovery request message to a third network element; wherein the first discovery request message is used to request the discovery of a second network element; and receiving a first discovery response message sent by the third network element. In one example, the first discovery request message refers to a Network Function Service Discovery Request message (NF service discovery request message), and correspondingly, the first discovery response message refers to a Network Function Service Discovery Response message (NF service discovery response message). For example, the first discovery request message can be an Nnrf_NF Discovery_Request message, and correspondingly, the first discovery response message can be an Nnrf_NF Discovery_Response message. When the second network element is an AMF, the first discovery request message can be an AMF discovery request message; when the second network element is an SMF, the first discovery request message can be an SMF discovery request message. Exemplarily, the third network element can be an NRF. In one example, the first network element sends the first discovery request message to the third network element, and the third network element selects one or more suitable second network elements based on the first discovery request message and in conjunction with the stored enhancement configuration file of the second network element; then the third network element replies to the first network element with the first discovery response message.

[0109] In one embodiment, the first discovery request message includes RAN data opening preference information; wherein, the RAN data opening preference information includes at least one of the following: information about the third-party application or service that prefers RAN data opening; the identity identifier of the core network functional entity that prefers RAN data opening; the relevant RAN data for the preference opening; the object associated with the preference opening RAN data; the time period for the preference opening; the reporting frequency of the preferred RAN open data; the time limit information for the preference reporting RAN data; the preference for machine learning capabilities; the machine learning model accuracy monitoring capability; the federated learning capability; and the preference reporting trigger event. In one example, the information about the third-party application or service that prefers RAN data opening refers to the information about the third-party application or service for the requested RAN open data, such as, but not limited to, at least one of the following: application ID, service ID, application type, service type, and service description. In one example, the identity identifier of the core network functional entity that prefers RAN data opening refers to the identity identifier of the core network functional entity requesting the RAN open data, such as, but not limited to, at least one of the following: NEF ID and NWDAF ID. In one example, the relevant RAN data for the preference opening may include, but not limited to, one of the following: specific RAN parameter names and RAN open data predefined events (RAN preference data IDs). In one example, the object associated with the preference for RAN data opening refers to the object associated with the preference for open RAN data, which may include, but is not limited to, one of the following: a UE (UE ID), certain UEs (UE ID List), a cell (Cell ID), certain cells (Cell ID List), a TAI region (TAI), certain TAI regions (TAI List), and a region (a region enclosed by multiple coordinates), etc. In one example, the time period for preference opening refers to the time period for requesting, analyzing, or predicting RAN data, for example, the time period can be from time XX 1 to time XX 2. In one example, the reporting frequency of preference for open RAN data refers to the reporting frequency of preference for open RAN data, which may include, but is not limited to, one-time reporting, periodic reporting (e.g., reporting once every XX seconds), and event-triggered reporting, etc. In one example, the time limit information for preference RAN data reporting refers to the time limit information for reporting preference for open RAN data, which may include, but is not limited to, one of the following: reporting no later than time XX, reporting starting from time XX, etc. In one example, preference for machine learning capabilities is used to characterize whether the training and deployment of ML models are supported. In another example, preference for machine learning model accuracy monitoring capabilities is used to characterize whether the accuracy of ML models, as well as the accuracy of analytical tasks, can be monitored. In yet another example, preference for federated learning capabilities is used to characterize whether the training and deployment of FL models are supported.In one example, the preference reporting trigger event is used to characterize the time description information of preference trigger reporting. For example, it may include, but is not limited to, one of the following: link quality is lower than a certain threshold (Reference Signal Received Power (RSRP) is lower than a certain threshold, Reference Signal Received Quality (RSRQ) is lower than a certain threshold, Signal to Interference plus Noise Ratio (SINR) is lower than a certain threshold, etc.), beam failure frequency is higher than a certain threshold, beam duration is greater than a certain threshold, average cell energy consumption is higher than a certain threshold, number of active users in the cell is greater than a certain threshold or lower than a certain threshold, abnormal cell energy consumption event occurs, green energy usage is higher than or lower than a certain threshold, UE handover frequency is higher than a certain threshold, UE handover success rate is lower than a certain threshold, UE connection establishment success rate is lower than a certain threshold, UE CPU utilization is higher than a certain threshold, UE battery level is lower than a certain threshold, etc.

[0110] In one embodiment, the first discovery response message includes at least one of the following: the identity identifier of the second network element; the configuration information of the second network element; and the data open capability information associated with the second network element. In one example, the identity identifier of the second network element is used to represent the unique identification information of the second network element. For example, if the second network element is an SMF, the identity identifier of the second network element is the SMF identity identifier; if the second network element is an AMF, the identity identifier of the second network element is the AMF identity identifier. In one example, the configuration information of the second network element refers to the relevant configuration information of the second network element itself. For example, the configuration information of the second network element can be the relevant configuration information of the AMF itself, or the relevant configuration information of the SMF itself. In one example, the parameters and explanations included in the data open capability information of the RAN node associated with the second network element can be found in the description of the above embodiments, and will not be repeated here.

[0111] In one embodiment, the RAN data open subscription request message includes at least one of the following: information about the third-party application or service for the subscribed RAN open data; the identity identifier of the core network functional entity for the subscribed RAN open data; the relevant RAN open data for subscription; the object associated with the subscribed RAN open data; the subscription open time period; the reporting frequency of the subscribed RAN open data; the reporting time limit information of the subscribed RAN open data; machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and reporting trigger events. In one example, the information about the third-party application or service for the subscribed RAN open data refers to the information of the third-party application or service requesting the subscription, which may include, but is not limited to, one of the following: application ID, service ID, application type, service type, and service description. In one example, the identity identifier of the core network functional entity for the subscribed RAN open data refers to the identity identifier of the core network entity requesting the subscription, which may include, but is not limited to, at least one of the following: NEF ID and NWDAF ID. In one example, the relevant RAN open data for subscription refers to the requested and subscribed RAN open data, which may include, but is not limited to, one of the following: specific RAN parameter names and RAN open data predefined events (RAN open data IDs). In one example, the objects associated with the subscribed RAN open data can include, but are not limited to, one of the following: a specific UE (UE ID), a list of UE IDs, a specific cell (Cell ID), a list of cells (Cell ID), a specific TAI region (TAI), a list of TAI regions (TAI), and a region (a region enclosed by multiple coordinates). In one example, the subscription open time period refers to the time period for requesting open, analyzed, or predicted RAN data; for example, the time period could be from time 1 to time 2. In one example, the reporting frequency of the subscribed RAN open data can include, but is not limited to, one of the following: one-time reporting, periodic reporting (reporting every xx seconds), event-triggered reporting, etc. In one example, the reporting time limit information for the subscribed RAN open data can include, but is not limited to, one of the following: reporting no later than time xx, reporting starting from time xx, etc. In one example, machine learning capabilities are used to characterize whether the training and deployment of ML models are supported. In one example, machine learning model accuracy monitoring capabilities are used to characterize whether the accuracy of the ML model and the accuracy of the analysis task can be monitored. In one example, federated learning capability is used to characterize whether training and deployment of FL models are supported.In one example, the reporting trigger event is used to characterize the time description information that triggers the reporting. For example, it may include, but is not limited to, one of the following: link quality is lower than a certain threshold (RSRP is lower than a certain threshold, RSRQ is lower than a certain threshold, SINR is lower than a certain threshold, etc.), beam failure frequency is higher than a certain threshold, beam duration is greater than a certain threshold, average cell energy consumption is higher than a certain threshold, number of active users in the cell is greater than a certain threshold or lower than a certain threshold, abnormal cell energy consumption event occurs, green energy usage is higher than or lower than a certain threshold, UE handover frequency is higher than a certain threshold, UE handover success rate is lower than a certain threshold, UE connection establishment success rate is lower than a certain threshold, UE CPU utilization is higher than a certain threshold, UE battery level is lower than a certain threshold, etc.

[0112] In one embodiment, the RAN data open subscription response message includes one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information. In one example, the information about the third-party application or service subscribed to the RAN open data may include, but is not limited to, one of the following: application ID, service ID, application type, service type, and service description. In one example, the identity identifier of the core network functional entity subscribed to the RAN open data refers to the identity identifier of the core network entity requesting the subscription to the RAN open data, such as, but not limited to, at least one of the following: NEF ID and NWDAF ID. In one example, the subscription identification information refers to the identification information of the second network element subscribing to the relevant RAN open data, such as, the subscription identification information may include one of the following: AMF identity identifier (e.g., AMF ID); and SMF identity identifier (SMF ID).

[0113] In one embodiment, the communication method applied to the first network element further includes: receiving a RAN data open notification message sent by the second network element. In one example, the second network element may send a RAN data open notification message to the first network element that has previously subscribed to a RAN data open event, in order to provide the first network element with associated RAN open data through the RAN data open notification message. Exemplarily, when the first network element is an NF Consumer (e.g., NEF or NWDAF) and the second network element is an AMF, the data open notification message may be a Namf_RANEventExposure_Notify message.

[0114] In one embodiment, the RAN data open notification message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; the relevant RAN open data subscribed to; the object associated with the subscribed RAN open data; and the RAN data open time period. In one example, the information about the third-party application or service subscribed to the RAN open data may include, but is not limited to, one of the following: application ID, service ID, application type, service type, and service description. In one example, the identity identifier of the core network functional entity subscribed to the RAN open data refers to the identity identifier of the core network entity requesting the subscription to the RAN open data, such as, but not limited to, at least one of the following: NEF ID and NWDAF ID. In one example, the relevant RAN open data subscribed to refers to the requested and subscribed RAN open data, such as, but not limited to, one of the following: specific RAN parameter names, and RAN open data predefined events (RAN open data IDs). In one example, the objects associated with the subscribed RAN open data can include, but are not limited to, one of the following: a specific UE (UE ID), a list of UE IDs, a specific cell (Cell ID), a list of cells (Cell ID), a specific TAI region (TAI), a list of TAI regions (TAI), and a region (a region enclosed by multiple coordinates). In one example, the RAN data open time period refers to the time period for requesting the openness, analysis, or prediction of RAN data; for example, the time period could be from time 1 to time 2.

[0115] In one embodiment, the communication method applied to the first network element further includes: sending a RAN data open subscription cancellation request message to the second network element; and receiving a RAN data open subscription cancellation response message sent by the second network element. In one example, the first network element may send a RAN data open subscription cancellation request message to the second network element so that the second network element can confirm whether to cancel the relevant RAN open data subscribed by the first network element, and notify the first network element of the data open subscription cancellation result through the RAN data open subscription cancellation response message.

[0116] In one embodiment, the RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information. The information about the third-party application or service subscribed to the RAN open data may include, but is not limited to, one of the following: application ID, service ID, application type, service type, and service description. In one example, the identity identifier of the core network functional entity subscribed to the RAN open data refers to the identity identifier of the core network entity requesting the subscription to the RAN open data, such as, at least one of the following: NEF ID and NWDAF ID. In one example, the subscription identification information refers to the identification information of the second network element subscribing to the relevant RAN open data, such as, the subscription identification information may include one of the following: AMF identity identifier (e.g., AMF ID); and SMF identity identifier (SMF ID).

[0117] In one example, the first network element can subscribe to a RAN data open event in the cell by using an unsubscribe service operation. The first network element unsubscribes from the RAN data open event by calling an unsubscribe data open notification message to the second network element. For example, if the first network element is an NF Consumer (e.g., NEF or NWDAF) and the second network element is an AMF, the unsubscribe data open notification message can be a Namf_RANEventExposure_UnSubscribe message.

[0118] In one embodiment, FIG6 is a flowchart of another communication method provided by an embodiment of this application. This embodiment can be executed by a second network element. Exemplarily, the second network element may include: AMF or SMF. As shown in FIG6, this embodiment includes: S210-S220.

[0119] S210, Receive the RAN data open subscription request message sent by the first network element.

[0120] S220: Send a RAN data open subscription response message to the second network element.

[0121] In one embodiment, the communication method applied to the second network element further includes: sending a registration request message to the third network element; wherein the registration request message includes an enhanced configuration file of the second network element.

[0122] In one embodiment, the enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; resident terminal list; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; historical response time.

[0123] In one embodiment, the RAN data open subscription request message includes at least one of the following: information about the third-party application or service of the subscribed RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; the relevant RAN open data being subscribed; the object associated with the subscribed RAN open data; the subscription open time period; the reporting frequency of the subscribed RAN open data; the reporting time limit information of the subscribed RAN open data; machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and reporting trigger events.

[0124] In one embodiment, the RAN data open subscription response message includes one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

[0125] In one embodiment, the communication method applied to the second network element further includes: sending a RAN data open notification message to the second network element.

[0126] In one embodiment, the RAN data open notification message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; the relevant RAN open data subscribed to; the object associated with the subscribed RAN open data; and the data open time period.

[0127] In one embodiment, the communication method applied to the second network element further includes: receiving a RAN data open subscription cancellation request message sent by the first network element; and returning a RAN data open subscription cancellation response message to the second network element.

[0128] In one embodiment, the RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

[0129] In one embodiment, when the second network element is an SMF, the communication method applied to the second network element further includes: receiving data open capability information supported by the node reported by the fourth network element. Exemplarily, the fourth network element may include an AMF or a UPF. In one example, when there is no direct SBI interface between the first and fourth network elements, information forwarding can be performed through the second network element. The first network element may send a RAN open data reporting request message to the second network element to inform the fourth network element that it can report the data open capability information of the RAN node. For an explanation of the data open capability information of the RAN node, please refer to the description of the above embodiments, which will not be repeated here.

[0130] In one embodiment, when the second network element is an SMF, the communication method applied to the second network element further includes: receiving updated data open capability information supported by the node reported by the fourth network element. In one example, the fourth network element may include an AMF or a UPF. In one example, when there is no direct SBI interface between the first network element and the fourth network element, information forwarding can be performed through the second network element. The first network element may send a RAN node RAN data openness request message to the second network element to inform the fourth network element that it can report updated RAN node data open capability information. For an explanation of the RAN node data open capability information, please refer to the description of the above embodiments, which will not be repeated here.

[0131] In one embodiment, when the second network element is an SMF, the communication method applied to the second network element further includes: sending a RAN data open request message to the fourth network element; and receiving a RAN data open response message sent by the fourth network element. In one example, the first network element may send a RAN data open request message to the second network element, and carry in the RAN data open request message the desired RAN data open event, the area description associated with the desired RAN open data, the UE list associated with the desired RAN open data, and the RAN data open configuration information of the desired RAN node. The second network element forwards the data open request message to the fourth network element, and the fourth network element forwards the relevant RAN open data to the first network element through the second network element based on the data open request message.

[0132] It should be noted that the parameters involved in the communication method applied to the second network element, such as the RAN data open subscription request message, the RAN data open subscription response message, and the data open capability information of the RAN node, as well as the parameter explanations of the various indicators included in the corresponding parameters, can be found in the description of the corresponding parameters in the communication method applied to the first network element, and will not be repeated here.

[0133] Example 1

[0134] In this embodiment, taking the connection establishment request message as an NG connection establishment request (e.g., NG Setup Request) message, the connection establishment response message as an NG connection establishment response (e.g., NG Setup Response) message, the first communication device as a RAN node, the second communication device as an AMF, and the first data open capability as a RAN data open capability as an example, the process of the interaction of RAN data open capability between the AMF and the RAN node is explained.

[0135] The process of exchanging RAN data openness capabilities between AMF and RAN nodes includes the following steps:

[0136] Step 1. The RAN node sends a Connection Establishment Request (NG Setup Request) message to the AMF, and needs to report the RAN data open capabilities it supports (Note: the RAN data open capabilities here refer to the functions or configurations related to openness that the RAN node itself has, not the data types that the RAN node can open).

[0137] Step 2. The AMF replies with a connection establishment response (NG Setup Response) message to the RAN node, which needs to include information on RAN data open capability support.

[0138] Example 2

[0139] In this embodiment, taking the configuration update request message as the RAN configuration update (e.g., RAN Configuration Update) message, the configuration update confirmation message as the RAN configuration update confirmation (e.g., RAN Configuration Update Acknowledge) message, the first communication device as the RAN node, the second communication device as the AMF, and the first data open capability as the updated RAN data open capability as an example, the process of the interaction of RAN data open capability between the AMF and the RAN node is explained.

[0140] The process of exchanging RAN data openness capabilities between AMF and RAN nodes includes the following steps:

[0141] Step 1. The RAN node sends a RAN Configuration Update message to the AMF, which can report updated RAN data access capabilities;

[0142] Step 2. The AMF replies to the RAN node with a RAN Configuration Update Acknowledge message, which needs to include the updated support status of RAN data open capabilities.

[0143] In one example, the RAN node supports RAN data exposure capabilities in the NG Setup Request, RAN Configuration Update, or newly defined messages, as shown in Table 1:

[0144] Table 1

[0145] Add an Information Element (IE) (e.g., Supported RAN Exposure Capabilities) to the newly defined response message in NG Setup Response / RAN Configuration Update Acknowledge / .

[0146] Table 2

[0147] Example 3

[0148] In this embodiment, taking the connection establishment request message as Xn connection establishment request (e.g., Xn Setup Request) message, the connection establishment response message as Xn connection establishment response (e.g., XN Setup Response) message, the first communication device as a RAN node, the second communication device as other RAN nodes, and the first data open capability as RAN data open capability as an example, the process of RAN nodes interacting with each other using RAN data open capability is explained.

[0149] The process of exchanging RAN data open capabilities between RAN Node 1 and RAN Node 2 includes the following steps:

[0150] Step 1. RAN node 1 sends a connection establishment request (Xn Setup Request) message to RAN node 2, which needs to include the RAN data open capabilities it supports (Note: RAN data open capabilities here refer to the functions or configurations related to openness that the RAN node itself has, not the data types that the RAN node can open).

[0151] Step 2. RAN Node 2 replies with a Connection Establishment Response (Xn Setup Response) message to the RAN Node, indicating whether the information was successfully received and also carrying its own support status for RAN data openness capabilities.

[0152] Example 4

[0153] In this embodiment, the process of RAN nodes interacting with each other using the following example is described: the configuration update request message is the RAN configuration update (e.g., NG-RAN node Configuration Update) message, the configuration update confirmation message is the RAN configuration update confirmation (e.g., NG-RAN node Configuration Update Acknowledge) message, the first communication device is the RAN node, the second communication device is other RAN nodes, and the first data open capability is the updated RAN data open capability.

[0154] The process of exchanging RAN data open capabilities between RAN Node 1 and RAN Node 2 includes the following steps:

[0155] Step 1. RAN node 1 sends a RAN configuration update (NG-RAN node Configuration Update) message to AMF, carrying the updated RAN data access capability;

[0156] Step 2. RAN Node 2 replies to RAN Node 1 with a RAN configuration update confirmation (NG-RAN node Configuration Update Acknowledge) message, indicating whether the information was successfully received and also including its own support status for the updated RAN data opening capabilities.

[0157] It should be noted that the RAN data open capabilities involved in Embodiments 3 and 4, or the updated RAN data open capabilities, can be found in Table 1 above, and will not be repeated here.

[0158] In one example, the information contained in the RAN open data is shown in Table 3:

[0159] Table 3

[0160] Example 5

[0161] In this embodiment, taking the first data open request message as a RAN data open request (e.g., RAN Exposure Context Setup Request) message, the first data open response message as a RAN data open response (e.g., RAN Exposure Context Setup Response) message, the first communication device as a RAN node, and the second communication device as an AMF as an example, the process of exchanging RAN open data between the AMF and the RAN node will be described.

[0162] Define the messages used for RAN open data management, including RAN data open request messages (e.g., RAN Exposure Context Setup Request) sent by the AMF to the RAN node, and RAN node data open response messages (e.g., RAN Exposure Context Setup Response) sent by the RAN node to the AMF.

[0163] The process of AMF initiating a RAN data open request includes the following steps:

[0164] Step 1. The AMF sends a RAN data open request message to the RAN node, requesting the RAN node to open the relevant data;

[0165] Step 2. The RAN node replies with a RAN data open response message to the AMF node in response to the RAN data open request sent by the AMF.

[0166] In one example, a RAN data open request message may include at least one of the following: Message type: RAN open data management type;

[0167] AMF identification identifiers, such as AMF ID;

[0168] RAN node identification, such as RAN node ID;

[0169] The requested list of RAN open data;

[0170] Information about third-party applications or services requesting RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0171] The identity identifier of the core network functional entity requesting RAN open data, such as NEF ID, NWDAF ID;

[0172] Request access to relevant RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data IDs);

[0173] The object associated with the requested RAN open data, such as the requested RAN open data being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0174] The requested open time period, such as the requested open, analyzed, or predicted data from time xx to time xx;

[0175] The frequency of requesting RAN open data reporting, such as one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.;

[0176] Request the RAN open data reporting time limit information, such as reporting no later than xx time point, or starting reporting from xx time point;

[0177] Report trigger event descriptions, such as link quality below xx (RSRP below a certain threshold, RSRQ below a certain threshold, SINR below a certain threshold, etc.), beam failure frequency above xx, beam duration longer than xx, average cell energy consumption above xx, number of active users in the cell more than xx or less than xx, abnormal cell energy consumption event, green energy usage above or below xx, UE handover frequency above xx, UE handover success rate below xx, UE connection establishment success rate below xx, UE CPU utilization above xx, UE battery level below xx, etc.

[0178] In one example, a RAN data open response message may include at least one of the following:

[0179] Message type: RAN Open Data Management type;

[0180] AMF identification identifiers, such as AMF ID;

[0181] RAN node identification, such as RAN node ID;

[0182] A list of RAN open data request information in response;

[0183] The response status of the RAN open data request, such as success or failure;

[0184] Request the release of relevant RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data ID) – corresponding to architecture Option 1. RAN nodes directly report RAN open data to AMF.

[0185] Example 6

[0186] In this embodiment, taking the first data open modification request message as a RAN data open modification request (e.g., RAN Exposure Context Modify Request) message, the first data open modification response message as a RAN data open modification response (e.g., RAN Exposure Context Modify Response) message, the first communication device as a RAN node, and the second communication device as an AMF as an example, the process of modifying RAN open data between the AMF and the RAN node is explained.

[0187] Define messages used for RAN open data management, including RAN data open modification request messages (e.g., RAN Exposure Context Modify Request) sent by AMF to RAN nodes to modify the RAN data to be opened, and RAN node data open modification response messages (e.g., RAN Exposure Context Modify Response) sent by RAN nodes to AMF.

[0188] The process of AMF initiating a RAN data open modification request includes the following steps:

[0189] Step 1. The AMF sends a RAN data open modification request message to the RAN node, requesting the RAN node to modify the relevant open data;

[0190] Step 2. The RAN node replies to the AMF node with a RAN data open modification response message, which is used to respond to the RAN data open modification request sent by the AMF.

[0191] In one example, a RAN data open update request message may include at least one of the following:

[0192] Message type: RAN Open Data Management type;

[0193] AMF identification identifiers, such as AMF ID;

[0194] RAN node identification, such as RAN node ID;

[0195] The list of RAN open data information to be modified;

[0196] The list of RAN open data to be released.

[0197] In one example, the list of RAN open data information to be modified includes at least one of the following:

[0198] The information of the third-party application or service for which the RAN open data is requested to be modified, such as application ID, service ID, application type, service type, service description, etc.

[0199] The identity identifier of the core network functional entity in the RAN open data to be modified, such as NEF ID, NWDAF ID;

[0200] The requested modification includes the relevant RAN open data, such as the specific RAN parameter name and the RAN open data predefined event (RAN open data ID).

[0201] The object associated with the requested RAN open data to be modified, such as the data requested being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0202] The requested modification of the open time period, such as requesting that the data to be opened / analyzed / predicted be from time xx to time xx;

[0203] The requested modification is the reporting frequency of RAN open data, such as one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.

[0204] The request is to modify the reporting time limit information for RAN open data, such as reporting no later than xx time point, or starting reporting from xx time point;

[0205] The requested modification includes descriptions of the reported triggering events, such as: link quality below xx (RSRP below a certain threshold, RSRQ below a certain threshold, SINR below a certain threshold, etc.), beam failure frequency above xx, beam duration longer than xx, average cell energy consumption above xx, number of active users in the cell more than xx or less than xx, abnormal cell energy consumption event, green energy usage above or below xx, UE handover frequency above xx, UE handover success rate below xx, UE connection establishment success rate below xx, UE CPU utilization above xx, UE battery level below xx, etc.

[0206] In one example, the list of RAN open data to be released includes at least one of the following:

[0207] Information about the third-party application or service requesting the release of RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0208] The identity identifier of the core network functional entity requesting the release of RAN open data, such as NEF ID, NWDAF ID;

[0209] The requested RAN open data to be released, such as the specific RAN parameter name and the RAN open data predefined event (RAN open data ID);

[0210] The object associated with the requested release of RAN open data, such as the data requested being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0211] In one example, the RAN data open update response message may include at least one of the following;

[0212] Message type: RAN Open Data Management type;

[0213] AMF identification identifiers, such as AMF ID;

[0214] RAN node identification, such as RAN node ID;

[0215] List of RAN open data modification request information in response.

[0216] In one example, the response list of the RAN Open Data Modification Request includes at least one of the following: the response status of the RAN Open Data Modification Request, such as success or failure;

[0217] The request modifies the relevant RAN open data, such as the specific RAN parameter name, RAN open data predefined event (RAN open data ID) – corresponding to architecture Option 1, where the RAN node directly reports the RAN open data to the AMF.

[0218] Example 7

[0219] In this embodiment, taking the first data release request message as a RAN data release request (e.g., RAN Exposure Context Release Command) message, the first data release response message as a RAN data release response (e.g., RAN Exposure Context Release Response) message, the first communication device as a RAN node, and the second communication device as an AMF as an example, the process of releasing RAN open data between the AMF and the RAN node is explained.

[0220] Define messages used for RAN open data management, including RAN data release request messages (e.g., RAN Exposure Context Release Command) sent by AMF to RAN nodes to release open RAN data, and RAN node data release response messages (e.g., RAN Exposure Context Release Response) sent by RAN nodes to AMF.

[0221] The process of AMF initiating a RAN data open release request includes the following steps:

[0222] Step 1. The AMF sends a RAN data open release request message to the RAN node, informing the RAN node to release the relevant RAN open data;

[0223] Step 2. The RAN node replies to the AMF node with a RAN data open release response message in response to the RAN data open release request.

[0224] In one example, a RAN data open release request message may contain at least one of the following:

[0225] Message type: RAN Open Data Management type;

[0226] AMF identification identifiers, such as AMF ID;

[0227] RAN node identification, such as RAN node ID;

[0228] The list of RAN open data to be released.

[0229] In one example, the list of RAN open data to be released includes at least one of the following:

[0230] Information about the third-party application or service requesting the release of RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0231] The identity identifier of the core network functional entity requesting the release of RAN open data, such as NEF ID, NWDAF ID;

[0232] The request includes the release of relevant RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data IDs).

[0233] The object associated with the requested release of RAN open data, such as the data requested being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0234] In one example, the RAN data open release response message may contain at least one of the following:

[0235] Message type: RAN Open Data Management type;

[0236] AMF identification identifiers, such as AMF ID;

[0237] RAN node identification, such as RAN node ID;

[0238] A list of RAN open data release request information in response.

[0239] In one example, the response list of open data release request information includes one of the following: the response status of the RAN open data release request, for example, the response status of the RAN open data release request may include: success or failure.

[0240] Example 8

[0241] In this embodiment, taking the first data release notification message as the RAN data release notification (e.g., RAN Exposure Context Release Indication) message, the first data release confirmation message as the RAN data release confirmation (e.g., RAN Exposure Context Release Confirm) message, the first communication device as the RAN node, and the second communication device as the AMF as an example, the process of exchanging RAN open data release notifications between the AMF and the RAN node will be described.

[0242] Define messages used for RAN open data management, including RAN data release notification messages (e.g., RAN Exposure Context Release Indication) sent by RAN nodes to AMF to inform AMF to release the RAN open data that has been opened, and RAN data release confirmation messages (e.g., RAN Exposure Context Release Confirm) sent by AMF to RAN nodes.

[0243] The description of the RAN open data release notification process includes the following steps:

[0244] Step 1. The RAN node sends a RAN open data release notification message to the AMF, informing the AMF to release the relevant RAN open data.

[0245] Step 2. The AMF replies to the AMF node with a RAN open data release confirmation message to acknowledge the RAN open data release request.

[0246] In one example, the RAN open data release notification message may contain at least one of the following:

[0247] Message type: RAN Open Data Management type;

[0248] AMF identification identifiers, such as AMF ID;

[0249] RAN node identification, such as RAN node ID;

[0250] The list of RAN open data released by the notification.

[0251] In one example, the list of RAN open data released in the notification includes at least one of the following:

[0252] The notification releases information about third-party applications or services in the RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0253] The notification releases the identity identifiers of core network functional entities in the RAN open data, such as NEF ID and NWDAF ID;

[0254] The notification releases RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data IDs);

[0255] The object associated with the RAN open data released in the notification, such as the requested open data being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0256] Reasons for release include the UE moving out of the RAN node's coverage area, or the RAN node no longer using green resources.

[0257] In one example, the RAN open data release acknowledgment message may contain at least one of the following:

[0258] Message type: RAN Open Data Management type;

[0259] AMF identification identifiers, such as AMF ID;

[0260] RAN node identification, such as RAN node ID;

[0261] List of confirmed RAN open data release request information.

[0262] In one example, the confirmed list of RAN open data release request information includes: the response status of the RAN open data release request, such as success or failure.

[0263] Example 9

[0264] In this embodiment, taking the first data open modification notification message as a RAN data open modification notification (e.g., RAN Exposure Context Modify Indication) message, the first data open modification confirmation message as a RAN data open modification confirmation (e.g., RAN Exposure Context Modify Confirm) message, the first communication device as a RAN node, and the second communication device as an AMF as an example, the process of exchanging RAN open data modification notifications between the AMF and the RAN node will be described.

[0265] Define messages used for RAN open data management, including RAN data open modification notification messages (e.g., RAN Exposure Context Modify Indication) sent by RAN nodes to AMF to inform AMF to modify the relevant open RAN data, and RAN open data modification confirmation messages (e.g., RAN Exposure Context Modify Confirm) sent by AMF to RAN nodes.

[0266] The RAN open data modification notification process includes the following steps:

[0267] Step 1. The RAN node sends a RAN open data modification notification message to the AMF, informing the AMF to modify the relevant RAN open data;

[0268] Step 2. The AMF replies to the RAN data open modification response message to the AMF node to confirm the RAN open data modification request.

[0269] In one example, the RAN Open Data Modification Notification message may contain at least one of the following:

[0270] Message type: RAN Open Data Management type;

[0271] AMF identification identifiers, such as AMF ID;

[0272] RAN node identification, such as RAN node ID;

[0273] The notification modifies the RAN open data list.

[0274] In one example, the list of RAN open data to be modified includes at least one of the following:

[0275] The notification modifies information about third-party applications or services in the RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0276] The notification modifies the identity identifiers of core network functional entities in the RAN open data, such as NEF ID and NWDAF ID.

[0277] The notification modifies the RAN open data, such as the specific RAN parameter name and the RAN open data predefined event (RAN open data ID);

[0278] The object associated with the RAN open data that the notification modifies, such as the requested open data being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0279] The reason for the modification is, for example, the UE moves out of the RAN node coverage area, or the RAN node configuration is updated.

[0280] In one example, the RAN open data modification confirmation message may contain at least one of the following:

[0281] Message type: RAN Open Data Management type;

[0282] AMF identification identifiers, such as AMF ID;

[0283] RAN node identification, such as RAN node ID;

[0284] List of confirmed RAN open data modification request information.

[0285] In one example, the confirmed list of RAN open data modification request information includes at least one of the following:

[0286] The response status of the RAN open data modification request, such as success or failure;

[0287] The information of the third-party application or service for which the RAN open data is requested to be modified, such as application ID, service ID, application type, service type, service description, etc.

[0288] The identity identifier of the core network functional entity in the RAN open data to be modified, such as NEF ID, NWDAF ID;

[0289] The requested modification includes the relevant RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data IDs).

[0290] The object associated with the requested RAN open data to be modified, such as the data requested being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0291] The requested modification of the open time period, such as requesting that the data to be opened / analyzed / predicted be from time xx to time xx;

[0292] The requested modification is the reporting frequency of RAN open data, such as one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.

[0293] The request is to modify the reporting time limit information for RAN open data, such as reporting no later than xx time point, or starting reporting from xx time point;

[0294] The requested modification includes descriptions of the reported triggering events, such as: link quality below xx (RSRP below a certain threshold, RSRQ below a certain threshold, SINR below a certain threshold, etc.), beam failure frequency above xx, beam duration longer than xx, average cell energy consumption above xx, number of active users in the cell more than xx or less than xx, abnormal cell energy consumption event, green energy usage above or below xx, UE handover frequency above xx, UE handover success rate below xx, UE connection establishment success rate below xx, UE CPU utilization above xx, UE battery level below xx, etc.

[0295] Example 10

[0296] In this embodiment, taking the first data open reporting notification message as the RAN data open reporting notification message (e.g., RAN Exposure Info Reporting Notify) message, the first communication device as the RAN node, and the second communication device as the AMF as an example, the process of exchanging RAN open data reporting notifications between the AMF and the RAN node is described.

[0297] If the requested RAN open data needs to be reported periodically, a new message for RAN open data management needs to be defined, namely the RAN Exposure Info Reporting Notify message, which is used to report RAN open data.

[0298] In one example, the RAN Open Data Reporting Notification Message may contain at least one of the following:

[0299] Message type: RAN Open Data Management type;

[0300] AMF identification identifiers, such as AMF ID;

[0301] RAN node identification, such as RAN node ID;

[0302] A list of RAN open data request information in response.

[0303] In one example, the response list of RAN open data request information includes: the relevant RAN open data requested; for example, the relevant RAN open data requested includes at least one of the following: the specific RAN parameter name, the RAN open data predefined event (RAN open data ID) - corresponding to architecture Option1, and the RAN node directly reporting RAN open data to the AMF.

[0304] Example 11

[0305] The signaling flow design for RAN node-to-RAN node interaction of RAN open data is similar to that of the interaction between AMF and RAN nodes, including the following process:

[0306] RAN Open Data Request / Response Process;

[0307] RAN Open Data Modification Request / Response Process;

[0308] RAN open data release request / response process;

[0309] RAN open data release notification / confirmation process;

[0310] RAN Open Data Modification Notification / Confirmation Process;

[0311] RAN Open Data Reporting Notification.

[0312] The specific signaling design is also basically the same, except for the following modifications:

[0313] The identity identifiers of the two nodes, namely the identity identifiers of the first communication device and the second communication device, are as follows:

[0314] Source Global NG-RAN Node ID;

[0315] Target Global NG-RAN Node ID.

[0316] Example 12

[0317] In this embodiment, RAN open data is transmitted through the GTP-U header (i.e., GTP-U HEADER), and its implementation process is described.

[0318] Since the amount of RAN open data is relatively large, it can be carried by GTP-U HEADER, sent by the RAN node to UPF, and then transferred by UPF to NEF / NWDAF.

[0319] In one example, a new GTP-U extension header is added for RAN open data transmission. For example, this GTP-U extension header can be a RAN Exposure Container. Figure 7 is a schematic diagram of the configuration of the number of bytes contained in a GTP-U extension header according to an embodiment of this application. As shown in Figure 7, the number of bytes occupied by the RAN Exposure Container and the Next Extension Header Type are 2-(4n-1) and 4n, respectively.

[0320] The GTP-U Extension Header (such as the RAN Exposure Container) may include at least one of the following:

[0321] PDU Type: Uplink Packet Data Unit Session Information (UL PDU SESSION INFORMATION) (PDU Type 1);

[0322] A list of open data request information in response (e.g., a predefined list of RAN data open events).

[0323] In one example, the predefined list of RAN data open events may include at least one of the following:

[0324] The information of the third-party application or service for which the RAN open data is requested to be modified, such as application ID, service ID, application type, service type, service description, etc.

[0325] The identity identifier of the core network functional entity requesting RAN open data, such as NEF ID, NWDAF ID;

[0326] Predefined RAN open data open event ID;

[0327] Parameters related to RAN data open events;

[0328] RAN data open association of object identity identifiers (UE ID, UE ID List, Cell ID, Cell ID list, TAI, TAI list, area description, etc.).

[0329] Example 13

[0330] In this embodiment, taking the first request message as a terminal capability acquisition message (e.g., UE Capability Enquiry message), the second response message as a terminal capability message (e.g., UE Capability Information), the first communication device as a RAN node, and the second communication device as a UE as an example, the process of obtaining UE capability enhancement between the UE and the RAN node is explained.

[0331] The UE needs to inform the RAN node whether it supports the RAN data opening function. If the UE supports this function, the RAN node can subsequently obtain information for opening from the UE node. Figure 8 is a flowchart of a UE data opening capability information acquisition method provided in an embodiment of this application. As shown in Figure 8, the scheme includes the following steps:

[0332] Step 1. Add an IE (RAN Exposure Request) to the UE Capability Enquiry message to inquire whether the UE supports RAN data exposure;

[0333] Step 2. Add an IE (RAN Exposure Support) in UE Capability Information to indicate whether RAN data exposure is supported.

[0334] Example 14

[0335] In this embodiment, taking the example of a second data exposure request (e.g., RAN Exposure Info Request) message carried in an RRC configuration (e.g., RRC Reconfiguration) message, and a second data exposure response message (e.g., RAN Exposure Info) message carried in a UE assistance message (e.g., UE Assistance Information), with the first communication device being the RAN node and the second communication device being the UE, the implementation process of the RAN node requesting relevant exposure information from the UE will be explained.

[0336] If a third-party application / service wants to request the RAN node to open UE-related information, the RAN node needs to interact with the UE to obtain the relevant information. The implementation scheme includes the following steps:

[0337] Step 1. Add an IE (e.g., RAN Exposure Info Request) in RRC Reconfiguration to request RAN Exposure information, such as UE battery level, UE power consumption, UE load resource status, etc.

[0338] Step 2. Add a new IE (e.g., RANExposureInfo) in UEAssistanceInformation to report relevant information.

[0339] In one example, the RAN Exposure Info Request message used by the RAN node to request UE-related open data includes at least one of the following:

[0340] Message type; UE ID; Requested list of open data for the UE.

[0341] In one example, the requested list of open data for the UE includes at least one of the following:

[0342] Information about third-party applications or services requesting RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0343] Request the UE to open relevant open data, such as UE ID, PRB utilization rate, CCE utilization rate, battery status (remaining power, battery consumption rate), UE hardware status (CPU utilization rate, memory utilization rate), connection status (UE time in RRC connected and idle states, length of time to keep the connection open, probability of successful connection establishment), etc.

[0344] The requested access period, such as the requested data being available from time xx to time xx;

[0345] The frequency of requesting open data reporting, such as one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.;

[0346] The time limit for requesting data reporting, such as reporting no later than xx time point, or starting reporting from xx time point;

[0347] The event description that triggers the request to be reported is as follows: the success rate of UE establishing a connection is lower than xx, the CPU utilization of UE is higher than xx, the battery level of UE is lower than xx, etc.

[0348] In one example, the second data open response message that the UE reports open data to the RAN may include at least one of the following:

[0349] Respond to the list of open data requests;

[0350] The decision to report one's own open data to third-party applications or services refers to whether or not to agree to report UE-related open data to third-party applications / services;

[0351] The requested data includes, for example, UE ID, PRB utilization, CCE utilization, battery status (remaining battery power, battery consumption rate), UE hardware status (CPU utilization, memory utilization), and connection status (UE time in RRC connected and idle states, length of time to maintain connection, and probability of successful connection establishment).

[0352] In the following embodiments, a second communication device is used as the core network node, and the core network node includes a first network element, a second network element, a third network element, and a fourth network element. The interaction process between the various network elements in the core network is explained using the following example: the first network element is a Network Consumer (NF Consumer) (e.g., NEF or NWDAF), the second network element is an AMF or SMF, the third network element is a Network Repository Function (NRF), and the fourth network element is an AMF or UPF. In the case where the fourth network element is an AMF or UPF, the second network element is an SMF.

[0353] The interaction process between NEF / NWDAF and AMF will be described in Examples 15 to 19 below.

[0354] Example 15

[0355] In this embodiment, the core network-side interaction process between NEF / NWDAF and AMF includes the following steps:

[0356] Step 1. The AMF sends a registration request message to the NRF to initiate the registration process. The registration request message includes the AMF profile and carries the data access capability information of the connected RAN node. This step 1 applies to network architectures 1, 2, and 3.

[0357] Step 2. When an NF consumer (e.g., NEF / NWDAF) needs to obtain RAN open data, it sends a first discovery request message to the NRF to initiate the AMF discovery process and selects an appropriate AMF based on the AMF Profile; Step 2 applies to network architectures 1, 2, and 3.

[0358] Step 3. The NF consumer (e.g., NEF / NWDAF) sends a data open subscription request to the selected AMF; wherein, step 3 applies to network architectures 1, 2 and 3;

[0359] Step 4. The AMF sends a data open notification message to the subscribed NF consumers (e.g., NEF / NWDAF); where network architecture 1 applies.

[0360] Based on the above process, the following processes or documents will be enhanced:

[0361] First, enhance the configuration file (enhanced AMF profile): add data open capability information related to the connected RAN node. For an explanation of the data open capability information, please refer to the description of the data open capability information of the RAN node in the above embodiments, which will not be repeated here.

[0362] Secondly, the AMF discovery process is enhanced: In the NF service discovery request (denoted as Nnrf_NFDiscovery_Request) service operation, if the target NF is an AMF, the data openness preference information of the RAN node can be carried in the NF service discovery request message. For an explanation of the data openness preference information, please refer to the description of the data openness preference information in the above embodiments, which will not be repeated here.

[0363] Third, new services supported by AMF (such as RAN data open events, denoted as Namf_RANEventExposure) are added, allowing other Network Function (NF) consumers to subscribe to or receive event and statistical information notifications related to RAN open data. The specific process includes: RAN data open subscription, unsubscription, and notification procedures.

[0364] In one embodiment, the newly added data open capability information related to the connected RAN node includes the contents shown in Table 4 below.

[0365] Table 4

[0366] Example 16

[0367] This embodiment describes the process of an NF consumer subscribing to RAN data open events. Other Network Function (NF) consumers can subscribe to events related to RAN open data from the AMF. In this embodiment, the data open subscription request message is a RAN data open subscription request message; correspondingly, in this embodiment, "data" refers to RAN data.

[0368] The process of subscribing to RAN data open events includes the following steps:

[0369] Step 1. The NF consumer (e.g., NEF / NWDAF) sends a RAN data open subscription request message (denoted as Namf_RANEventExposure_Subscribe_Request) to the AMF to request the relevant open data of the RAN node.

[0370] The RAN data open subscription request message contains:

[0371] Information about third-party applications or services subscribed to in the RAN open data, such as application ID, service ID, application type, service type, service description, etc.

[0372] The identity identifier of the core network functional entity subscribed to RAN open data, such as NEF ID, NWDAF ID;

[0373] Subscribed RAN open data, such as specific RAN parameter names and RAN open data predefined events (RAN open data IDs);

[0374] The objects associated with the subscribed RAN open data, such as the subscribed open data being about a certain UE (UE ID), certain UEs (UE ID List), a certain cell (Cell ID), certain cells (Cell ID List), a certain TAI area (TAI), certain TAI areas (TAI List), a certain area (area enclosed by multiple coordinates), etc.

[0375] The subscription's open time period, for example, the RAN data that is available for subscription, analysis, or prediction is from time xx to time xx;

[0376] The reporting frequency of subscribed RAN open data, such as one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.;

[0377] RAN data reporting time limits, such as no later than xx time point, or reporting starting from xx time point;

[0378] Machine learning capability, which indicates whether it supports the training and deployment of ML models;

[0379] Machine learning model accuracy monitoring capability characterizes whether the accuracy of the ML model and the accuracy of the analysis task can be monitored;

[0380] Federated learning capability indicates whether it supports the training and deployment of FL models;

[0381] Report triggering events, such as: link quality below a certain threshold (RSRP below a certain threshold, RSRQ below a certain threshold, SINR below a certain threshold, etc.), beam failure frequency above a certain threshold, beam duration above a certain threshold, average cell energy consumption above a certain threshold, number of active users in the cell above a certain threshold or below a certain threshold, abnormal cell energy consumption event, green energy usage above or below a certain threshold, UE handover frequency above a certain threshold, UE handover success rate below a certain threshold, UE connection establishment success rate below a certain threshold, UE CPU utilization above a certain threshold, UE battery level below a certain threshold, etc.

[0382] Step 2. The AMF assigns a subscription association ID to the subscriber and replies to the NF consumer (e.g., NEF / NWDAF) in the RAN data open subscription response (Namf_RANEventExposure_Subscribe_Response) message.

[0383] Example 17

[0384] This embodiment describes the process of the AMF notifying the RAN of a data open event. In this embodiment, the AMF provides the previously subscribed event information to NF consumers who have subscribed to the event. The data open notification message is a RAN data open notification message. The notification process for the RAN data open event in this embodiment includes the following steps:

[0385] Step 1. The AMF sends a RAN data open notification (Namf_RANEventExposure_Notify) message to NF consumers (e.g., NEF / NWDAF) that have previously subscribed to RAN data open events, providing relevant RAN open data. This RAN data notification message may contain: AMF ID; subscription association ID; NF consumer ID; the relevant RAN open data subscribed to, such as specific RAN parameter names, RAN open data predefined events (RAN open data ID); the object associated with the subscribed RAN open data, such as the requested open data being about a specific UE (UE ID), certain UEs (UE ID List), a specific cell (Cell ID), certain cells (Cell ID List), a specific TAI area (TAI), certain TAI areas (TAI List), a specific area (area enclosed by multiple coordinates), etc.; and the open time period associated with the RAN open data, such as time xx to time xx.

[0386] Example 18

[0387] This embodiment describes the process of an NF consumer unsubscribing from a RAN data open event. In this embodiment, the NF consumer uses this service operation to unsubscribe from a specific RAN data open event. The data open subscription cancellation request message is a RAN data open subscription cancellation request message.

[0388] In this embodiment, the unsubscription process for RAN data open events includes the following steps:

[0389] Step 1. The NF consumer unsubscribes from RAN data open subscription notifications by sending a Namf_RANEventExposure_UnSubscribe message to the AMF. The subscription association ID is carried in this Namf_RANEventExposure_UnSubscribe message.

[0390] Example 19

[0391] This embodiment describes the enhanced process of NF CONSUMER discovering AMFs. In this embodiment, the first discovery request message is an NF service discovery request message, and correspondingly, the first discovery response message is an NF service discovery response message. The enhanced AMF discovery process includes the following steps:

[0392] Step 1. The NF consumer (NEF / NWDAF) sends an NF service discovery request message (e.g., Nnrf_NFDiscovery_Request) to the NRF. If the target NF is an AMF, the NF service discovery request message may contain RAN data openness preference information. For an explanation of the RAN data openness preference information, please refer to the description in Table 1 of the above embodiments, which will not be repeated here.

[0393] Step 2. Based on the NF service discovery request message and the stored AMF profile, NRF selects one or more appropriate AMFs.

[0394] Step 3. The NRF replies with an NF service discovery response message, which includes the AMF ID and the data open capability information of the RAN node associated with the AMF. For an explanation of the data open capability information, please refer to Table 1 in the above embodiments; it will not be repeated here.

[0395] The interaction process between NEF / NWDAF and SMF will be described in Examples 20 to 21 below. In these examples, the first discovery request message may be an SMF discovery request message.

[0396] Example 20

[0397] This embodiment uses architecture 3 to illustrate the interaction process between NEF / NWDAF and SMF. There is no direct SBI interface between NEF / NWDAF and UPF; information forwarding needs to be done through SMF. Therefore, NEF / NWDAF can send a RAN Open Data Reporting Request message to SMF to instruct UPF to report RAN Open Data.

[0398] The interaction process between NEF / NWDAF and SMF includes the following steps:

[0399] Step 1. The UPF reports its configuration information to the SMF via the N4 interface. If the UPF can optionally support reporting RAN node data openness information, the UPF configuration file can include the following information: whether it supports reporting relevant RAN open data; the RAN data openness events that can be reported; the area description information associated with the reported RAN open data, which can be represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; and the list of resident UEs associated with the reported RAN open data, which contains UEs that frequently appear in the area covered by the UPF.

[0400] Step 2. The SMF sends its profile to the NRF to complete registration. If the UPF associated with the SMF can optionally support reporting RAN node data openness information, the SMF's profile needs to carry the following information: whether it supports reporting relevant RAN open data; the RAN data openness events that can be reported; the area description information associated with the reported RAN open data, which can be represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; and the list of resident UEs associated with the reported RAN open data, which includes UEs that frequently appear in the area covered by the UPF.

[0401] Step 3. The NF Consumer (e.g., NEF / NWDAF) sends an SMF discovery request message to the NRF to discover a suitable SMF. If the SMF is used to subscribe to relevant RAN open data, the following information needs to be included in the SMF discovery request message: preference for having the ability to report RAN open data; preference for reporting which RAN data open events; preference for the area associated with the requested RAN open data; and a list of UEs associated with the requested RAN open data.

[0402] Step 4. The NRF sends an SMF discovery response message to the NF Consumer (e.g., NEF / NWDAF). If the NF Consumer is requesting SMFs with RAN node data open capability information, the SMF discovery response message must include the following information: whether the relevant RAN open data is supported for reporting; the RAN data open events that are supported for reporting; the area description information associated with the reported RAN open data, which can be represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; and the list of resident UEs associated with the reported RAN open data, which includes UEs that frequently appear in the area covered by the UPF.

[0403] Step 5. Based on the NRF's response, the NF Consumer selects the appropriate SMF and sends a RAN data open subscription request (e.g., Namf_RANEventExposure_Subscribe_Request) message to the SMF to request relevant open data from the RAN node. This Namf_RANEventExposure_Subscribe_Request message contains: the RAN data open event to be reported; a description of the area associated with the RAN open data to be reported, usually represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; and a list of UEs associated with the RAN open data to be reported.

[0404] Step 6. Based on the RAN Data Open Subscription Request message, the SMF selects a suitable UPF from the associated UPF list and sends a RAN Data Open Subscription Response message to the selected UPF. This response message includes: the RAN data open event to be reported; a description of the area associated with the RAN open data to be reported, typically expressed as a TAI (Tracking Area Identifier), Cell ID, or location coordinates; and a list of UEs associated with the RAN open data to be reported.

[0405] Step 7. The UPF assigns a subscription association ID to the SMF based on the RAN data subscription request message and replies to the SMF in the RAN data subscription response message.

[0406] Step 8. SMF sends a subscription association ID to the subscriber and replies to the NF consumer (e.g., NEF / NWDAF) in the RAN data subscription response (Namf_RANEventExposure_Subscribe_Response) message.

[0407] Step 9. After receiving the RAN open data reported by the RAN side, the UPF sends a RAN open data notification message to the SMF.

[0408] Step 10. SMF sends RAN open data to NF consumers (e.g., NEF / NWDAF).

[0409] Due to the enhancements to the process, it is also necessary to consider enhancing the functional descriptions of AMF, UPF, and SMF:

[0410] Firstly, the AMF function description is enhanced: as a transmission between the NG-RAN side and NEF / NWDAF, it is used to transmit RAN Exposure Information related information (such as request, update, release, etc. messages).

[0411] Secondly, the UPF function description is enhanced: it reports RAN Exposure Information to the SMF.

[0412] Third, the SMF function description is enhanced: the SMF forwards the RAN Exposure Information sent by the UPF to the NEF / NWDAF.

[0413] Example 21

[0414] This embodiment uses architecture 4 to describe the interaction process between NEF / NWDAF and SMF. The SMF uniformly organizes the configuration information of AMF and UPF, transmits it to the NRF and saves it. The NF Consumer selects the appropriate SMF to complete the RAN open data acquisition.

[0415] In this embodiment, the interaction process between NEF / NWDAF and SMF includes the following steps:

[0416] Step 1. The UPF reports its configuration information to the SMF via the N4 interface. If the UPF can optionally support RAN data openness capabilities, the following information needs to be included in the UPF's configuration file: whether it supports reporting RAN open data; the RAN data openness events that can be reported; the area description associated with the reported RAN open data, usually represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; and a description of the list of resident UEs associated with the reported RAN open data, which includes UEs that frequently appear in the area covered by the UPF.

[0417] Step 2. The AMF reports its configuration information to the SMF via the N11 interface. If the AMF optionally supports RAN data opening capabilities, the AMF configuration file needs to include the following information: whether it supports sending RAN data opening request messages to RAN nodes; and the RAN data opening configuration of the associated RAN nodes. For details, please refer to Table 1 in the above embodiment.

[0418] Step 3. The SMF sends its profile to the NRF to complete registration. If the AMF / UPF associated with the SMF optionally supports the ability to report RAN open data, the SMF's profile needs to carry the following information: whether it supports issuing RAN open data requests; whether it supports reporting RAN open data; the RAN data open events that can be reported; the area description associated with the reported RAN open data, usually represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; a description of the list of resident UEs associated with the reported RAN open data, which includes UEs that frequently appear in the area covered by the UPF; and the RAN data open configuration of the associated RAN node, as shown in Table 1 of the above embodiment.

[0419] Step 4. The NF Consumer (NEF / NWDAF) sends an SMF discovery request to the NRF to discover a suitable SMF. If the SMF is used to subscribe to RAN open data, the following information needs to be included in the request message: the preference for having the ability to report RAN open data; the preferred RAN data open events to be reported; the area associated with the preference request for RAN open data; the list of UEs associated with the preference request for RAN open data; and the RAN data open configuration of the preferred RAN node.

[0420] Step 5. The NRF sends an SMF discovery response to the NF Consumer (NEF / NWDAF). If the NF Consumer is requesting an SMF with RAN data open capability, the response message must include the following information about the SMF: whether it supports reporting RAN open data; supported RAN data open events; a description of the area associated with the reported RAN open data, usually represented by TAI (Tracking Area Identifier), Cell ID, or location coordinates; a description of the list of resident UEs associated with the reported RAN open data, which includes UEs that frequently appear in the area covered by the UPF; and the RAN data open configuration of the associated RAN node.

[0421] Step 6. Based on the NRF's response, the NF Consumer selects the appropriate SMF and sends a Namf_RANEventExposure_Subscribe_Request to the SMF, requesting the RAN node to open data. This message includes: the RAN data opening event to be requested; a description of the area associated with the requested RAN data opening, usually represented in the form of TAI (Tracking Area Identifier), Cell ID, or location coordinates; a list of UEs associated with the requested RAN data opening; and the RAN data opening configuration of the requested RAN node.

[0422] Step 7. Based on the request content sent by the NF Consumer in Step 6, the SMF selects a suitable AMF and sends a RAN data open request to the selected AMF. This message includes: the RAN data open event to be requested; the area description associated with the RAN open data to be requested, usually represented in the form of TAI (Tracking Area Identifier), Cell Identifier (Cell ID), or location coordinates; the list of UEs associated with the RAN open data to be requested; and the RAN data open configuration of the RAN node to be requested.

[0423] Step 8. Based on the request content sent by the NF Consumer in Step 6, the SMF selects a suitable UPF and sends a RAN data open reporting request to the selected UPF. This message includes: the RAN data open event to be reported; the area description associated with the RAN open data to be reported, usually represented in the form of TAI (Tracking Area Identifier), Cell Identifier (Cell ID), or location coordinates; the list of UEs associated with the RAN open data to be reported; and the RAN data open configuration of the RAN node to be reported.

[0424] Step 9. The AMF forwards the message sent by the SMF to the RAN node. The implementation process of this step can be referred to the descriptions of Embodiments 5-9 above, and will not be repeated here.

[0425] In one embodiment, if the RAN node updates its RAN Open Data configuration and sends it to the AMF, the AMF can forward the update to the SMF. The SMF, based on the information reported by the AMF, updates its own profile and triggers the NF service update procedure to update the SMF profile stored in the NRF. The specific procedure includes the following steps:

[0426] Step 1. The AMF sends a RAN open data configuration update message to the SMF. This message contains updated RAN node data open capability information, which can be found in Table 1 of the above embodiment.

[0427] Step 2. Update the profile using SMF;

[0428] Step 3. SMF sends NF service update to NRF to update AMF profile.

[0429] The enhanced processes allow for improvements to the functional descriptions of AMF, UPF, and SMF:

[0430] Firstly, the AMF function description is enhanced: it forwards RAN data opening request update or release messages issued by the SMF to the RAN nodes; and it reports the RAN data opening configuration information or RAN opening data of the RAN nodes to the SMF.

[0431] Secondly, the UPF function description is enhanced: it reports RAN Exposure Information to the SMF.

[0432] Third, the SMF function description is enhanced: Select the appropriate UPF and AMF, execute the RAN data opening request, update or release process of NEF / NWDAF; report the RAN data opening configuration information of the RAN node or the updated RAN opening data to NEF / NWDAF.

[0433] In one embodiment, FIG9 is a structural block diagram of a communication device provided in an embodiment of this application. This embodiment is applied to a first network element. As shown in FIG9, the communication device in this embodiment includes: a transmitting module 310 and a receiving module 320.

[0434] The sending module 310 is configured to send a RAN data open subscription request message to the second network element.

[0435] The receiving module 320 is configured to receive the RAN data open subscription response message sent by the second network element.

[0436] In one embodiment, the enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; resident terminal list; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; historical response time.

[0437] In one embodiment, the communication device applied to the first network element further includes:

[0438] The sending module is also configured to send a first discovery request message to a third network element; wherein the first discovery request message is used to request the discovery of a second network element;

[0439] The receiving module is also configured to receive the first discovery response message sent by the third network element.

[0440] In one embodiment, the first discovery request message includes RAN data openness preference information; wherein, the RAN data openness preference information includes at least one of the following: information about third-party applications or services that prefer RAN data openness; the identity identifier of the core network functional entity that prefers RAN data openness; the relevant RAN data that prefers openness; the object associated with the preferred RAN data openness; the time period for preference openness; the reporting frequency of preferred RAN openness data; the time limit information for preferred RAN data reporting; preferred machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and preference reporting trigger events.

[0441] In one embodiment, the first discovery response message includes at least one of the following: the identity identifier of the second network element; the configuration information of the second network element; and the data openness capability information associated with the second network element.

[0442] In one embodiment, the RAN data open subscription request message includes at least one of the following: information about the third-party application or service of the subscribed RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; the relevant RAN open data being subscribed; the object associated with the subscribed RAN open data; the subscription open time period; the reporting frequency of the subscribed RAN open data; the reporting time limit information of the subscribed RAN open data; machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and reporting trigger events.

[0443] In one embodiment, the RAN data open subscription response message includes one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

[0444] In one embodiment, the communication device applied to the first network element further includes:

[0445] The receiving module is also configured to receive RAN data open notification messages sent by the second network element.

[0446] In one embodiment, the RAN data open notification message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; the relevant RAN open data subscribed to; the object associated with the subscribed RAN open data; and the data open time period.

[0447] In one embodiment, the communication device applied to the first network element further includes:

[0448] The sending module is also configured to send a RAN data open subscription cancellation request message to the second network element;

[0449] The receiving module is also configured to receive RAN data open subscription cancellation response messages sent by the second network element.

[0450] In one embodiment, the RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

[0451] The communication device provided in this embodiment is configured to implement the communication method applied to the first network element in the embodiment shown in Figure 5. The implementation principle and technical effect of the communication device provided in this embodiment are similar, and will not be described again here.

[0452] In one embodiment, FIG10 is a structural block diagram of another communication device provided in this application embodiment. This embodiment is applied to a second network element. As shown in FIG10, the communication device in this embodiment includes: a receiving module 410 and a transmitting module 420.

[0453] The receiving module 410 is configured to receive the RAN data open subscription request message sent by the first network element.

[0454] The sending module 420 is configured to send a RAN data open subscription response message to the second network element.

[0455] In one embodiment, the communication device applied to the second network element further includes:

[0456] The sending module is also configured to send a registration request message to a third network element; wherein the registration request message includes the enhanced configuration file of the second network element.

[0457] In one embodiment, the enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; resident terminal list; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; historical response time.

[0458] In one embodiment, the RAN data open subscription request message includes at least one of the following: information about the third-party application or service of the subscribed RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; the relevant RAN open data being subscribed; the object associated with the subscribed RAN open data; the subscription open time period; the reporting frequency of the subscribed RAN open data; the reporting time limit information of the subscribed RAN open data; machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and reporting trigger events.

[0459] In one embodiment, the data open subscription response message includes one of the following: information about the third-party application or service of the subscribed RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; and subscription identification information.

[0460] In one embodiment, the communication device applied to the second network element further includes:

[0461] The sending module is also configured to send RAN data access notification messages to the second network element.

[0462] In one embodiment, the RAN data open notification message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; the relevant RAN open data subscribed to; the object associated with the subscribed RAN open data; and the data open time period.

[0463] In one embodiment, the communication device applied to the second network element further includes:

[0464] The receiving module is also configured to receive the RAN data open subscription cancellation request message sent by the first network element; and to return the RAN data open subscription cancellation response message to the second network element.

[0465] In one embodiment, the RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

[0466] In one embodiment, when the second network element is an SMF, the communication device applied to the second network element further includes:

[0467] The receiving module is also configured to receive information on the data openness capabilities supported by the node reported by the fourth network element.

[0468] In one embodiment, when the second network element is an SMF, the communication device applied to the second network element further includes:

[0469] The receiving module is also configured to receive updated data access capability information supported by the node reported by the fourth network element.

[0470] In one embodiment, when the second network element is an SMF, the communication device applied to the second network element further includes:

[0471] The sending module is also configured to send a RAN data access request message to the fourth network element;

[0472] The receiving module is also configured to receive RAN data open response messages sent by the fourth network element.

[0473] The communication device provided in this embodiment is configured to implement the communication method applied to the second network element in the embodiment shown in FIG6. The implementation principle and technical effect of the communication device provided in this embodiment are similar, and will not be described again here.

[0474] In one embodiment, FIG11 is a schematic diagram of the structure of a communication device provided in this application embodiment. As shown in FIG11, the device provided in this application includes: a processor 510, a memory 520, and a communication module 530. The number of processors 510 in the device can be one or more; FIG11 shows one processor 510 as an example. The number of memories 520 in the device can be one or more; FIG11 shows one memory 520 as an example. The processor 510, memory 520, and communication module 530 of the device can be connected via a bus or other means; FIG11 shows a connection via a bus as an example. In this embodiment, the device can be a first network element, a second network element, a third network element, or a fourth network element.

[0475] The memory 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device in any embodiment of this application (e.g., the transmitting module 310 and receiving module 320 in a communication device applied to the first network element). The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created according to the use of the device, etc. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include memory remotely located relative to the processor 510, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0476] When the communication device is the first network element, the device provided above can be configured to execute the communication method applied to the first network element provided in any of the above embodiments, and has the corresponding functions and effects.

[0477] When the communication device is a second network element, the device provided above can be configured to execute the communication method applied to the second network element provided in any of the above embodiments, and has the corresponding functions and effects.

[0478] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a communication method applied to a first network element. The method includes: sending a RAN data open subscription request message to a second network element; and receiving a RAN data open subscription response message sent by the second network element.

[0479] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a communication method applied to a second network element. The method includes: receiving a RAN data open subscription request message sent by a first network element; and sending a RAN data open subscription response message to the second network element.

[0480] Those skilled in the art will understand that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0481] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0482] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0483] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0484] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the communication method provided in any embodiment of this application.

[0485] In the implementation of the computer program product, computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer through any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0486] The above are merely optional embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A communication method applied to a first network element, comprising: Send a Radio Access Network (RAN) Data Open Subscription Request message to the second network element; Receive the RAN data open subscription response message sent by the second network element.

2. The method according to claim 1, wherein, The enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support status; service area information; list of resident terminals; supported cell types; supported network slices; machine learning support status; machine learning model accuracy monitoring capability; federated learning support status; metadata provision capability; historical analysis performance; historical response time.

3. The method according to claim 1, further comprising: Send a first discovery request message to the third network element; wherein, the first discovery request message is used to request the discovery of the second network element; Receive the first discovery response message sent by the third network element.

4. The method according to claim 3, wherein, The first discovery request message contains RAN data openness preference information; wherein, the RAN data openness preference information includes at least one of the following: information about third-party applications or services that prefer RAN data openness; the identity identifier of the core network functional entity that prefers RAN data openness; the relevant RAN data that prefers openness; the object associated with the preferred RAN data openness; the time period for preference openness; the reporting frequency of preferred RAN openness data; the time limit information for preferred RAN data reporting; preferred machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; and preference reporting trigger events.

5. The method according to claim 3, wherein, The first discovery response message includes at least one of the following: the identity identifier of the second network element; the configuration information of the second network element; and the data open capability information associated with the second network element.

6. The method according to claim 1, wherein, The RAN data open subscription request message includes at least one of the following: information about the third-party application or service of the subscribed RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; the relevant RAN open data being subscribed; the object associated with the subscribed RAN open data; the subscription open time period; the reporting frequency of the subscribed RAN open data; and the reporting time limit information of the subscribed RAN open data. Machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; reporting of triggered events.

7. The method according to claim 1, wherein, The data open subscription response message includes one of the following: information about third-party applications or services subscribed to RAN open data; the identity identifier of the core network functional entity of the subscribed RAN open data; or subscription identification information.

8. The method according to claim 1, further comprising: Receive the RAN data open notification message sent by the second network element.

9. The method according to claim 8, wherein, The RAN data open notification message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; the relevant RAN open data subscribed to; the object associated with the subscribed RAN open data; and the RAN data open time period.

10. The method according to claim 1, further comprising: Send a RAN data open subscription cancellation request message to the second network element; Receive the RAN data open subscription cancellation response message sent by the second network element.

11. The method according to claim 10, wherein, The RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the RAN open data; the identity identifier of the core network functional entity subscribed to the RAN open data; and subscription identification information.

12. A communication method applied to a second network element, comprising: Receive the Radio Access Network (RAN) Data Open Subscription Request message sent by the first network element; Send a RAN data open subscription response message to the second network element.

13. The method according to claim 12, further comprising: Send a registration request message to the third network element; wherein the registration request message includes the enhanced configuration file of the second network element.

14. The method according to claim 13, wherein, The enhanced configuration file of the second network element is used to carry data open capability information of RAN nodes in the associated area; wherein, the data open capability information includes at least one of the following: radio access network node identifier; supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support status; service area information; list of resident terminals; supported cell types; supported network slices; machine learning support status; machine learning model accuracy monitoring capability; federated learning support status; metadata provision capability; historical analysis performance; historical response time.

15. The method according to claim 12, wherein, The RAN data open subscription request message includes at least one of the following: information about the third-party application or service for the subscribed open data; the identity identifier of the core network functional entity for the subscribed open data; the relevant open data for the subscription; the object associated with the subscribed open data; the open time period for the subscription; the reporting frequency of the subscribed open data; and the reporting time limit information for the subscribed open data. Machine learning capabilities; machine learning model accuracy monitoring capabilities; federated learning capabilities; reporting of triggered events.

16. The method according to claim 12, wherein, The RAN data open subscription response message includes one of the following: information about the third-party application or service subscribed to the open data; the identity identifier of the core network functional entity subscribed to the open data; or subscription identification information.

17. The method according to claim 12, further comprising: Send a RAN data open notification message to the second network element.

18. The method according to claim 17, wherein, The RAN data open notification message includes at least one of the following: information about the third-party application or service for the subscribed open data; the identity identifier of the core network functional entity for the subscribed open data; the relevant open data for the subscription; the object associated with the subscribed open data; and the data open period.

19. The method according to claim 12, further comprising: Receive the RAN data open subscription cancellation request message sent by the first network element; Return a RAN data open subscription cancellation response message to the second network element.

20. The method according to claim 19, wherein, The RAN data open subscription cancellation response message includes at least one of the following: information about the third-party application or service subscribed to the open data; the identity identifier of the core network functional entity subscribed to the open data; and subscription identification information.

21. The method according to claim 12, wherein when the second network element is a Session Management Function (SMF), the method further comprises: Receive the data open capability information supported by the RAN node reported by the fourth network element.

22. The method according to claim 12, wherein when the second network element is an SMF, the method further comprises: Receive updated data access capability information supported by the RAN node reported by the fourth network element.

23. The method according to claim 17, wherein when the second network element is an SMF, the method further comprises: Send a RAN data access request message to the fourth network element; Receive the RAN data open response message sent by the fourth network element.

24. A communication device, comprising: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any one of claims 1-11 or 12-23 above.

25. A storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of claims 1-11 or 12-23.

Images