Communication method, communication device and storage medium

Abstract

The present application provides a communication method, a communication device and a storage medium. A first communication device is an access network node, and the communication method applied to the first communication device comprises: receiving a first data opening request message sent by a second communication device; and reporting to the second communication device a first data opening response message carrying open data.

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 communication device, wherein the first communication device is an access network node; the method includes:

[0005] Receive the first data open request message sent by the second communication device;

[0006] Report a first data open response message carrying open data to the second communication device.

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

[0008] Send a first data access request message to the first communication device;

[0009] Receive a first data open response message carrying open data returned by the first communication device.

[0010] This application provides a communication method applied to a first communication device, wherein the first communication device is an access network node; the method includes:

[0011] Send a second data access request message to the second communication device;

[0012] Receive the second data open response message sent by the second communication device.

[0013] This application provides a communication method applied to a second communication device, including:

[0014] Receive the second data open request message sent by the first communication device;

[0015] Send a second data open response message to the first communication device.

[0016] This application provides a communication device applied to a first communication device, comprising:

[0017] The receiving module is configured to receive a first data open request message sent by the second communication device;

[0018] The sending module is configured to report a first data open response message carrying open data to the second communication device.

[0019] This application provides a communication device applied to a second communication device, comprising:

[0020] The sending module is configured to send a first data access request message to the first communication device;

[0021] The receiving module is configured to receive a first data open response message carrying open data returned by the first communication device.

[0022] This application provides a communication device applied to a first communication device, comprising:

[0023] The sending module is configured to send a second data access request message to the second communication device;

[0024] The receiving module is configured to receive a second data open response message sent by the second communication device.

[0025] This application provides a communication device applied to a second communication device, comprising:

[0026] The receiving module is configured to receive a second data open request message sent by the first communication device;

[0027] The sending module is configured to send a second data open response message to the first communication device.

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

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

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

[0031] 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

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

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

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

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

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

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

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

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

[0040] Figure 9 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;

[0041] Figure 10 is a flowchart of a UE's data openness capability information acquisition according to an embodiment of this application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0066] 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, the NEF / NWDAF establishes a connection with the Access and Mobility Management Function (AMF) through a Service Based Interface (SBI), and the AMF establishes a connection with the RAN node through a traditional peer-to-peer (P2P) network. This embodiment includes a pre-preparation process and a RAN data opening process. The specific process is as follows:

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

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

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

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

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

[0072] Step 2. The AMF forwards the RAN data open request to the Next Generation Radio Access Network (NG-RAN);

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

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

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

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

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

[0078] 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, the NEF / NWDAF establishes a connection with the AMF and the User Plane Function (UPF) through the SBI interface. The AMF and UPF establish a connection with the RAN node through a traditional P2P method. The RAN data open request message from the NEF / NWDAF is forwarded to the RAN node through the AMF, and the RAN open data information is reported to the NEF / NWDAF by the UPF through the General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header. This embodiment includes a pre-preparation process and a RAN data open process. The specific process is as follows:

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

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

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

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

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

[0084] 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;

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

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

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

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

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

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

[0091] 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 Session Management Function (SMF) through the SBI interface. SMF establishes connections with UPF through a traditional P2P method. 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. 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:

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

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

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

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

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

[0097] 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;

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

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

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

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

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

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

[0104] 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:

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

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

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

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

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

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

[0111] 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;

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

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

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

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

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

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

[0118] 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 communication device. Exemplarily, the first communication device can be a radio access network node (hereinafter referred to as an access network node or RAN node). As shown in FIG5, this embodiment includes: S110-S120.

[0119] S110, Receive the first data open request message sent by the second communication device.

[0120] In one example, the first data access request message can be a message used to request RAN data; for example, the first data access request message can be a RAN data access request message. The second communication device can initiate a RAN data access request process by sending a RAN data access request message to the first communication device, and request the first communication device to access the associated RAN data.

[0121] In one example, the second communication device may include one of the following: an AMF, another RAN node, or a UE. In one example, the RAN node may exchange information with the AMF. In one example, the RAN node may exchange information with other RAN nodes. In one example, the RAN node may exchange information with the UE.

[0122] S120. Report a first data open response message carrying open data to the second communication device.

[0123] For example, when the first data open response message is a RAN data open response message, the corresponding first data open response message can be a RAN data open response message. In one example, after receiving the first data open request message sent by the second communication device, the first communication device can reply to the second communication device with the first data open response message to respond to the first data open request message, thereby completing the interaction process of exchanging RAN open data between the first communication device and the second communication device.

[0124] In one embodiment, open data includes at least one of the following: cell configuration information; cell measurement information; cell resource load information; cell beam information; cell power consumption information; terminal mobility parameters; and terminal resource load information. In one example, open data may also be referred to as open events. In one example, cell configuration information may include, but is not limited to, at least one of the following: Discontinuous Reception (DRX) configuration, beam configuration, Synchronization Signal Block (SSB) configuration, measurement configuration, cell selection and reselection configuration, Frequency-Division Duplexing / Time-Division Duplexing (FDD / TDD), Resource Scheduling Allocation Bitmap, and band. In one example, cell measurement information may include, but is not limited to, at least one of the following: cell identity (ID), radio link quality information (such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), CQI, Signal to Interference plus Noise Ratio (SINR), Modulation and Coding Scheme (MCS), etc.), Intra and inter Radio Access Technology (RAT) measurement reports, Cell Global Identity (CGI) reports and / or Measurement Interval (GAP), uplink channel status (e.g., Sounding Reference Signal (SRS), ACK count, or NACK counts), downlink channel status (e.g., Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), Acknowledgment count (ACK count), or Non-Acknowledgment count (NACK counts)).In one example, cell resource load information may include, but is not limited to, at least one of the following: cell ID, PRB occupancy, CCE utilization, throughput, latency, spectral efficiency, average / maximum number of active users or connections, and number of active users scheduled per transmission time interval (TTI). Cell beam information may include, but is not limited to, at least one of the following: cell ID, such as beam resource usage, beam configuration, and beam failure statistics (e.g., number of failures, reasons for failures, duration of failures, and beam switching frequency). In one example, cell energy consumption information may include, but is not limited to, at least one of the following: cell ID, peak energy consumption (the highest energy consumption of the cell in a certain time period (kWh)), average energy consumption (the average energy consumption of the cell in a certain time period (kWh)), energy consumption record timestamp, remote radio unit (RRU) energy consumption data, base band unit (BBU) energy consumption data, power parameters (e.g., transmit power, receive power), number of active users in the cell, energy-saving events (recording the application and effect of energy-saving measures), environmental factors (e.g., temperature, humidity, climate conditions, etc.), abnormal energy consumption events, and green energy usage. In one example, terminal mobility parameters may include, but are not limited to, at least one of the following: UE ID, UE location, handover events (handover trigger timestamp, handover frequency, handover success rate, handover failure reason, etc.), moving speed, and changes in moving direction. In one example, terminal resource load information may include, but is not limited to, at least one of the following: UE ID, Physical Resource Block (PRB) occupancy rate, Control Channel Element (CCE) utilization rate, battery status (remaining battery power and battery consumption rate), UE hardware status (e.g., Central Processing Unit (CPU) utilization rate and memory utilization rate), and connection status (e.g., the time the UE is in RRC connected or idle state, the length of time the connection is held, and the probability of successfully establishing a connection).

[0125] In one embodiment, the communication method applied to the first communication device further includes: sending a first data open capability to a second communication device; wherein the first data open capability is data open capability information supported by the first communication device; and receiving a first response message returned by the second communication device. In one example, the first communication device may send its supported data open capability information to the second communication device and receive the first response message returned by the second communication device, so as to indicate whether the second communication device supports the first data open capability requested from the first communication device through the first response message. Exemplarily, the first data open capability may be a RAN data open capability.

[0126] In one embodiment, the first data openness capability includes at least one of the following: supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; list of resident terminals; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; and historical response time. In one example, 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: support for raw data, support for reporting analysis data, and support for aggregating data from other NG-RAN nodes. In one example, supported open data types refer to the data types that the RAN node supports opening externally, 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, analysis data reporting latency may include RAN data collection time and analysis report generation time. In one example, the accuracy of the analysis function refers to the RAN node being configured with different accuracy parameters for different open analysis tasks. The difference between the quantitative analysis result and the true value of this accuracy parameter can help consumers assess the reliability of NG-RAN open analysis and select an NG-RAN node that suits their needs. The open analysis tasks can include at least one of the following: signal strength assessment tasks, user experience analysis tasks, and classification tasks. The parameters used to measure the accuracy parameter can 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 that the current NG-RAN node can use for open processing. The load information can include, but is not limited to, one of the following: the number of ongoing open analysis tasks, CPU or memory utilization, etc. In one example, the green computing support status is used to indicate whether the open functions of the NG-RAN node use green computing technology. If the open functions of the NG-RAN node use green computing technology, this green computing support status metric can be used to reflect this, so as to help consumers consider this energy efficiency factor when selecting network functions (NFs).In one example, the service area information describes the geographical area or cell range covered by the open functions of the NG-RAN node; it can be represented in the form of Tracking Area Identity (TAI), Cell ID, Cell ID List, or location coordinates. In one example, the resident terminal list describes the list of resident UE IDs associated with the NG-RAN node. In one example, the supported cell types describe the cell types that the NG-RAN node supports for analysis; for example, cell types may include, but are not limited to, macro cells, micro cells, or indoor cells. In one example, the supported network slice terminology describes the Single-Network Slice Selection Assistance Information (S-NSSAI) supported by the open functions of the NG-RAN node, which can help consumers select the NG-RAN instance suitable for a specific network slice. In one example, the machine learning support status describes whether the open functions of the NG-RAN node support the training and deployment of machine learning (ML) models. In one example, machine learning model accuracy monitoring capability describes whether the open functions of the Multi-Generation Radio Access Network (MG-RAN) node can monitor the accuracy of machine learning models and the accuracy of analysis tasks. In another example, federated learning support describes whether the open functions of the NG-RAN node support federated learning. In yet another example, metadata provision capability provides attribute information such as the source, timestamp, and format of RAN data. In one 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 judge the reliability of the NG-RAN's open functions. In yet another example, historical response time records the average response time of the NG-RAN node's open functions in performing analysis tasks in the past, helping consumers select NG-RAN nodes with faster response times.

[0127] In one embodiment, the first response message includes: support status of a first data open capability. In one example, the support status of the first data open capability is used to indicate whether the second communication device supports the first data open capability requested from the first communication device. Exemplarily, the first data open capability is a RAN data open capability, the first communication device can be a RAN node, and the second communication device can be an AMF, that is, the support status of the first data open capability is used to indicate whether the AMF supports the RAN data open capability requested from the RAN node.

[0128] In one embodiment, the message carrying the first data open capability is a connection establishment request message, and correspondingly, the first response message is a connection establishment response message. In one example, the first communication device can send a connection establishment request message to the second communication device, carrying its supported data open capability information in the connection establishment request message; after receiving the connection establishment request message carrying the first data open capability, the second communication device replies to the first communication device with a connection establishment response message, thereby replying to the first communication device via a configuration update request message whether it supports the first data open capability requested from the first communication device.

[0129] In one embodiment, the message carrying the first data open capability is a configuration update request message, and correspondingly, the first response message is a configuration update confirmation message. In one example, the first communication device can send a configuration update request message to the second communication device, carrying its supported data open capability information in the configuration update request message; after receiving the configuration update request message carrying the first data open capability, the second communication device replies to the first communication device with a configuration update request message, thereby replying to the first communication device whether it supports the first data open capability requested from the first communication device.

[0130] In one embodiment, the first data open request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of requested open data.

[0131] The requested open data list includes at least one of the following: information about the third-party application or service requesting open data; the identity identifier of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event. For example, the identity identifier of the first communication device can be the RAN node ID; the identity identifier of the second communication device can be the AMF ID, UE ID, or other RAN node ID. In one example, the message type refers to the management type of the RAN open data. In one example, the requested open data list can be a list of information about the requested RAN open data, and correspondingly, all related information included in it is related to the request for RAN open data. In one example, the information about the third-party application or service requesting open data refers to the information about the third-party application or service requesting 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 requesting open data refers to the identity identifier of the core network functional entity requesting RAN open data, such as, but not limited to, at least one of the following: NEF ID, NWDAF ID. In one example, the requested open data refers to the RAN open data related to the request, which may include, but is not limited to, at least one of the following: specific RAN parameter names, RAN open data predefined events (RAN open data IDs). In one example, the object associated with the requested open data refers to the object associated with the requested RAN open data, which may include, but is not limited to, at least one of the following: the requested open data is about a specific UE (UE ID), certain UEs (UE ID List), a specific cell (Cell ID), certain cells (Cell ID List), a specific TAI region (TAI), certain TAI regions (TAI List), a region (a region enclosed by multiple coordinates), etc. In one example, the requested open time period may include, but is not limited to, at least one of the following: the requested open, analyzed, or predicted RAN open data is from time xx to time xx. In one example, the reporting frequency of the requested open data refers to the reporting frequency of the requested RAN open data, which may include, but is not limited to, at least one of the following: one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc. In one example, the time limit information for requesting open data reporting may include, for example, at least one of the following: reporting no later than xx time point, or reporting starting from xx time point.In one example, the reported triggering event may include, but is not limited to, at least one of the following: 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 occurs, green energy usage is higher or lower than xx, UE handover frequency is higher than xx, UE handover success rate is lower than xx, UE connection establishment success rate is lower than xx, UE CPU utilization is higher than xx, UE battery level is lower than xx, etc.

[0132] In one embodiment, the first data open response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data in response.

[0133] The response list of open data includes at least one of the following: the response status of the open data request; and the relevant open data requested for opening. It should be noted that the explanations of message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the response list of open data refers to the information list of the RAN open data in response. Correspondingly, the response status of the open data request refers to the response status of the RAN open data request, which may include, for example, success or failure. In one example, the relevant open data requested for opening may include, but is not limited to, one of the following: specific RAN parameter names, RAN open data predefined events (RAN open data ID), corresponding to the architecture 1 where the RAN node can directly report RAN open data to the AMF.

[0134] In one embodiment, the communication method applied to the first communication device further includes: receiving a first data open modification request message sent by a second communication device; and returning a first data open modification response message to the second communication device. In one example, the first data open modification request message can be a message for requesting modification of RAN data; for example, the first data open modification request message can be a RAN data open modification request message. The second communication device can initiate a RAN data open modification process by sending a RAN data open modification request message to the first communication device, and request the first communication device to modify the associated RAN open data. In one example, the second communication device can include one of the following: an AMF, other RAN nodes, or a UE. In one example, the RAN node can interact with the AMF. In one example, the RAN node can interact with other RAN nodes. In one example, the RAN node can interact with the UE. Exemplarily, when the first data open modification response message is a RAN data open modification response message, the corresponding first data open modification response message can be a RAN data open modification response message. In one example, after receiving a first data open modification request message from a second communication device, the first communication device can reply with a first data open modification response message to the second communication device to respond to the first data open modification request message and complete the process of modifying RAN open data between the first and second communication devices.

[0135] In one embodiment, the first data open modification request message includes at least one of the following: a message type; an identity identifier of a first communication device; an identity identifier of a second communication device; a list of open data to be modified; or a list of open data to be released.

[0136] The list of open data to be modified shall include at least one of the following: information on third-party applications or services of the open data to be modified; the identity of the core network functional entity of the open data to be modified; the relevant open data to be modified; the object associated with the open data to be modified; the open time period to be modified; the reporting frequency of the open data to be modified; the reporting time limit information of the open data to be modified; and the reporting triggering event for the modification.

[0137] The list of open data to be released includes at least one of the following: information about third-party applications or services of the open data to be released; the identity identifier of the core network functional entity of the open data to be released; the open data to be released; and the object associated with the open data to be released. In one example, it should be noted that the explanations of message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the list of open data to be modified can be a list of information about the RAN open data to be modified. Correspondingly, the relevant information about the open data to be modified contained therein is all relevant information about the RAN open data to be modified. In one example, the information about third-party applications or services of the open data to be modified refers to the information about the third-party applications or services of the RAN open data to be modified, 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 of the open data to be modified refers to the identity identifier of the core network functional entity of the RAN open data to be modified, such as, but not limited to, at least one of the following: NEF ID and NWDAF ID. In one example, the requested modification of the relevant open data refers to the RAN open data related to the requested modification, which may include, but is not limited to, at least one of the following: a specific RAN parameter name, a predefined RAN open data event (RAN open data ID). In one example, the object associated with the requested modification of the open data refers to the object associated with the requested modification of the RAN open data, which may include, but is not limited to, at least one of the following: the requested modification of the RAN open data pertains to a specific UE (UE ID), certain UEs (UE ID List), a specific cell (Cell ID), certain cells (Cell ID List), a specific TAI region (TAI), certain TAI regions (TAI List), a region (a region enclosed by multiple coordinates), etc. In one example, the requested modification of the open time period may include, but is not limited to, at least one of the following: the requested open, analyzed, or predicted RAN open data is from time xx to time xx. In one example, the reporting frequency of the requested modification of the open data refers to the reporting frequency of the requested RAN open data, which may include, but is not limited to, at least one of the following: one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc. In one example, the reporting time limit information for the requested modified open data may include, for example, at least one of the following: reporting no later than xx time point, or reporting starting from xx time point.In one example, the reporting triggering event for the modification request may include, but is not limited to, at least one of the following: 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 occurs, green energy usage is higher or lower than xx, UE handover frequency is higher than xx, UE handover success rate is lower than xx, UE connection establishment success rate is lower than xx, UE CPU utilization is higher than xx, UE battery level is lower than xx, etc.

[0138] In one example, the list of open data to be released refers to the list of RAN open data to be released, which includes relevant information about the open data to be released. In another example, the information about third-party applications or services in the open data to be released refers to information about the third-party applications or services in the RAN open data to be released, such as application ID, service ID, application type, service type, service description, etc.; the identity identifier of the core network functional entity in the open data to be released refers to the identity identifier of the core network functional entity in the RAN open data to be released, such as NEF ID, NWDAF ID; the open data to be released refers to the RAN open data to be released, such as specific RAN parameter names, RAN open data predefined events (RAN open data ID); the object associated with the open data to be released refers to the object associated with the open data to be released, such as the RAN open data to be released 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.

[0139] In one embodiment, the first data open modification response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data modification request information in response.

[0140] The response list of open data modification request information includes at least one of the following: the response status of the open data modification request; and the relevant open data to be modified. It should be noted that the explanations of message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the response list of open data modification request information refers to the information list of RAN open data modification requests. Correspondingly, the response status of the open data modification request refers to the response status of the RAN open data modification request, which may include, for example, success or failure. In one example, the relevant open data to be modified may include, but is not limited to, one of the following: the specific RAN parameter name, the RAN open data predefined event (RAN open data ID), corresponding to the architecture 1 where the RAN node can directly report RAN open data to the AMF.

[0141] In one embodiment, the communication method applied to the first communication device further includes: receiving a first data open release request message sent by a second communication device; and returning a first data open release response message to the second communication device. In one example, the first data open release request message can be a message for requesting the release of RAN data; for example, the first data open release request message can be a RAN data open release request message. The second communication device can initiate a RAN data open release procedure by sending a RAN data open release request message to the first communication device, and request the first communication device to release the associated RAN open data. In one example, the second communication device can include one of the following: an AMF, other RAN nodes, or a UE. In one example, the RAN node can interact with the AMF. In one example, the RAN node can interact with other RAN nodes. In one example, the RAN node can interact with the UE. Exemplarily, when the first data open release response message is a RAN data open release response message, the corresponding first data open release response message can be a RAN data open release response message. In one example, after receiving a first data open release request message from a second communication device, the first communication device can reply with a first data open release response message to the second communication device to respond to the first data open release request message and complete the process of releasing open RAN data between the first and second communication devices.

[0142] In one embodiment, the first data release request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0143] The list of open data to be released shall include at least one of the following: information about third-party applications or services for the open data to be released; the identity identifier of the core network functional entity of the open data to be released; the relevant open data to be released; and the object associated with the open data to be released. It should be noted that explanations of the message type, the identity identifier of the first communication device, the identity identifier of the second communication device, the list of open data to be released, and the related information contained in the list of open data to be released can be found in the description of the above embodiments, and will not be repeated here.

[0144] In one embodiment, the first data release response message includes at least one of the following: message type; identification of the first communication device; identification of the second communication device; and a list of open data release request information in response.

[0145] The response list of open data release request information includes at least one of the following: the response status of the open data release request. It should be noted that the explanations of message type, the identity of the first communication device, and the identity of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the response list of open data release request information refers to the information list for releasing RAN open data; correspondingly, the response status of the open data release request refers to the response status of the RAN open data release request, which may include, for example, success or failure.

[0146] In one embodiment, the communication method applied to the first communication device further includes: sending a first data open release notification message to the second communication device; and receiving a first data open release confirmation message returned by the second communication device. In one example, the first data open release notification message can be a message used to inform the second communication device of the release of RAN open data; for example, the first data open release notification message can be a RAN data open release notification message. The second communication device can initiate a RAN data open release notification process by sending a RAN data open release notification message to the first communication device, and notify the first communication device to release the associated RAN open data. In one example, the second communication device can include one of the following: an AMF, other RAN nodes, or a UE. In one example, the RAN node can interact with the AMF. In one example, the RAN node can interact with other RAN nodes. In one example, the RAN node can interact with the UE. Exemplarily, when the first data open release confirmation message is a RAN data open release confirmation message, the corresponding first data open release confirmation message can be a RAN data open release confirmation message. In one example, after receiving a first data open release notification message from a second communication device, the first communication device can reply with a first data open release confirmation message to the second communication device to respond to the first data open release notification message and complete the process of exchanging RAN open data release notifications between the first and second communication devices.

[0147] In one embodiment, the first data release notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0148] The list of open data released in the notification includes at least one of the following: information about third-party applications or services releasing the open data; the identity identifier of the core network functional entity releasing the open data; related open data released in the notification; the object associated with the open data released in the notification; and the reason for release. It should be noted that the explanations of the message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the information of third-party applications or services in the released open data refers to the information of third-party applications or services in the released RAN open data, such as application ID, service ID, application type, service type, service description, etc.; the identity identifier of the core network functional entity in the released open data refers to the identity identifier of the core network functional entity in the released RAN open data, such as NEF ID, NWDAF ID; the released open data refers to the released RAN open data, such as specific RAN parameter names, RAN open data predefined events (RAN open data ID); the object associated with the released open data refers to the object associated with the released RAN open data, such as the released 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.; the release reason may include, but is not limited to, one of the following: the UE moves out of the RAN node coverage area, the RAN node is no longer using green resources, etc.

[0149] In one embodiment, the first data release confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a confirmed list of open data release request information.

[0150] The confirmed list of open data release request information includes at least one of the following: the response status of the data release request. It should be noted that the explanations of message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the confirmed list of open data release request information refers to the confirmed list of information for releasing RAN open data; correspondingly, the response status of the open data release request refers to the response status of the RAN open data release request, which may include, for example, success or failure.

[0151] In one embodiment, the communication method applied to the first communication device further includes: sending a first data open modification notification message to the second communication device; and receiving a first data open modification confirmation message returned by the second communication device. In one example, the first data open modification notification message can be a message used to inform the second communication device of the modified RAN open data; for example, the first data open modification notification message can be a RAN data open modification notification message. The second communication device can initiate a RAN data open modification notification process by sending a RAN data open modification notification message to the first communication device, and notify the first communication device to modify the associated RAN open data. In one example, the second communication device can include one of the following: an AMF, other RAN nodes, or a UE. In one example, the RAN node can interact with the AMF. In one example, the RAN node can interact with other RAN nodes. In one example, the RAN node can interact with the UE. Exemplarily, when the first data open modification confirmation message is a RAN data open modification confirmation message, the corresponding first data open modification confirmation message can be a RAN data open modification confirmation message. In one example, after receiving a first data open modification notification message from a second communication device, the first communication device can reply with a first data open modification confirmation message to the second communication device to respond to the first data open modification notification message and complete the process of exchanging RAN open data modification notifications between the first and second communication devices.

[0152] In one embodiment, the first data open modification notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be modified.

[0153] The list of open data to be modified includes at least one of the following: information about third-party applications or services whose open data has been modified; the identity identifier of the core network functional entity whose open data has been modified; the related open data to be modified; the object associated with the open data whose open data has been modified; and the reason for the modification. It should be noted that the explanations of the message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the information of the third-party application or service in the notified modified open data refers to the information of the third-party application or service in the notified modified RAN open data, such as application ID, service ID, application type, service type, service description, etc.; the identity identifier of the core network functional entity in the notified modified open data refers to the identity identifier of the core network functional entity in the notified modified RAN open data, such as NEF ID, NWDAF ID; the notified modified open data refers to the notified modified RAN open data, such as specific RAN parameter names, RAN open data predefined events (RAN open data ID); the object associated with the notified modified open data refers to the object associated with the notified modified RAN open data, such as the notified modified 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.; the modification reason may include, but is not limited to, one of the following: the UE moves out of the RAN node coverage area, the RAN node configuration is updated, etc.

[0154] In one embodiment, the first data open modification confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of confirmed open data modification request information.

[0155] The confirmed list of open data modification request information includes at least one of the following: the response status of the open data modification request; information about the third-party application or service requesting modification of the open data; the identity identifier of the core network functional entity requesting modification of the open data; the relevant open data to be modified; the object associated with the open data to be modified; the open time period for the request modification; the reporting frequency of the open data to be modified; the reporting time limit information of the open data to be modified; and the reporting trigger event for the request modification. It should be noted that explanations of message type, identity identifier of the first communication device, identity identifier of the second communication device, response status of the open data modification request, information about the third-party application or service requesting modification of the open data, identity identifier of the core network functional entity requesting open data, relevant open data to be modified, object associated with the open data to be modified, open time period for the request modification, reporting frequency of the open data to be modified, reporting time limit information of the open data to be modified, and reporting trigger event for the request modification can be found in the description of the above embodiments, and will not be repeated here.

[0156] In one embodiment, the communication method applied to the first communication device further includes: receiving a first data open reporting notification message sent by the second communication device. In one example, if the requested open RAN data needs to be reported periodically, a new message for RAN open data management is defined, for example, it can be a first data open reporting notification message, which can be a RAN data open reporting notification message used to report RAN open data.

[0157] In one embodiment, the first data open reporting notification message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of open data request information in response.

[0158] The response list of open data request information includes at least the requested open data. It should be noted that the explanations of message type, the identity identifier of the first communication device, and the identity identifier of the second communication device can be found in the description of the above embodiments, and will not be repeated here. In one example, the response list of open data request information is a response list of RAN open data request information. For example, this response list of RAN open data request information may include the requested open data, such as specific RAN parameter names, RAN open data predefined events (RAN open data ID) corresponding one-to-one with architecture Option 1, and RAN nodes directly reporting RAN open data to the AMF.

[0159] In one embodiment, the communication method applied to the first communication device further includes: sending a GTP-U extension header for open data transmission to the third communication device;

[0160] The GTP-U extension header includes at least one of the following: Packet Data Unit (PDU) type; or a list of open data request information in response.

[0161] The response list of open data request information shall include at least one of the following: information about the third-party application or service requesting modification of the open data; the identity identifier of the core network functional entity requesting the open data; a predefined data open event identifier; relevant parameters of the data open event; and the identity identifier of the object associated with the open data. In one example, the response list of open data request information may be a predefined list of RAN data open events, and correspondingly, the data open events or related information of the open data contained in the response list shall be RAN data open events or related information of RAN open data. In one example, the information of the third-party application or service requesting modification of open data can be the information of the third-party application or service requesting modification of RAN open data, such as application ID, service ID, application type, service type, service description, etc.; the identity identifier of the core network function entity requesting open data can be the identity identifier of the core network function entity requesting RAN open data, such as NEF ID, NWDAF ID; a predefined data open event identifier; the relevant parameters of the data open event refer to the relevant parameters of the RAN data open event; the object identity identifier associated with the open data refers to the object identity identifier associated with the RAN open data, such as, but not limited to, at least one of the following: UE ID, UE ID List, Cell ID, Cell ID list, TAI, TAI list, area description, etc.

[0162] In one embodiment, the second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

[0163] 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 communication device. As shown in FIG6, this embodiment includes:

[0164] S210, Send a first data open request message to the first communication device.

[0165] S220: Receive a first data open response message carrying open data returned by the first communication device.

[0166] In one embodiment, the open data includes at least one of the following: cell configuration information; cell measurement information; cell resource load information; cell beam information; cell energy consumption information; terminal mobility parameters; and terminal resource load information.

[0167] In one embodiment, the communication method applied to the second communication device further includes:

[0168] Receive a first data open capability sent by a first communication device; wherein, the first data open capability is data open capability information supported by the first communication device;

[0169] Return the first response message to the first communication device.

[0170] In one embodiment, the first data openness capability includes at least one of the following: 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 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; and historical response time.

[0171] In one embodiment, the first response message includes: the support status of the first data open capability.

[0172] In one embodiment, the bearer message for the first data open capability is a connection establishment request message, and correspondingly, the first response message is a connection establishment response message.

[0173] In one embodiment, the carrier message for the first data open capability is a configuration update request message, and the corresponding first response message is a configuration update confirmation message.

[0174] In one embodiment, the first data open request message includes at least one of the following: message type; identity identifier of the first communication device; and a list of requested open data.

[0175] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0176] In one embodiment, the first data open response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data in response.

[0177] The open data list in the response shall include at least one of the following: the response status of the data openness request; or the relevant data requested to be open.

[0178] In one embodiment, the communication method applied to the second communication device further includes:

[0179] Send a first data open modification request message to the first communication device;

[0180] Receive the first data open modification response message returned by the first communication device.

[0181] In one embodiment, the first data open modification request message includes at least one of the following: a message type; an identity identifier of a first communication device; an identity identifier of a second communication device; a list of open data to be modified; or a list of open data to be released.

[0182] The list of open data to be modified shall include at least one of the following: information of the third-party application or service requesting modification of the open data; the identity of the core network functional entity requesting modification of the open data; the open data to be modified; the object associated with the open data to be modified; the open time period for the request to be modified; the reporting frequency of the open data to be modified; the reporting time limit information for the open data to be modified; and the reporting triggering event for the request to be modified.

[0183] The list of open data to be released shall include at least one of the following: information of third-party applications or services for which open data is to be released; the identity of the core network functional entity for which open data is to be released; the open data to be released; and the object associated with the open data to be released.

[0184] In one embodiment, the first data open modification response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data modification request information in response.

[0185] The response list of open data modification request information shall include at least one of the following: the response status of the open data modification request; and the relevant open data to be modified.

[0186] In one embodiment, the communication method applied to the second communication device further includes:

[0187] Send a first data release request message to the first communication device;

[0188] Receive the first data open release response message returned by the first communication device.

[0189] In one embodiment, the first data release request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0190] The list of open data to be released shall include at least one of the following: information about third-party applications or services of the open data to be released; the identity identifier of the core network functional entity of the open data to be released; the relevant open data to be released; and the object associated with the open data to be released.

[0191] In one embodiment, the first data release response message includes at least one of the following: message type; identification of the first communication device; identification of the second communication device; and a list of open data release request information in response.

[0192] The response list of open data release request information shall include at least one of the following: the response status of the data release request.

[0193] In one embodiment, the communication method applied to the second communication device further includes:

[0194] Receive the first data release notification message sent by the first communication device;

[0195] Return a first data release confirmation message to the first communication device.

[0196] In one embodiment, the first data release notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0197] The list of open data released in the notification shall include at least one of the following: information about third-party applications or services of the open data released in the notification; the identity identifier of the core network functional entity of the open data released in the notification; the relevant open data released in the notification; the object associated with the open data released in the notification; and the reason for the release.

[0198] In one embodiment, the first data release confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a confirmed list of open data release request information.

[0199] The confirmed list of open data release request information includes at least one of the following: the response status of the data release request.

[0200] In one embodiment, the communication method applied to the second communication device further includes:

[0201] Receive the first data open modification notification message sent by the first communication device;

[0202] The first data open modification confirmation message is returned to the first communication device.

[0203] In one embodiment, the first data open modification notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be modified.

[0204] The list of open data to be modified in the notification shall include at least one of the following: information on third-party applications or services of the open data to be modified in the notification; the identity identifier of the core network functional entity of the open data to be modified in the notification; the relevant open data to be modified in the notification; the object associated with the open data to be modified in the notification; and the reason for the modification.

[0205] In one embodiment, the first data open modification confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of confirmed open data modification request information.

[0206] The confirmed list of open data modification request information shall include at least one of the following: the response status of the open data modification request; information of the third-party application or service requesting the open data; the identity of the core network functional entity requesting the open data; the access network open data to be modified; the object associated with the data to be modified; the time period for the modification; the reporting frequency of the modified open data; the reporting time limit information of the modified open data; and the reporting trigger event for the modification.

[0207] In one embodiment, the communication method applied to the second communication device further includes:

[0208] Send a first data open reporting notification message to the first communication device.

[0209] In one embodiment, the first data open reporting notification message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of open data request information in response.

[0210] The response list of open data request information should include at least the relevant data requested to be made available.

[0211] In one embodiment, the second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

[0212] It should be noted that the explanations of parameters such as the first data open request message, the first data open response message, the first data open capability, the first response message, the first data open modification request message, the first data open modification response message, the first data open release request message, the first data open release response message, the first data open release notification message, the first data open release confirmation message, the first data open modification notification message, the first data open modification confirmation message, and the first data open reporting notification message in the communication method applied to the first communication device can be found in the descriptions of the corresponding parameters in the communication method applied to the first communication device above, and will not be repeated here.

[0213] In one embodiment, FIG7 is a flowchart of another communication method provided by an embodiment of this application. This embodiment can be executed by a first communication device. Exemplarily, the first communication device can be a network side (e.g., a RAN node). This embodiment describes the process of obtaining UE data open capability information. As shown in FIG7, this embodiment includes:

[0214] S310, Send a second data open request message to the second communication device.

[0215] For example, the second communication device can be a terminal (e.g., a UE). In one example, when a third-party application or service wants to request the first communication device to open relevant information about the UE, the first communication device interacts with the second communication device to obtain the relevant information. The first communication device sends a second data open request message to the second communication device to request information to be opened by the RAN. S320: Receive the second data open response message sent by the second communication device.

[0216] The second communication device sends a second data open response message to the first communication device and reports relevant information through the second data open response message. In one embodiment, the communication method applied to the first communication device further includes:

[0217] A first request message is sent to a second communication device; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device;

[0218] The system receives a second response message carrying a second data open capability sent by a second communication device. Exemplarily, the second communication device can be a terminal (e.g., a UE). In one example, the first communication device can send a first request message to the second communication device to inquire whether the second communication device supports RAN open data. In an embodiment, the second communication device sends a second response message to the first communication device, indicating whether the second communication device supports RAN open data.

[0219] In one embodiment, the first request message is a terminal capability acquisition message, and the corresponding second response message is terminal capability information.

[0220] In one embodiment, the second data access request message is carried in the RRC configuration message.

[0221] In one embodiment, the second data open response message is carried in the UE assistance message.

[0222] In one embodiment, the second data open request message includes at least one of the following: message type; identification of the second communication device; and a list of requested open data.

[0223] The requested open data list shall include at least one of the following: information about the third-party application or service requesting open data; the identity identifier of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event. In one example, the requested open data list refers to the list of data requested by the UE. In one example, the information of the third-party application or service requesting open data refers to the information of the third-party application or service requesting open data from the RAN, such as application ID, service ID, application type, service type, service description, etc.; the relevant open data requested refers to the data requested from the UE, 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's time in RRC connected, idle state, length of time to maintain connection, probability of successful connection establishment), etc.; the requested open time period can include one of the following: the requested open data is from time xx to time xx; the reporting frequency of the requested open data can include one of the following: one-time reporting, periodic reporting (reporting once every xx seconds), event-triggered reporting, etc.; the reporting time limit information of the requested open data, such as reporting no later than time xx, reporting starting from time xx; the description information of the event triggering the request, such as the success rate of UE connection establishment is lower than xx, the CPU utilization rate of UE is higher than xx, the battery level of UE is lower than xx, etc.

[0224] In one embodiment, the second data open response message includes at least one of the following: reporting the decision to open its own data to a third-party application or service; requesting relevant data to be opened; and a response list of open data requests.

[0225] In one example, the decision to report one's own open data to a third-party application or service refers to whether to agree to report UE-related open data to the third-party application / service. In one example, the relevant data requested to be opened may include at least one of the following: UE ID, PRB utilization rate, CCE utilization rate, battery status (remaining battery power, battery consumption rate), UE hardware status (CPU utilization rate, memory utilization rate), connection status (UE's time in RRC connected and idle states, length of time to maintain connection, probability of successful connection establishment), etc.

[0226] In one embodiment, the communication method applied to the first communication device further includes: sending a second data open modification request message to the second communication device; and receiving a second data open modification response message sent by the second communication device.

[0227] In one embodiment, the second data open modification request message includes at least one of the following: message type; identification of the second communication device; and a list of open data to be modified.

[0228] The list of open data to be modified shall include at least one of the following: information on third-party applications or services of the open data to be modified; the identity identifier of the core network functional entity of the open data to be modified; the relevant open data to be modified; the object associated with the open data to be modified; the open time period to be modified; the reporting frequency of the open data to be modified; the reporting time limit information of the open data to be modified; and the reporting trigger event.

[0229] In one embodiment, the second data open modification response message includes at least one of the following: reporting the decision-making status of its own open data to a third-party application or service; the relevant open data to be modified; and a list of open data modification requests in response.

[0230] In one embodiment, the communication method applied to the first communication device further includes: sending a second data open / release request message to the second communication device; and receiving a second data open / release response message returned by the second communication device.

[0231] In one embodiment, the second data release request message includes at least one of the following: message type; identification of the second communication device; and a list of open data to be released.

[0232] The list of open data to be released shall include at least one of the following: information on third-party applications or services of the open data to be released; identity identifier of the core network functional entity of the open data to be released; related open data to be released; objects associated with the open data to be released; open time period to be released; reporting frequency of the open data to be released; reporting time limit information of the open data to be released; and reporting trigger events.

[0233] In one embodiment, the second data release response message includes at least one of the following: reporting the decision-making status of its own open data to a third-party application or service; requesting the release of the relevant open data; and responding with a list of open data requests for release.

[0234] In one embodiment, the communication method applied to the first communication device further includes: receiving a second data open / release notification message sent by the second communication device; and returning a second data open / release confirmation message to the second communication device.

[0235] In one embodiment, the second data open modification release notification message includes at least one of the following: message type; identification of the second communication device; and a list of open data to be released.

[0236] The list of open data to be released shall include at least one of the following: information of third-party applications or services of the open data to be modified; identity identifier of the core network functional entity of the open data to be modified; related open data to be modified; objects associated with the open data to be modified; open time period to be modified; reporting frequency of the open data to be modified; reporting time limit information of the open data to be modified; and reporting triggering events.

[0237] In one embodiment, the second data release confirmation message includes at least one of the following: reporting the decision-making status of its own data release to a third-party application or service; requesting the release of the relevant data; and responding with a list of data release requests.

[0238] In one embodiment, the communication method applied to the first communication device further includes: receiving a second data open modification notification message sent by the second communication device; and returning a second data open modification confirmation message to the second communication device.

[0239] In one embodiment, the second data open modification notification message includes at least one of the following: message type; identification of the second communication device; and a list of open data to be modified.

[0240] The list of open data to be modified shall include at least one of the following: information on third-party applications or services of the open data to be modified; the identity identifier of the core network functional entity of the open data to be modified; the relevant open data to be modified; the object associated with the open data to be modified; the open time period to be modified; the reporting frequency of the open data to be modified; the reporting time limit information of the open data to be modified; and the reporting trigger event.

[0241] In one embodiment, the second data open modification confirmation message includes at least one of the following: reporting the decision-making status of its own open data to a third-party application or service; the relevant open data to be modified; and a list of open data modification requests in response.

[0242] In one embodiment, the communication method applied to the first communication device further includes: sending a second data open reporting notification message to the second communication device.

[0243] In one embodiment, the second data open reporting notification message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of UE open data request information in response.

[0244] The response list of open data request information shall include at least the relevant UE open data requested.

[0245] It should be noted that the explanation of the second data open modification request message, second data open modification response message, second data open release request message, second data open release response message, second data open release notification message, second data open release confirmation message, second data open modification notification message, second data open modification confirmation message, and second data open reporting notification message, as well as the information contained therein, in the communication method applied to the first communication device, can be found in the description of the relevant information contained in the second data open request message and the second data open response message in the aforementioned communication method applied to the first communication device. The information contained therein is similar, except that each message corresponds to information related to modification and release, respectively, and will not be repeated here.

[0246] In one embodiment, FIG8 is a flowchart of another communication method provided by an embodiment of this application. This embodiment can be executed by a second communication device. As shown in FIG8, this embodiment includes:

[0247] S410: Receive the second data open request message sent by the first communication device.

[0248] S420: Send a second data open response message to the first communication device.

[0249] In one embodiment, the communication method applied to the second communication device further includes:

[0250] Receive a first request message sent by a first communication device; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device;

[0251] Send a second response message carrying the second data open capability to the first communication device.

[0252] The first request message is a terminal capability acquisition message, and the corresponding second response message is terminal capability information.

[0253] In one embodiment, the second data access request message is carried in the RRC configuration message.

[0254] In one embodiment, the second data open response message is carried in the UE assistance message.

[0255] In one embodiment, the second data open request message includes at least one of the following: message type; identification of the second communication device; and a list of requested open data.

[0256] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0257] In one embodiment, the second data open response message includes at least one of the following: reporting the decision to open its own data to a third-party application or service; requesting relevant data to be opened; and a response list of open data requests.

[0258] It should be noted that the explanations of parameters such as the second data open request message, the second data open response message, the first request message, and the second response message involved in the communication method applied to the second communication device can be found in the descriptions of the corresponding parameters in the communication method applied to the first communication device, and will not be repeated here.

[0259] Example 1

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

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

[0262] 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).

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

[0264] Example 2

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

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

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

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

[0269] 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:

[0270] Table 1

[0271] 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 / .

[0272] Table 2

[0273] Example 3

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

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

[0276] 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).

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

[0278] Example 4

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

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

[0281] 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;

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

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

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

[0285] Table 3

[0286] Example 5

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

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

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

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

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

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

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

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

[0295] The requested list of RAN open data;

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

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

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

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

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

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

[0302] 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;

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

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

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

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

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

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

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

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

[0311] Example 6

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

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

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

[0315] 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;

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

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

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

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

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

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

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

[0323] In one example, the list of RAN open data information to be modified includes 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 in the RAN open data to be modified, such as NEF ID, NWDAF ID;

[0326] 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).

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

[0328] 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;

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

[0330] 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;

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

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

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

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

[0335] 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);

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

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

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

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

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

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

[0342] 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;

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

[0344] Example 7

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

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

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

[0348] 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;

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

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

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

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

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

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

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

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

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

[0358] 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).

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

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

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

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

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

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

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

[0366] Example 8

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0389] Example 9

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

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

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

[0393] 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;

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

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

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

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

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

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

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

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

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

[0403] 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);

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

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

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

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

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

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

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

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

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

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

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

[0415] 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).

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

[0417] 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;

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

[0419] 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;

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

[0421] Example 10

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

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

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

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

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

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

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

[0429] 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 Option 1, and the RAN node directly reporting RAN open data to the AMF.

[0430] Example 11

[0431] 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:

[0432] RAN Open Data Request / Response Process;

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

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

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

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

[0437] RAN Open Data Reporting Notification.

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

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

[0440] Source Global NG-RAN Node ID;

[0441] Target Global NG-RAN Node ID.

[0442] Example 12

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

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

[0445] 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 9 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 9, the number of bytes occupied by the RAN Exposure Container and the Next Extension Header Type are 2-(4n-1) and 4n, respectively.

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

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

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

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

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

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

[0452] Predefined RAN open data open event ID;

[0453] Parameters related to RAN data open events;

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

[0455] Example 13

[0456] 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 terminal capability information (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.

[0457] The UE needs to inform the RAN node whether it supports the RAN data openness function. If the UE supports this function, the RAN node can subsequently obtain information for openness from the UE node. Figure 10 is a flowchart of a UE's data openness capability information acquisition according to an embodiment of this application. As shown in Figure 10, the scheme includes the following steps:

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

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

[0460] Example 14

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

[0462] 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:

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

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

[0465] 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:

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

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

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

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

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

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

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

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

[0474] 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:

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

[0476] 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;

[0477] 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).

[0478] 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 Function 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.

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

[0480] Example 15

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

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

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

[0484] 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;

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

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

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

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

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

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

[0491] Table 4

[0492] Example 16

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

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

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

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

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

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

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

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

[0501] 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;

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

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

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

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

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

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

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

[0509] Example 17

[0510] 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:

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

[0512] Example 18

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

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

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

[0516] Example 19

[0517] 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:

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

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

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

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

[0522] Example 20

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

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

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

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

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

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

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

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

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

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

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

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

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

[0536] 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).

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

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

[0539] Example 21

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

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

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

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

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

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

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

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

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

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

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

[0551] 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:

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

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

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

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

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

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

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

[0559] In one embodiment, FIG11 is a structural block diagram of a communication device provided in an embodiment of this application. This embodiment is applied to a first communication device. As shown in FIG11, the communication device in this embodiment includes: a receiving module 510 and a transmitting module 520.

[0560] The receiving module 510 is configured to receive a first data open request message sent by the second communication device;

[0561] The sending module 520 is configured to report a first data open response message carrying open data to the second communication device.

[0562] In one embodiment, the open data includes at least one of the following: cell configuration information; cell measurement information; cell resource load information; cell beam information; cell energy consumption information; terminal mobility parameters; and terminal resource load information.

[0563] In one embodiment, the communication device applied to the first communication device further includes:

[0564] The sending module is also configured to send a first data open capability to the second communication device; wherein, the first data open capability is data open capability information supported by the first communication device;

[0565] The receiving module is also configured to receive a first response message returned by the second communication device.

[0566] In one embodiment, the first data openness capability includes at least one of the following: supported open types; supported open data types; analysis data reporting latency; analysis function accuracy; analysis processing capability; green computing support; service area information; list of resident terminals; supported cell types; supported network slices; machine learning support; machine learning model accuracy monitoring capability; federated learning support; metadata provision capability; historical analysis performance; and historical response time.

[0567] In one embodiment, the first response message includes: the support status of the first data open capability.

[0568] In one embodiment, the bearer message for the first data open capability is a connection establishment request message, and correspondingly, the first response message is a connection establishment response message.

[0569] In one embodiment, the carrier message for the first data open capability is a configuration update request message, and the corresponding first response message is a configuration update confirmation message.

[0570] In one embodiment, the first data open request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of requested open data.

[0571] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0572] In one embodiment, the first data open response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data in response.

[0573] The open data list in the response shall include at least one of the following: the response status of the open data request; or the relevant open data requested to be made available.

[0574] In one embodiment, the communication device applied to the first communication device further includes:

[0575] The receiving module is also configured to receive a first data open modification request message sent by the second communication device;

[0576] The sending module is also configured to return a first data open modification response message to the second communication device.

[0577] In one embodiment, the first data open modification request message includes at least one of the following: a message type; an identity identifier of a first communication device; an identity identifier of a second communication device; a list of open data to be modified; or a list of open data to be released.

[0578] The list of open data to be modified shall include at least one of the following: information on third-party applications or services of the open data to be modified; the identity of the core network functional entity of the open data to be modified; the relevant open data to be modified; the object associated with the open data to be modified; the open time period to be modified; the reporting frequency of the open data to be modified; the reporting time limit information of the open data to be modified; and the reporting triggering event for the modification.

[0579] The list of open data to be released shall include at least one of the following: information of third-party applications or services of the open data to be released; identity identifier of the core network functional entity of the open data to be released; the open data to be released; and the object associated with the open data to be released.

[0580] In one embodiment, the first data open modification response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data modification request information in response.

[0581] The response list of open data modification request information shall include at least one of the following: the response status of the open data modification request; and the relevant open data to be modified.

[0582] In one embodiment, the communication device applied to the first communication device further includes:

[0583] The receiving module is also configured to receive a first data release request message sent by the second communication device;

[0584] The sending module is also configured to return a first data release response message to the second communication device.

[0585] In one embodiment, the first data release request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0586] The list of open data to be released shall include at least one of the following: information about third-party applications or services of the open data to be released; the identity identifier of the core network functional entity of the open data to be released; the relevant open data to be released; and the object associated with the open data to be released.

[0587] In one embodiment, the first data release response message includes at least one of the following: message type; identification of the first communication device; identification of the second communication device; and a list of open data release request information in response.

[0588] The response list of open data release request information shall include at least one of the following: the response status of the open data release request.

[0589] In one embodiment, the communication device applied to the first communication device further includes:

[0590] The sending module is also configured to send a first data release notification message to the second communication device;

[0591] The receiving module is also configured to receive a first data release confirmation message returned by the second communication device.

[0592] In one embodiment, the first data release notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0593] The list of open data released in the notification shall include at least one of the following: information about third-party applications or services of the open data released in the notification; the identity identifier of the core network functional entity of the open data released in the notification; the relevant open data released in the notification; the object associated with the open data released in the notification; and the reason for the release.

[0594] In one embodiment, the first data release confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a confirmed list of open data release request information.

[0595] The confirmed list of open data release request information includes at least one of the following: the response status of the data release request.

[0596] In one embodiment, the communication device applied to the first communication device further includes:

[0597] The sending module is also configured to send a first data open modification notification message to the second communication device;

[0598] The receiving module is also configured to receive the first data open modification confirmation message returned by the second communication device.

[0599] In one embodiment, the first data open modification notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be modified.

[0600] The list of open data to be modified in the notification shall include at least one of the following: information on third-party applications or services of the open data to be modified in the notification; the identity identifier of the core network functional entity of the open data to be modified in the notification; the relevant open data to be modified in the notification; the object associated with the open data to be modified in the notification; and the reason for the modification.

[0601] In one embodiment, the first data open modification confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of confirmed open data modification request information.

[0602] The confirmed list of open data modification request information shall include at least one of the following: the response status of the open data modification request; information about the third-party application or service for the requested open data modification; the identity of the core network functional entity for the requested open data modification; the relevant open data to be modified; the object associated with the open data to be modified; the time period for the requested modification; the reporting frequency of the requested open data modification; the reporting time limit information for the requested open data modification; and the reporting trigger event for the requested modification.

[0603] In one embodiment, the communication device applied to the first communication device further includes:

[0604] The receiving module is also configured to receive the first data open reporting notification message sent by the second communication device.

[0605] In one embodiment, the first data open reporting notification message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of open data request information in response.

[0606] The response list of open data request information should include at least the relevant open data requested.

[0607] In one embodiment, the communication device applied to the first communication device further includes:

[0608] The transmitting module is also configured to send a GTP-U extension header for open data transmission to a third communication device;

[0609] The GTP-U extension header must include at least one of the following: PDU type; a list of open data request information in response;

[0610] The response list of open data request information shall include at least one of the following: information about the third-party application or service requesting modification of the open data; the identity identifier of the core network functional entity requesting the open data; a predefined data open event identifier; relevant parameters of the data open event; and the identity identifier of the object associated with the open data.

[0611] In one embodiment, the second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

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

[0613] In one embodiment, FIG12 is a structural block diagram of another communication device provided in this application embodiment. This embodiment is applied to a second communication device. As shown in FIG12, the communication device in this embodiment includes: a transmitting module 610 and a receiving module 620.

[0614] The sending module 610 is configured to send a first data access request message to the first communication device;

[0615] The receiving module 620 is configured to receive a first data open response message carrying open data returned by the first communication device.

[0616] In one embodiment, the open data includes at least one of the following: cell configuration information; cell measurement information; cell resource load information; cell beam information; cell energy consumption information; terminal mobility parameters; and terminal resource load information.

[0617] In one embodiment, the communication device applied to the second communication device further includes:

[0618] The receiving module is further configured to receive a first data open capability sent by the first communication device; wherein, the first data open capability is data open capability information supported by the first communication device;

[0619] The sending module is also configured to return a first response message to the first communication device.

[0620] In one embodiment, the first data openness capability includes at least one of the following: 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 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; and historical response time.

[0621] In one embodiment, the first response message includes: the support status of the first data open capability.

[0622] In one embodiment, the bearer message for the first data open capability is a connection establishment request message, and correspondingly, the first response message is a connection establishment response message.

[0623] In one embodiment, the carrier message for the first data open capability is a configuration update request message, and the corresponding first response message is a configuration update confirmation message.

[0624] In one embodiment, the first data open request message includes at least one of the following: message type; identity identifier of the first communication device; and a list of requested open data.

[0625] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0626] In one embodiment, the first data open response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data in response.

[0627] The open data list in the response shall include at least one of the following: the response status of the data openness request; or the relevant data requested to be open.

[0628] In one embodiment, the communication device applied to the second communication device further includes:

[0629] The sending module is also configured to send a first data open modification request message to the first communication device;

[0630] The receiving module is also configured to receive a first data open modification response message returned by the first communication device.

[0631] In one embodiment, the first data open modification request message includes at least one of the following: a message type; an identity identifier of a first communication device; an identity identifier of a second communication device; a list of open data to be modified; or a list of open data to be released.

[0632] The list of open data to be modified shall include at least one of the following: information of the third-party application or service requesting modification of the open data; the identity of the core network functional entity requesting modification of the open data; the open data to be modified; the object associated with the open data to be modified; the open time period for the request to be modified; the reporting frequency of the open data to be modified; the reporting time limit information for the open data to be modified; and the reporting triggering event for the request to be modified.

[0633] The list of open data to be released shall include at least one of the following: information of third-party applications or services for which open data is to be released; the identity of the core network functional entity for which open data is to be released; the open data to be released; and the object associated with the open data to be released.

[0634] In one embodiment, the first data open modification response message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data modification request information in response.

[0635] The response list of open data modification request information shall include at least one of the following: the response status of the open data modification request; and the relevant open data to be modified.

[0636] In one embodiment, the communication device applied to the second communication device further includes:

[0637] The sending module is also configured to send a first data release request message to the first communication device;

[0638] The receiving module is also configured to receive a first data release response message returned by the first communication device.

[0639] In one embodiment, the first data release request message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0640] The list of open data to be released shall include at least one of the following: information about third-party applications or services of the open data to be released; the identity identifier of the core network functional entity of the open data to be released; the relevant open data to be released; and the object associated with the open data to be released.

[0641] In one embodiment, the first data release response message includes at least one of the following: message type; identification of the first communication device; identification of the second communication device; and a list of open data release request information in response.

[0642] The response list of open data release request information shall include at least one of the following: the response status of the data release request.

[0643] In one embodiment, the communication device applied to the second communication device further includes:

[0644] The receiving module is also configured to receive a first data release notification message sent by the first communication device;

[0645] The sending module is also configured to return a first data release confirmation message to the first communication device.

[0646] In one embodiment, the first data release notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be released.

[0647] The list of open data released in the notification shall include at least one of the following: information about third-party applications or services of the open data released in the notification; the identity identifier of the core network functional entity of the open data released in the notification; the relevant open data released in the notification; the object associated with the open data released in the notification; and the reason for the release.

[0648] In one embodiment, the first data release confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a confirmed list of open data release request information.

[0649] The confirmed list of open data release request information includes at least one of the following: the response status of the data release request.

[0650] In one embodiment, the communication device applied to the second communication device further includes:

[0651] The receiving module is also configured to receive a first data open modification notification message sent by the first communication device;

[0652] The sending module is also configured to return a first data open modification confirmation message to the first communication device.

[0653] In one embodiment, the first data open modification notification message includes at least one of the following: message type; identity identifier of the first communication device; identity identifier of the second communication device; and a list of open data to be modified.

[0654] The list of open data to be modified in the notification shall include at least one of the following: information on third-party applications or services of the open data to be modified in the notification; the identity identifier of the core network functional entity of the open data to be modified in the notification; the relevant open data to be modified in the notification; the object associated with the open data to be modified in the notification; and the reason for the modification.

[0655] In one embodiment, the first data open modification confirmation message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of confirmed open data modification request information.

[0656] The confirmed list of open data modification request information shall include at least one of the following: the response status of the open data modification request; information of the third-party application or service requesting the open data; the identity of the core network functional entity requesting the open data; the access network open data to be modified; the object associated with the data to be modified; the time period for the modification; the reporting frequency of the modified open data; the reporting time limit information of the modified open data; and the reporting trigger event for the modification.

[0657] In one embodiment, the communication device applied to the second communication device further includes:

[0658] The sending module is also configured to send a first data open reporting notification message to the first communication device.

[0659] In one embodiment, the first data open reporting notification message includes at least one of the following: message type; identity identifier of the second communication device; identity identifier of the first communication device; and a list of open data request information in response.

[0660] The response list of open data request information should include at least the relevant data requested to be made available.

[0661] In one embodiment, the second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

[0662] The communication device provided in this embodiment is configured to implement the communication method applied to the second communication device 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.

[0663] In one embodiment, FIG13 is a structural block diagram of another communication device provided in this application. This embodiment is applied to a first communication device. As shown in FIG13, the communication device in this embodiment includes: a transmitting module 710 and a receiving module 720.

[0664] The sending module 710 is configured to send a second data access request message to the second communication device.

[0665] The receiving module 720 is configured to receive a second data open response message sent by the second communication device.

[0666] In one embodiment, the communication device applied to the first communication device further includes:

[0667] The sending module is also configured to send a first request message to the second communication device; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device;

[0668] The receiving module is also configured to receive a second response message carrying a second data open capability sent by the second communication device.

[0669] In one embodiment, the first request message is a terminal capability acquisition message, and the corresponding second response message is terminal capability information.

[0670] In one embodiment, the second data access request message is carried in the RRC configuration message.

[0671] In one embodiment, the second data open response message is carried in the UE assistance message.

[0672] In one embodiment, the second data open request message includes at least one of the following: message type; identification of the second communication device; and a list of requested open data.

[0673] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0674] In one embodiment, the second data open response message includes at least one of the following: reporting the decision to open its own data to a third-party application or service; requesting relevant data to be opened; and a response list of open data requests.

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

[0676] In one embodiment, FIG14 is a structural block diagram of another communication device provided in this application embodiment. This embodiment is applied to a second communication device. As shown in FIG14, the communication device in this embodiment includes: a receiving module 810 and a transmitting module 820.

[0677] The receiving module 810 is configured to receive a second data open request message sent by the first communication device;

[0678] The sending module 820 is configured to send a second data open response message to the first communication device.

[0679] In one embodiment, the communication device applied to the second communication device further includes:

[0680] The receiving module is further configured to receive a first request message sent by the first communication device; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device;

[0681] The sending module is also configured to send a second response message carrying a second data open capability to the first communication device.

[0682] The first request message is a terminal capability acquisition message, and the corresponding second response message is terminal capability information.

[0683] In one embodiment, the second data access request message is carried in the RRC configuration message.

[0684] In one embodiment, the second data open response message is carried in the UE assistance message.

[0685] In one embodiment, the second data open request message includes at least one of the following: message type; identification of the second communication device; and a list of requested open data.

[0686] The requested list of open data shall include at least one of the following: information of the third-party application or service requesting open data; the identity of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

[0687] In one embodiment, the second data open response message includes at least one of the following: reporting the decision to open its own data to a third-party application or service; requesting relevant data to be opened; and a response list of open data requests.

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

[0689] In one embodiment, FIG15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in FIG15, the device provided in this application includes: a processor 910, a memory 920, and a communication module 930. The number of processors 910 in the device can be one or more; FIG15 shows one processor 910 as an example. The number of memories 920 in the device can be one or more; FIG15 shows one memory 920 as an example. The processor 910, memory 920, and communication module 930 of the device can be connected via a bus or other means; FIG15 shows a connection via a bus as an example. In this embodiment, the device can be a first communication device or a second communication device.

[0690] The memory 920, 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., receiving module 510 and transmitting module 520 applied to the communication device of the first communication device). The memory 920 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 920 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 920 may further include memory remotely located relative to the processor 910, 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.

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

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

[0693] This application 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 communication device. The method includes: receiving a first data open request message sent by a second communication device; and reporting a first data open response message carrying open data to the second communication device.

[0694] This application 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 communication device. The method includes: sending a second data open request message to a second communication device; and receiving a second data open response message sent by the second communication device.

[0695] This application 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 communication device. The method includes: sending a first data open request message to a first communication device; and receiving a first data open response message carrying open data returned by the first communication device.

[0696] This application 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 communication device. The method includes: receiving a second data open request message sent by a first communication device; and sending a second data open response message to the first communication device.

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

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

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

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

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

[0702] 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).

[0703] 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 communication device, wherein, The first communication device is an access network node; the method comprises: receiving a first data opening request message sent by a second communication device; reporting a first data opening response message carrying opening data to the second communication device.

2. The method of claim 1, wherein, The opening data comprises at least one of the following information: cell configuration information; cell measurement information; cell resource load information; cell beam information; cell energy consumption information; terminal mobility parameter; terminal resource load information.

3. The method of claim 1, further comprising: sending a first data opening capability to the second communication device; wherein the first data opening capability is data opening capability information supported by the first communication device; receiving a first response message returned by the second communication device.

4. The method of claim 3, wherein, The first data opening capability comprises at least one of the following: supported opening type; supported opening data type; analysis data reporting delay; analysis function accuracy; analysis processing capability; green computing support condition; service area information; resident terminal list; supported analysis cell type; supported analysis network slice; Machine learning support condition; Machine learning model accuracy monitoring capability; federal learning support condition; Metadata providing capability; historical analysis performance; historical response time.

5. The method of claim 3, wherein, The first response message comprises the support condition of the first data opening capability.

6. The method of claim 3, wherein, The first data opening capability bearing message is a connection establishment request message, and correspondingly, the first response message is a connection establishment response message.

7. The method of claim 3, wherein, The first data opening capability bearing message is a configuration update request message, and correspondingly, the first response message is a configuration update confirmation message.

8. The method of claim 1, wherein, The first data opening request message comprises at least one of the following: message type; identity of the first communication device; identity of the second communication device; requested opening data list; Wherein, the requested opening data list comprises at least one of the following: information of a third-party application or service requesting opening data; identity of a core network function entity requesting opening data; related opening data requesting opening; object associated with the requested opening data; requested opening time period; requested opening data reporting frequency; reporting time limit information of the requested opening data; reporting trigger event.

9. The method of claim 1, wherein, The first data opening response message comprises at least one of the following: message type; identity of the first communication device; identity of the second communication device; response opening data list; Wherein, the response opening data list comprises at least one of the following: response state of the opening data request; related opening data requesting opening.

10. The method of claim 1, further comprising: receiving a first data opening modification request message sent by the second communication device; returning a first data opening modification response message to the second communication device.

11. The method of claim 10, wherein, The first data opening modification request message comprises at least one of the following: message type; identity of the first communication device; identity of the second communication device; requested opening data list; requested opening data list to be released; The request modification open data list includes at least one of the following: information of a third-party application or service requesting modification of open data; an identity of a core network function entity requesting modification of open data; related open data requesting modification; an object associated with open data requesting modification; an open time period requesting modification; a reporting frequency of open data requesting modification; reporting time limit information of open data requesting modification; and a reporting trigger event requesting modification. The request release open data list includes at least one of the following: information of a third-party application or service requesting release of open data; an identity of a core network function entity requesting release of open data; and open data requesting release.

12. The method of claim 10, wherein, The first data open modification response message includes at least one of the following: a message type; an identity of the first communication device; an identity of the second communication device; and a response open data modification request information list. The response open data modification request information list includes at least one of the following: a response state of an open data modification request; and related open data requesting modification.

13. The method of claim 1, further comprising: receiving a first data open release request message sent by the second communication device; returning a first data open release response message to the second communication device.

14. The method of claim 13, wherein, The first data open release request message includes at least one of the following: a message type; an identity of the first communication device; an identity of the second communication device; and a request release open data list. The request release open data list includes at least one of the following: information of a third-party application or service requesting release of open data; an identity of a core network function entity requesting release of open data; and related open data requesting release.

15. The method of claim 13, wherein, The first data open release response message includes at least one of the following: a message type; an identity of the first communication device; an identity of the second communication device; and a response open data release request information list. The response open data release request information list includes at least one of the following: a response state of an open data release request.

16. The method of claim 1, further comprising: sending a first data open release notification message to the second communication device; receiving a first data open release confirmation message returned by the second communication device.

17. The method of claim 16, wherein, The first data open release notification message includes at least one of the following: a message type; an identity of the first communication device; an identity of the second communication device; and a notification release open data list. The notification release open data list includes at least one of the following: information of a third-party application or service notifying release of open data; an identity of a core network function entity notifying release of open data; related open data notifying release; an object associated with open data notifying release; and a release reason.

18. The method of claim 16, wherein, The first data open release confirmation message comprises at least one of the following: a message type; an identity of the second communication device; an identity of the first communication device; a list of confirmed open data release request information. The list of confirmed open data release request information comprises at least one of the following: a response state of the data open release request.

19. The method of claim 1, further comprising: sending a first data open modification notification message to the second communication device; receiving a first data open modification confirmation message returned by the second communication device.

20. The method of claim 19, wherein, The first data open modification notification message comprises at least one of the following: a message type; an identity of the first communication device; an identity of the second communication device; a list of notified modified open data; The list of notified modified open data comprises at least one of the following: information of a third-party application or service of the notified modified open data; an identity of a core network function entity of the notified modified open data; notified related open data; an object associated with the notified modified open data; a modification reason.

21. The method of claim 19, wherein, The first data open modification confirmation message comprises at least one of the following: a message type; an identity of the second communication device; an identity of the first communication device; a list of confirmed open data modification request information. The list of confirmed open data modification request information comprises at least one of the following: a response state of the open data modification request; information of a third-party application or service of the requested modified open data; an identity of a core network function entity of the requested modified open data; requested related open data; an object associated with the requested modified open data; a requested open time period; a reporting frequency of the requested modified open data; reporting time limit information of the requested modified open data; a requested reporting trigger event.

22. The method of claim 1, further comprising: receiving a first data open reporting notification message sent by the second communication device.

23. The method of claim 22, wherein, The first data open reporting notification message comprises at least one of the following: a message type; an identity of the second communication device; an identity of the first communication device; a list of responded open data request information. The list of responded open data request information comprises requested related open data.

24. The method of claim 1, further comprising: sending, to a third communication device, a user plane GTP-U extension header of a general packet radio service tunneling protocol (GTP-U) for open data transmission; The GTP-U extension header comprises at least one of the following: a packet data unit (PDU) type; a list of responded open data request information. The list of responded open data request information comprises at least one of the following: information of a third-party application or service of the requested open data; an identity of a core network function entity of the requested open data; a predefined data open event identifier; related parameters of the data open event; an object identity associated with the open data.

25. The method of any one of claims 1-24, wherein, The second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

26. A communication method applied to a second communication device, comprising: Send a first data access request message to the first communication device; Receive a first data open response message carrying open data returned by the first communication device.

27. The method according to claim 26, further comprising: Receive the first data open capability sent by the first communication device; wherein, the first data open capability is the data open capability information supported by the first communication device; Return a first response message to the first communication device.

28. The method according to claim 26, further comprising: Send a first data open modification request message to the first communication device; Receive the first data open modification response message returned by the first communication device.

29. The method according to claim 26, further comprising: Send a first data release request message to the first communication device; Receive the first data release response message returned by the first communication device.

30. The method according to claim 26, further comprising: Receive the first data release notification message sent by the first communication device; Return a first data release confirmation message to the first communication device.

31. The method according to claim 26, further comprising: Receive the first data open modification notification message sent by the first communication device; The first data access modification confirmation message is returned to the first communication device.

32. The method according to claim 26, further comprising: Send a first data open reporting notification message to the first communication device.

33. The method of any one of claims 26-32, wherein, The second communication device includes one of the following: a core network functional node; an access network node; or a user equipment.

34. A communication method applied to a first communication device, comprising: Send a second data access request message to the second communication device; Receive the second data open response message sent by the second communication device.

35. The method according to claim 34, further comprising: A first request message is sent to the second communication device; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device; Receive a second response message sent by the second communication device, which carries the second data open capability.

36. The method of claim 35, wherein, The first request message is a terminal capability acquisition message, and the corresponding second response message is terminal capability information.

37. The method according to claim 34, wherein the second data open request message is carried in a Radio Resource Control (RRC) configuration message.

38. The method of claim 34, wherein, The second data access response message is carried in the user equipment (UE) auxiliary message.

39. The method of claim 34, wherein, The second data open request message includes at least one of the following: message type; identity identifier of the second communication device; and a list of requested open data. The requested list of open data includes at least one of the following: information about the third-party application or service requesting open data; the identity identifier of the core network functional entity requesting open data; the relevant open data requested; the object associated with the requested open data; the requested open time period; the reporting frequency of the requested open data; the reporting time limit information of the requested open data; and the reporting trigger event.

40. The method of claim 34, wherein, The second data open response message includes at least one of the following: reporting the decision to open its own data to a third-party application or service; requesting relevant data to be opened; or responding with a list of open data requests.

41. A communication method applied to a second communication device, comprising: Receive the second data open request message sent by the first communication device; Send a second data open response message to the first communication device.

42. The method according to claim 41, further comprising: The first request message sent by the first communication device is received; wherein the first request message is used to request a second data open capability, and the second data open capability is data open capability information supported by the second communication device. Send a second response message carrying the second data open capability to the first communication device.

43. 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-25, 26-33, 34-40, or 41-42.

44. A storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of claims 1-25, 26-33, 34-40, or 41-42.

Images