Communication method and apparatus

By introducing data collection identification and user plane transmission mechanisms into the core network elements, the problems of low efficiency and high signaling overhead in OTT servers obtaining AI data from terminal devices from core network elements are solved, and efficient and accurate data collection and transmission are achieved.

WO2025227828A1PCT designated stage Publication Date: 2025-11-06HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/070862
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-29
Filing Date
2025-01-06
Publication Date
2025-11-06

AI Technical Summary

Technical Problem

The existing 3GPP standards do not specify how OTT servers should obtain AI data from terminal devices from core network elements, resulting in low data collection efficiency and high signaling overhead.

Method used

By introducing new data collection identifiers, core network elements can subscribe to event use cases of terminal devices, directly obtain data from terminal devices, and transmit it through the user plane, reducing interaction overhead and carrying vendor information to facilitate data source identification.

Benefits of technology

It improves data collection efficiency, reduces signaling overhead, ensures the standardization and accuracy of data transmission, and saves communication resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025070862_06112025_PF_FP_ABST
    Figure CN2025070862_06112025_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method and apparatus. The method comprises: a first network element receives first information; the first network element acquires first data on the basis of the first information; and the first network element sends the first data to a service device, wherein the first information is from the service device, the first information can be used for subscribing to the first data, the first data is event data corresponding to a first identifier, and the first identifier can be used for identifying a first event instance. In this way, in the method, by introducing a new data collection identifier (such as the first identifier), the first data can be collected by means of a core network element once the service device has subscribed to the first event instance corresponding to the first identifier, thereby allowing the service device to acquire the first data by means of the core network element.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and apparatus

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese Patent Application No. 202410533010.5, filed on April 29, 2024, and entitled “A communication method and apparatus”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a communication method and apparatus. BACKGROUND

[0004] Artificial intelligence (AI) is a technology that simulates human brain to perform complex calculations. With the improvement of data storage and computing power, AI has been increasingly applied. For example, the 3rd generation partnership project (3GPP) standard proposes to apply AI to new radio (NR) communication systems to improve network performance and user experience through intelligent collection and data analysis.

[0005] Currently, for AI data collection on the side of a terminal device (such as a UE), due to the limited capability of the terminal device, the 3GPP standard considers that AI data collection and AI model training are performed by an over the top server (OTT server) (or can be referred to as a terminal device side data collection server), and therefore AI data collection is configured by the OTT server. The OTT server generally refers to a cloud server deployed by a terminal device manufacturer or an operator, and therefore when the OTT server collects data, it needs to interact with the network. However, the current standard does not specify how the OTT server obtains data from a core network element. SUMMARY

[0006] The present application provides a communication method and apparatus to enable a service device to obtain data through a core network element.

[0007] In a first aspect, a communication method is provided. The method can be performed by a first network element. It should be understood that, in the present application, the "network element" can refer to the network element itself, a module (e.g., a processor, a chip, or a chip system) in the network element, or a logic node, a logic module, or software capable of implementing all or part of the functions of the network element. For example, the following describes the communication method performed by the first network element. The method can include the following steps: the first network element receives first information, then the first network element can obtain first data according to the first information, and then the first network element can send the first data to a service device, wherein the first information is from the service device, the first information can be used to subscribe to the first data, the first data is event data corresponding to a first identifier, and the first identifier can be used to identify a first event use case.

[0008] In the method, by introducing a new data collection identifier (e.g., the first identifier), after the service device subscribes to the first event use case (or can be understood as a data collection event use case) corresponding to the first identifier, the first network element can collect the first data, so that the service device can obtain the first data through the first network element.

[0009] In a possible implementation, the first network element obtains the first data according to the first information, including: the first network element can send second information to a second network element, wherein the second information can be used to subscribe to the first data, and then the first network element receives the first data from the second network element.

[0010] In the above implementation, the first network element can further collect the first data through the second network element, so that the underlying data (e.g., terminal device side underlying data) can be collected.

[0011] In a possible implementation, the first network element obtains the first data according to the first information, including: if the first data exists in a local cache area, the first network element can obtain the first data from the local cache area.

[0012] In the above implementation, when the first network element has collected the first data, the first network element can directly feed back the first data to the service device without interacting with the second network element to obtain the first data, which can save signaling overhead (or communication overhead) and improve data feedback efficiency.

[0013] In a possible implementation, the first network element obtains the first data according to the first information, including: the first network element can send third information, and then the first network element can receive the first data, wherein the third information can be used to instruct a terminal device to collect data, the third information can be sent (or forwarded) to the terminal device by a third network element, or the third information can be sent to the terminal device by a user plane.

[0014] In the implementation manner, the first network element can collect the data through the user plane, so that some overheads caused by interaction can be saved. In addition, the data collection through the user plane can also introduce an XML content format, so that the recommended format of data transmission can be standardized.

[0015] In a possible implementation manner, the first network element acquires the first data according to the first information, including that the first network element can send first configuration information to the terminal device, and then the first network element can receive the first data of the terminal device, where the first configuration information can be used to configure parameters of the terminal device for data collection.

[0016] In the implementation manner, the first network element can also collect the related data by sending configuration information for indicating data collection to the terminal device.

[0017] In a possible implementation manner, the first data can include vendor information, where the vendor information can be used to indicate a vendor to which the first data belongs.

[0018] In the implementation manner, by directly carrying the vendor information in the first data, the core network element (such as the first network element) can timely and accurately know that the first data is the data of which vendor, so that the core network element can timely and accurately provide the first data to the corresponding service device. In addition, by directly carrying the vendor information in the first data, the vendor information does not need to be sent separately, which helps to save communication overheads and resource overheads caused by separately sending the vendor information.

[0019] In a possible implementation manner, the method further includes that the first network element receives vendor information, where the vendor information can be used to indicate a vendor to which the first data belongs.

[0020] In the implementation manner, the vendor information can also be sent to the first network element separately, so that the bit space of the first data is not occupied, and the first network element can directly and intuitively know the vendor information to know that the first data is the data of which vendor, so that the core network element can timely and accurately provide the first data to the corresponding service device.

[0021] In a possible implementation manner, the first event use case can include at least one of the following: data size, area of interest, layer 1-reference signal received power, beam width, or location.

[0022] In the above implementation, by introducing a new data collection event subscription (such as an analytics event subscription or an event subscription, including one or more of data size, area of interest, layer 1-reference signal received power, beam width, or location), the service device can be facilitated to collect relevant data in a timely and effective manner through event subscription.

[0023] In a possible implementation, the first event use case can be one of the following use cases: a positioning use case, a channel state information (CSI) feedback use case, or a beam management use case.

[0024] In a possible implementation, the first information includes at least one of the following: the first identifier, the second identifier, a data size of the first data, a data type of the first data, a collection time length of the first data, or a collection time period of the first data; the second identifier can be used to identify a vendor to which the first data belongs, or the second identifier can also be used to identify a vendor to which the service device belongs.

[0025] In the above implementation, by carrying the first identifier in the first information, the first network element can be facilitated to explicitly know which event use case (or application instance) data. By carrying one or more of the data size, the data type, or the collection time period in the first information, the first network element can be facilitated to explicitly know what kind of data (such as the data size or the data type or the collection time period) needs to be collected. By carrying the second identifier in the first information, the first network element can be facilitated to explicitly know which vendor terminal device data needs to be collected.

[0026] In a second aspect, the present application provides a communication method, which can be executed by a second network element. It should be understood that, without special indication, the "network element" in the present application can refer to the network element itself, or a module (such as a processor, a chip, or a chip system, etc.) in the network element, or a logic node, a logic module, or software capable of realizing all or part of the network element functions. Exemplarily, the following takes the second network element executing the communication method as an example. The method can include the following steps: the second network element receives second information from the first network element, and then the second network element can send first data to the first network element, wherein the second information can be used to subscribe to the first data, the first data is event data corresponding to the first identifier, and the first identifier can be used to identify the first event use case.

[0027] The technical effects achieved by the second aspect can refer to the technical effects achieved by the corresponding implementation of the first aspect provided above, which will not be repeated here.

[0028] In a possible implementation manner of the second aspect, the method further includes: the second network element sending first configuration information to the terminal device, and then the second network element can receive the first data of the terminal device, wherein the first configuration information can be used to configure parameters of data collection of the terminal device.

[0029] In the implementation manner, the second network element can realize collection of relevant data by sending configuration information used to instruct data collection to the terminal device.

[0030] In a possible implementation manner of the second aspect, the first data can include vendor information, wherein the vendor information can be used to indicate a vendor to which the first data belongs.

[0031] The technical effects achieved by the implementation manner can refer to the technical effects achieved by the corresponding implementation manner of the first aspect, which will not be described herein.

[0032] In a possible implementation manner of the second aspect, the method further includes: the second network element receiving vendor information, and then the second network element can send the vendor information to the first network element, wherein the vendor information can be used to indicate a vendor to which the first data belongs.

[0033] The technical effects achieved by the implementation manner can refer to the technical effects achieved by the corresponding implementation manner of the first aspect, which will not be described herein.

[0034] In the third aspect, the application provides a communication method, which can be executed by a terminal device. It should be understood that, without special description, the "terminal device" in the application can refer to the terminal device itself, or a module (for example, a processor, a chip, or a chip system) in the terminal device, or a logic node, a logic module, or software capable of realizing all or part of the terminal device functions. Exemplarily, the following takes the terminal device executing the communication method as an example. The method can include the following steps: the terminal device can receive first configuration information from a first network element or a second network element, and then the terminal device can send first data to the first network element or the second network element, wherein the first configuration information can be used to configure parameters of data collection of the terminal device.

[0035] The technical effects achieved by the third aspect can refer to the technical effects achieved by the corresponding implementation manner of the first aspect or the second aspect, which will not be described herein.

[0036] In a possible implementation manner of the third aspect, the first configuration information can further include fourth information, wherein the fourth information can be used to instruct reporting of vendor information.

[0037] In the implementation manner, the fourth information is carried in the first configuration information, so that the terminal device can timely and effectively report the corresponding vendor information, so that the core network element can timely know which vendor (which can be understood as a terminal device vendor) the reported data belongs to, thereby facilitating the core network element to effectively distinguish the data of different vendors.

[0038] In a possible implementation manner provided in the third aspect, the first configuration information can be one of the following configuration information: data collection configuration information, measurement configuration information, or minimization of drive test configuration information.

[0039] In the implementation manner, the first configuration information is provided, so that the terminal device can timely and effectively perform data collection.

[0040] In a possible implementation manner provided in the third aspect, the first data can include vendor information, wherein the vendor information can be used to indicate a vendor to which the first data belongs.

[0041] The technical effects achieved by the implementation manners can refer to the technical effects achieved by the corresponding implementation manners provided in the first aspect or the second aspect, which will not be described herein.

[0042] In a possible implementation manner provided in the third aspect, the method further includes that the terminal device can send the vendor information to the first network element or the second network element, wherein the vendor information can be used to indicate a vendor to which the first data belongs.

[0043] The technical effects achieved by the implementation manners can refer to the technical effects achieved by the corresponding implementation manners provided in the first aspect or the second aspect, which will not be described herein.

[0044] In the fourth aspect, the application provides a communication method, which can be executed by a terminal device. It should be understood that, without special description, the "terminal device" in the application can refer to the terminal device itself, or a module (such as a processor, a chip, or a chip system) in the terminal device, or a logic node, a logic module, or software capable of realizing all or part of the terminal device functions. Exemplarily, the following takes the terminal device executing the communication method as an example. The method can include the following steps: the terminal device can receive third information, and then the terminal device can send first data, wherein the third information is used to instruct the terminal device to perform data collection, and the third information can be sent to the terminal device by a third network element, or the third information can also be sent to the terminal device by a user plane.

[0045] The technical effects achieved by the fourth aspect can refer to the technical effects achieved by the corresponding implementation manners provided in the first aspect, which will not be described herein.

[0046] In a possible implementation of the fourth aspect, the first data can include vendor information, where the vendor information can be used to indicate a vendor to which the first data belongs.

[0047] The technical effects achieved by the above implementation can refer to the technical effects achieved by the corresponding implementation of the first aspect or the second aspect or the third aspect, which will not be repeated here.

[0048] In a possible implementation of the fourth aspect, the method further includes that the terminal device can send vendor information, where the vendor information can be used to indicate a vendor to which the first data belongs. Accordingly, the first network element can receive the vendor information, for example, the first network element can receive the vendor information through the third network element or the user plane.

[0049] The technical effects achieved by the above implementation can refer to the technical effects achieved by the corresponding implementation of the first aspect, which will not be repeated here.

[0050] In the fifth aspect, the present application provides a communication method, which can be executed by a terminal device. It should be understood that, without special description, the "terminal device" in the present application can refer to the terminal device itself, or a module (such as a processor, a chip, or a chip system, etc.) in the terminal device, or a logic node, a logic module or software capable of realizing all or part of the terminal device functions. Exemplarily, the following takes the terminal device executing the communication method as an example. The method can include the following steps: the terminal device can receive second configuration information, and then the terminal device can send fifth information, where the second configuration information can be used to configure parameters for data collection of the terminal device, and the fifth information can be used to indicate that the data collection is stopped.

[0051] In the method, when the terminal device is insufficient in capability (or can be referred to as capability-limited), the terminal device can send the fifth information to inform the receiving side device (such as a network device) to stop the data collection, so that the receiving side device can timely stop the corresponding data collection operation, and the behavior of the terminal device side can be ensured to be correct, so as to avoid the terminal device side from producing an error behavior.

[0052] Accordingly, in a sixth aspect, the present disclosure provides a communication method, which can be performed by a network device. Alternatively, the method can also be implemented by a logic node, a logic module or software capable of implementing all or part of the functions of the network device. For example, the network device can include a core network element (such as the first network element) or a module (such as a processor, a processing unit, a chip system, a circuit or a chip, etc.) of the core network element, and / or an access network device (such as a base station) or a module (such as a processor, a processing unit, a chip system, a circuit or a chip, etc.) of the access network device. For example, the communication method performed by the network device is described below. The method can include the following steps: the network device can send second configuration information, and then the network device can receive fifth information, wherein the second configuration information can be used to configure parameters for data collection of the terminal device, and the fifth information can be used to indicate that the data collection is stopped.

[0053] The technical effects achieved by the sixth aspect can refer to the technical effects achieved by the fifth aspect, which will not be repeated here.

[0054] In a possible implementation of the fifth aspect or the sixth aspect, the terminal device can send second data, and correspondingly, the network device receives the second data, wherein the second data can be the data (or can be understood as part of the data) collected by the terminal device.

[0055] In the above implementation, the terminal device can feed back the part of the data collected to the network device, which can facilitate the network device to perform corresponding processing operation based on the part of the data collected.

[0056] In a possible implementation of the fifth aspect or the sixth aspect, the terminal device can also send sixth information, and correspondingly, the network device receives the sixth information, wherein the sixth information can be used to indicate that the second data is not collected completely.

[0057] In the above implementation, by feeding back the sixth information to the network device, the network device can timely and accurately know that the second data is not collected completely, so as to facilitate the network device to perform corresponding processing operation on the part of the data received.

[0058] In a possible implementation of the fifth aspect or the sixth aspect, the fifth information can include a reason for stopping the data collection, wherein the reason for stopping the data collection can include at least one of the following: the remaining storage space is less than (or lower than) a first threshold value, the remaining power is less than a second threshold value, the storage space is insufficient, the maximum data amount supported by the remaining power for transmission is less than the data amount of the first data, the maximum cache space supported by the remaining storage space for storage is less than the cache space occupied by the first data, or the power is insufficient.

[0059] In the implementation manner, the network device can learn the reason why the terminal device stops data collection in time, so that the network device can make corresponding data collection adjustment in time.

[0060] In a possible implementation manner of the fifth aspect or the sixth aspect, the first threshold and the second threshold can be configured by the network device, or the first threshold and the second threshold can also be predefined.

[0061] In the implementation manner, the first threshold and the second threshold can be determined in multiple ways, so that the determination of the first threshold and the second threshold is relatively flexible, and the requirements of different application scenarios can be met.

[0062] In a possible implementation manner of the fifth aspect or the sixth aspect, the second configuration information can include at least one of the following: a data collection size, a data collection time period, a data collection duration, or a data collection location range.

[0063] In the implementation manner, by carrying one or more of the data collection size (or referred to as data size), the data collection time period, the data collection duration, or the data collection location range in the second configuration information, the terminal device can learn specifically what kind of data needs to be collected (such as the data size or how long the data needs to be collected or which range of data needs to be collected).

[0064] In a possible implementation manner of the fifth aspect or the sixth aspect, the second configuration information can be one of the following configuration information: data collection configuration information, measurement configuration information, or minimization of drive test configuration information.

[0065] In the implementation manner, by providing the second configuration information, the terminal device can perform data collection in time and effectively.

[0066] In the seventh aspect, the present application provides a communication device, which has the functions of the first aspect to the sixth aspect, for example, the communication device includes a module or a unit or a means corresponding to the operations of the first aspect to the sixth aspect, and the functions or units or means can be realized by software or can be realized by hardware, or the corresponding software can be realized by hardware.

[0067] In a possible implementation, the communication apparatus includes a transceiver (or can be referred to as a communication module or a transceiver module or a communication module, for transmitting and receiving data) and a processing unit (or can be referred to as a processing module), wherein the transceiver can be used to transceive signals to realize communication between the communication apparatus and other apparatuses, for example, the transceiver is used to transmit data to the cloud; the processing unit can be used to perform some internal operations of the communication apparatus. The functions performed by the transceiver and the processing unit can correspond to the operations related to the first aspect to the sixth aspect.

[0068] In a possible implementation, the communication apparatus includes a processor, which can be coupled with a memory. The memory can store necessary computer programs or instructions for implementing the functions related to the first aspect to the sixth aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible implementation of any one of the first aspect to the sixth aspect.

[0069] In a possible implementation, the communication apparatus includes a processor and a memory, and the memory can store necessary computer programs or instructions for implementing the functions related to the first aspect to the second aspect. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication apparatus can implement the method in any possible implementation of any one of the first aspect to the sixth aspect.

[0070] In a possible implementation, the communication apparatus includes a processor and an interface circuit (or a communication interface), wherein the processor is configured to communicate with other apparatuses through the interface circuit and perform the method in any possible implementation of any one of the first aspect to the sixth aspect. The interface circuit is configured to realize communication between the communication apparatus and other apparatuses, for example, to receive signals from other communication apparatuses and transmit the signals to the processor or transmit signals from the processor of the communication apparatus to other communication apparatuses, for example, transmission or reception of data and / or signals. Exemplarily, the communication interface can be a transceiver, a circuit, a bus, a module or other types of communication interfaces.

[0071] It can be understood that, in the seventh aspect, the processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor, which implements by reading software codes stored in the memory. In addition, the processor can be one or more, and the memory can be one or more. The memory can be integrated with the processor, or the memory and the processor can be separately arranged. In the implementation process, the memory can be integrated on the same chip as the processor, or can be separately arranged on different chips. The type of the memory and the arrangement manner of the memory and the processor are not limited in the embodiments of the present application.

[0072] In the eighth aspect, the present application provides a possible communication system, which can include one or more of the terminal device or the access network device or the core network element (such as the first network element, the second network element, or the third network element, etc.) or the service device mentioned in the first aspect or the second aspect or the third aspect or the fourth aspect or the fifth aspect or the sixth aspect. The related functions of the terminal device or the access network device or the core network element or the service device can be implemented as described above in the first aspect or the second aspect or the third aspect or the fourth aspect or the fifth aspect or the sixth aspect, which will not be repeated here.

[0073] For example, the number of terminal devices or access network devices or core network elements or service devices can be one or more, which is not limited in the present application.

[0074] In the ninth aspect, the present application provides a computer program product, which includes a computer program or instructions, when the computer program or instructions are executed on a communication device (or a computer), so that the communication device (or the computer) executes the method in any possible implementation manner of any one of the first aspect to the sixth aspect.

[0075] In the tenth aspect, the present application provides a computer readable storage medium, which stores a computer program or instructions, when the computer program or instructions are executed by a communication device (or a computer), so that the communication device (or the computer) executes the method in any possible implementation manner of any one of the first aspect to the sixth aspect.

[0076] In the eleventh aspect, the present application provides a chip, which can include a processor and can also include a memory (or the chip is coupled with the memory). The chip executes program instructions in the memory, so that the chip executes the method in any possible implementation manner of any one of the first aspect to the sixth aspect. Wherein, "coupled" means that two components are directly or indirectly combined with each other, such as the electrical connection between the two components.

[0077] In a twelfth aspect, the present application also provides a chip system, which comprises a processor for supporting a computer device to implement the method in any possible implementation manner of any one of the first aspect to the sixth aspect. In a possible implementation manner, the chip system further comprises a memory for storing the necessary programs and data of the computer device. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0078] On the basis of the implementation manners of the aspects described above, the present application can be further combined to provide more implementation manners. BRIEF DESCRIPTION OF DRAWINGS

[0079] FIG. 1 exemplarily shows an application architecture schematic diagram of an AI model provided by an embodiment of the present application;

[0080] FIG. 2 exemplarily shows an AI model schematic diagram provided by an embodiment of the present application;

[0081] FIG. 3 exemplarily shows a possible application scenario schematic diagram provided by an embodiment of the present application;

[0082] FIG. 4 exemplarily shows a possible communication system architecture schematic diagram provided by an embodiment of the present application;

[0083] FIG. 5 exemplarily shows a flow schematic diagram of a communication method provided by an embodiment of the present application;

[0084] FIG. 6 exemplarily shows a flow schematic diagram of another communication method provided by an embodiment of the present application;

[0085] FIG. 7 exemplarily shows a flow schematic diagram of still another communication method provided by an embodiment of the present application;

[0086] FIG. 8 exemplarily shows a flow schematic diagram of still another communication method provided by an embodiment of the present application;

[0087] FIG. 9 exemplarily shows a flow schematic diagram of still another communication method provided by an embodiment of the present application;

[0088] FIG. 10 exemplarily shows a flow schematic diagram of still another communication method provided by an embodiment of the present application;

[0089] FIG. 11 exemplarily shows a flow schematic diagram of still another communication method provided by an embodiment of the present application;

[0090] FIG. 12 exemplarily shows a structure schematic diagram of a possible communication device provided by an embodiment of the present application;

[0091] FIG. 13 exemplarily shows a structure schematic diagram of another possible communication device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0092] Before introducing the technical solutions provided in the present application, first, some of the terms involved in the present application are explained and described in order to facilitate understanding by those skilled in the art.

[0093] AI model: is the specific implementation of AI function, which represents the mapping relationship between the input and output of the model. For example, the AI model can be a neural network, a linear regression model, a decision tree model, a support vector machine (SVM), a Bayesian network, a Q learning model or other machine learning models, etc. The AI function can include one or more of the following: data collection (collecting training data and / or inference data), data preprocessing, model training (model learning), model information publishing (configuring model information), model verification, model inference, or inference result publishing, etc.

[0094] Figure 1 illustrates an application architecture diagram of an AI model according to an embodiment of the present application. As shown in Figure 1, the data source is used to store training data and inference data. The model training node obtains the AI model by analyzing or training the training data provided by the data source, and deploys the AI model in the model inference node. Optionally, the model training node can also update the AI model that has been deployed in the model inference node. The model inference node can also feed back the relevant information of the deployed AI model to the model training node, so that the model training node optimizes or updates the deployed AI model, etc.

[0095] The AI model is learned by the model training node, which is equivalent to that the model training node learns the mapping relationship between the input and the output of the AI model by using the training data. The model inference node uses the AI model to perform inference based on the inference data provided by the data source to obtain an inference result. The method can also be described as follows: the model inference node inputs the inference data into the AI model, and obtains the output of the AI model, which is the inference result. The inference result can indicate the configuration parameter used (executed) by the execution object and / or the operation executed by the execution object. The inference result can be uniformly planned by an execution (actor) entity and sent to one or more execution objects (for example, network entities) for execution. Optionally, the execution entity or the execution object can feed back the collected parameters or measured quantities to the data source, and the process can be referred to as performance feedback. The feedback parameters can be used as training data or inference data. Optionally, the execution entity or the execution object can also determine feedback information related to the performance of the AI model according to the inference result output by the model inference node, and feed back the feedback information to the model inference node. The model inference node can feed back the performance information of the AI model to the model training node according to the feedback information, so as to optimize or update the deployed AI model, and the like. The process can be referred to as model performance feedback.

[0096] In addition, the current 3GPP introduces the discussion of AI application instances (AI use cases), wherein the AI application instances (which can be referred to as AI use cases) mainly include the following:

[0097] (1) Energy saving application instance:

[0098] The network device can predict the load of the network device according to the load, energy consumption, energy efficiency and the like of the network device and the neighboring cell, and the trajectory, measurement result and the like of the terminal device (or referred to as terminal). On the premise of not affecting the network coverage and user access, the network device can timely and appropriately take energy saving measures according to the prediction result. The energy saving measures can include at least one of the following: deactivating the cell, shutting down the carrier, shutting down the channel, shutting down the time slot, reducing the transmission power and the like.

[0099] (2) Load balancing application instance:

[0100] The network device can predict the load of the network device according to the load, energy consumption, energy efficiency and the like of the network device and the neighboring cell, and the trajectory, measurement result and the like of the terminal device. The network device can switch part of the terminal devices to the neighboring cell or switch part of the terminal devices served by the neighboring cell to the cell according to the prediction result, so that the loads of the network devices in the network are close, and the situation that part of the network devices are overloaded and affect the service of the terminal device, while the resources of another part of the network devices are idle, is avoided.

[0101] (3) Mobility optimization application example:

[0102] The network device can predict the future trajectory of the terminal device according to the historical trajectory information of the terminal device and the measurement information of the terminal device. The network device can judge in advance whether the terminal device needs to be switched and configure the information required for switching for the terminal device in advance according to the prediction result, and notify the target cell to prepare access resources for the terminal device, so that the delay of the terminal device in the switching process can be reduced, and the success rate of the terminal device switching can be improved.

[0103] (4) Channel state information feedback enhancement application example:

[0104] The channel state information is the channel attribute of the communication link, and the terminal device reports the channel state information to the network device, so that the network device selects a more suitable modulation and coding scheme (MCS) for the terminal device, and the MCS is used for transmitting data between the network device and the terminal device. The channel state information feedback application example can specifically include two application examples of channel state information compression and channel state information prediction.

[0105] The channel state information compression application instance is implemented based on a two-sided AI model (two-sided (AI / ML) model), as shown in the AI model schematic diagram in FIG. 2. The two-sided AI model (i.e., a channel state information compression model) includes an encoder and a quantizer on the terminal device side, and a decoder and a dequantizer on the network device side. The input of the encoder is actual channel state information obtained by the terminal device measuring a reference signal. The channel state information can be in the form of an original channel matrix, a precoded channel matrix, or a feature vector after channel decomposition. The output of the encoder is a floating-point vector carrying compressed channel state information. Further, the quantizer maps the floating-point vector carrying compressed channel state information to a quantized bit sequence (possible quantization methods include scalar quantization and vector quantization). The decoder and the dequantizer have opposite functions to the encoder and the quantizer. The channel state information output by the decoder can be considered as inference channel state information. For example, the encoder or the decoder can be implemented by an AI model such as a convolutional neural network (CNN) or a transformer.

[0106] The channel state information prediction application instance is implemented based on a one-sided AI model (one-sided (AI / ML) model) deployed on the terminal device side. The input of the one-sided AI model (i.e., a channel state information prediction model) is channel state information at multiple historical time points. The output of the one-sided AI model is channel state information at a target time point (i.e., inference channel state information). The one-sided AI model can be a multi-layer perceptron (MLP).

[0107] (5) Beam management (BM) application instance:

[0108] The BM application instance is implemented based on a one-sided AI model (i.e., a beam management model). The beam management model is mainly used to find the strongest beam pair. The beam management model can be deployed on the network side (e.g., in a network device) or on the terminal device.

[0109] When the beam management model is deployed at the terminal device side, it can be used to predict the optimal beam at the network device side, wherein the beam management model can be self-provided by the terminal device or issued by the network side to the terminal device. In the AI model usage process, the terminal device measures the downlink synchronization signal block (SSB) and channel state information reference signal (CSI-RS) to obtain the angle domain information of the channel, inputs the angle domain information of the channel into the beam management model, infers the top-k beams (such as the top-k beams in the reference signal received power (RSRP) ranking, k is a positive integer) in the plurality of beams, and feeds back the identification of the inferred top-k beams to the network device (for the second round of scanning and the determination of the optimal beam).

[0110] When the beam management model is deployed at the network side, the beam management model relies on the channel angle domain information measured by the terminal device for beam prediction, such as using the beam RSRP measured by the terminal device for prediction: the network device transmits part of the beams in the full codebook, the terminal device measures the RSRP of the sparse beams and feeds back the RSRP to the network device, the network device inputs the obtained RSRP into the beam management model, determines the top-k beams (such as the top-k beams in the RSRP ranking, wherein k is a positive integer), and performs the second round of scanning on the top-k beams, and the terminal device measures and reports the optimal beam in the second round.

[0111] (6) Positioning accuracy enhancements application example:

[0112] The positioning accuracy enhancements application example is implemented based on a single-sided AI model (i.e., a positioning accuracy enhancements model), and based on the ability of AI to identify line of sight (LOS) / non light of sight (NLOS), thereby improving the positioning accuracy under a small number of transmission reception point (TRP) antennas. For example, in a heavy NLOS scenario, there can not be a sufficient number of LOS paths, and the positioning of the terminal device based on the positioning accuracy enhancements model can improve the positioning accuracy in the indoor scenario.

[0113] It should be noted that in the embodiments of the present application, "sending information" can be understood as one device sending information to another device, or can also be understood as one logical module in a device sending information to another logical module. For example, "the service device sending information" can be understood as the service device sending information to another device (such as the first network element), or can be understood as the logical module 1 in the service device sending information to the logical module 2 in the first network element.

[0114] In the embodiments of the present application, "receiving information" can be understood as one device receiving information from another device, or can also be understood as one logical module in a device receiving information from another logical module. For example, "the first network element receiving information" can be understood as the first network element receiving information from another device (such as the service device), or can be understood as the logical module 1 in the first network element receiving information from the logical module 2 in the service device.

[0115] In the embodiments of the present application, "sending information to the first network element" can be understood as that the destination of the information is the first network element. It can include directly or indirectly sending information to the first network element. "Receiving information from the service device" can be understood as that the source of the information is the service device, and can include directly or indirectly receiving information from the service device. The information can be processed as necessary between the source and the destination of the information sending, such as format change, etc., but the destination can understand the valid information from the source. Similar expressions in the embodiments of the present application can be understood similarly, which will not be described here.

[0116] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0117] FIG. 3 exemplarily shows a possible application scenario suitable for the embodiments of the present application. As shown in FIG. 3, the application scenario can include an OTT server, a core network (CN) device (or can be referred to as a core network element), an access network (AN) (for example, a radio access network (RAN)) device and a terminal device (for example, a user equipment (UE)).

[0118] The OTT server has an AI function, and is configured to obtain corresponding data (such as AI-related training data) from a network side (such as a core network device or an access network device).

[0119] The terminal device has an AI function, is configured to collect corresponding data (such as AI data or other data), and can feed back the collected data to the core network device or the access network device. It should be understood that the relevant description of the terminal device can be referred to the relevant description of the terminal device in FIG. 4, and will not be repeated here.

[0120] The access network device has an AI function, is configured to perform access management and handover management on the terminal device, and can communicate with the core network device. It should be understood that the relevant description of the access network device can be referred to the relevant description of the access network device in FIG. 4, and will not be repeated here. Optionally, in an open RAN (O-RAN or ORAN) system, the access network device can be a combination of an open distributed unit (O-DU) and an open radio unit (O-RU) (or can be referred to as an open radio frequency unit), or can also be a combination of an open centralized unit (O-CU), an O-DU and an O-RU, and the embodiments of the present application do not limit this. For example, when the access network device is a combination of an O-DU and an O-RU, the O-DU has a baseband processing function and a complete protocol layer function, and is mainly configured to be responsible for high-layer protocol functions such as data encryption and integrity protection, and has a physical layer high-layer processing function. The O-RU has a physical layer bottom-layer signal processing function, and is mainly configured to be responsible for transmitting and receiving radio frequency signals.

[0121] The core network device has an AI function, and is configured to manage the network. It should be understood that the relevant description of the core network device can be referred to the relevant description of the core network device in FIG. 4, and will not be repeated here.

[0122] It should be noted that FIG. 3 only schematically provides a possible application scenario, and the schematic application scenario is used to more clearly illustrate the technical solutions of the embodiments of the present application, and does not limit the application scenarios of the vehicle driving accompanying method provided by the present application. In addition, the forms and quantities of the devices in the application scenario shown in FIG. 3 are only used for examples, and do not constitute a limitation on the present application. Furthermore, the names of the devices in the application scenario shown in FIG. 3 are only examples, and the names of the devices in the specific implementation can also be other names, and the present application does not specifically limit this. In addition, those skilled in the art can know that with the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0123] Based on the application scenario shown in FIG. 3, the communication system architecture to which the communication method provided by the present application is applicable is introduced as follows. It should be noted that these introductions are for the convenience of those skilled in the art to understand and do not constitute a limitation on the scope of protection required by the present application.

[0124] FIG. 4 exemplarily shows a possible communication system architecture to which the embodiments of the present application are applicable. The communication system architecture shown in FIG. 4 is the fifth-generation (5G) communication system architecture specified by the 3GPP standard, which includes terminal devices, access network (AN) devices, core network devices and data networks (DN). Optionally, the terminal device can be connected to the access network device (such as (R)AN device) in a wireless manner, and the access network device can be connected to the core network in a wireless or wired manner. The core network device and the wireless access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the wireless access network device can be integrated on the same physical device, or a physical device can integrate part of the functions of the core network device and part of the functions of the wireless access network device. The terminal device and the terminal device, and the access network device and the access network device can be connected to each other in a wired or wireless manner. Exemplarily, the communication system architecture can also include other network devices (such as wireless relay devices or wireless backhaul devices, etc.).

[0125] The functions of some of the devices included in the communication system architecture are briefly introduced as follows.

[0126] Terminal device: a kind of entity with transceiver signal function on the user side, which can provide video, voice, data connectivity and other service functions for users. For example, the terminal device is the entrance for mobile users to interact with the network, which can provide basic computing power, storage capacity, display business windows to users, and receive user operation input. The next-generation terminal device (NextGen UE) can use new radio technology to establish a signal connection with the access network device, data connection, so as to transmit control signals and service data to the mobile network.

[0127] Optionally, the terminal device can also be referred to as a terminal, a user equipment (UE), an access terminal device, a vehicle-mounted terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal device, a mobile device, a UE terminal device, a terminal device, a wireless communication device, a UE agent, or a UE apparatus, etc. In the embodiments of the present application, the terminal device can be fixed in position or mobile, and the present application does not make any limitation in this regard. Illustratively, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted, or can also be deployed on the surface of water (such as a ship, etc.), or can also be deployed in the air (such as an airplane, a balloon, or a satellite, etc.).

[0128] Exemplarily, the terminal device can be a mobile phone, a Pad, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a Personal Digital Assistant (PDA) computer, a wireless modem, a handset, a laptop computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a head mounted display (HMD), a wireless terminal in industrial control, a vehicle-mounted terminal device, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a wearable terminal device, a vehicle, a drone, a helicopter, an airplane, a factory machine / device, a Machine Type Communication (MTC) terminal, a ship or a robot, etc. For example, the vehicle can include, but is not limited to, a smart car or an intelligent car, a digital car, an unmanned car or a driverless car or a pilotless car or an automobile, a self-driving car or an autonomous car, a pure EV or a Battery EV, a hybrid electric vehicle (HEV), a range extended EV (REEV), a plug-in HEV (PHEV), a new energy vehicle, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device.

[0129] Access network device: a device for accessing terminal devices to a wireless network. The access network device can also be referred to as an access network apparatus or a radio access network device or a (R)AN entity or a network device or an access node or a (R)AN node or a (R)AN device, etc. For example, the access network device can provide access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data according to the levels of users, the requirements of services, etc. The access network device can manage its own resources, rationally utilize, provide access services for terminal devices on demand, and be responsible for forwarding control signals and user data between terminal devices and core network devices.

[0130] Exemplarily, the access network device can include but is not limited to: a next generation NodeB (gNB) in a 5G communication system, a next generation NodeB in a 6th generation (6G) communication system, a base station in a future communication system, a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved Node B, or a home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wi-Fi) access point (AP), etc.

[0131] Optionally, in a network architecture, the access network device can include a CU or a DU. This architecture can split the protocol layers of the access network device, with some of the protocol layer functions being centrally controlled in the CU, and the rest of the protocol layer functions being distributed in the DU, with the CU centrally controlling the DU. For example, the packet data convergence protocol (PDCP) layer and above protocol layer functions can be provided in the CU, and the protocol layer functions below the PDCP, such as the radio link control (RLC) layer and the medium access control (MAC) layer, etc., can be provided in the DU. It should be noted that this protocol layer division is only an example, and other protocol layer divisions can also be used. The radio frequency device can be remote from the DU, integrated in the DU, or partially remote and partially integrated in the DU, and the embodiments of the present application do not make any limitation. In addition, in some embodiments, the control plane (CP) and the user plane (UP) of the CU can also be separated and implemented by different entities, respectively, as a control plane CU entity (CU-CP entity) and a user plane CU entity (CU-UP entity).

[0132] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be referred to as an O-CU, the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in the present application. Any one of the CU (or CU-CP, CU-UP), DU and RU in the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0133] In the embodiments of the present application, the access network device can adopt a CU-DU separation architecture, which can also be referred to as a distributed deployment architecture, or can also adopt a CU-DU-RU separation architecture. For example, the access network device can logically include a CU and one or more DUs, each DU can be connected with the CU through an F1 interface, and information interaction between different DUs can be completed based on forwarding of the CU. The CU and the DU can be physically arranged together or physically separated, which is not limited. The CU can support functions of radio resource control (RRC) layer protocol, PDCP layer protocol, and service data adaptation protocol (SDAP) layer protocol; the DU can support RLC layer protocol, MAC layer protocol, and part of physical (PHY) layer or all PHY layer functions. For specific descriptions of the above protocol layers, reference can be made to related technical specifications of 3GPP. For another example, the access network device can logically include a CU, a DU, and an RU. The CU and the DU can be physically arranged together or physically separated, which is not limited. The CU can support functions of RRC layer protocol, PDCP protocol, and SDAP protocol; the DU can support functions of RLC layer protocol and MAC layer protocol, and can also support part of PHY layer protocol; the RU can support part of PHY layer or all PHY layer functions. For example, the DU is mainly responsible for high layer protocol functions such as data encryption and integrity protection, and the RU is mainly responsible for transmission and reception of radio frequency signals. It can be understood that in the CU-DU-RU separation architecture, the interface between the DU and the RU can be referred to as front transmission, the interface between the CU and the DU can be referred to as middle transmission, and the interface between the CU and the core network device can be referred to as back transmission.

[0134] For example, the access network device is a base station, the base station can communicate with the terminal device, or can communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations in different access technologies.

[0135] In the embodiments of the present application, the access network device can be a macro base station, a micro base station or an indoor station, or a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form of the wireless access network device.

[0136] Data network: a data network providing service for a user, generally a client is located at a terminal device and a server is located at the data network. The data network can be a private network such as a local area network, can be an external network not controlled by an operator such as the Internet, or can be a dedicated network deployed by operators together such as a network providing IP multimedia core network subsystem (IMS) service.

[0137] The core network is responsible for maintaining subscription data of the mobile network, managing network elements of the mobile network, and providing session management, mobility management, policy management, security authentication, and the like for terminal devices. When a terminal device is attached, the core network provides network access authentication for the terminal device; when the terminal device has a service request, the core network allocates network resources for the terminal device; when the terminal device moves, the core network updates network resources for the terminal device; when the terminal device is idle, the core network provides a fast recovery mechanism for the terminal device; when the terminal device detaches, the core network releases network resources for the terminal device; when the terminal device has service data, the core network provides data routing functions for the terminal device, such as forwarding uplink data to a data network; or receiving downlink data of the terminal device from the data network and forwarding it to the access network device, so as to send it to the terminal device by the access network device. Optionally, in terms of functional logic, the network elements of the core network can be divided into two parts: user plane network elements and control plane network elements. Among them, the user plane network elements are responsible for the transmission of service data, for example, the user plane network elements can include but are not limited to user plane function (UPF) network elements. The control plane network elements are responsible for the management of the mobile network, for example, the control plane can include but is not limited to access and mobility management function (AMF) network elements, SMF network elements, unified data management (UDM) network elements (or unified data repository (UDR) network elements), PCF network elements, AF network elements, authentication server function (AUSF) network elements, network data analytics function (NWDAF) network elements, data collection coordination function (DCCF) network elements. Of course, the core network can also include other network elements (such as network exposure function (NEF) network elements, network function repository function (NRF) network elements, analytics data repository function (ADRF) network elements, data collection application function (DCAF) network elements, etc., which are not listed one by one here.

[0138] Optionally, the core network control plane adopts a service-oriented architecture, and the interaction between control plane network elements adopts a service invocation manner to replace the point-to-point communication manner in the traditional architecture. In the service-oriented architecture, a control plane network element opens services to other control plane network elements for invocation by other control plane network elements; in the point-to-point communication, the communication interface between control plane network elements stores a specific set of messages that can only be used by the control plane network elements at both ends of the interface when communicating.

[0139] The functions of some network elements included in the core network are briefly introduced as follows:

[0140] (1) SMF network element: mainly used for session management, IP address allocation and management of terminal devices, selection of manageable user equipment plane functions, policy control, or termination of charging function interfaces, and downlink data notification, etc., such as completing the establishment, release, update, etc. processes related to protocol data unit (PDU) sessions. In the 5G communication system, the session management network element can be an SMF network element, and in the future communication such as the 6th-generation (6G) communication system, the session management function network element can still be an SMF network element, or have other names, which are not limited in the present application. Nsmf is a service-based interface provided by the SMF network element, and the SMF network element can communicate with other network functions through Nsmf.

[0141] (2) AMF network element: mainly used for mobility management and access management, etc., such as receiving non-access layer (NAS) signaling (including mobility management (MM) signaling and session management (SM) signaling) of terminal devices and related signaling of access network devices (for example, N2 signaling of base station granularity interacting with the AMF network element), completing the registration process of users and the forwarding of SM signaling and mobility management. For example, it can be a mobility management entity (MME) in the 4th-generation (4G) communication system or an AMF network element in the 5G communication system. In the future communication system such as the 6G communication system, the access management network element can still be an AMF network element, or have other names, which are not limited in the present application. Namf is a service-based interface provided by the AMF network element, and the AMF network element can communicate with other network functions through Namf.

[0142] (3) UDM network element: used for processing user identification, subscription, access authentication, registration, or mobility management, etc. In the 5G communication system, the data management network element can be a UDM network element, and in the future communication system such as the 6G communication system, the data management network element can still be a UDM network element, or have other names, which are not limited in the present application. Nudm is a service-based interface provided by the UDM network element, and the UDM network element can communicate with other network functions through Nudm.

[0143] (4) PCF network element: used for guiding unified policy framework of network behavior, providing policy rule information (such as mobility related policy or PDU session related policy (such as quality of service (QoS) policy, charging policy, etc.) or slice selection policy) for control plane function network element (such as AMF, SMF, etc.). In the 5G communication system, the policy control network element can be a PCF network element, and in the future communication system such as the 6G communication system, the policy control network element can still be a PCF network element, or have other names, which are not limited in the present application. Npcf is a service-based interface provided by the PCF network element, and the PCF network element can communicate with other network functions through Npcf.

[0144] (5) AF network element: used for data routing of application influence, access network exposure function, or interaction with policy framework for policy control, etc. In the 5G communication system, the application network element can be an AF network element, and in the future communication system such as the 6G communication system, the application network element can still be an AF network element, or have other names, which are not limited in the present application. Naf is a service-based interface provided by the AF, and the AF network element can communicate with other network functions through Naf.

[0145] (6) UPF network element: used for packet routing and forwarding, or QoS processing of user plane data, etc. In the 5G communication system, the user plane network element can be a UPF network element, and in the future communication system such as the 6G communication system, the user plane network element can still be a UPF network element, or have other names, which are not limited in the present application.

[0146] (7) AUSF network element: mainly used for user authentication, etc. In the 5G communication system, the authentication service network element can be an AUSF network element, and in the future communication system such as the 6G communication system, the authentication service network element can still be an AUSF network element, or have other names, which are not limited in the present application. Nausf is a service-based interface provided by the AUSF network element, and the AUSF network element can communicate with other network functions through Nausf.

[0147] (8) NEF network element: used for securely opening services and capabilities provided by 3GPP network functions, etc. In the 5G communication system, the network opening network element can be the NEF network element, and in the future communication system such as the 6G communication system, the network opening function network element can still be the NEF network element, or have other names, which are not limited in the present application. Nnef is a service-based interface provided by the NEF network element, and the NEF network element can communicate with other network functions through Nnef.

[0148] (9) NRF network element: used for providing service registration, discovery and authorization, and maintaining available network function (NF) instance information, and can realize on-demand configuration of network functions and services and interconnection between NFs. In the 5G communication system, the network storage network element can be the NRF network element, and in the future communication system such as the 6G communication system, the network storage function network element can still be the NRF network element, or have other names, which are not limited in the present application. Nnrf is a service-based interface provided by the NRF network element, and the NRF network element can communicate with other network functions through Nnrf.

[0149] (10) UDR network element: used for UDM network element to store subscription data or read subscription data, and PCF network element to store policy data or read policy data.

[0150] (11) NWDAF network element: responsible for network data intelligent analysis function, and can interact with different entities for different purposes, such as collecting network data from AMF network element, SMF network element, PCF network element, UDM network element, AF network element, operation, administration and management (OAM) entity, etc. based on data subscription and event response mechanism; retrieving information related to subscribed users from the UDR network element; retrieving information related to network element entities from the NRF network element; providing analysis results to consumer network elements (such as OTT servers); providing statistical results to consumer network elements; relying on the DCCF network element to complete data collection and provide analysis results; relying on the analytics data repository function (ADRF) network element to complete historical data collection and provide historical analysis results.

[0151] (12) DCCF network element: can collect required data, such as network data, user data, analysis results, etc., from data sources according to the request of a consumer network element. The DCCF network element can avoid sending repeated data requests to data sources, thereby improving the efficiency and accuracy of data collection. In the data collection coordination process, the DCCF network element will maintain an active data collection request record list to track which data sources are currently collecting data from. When a new data collection request is received, if the data source of the new request matches the requested data source in the active list, the DCCF can directly feedback the collected data or simply modify the existing data subscription request, otherwise the DCCF network element needs to initiate a new data subscription request.

[0152] (13) ADRF network element: used for storing and retrieving collected data and analysis results.

[0153] (14) DCAF network element: can collect required data, such as network data, user data, analysis results, etc., from data sources according to the request of a consumer network element. It should be understood that the DCAF network element is not shown in FIG. 4.

[0154] It can be understood that the above-mentioned network elements or functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Alternatively, the above-mentioned network elements or functions can be implemented by one device, or implemented by multiple devices together, or be a functional module in a device, and the embodiments of the present application do not make specific limitations thereto.

[0155] As shown in FIG. 4, a terminal device can access a 5G communication system through an access network device (such as a (R)AN device), the terminal device can communicate with an AMF network element through a next generation (NG) 1 interface (referred to as N1), the access network device communicates with the AMF network element through an N2 interface (referred to as N2), the access network device communicates with a UPF network element through an N3 interface (referred to as N3), an SMF network element communicates with the UPF network element through an N4 interface (referred to as N4), and the UPF network element accesses a data network through an N6 interface (referred to as N6).

[0156] It should be understood that the above network elements or functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Alternatively, the above network elements or functions can be implemented by one device, or by multiple devices together, or by a functional module within one device, and the embodiments of the present application do not make specific limitations thereon. In addition, for the convenience of description, in the embodiments of the present application, "xxx network element" can also be referred to as "xxx" for short, for example, AMF network element can be referred to as AMF for short, and SMF network element can be referred to as SMF for short.

[0157] It can be understood that the access network device, the terminal device, the network element in the core network, etc. can be referred to as a communication apparatus. For example, the access network device can be understood as a communication apparatus with a base station function. The terminal device can be understood as a communication apparatus with a terminal function. The network element in the core network can be understood as an apparatus with a core network element function. For example, the AMF can be understood as a communication apparatus with an AMF function.

[0158] It should be noted that the communication system architecture shown in FIG. 4 is for more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be understood by those skilled in the art that, as the communication system architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0159] The specific implementation of the communication method in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0160] FIG. 5 shows a flow diagram of a communication method according to an embodiment of the present application. The method is applicable to the application scenario shown in FIG. 3 or the communication system architecture shown in FIG. 4. It can be understood that the communication method shown in FIG. 5 is exemplarily shown by taking the first network element and the service device as the execution subject of the interaction, but the present application does not limit the execution subject of the interaction. It should be understood that, without special indication, the "network element" in the present application can refer to the network element itself, or a module (such as a processor, a chip, or a chip system, etc.) in the network element, or a logic module or software capable of realizing all or part of the function of the network element. The "device" (such as the service device or the terminal device) in the present application can refer to the device itself, or a module (such as a processor, a chip, or a chip system, etc.) in the device, or a logic module or software capable of realizing all or part of the function of the device. For example, the method performed by the first network element in the present application can also be performed by a module applied to the first network element, and can also be realized by a logic node, a logic module or software capable of realizing all or part of the function of the first network element; the method performed by the service device in the present application can also be performed by a module applied to the service device, and can also be realized by a logic node, a logic module or software capable of realizing all or part of the function of the service device; the method performed by the terminal device in the present application can also be performed by a module applied to the terminal device, and can also be realized by a logic node, a logic module or software capable of realizing all or part of the function of the terminal device.

[0161] As shown in FIG. 5, the method comprises:

[0162] Step 501: The service device sends first information. Correspondingly, the first network element receives the first information.

[0163] Optionally, the service device can refer to a network function or a server outside the 3GPP. For example, the service device can be an OTT server. It can be understood that the service device can be deployed in the operator network, or the service device can also be deployed outside the operator network.

[0164] The first information is used for subscribing to first data, which can be event data corresponding to a first identifier. The first identifier can be used to identify a first event use case. It can be understood that the first data can be data of one or some specific terminal devices, or can not be data of specific terminal devices, depending on the needs of the service device. For example, the first data can include at least one of the following: measurement results, historical data, model training data (or can be referred to as request data), or analysis data (or collected raw data), etc. It can be understood that the measurement results or model training data can be understood as underlying data on the terminal device side. For example, the measurement results, historical data, model training data or analysis data (or collected raw data) can include at least one of the following: layer 1 reference signal receiving power (L1-RSRP) of a reference signal, phase information, time information, power information, location information, or paired information of time and power, etc. It should be understood that the model training data can be replaced by data requested by the first network element, and the model training data can be used for model training, or can be used for other purposes (such as data analysis).

[0165] In the embodiments of the present application, the first event use case can be a specified bit use case, a CSI feedback use case, or a beam management use case, etc. For example, the first event use case can include at least one of the following (or it can be understood that the event filter information included in the first event use case includes at least one of the following): data size (such as the size of the first data), area of interest, L1-RSRP, beam width, or location, etc. It should be understood that the event filter information can be used to distinguish the data to be collected.

[0166] Exemplarily, the first information can comprise at least one of the following: the first identifier, the second identifier, a data size (or can be referred to as a data size of the first data), a data type (or can be referred to as a data type of the first data, such as network configuration data or terminal device collected data or application layer data), a data collection time length (or can be referred to as a collection time length of the first data, such as how long the data needs to be collected, for example, starting from a certain time, how long to collect and end collecting), or a data collection time period (or can be referred to as a collection time period of the first data, including a collection start time and a collection end time), etc. Wherein, the second identifier is used to identify a vendor (such as which vendor terminal device the first data belongs to) to which the first data belongs, or the second identifier is used to identify a vendor to which the service device belongs (such as different vendors of service devices collect data of terminal devices of different vendors).

[0167] For example, when the first data is data of a specific terminal device, the second identifier needs to be included in the first information. In this way, the second identifier can be used to identify which terminal device data the service device needs to collect (such as terminal device data), or the second identifier can also be used to identify the type of the service device (such as a server).

[0168] For example, the first identifier can refer to an analytics ID (or can be referred to as a data collection analytics ID) or an event ID (or can be referred to as a data collection event ID). For example, when the first identifier refers to the analytics ID, the first network element can refer to the NWDAF network element. For example, the first information sent by the service device to the NWDAF network element can be Nnwdaf_AnalyticsSubscription_Subscribe subscription information. For another example, when the first identifier refers to the event ID, the first network element can refer to the DCCF network element or the DCAF network element. For example, the first information sent by the service device to the DCCF network element or the DCAF network element can be Naf_EventExposure_Subscribe subscription information.

[0169] In one example, when the first identifier refers to an analytics identifier, the analytics identifier is used to identify an analytics event (such as an AI analytics event), which can be used to design different analytics identifiers for different use cases, such as AI data collection for positioning, AI data collection for CSI feedback, and AI data collection for beam, etc. Among them, AI data collection for positioning is used to identify an AI data collection positioning event, AI data collection for CSI feedback is used to identify an AI data collection CSI feedback event, and AI data collection for beam is used to identify an AI data collection beam management event.

[0170] In another example, when the first identifier refers to an event identifier, the event identifier is used to identify a subscription event (or can be referred to as an event) (such as an AI subscription event), which can be used to design different event identifiers for different use cases, such as AI data collection for positioning, AI data collection for CSI feedback, and AI data collection for beam, etc. Among them, AI data collection for positioning is used to identify an AI data collection positioning event, AI data collection for CSI feedback is used to identify an AI data collection CSI feedback event, and AI data collection for beam is used to identify an AI data collection beam management event.

[0171] For example, the event filter information corresponding to the positioning event can include data size, area of interest, location, etc. The event filter information corresponding to the CSI feedback event can include data size, area of interest, L1-RSRP, etc. The event filter information corresponding to the beam management event can include data size, area of interest, beam width, etc.

[0172] Step 502: The first network element acquires first data according to the first information.

[0173] The implementation process of the first network element acquiring the first data according to the first information is described below through the following possible implementation manners.

[0174] In an implementation, when the first network element is a NWDAF network element or a DCAF network element, the first network element can send second information to the second network element. The second information is used to subscribe to the first data. After receiving the second information, the second network element can send the first data to the first network element.

[0175] For example, in this implementation, when the first network element is a NWDAF network element, the second network element can be a DCCF network element, an ADRF network element, an OAM entity, an AMF network element, and the like. When the first network element is a DCAF, the second network element can be a NWDAF network element, an ADRF network element, a DCCF network element, an OAM entity, an AMF network element, and the like.

[0176] The following describes the implementation process of the second network element sending the first data to the first network element through the following possible examples.

[0177] Example 1: Taking the first network element as a NWDAF network element, the second network element as a DCCF network element, an ADRF network element, an OAM entity, and an AMF network element, and the second information as subscription information (or subscription message) as an example. In one possible implementation, the NWDAF network element can send subscription information to one or more of the OAM entity, the ADRF network element, or the AMF network element to obtain related data. For example, taking the NWDAF network element sending subscription information to the OAM entity, the ADRF network element, and the AMF network element as an example. The NWDAF network element can send subscription information 1, subscription information 2, and subscription information 3 to the OAM entity, the ADRF network element, and the AMF network element, respectively. The subscription information 1 is used to subscribe to the measurement results (or measurement reports) reported by the terminal device to the OAM entity through the minimization of drive test (MDT) procedure, the subscription information 2 is used to subscribe to the historical data (such as trajectory data (for example, geographical location, speed data, moving direction, height data, and the like) of the terminal device or measurement results) of the ADRF network element, and the subscription information 3 is used to subscribe to the model training data (such as measurement results) of the AMF network element. This implementation can realize that the NWDAF network element directly subscribes to related data from multiple second network elements, so that the NWDAF network element can directly and effectively obtain related data.

[0178] For the OAM entity, after receiving the subscription information 1, the OAM entity can send the measurement result to the NWDAF network element. Optionally, since the measurement result is reported to the OAM entity by the terminal device through the MDT procedure, the terminal device can carry the vendor information (such as the vendor ID) in the measurement result, or the terminal device can also send the vendor information to the OAM entity separately, or the first data and the vendor information can be carried in the same information (or the same message) and sent to the OAM entity. The vendor information is used to indicate the manufacturer (or can be understood as the manufacturer of the terminal device) to which the first data belongs. In this way, the terminal device carries the corresponding vendor information in the measurement result, so that the core network element (such as the NWDAF network element) can timely and accurately know that the measurement result is the data of which manufacturer (or can be understood as the data of which manufacturer terminal device), so that the core network element can timely and accurately provide the first data to the corresponding service device.

[0179] For example, taking the measurement result carrying the vendor information as an example. In one example, the terminal device can directly carry the vendor information, so that the vendor information is explicit. In another example, the terminal device can include the vendor information in a container, and then carry the container in the measurement result, so that the vendor information is implicit. It can be understood that the vendor information (such as the vendor ID) can be assigned to the terminal device manufacturer by the operator offline.

[0180] Optionally, before the terminal device reports the vendor information to the OAM entity through the MDT procedure, the network device (or can be referred to as the network side device, such as the core network element and / or the access network device) can send the corresponding configuration information (such as the first configuration information) to the terminal device. The first configuration information can be used to configure the parameters of the terminal device for data collection (such as CSI measurement). For example, the first configuration information can be data collection configuration information, measurement configuration information, or minimization of drive test configuration information, etc. Optionally, the first configuration information can include fourth information. The fourth information can be used to indicate the reported vendor information (which can be understood as a field for distinguishing the manufacturer of the terminal device, such as the vendor field). Exemplarily, the fourth information can be 1 bit information.

[0181] After receiving the first configuration information, the terminal device can determine whether it can perform data collection (e.g., CSI measurement or data collection) according to its capability. For example, when the terminal device has insufficient capability, the terminal device can send (or feed back) configuration failure information to the network device. The configuration failure information is used to indicate configuration failure. Alternatively, when the terminal device has insufficient capability, the terminal device can also send data collection stop information to the network device. The data collection stop information is used to indicate data collection stop. For example, the reasons for configuration failure (or data collection stop) can include at least one of the following: insufficient power (e.g., the remaining power is less than (or lower than) the minimum transmission voltage or a second threshold (or can be understood as a power threshold)), power depletion, insufficient storage space (e.g., the remaining storage space is less than the minimum data cache space or a first threshold (or can be understood as a storage space threshold)), or storage space depletion, etc. For another example, when the terminal device has sufficient or sufficient capability, the terminal device can determine whether it can perform data collection according to its capability. After sending the configuration success information to the network device, the terminal device can send insufficient capability information to the network device and stop data collection due to subsequent changes in the capability of the terminal device. For another example, when the terminal device has sufficient or sufficient capability, the terminal device can perform data collection and feed back relevant data to the network device. For example, taking data collection as CSI measurement as an example. When the terminal device has sufficient or sufficient capability, the terminal device can perform CSI measurement to obtain measurement results. Then, the terminal device can send the measurement results to the OAM entity through the MDT procedure. It should be noted that the description of the terminal device sending data collection stop information to the network device can refer to the communication scheme shown in FIG. 10 or FIG. 11, which will not be described here. It should be understood that the "power" in this application can also be described (or replaced) as "energy" and the like.

[0182] In the embodiments of the present application, when the fourth information is included in the first configuration information, the terminal device can carry the vendor information (e.g., vendor ID) in the measurement results. Alternatively, the terminal device can also send the vendor information to the OAM entity separately, or can carry the first data and the vendor information in the same information (or the same message) to send to the OAM entity. Alternatively, when the fourth information is included in the first configuration information, if the terminal device does not want to report the vendor information, the fourth information can be ignored.

[0183] For the ADRF network element, after receiving the subscription information 2, the ADRF network element can send historical data to the NWDAF network element.

[0184] For the AMF network element, after receiving the subscription information 3, the AMF network element can send a first request to the access network device. The first request is used to request model training data. After receiving the first request, the access network device can send first configuration information to the terminal device. The first configuration information can be used to configure the parameters of the terminal device for data collection. After receiving the first configuration information, the terminal device can send model training data to the access network device. After receiving the model training data, the access network device can send the model training data to the AMF network element. After receiving the model training data, the AMF network element can send the model training data to the NWDAF network element. Optionally, the first request can also carry the first configuration information, so that the access network device can send the first configuration information in the first request to the terminal device. Optionally, after receiving the subscription information 3, the AMF network element can also send the first configuration information to the access network device, so that the access network device can forward the first configuration information to the terminal device.

[0185] For example, after receiving the first configuration information, the terminal device can determine whether it can perform data collection (such as CSI measurement or data collection) according to its own capability. For example, when the terminal device is insufficient in capability, the terminal device can send configuration failure information to the access network device. The configuration failure information is used to indicate configuration failure. Optionally, when the terminal device is insufficient in capability, the terminal device can also send data collection stop information to the access network device. The data collection stop information is used to indicate data collection stop. For example, the reasons for configuration failure (or data collection stop) can include at least one of the following: insufficient power, power depletion, insufficient storage space, or exhausted storage space, etc. For another example, when the terminal device is sufficient or sufficient in capability, the terminal device can determine whether it can perform data collection according to its own capability. After sending configuration success information to the network device, the terminal device can send capability deficiency information to the network device and stop data collection due to subsequent changes in the capability of the terminal device. For another example, when the terminal device is sufficient or sufficient in capability, the terminal device can perform data collection to obtain model training data. After that, the terminal device can send the model training data to the access network device, and then the access network device sends the model training data to the AMF network element. It should be noted that the description of the terminal device sending data collection stop information to the access network device can refer to the communication scheme shown in FIG. 10 or FIG. 11, which will not be repeated here.

[0186] In the embodiments of the present application, when the fourth information is included in the first configuration information, the terminal device can carry the vendor information in the model training data. Alternatively, the terminal device can also send the vendor information to the access network device separately, or can carry the model training data and the vendor information in the same information (or the same message) and send them to the access network device. Alternatively, when the fourth information is included in the first configuration information, if the terminal device does not want to report the vendor information, the fourth information can be ignored.

[0187] In another possible implementation, the NWDAF network element sends subscription information 4 to the DCCF network element. The subscription information 4 is used to subscribe to the first data from the DCCF network element. After receiving the subscription information 4, the DCCF network element can determine whether the first data has been collected (or determine whether the local cache area has the first data). If the DCCF network element has collected (or the local cache area has the first data), the DCCF network element can obtain the first data and directly send the first data to the NWDAF network element. If the DCCF network element has not collected (or the local cache area does not have the first data) or has only collected part of (or the local cache area has only part of the first data), the DCCF network element can request other network elements (such as the OAM entity, the ADRF network element, or the AMF network element) to obtain the first data. Alternatively, the DCCF network element can send subscription information to one or more of the OAM entity, the ADRF network element, or the AMF network element to obtain related data. For example, the DCCF network element sends subscription information 01, subscription information 02, and subscription information 03 to the OAM entity, the ADRF network element, and the AMF network element, respectively. The subscription information 01 is used to subscribe to the measurement results reported by the terminal device to the OAM entity through the MDT procedure, the subscription information 02 is used to subscribe to the historical data from the ADRF network element, and the subscription information 03 is used to subscribe to the model training data from the AMF network element. This implementation can enable the NWDAF network element to obtain related data of other network elements through the DCCF network element, so that the NWDAF network element does not need to directly interface with multiple second network elements, which helps to save the signaling overhead of the NWDAF network element.

[0188] For the OAM entity, after receiving the subscription information 01, the OAM entity can send the measurement results to the DCCF network element. Alternatively, the terminal device can carry the vendor information in the measurement results, or can send the vendor information to the OAM entity separately, or can carry the first data and the vendor information in the same information and send them to the OAM entity. It should be understood that the related description of the terminal device feeding back the vendor information to the OAM entity can refer to the related description in the foregoing, which will not be described here.

[0189] For the ADRF network element, after receiving the subscription information 02, the ADRF network element can send historical data to the DCCF network element.

[0190] For the AMF network element, after receiving the subscription information 03, the AMF network element can send a second request to the access network device. The second request is used to request model training data. After receiving the second request, the access network device can send first configuration information to the terminal device. The first configuration information can be used to configure the parameters of the terminal device for data collection. After receiving the first configuration information, the terminal device can send model training data to the access network device. After receiving the model training data, the access network device can send the model training data to the AMF network element. After receiving the model training data, the AMF network element can send the model training data to the DCCF network element. After receiving the measurement result, the historical data and the model training data, the DCCF network element can send the measurement result, the historical data and the model training data to the NWDAF network element. Optionally, the first configuration information can also be carried in the second request, so that the access network device can send the first configuration information in the second request to the terminal device. Optionally, after receiving the subscription information 03, the AMF network element can also send the first configuration information to the access network device, so that the access network device can forward the first configuration information to the terminal device.

[0191] Optionally, the terminal device can carry the vendor information in the model training data, or can separately send the vendor information to the access network device, or can carry the model training data and the vendor information in the same information to send to the access network device. It should be understood that the related description of the terminal device feeding back the vendor information to the access network device can refer to the related description in the foregoing, which will not be described here.

[0192] Example two: taking the first network element as the DCAF network element, the second network element as the OAM entity, the ADRF network element, the NWDAF network element and the AMF network element, and the second information as the subscription information for example. The DCAF network element can send the subscription information to one or more of the OAM entity, the ADRF network element, the NWDAF network element or the AMF network element to obtain related data. For example, taking the DCAF network element as an example, the DCAF network element sends the subscription information to the OAM entity, the ADRF network element, the NWDAF network element and the AMF network element respectively. The DCAF network element can send the subscription information 10, the subscription information 11, the subscription information 12 and the subscription information 13 to the OAM entity, the ADRF network element, the NWDAF network element and the AMF network element respectively. The subscription information 10 is used to subscribe to the measurement result reported by the terminal device to the OAM entity through the MDT procedure, the subscription information 11 is used to subscribe to the historical data from the ADRF network element, the subscription information 11 is used to subscribe to the analysis data or the collected original data from the NWDAF network element, and the subscription information 13 is used to subscribe to the model training data from the AMF network element.

[0193] For the OAM entity, the OAM entity can send the measurement result to the DCAF network element after receiving the subscription information 10. Optionally, the terminal device can carry the vendor information in the measurement result, or can also send the vendor information to the OAM entity separately, or can also carry the first data and the vendor information in the same information to send to the OAM entity. It should be understood that the related description about the terminal device feeding back the vendor information to the OAM entity can refer to the related description in Example 1 above, and will not be repeated here.

[0194] For the ADRF network element, the ADRF network element can send the historical data to the DCAF network element after receiving the subscription information 11.

[0195] For the NWDAF network element, the NWDAF network element can send the analysis data or the collected original data to the DCAF network element after receiving the subscription information 12.

[0196] For the AMF network element, the AMF network element can send a third request to the access network device after receiving the subscription information 13. The third request is used to request model training data. The access network device can send first configuration information to the terminal device after receiving the third request. The first configuration information can be used to configure the parameters of the terminal device for data collection. The terminal device can send the model training data to the access network device after receiving the first configuration information. The access network device can send the model training data to the AMF network element after receiving the model training data. The AMF network element can send the model training data to the DCAF network element after receiving the model training data. Optionally, the first configuration information can also be carried in the third request, so that the access network device can send the first configuration information in the third request to the terminal device. Optionally, the AMF network element can also send the first configuration information to the access network device after receiving the subscription information 13, so that the access network device can forward the first configuration information to the terminal device. It should be understood that the related description about the first configuration information in Example 2 can refer to the related description about the first configuration information in Example 1 above, and will not be repeated here.

[0197] Optionally, when the first network element is the DCAF network element and the second network element is the DCCF network element, the DCAF network element can also collect the related data (such as the first data) subscribed by the service device through the DCCF network element. For example, the DCAF network element can send a corresponding data request to the DCCF network element. The corresponding data request is used to request to obtain the related data. The DCCF network element can send the related data to the DCAF network element after receiving the data request.

[0198] Optionally, the terminal device can carry the vendor information in the model training data, or can separately send the vendor information to the access network device, or can send the model training data and the vendor information in the same information to the access network device. It should be understood that the related description about the terminal device feeding back the vendor information to the access network device can refer to the related description in Example 1 above, and will not be repeated here.

[0199] Implementation mode two: when the first network element is a DCCF network element, if the first data exists in the local cache area or has been collected, the first network element can obtain the first data from the local cache area.

[0200] Optionally, in this implementation mode two, when the first network element is a DCCF network element, the second network element can be a NWDAF network element, an ADRF network element, an OAM entity, an AMF network element, etc.

[0201] For example, the DCCF network element can judge whether the first data has been collected (or judge whether the first data exists in the local cache area). If the DCCF network element has collected (or the local cache area already exists the first data), the DCCF network element can obtain the first data.

[0202] If the DCCF network element has not collected (or the collection is incomplete or the local cache area does not exist the first data or the local cache area exists part of the first data), the DCCF network element can send the subscription information to one or more of the OAM entity, the ADRF network element, the NWDAF network element, or the AMF network element to obtain the related data. For example, the DCCF network element sends the subscription information to the OAM entity, the ADRF network element, the NWDAF network element, and the AMF network element respectively. The DCCF network element can send the subscription information 20, the subscription information 21, the subscription information 22, and the subscription information 23 to the OAM entity, the ADRF network element, the NWDAF network element, and the AMF network element respectively. The subscription information 20 is used to subscribe to the measurement results reported by the terminal device to the OAM entity through the MDT procedure, the subscription information 21 is used to subscribe to the historical data to the ADRF network element, the subscription information 21 is used to subscribe to the analysis data or the collected original data to the NWDAF network element, and the subscription information 23 is used to subscribe to the model training data to the AMF network element.

[0203] For the OAM entity, after receiving the subscription information 20, the OAM entity can send the measurement results to the DCCF network element. Optionally, the terminal device can carry the vendor information in the measurement results, or can separately send the vendor information to the OAM entity, or can send the first data and the vendor information in the same information to the OAM entity. It should be understood that the related description about the terminal device feeding back the vendor information to the OAM entity can refer to the related description in Example 1 above, and will not be repeated here.

[0204] For the ADRF network element, after receiving the subscription information 21, the ADRF network element can send historical data to the DCCF network element.

[0205] For the NWDAF network element, after receiving the subscription information 22, the NWDAF network element can send analysis data or collected raw data to the DCCF network element.

[0206] For the AMF network element, after receiving the subscription information 23, the AMF network element can send a fourth request to the access network device. The fourth request is used to request model training data. After receiving the fourth request, the access network device can send first configuration information to the terminal device. The first configuration information can be used to configure parameters for the terminal device to collect data. After receiving the first configuration information, the terminal device can send model training data to the access network device. After receiving the model training data, the access network device can send the model training data to the AMF network element. After receiving the model training data, the AMF network element can send the model training data to the DCCF network element. Alternatively, the first configuration information can also be carried in the fourth request, so that the access network device can send the first configuration information in the fourth request to the terminal device. Alternatively, the AMF network element can also send the first configuration information to the access network device after receiving the subscription information 23, so that the access network device can forward the first configuration information to the terminal device.

[0207] Alternatively, the terminal device can carry the vendor information in the model training data, or can separately send the vendor information to the access network device, or can carry the model training data and the vendor information in the same information to send to the access network device. It should be understood that the related description of the terminal device feeding back the vendor information to the access network device can refer to the related description in Example 1 above, which will not be described here.

[0208] Implementation mode three: when the first network element is the NWDAF network element or the DCCF network element or the DCAF network element, the first network element can send third information to the terminal device. The third information can be used to instruct (or request) the terminal device to collect data. After receiving the third information, the terminal device can send first data to the first network element.

[0209] For example, the third information can be a data collection request. For example, the third information can include a data collection configuration or a measurement configuration, or the data collection configuration or the measurement configuration can be separately sent to the terminal device as configuration information. The data collection configuration or the measurement configuration is used to configure the relevant parameters of the terminal device for data collection. For example, the data collection configuration or the measurement configuration can include indication information, or the third information can also include indication information. The indication information can be used to instruct the terminal device to fill in / report the corresponding field (which can be understood as a field used to distinguish the manufacturer to which the terminal device belongs, for example, a vendor field). For example, the indication information can be 1-bit indication information.

[0210] Optionally, the content format of the first data can be an XML format, as shown in Table 4 below. The content format of the first data can be predefined, such as a predefined XML content format of data collection, so as to standardize the recommended format of data transmission.

[0211] For example, taking the first network element as an NWDAF network element as an example. In one example, the NWDAF network element can forward the third information to the terminal device through a third network element (such as a UPF network element). After receiving the third information, the terminal device can send the first data to the NWDAF network element through the third network element. In another example, the NWDAF network element can send the third information to the terminal device through a UP plane or a user plane channel. After receiving the third information, the terminal device can send the first data to the NWDAF network element through the UP plane or the user plane channel.

[0212] Implementation four: when the first network element is an NWDAF network element or a DCCF network element or a DCAF network element, the first network element can send first configuration information to the terminal device. The first configuration information can be used to configure the parameters of the terminal device for data collection. After receiving the first configuration information, the terminal device can send the first data to the first network element.

[0213] Optionally, the related description of the first configuration information in implementation four can refer to the related description of the first configuration information in example one described above, which will not be described here.

[0214] For example, taking the first network element as the NWDAF network element as an example. After receiving the first configuration information, the terminal device can determine whether the terminal device can perform data collection (such as CSI measurement or data collection) according to the capability of the terminal device. For example, when the terminal device is insufficient in capability, the terminal device can send configuration failure information to the NWDAF network element. The configuration failure information is used to indicate configuration failure. Alternatively, when the terminal device is insufficient in capability, the terminal device can also send data collection stop information to the NWDAF network element. The data collection stop information is used to indicate that data collection is stopped. For example, the reason for configuration failure (or data collection stop) can include at least one of the following: insufficient power, power depletion, insufficient storage space, or exhausted storage space, and the like. For another example, when the terminal device is sufficient or sufficient in capability, the terminal device can determine whether the terminal device can perform data collection according to the capability of the terminal device. Then, after sending the configuration success information to the network device, the terminal device can send capability insufficient information to the network device and can stop data collection because the capability of the terminal device changes subsequently. For another example, when the terminal device is sufficient or sufficient in capability, the terminal device can perform data collection and obtain first data. Then, the terminal device can send the first data to the NWDAF network element. It should be noted that the description of the terminal device sending the data collection stop information to the NWDAF network element can refer to the communication scheme shown in FIG. 10 or FIG. 11, and details are not described herein again.

[0215] For example, continuing to take the first network element as the NWDAF network element as an example. When the fourth information is included in the first configuration information, the terminal device can carry the vendor information in the first data. Alternatively, the terminal device can also send the vendor information to the NWDAF network element separately, or can carry the first data and the vendor information in the same information (or the same message) and send the same to the NWDAF network element. Alternatively, when the fourth information is included in the first configuration information, if the terminal device does not want to report the vendor information, the fourth information can be ignored.

[0216] Step 503: The first network element sends the first data. Correspondingly, the service device receives the first data.

[0217] The implementation process of the first network element sending the first data is described below through the following possible implementation manners.

[0218] Implementation manner one: when the first network element is the NWDAF network element or the DCAF network element, the first network element can send the first data. Correspondingly, the service device receives the first data.

[0219] For example, the first network element can send the first data to the service device through a notification (notify) program.

[0220] The implementation process of the first network element sending the first data is described below through the following possible examples.

[0221] Example one: taking the first network element as the NWDAF network element, the second network element as the DCCF network element, the ADRF network element, the OAM entity and the AMF network element, the NWDAF network element sends subscription information to the OAM entity, the ADRF network element and the AMF network element respectively. In a possible implementation manner, after receiving the measurement result from the OAM entity, the historical data from the ADRF network element and the model training data from the AMF network element, the NWDAF network element can send the measurement result, the historical data and the model training data as the first data to the corresponding service device. In another possible implementation manner, after receiving the measurement result, the historical data and the model training data from the DCCF network element, the NWDAF network element can send the measurement result, the historical data and the model training data as the first data to the corresponding service device.

[0222] Example two: taking the first network element as the DCAF network element, the second network element as the OAM entity, the ADRF network element, the NWDAF network element and the AMF network element, the DCAF network element sends subscription information to the OAM entity, the ADRF network element, the NWDAF network element and the AMF network element respectively. After receiving the measurement result from the OAM entity, the historical data from the ADRF network element, the analysis data (or the collected original data) from the NWDAF network element and the model training data from the AMF network element, the DCAF network element can send the measurement result, the historical data, the analysis data (or the collected original data) and the model training data as the first data to the corresponding service device.

[0223] Optionally, when the first network element is the DCAF network element and the second network element is the DCCF network element, the DCAF network element can also collect the relevant data subscribed by the service device through the DCCF network element, and can send the relevant data as the first data to the corresponding service device.

[0224] Implementation manner two: when the first network element is the DCCF network element, if the first data exists in the local cache area or has been collected, the first network element can send the first data. Correspondingly, the service device receives the first data.

[0225] If the first network element has not collected (or the collection is incomplete or the first data does not exist in the local cache area or part of the data exists in the local cache area), after receiving the measurement result from the OAM entity, the historical data from the ADRF network element, the analysis data (or the collected original data) from the NWDAF network element and the model training data from the AMF network element, the first network element can send the measurement result, the historical data, the analysis data (or the collected original data) and the model training data as the first data to the corresponding service device.

[0226] For example, the first network element can send the first data to the service device through the notification procedure.

[0227] Implementation three: when the first network element is a NWDAF network element or a DCCF network element or a DCAF network element, if the first network element sends the third information to the terminal device, the first network element can send the first data after receiving the first data (such as the first data in XML format) fed back by the terminal device based on the third information. Correspondingly, the service device receives the first data.

[0228] For example, the NWDAF network element or the DCCF network element or the DCAF network element can send the first data in XML format to the service device through the notification procedure.

[0229] Implementation four: when the first network element is a NWDAF network element or a DCCF network element or a DCAF network element, if the first network element sends the first configuration information to the terminal device, the first network element can send the first data after receiving the first data (such as measurement result) fed back by the terminal device based on the first configuration information. Correspondingly, the service device receives the first data.

[0230] For example, the NWDAF network element or the DCCF network element or the DCAF network element can send the measurement result to the service device through the notification procedure.

[0231] Through the above steps 501 to 503, it can be seen that by introducing a new data collection identifier (such as a first identifier, for example, the first identifier can be an analysis identifier or an event identifier), after the service device subscribes to the first event use case (or can be understood as a data collection event use case) corresponding to the first identifier, the first data can be collected through the core network element (such as the first network element or the second network element, etc.), so that the service device can obtain the first data through the core network element.

[0232] Based on the implementation of the communication method shown in Figure 5, the communication method shown in Figure 5 is described in detail below through specific examples shown in Figures 6 to 9. In the specific example shown in Figure 6, the service device is an OTT server, the first network element is a NWDAF network element, the second network element includes multiple network elements such as a DCCF network element, an ADRF network element, an OAM entity, and an AMF network element, the access network device is a gNB, the terminal device is a UE, the first information and the second information are both subscription messages, the fourth information is indication information, the NWDAF network element sends a subscription message to the OAM entity and / or the ADRF network element and / or the AMF network element, or the DCCF network element sends a subscription message to the OAM entity and / or the ADRF network element and / or the AMF network element. In the specific example shown in Figure 7, the service device is an OTT server, the first network element is a DCCF network element or a DCAF network element, the second network element includes multiple network elements such as a NWDAF network element, an ADRF network element, an OAM entity, and an AMF network element, the access network device is a gNB, the terminal device is a UE, the first information and the second information are both subscription messages, the fourth information is indication information, the data fed back by the NWDAF network element to the DCCF network element or the DCAF network element is analysis data, and the DCCF network element / DCAF network element sends a subscription message to the OAM entity and / or the ADRF network element and / or the NWDAF network element and / or the AMF network element. In the specific example shown in Figure 8, the service device is an OTT server, the first network element is a NWDAF network element or a DCCF network element or a DCAF network element, the third network element is a UPF network element, the terminal device is a UE, the first information is a subscription message, the third information is a request, and the fourth information is indication information. In the specific example shown in Figure 9, the network device includes a core network element and a gNB, and the terminal device is a UE.

[0233] Figure 6 is a flowchart of another communication method provided by an embodiment of the application. As shown in Figure 6, the specific process of the method can include:

[0234] Step 601: The OTT server sends a subscription message 1 to the NWDAF network element. Correspondingly, the NWDAF network element receives the subscription message 1.

[0235] The subscription message 1 is used to subscribe to first data. For example, the subscription message 1 can be a Nnwdaf_AnalyticsSubscription_Subscribe subscription message.

[0236] For example, the subscription message 1 can include an analytics identifier or event filtering information, etc. The analytics identifier is used to identify an analytics event (such as an AI analytics event), so that different analytics identifiers can be designed for different application instances, for example, AI data collection for positioning, AI data collection for CSI feedback, and AI data collection for beam, etc. The AI data collection for positioning is used to identify an AI data collection positioning event, the AI data collection for CSI feedback is used to identify an AI data collection CSI feedback event, and the AI data collection for beam is used to identify an AI data collection beam management event.

[0237] The event filtering information can include a data size (which can be in bits, for example, 10 bits), a region of interest, a measurement result (such as a layer 1 - reference signal received power), or a beam width, etc.

[0238] For example, the correspondence between the analytics identifier and the event filtering information can refer to Table 1. It should be noted that Table 1 is only a simple example, which is used to facilitate the description of the technical solutions in the embodiments of the present application, and does not constitute a limitation on the technical solutions in the embodiments of the present application.

[0239] Table 1

[0240] Optionally, the subscription message 1 can also include a data type (such as network configuration data or UE collected data or application layer data) required by the OTT server to collect, a UE speed or a data collection time period, etc.

[0241] For example, the first data can include but is not limited to at least one of the following: a measurement result, historical data, model training data, or analytics data (or collected raw data), etc.

[0242] Optionally, after step 601 is performed, the embodiment of the application can perform steps 602-611 or steps 612-623. By performing steps 602-611, the NWDAF network element can directly subscribe to related data (such as first data) from multiple second network elements, so that the NWDAF network element can directly and effectively obtain related data. By performing steps 612-623, the NWDAF network element can obtain related data of other network elements (such as ADRF network element, OAM entity, AMF network element) through the DCCF network element, so that the NWDAF network element does not need to directly interface with multiple second network elements, which helps to save the signaling overhead of the NWDAF network element.

[0243] Step 602: The NWDAF network element sends a subscription message 2 to the OAM entity. Correspondingly, the OAM entity receives the subscription message 2.

[0244] The subscription message 2 is used to subscribe to the measurement results reported by the UE to the OAM entity through the MDT procedure.

[0245] Step 603: The OAM entity sends the measurement results to the NWDAF network element. Correspondingly, the NWDAF network element receives the measurement results.

[0246] Step 604: The NWDAF network element sends a subscription message 3 to the ADRF network element. Correspondingly, the ADRF network element receives the subscription message 3.

[0247] The subscription message 3 is used to subscribe to historical data (such as trajectory data (for example, geographical location, speed data, moving direction, height data, etc.) of the UE or measurement results, etc.).

[0248] Step 605: The ADRF network element sends the historical data to the NWDAF network element. Correspondingly, the NWDAF network element receives the historical data.

[0249] Step 606: The NWDAF network element sends a subscription message 4 to the AMF network element. Correspondingly, the AMF network element receives the subscription message 4.

[0250] The subscription message 4 is used to subscribe to model training data (such as measurement results).

[0251] Step 607: The AMF network element sends a request 1 to the gNB. Correspondingly, the gNB receives the request 1.

[0252] The request 1 is used to request model training data.

[0253] Step 608: The gNB sends configuration information 1 to the UE. Correspondingly, the UE receives the configuration information 1.

[0254] The configuration information 1 is used to configure parameters of the UE for data collection (such as CSI measurement).

[0255] For example, the configuration information 1 can be data collection configuration information, measurement configuration information, or configuration information of MDT (such as loggedmeasurementconfiguration), etc. For example, the form of loggedmeasurementconfiguration can refer to Table 2. It should be noted that Table 2 is only a simple example, which is used to facilitate the description of the technical solutions in the embodiments of the present application, and does not constitute a limitation on the technical solutions in the embodiments of the present application.

[0256] Table 2

[0257] Optionally, the configuration information 1 can also include indication information. The indication information is used to instruct the UE to fill in / report the corresponding field (which can be understood as a field used to distinguish the manufacturer to which the UE belongs, for example, a vendor field). For example, the indication information can be 1-bit indication information.

[0258] Step 609: The UE sends the model training data to the gNB. Correspondingly, the gNB receives the model training data.

[0259] In the embodiments of the present application, after receiving the configuration information 1, the UE can determine whether it can perform data collection (such as CSI measurement or data collection) according to its own capability.

[0260] For example, when the UE capability is insufficient, the UE can send configuration failure information to the gNB. The configuration failure information is used to indicate configuration failure. Optionally, when the UE capability is insufficient, the UE can also send data collection stop information to the gNB. The data collection stop information is used to indicate data collection stop. For example, the reason for configuration failure (or data collection stop) can include at least one of the following: insufficient power, power depletion, insufficient storage space, or storage space exhaustion, etc. It should be noted that the related description of the UE sending data collection stop information to the gNB can refer to the communication scheme shown in FIG. 10 or FIG. 11, which will not be repeated here.

[0261] For example, when the UE has sufficient or adequate capability, the UE can perform data collection. For example, taking CSI measurement as an example of data collection. When the UE has sufficient or adequate capability, the UE can perform CSI measurement to obtain measurement results. Then, the UE can report the measurement results to the gNB through a CSI reporting procedure. For example, the measurement results reported by the UE can include but are not limited to channel quality indicator (CQI), precoding matrix indication (PMI), layer indicator (LI), rank indicator (RI), or L1-RSRP, etc.

[0262] In one example, when the configuration information 1 includes the above-mentioned indication information, the UE can carry the vendor information of the UE in the model training data, so that the vendor information is explicit. Alternatively, the UE can also carry the data identification (or data set identification) of the model training data in the model training data. Alternatively, the UE can carry multiple items of the model training data, the vendor information, or the data identification (or data set identification) in the same information or the same message to send to the gNB.

[0263] For example, the vendor information can be the identification or name of the vendor to which the UE belongs. For example, taking the vendor information as the identification (abbreviated as vendor ID) of the vendor to which the UE belongs, and taking the vendor ID as 4 bits as an example, for example, 0001 is used to represent 0002 is used to represent 0003 is used to represent It can be understood that the vendor ID can be assigned to the UE vendor offline by the operator. In this way, the UE can make the core network element (such as the NWDAF element) know (or distinguish) in time and accurately that the reported data of the UE is the data of which vendor (or can be understood as the data of which vendor UE) by carrying the corresponding vendor ID in the reported data, so as to facilitate the core network element to provide the reported data of the UE to the corresponding OTT server in time and accurately. For example, taking the UE carrying 0001 in the reported data as an example. In this way, the core network element (such as the NWDAF element) can know that the reported data is the data of the UE through 0001 carried in the reported data, so as to facilitate the core network element to provide the reported data to the corresponding server in time and accurately.

[0264] In another example, when the configuration information 1 includes the indication information described above, the UE can include the vendor information in a container, and then carry the container in the model training data, so that the vendor information is implicit. Optionally, the UE can also carry the data identification (or data set identification) of the model training data in the model training data. Optionally, the UE can carry multiple items in the model training data, the container or the data identification (or data set identification) in the same information or the same message to the gNB.

[0265] In the embodiments of the present application, if the vendor information is implicit, the UE can distinguish the vendor information by token or index. Among them, the operator and the UE vendor can align the corresponding token or index offline.

[0266] Optionally, when the configuration information 1 includes the indication information described above, the UE can also ignore the indication information. For example, when the UE does not want to report the vendor information, the UE can ignore the indication information.

[0267] Step 610: The gNB sends the model training data to the AMF network element. Correspondingly, the AMF network element receives the model training data.

[0268] Optionally, in the ORAN system, the gNB can be split into O-DU and O-RU, or also can be split into O-CU, O-DU and O-RU. It should be understood that when the O-CU and the O-DU are not deployed separately, the O-CU and the O-DU are one whole; when the O-CU and the O-DU are deployed separately, the O-CU and the O-DU communicate through the F1 interface. Among them, the O-RU is responsible for the reception and transmission of information (or data or signal), and the O-DU is responsible for the processing of information (or data or signal).

[0269] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 608, the configuration information 1 is sent by the O-DU to the O-RU. Then, the O-RU sends the configuration information 1 to the UE. For the above step 609, the UE sends the model training data to the O-RU, and the O-RU sends the model training data to the O-DU. For the above step 610, the O-DU can send the processed model training data to the O-RU after processing the model training data (such as the O-DU adding the destination address to the model training data). Then, the O-RU sends the processed model training data to the corresponding AMF network element.

[0270] Step 611: The AMF network element sends the model training data to the NWDAF network element. Correspondingly, the NWDAF network element receives the model training data.

[0271] Step 612: The NWDAF network element sends a subscription message 5 to the DCCF network element. Accordingly, the DCCF network element receives the subscription message 5.

[0272] The subscription message 5 is used to subscribe to first data. For example, the first data can include, but is not limited to, measurement results, historical data, and model training data, etc.

[0273] Step 613: The DCCF network element sends a subscription message 6 to the OAM entity. Accordingly, the OAM entity receives the subscription message 6.

[0274] The subscription message 6 is used to subscribe to measurement results reported by the UE to the OAM entity through the MDT procedure.

[0275] Step 614: The OAM entity sends measurement results to the DCCF network element. Accordingly, the DCCF network element receives the measurement results.

[0276] Step 615: The DCCF network element sends a subscription message 7 to the ADRF network element. Accordingly, the ADRF network element receives the subscription message 7.

[0277] The subscription message 7 is used to subscribe to historical data.

[0278] Step 616: The ADRF network element sends historical data to the DCCF network element. Accordingly, the DCCF network element receives the historical data.

[0279] Step 617: The DCCF network element sends a subscription message 8 to the AMF network element. Accordingly, the AMF network element receives the subscription message 8.

[0280] The subscription message 8 is used to subscribe to model training data (such as measurement results).

[0281] Step 618: The AMF network element sends a request 2 to the gNB. Accordingly, the gNB receives the request 2.

[0282] The request 2 is used to request model training data.

[0283] Step 619: The gNB sends configuration information 2 to the UE. Accordingly, the UE receives the configuration information 2.

[0284] The configuration information 2 is used to configure parameters for the UE to collect data (such as CSI measurement). Alternatively, the related description of the configuration information 2 in step 619 can refer to the related description of the configuration information 1 in the above step 608, which will not be described here.

[0285] Step 620: The UE sends model training data to the gNB. Accordingly, the gNB receives the model training data.

[0286] Optionally, the implementation process of step 620 can refer to the implementation process of step 609 described above, and thus is not described herein again.

[0287] Step 621: The gNB sends the model training data to the AMF network element. Accordingly, the AMF network element receives the model training data.

[0288] For example, for step 619 described above, the configuration information 2 is sent by the O-DU to the O-RU. Then, the O-RU sends the configuration information 2 to the UE. For step 620 described above, the UE sends the model training data to the O-RU, and the O-RU sends the model training data to the O-DU. For step 621 described above, the O-DU can send the processed model training data to the O-RU after processing the model training data (for example, the O-DU adds a destination address to the model training data). Then, the O-RU sends the processed model training data to the corresponding AMF network element.

[0289] Step 622: The AMF network element sends the model training data to the DCCF network element. Accordingly, the DCCF network element receives the model training data.

[0290] Step 623: The DCCF network element sends the measurement result, the historical data and the model training data to the NWDAF network element. Accordingly, the NWDAF network element receives the measurement result, the historical data and the model training data.

[0291] In one example, after receiving the measurement result, the historical data and the model training data, the DCCF network element can send the measurement result, the historical data and the model training data to the NWDAF network element together. In another example, after receiving the measurement result, the historical data and the model training data respectively, the DCCF network element can also send the measurement result, the historical data and the model training data to the NWDAF network element respectively.

[0292] Step 624: The NWDAF network element sends the measurement result, the historical data and the model training data to the OTT server. Accordingly, the OTT server receives the measurement result, the historical data and the model training data.

[0293] For example, the NWDAF network element can send the measurement result, the historical data and the model training data to the OTT server through a notification program. Optionally, the NWDAF network element can also send the analysis data (or the collected original data) to the OTT server.

[0294] In one example, after receiving the measurement result, the historical data and the model training data, the NWDAF network element can send the measurement result, the historical data and the model training data to the OTT server together. In another example, after receiving the measurement result, the historical data and the model training data respectively, the NWDAF network element can also send the measurement result, the historical data and the model training data to the OTT server respectively.

[0295] As can be seen from the above steps 601 to 624, for data collection (such as AI data collection), a new analysis event (or an analysis subscription event, such as an AI data collection related analysis event) or an analysis ID is introduced. After the OTT server subscribes to the corresponding analysis event, the NWDAF network element can collect UE side data through the corresponding core network element (such as the NWDAF network element collecting UE side related data from the core network element according to the new analysis ID), thereby realizing UE side data collection, and the OTT server can collect UE side related data (such as AI related data) through the NWDAF network element.

[0296] FIG. 7 is a flow diagram of another communication method provided by the embodiments of the present application. As shown in FIG. 7, the specific flow of the method can include:

[0297] Step 701: The OTT server sends a subscription message 01 to the DCCF network element / DCAF network element. Correspondingly, the DCCF network element / DCAF network element receives the subscription message 01.

[0298] The subscription message 01 is used to subscribe to first data. For example, the subscription message 01 can be a Naf_EventExposure_Subscribe subscription message.

[0299] Exemplarily, the subscription message 01 can include an event identifier or event filter information, etc. The event identifier is used to identify a subscription event (such as an AI subscription event), so that different event identifiers can be designed for different application instances (use cases), for example, AI data collection for positioning, AI data collection for CSI feedback, and AI data collection for beam, etc. The AI data collection for positioning is used to identify a positioning event of AI data collection, the AI data collection for CSI feedback is used to identify a CSI feedback event of AI data collection, and the AI data collection for beam is used to identify a beam management event of AI data collection.

[0300] The event filter information can include a data size (which can be in bits, for example, 10 bits), a region of interest, a measurement result (such as L1-RSRP), or a beam width, etc.

[0301] For example, the correspondence between the event identifier and the event filter information can be seen from Table 3. It should be noted that Table 3 is only a simple example, which is used to facilitate the description of the technical solutions in the embodiments of the present application, and does not constitute a limitation on the technical solutions in the embodiments of the present application.

[0302] Table 3

[0303] Optionally, the subscription message 1 can also include a data type (such as network configuration data or UE collected data or application layer data) required to be collected by the OTT server, a UE speed, or a data collection time period, etc.

[0304] For example, the first data can include but is not limited to at least one of the following: a measurement result, historical data, model training data, or analysis data, etc.

[0305] Optionally, after step 701 is performed, if the DCCF network element, the DCCF network element can determine whether the first data requested by the OTT server has been collected. If the DCCF network element has not collected or only collected part of the first data, step 702 is performed. If the DCCF network element has collected the first data, the DCCF network element can send the first data to the OTT server, so that the DCCF network element does not need to interact with other network elements (such as the ADRF network element, the OAM entity, the NWDAF network element, the AMF network element, etc.) to obtain the first data, thereby reducing communication overhead. If the DCAF network element, the process of determining whether the first data requested by the OTT server has been collected is not performed, and step 702 is directly performed. By performing steps 702 to 713, the DCCF network element / DCAF network element can directly subscribe to related data from multiple second network elements, so that the DCCF network element / DCAF network element can directly and effectively obtain the related data. It can be understood that if the DCAF network element, the DCAF network element can also collect the related data subscribed by the OTT server through the DCCF network element. For example, the DCAF network element can send a data request to the DCCF network element. The data request is used to request to obtain the related data. After receiving the data request, the DCCF network element can send the related data to the DCAF network element.

[0306] For example, the DCCF network element can determine whether the local cache area has the first data. If the local cache area has part of the first data or does not have the first data, the DCCF network element can perform step 702. If the local cache area has the first data, the DCCF network element does not need to perform step 702, and can feed back the first data to the OTT server.

[0307] Step 702: The DCCF network element / DCAF network element sends a subscription message 02 to the OAM entity. Correspondingly, the OAM entity receives the subscription message 02.

[0308] The subscription message 02 is used to subscribe to the measurement result reported by the UE to the OAM entity through the MDT procedure.

[0309] Step 703: The OAM entity sends the measurement result to the DCCF network element / DCAF network element. Correspondingly, the DCCF network element / DCAF network element receives the measurement result.

[0310] Step 704: The DCCF network element / DCAF network element sends a subscription message 03 to the ADRF network element. Correspondingly, the ADRF network element receives the subscription message 03.

[0311] The subscription message 03 is used to subscribe to historical data (such as trajectory data (for example, geographical position, speed data, moving direction, height data, etc.) of the UE or measurement results, etc.).

[0312] Step 705: The ADRF network element sends historical data to the DCCF network element / DCAF network element. Accordingly, the DCCF network element / DCAF network element receives the historical data.

[0313] Step 706: The DCCF network element / DCAF network element sends a subscription message 04 to the NWDAF network element. Accordingly, the NWDAF network element receives the subscription message 04.

[0314] The subscription message 04 is used to subscribe to analysis data.

[0315] Step 707: The NWDAF network element sends analysis data to the DCCF network element / DCAF network element. Accordingly, the DCCF network element / DCAF network element receives the analysis data.

[0316] Step 708: The DCCF network element / DCAF network element sends a subscription message 05 to the AMF network element. Accordingly, the AMF network element receives the subscription message 05.

[0317] The subscription message 05 is used to subscribe to model training data (such as measurement results).

[0318] Step 709: The AMF network element sends a request 01 to the gNB. Accordingly, the gNB receives the request 01.

[0319] The request 01 is used to request model training data.

[0320] Step 710: The gNB sends configuration information 01 to the UE. Accordingly, the UE receives the configuration information 01.

[0321] The configuration information 01 is used to configure parameters for the UE to collect data (such as CSI measurement). Alternatively, the related description of the configuration information 01 in step 710 can refer to the related description of the configuration information 1 in the above step 608, which will not be described here.

[0322] Step 711: The UE sends model training data to the gNB. Accordingly, the gNB receives the model training data.

[0323] Alternatively, the implementation process of step 711 can refer to the implementation process of the above step 609, which will not be described here.

[0324] Step 712: The gNB sends model training data to the AMF network element. Accordingly, the AMF network element receives the model training data.

[0325] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 710, the O-DU sends the configuration information 01 to the O-RU. Then, the O-RU can send the configuration information 01 to the UE. For the above step 711, the UE sends the model training data to the O-RU, and the O-RU sends the model training data to the O-DU. For the above step 712, the O-DU can send the processed model training data to the O-RU after processing the model training data (such as the O-DU adding a destination address to the model training data) accordingly. Then, the O-RU sends the processed model training data to the corresponding AMF network element.

[0326] Step 713: The AMF network element sends the model training data to the DCCF network element / DCAF network element. Correspondingly, the DCCF network element / DCAF network element receives the model training data.

[0327] Step 714: The DCCF network element / DCAF network element sends the measurement result, historical data, model training data and analysis data to the OTT server. Correspondingly, the OTT server receives the measurement result, historical data, model training data and analysis data.

[0328] For example, the DCCF network element / DCAF network element can send the measurement result, historical data, model training data and analysis data to the OTT server through a notification program.

[0329] In one example, after receiving the measurement result, historical data, model training data and analysis data, the DCCF network element / DCAF network element can send the measurement result, historical data, model training data and analysis data together to the OTT server. In another example, after receiving the measurement result, historical data, model training data and analysis data respectively, the DCCF network element / DCAF network element can also send the measurement result, historical data, model training data and analysis data to the OTT server respectively.

[0330] As can be seen from the above steps 701 to 714, for data collection (such as AI data collection), a new event information (or subscription event information, such as an event ID related to AI data collection) is introduced. After the OTT server subscribes to the corresponding event, the DCCF network element / DCAF network element can collect the UE side data through the corresponding core network element (such as the DCCF network element / DCAF network element collecting the relevant data of the UE side from the core network element according to the new event ID), thereby realizing the data collection of the UE side, and the OTT server can collect the relevant data (such as AI related data) of the UE side through the DCCF network element / DCAF network element.

[0331] FIG. 8 is a flow diagram of another communication method provided by the embodiments of the present application. As shown in FIG. 8, the specific flow of the method can include the following steps:

[0332] Step 801: The OTT server sends a subscription message 001 to the NWDAF network element / DCCF network element / DCAF network element. Accordingly, the NWDAF network element / DCCF network element / DCAF network element receives the subscription message 001.

[0333] The subscription message 001 is used to subscribe to first data.

[0334] In one example, when the OTT server sends the subscription message 001 to the NWDAF network element, the subscription message 001 can be an Nnwdaf_AnalyticsSubscription_Subscribe subscription message. It should be understood that in this example, the subscription message 001 and the related description of the first data can refer to the above-mentioned description of the subscription message 1 and the first data in step 601, which will not be repeated here.

[0335] In another example, when the OTT server sends the subscription message 001 to the DCCF network element / DCAF network element, the subscription message 001 can be an Naf_EventExposure_Subscribe subscription message. It should be understood that in this example, the subscription message 001 and the related description of the first data can refer to the above-mentioned description of the subscription message 01 and the first data in step 701, which will not be repeated here.

[0336] Step 802: The NWDAF network element / DCCF network element / DCAF network element sends a request 001 to the UE. Accordingly, the UE receives the request 001.

[0337] The request 001 is used to request (or instruct) the UE to collect data. For example, the request 001 can include data collection configuration or measurement configuration, or the data collection configuration or measurement configuration can be separately sent to the UE as configuration information. The data collection configuration or measurement configuration is used to configure the related parameters of the UE for data collection. For example, the data collection configuration or measurement configuration can include indication information, or the request 001 can also include indication information. The indication information can be used to instruct the UE to fill in / report the corresponding field (which can be understood as a field for distinguishing the vendor of the UE, such as a vendor field). For example, the indication information can be 1-bit indication information.

[0338] In one example, the request 001 can be forwarded to the UE by the NWDAF network element / DCCF network element / DCAF network element through a UPF network element. In another example, the request 001 can be sent to the UE by the NWDAF network element / DCCF network element / DCAF network element through a user plane (UP) interface or a user plane channel.

[0339] At step 803, the UE sends first data to the NWDAF network element / DCCF network element / DCAF network element according to the request 001. Accordingly, the NWDAF network element / DCCF network element / DCAF network element receives the first data.

[0340] For example, the content format of the first data is an XML format. The content format of the first data can be predefined, such as a predefined XML content format of data collection, so as to standardize the recommended format of data transmission. For example, the XML content format can refer to Table 4. It should be noted that Table 4 is only a simple example, which is used to facilitate the description of the technical solutions in the embodiments of the present application, and does not constitute a limitation on the technical solutions in the embodiments of the present application.

[0341] Table 4

[0342] In the embodiments of the present application, the UE can perform data transmission with the NWDAF network element / DCCF network element / DCAF network element through a user plane. For example, in one example, the UE can forward the first data to the NWDAF network element / DCCF network element / DCAF network element through a UPF network element. In another example, the UE can send the first data to the NWDAF network element / DCCF network element / DCAF network element through a UP interface or a user plane channel.

[0343] Optionally, the UE can carry vendor information (such as a vendor ID) in the first data, or can separately send the vendor information to the NWDAF network element / DCCF network element / DCAF network element, or can carry the first data and the vendor information in the same information (or the same message) and send them to the NWDAF network element / DCCF network element / DCAF network element. The vendor information is used to indicate the vendor to which the first data belongs (or can be understood as the vendor to which the UE belongs). In this way, the UE carries the corresponding vendor ID in the first data, so that the core network element (such as the NWDAF network element) can timely and accurately know that the first data is the data of which vendor (or can be understood as the data of which vendor UE), so as to facilitate the core network element to timely and accurately provide the first data to the corresponding OTT server.

[0344] For example, the following takes the vendor information carried in the first data as an example to introduce the sending process of the vendor information through the following possible examples.

[0345] Example 1: When the data collection configuration or the measurement configuration or the request 001 includes the indication information, the UE can directly carry the vendor information (i.e., vendor information such as vendor ID) in the first data to send to the NWDAF network element / DCCF network element / DCAF network element.

[0346] The indication information is used to indicate that the UE fills in / reports the corresponding field (which can be understood as a field for distinguishing the vendor to which the UE belongs, for example, a vendor field). For example, the indication information can be 1-bit indication information. For example, taking the vendor ID as 4 bits as an example. For example, the vendor ID 0001 is used to represent The UE can directly carry 0001 in the first data to send to the NWDAF network element / DCCF network element / DCAF network element.

[0347] Example 2: When the data collection configuration or the measurement configuration or the request 001 includes the above-mentioned indication information, the UE can include the vendor information in the container. Then, the UE can carry the container in the first data to send to the NWDAF network element / DCCF network element / DCAF network element.

[0348] For example, continuing to take the vendor ID as 4 bits (for example, the vendor ID is 0001) as an example. The UE can include 0001 in the container. Then, the UE can carry the container in the first data to send to the NWDAF network element / DCCF network element / DCAF network element.

[0349] Optionally, when the data collection configuration or the measurement configuration or the request 001 includes the above-mentioned indication information, the UE can also ignore the above-mentioned indication information. For example, when the UE does not want to report the vendor information, the UE can ignore the above-mentioned indication information.

[0350] Step 804: The NWDAF network element / DCCF network element / DCAF network element sends the first data to the OTT server. Correspondingly, the OTT server receives the first data.

[0351] For example, the NWDAF network element can send the first data to the OTT server through a notification program.

[0352] As can be seen from the steps 801 to 804, the NWDAF network element / DCCF network element / DCAF network element can collect data through the user plane, can realize UE-side data collection, and can realize that the OTT server collects UE-side related data (such as AI-related data) through the NWDAF network element / DCCF network element / DCAF network element in the user plane. In addition, the method can realize the recommended format of the specification data transmission by introducing (or defining) the content format (such as the XML content format) of the data collection.

[0353] FIG. 9 is a flow diagram of another communication method provided by the embodiments of the present application. As shown in FIG. 9, the specific process of the method can include:

[0354] Step 901: The core network element sends configuration information 10 to the gNB. Correspondingly, the gNB receives the configuration information 10.

[0355] For example, the core network element can be a NWDAF network element, a DCCF network element, a DCAF network element, or an AMF network element, etc.

[0356] The configuration information 10 is used to configure the parameters of the UE for data collection (such as CSI measurement). Optionally, the related description of the configuration information 10 in step 901 can refer to the related description of the configuration information 1 in the above step 608, and will not be described here.

[0357] Step 902: The gNB sends the configuration information 10 to the UE. Correspondingly, the UE receives the configuration information 10.

[0358] Step 903: The UE sends first data to the gNB. Correspondingly, the gNB receives the first data.

[0359] For example, the first data can be measurement results or model training data, etc.

[0360] In the embodiments of the present application, after receiving the configuration information 10, the UE can determine whether it can perform data collection (such as CSI measurement or data collection) according to its own capability.

[0361] For example, when the UE capability is insufficient, the UE can send configuration failure information to the gNB. The configuration failure information is used to indicate the configuration failure. Optionally, when the UE capability is insufficient, the UE can also send data collection stop information to the gNB. The data collection stop information is used to indicate the data collection stop. For example, the reasons for the configuration failure (or data collection stop) can include at least one of the following: insufficient power, power depletion, insufficient storage space, or exhausted storage space, etc. It should be noted that the related description of the UE sending the data collection stop information to the gNB can refer to the communication scheme shown in FIG. 10 or FIG. 11, and will not be described here.

[0362] For another example, when the UE has sufficient or adequate capability, the UE can perform data collection. For example, taking CSI measurement as an example of data collection. When the UE has sufficient or adequate capability, the UE can perform CSI measurement to obtain measurement results. Then, the UE can report the measurement results to the gNB through a CSI reporting procedure.

[0363] Optionally, the UE can carry the vendor information (such as vendor ID) in the first data, or can send the vendor information to the gNB separately, or can carry the first data and the vendor information in the same information (or the same message) to send to the gNB. The vendor information is used to indicate the vendor to which the first data belongs (or can be understood as the vendor to which the UE belongs). In this way, the UE carries the corresponding vendor ID in the first data, so that the core network element (such as the NWDAF element) can timely and accurately know that the first data is the data of which vendor (or can be understood as the data of which vendor UE), so that the core network element can timely and accurately provide the first data to the corresponding OTT server.

[0364] For example, the following takes the vendor information carried in the first data as an example to introduce the sending process of the vendor information through the following possible examples.

[0365] Example 1: When the configuration information 10 includes the indication information, the UE can directly carry the vendor information (that is, the vendor information such as vendor ID) in the first data to send to the gNB.

[0366] The indication information is used to indicate that the UE fills in / reports the corresponding field (which can be understood as the field used to distinguish the vendor to which the UE belongs, for example, the vendor field). For example, the indication information can be 1-bit indication information. For example, taking the vendor ID as 4 bits as an example. For example, the vendor ID 0001 is used to represent The UE can directly carry 0001 in the first data to send to the gNB.

[0367] Example 2: When the configuration information 10 includes the above-mentioned indication information, the UE can include the vendor information in the container. Then, the UE can carry the container in the first data to send to the gNB.

[0368] For example, continuing to take the vendor ID as 4 bits (such as the vendor ID 0001) as an example. The UE can include 0001 in the container. Then, the UE can carry the container in the first data to send to the gNB.

[0369] Optionally, when the configuration information 10 includes the above-mentioned indication information, the UE can also ignore the above-mentioned indication information. For example, when the UE does not want to report the vendor information, the UE can ignore the above-mentioned indication information.

[0370] Step 904: The gNB sends the first data to the core network element. Correspondingly, the core network element receives the first data.

[0371] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above-mentioned step 901, the core network element sends the configuration information 10 to the O-RU. Then, the O-RU sends the configuration information 10 to the O-DU, and the O-DU processes the configuration information 10 accordingly (for example, adding the address of the UE to the configuration information 10). For the above-mentioned step 902, the O-DU sends the processed configuration information 10 to the O-RU, and then the O-RU sends the processed configuration information 10 to the corresponding UE. For the above-mentioned step 903, the UE sends the first data to the O-RU, and then the O-RU sends the first data to the O-DU, and the O-DU processes the first data accordingly (for example, adding the address of the core network element to the first data). For the above-mentioned step 904, the O-DU sends the processed first data to the O-RU, and then the O-RU sends the processed first data to the corresponding core network element.

[0372] As can be seen from the above-mentioned steps 901 to 904, by reserving a corresponding field (a field for distinguishing the manufacturer of the UE) (for example, reserving a corresponding field for the UE to fill in / report the manufacturer information when the standard defines the data reported by the UE), the UE fills in / reports, which can enable the UE to fill in / report the relevant content of the reserved field (for example, the relevant content of the vendor field, such as the vendor ID) in a timely and effective manner when reporting the data, so that different manufacturer data can be effectively distinguished, thereby ensuring correct data collection.

[0373] It can be understood that the communication schemes shown in the above-mentioned FIGS. 6 to 9 can be implemented separately or in combination, and the specific implementation is not limited. For example, the communication schemes shown in FIGS. 6 to 8 can be implemented in combination with the communication scheme shown in FIG. 9. In one possible implementation, the communication scheme shown in FIG. 9 can be executed after part of the steps of the communication schemes shown in FIGS. 6 or 7 or 8. In addition, the step numbers of each flowchart described in the above-mentioned FIGS. 6 to 9 are only one example of the execution flow, and do not constitute a limitation on the execution order of the steps. The steps in each flowchart are not all necessary steps, and some steps can be added or deleted based on each flowchart as needed.

[0374] FIG. 10 illustrates a flow diagram of another communication method according to some embodiments of the present application. The method is applicable to the application scenario illustrated in FIG. 3 or the communication system architecture illustrated in FIG. 4. It can be understood that the communication method illustrated in FIG. 10 is illustrated by taking a terminal device and a network device as the execution subject of interaction, but the present application does not limit the execution subject of interaction. For example, the network device can include a core network element (such as a NWDAF network element) or a module (such as a processor, a processing unit, a chip system, a circuit, or a chip) of the core network element, and / or an access network device (such as a base station) or a module (such as a processor, a processing unit, a chip system, a circuit, or a chip) of the access network device. It can be understood that, without special indication, the "terminal device" in the present application can refer to the device itself, or a module (such as a processor, a chip, or a chip system) in the terminal device, or a logic module or software capable of realizing all or part of the terminal device function. For example, the method executed by the core network element (or the access network device) in the present application can also be executed by a module applied to the core network element (or the access network device), and can also be realized by a logic node, a logic module, or software capable of realizing all or part of the core network element (or the access network device) function; the method executed by the terminal device in the present application can also be executed by a module applied to the terminal device, and can also be realized by a logic node, a logic module, or software capable of realizing all or part of the terminal device function.

[0375] As shown in FIG. 10, the method includes the following steps.

[0376] Step 1001: The network device sends second configuration information. Correspondingly, the terminal device receives the second configuration information.

[0377] The second configuration information can be used to configure parameters for data collection of the terminal device. For example, the second configuration information can be data collection configuration information, measurement configuration information, or minimization of drive test configuration information, etc.

[0378] For example, the second configuration information can include at least one of the following: data collection size (such as how much size or how many bits of data need to be collected), data collection time period (such as data collection from a certain start time to a certain end time), data collection duration (such as how long time of data needs to be collected, for example, starting from a certain time and ending after a certain duration), or data collection location range (such as data collection in which location range), etc.

[0379] Step 1002: The terminal device sends fifth information. Correspondingly, the network device receives the fifth information.

[0380] In the embodiments of the present application, after receiving the second configuration information, the terminal device can determine whether it can perform data collection (such as CSI measurement or data collection) according to its own capability.

[0381] In one example, when the terminal device is insufficient in capability (or can be referred to as capability-limited), the terminal device can stop (or refuse) data collection (such as stopping CSI measurement), and can send fifth information (or can be referred to as data collection stop information) to the network device. The fifth information is used to indicate that data collection is stopped. Optionally, the terminal device can carry the reason for data collection stop in the fifth information, or can separately send the reason for data collection stop to the network device. For example, the reason for data collection stop can include at least one of the following: insufficient power, power depletion, insufficient storage space, storage space depletion, remaining storage space less than a first threshold, remaining power supporting the maximum data amount for transmission less than the data amount of the first data, remaining storage space supporting the maximum cache space for storage less than the cache space occupied by the first data, or remaining power less than a second threshold. The first threshold and the second threshold can be configured by the network device, for example, pre-configured by the network device or pre-configured by the network device and the terminal device through negotiation, or the first threshold and the second threshold can be pre-defined, for example, pre-defined by the terminal device or pre-defined by the protocol, or the first threshold and the second threshold can be defined by the terminal device itself, for example, defined by the terminal device according to actual conditions.

[0382] Optionally, when the terminal device is insufficient in capability, the terminal device can also send second data to the network device. For example, the second data can be sent to the network device together with the fifth information, or the second data can be sent after the fifth information is sent. The second data is the data (or can be referred to as partial data, for example, the collected data is part of the first data) collected by the terminal device.

[0383] Optionally, the terminal device can also send sixth information to the network device when sending the second data to the network device, or the terminal device can also send the sixth information to the network device after sending the second data to the network device. In this way, the method can facilitate the network device to know in time that the obtained second data is not complete data but partial data. The sixth information can be used to indicate that the second data is not collected completely. For example, the second data is partial measurement results (or can be referred to as partial measurement reports), and the sixth information can be used to indicate that the second data is not collected completely.

[0384] In the embodiments of the present application, after receiving the fifth information, the network device can stop performing data collection.

[0385] In another example, when the terminal device has sufficient or adequate capability, the terminal device can perform data collection. Then, the terminal device can send the collected relevant data (such as the first data) to the network device. For example, taking CSI measurement as an example of data collection. When the terminal device has sufficient or adequate capability, the terminal device can perform CSI measurement to obtain measurement results. Then, the terminal device can send the measurement results to the network device.

[0386] Optionally, when the terminal device has sufficient or adequate capability, the terminal device can perform data collection according to its own capability judgment. Then, after the terminal device sends the configuration success information to the network device, because the capability of the terminal device changes subsequently, the terminal device can send the insufficient capability information or the fifth information to the network device, and can stop data collection.

[0387] As can be seen from the above steps 1001 to 1002, when the terminal device has insufficient capability, the terminal device can stop data collection by sending the fifth information to the network device to inform (or notify) the network device, so that the network device can stop the corresponding data collection operation in time, and the behavior of the terminal device side can be ensured to be correct, so as to avoid the terminal device side from producing incorrect behavior.

[0388] Based on the implementation of the communication method shown in FIG. 10, the communication method shown in FIG. 10 is described in detail through the specific example shown in FIG. 11. In the specific example shown in FIG. 11, the terminal device is a UE, the network device is a gNB and a core network element (such as a NWDAF element), the second configuration information is configuration information a, the fifth information is indication information a, and the sixth information is indication information b.

[0389] FIG. 11 is a flowchart of another communication method provided by an embodiment of the present application. As shown in FIG. 11, the specific process of the method can include:

[0390] Step 1101: The core network element sends the configuration information a to the gNB. Correspondingly, the gNB receives the configuration information a.

[0391] Optionally, the relevant description of the configuration information a can refer to the relevant description of the second configuration information in the above step 1001, which will not be described here again.

[0392] Optionally, in the ORAN system, the gNB can be split into O-DU and O-RU, or also can be split into O-CU, O-DU and O-RU. It should be understood that when the O-CU and the O-DU are not separately deployed, the O-CU and the O-DU are one whole; when the O-CU and the O-DU are separately deployed, the O-CU and the O-DU communicate through the F1 interface. Among them, the O-RU is responsible for the reception and transmission of information (or data or signal), and the O-DU is responsible for the processing of information (or data or signal).

[0393] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 1101, the core network element sends the configuration information a to the O-RU. Then, the O-RU sends the configuration information a to the O-DU, and the O-DU processes accordingly (such as adding the address of the UE to the configuration information a).

[0394] Step 1102: The gNB sends the configuration information a to the UE. Accordingly, the UE receives the configuration information a.

[0395] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 1102, the O-DU can send the processed configuration information a to the O-RU. Then, the O-RU can send the processed configuration information a to the corresponding UE.

[0396] Step 1103: The UE sends the indication information a to the gNB. Accordingly, the gNB receives the indication information a.

[0397] Optionally, the related description of the indication information a can refer to the related description of the fifth information in the above step 1002, which will not be repeated here.

[0398] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 1103, the UE can send the indication information a to the O-RU. Then, the O-RU sends the indication information a to the O-DU, and the O-DU processes accordingly (such as adding the address of the core network element to the indication information a).

[0399] Step 1104: The gNB sends the indication information a to the core network element. Accordingly, the core network element receives the indication information a.

[0400] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above step 1104, the O-DU can send the processed indication information a to the O-RU. Then, the O-RU can send the processed indication information a to the corresponding core network element.

[0401] Step 1105: The UE sends the collected partial data to the gNB. Accordingly, the gNB receives the collected partial data.

[0402] It should be understood that the execution of the above-mentioned step 1105 and step 1103 has no sequence. For example, step 1105 can be executed before step 1103, or also can be executed after step 1103, or also can be executed in parallel with step 1103, and the present application does not limit this.

[0403] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above-mentioned step 1105, the UE can send the collected partial data to the O-RU. Then, the O-RU sends the collected partial data to the O-DU, and the O-DU processes the collected partial data accordingly (such as adding the address of the core network element to the collected partial data).

[0404] Step 1106: The gNB sends the collected partial data to the core network element. Accordingly, the core network element receives the collected partial data.

[0405] The above-mentioned step 1105 to step 1106 is an optional step.

[0406] For example, in the ORAN system, the gNB is split into O-DU and O-RU. For the above-mentioned step 1106, the O-DU can send the processed collected partial data to the O-RU. Then, the O-RU can send the processed collected partial data to the corresponding core network element.

[0407] As can be seen from the above-mentioned steps 1101 to 1106, when the UE capability is insufficient, the UE can send the indication information a to the gNB to inform the data collection to stop, so as to further inform the core network element to stop the data collection, so that the gNB and the core network element can timely stop the corresponding data collection operation, and the behavior of the UE side can be ensured to be correct, so as to avoid the UE side to produce error behavior. In addition, the UE can also send the collected partial data to the gNB, so as to further send the collected partial data to the core network element, so that the core network element can timely obtain the collected partial data.

[0408] It can be understood that the communication scheme shown in FIG. 10 or FIG. 11 can be implemented alone or in combination with one or more of the communication schemes shown in FIG. 6 to FIG. 9, without limitation. For example, in the communication scheme shown in FIG. 11, the communication scheme shown in FIG. 11 can be implemented in combination with the communication scheme shown in FIG. 6 (or FIG. 7 or FIG. 8 or FIG. 9), and in one possible implementation, the communication scheme shown in FIG. 11 can be executed after part of the steps of the communication scheme shown in FIG. 6 (or FIG. 7 or FIG. 8 or FIG. 9). Similarly, part of the steps of the communication scheme shown in FIG. 6 (or FIG. 7 or FIG. 8 or FIG. 9) can also be implemented in combination with part of the steps of the communication scheme shown in FIG. 11, and the embodiments of the present application do not limit this. In addition, the step numbers of each flowchart described above in FIG. 11 are only one example of the execution flow, and do not constitute a limitation on the order of execution of the steps. The steps in the embodiments of the present application have no time sequence dependency relationship with each other, and there is no strict execution order. In addition, the steps shown in each flowchart are not all necessary steps, and part of the steps can be added or deleted based on each flowchart as needed.

[0409] It can be understood that, in order to implement the functions in the above-described embodiments, the terminal device or the access network device or the core network element (such as the first network element, the second network element, or the third network element) or the service device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the units and method steps of the examples described in the embodiments disclosed in the present application, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0410] FIG. 12 and FIG. 13 are structural schematic diagrams of possible communication apparatuses provided by the embodiments of the present application. The communication apparatuses can be used to implement the functions of the terminal device or the access network device or the core network element (such as the first network element, the second network element, or the third network element) or the service device in the above-described method embodiments, and thus can also achieve the beneficial effects possessed by the above-described method embodiments. In the embodiments of the present application, the communication apparatus can be the terminal device as shown in FIG. 3, the access network device as shown in FIG. 3, the OTT server as shown in FIG. 3, or the core network device as shown in FIG. 3, or can be a module (such as a chip) applied to the terminal device or the access network device or the OTT server or the core network device.

[0411] The communication apparatus 1200 shown in FIG. 12 includes a processing unit 1210 (or can be referred to as a processing module) and a transceiver unit 1220 (or can be referred to as a communication module or a transceiver module or a communication module for transmitting and receiving data). The communication apparatus 1200 can be used to implement the functions of a terminal device (such as a UE) or an access network device (such as a gNB) or a core network network element (such as a first network element, a second network element, or a third network element, etc.) or a service device (such as an OTT server) in the above-mentioned method embodiments shown in FIGS. 5-11. For example, the transceiver unit 1220 can perform the receiving actions and transmitting actions performed by the terminal device or the access network device or the core network network element or the service device in the above-mentioned method embodiments. The processing unit 1210 can perform other actions in addition to the transmitting actions and receiving actions performed by the terminal device or the access network device or the core network network element or the service device in the above-mentioned method embodiments.

[0412] When the communication apparatus 1200 is used to implement the functions of the first network element in the above-mentioned method embodiments shown in FIGS. 5-8, the transceiver unit 1220 is configured to receive first information. The first information is from a service device, and the first information can be used to subscribe to first data, and the first data is event data corresponding to a first identifier. The first identifier is used to identify a first event use case. The processing unit 1210 is configured to obtain the first data according to the first information. The transceiver unit 1220 is further configured to send the first data to the service device.

[0413] When the communication apparatus 1200 is used to implement the functions of the service device in the above-mentioned method embodiments shown in FIGS. 5-8, the transceiver unit 1220 is configured to send first information. The first information can be used to subscribe to first data, and the first data is event data corresponding to a first identifier. The first identifier is used to identify a first event use case. The transceiver unit 1220 is further configured to receive the first data. The processing unit 1210 is configured to perform corresponding processing operations, such as sorting data, etc.

[0414] When the communication apparatus 1200 is used to implement the functions of the second network element in the above-mentioned method embodiments shown in FIGS. 5-7, the transceiver unit 1220 is configured to receive second information from a first network element. The second information can be used to subscribe to first data, and the first data is event data corresponding to a first identifier. The first identifier can be used to identify a first event use case. The transceiver unit 1220 is further configured to send the first data to the first network element. The processing unit 1210 is configured to perform corresponding processing operations, such as obtaining the first data according to the second information, etc.

[0415] When the communication apparatus 1200 is configured to implement the function of the terminal device in the method embodiments shown in FIG. 5 or FIG. 8, the transceiver 1220 is configured to receive third information. The third information can be used to instruct the terminal device to perform data collection. The third information can be sent to the terminal device by a third network element, or the third information can also be sent to the terminal device by a user plane. The transceiver 1220 is further configured to send first data. The processing unit 1210 is configured to perform corresponding processing operations, such as performing data collection operations, etc.

[0416] When the communication apparatus 1200 is configured to implement the function of the terminal device in the method embodiments shown in FIG. 5 to FIG. 7, or FIG. 9, the transceiver 1220 is configured to receive first configuration information from a first network element or a second network element. The first configuration information can be used to configure parameters for the terminal device to perform data collection. The transceiver 1220 is further configured to send first data to the first network element or the second network element. The processing unit 1210 is configured to perform corresponding processing operations, such as performing data collection operations, etc.

[0417] When the communication apparatus 1200 is configured to implement the function of the core network element (such as the first network element or the second network element) in the method embodiment shown in FIG. 9, the transceiver 1220 is configured to send first configuration information to the terminal device. The first configuration information can be used to configure parameters for the terminal device to perform data collection. The transceiver 1220 is further configured to receive first data of the terminal device. The processing unit 1210 is configured to perform corresponding processing operations, such as generating the first configuration information, etc.

[0418] When the communication apparatus 1200 is configured to implement the function of the terminal device (such as a UE) in the method embodiments shown in FIG. 10 or FIG. 11, the transceiver 1220 is configured to receive second configuration information. The second configuration information can be used to configure parameters for the terminal device to perform data collection. The transceiver 1220 is further configured to send fifth information. The fifth information can be used to instruct to stop data collection. The processing unit 1210 is configured to perform corresponding processing operations, such as performing data collection operations, etc.

[0419] When the communication apparatus 1200 is configured to implement the function of the network device (such as a core network element) in the method embodiments shown in FIG. 10 or FIG. 11, the transceiver 1220 is configured to send second configuration information. The second configuration information can be used to configure parameters for the terminal device to perform data collection. The transceiver 1220 is further configured to receive fifth information. The fifth information can be used to instruct to stop data collection. The processing unit 1210 is configured to perform corresponding processing operations, such as stopping performing data collection operations, etc.

[0420] More details about the processing unit 1210 and the transceiver unit 1220 can be found in the above description of the method embodiments shown in FIG. 5 to FIG. 11, which will not be repeated here.

[0421] It should be understood that the transceiver unit 1220 in the embodiments of the present application can be implemented by an interface circuit or an interface circuit related circuit component, and the processing unit 1210 can be implemented by a processor or a processor related circuit component.

[0422] It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical functional division. Actual implementation can have another division manner. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or can be physically separated, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0423] If the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a plurality of instructions to make a computer device (which can be a personal computer, a server, etc.) or a processor execute all or part of the steps of the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0424] The communication device 1300 shown in FIG. 13 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It can be understood that the interface circuit 1320 can be a transceiver or an input / output interface. Optionally, the communication device 1300 can further include a memory 1330 for storing instructions executed by the processor 1310 or storing input data required by the processor 1310 to execute instructions or storing data generated after the processor 1310 executes instructions.

[0425] When the communication device 1300 is used to implement the method embodiments shown in FIG. 5 to FIG. 11, the processor 1310 is configured to implement the functions of the processing unit 1210, and the interface circuit 1320 is configured to implement the functions of the transceiver unit 1220.

[0426] For example, taking the terminal device as UE and the access network device as a base station. When the communication apparatus is a chip applied to the UE, the UE chip implements the functions of the UE in the method embodiments. The UE chip receives information from the base station, which can be understood as the information being received by other modules (such as a radio frequency module or an antenna) in the UE first, and then being sent to the UE chip by the modules. The UE chip sends information to the base station, which can be understood as the information being sent to other modules (such as a radio frequency module or an antenna) in the UE first, and then being sent to the base station by the modules.

[0427] When the communication apparatus is a chip applied to the base station, the base station chip implements the functions of the base station in the method embodiments. The base station chip receives information from the UE, which can be understood as the information being received by other modules (such as a radio frequency module or an antenna) in the base station first, and then being sent to the base station chip by the modules. The base station chip sends information to the UE, which can be understood as the information being sent to other modules (such as a radio frequency module or an antenna) in the base station first, and then being sent to the UE by the modules.

[0428] In this application, entity A sending information to entity B can be A sending directly to B, or A sending indirectly to B through other entities. Similarly, entity B receiving information from entity A can be entity B receiving the information sent by entity A directly, or entity B receiving the information sent by entity A indirectly through other entities. Here, entity A and B can be terminal devices or access network devices or core network elements or service devices, or can be modules inside terminal devices or access network devices or core network elements or service devices. For example, taking the core network element and the service device as an example. The sending and receiving of information can be the information interaction between the core network element and the service device, for example, the information interaction between the NWDAF network element and the OTT server. The sending and receiving of information can also be the information interaction between two core network elements, for example, the information interaction between the NWDAF network element and the ADRF network element. The sending and receiving of information can also be the information interaction between different modules in one device, for example, the information interaction between the terminal device chip and other modules in the terminal device, or the information interaction between the access network device chip and other modules in the access network device.

[0429] Based on the same idea, the embodiments of the present application further provide a possible communication system. The communication system comprises one or more of the terminal device, the access network device, the core network element or the service device. The terminal device can be used to implement the technical solutions related to the terminal device in the above embodiments, the access network device can be used to implement the technical solutions related to the access network device in the above embodiments, the core network element can be used to implement the technical solutions related to the core network element in the above embodiments, and the service device can be used to implement the technical solutions related to the service device in the above embodiments.

[0430] Based on the same idea, the embodiments of the present application further provide a computer program product, which comprises computer programs or instructions, and when the computer programs or instructions run on a communication device (or a computer), the communication device (or the computer) is caused to execute the method provided by the above embodiments.

[0431] Based on the same idea, the embodiments of the present application further provide a computer readable storage medium, which stores computer programs or instructions, and when the computer programs or instructions are executed by a communication device (or a computer), the communication device (or the computer) is caused to execute the method provided by the above embodiments.

[0432] The storage medium can be any available medium that can be accessed by a computer. For example, but not limited to: the computer readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0433] Based on the same idea, the embodiments of the present application further provide a chip, which can include a processor and can also include a memory (or the chip is coupled with the memory), and the processor executes program instructions in the memory to cause the chip to execute the method provided by the above embodiments. Wherein, "coupled" means that two components are directly or indirectly combined with each other, such as the coupling can mean that the two components are electrically connected.

[0434] Based on the same idea, the embodiments of the present application further provide a chip system, which includes a processor for supporting the computer device to implement the functions related to the terminal device, the access network device, the core network element (such as the first network element, the second network element or the third network element, etc.) or the service device in the above embodiments. In a possible implementation manner, the chip system further includes a memory for saving the necessary programs and data of the computer device. The chip system can be composed of a chip, or can contain a chip and other discrete devices.

[0435] It is to be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0436] The method steps in the embodiments of the present application can be implemented by means of hardware, or by means of a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a UE or a base station. Of course, the processor and the storage medium can also exist as discrete components in a network device or a terminal device.

[0437] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. The computer program refers to a set of instructions for instructing an electronic computer or other devices with message processing capability to perform each step. The computer program is usually written in a certain programming language and runs on a certain target architecture. When the computer program or instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer program or instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired or wireless mode. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center and the like integrated with one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or an optical medium, such as a digital video disc; or a semiconductor medium, such as a solid state disk. The computer readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0438] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0439] In the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship between the associated objects, which means that there can be three kinds of relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In the literal description of the present application, the character " / ", generally represents that the front and rear associated objects have an "or" relationship; in the formula of the present application, the character " / ", represents that the front and rear associated objects have a "division" relationship.

[0440] It can be understood that various digital numbers involved in the embodiments of the present application are only distinguished for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic.

Claims

1. A communication method characterized by comprising: The method applied to a first network element comprises: receiving first information, the first information being used for subscribing to first data, the first data being event data corresponding to a first identifier, the first identifier being used for identifying a first event use case, the first information being from a service device; obtaining the first data according to the first information; sending the first data to the service device.

2. The method of claim 1, wherein, The obtaining the first data according to the first information comprises: sending second information to a second network element, the second information being used for subscribing to the first data; receiving the first data from the second network element.

3. The method of claim 1, wherein, The obtaining the first data according to the first information comprises: sending third information, the third information being used for instructing a terminal device to collect data; receiving the first data; wherein the third information is sent to the terminal device through a third network element, or the third information is sent to the terminal device through a user plane.

4. The method of claim 1, wherein, The obtaining the first data according to the first information comprises: sending first configuration information to a terminal device, the first configuration information being used for configuring parameters of the terminal device for collecting data; receiving the first data of the terminal device.

5. The method according to any one of claims 1 to 4, wherein The first data comprises vendor information, the vendor information being used for indicating a vendor to which the first data belongs.

6. The method according to any one of claims 1 to 5, wherein, The first event use case comprises at least one of the following: data size, region of interest, layer 1-reference signal received power, beam width, or location.

7. The method according to any one of claims 1 to 6, wherein The first event use case is one of the following use cases: a positioning use case, a channel state information (CSI) feedback use case, or a beam management use case.

8. The method according to any one of claims 1 to 7, wherein, The first information comprises at least one of the following: the first identifier, a second identifier, a data size of the first data, a data type of the first data, a collection time length of the first data, or a collection time period of the first data; wherein the second identifier is used for identifying a vendor to which the first data belongs, or the second identifier is used for identifying a vendor to which the service device belongs.

9. A communication method characterized by comprising: The method applied to a second network element comprises: receiving second information from a first network element, the second information being used for subscribing to first data, the first data being event data corresponding to a first identifier, the first identifier being used for identifying a first event use case; sending the first data to the first network element.

10. The method of claim 9, wherein, The method further comprises: sending first configuration information to a terminal device, the first configuration information being used for configuring parameters of the terminal device for collecting data; receiving the first data of the terminal device.

11. The method of claim 9 or 10, wherein, The first data comprises vendor information, the vendor information being used for indicating a vendor to which the first data belongs.

12. A communication method characterized by comprising: The method applied to a terminal device comprises: receiving first configuration information from a first network element or a second network element, the first configuration information being used for configuring parameters of the terminal device for collecting data; sending first data to the first network element or the second network element.

13. The method of claim 12, wherein, The first configuration information further comprises fourth information, wherein the fourth information is used for indicating to report vendor information.

14. The method of claim 12 or 13, wherein, The first configuration information is one of the following configuration information: data collection configuration information, measurement configuration information, or minimization of drive test configuration information.

15. The method according to any one of claims 12 to 14, wherein, The first data comprises vendor information, and the vendor information is used to indicate a vendor to which the first data belongs.

16. A method of communication, comprising: The method applied to a terminal device comprises: receiving third information used to instruct the terminal device to collect data; sending first data; The third information is sent to the terminal device by a third network element, or the third information is sent to the terminal device by a user plane.

17. The method of claim 16, wherein, The first data comprises vendor information, and the vendor information is used to indicate a vendor to which the first data belongs.

18. A method of communication, comprising: The method applied to a terminal device comprises: receiving second configuration information used to configure parameters of the terminal device for collecting data; sending fifth information used to instruct to stop data collection.

19. The method of claim 18, wherein, The method further comprises: sending second data collected by the terminal device.

20. The method of claim 18 or 19, wherein, The fifth information comprises a reason for stopping data collection, wherein the reason comprises at least one of the following: a remaining storage space is less than a first threshold value, a remaining power is less than a second threshold value, a storage space is insufficient, or a power is insufficient.

21. The method of claim 20, wherein, The first threshold value and the second threshold value are configured by a network device, or the first threshold value and the second threshold value are predefined.

22. The method of any one of claims 18-21, wherein, The second configuration information comprises at least one of the following: a data collection size, a data collection time period, a data collection duration, or a data collection location range.

23. The method of any one of claims 18-22, wherein, The second configuration information is one of the following configuration information: data collection configuration information, measurement configuration information, or minimization of drive test configuration information.

24. A method of communication, comprising: The method applied to a network device comprises: sending second configuration information used to configure parameters of a terminal device for performing data collection; receiving fifth information used to instruct to stop data collection.

25. The method of claim 24, wherein, The method further comprises: receiving second data collected by the terminal device.

26. The method of claim 25, wherein, The method further comprises: receiving sixth information used to indicate that the second data is not collected completely.

27. A communications device, characterized by The modules or units for executing the method in any of claims 1-8, or the modules or units for executing the method in any of claims 9-11, or the modules or units for executing the method in any of claims 12-15, or the modules or units for executing the method in any of claims 16-17, or the modules or units for executing the method in any of claims 18-23, or the modules or units for executing the method in any of claims 24-26.

28. A communications device, characterized by comprise a processor and an interface circuit; The interface circuit is used to receive signals from other communication devices and transmit the signals to the processor or send signals from the processor to other communication devices; The processor is configured to implement the method of any one of claims 1-8 or the method of any one of claims 9-11 or the method of any one of claims 12-15 or the method of any one of claims 16-17 or the method of any one of claims 18-23 or the method of any one of claims 24-26 by logic circuitry or by executing computer program instructions.

29. A computer-readable storage medium, characterized in that, The computer program or instructions stored in the computer readable storage medium, when executed by the communication device, cause the communication device to perform the method of any one of claims 1-8 or the method of any one of claims 9-11 or the method of any one of claims 12-15 or the method of any one of claims 16-17 or the method of any one of claims 18-23 or the method of any one of claims 24-26.

30. A computer program product, characterised in that, The computer program product comprises computer program or instructions, which, when run on a communication device, cause the communication device to perform the method of any one of claims 1-8 or the method of any one of claims 9-11 or the method of any one of claims 12-15 or the method of any one of claims 16-17 or the method of any one of claims 18-23 or the method of any one of claims 24-26.

Citation Information

Patent Citations

  • Event opening method and device

    CN115996369A

  • Information processing method and apparatus based on model transmission state analysis

    WO2023093430A1

  • Model performance monitoring method and apparatus, and device and medium

    WO2023141834A1

  • Communication related to analysis information

    WO2023172094A1