COMMUNICATION METHOD, COMMUNICATION DEVICE, AND COMMUNICATION SYSTEM

Abstract

Provided are a communication method, a communication apparatus, and a communication system for implementing a data service. The method includes the following. That is, a domain data orchestration network element receives first requirement information, and based on the first requirement information and a part of one or more domain data service function information, determines at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element, and transmits the operation configuration information. The first requirement information is a service requirement in the initial data and is a service requirement corresponding to the domain data orchestration network element. The part of one or more domain data service function information has a one-to-one correspondence with the at least one domain data agent network element. The at least one domain data agent network element is at least one of the one or more domain data agent network elements. The first requirement information corresponds to at least one of the parts of the one or more domain data service function information. And the operation configuration information of any one of the at least one domain data agent network elements indicates an operation to be executed on the initial data by any one of the domain data agent network elements.

Description

[Technical Field]

[0001] The present application relates to the field of communications, and in particular to a communication method, a communication device, and a communication system. [Background technology]

[0002] This application claims priority to Chinese Patent Application No. 202210612735.4, filed with the State Intellectual Property Office of China on May 31, 2022, and entitled "Communication Method, Communication Device, and Communication System," which is incorporated herein by reference in its entirety.

[0003] In a data service (DS), data collection, pre-processing, analysis, and other operations may be performed on the data, and the obtained data is provided as a service product. With the expansion of the scale of mobile communication networks, the development of new technologies, and the like, the amount of data in the mobile communication networks is increasing, and the demand for data services is also increasing.

[0004] Therefore, data in a mobile communication network may be processed based on a data service architecture to implement data services, although the specific implementation is still under discussion. Summary of the Invention

[0005] SUMMARY OF THE INVENTION The embodiments of the present application provide a communication method, a communication device, and a communication system for processing data in a mobile communication network to implement a data service based on a data service architecture.

[0006] To achieve the above objectives, the following technical solutions are used in this application:

[0007] According to a first aspect, there is provided a communication method. The communication method includes: a domain data orchestration network element receiving first requirements information; the domain data orchestration network element determining at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information and one or more portions of domain data service capability information; and the domain data orchestration network element transmitting the operation configuration information. The first requirements information is a service requirement related to the first data and corresponds to the domain data orchestration network element. The one or more portions of domain data service capability information correspond one-to-one to one or more domain data agent network elements, the at least one domain data agent network element being at least one of the one or more domain data agent network elements, the first requirements information corresponding to at least one of the one or more portions of domain data service capability information, and the operation configuration information of any one of the at least one domain data agent network element indicating an operation to be performed by any one domain data agent network element on the first data.

[0008] According to the communication method provided in the first aspect, a domain data orchestration network element receives first requirements information, determines from one or more domain data agent network elements which domain data agent network elements are participating in a current data service based on the first requirements information and one or more portions of domain data service capability information, and obtains operation configuration information corresponding to each domain data agent network element participating in the current data service. The operation configuration information indicates an operation to be performed by the domain data agent network element on the first data, and the first requirements information corresponds to at least one or more portions of domain data service capability information. The domain data orchestration network element transmits the operation configuration information to the corresponding domain data agent network element, and the domain data agent network element performs the operation indicated by the operation configuration information. In this manner, a data service can be implemented.

[0009] In a possible design, the domain data orchestration network element's determining at least one domain data agent network element and operational configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information and the one or more portions of domain data service capability information may include: the domain data orchestration network element determining the at least one domain data agent network element based on the first requirements information and the one or more portions of domain data service capability information; if any one of the at least one domain data agent network elements has access to the first data, the domain data orchestration network element determining operational configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirements information and the one or more portions of domain data service capability information.

[0010] In this way, the domain data orchestration network element may first determine the domain data agent network elements participating in the data service, and then determine the corresponding operation configuration information if it is determined that the domain data agent network element has access to the first data, or may not determine the corresponding operation configuration information if it is determined that the domain data agent network element does not have access to the first data, thereby implementing a trusted data service.

[0011] In one possible design, the communication method provided in the first aspect may further include the domain data orchestration network element receiving a first validation response message from the trust anchor. The first validation response message may indicate whether any one of the at least one domain data agent network element has access to the first data. A trusted data service may be implemented.

[0012] In a possible design, the communication method provided in the first aspect may further include the domain data orchestration network element sending a first validation request message to the trust anchor, the first validation request message being for requesting verification of whether any one of the at least one domain data agent network elements has access to the first data. A trusted data service may be implemented.

[0013] In a possible design, the communication method provided in the first aspect may further include the domain data orchestration network element receiving first indication information from the data orchestration network element, where the first indication information may indicate that the domain data agent network element directly communicating with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0014] In this way, the domain data orchestration network element may know about the domain to which the domain data agent network element that communicates directly with the service request network element belongs.

[0015] In a possible design, the communication method provided in the first aspect may further include the domain data orchestration network element sending first communication information, wherein the first communication information may indicate information about a domain data agent network element in at least one domain data agent network element that directly communicates with the service request network element.

[0016] In other words, the domain data orchestration network element may select a domain data agent network element that communicates directly with the service requesting network element from the domain data agent network elements determined to be participating in the current data service.

[0017] In one possible design, the communication method provided in the first aspect may further include the domain data orchestration network element receiving domain data service capability information corresponding to one or more domain data agent network elements, such that the domain data orchestration network element receives the data service capabilities reported by the domain data agent network elements.

[0018] In one possible design, the communication method provided in the first aspect may further include: the domain data orchestration network element transmitting first data service capability information to the data orchestration network element, where the first data service capability information may be determined based on one or more portions of the domain data service capability information.

[0019] In this way, the domain data orchestration network element may collect statistical information about the domain data service capability information of the domain data agent network elements in the local domain to obtain first data service capability information, and send the first data service capability information to the data orchestration network element.

[0020] In a possible design, the domain data service capability information of any one of the one or more domain data agent network elements may include, but is not limited to, one or more of the following: an identifier of any one of the domain data agent network elements, location information of any one of the domain data agent network elements, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0021] In a possible design, the operations indicated by the operation configuration information include one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with the service request network element. It should be noted that the data service functions of the domain data agent network element are not limited thereto. In this way, the domain data agent network element can perform the operations indicated by the operation configuration information.

[0022] It should be noted that the operations indicated by the operation configuration information in this application are different from general encoding / decoding, modulation / demodulation, and rate matching.

[0023] In a possible design manner, the first requirement information includes one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0024] In a possible design scheme, the domain data orchestration network element is a core network domain data orchestration network element or an access network domain data orchestration network element.

[0025] In a possible design, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

[0026] For example, a data agent network element in a core network domain may include, but is not limited to, one or more of the following: a core network domain data agent network element and a standalone data agent network element. A data agent network element in an access network domain may include, but is not limited to, one or more of the following: an access network domain data agent network element, an end domain data agent network element, and a standalone data agent network element.

[0027] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0028] Optionally, the initial data may include, but is not limited to, one or more of the following: data on the terminal equipment side, data on each function node on the access network equipment side, data on each function node on the transport network side, data on each function node on the core network side, data on each function node of operations, administration and maintenance (OAM), and combined data.

[0029] Optionally, the synthetic data may be artificially synthesized data.

[0030] According to a second aspect, there is provided a communication method, the communication method including: receiving a first service request message from a data orchestration network element; determining first requirement information and second requirement information based on requirement information, first data service capability information, and second data service capability information from the data orchestration network element; and transmitting the first requirement information and second requirement information from the data orchestration network element, the requirement information being service requirements related to the first data and determined based on a service requested using the first service request message, the first data service capability information corresponding to a first domain data orchestration network element, the second data service capability information corresponding to a second domain data orchestration network element, the first requirement information being service requirements related to the first data and corresponding to the first domain data orchestration network element, and the second requirement information being service requirements related to the first data and corresponding to the second domain data orchestration network element.

[0031] In a possible design scenario, the first service request message may be for requesting an application service or a service service.

[0032] In a possible design, the communication method provided in the second aspect may further include receiving, by the data orchestration network element, first data service capability information from the first domain data orchestration network element, where the first data service capability information may be determined based on one or more portions of the domain data service capability information.

[0033] In a possible design, the communication method provided in the second aspect may further include receiving, by the data orchestration network element, second data service capability information from the second domain data orchestration network element, where the second data service capability information may be determined based on one or more portions of the domain data service capability information.

[0034] In a possible design, the one or more pieces of domain data service capability information have a one-to-one correspondence with one or more domain data agent network elements, and the domain data service capability information of any one of the one or more domain data agent network elements may include one or more of the following: an identifier of any one of the domain data agent network elements, location information of any one of the domain data agent network elements, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0035] In a possible design, the first service request message is from a service requesting network element, and the communication method provided in the second aspect may further include the data orchestration network element sending a second verification request message to the trust anchor, the second verification request message being for requesting verification of whether the service requesting network element has access to the first data.

[0036] In a possible design, the first service request message is from a service request network element, and the communication method provided in the second aspect may further include the data orchestration network element sending first indication information to the first domain data orchestration network element and / or the second domain data orchestration network element, where the first indication information may indicate that the domain data agent network element directly communicating with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0037] In a possible design, the communication method provided in the second aspect may further include the data orchestration network element sending updated information regarding the data security and privacy protection technology repository and / or updated information regarding the analysis tool repository.

[0038] In a possible design scenario, the requirements information may include one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0039] In a possible design scenario, the requirements information may correspond to a data service task identifier.

[0040] In a possible design scheme, the first domain data orchestration network element may be a core network domain data orchestration network element, and the second domain data orchestration network element is an access network domain data orchestration network element.

[0041] In a possible design, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

[0042] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0043] Regarding the technical effects of the communication method according to the second aspect, please refer to the technical effects of the communication method according to any possible implementation of the first aspect, and the details will not be described again in this specification.

[0044] According to a third aspect, there is provided a communication method. The communication method includes the following: a first domain data agent network element receives operation configuration information; the first domain data agent network element processes first data based on an operation indicated by the operation configuration information to obtain first information; if the operation configuration information indicates that the first domain data agent network element is to communicate with a second domain data agent network element, the first domain data agent network element transmits the first information to the second domain data agent network element; or, if the operation configuration information indicates that the first domain data agent network element is to communicate with a service request network element, the first domain data agent network element transmits the first information to the service request network element. The operation configuration information indicates an operation to be performed by the first domain data agent network element on the first data.

[0045] In a possible design scenario, the operations indicated by the operation configuration information may include one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with service request network elements.

[0046] In one possible design, the first domain data agent network element processing the first data based on the operation indicated by the operation configuration information to obtain the first information includes the first domain data agent network element sending a data request message to a third domain data agent network element based on the operation configuration information, and the first domain data agent network element receiving a data response message from the third domain data agent network element. The data request message may be for requesting one or more of the following data: network data, user data, Internet of Things data, and artificial intelligence model data. The data response message includes one or more of the data included in the data request message.

[0047] In a possible design scheme, the data request message may further include security information, which is used to verify whether the first domain data agent network element has access rights to the first data.

[0048] In one possible design, the first domain data agent network element processing the first data based on the operation indicated by the operation configuration information to obtain the first information includes the first domain data agent network element processing the second information based on the operation indicated by the operation configuration information to obtain the first information, wherein the second information is received by the first domain data agent network element, and the second information is obtained based on the first data.

[0049] In a possible design, the communication method provided in the third aspect may further include receiving, by the first domain data agent network element, a first validation response message from the trust anchor, the first validation response message indicating that the second domain data agent network element has access to the first data of the first domain data agent network element.

[0050] In a possible design, the communication method provided in the third aspect may further include the first domain data agent network element sending a third verification request message to the trust anchor, the third verification request message being for requesting that the second domain data agent network element verify whether it has access to the first data of the first domain data agent network element.

[0051] In a possible design, the communication method provided in the third aspect may further include: the first domain data agent network element sending domain data service capability information to the domain data orchestration network element.

[0052] In a possible design, the domain data service capability information may include one or more of the following: an identifier of the first domain data agent network element, location information of the first domain data agent network element, a data collection capability, a data pre-processing capability, a data storage capability, a data reporting capability, a data analysis capability, a capability to interact with a service requesting network element, a data protection capability, and a data compression capability.

[0053] In a possible design, the communication method provided in the third aspect may further include the first domain data agent network element receiving, from the data orchestration network element, update information regarding the data security and privacy protection technology repository and / or update information regarding the analysis tool repository.

[0054] In possible design scenarios, the first domain data agent network element may be a core network domain data agent network element, an access network domain data agent network element, a terminal domain data agent network element, or a standalone data agent network element.

[0055] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0056] For technical effects of the communication method according to the third aspect, please refer to the technical effects of the communication method according to any possible implementation of the first aspect, and details thereof will not be described again in this specification.

[0057] According to a fourth aspect, there is provided a communications device. The communications device includes a transceiver module and a processing module. The transceiver module is configured to receive first requirements information. The processing module is configured to determine at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information and one or more portions of domain data service capability information. The transceiver module is further configured to transmit the operation configuration information. The first requirements information is a service requirement related to the first data, the service requirement corresponding to the communications device. The one or more portions of domain data service capability information correspond one-to-one to the one or more domain data agent network elements, the at least one domain data agent network element being at least one of the one or more domain data agent network elements, the first requirements information corresponding to at least one of the one or more portions of domain data service capability information, and the operation configuration information of any one of the at least one domain data agent network element indicating an operation to be performed by any one of the domain data agent network elements on the first data.

[0058] In a possible design, the processing module is configured to determine at least one domain data agent network element based on the first requirements information and the one or more portions of domain data service capability information, and the transceiver module is further configured to: determine operational configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirements information and the one or more portions of domain data service capability information if any one of the at least one domain data agent network elements has access to the first data;

[0059] In one possible design, the transceiver module is further configured to receive a first validation response message from the trust anchor, the first validation response message may indicate whether any one of the at least one domain data agent network element has access to the first data.

[0060] In one possible design, the transceiver module is further configured to send a first validation request message to the trust anchor, the first validation request message requesting validation of whether any one of the at least one domain data agent network element has access to the first data.

[0061] In one possible design, the transceiver module is further configured to receive first indication information from the data orchestration network element, where the first indication information may indicate that the domain data agent network element that directly communicates with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0062] In a possible design, the transceiver module is further configured to transmit first communication information, the first communication information being indicative of information about a domain data agent network element within the at least one domain data agent network element that directly communicates with the service request network element.

[0063] In a possible design, the transceiver module is further configured to receive domain data service capability information corresponding to one or more domain data agent network elements.

[0064] In one possible design, the transceiver module is further configured to transmit first data service capability information to the data orchestration network element, where the first data service capability information can be determined based on one or more portions of the domain data service capability information.

[0065] In a possible design, the domain data service function information of any one of the one or more domain data agent network elements may include one or more of the following: an identifier of the one domain data agent network element, location information of the one domain data agent network element, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0066] In a possible design scenario, the operations indicated by the operation configuration information include one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with a service request network element.

[0067] In a possible design manner, the first requirement information includes one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0068] In a possible design scheme, the communications device is a core network domain data orchestration network element or an access network domain data orchestration network element.

[0069] In a possible design, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

[0070] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0071] It should be noted that the transceiver module according to the fourth aspect may include: a receiving module and a transmitting module, and the specific implementation of the transceiver module is not particularly limited in this application.

[0072] Optionally, the communication device according to the fourth aspect may further include a storage module for storing a program or instructions, which, when executed by the processing module, enables the communication device according to the fourth aspect to perform the method according to the first aspect.

[0073] It should be noted that the communication device according to the fourth aspect may be a domain data orchestration network element, such as a core network domain data orchestration network element or an access network domain data orchestration network element, or may be a chip (system) or another component or assembly that may be disposed within a domain data orchestration network element, which is not limited in this application.

[0074] Regarding the technical effects of the communication device according to the fourth aspect, please refer to the technical effects of the communication method according to any possible implementation of the first aspect, and the details will not be described again in this specification.

[0075] According to a fifth aspect, there is provided a communications device, the communications device including: a transceiver module and a processing module. The transceiver module is configured to receive a first service request message. The processing module is configured to determine first requirement information and second requirement information based on requirement information, first data service capability information, and second data service capability information. The transceiver module is further configured to transmit the first requirement information and the second requirement information. The requirement information is a service requirement related to the first data, the service requirement being determined based on a service requested using the first service request message, the first data service capability information corresponding to a first domain data orchestration network element, the second data service capability information corresponding to a second domain data orchestration network element, the first requirement information is a service requirement related to the first data, the service requirement corresponding to the first domain data orchestration network element, and the second requirement information is a service requirement related to the first data, the service requirement corresponding to the second domain data orchestration network element.

[0076] In a possible design scenario, the first service request message may be for requesting an application service or a service service.

[0077] In one possible design, the transceiver module is further configured to receive first data service capability information from the first domain data orchestration network element, where the first data service capability information can be determined based on one or more portions of the domain data service capability information.

[0078] In one possible design, the transceiver module is further configured to receive second data service capability information from the second domain data orchestration network element, where the second data service capability information can be determined based on one or more portions of the domain data service capability information.

[0079] In a possible design, the one or more pieces of domain data service capability information have a one-to-one correspondence with one or more domain data agent network elements, and the domain data service capability information of any one of the one or more domain data agent network elements may include one or more of the following: an identifier of any one of the domain data agent network elements, location information of any one of the domain data agent network elements, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0080] In a possible design manner, the first service request message is from a service requesting network element, and the transceiver module is further configured to send a second verification request message to the trust anchor, The second verification request message may be to request verification of whether the service requesting network element has access to the first data.

[0081] In one possible design, the first service request message is from a service requesting network element, and the transceiver module is further configured to send first indication information to the first domain data orchestration network element and / or the second domain data orchestration network element, where the first indication information may indicate that the domain data agent network element directly communicating with the service requesting network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0082] In a possible design, the transceiver module is further configured to transmit updates regarding the data security and privacy protection technology repository and / or updates regarding the analysis tool repository.

[0083] In a possible design scenario, the requirements information may include one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0084] In a possible design scenario, the requirements information may correspond to a data service task identifier.

[0085] In a possible design scheme, the first domain data orchestration network element may be a core network domain data orchestration network element, and the second domain data orchestration network element is an access network domain data orchestration network element.

[0086] In a possible design, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

[0087] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0088] It should be noted that the transceiver module according to the fifth aspect may include: a receiving module and a transmitting module, and the specific implementation of the transceiver module is not particularly limited in this application.

[0089] Optionally, the communication device according to the fifth aspect may further include a storage module for storing a program or instructions, which, when executed by the processing module, enables the communication device according to the fifth aspect to perform the method according to the second aspect.

[0090] It should be noted that the communication device according to the fifth aspect may be a data orchestration network element, or may be a chip (system) or another component or assembly that may be disposed within a data orchestration network element, which is not limited in this application.

[0091] Regarding the technical effects of the communication device according to the fifth aspect, please refer to the technical effects of the communication method according to any possible implementation of the second aspect, and the details will not be described again in this specification.

[0092] According to a sixth aspect, there is provided a communications device. The communications device includes: a transceiver module and a processing module. The transceiver module is configured to receive operation configuration information. The processing module is configured to process initial data based on an operation indicated by the operation configuration information to obtain first information. The transceiver module is further configured to: send the first information to a second domain data agent network element if the operation configuration information indicates that the communications device is to communicate with a second domain data agent network element; or, the transceiver module is further configured to: send the first information to a service request network element if the operation configuration information indicates that the communications device is to communicate with a service request network element. The operation configuration information indicates an operation to be performed by the communications device on the initial data.

[0093] In a possible design scenario, the operations indicated by the operation configuration information may include one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with service request network elements.

[0094] In a possible design, the transceiver module is further configured to send a data request message to a third domain data agent network element based on the operational configuration information. The transceiver module is further configured to receive a data response message from the third domain data agent network element. The data request message can be for requesting one or more of the following data: network data, user data, Internet of Things data, and artificial intelligence model data. The data response message includes one or more of the data included in the data request message.

[0095] In a possible design, the data request message may further include security information, which is used to verify whether the communication device has access rights to the original data.

[0096] In a possible design manner, the processing module is further configured to process the second information based on the operation indicated by the operation configuration information to obtain the first information, wherein the second information is received by the communication device, and the second information is obtained based on the initial data.

[0097] In one possible design, the transceiver module is further configured to receive a first validation response message from the trust anchor, the first validation response message indicating that the second domain data agent network element has access to the first data of the communication device.

[0098] In one possible design, the transceiver module is further configured to send a third verification request message to the trust anchor, the third verification request message being for requesting that the second domain data agent network element verify whether it has access to the first data of the communication device.

[0099] In a possible design, the transceiver module is further configured to transmit the domain data service capability information to a domain data orchestration network element.

[0100] In a possible design, the domain data service capability information may include one or more of the following: a communication device identifier, communication device location information, data collection capabilities, data pre-processing capabilities, data storage capabilities, data reporting capabilities, data analysis capabilities, capabilities for interacting with service request network elements, data protection capabilities, and data compression capabilities.

[0101] In a possible design, the transceiver module is further configured to receive updates regarding the data security and privacy protection technology repository and / or updates regarding the analysis tool repository from the data orchestration network element.

[0102] In possible design scenarios, the communications device may be a core network domain data agent network element, an access network domain data agent network element, a terminal domain data agent network element, or a standalone data agent network element.

[0103] In a possible design scenario, the initial data may include: data collected from a mobile communication network, or synthetic data.

[0104] It should be noted that the transceiver module according to the sixth aspect may include: a receiving module and a transmitting module, and the specific implementation of the transceiver module is not particularly limited in this application.

[0105] Optionally, the communication device according to the sixth aspect may further include a storage module for storing a program or instructions, which, when executed by the processing module, enables the communication device according to the sixth aspect to perform the method according to the third aspect.

[0106] It should be noted that the communication device according to the sixth aspect may be a first domain data agent network element, such as a core network domain data agent network element, an access network domain data agent network element, a terminal domain data agent network element, or a standalone data agent network element, or may be a chip (system) or another component or assembly that may be disposed within the first domain data agent network element, which is not limited in the present application.

[0107] Regarding the technical effects of the communication device according to the sixth aspect, please refer to the technical effects of the communication method according to any possible implementation of the second aspect, and the details will not be described again in this specification.

[0108] According to a seventh aspect, there is provided a communications device, the communications device including a processor, coupled to a memory, the memory configured to store a computer program.

[0109] The processor is configured to execute a computer program stored in the memory to perform the method according to any possible implementation of the first to third aspects.

[0110] In a possible design, the communications device according to the seventh aspect may further include a memory.

[0111] In one possible design, the communication device according to the seventh aspect may further include a transceiver, which may be a transceiver circuit or an input / output port, and which may be used by the communication device to communicate with another device.

[0112] It should be noted that the input port may be configured to implement a receiving function in the first to third aspects, and the output port may be configured to implement a transmitting function in the first to third aspects.

[0113] In the present application, the communications device according to the seventh aspect may be a domain data orchestration network element, a data orchestration network element, or a first domain data agent network element, or a chip or chip system disposed within the domain data orchestration network element, the data orchestration network element, or the first domain data agent network element.

[0114] Regarding the technical effects of the communication device according to the seventh aspect, please refer to the technical effects of the method according to any possible implementation of the first aspect, and the details will not be described again in this specification.

[0115] According to an eighth aspect, there is provided a communication system. The communication system includes a domain data orchestration network element and a data orchestration network element, and may further include a first domain data agent network element. The domain data orchestration network element is configured to implement the method according to the first aspect. The data orchestration network element is configured to implement the method according to the second aspect. The first domain data agent network element is configured to implement the method according to the third aspect. The communication system may further include a service request network element.

[0116] Alternatively, the communication system includes: a communication device according to the fourth aspect, configured to implement the method according to the first aspect; and a communication device according to the fifth aspect, configured to implement the method according to the second aspect. The communication system may further include a communication device according to the sixth aspect, configured to implement the method according to the third aspect. The communication system may further include a service request network element.

[0117] According to a ninth aspect, there is provided a chip system. The chip system includes a logic circuit and an input / output port. The logic circuit is configured to implement the processing function of the first to third aspects, and the input / output port is configured to implement the receiving function and the transmitting function of the first to third aspects. Specifically, the input port can be configured to implement the receiving function of the first to third aspects, and the output port can be configured to implement the transmitting function of the first to third aspects.

[0118] In a possible design, the chip system further includes a memory configured to store program instructions and data for implementing the functions of the first to third aspects.

[0119] A chip system may include a chip, or may include a chip and another individual device.

[0120] According to a tenth aspect, there is provided a computer-readable storage medium storing a computer program or instructions which, when executed on a computer, perform a method according to any possible implementation of the first to third aspects.

[0121] According to an eleventh aspect, there is provided a computer program product comprising a computer program or instructions which, when run on a computer, perform a method according to any possible implementation of the first to third aspects. [Brief explanation of the drawings]

[0122] [Figure 1] 1 illustrates an architecture of a communication system according to an embodiment of the present application; [Figure 2] FIG. 1 illustrates a data service architecture according to an embodiment of the present application. [Figure 3] FIG. 2 illustrates a functional diagram of a data services architecture according to an embodiment of the present application. [Figure 4] FIG. 1 is a schematic diagram illustrating a logical network topology according to an embodiment of the present application. [Figure 5] FIG. 2 illustrates an operational chain according to an embodiment of the present application. [Figure 6a] FIG. 1 illustrates a network architecture according to an embodiment of the present application. [Figure 6b] FIG. 1 illustrates a network architecture according to an embodiment of the present application. [Figure 6c] FIG. 1 illustrates a network architecture according to an embodiment of the present application. [Figure 6d] FIG. 1 illustrates a network architecture according to an embodiment of the present application. [Figure 6e] FIG. 1 illustrates a network architecture according to an embodiment of the present application. [Figure 7] 1 is a diagram illustrating a configuration of a communication device according to an embodiment of the present application. [Figure 8A] 1 is a schematic flow chart illustrating a communication method according to an embodiment of the present application; [Figure 8B] 1 is a schematic flow chart illustrating a communication method according to an embodiment of the present application; [Figure 8C]1 is a schematic flow chart illustrating a communication method according to an embodiment of the present application; [Figure 9] FIG. 10 illustrates another configuration of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0123] The technical solutions of the present application will be described below with reference to the accompanying drawings.

[0124] The technical solutions in the embodiments of the present application may be applied to various communication systems, for example, a universal mobile telecommunications system (UMTS), a wireless local area network (WLAN), a wireless fidelity (Wi-Fi) system, a wired network, a vehicle-to-everything (V2X) communication system, a device-to-device (D2D) communication system, a vehicular Internet of Things (V2X) communication system, a fourth-generation (4G) mobile communication system such as a long-term evolution (LTE) system or a worldwide interoperability for microwave access (WiMAX) communication system, a fifth-generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system such as a sixth-generation (6G) mobile communication system.

[0125] Any aspect, embodiment, or feature is presented in this application by describing a system that may include multiple devices, assemblies, modules, and the like. It is to be appreciated and understood that each system may include other devices, assemblies, modules, and the like and / or may not include all of the devices, assemblies, modules, and the like described with reference to the accompanying drawings. Combinations of these solutions may also be used.

[0126] It should be noted that in the embodiments of the present application, terms such as "example" and "for example" are used to indicate providing an example, illustration, or explanation. Any embodiment or design solution described in the present application as an "example" should not be described as being preferred or having more advantages than another embodiment or design solution. Rather, the term "example" is used to present a concept in a particular way.

[0127] In the embodiments of the present application, "of", "corresponding", and "corresponding" are sometimes mixed. It should be noted that the meanings expressed by these terms are the same unless differences are highlighted.

[0128] The network architectures and service scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions in the embodiments of the present application, and do not constitute limitations on the technical solutions provided in the embodiments of the present application. Those skilled in the art may recognize that, with the development of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application can also be applied to similar technical problems.

[0129] To facilitate understanding of the embodiments of the present application, the communication system shown in Figure 1 will first be used as an example to describe in detail the communication system applicable to the embodiments of the present application. For example, Figure 1 is a diagram showing the architecture of a communication system to which the communication method according to the embodiments of the present application is applicable.

[0130] As shown in Figure 1, the communication system includes a data orchestration (DO) network element and a data agent (DA) network element. There may be one or more data orchestration network elements, and there may be one or more data agent network elements.

[0131] The data orchestration network element may obtain a service request, convert the service request into service requirements for data, determine a data agent network element to implement the service requirements, and coordinate the functions of the data agent network element, so that the data agent network element performs corresponding operations and establishes a dynamic logical network topology to implement the corresponding service requirements.

[0132] For example, a data orchestration network element may be deployed within any core network element, transfer network (TN) network element, or access network equipment, or within another network element (e.g., an operations, administration, and maintenance (OAM) network element, etc.), or the data orchestration network element may be deployed independently. For example, the data orchestration network element may be deployed hierarchically in the core network or in the access network equipment. The data orchestration network element may be deployed within a network service (NS) network element. As another example, the data orchestration network element may be deployed independently in the network as a network function (NF), or as a network element. In an actual deployment, one or more NFs may form a network element.

[0133] A data agent network element may implement one or more of the following functions: data collection, preprocessing, storage, analysis, data protection, and the like. Different data agent network elements may have the same or different data service functions and may implement the same or different functions. Data agent network elements may interact with data orchestration network elements to obtain relevant operations that need to be performed to fulfill service requirements and execute those operations. Data agent network elements may establish a logical network topology to form a dynamic data pipeline (also called a data flow, service logic, function chain, operation chain, or the like). A data pipeline includes functions corresponding to one or more data agent network elements based on service requirements, and the output of the previous function becomes the input of the next function to implement the corresponding data service.

[0134] The data agent network element may be deployed within any core network element, transfer network (TN) network element, terminal equipment, or access network equipment, or within another network element (e.g., an operations, administration, and maintenance (OAM) network element, etc.), or the data agent network element may be deployed independently, e.g., as a network function NF or as a network element.

[0135] For example, a data agent network element may be evolved from any core network element, transport network element, terminal equipment, or access network equipment, or another network element. A data agent network element may implement functionality that can be implemented by any core network element, transport network element, terminal equipment, or access network equipment, or another network element. Alternatively, the functionality of a data agent network element provided in this application may be implemented by any core network element, transport network element, terminal equipment, or access network equipment, or another network element.

[0136] For example, a data agent network element may be evolved from a network data analytics function (NWDAF) network element and may implement the functionality of the NWDAF network element, scenario cases implemented based on the NWDAF network element, and the like.

[0137] Optionally, the data agent network element may be optionally deployed in any core network element, transport network element, terminal equipment, or access network equipment, or another network element based on the network element's resources and / or capabilities, to implement cross-domain data collection. The data agent network element may collect data from across domains to implement cross-domain data management and coordination.

[0138] For example, as a network function NF, a data agent network element can integrate cloud-native SBI encryption, NF dynamic instantiation, and K8S deployment encryption environments, minimizing the impact on NF performance and security.

[0139] When multiple data agent network elements exist in a communication system, some of the data agent network elements may be disposed within a network device (referring to any core network element, terminal device, access network device, or other network element), some of the data agent network elements may be deployed independently, or the multiple data agent network elements may all be disposed within a network device, or the multiple data agent network elements may all be deployed independently, but this is not a limitation of the present application.

[0140] It should be noted that the data orchestration network element may be a logical entity or a physical entity, and the data agent network element may be a logical entity or a physical entity, which is not a limitation in this application.

[0141] For example, data agent network elements may be deployed in a centralized manner or in a distributed manner, which may include distributed hash table (DHT) methods, and the like.

[0142] Data agent network elements are flexibly deployed in a distributed and on-demand manner, which can meet diverse and flexible data service requirements and reduce data collection overhead.

[0143] A core network element may be located on the network side of a communication system and configured to provide network services to access network equipment, terminal equipment, and the like. A core network element may include, but is not limited to, one or more of the following: a mobility management network element, a session management network element, a user plane network element, a policy control network element, a network exposure network element, an application network element, an NWDAF network element, and / or an OAM network element.

[0144] The mobility management network element is mainly used for mobility management, access management, and the like. In a 5G mobile communication system, the access management network element may be an access and mobility management function (AMF) network element, which mainly performs functions such as mobility management and access authentication / authorization. The mobility management network element may also be responsible for transferring user policies between the terminal and a policy control function (PCF) network element.

[0145] The session management network element is primarily used for session management (e.g., creation or deletion), maintaining session context and user plane forwarding tunnel information, allocating and managing internet protocol (IP) addresses for terminal equipment, selecting terminations that can manage user plane function interfaces, as well as policy control and charging function interfaces, downlink data notification, and the like.

[0146] In a 5G communication system, the session management network element may be a session management function (SMF) network element, which completes terminal IP address allocation, UPF selection, charging, QoS policy control, and the like.

[0147] The user plane network element serves as an interface to the data network and completes functions such as user plane data forwarding, session / flow level-based charging statistics collection, and bandwidth limitation, specifically packet routing and forwarding, quality of service (QoS) processing for user plane data, and the like. In a 5G communication system, the user plane network element may be a user plane function (UPF) network element.

[0148] The policy control network element includes a user subscription data management function, a policy control function, a charging policy control function, a quality of service (QoS) control, and the like, and is an integrated policy framework used to guide network behavior, and provides policy rule information and the like to a control plane function network element (e.g., an AMF network element or an SMF network element, etc.). In a 5G mobile communication system, the policy control network element may be a PCF.

[0149] A network exposure network element may be configured to provide a framework, authentication, and interface related to network function exposure and transfer information between a 5G system network function and another network function. In a 5G communication system, the network exposure network element may be a network exposure function (NEF) network element, which is primarily configured to expose the services and capabilities of 3GPP network functions to an AF and may further enable the AF to provide information to the 3GPP network function.

[0150] The application network element may be configured to provide various services, interact with the core network through a network exposure function (NEF) network element, and interact with a policy management framework to perform policy management. In a 5G communication system, the application network element may be an application function (AF) network element or a time sensitive network application function (TSNAF) network element, which represents a third-party or operator's application function, is an interface for obtaining external application data in the 5G network, and is mainly configured to forward application requirements on the network side.

[0151] The NWDAF network element may be configured to collect data from the core network and OAM network elements and feed back data analysis results to the NF, AF network element, or OAM network element. For example, the NWDAF network element may collect OAM data from the OAM network element and non-OAM data from the NFs in the core network or the AF network element. The non-OAM data may include non-OAM data collected at the terminal, terminal group, and service levels.

[0152] The OAM network element may collect data from the access network equipment.

[0153] The access network equipment may also be called an access device or a radio access network equipment. The access network equipment may manage radio resources, provide access services to terminal equipment, and finalize data transfer between the terminal equipment and the core network. The access network equipment may be understood as a base station in the network.

[0154] For example, the access network equipment in the embodiments of the present application may be any communication equipment having a radio transceiver function and configured to communicate with a terminal device, including but not limited to an evolved NodeB (eNB), a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (Home evolved NodeB, HeNB, or Home NodeB, HNB), a baseband unit (BBU), an access point (AP), a wireless relay node, a wireless backhaul node, and a transmission point (TP) or a transmission reception point (TRP) in a wireless fidelity (Wi-Fi) system. Alternatively, the access network equipment may be a gNB or transmission point (TRP or TP) in a 5G system such as an NR system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node forming a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU), or may be a satellite or unmanned aerial vehicle.

[0155] In some deployments, a gNB may include a central unit (CU) and a DU. The gNB may further include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implements functions of the radio resource control (RRC) layer and packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services and implements functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical layer (PHY). The AAU implements some physical layer processing functions, radio frequency processing, and functions related to active antennas. Information at the RRC layer is generated by the CU and is finally encapsulated into information at the PHY layer in the DU's PHY layer or obtained through conversion from information at the PHY layer. Therefore, in this architecture, higher layer signaling, for example, RRC layer signaling, can be considered to be transmitted by the DU or by the DU and AAU. It can be understood that the access network equipment can be a device including one or more of a CU node, a DU node, or an AAU node. Also, the CU can be wireless The CU may be classified as an access network device in a radio access network (RAN), or the CU may be classified as an access network device in a core network (CN), which is not a limitation in this application.

[0156] A terminal device is a terminal that accesses a communication system and has radio transceiver capabilities, or a chip or chip system that may be disposed within a terminal. In this application, terminal device may also be referred to as a terminal, user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user equipment. In embodiments of the present application, the terminal may be a mobile phone, a tablet computer (pad), an unmanned aerial vehicle, a computer with wireless transceiver capabilities, customer premises equipment (CPE), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a mobile phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld or computing device with wireless communication capabilities, another processing device, an in-vehicle device, or a wearable device connected to a wireless modem, a terminal in a 5G network, a terminal in a future evolved network, or the like.

[0157] As another example, the terminal device in the present application may be an express terminal in intelligent logistics (e.g., a device capable of monitoring the location of cargo vehicles, or a device capable of monitoring the temperature and humidity of cargo, etc.), a wireless terminal in intelligent agriculture (e.g., a wearable device capable of collecting data related to poultry and livestock, etc.), a wireless terminal in intelligent architecture (e.g., a smart elevator, a fire monitoring device, or a smart meter, etc.), a wireless terminal in intelligent healthcare (e.g., a wearable device capable of monitoring the physiological status of humans or animals, etc.), a wireless terminal in intelligent transportation (e.g., an intelligent bus, an intelligent vehicle, a shared bicycle, a charging station monitoring device, an intelligent traffic light, or an intelligent monitoring and intelligent parking device, etc.), or a wireless terminal in intelligent retail (e.g., a vending machine, a self-service checkout machine, or an unmanned convenience store, etc.). As another example, the terminal device in the present application may be an on-board module, an on-board assembly, an on-board component, an on-board chip, or an on-board unit arranged in a vehicle as one or more components or units. A vehicle may implement the methods provided herein by using an on-board module, on-board assembly, on-board component, on-board chip, or on-board unit disposed within the vehicle. The terminal device in this application may be a smart internet of things (SIoT) terminal device or a non-SIoT terminal device with specific computing, storage, and other functions. The non-SIoT terminal device may collect data by using an Internet of Things gateway. For example, the non-SIoT terminal device may be a terminal with limited computing capabilities, such as a single-function sensor. Optionally, a data agent network element may be disposed within the SIoT terminal device, or the SIoT terminal device may implement the functionality of a data agent network element.

[0158] It should be understood that Figure 1 is merely a simplified diagram of an example for ease of understanding, and the communication system may further include other devices not shown in Figure 1, such as a trust anchor (TA), a service request network element, and / or a data storage network element (for specific implementations, see the corresponding description below in Figure 2).

[0159] For example, Figure 2 is a diagram illustrating a data service architecture according to an embodiment of the present application. The communication system illustrated in Figure 1 is applicable to the data service architecture illustrated in Figure 2.

[0160] As shown in Figure 2, this application proposes a case where a normalized data service architecture is built based on a data plane to provide data services to service request network elements. The data service architecture may include, but is not limited to, one or more of the following: a data orchestration network element, a data agent network element, a trust anchor (TA), a service request network element, and a data storage network element.

[0161] A trust anchor may provide trusted services such as authentication, authorization, and access control (AAA), which may be implemented, for example, by using distributed ledger technology (DLT). A trust anchor may store immutable data, such as public keys, identifiers, or indexes of terminal devices or network elements, transaction-related data, or other immutable critical data.

[0162] Optionally, the storage function of distributed ledger technology can be extended with on-chain and off-chain storage methods. For example, original data is stored locally in a data agent network element or a data storage network element (off-chain), a hash value for the original data or a hash value for a digest of the packaged original data is stored in an extended DLT (on-chain), and an address pointing to the original data is also stored in the DLT (on-chain). The new hash value generated by the original data stored off-chain or the digest of the original data is compared with the hash value stored on-chain to prevent tampering with the original data.

[0163] For example, trust anchors may be deployed in a decentralized manner or in a centralized manner. Trust anchors deployed in a decentralized manner are typically deployed using distributed ledger technology (DLT). ( DLT ) The trust anchors may be nodes in a centralized system (e.g., a blockchain), or the like. Trust anchors deployed in a centralized manner may be implemented through the re-architecting and evolving of existing security and trust mechanisms, such as authentication, authorization, and access control.

[0164] For example, a trust anchor can implement security and privacy protection mechanisms for the entire data service process through data access control, such as authentication, authorization, and access control, and in combination with a data security and privacy protection technology repository, support security and privacy protection for the entire data service process, support trusted data service requirements, such as source tracing, audit functions, and user data autonomous control, support meeting data sharing and transaction requirements in trusted mechanisms, such as source tracing and audit functions, and meet compliance requirements, such as the Personal Information Protection Law (PIPL) and the General Data Protection Regulation (GDPR), to provide trusted data services. Compliance detection of user data processing can implement a decentralized verification mechanism to avoid problems of centralized reliability and failure.

[0165] Service request network elements include applications, application servers, and network services. ( NS ) The service request network element may include a service request network function, a service request network element, or the like. The application may be an operator's (or communication service provider's (CSP's)) application used for network planning and optimization, network artificial intelligence (AI), and / or the like, or it may be an application outside the mobile communication network (sometimes called a third-party application). The service request network element may be deployed independently within the network as a network function or a network element.

[0166] A data storage network element may store various types of data, such as streaming data, batch data, log information, parameter configuration information for AI models, and intermediate data, and may extend the storage capabilities of a data agent network element. For example, a DSF network element may be a centralized database or a distributed database, such as a distributed hash table (DHT) or an interplanetary file system (IPFS). For example, a data storage network element may be a data storage function (DSF) network element or may be evolved from a data storage function network element. A data storage network element may be deployed within a network as an NF or a network element.

[0167] For example, FIG. 3 is a diagram illustrating the functionality of a data service architecture according to an embodiment of the present application.

[0168] The functionality of the data orchestration network element will now be described with reference to Figure 3.

[0169] Referring to Figure 3, functions that may be implemented by a data orchestration network element include, but are not limited to, one or more of the following: interface to applications, requirements translation, data agent orchestration, data agent management, data protection, interface to network services (NS), and interface to trust anchors.

[0170] Interface to Applications: The data orchestration network element may interact with the service request network element through an interface to applications. For example, the data orchestration network element receives a service request from the service request network element. For example, the service request may be embedded requirements according to a standard template. For example, the standard template may be a service level agreement (SLA).

[0171] Requirements translation: The data orchestration network element translates the service request into service requirements for the capabilities of the data agent network element. For example, the data orchestration network element translates requirements such as service level agreements into requirements for the corresponding resources and network configurations.

[0172] Data Agent Orchestration: Data agent network elements are coordinated based on the data service capabilities of the data agent network elements to form a dynamic logical network topology to meet service requirements.

[0173] For example, the data orchestration network element translates requirements such as service level agreements into requirements for corresponding resources and network configurations, selects data agent network elements participating in the current data service based on the data service capabilities of the data agent network elements, and coordinates the data agent network elements to form a dynamic logical network topology.

[0174] Optionally, the data orchestration network element may negotiate with another network service network element in the process of performing data agent orchestration. For example, when an algorithm and computing power need to be used, the data orchestration network element may cooperate with another network service network element to select the corresponding AI algorithm and computing power, and the network service network element will execute the algorithm.

[0175] Optionally, the data orchestration network element may dynamically designate a data agent network element that interacts directly with the service request network element and send information about the data agent network element to the service request network element, allowing the application to call an application programming interface (API) of the data agent network element to obtain data, processing results, or the like.

[0176] Data Agent Management: Manages registration, deregistration, and the like of requests made by data agent network elements to data orchestration network elements, and receives data service capabilities, and the like, reported by data agent network elements.

[0177] Data Protection: Data protection functionality can be implemented through the use of a data protection technology repository (DPTR). The data protection technology repository can contain multiple algorithms, such as a data security and privacy protection algorithm repository, for example, differential privacy, homomorphic encryption, multi-party computation, and zero-knowledge proofs. Data orchestration network elements can promote or update information about the data protection technology repository to data agent network elements as needed, which serves as the data protection technology (DPT) for the data agent network elements. The data protection technology repository can be loosely coupled with the data orchestration network elements. The data protection technology repository can be a common feature of network elements within a data services architecture and can evolve and optimize independently. An independent data protection technology repository facilitates compliance detection of end-to-end (E2E) data processing.

[0178] For example, information about a data protection technology repository may include identifiers, indexes, and configuration information belonging to the data protection technology repository, as well as the data protection technology repository itself.

[0179] Interface to network services: A data orchestration network element may interact with a network service network element through an interface to network services. For example, a data orchestration network element may negotiate with a network service network element based on service requirements. For example, a data orchestration network element may collaborate with another network service network element if it needs to use algorithms and computing power.

[0180] Trust anchor agent: The trust anchor agent is the interface between the data orchestration network element and the trust anchor. The data orchestration network element may interact with the trust anchor by using the trust anchor agent functionality.

[0181] It should be noted that in the embodiments of the present application, the data orchestration network element may be divided into functional modules based on the above-described functions or the following method embodiments. For example, each functional module may be obtained through division based on each function, or two or more functions may be integrated into one module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, the division into functions or modules is merely an example and is merely a logical division of functions. In actual implementation, a different division method may be used.

[0182] The function of the data agent network element will now be described with reference to FIG.

[0183] Referring to Figure 3, functions that may be implemented by a data agent network element include, but are not limited to, one or more of the following: control, data collection, pre-processing, storage, application programming interface, data analysis, and data protection.

[0184] The data agent network element may implement data service coordination and closed-loop management by performing the functions described above and may output data for various processing requirements as needed.

[0185] Control: The functions of the data agent network elements are coordinated based on the operations set by the data orchestration network element for the data agent network elements to form a data pipeline. The control function may be implemented by a controller of the data orchestration network element.

[0186] For example, data orchestration network elements coordinate data agent network elements to form dynamic logical network topologies, and data agent network elements coordinate the functions of data agent network elements to form data pipelines, implementing automatic data management and dynamic on-demand configuration, quickly responding to new services and new requirements, supporting the implementation of rich application scenarios, enabling new data services to quickly enter the market, and shortening time to market (TTM).

[0187] Data Acquisition: Acquire data. For example, data may be acquired in a subscription / notification manner, or data is acquired in a request / response manner. Optionally, the request may indicate a data reporting trigger method, trigger conditions, a reporting periodicity, a data volume, and the like. Optionally, the data agent network element may support streaming data collection and batch data collection. Optionally, the data agent network element may support real-time data collection and non-real-time data collection. Optionally, the data agent network element may collect various types of data. Data may be categorized into several types. For example, the types of data may include, but are not limited to, network data, user data, AI model data, and internet of things (IoT) data.

[0188] It should be noted that the classification of data is not limited in the present application, and data may be classified into more or fewer types, or data may be classified into types from a different perspective, or data may not be classified into types.

[0189] In this manner, data services for various types of data can be implemented using the normalized data services architecture provided in this application.

[0190] Pre-processing: Pre-processing refers to performing cleaning, filling, smoothing, combining, normalizing, and consistency checks on collected raw data, extracting fields from raw data, converting formats, eliminating redundant data, compressing, filtering, merging, and / or other operations to improve data quality and lay the foundation for subsequent processing (e.g., analysis, etc.). Raw data is removed, which may result in problems such as data loss, data noise, data redundancy, and / or dataset imbalance.

[0191] Storage: Supports centralized and decentralized storage. Optionally, data requiring strict access or privacy protection, such as user subscription data, is stored locally within the data agent network elements.

[0192] Application Programming Interface: Each function of the data agent network element is implemented using an application programming interface. ( API ) The service provider may provide services directly to service requesters through the service provider.

[0193] Data analytics: Data analytics is loosely coupled with the data agent network element and can be deployed separately from the data agent network element, if necessary. It can support various data analysis techniques, such as AI training, AI inference, machine learning (ML), and big data analytics. This data analytics function can invoke data services at the data agent network element's data collection, preprocessing, and storage levels through APIs. Optionally, the AI ​​models required in the data analysis process can be preconfigured locally on the data agent network element or driven by the network service network element.

[0194] Data Protection: Data is processed using techniques such as k-anonymity, l-diversity, and differential privacy, which prevent attackers from directly obtaining sensitive information from declassified data and protect data privacy. Information about data protection technology repositories may be pre-installed on data agent network elements or promoted by the Data Providers (DOs) as needed, and security and privacy protection for data is implemented at each level of the data agent network elements.

[0195] It should be noted that in the embodiments of the present application, the data agent network element may be divided into functional modules based on the functions described above or the following method embodiments. For example, each functional module may be obtained through division based on each function, or two or more functions may be integrated into one module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, the division into functions or modules is merely an example and is merely a logical division of functions. In actual implementation, other division methods may be used.

[0196] 4 is a schematic diagram illustrating a logical network topology according to an embodiment of the present application. Hereinafter, referring to FIG. 4, the logical network topology will be described. ( D A) The logical network topology formed by adjusting the

[0197] 4, the logical network topologies may include, but are not limited to, the following: a star logical network topology, a mesh logical network topology, and a hybrid logical network topology.

[0198] For example, in a star logical network topology, a DA as an aggregation node may collect information about a common node DA and further process the collected information. Optionally, a DA as an aggregation node may directly interact with a service request network element, and the common node DA may interact with the service request network element through a DA as an aggregation node. This is not limited in this application. The DA that directly interacts with a service request network element may be any DA. The star logical network topology is applicable to scenarios such as data aggregation and federated learning.

[0199] For example, in a mesh logical network topology, data collaboration is performed between DAs, and any DA can be selected to directly interact with a service requesting network element.

[0200] For example, in a hybrid (or hybrid-hierarchical) logical network topology, a DA as an aggregation node may hierarchically collect information about common node DAs and further process the collected information. Similar to a star logical network topology, a DA as an aggregation node may directly interact with a service request network element, and a common node DA may interact with a service request network element through a DA as an aggregation node. This is not limited in the present application. A DA that directly interacts with a service request network element may be any DA.

[0201] It should be noted that the logical network topology shown in Figure 4 is only an example provided in this application. In actual applications, the data orchestration network element may be connected to the data agent network element as needed, as long as it can implement the data service. ( D A) can be adjusted to form any logical network topology.

[0202] 5 is a diagram illustrating an operation chain according to an embodiment of the present application. Hereinafter, with reference to FIG. 5, the operation chain formed by controlling the functions of the data agent network elements by the data agent network elements will be described.

[0203] An operation chain is formed by coordinating the functions of a data agent network element based on operations set by a data orchestration network element for a data agent network element and obtained by the data agent network element from the data orchestration network element.

[0204] For example, as shown in Figure 5, the operations configured in the data agent network element 1 and acquired by the data agent network element 1 from the data orchestration network element include: analyzing the data acquired from another data agent network element after pre-processing such as merging is performed on the data, and sending the analysis result to the service request network element. The data agent network element 1 coordinates functions to form the operation chain 1 shown in Figure 5: collecting data, then pre-processing the data, analyzing the pre-processing result, and sending the analysis result to the service request network element through the application programming interface.

[0205] In another example, as shown in Figure 5, it is assumed that the operations configured in the data agent network element 1 and obtained by the data agent network element 1 from the data orchestration network element include the following: when collected data is transmitted to the data agent network element 2, the data agent network element 1 coordinates functions to form the operation chain 2 shown in Figure 5, namely, collecting data and sending the data to the data agent network element 2.

[0206] It should be noted that the operation chain 1 and operation chain 2 shown in Figure 5 are merely examples provided in the present application and do not constitute any restriction on the order of performing the functions of the data agent network elements. The order of performing the functions of the data agent network elements may be dynamically adjusted based on service requirements.

[0207] For example, Figures 6a to 6e are diagrams illustrating several network architectures according to embodiments of the present application. The communication system illustrated in Figure 1 is applicable to the network architectures illustrated in Figures 6a to 6e.

[0208] Figure 6a illustrates a network architecture used when the core network equipment and the access network equipment are all service-oriented; Figure 6b illustrates a network architecture used when the access network equipment is not service-oriented and the core network is service-oriented; Figure 6c illustrates a network architecture used when the access network equipment is not service-oriented and the core network is service-oriented (the N4 interface is spare); and Figure 6d illustrates a network architecture where network elements are directly interconnected.

[0209] Referring to Figures 6a to 6c, the network architecture may include, but is not limited to, one or more of the following: a service request network element, a terminal device, an access network device, a user plane network element, a data network element, a core network element, a data orchestration network element, a data agent network element, a data storage network element, a trust anchor, and a service request network element. For specific implementations, please refer to the descriptions in Figures 1 to 5. Details will not be described again herein. The network architecture may further include, but is not limited to, one or more of the following: a mobility management network element (Figures 6b and 6c). The network architecture may further include, but is not limited to, one or more of the following: a session management network element (Figure 6c). The core network elements shown in Figures 6a to 6c may include any core network element other than a user plane network element, a mobility management network element, and / or a session management network element.

[0210] A data agent network element may be deployed within any network element other than a data orchestration network element, a data storage network element, and a trust anchor within the network architecture. In other words, any network element other than a data orchestration network element, a data storage network element, and a trust anchor within the network architecture may implement the functionality of a data agent network element.

[0211] Data Orchestration Network Elements Service Oriented Interfaces DOThe data agent network element interacts with other network elements (e.g., a service request network element, a data agent network element, a core network element, and a trust anchor) through a service-oriented interface N DA The network element interacts with other network elements (e.g., a service request network element, a data orchestration network element, a core network element, a terminal device, an access network device, a data storage network element, and a trust anchor) through a service-oriented interface N. DSF The trust anchor interacts with other network elements (e.g., data agent network elements, core network elements, terminal equipment, and access network equipment) through a service-oriented interface N TA The network element interacts with other network elements (e.g., data orchestration network elements, data agent network elements, core network elements, terminal equipment, access network equipment, data storage network elements, and trust anchors) through the network element.

[0212] In the network architectures shown in Figures 6a to 6c, service-oriented interfaces can be used to improve independence between network functions, achieve deployment flexibility and efficient scalability, and improve the development efficiency of new functions.

[0213] Referring to Figure 6d, the network architecture may include, but is not limited to, one or more of the following: a service request network element, a data orchestration network element, an access network domain data orchestration network element (RAN-DO), a CN domain data orchestration network element (CN-DO), and access network equipment. ( RAN ), core network elements, terminal equipment, trust anchors, and data storage network elements.

[0214] In the architecture shown in Figure 6d, data orchestration network elements are deployed hierarchically. The data orchestration network elements may manage RAN domain data orchestration network elements and CN domain data orchestration network elements. The RAN domain data orchestration network elements may interact directly with CN domain data orchestration network elements. The RAN domain data orchestration network elements may interact directly with access network equipment. The CN domain data orchestration network elements may interact directly with core network elements. The trust anchor may interact directly with any network element in the network architecture. The data storage network elements may interact directly with terminal equipment, access network equipment, and core network elements.

[0215] The network elements in the network architecture shown in FIG. 6d are directly interconnected, which allows the architecture to meet backward compatibility.

[0216] FIG. 6e illustrates a network architecture in which data orchestration network elements are deployed in a hierarchical manner, according to an embodiment of the present application.

[0217] Referring to Figure 6e, the network architecture may include, but is not limited to, one or more of the following: a service request network element, a data orchestration network element, an access network domain data orchestration network element (RAN-DO), a CN domain data orchestration network element (CN-DO), an access network domain data agent network element (RAN-DA), a terminal domain data agent network element (UE-DA), a core network domain data agent network element (CN-DA), and a standalone data agent network element (DA). Optionally, the network architecture may further include a trust anchor and a data storage network element.

[0218] In the architecture shown in Figure 6e, data orchestration network elements are deployed hierarchically. The data orchestration network element may manage RAN domain data orchestration network elements and CN domain data orchestration network elements. The RAN domain data orchestration network element may interact directly with the CN domain data orchestration network element. The RAN domain data orchestration network element may interact directly with the access network domain data agent network element, the terminal domain data agent network element (UE-DA), and the standalone data agent network element (not shown in Figure 6e). The CN domain data orchestration network element may interact directly with the core network domain data agent network element and the standalone data agent network element. Figure 6e uses an example in which the CN domain data orchestration network element interacts directly with the standalone data agent network element.

[0219] Optionally, one or more standalone data agent network elements may be present. For example, if one standalone data agent network element is present, the standalone data agent network element may interact directly with a RAN domain data orchestration network element or may interact directly with a CN domain data orchestration network element. For example, if multiple standalone data agent network elements are present, some of the standalone data agent network elements may interact directly with a RAN domain data orchestration network element, some of the standalone data agent network elements may interact directly with a CN domain data orchestration network element, or all of the multiple standalone data agent network elements may interact directly with a CN domain data orchestration network element, or all of the multiple standalone data agent network elements may interact directly with a RAN domain data orchestration network element. This is not a limitation of the present application.

[0220] Optionally, in the architecture shown in Figure 6e, the data orchestration network element may also be referred to as a cross-domain data orchestration network element, and the access network domain data orchestration network element (RAN-DO) and the core network domain data orchestration network element (CN-DO) may also be referred to collectively as domain data orchestration network elements. The access network domain data agent network element, terminal domain data agent network element, core network domain data agent network element, and standalone data agent network element may also be referred to collectively as domain data agent network elements.

[0221] Optionally, domain data agent network elements may be categorized into data agent network elements in a core network domain and data agent network elements in an access network domain. Data agent network elements in a core network domain may include, but are not limited to, one or more of the following: core network domain data agent network elements and standalone data agent network elements. Data agent network elements in an access network domain may include, but are not limited to, one or more of the following: access network domain data agent network elements, terminal domain data agent network elements, and standalone data agent network elements.

[0222] It should be noted that a domain data agent network element may implement the functionality of the data agent network element described in Figures 1 to 6d, and in this specification the data agent network element will be referred to simply as a domain data agent network element.

[0223] For example, a cross-domain data orchestration network element may be combined with a network management system (NMS) or implemented through the evolution of NMS functionality, a domain data orchestration network element may be combined with an element management system (EMS) or implemented through the evolution of EMS functionality, etc.

[0224] In the network architecture shown in Figure 6e, the cross-domain data orchestration network element and the domain data orchestration network element may perform automatic orchestration and configure corresponding operations for the domain data agent network element (a network element that can implement the functions of the data agent network element) to implement data service automation. For example, a series of functional actions may be performed by the data orchestration network element ( Cross-domain The service request is stored in the cross-domain data orchestration network element and / or the domain data orchestration network element. After receiving the service request, the cross-domain data orchestration network element coordinates the domain data agent network elements to implement end-to-end configuration of the data service, form a logical network topology, and thereby implement automation of data service provision.

[0225] The following describes the functions of the cross-domain data orchestration network element and the functions of the domain data orchestration network element.

[0226] For example, functions that may be implemented by a cross-domain data orchestration network element include, but are not limited to, one or more of the following: interfacing to applications, requirements translation, data protection, interfacing to trust anchors, and managing the lifecycle of data service tasks, e.g., assigning or deleting data service task IDs.

[0227] Requirements translation: The service request is translated into service requirements at the RAN-DO and CN-DO levels, the RAN-DO and CN-DO are selected, the required data type and data service type are selected, and the domain to which the data agent network element that will communicate directly with the service requester belongs is determined.

[0228] For example, data service types may include, but are not limited to, one or more of the following: raw data output, providing pre-processed data, data storage, data analysis, tracing data sources, data dictionary, data privacy and security, and data sharing or transaction.

[0229] Data Protection: See the functional description of the Data Orchestration Network Element in Figure 2. Details will not be repeated here.

[0230] For example, functions that may be implemented by a domain data orchestration network element include, but are not limited to, one or more of the following: data agent management, data service function reporting, data agent orchestration, data protection, and cross-domain next-hop data agent network element selection.

[0231] Data Agent Management: Manages registrations, deregistrations, and the like requested by domain data agent network elements, and receives data service capabilities, and the like reported by domain data agent network elements.

[0232] Data service function reporting: For example, a data service function of a data agent network element is sent to a data orchestration network element. As another example, statistics collection is performed on the received data service function of the domain data agent network element, and then the statistics are obtained and reported to the cross-domain data orchestration network element.

[0233] Data Agent Orchestration: Requirements from cross-domain data orchestration network elements are received, and the data agent network elements are coordinated based on the requirements and the data service capabilities of the data agent network elements to fulfill the service requirements, forming a dynamic logical network topology.

[0234] Data Protection: See the functional description of the Data Orchestration Network Element in Figure 2. Details will not be repeated here.

[0235] Cross-domain next-hop data agent network element selection: A domain data orchestration network element may select a data agent network element within one or more data agent network elements in its local domain that will interact with a data agent network element in another domain.

[0236] For example, the CN-DO may select a data agent network element (e.g., CN domain data agent network element 1) within one or more data agent network elements in the CN domain that interacts with a data agent network element in the access network domain, and the RAN-DO may select a data agent network element (e.g., RAN domain data agent network element 1) within one or more data agent network elements in the RAN domain that interacts with a data agent network element in the core network domain. The selected CN domain data agent network element 1 may interact directly with the RAN domain data agent network element 1, and another data agent network element in the CN domain may interact with another data agent network element in the RAN domain via the CN domain data agent network element 1 and the RAN domain data agent network element 1.

[0237] In the following, we describe the service-oriented interface in a scenario where data orchestration network elements are deployed hierarchically.

[0238] Service-oriented interface between a cross-domain data orchestration network element and a service request network element: The service-oriented interface may be used by the cross-domain data orchestration network element to receive service requests from the service request network element, to send information to the service request network element about data agent network elements that communicate directly with the service request network element, and the like.

[0239] Service-oriented interface between cross-domain data orchestration network elements and domain data orchestration network elements: The service-oriented interface may be used by the cross-domain data orchestration network element to send to the domain data orchestration network element a data service task identifier, a data service task / function in the local domain, and a notification indicating whether there are any data agent network elements in this domain that interact directly with the service request network element. This service-oriented interface may be used by the domain data orchestration network element to send to the cross-domain data orchestration network element statistical information about the data agent network elements in the local domain and the functions of selected domain data agent network elements that interact directly with the service request network element.

[0240] Service-oriented interface between domain data orchestration network elements: Between domain data orchestration network elements, information about cross-domain next-hop data agent network elements, for example addresses or identifiers of data agent network elements, is exchanged.

[0241] Service-oriented interface between domain data orchestration network elements and domain data agent network elements: A service-oriented interface may be used for interaction between domain data agent network elements and domain data orchestration network elements. For example, a service-oriented interface may be used by a domain data agent network element to request registration, deregistration, and the like from a domain data orchestration network element, and to receive data service capabilities reported by the domain data agent network element. This service-oriented interface may be used by a domain data agent network element to periodically report heartbeats to the domain data orchestration network element. This service-oriented interface may be used by a domain data orchestration network element to send a data service task identifier to the domain data agent network element and to assign the data service task, the operation to be performed (see the operation configuration information below for details), output data format requirements, data next-hop address, and the like to the domain data agent network element.

[0242] Service-oriented interface between cross-domain data orchestration network elements and trust anchors: The service-oriented interface can be used to verify the access rights of the service requesting network element to the relevant data required.

[0243] Service-oriented interface between domain data orchestration network elements and trust anchors: The service-oriented interface can be used to verify the access rights of domain data agent network elements to the relevant data.

[0244] It should be noted that the communication method provided in the embodiments of the present application can be applied to any two nodes shown in Figures 1 to 6e. For specific implementation, please refer to the following method embodiments. The details will not be described again in this specification.

[0245] It should be noted that the solutions in the embodiments of the present application may further be applied to another communication system, and the corresponding names may be replaced with the names of the corresponding functions in the other communication system.

[0246] 7 illustrates a configuration of a communication device 700 that may be configured to perform a communication method according to an embodiment of the present application. The communication device 700 may be a data orchestration network element, a domain data orchestration network element, a domain data agent network element, a service request network element, or a trust anchor, or may be a chip or another component or assembly used within a data orchestration network element, a domain data orchestration network element, a domain data agent network element, a service request network element, or a trust anchor.

[0247] 7, the communications device 700 may include a processor 701. Optionally, the communications device 700 may further include one or more of a memory 702 and a transceiver 703. The processor 701 and the one or more of the memory 702 and the transceiver 703 may be coupled, such as connected through a communications bus, or the processor 701 may be used independently.

[0248] Each component of the communication device 700 is described in more detail below with reference to FIG.

[0249] Processor 701 is the control center of communication device 700 and may be a single processor or a composite of multiple processing elements. For example, processor 701 may be one or more central processing units (CPUs), or may be an application-specific integrated circuit (ASIC), or may be configured as one or more integrated circuits implementing embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0250] The processor 701 may execute or perform software programs stored in the memory 702 and access data stored in the memory 702 to perform various functions in the communication device 700 .

[0251] In a specific implementation, in one embodiment, the processor 701 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.

[0252] In a specific implementation, in one embodiment, communications device 700 may alternatively include multiple processors, such as processor 701 and processor 704 shown in Figure 7. Each of the processors may be a single-core processor (single CPU) or a multi-core processor (multiple CPUs). A processor herein may be one or more communications devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions, etc.).

[0253] Memory 702 may be read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, or random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, or may be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disc storage (compact optical disc, laser disc, optical disc, digital versatile disc, Blu-ray (registered trademark) The memory 702 may be, but is not limited to, an optical disk storage (including a disk, or the like), a magnetic disk storage medium, or another magnetic storage communication device, or any other medium that can be configured to carry or store expected program code in the form of instructions or data structures and that can be accessed by a computer. The memory 702 may be integrated with the processor 701 or may exist separately, and is coupled to the processor 701 through an input / output port (not shown in FIG. 7) of the communication device 700. This is particularly limiting in this embodiment of the present application.

[0254] The memory 702 is configured to store a software program for implementing the solution of the present application, and the processor 701 controls its execution. For specific implementations of the above, please refer to the following method embodiments. Details will not be described again in this specification.

[0255] The transceiver 703 is configured to communicate with another communication device. For example, if the communication device 700 is a data orchestration network element, the transceiver 703 may be configured to communicate with a domain data orchestration network element, a service request network element, a trust anchor, and / or the like. As another example, if the communication device 700 is a domain data orchestration network element, the transceiver 703 may be configured to communicate with a data orchestration network element, a domain data agent network element, a service request network element, a trust anchor, and / or the like. As another example, if the communication device 700 is a domain data agent network element, the transceiver 703 may be configured to communicate with a domain data orchestration network element, a service request network element, a trust anchor, and / or the like. As another example, if the communication device 700 is a service request network element, the transceiver 703 may be configured to communicate with a data orchestration network element, a domain data orchestration network element, a domain data agent network element, a trust anchor, and / or the like. Furthermore, the transceiver 703 may include a receiver and a transmitter (not shown separately in FIG. 7 ). The receiver is configured to implement receiving functionality, and the transmitter is configured to implement transmitting functionality. The transceiver 703 may be integrated with the processor 701 or may exist independently, and may be coupled to the processor 701 through an input / output port (not shown in FIG. 7 ) of the communication device 700. This is not particularly limiting in this embodiment of the present application.

[0256] It should be noted that the configuration of communications device 700 shown in Figure 7 does not constitute a limitation on the communications device. An actual communications device may include more or fewer components than those shown in the figure, may combine some components, or may have a different component arrangement.

[0257] Hereinafter, a communication method according to an embodiment of the present application will be described in detail with reference to FIGS. 8A to 8C.

[0258] For example, Figures 8A to 8C are schematic flow charts illustrating a communication method according to one embodiment of the present application.

[0259] The methods illustrated in Figures 8A to 8C are applicable to a scenario in which data orchestration network elements are deployed hierarchically. The data orchestration network elements may be referred to as cross-domain data orchestration network elements. The first domain data orchestration network element and the second domain data orchestration network element may be data orchestration network elements in different domains. For example, the first domain data orchestration network element may be a data orchestration network element in the core network domain, and the second domain data orchestration network element may be a data orchestration network element in the access network domain.

[0260] The first domain data orchestration network element may coordinate and manage data agent network elements in the first domain. For example, the data agent network element in the first domain may be a data agent network element in the core network domain. The core network domain data agent network element may include, but is not limited to, one or more of the following: a core network domain data agent network element and a standalone data agent network element. The second domain data orchestration network element may coordinate and manage data agent network elements in the second domain. For example, the data agent network element in the second domain may be a data agent network element in the access network domain. The data agent network element in the access network domain may include, but is not limited to, one or more of the following: an access network domain data agent network element, an end domain data agent network element, and a standalone data agent network element.

[0261] It should be noted that the functions of the first domain data orchestration network element are similar to those of the second domain data orchestration network element. The following description mainly uses the first domain data orchestration network element or the domain data orchestration network element (which may represent the first domain data orchestration network element or the second domain data orchestration network element) as an example. For the implementation of the functions of the second domain data orchestration network element, please refer to the specific implementation of the functions of the first domain data orchestration network element.

[0262] The functions of the data agent network element in the first domain are similar to those of the data agent network element in the second domain. The following mainly uses the data agent network element in the first domain or the domain data agent network element (which may represent the data agent network element in the first domain or the data agent network element in the second domain) as an example. For the implementation of the functions of the data agent network element in the second domain, please refer to the specific implementation of the functions of the data agent network element in the first domain.

[0263] In the following embodiments, the first domain data agent network element represents any one domain data agent network element, for example, any data agent network element in the first domain or any data agent network element in the second domain. Similarly, the second domain data agent network element represents any one domain data agent network element, and the third domain data agent network element represents any one domain data agent network element. The first domain data agent network element, the second domain data agent network element, and the third domain data agent network element are different from each other.

[0264] As shown in FIGS. 8A to 8C, the communication method includes the following steps.

[0265] S801: A service request network element sends a first service request message to a data orchestration network element, and in response, the data orchestration network element receives the first service request message from the service request network element.

[0266] Optionally, the first service request message may be for requesting an application service or a service service.

[0267] Optionally, the service request network element may be an application, an application server, a network service network element, or the like.

[0268] In this embodiment of the present application, the application service may be a service requested by an application or an application server, and the service may be a service requested by a network element. In various scenarios, the service requested by using the first service request message may be different.

[0269] For example, the first service request message may be to request one or more of the following services, but is not limited to: a service related to network data, a service related to user data, a service related to artificial intelligence model data, and a service related to Internet of Things data.

[0270] Optionally, the network data may include, but is not limited to, one or more of the following: logs (e.g., debug logs, security logs, or call history records (CHR) logs), alarms, traffic statistics, configuration data, minimization of drive test (MDT) data, user session information, integrated sensing and communication (ISAC) data, digital twin network data, network metadata, network status, and network behavior.

[0271] For example, network data may include data collected by access network equipment, data collected by terminal equipment, and the like.

[0272] Optionally, the user data may include, but is not limited to, one or more of the following: user subscription information, such as a user profile.

[0273] Optionally, the Internet of Things data may include, but is not limited to, one or more of the following: environmental data, sensor-type data, and measurement data at the Internet of Things terminals.

[0274] For example, Internet of Things data may include data collected by SIoT terminal devices and data collected by non-SIoT terminal devices by using an Internet of Things gateway.

[0275] Optionally, the data of the artificial intelligence AI model may include, but is not limited to, one or more of the following: a task-corresponding training dataset, a task-corresponding test dataset, local model data / global model data, and AI metadata.

[0276] Optionally, data may be categorized along multiple dimensions, such as data type, data source, data consumer, or as orthogonal as possible.

[0277] In this way, there are various data sources and various data types in the network, so the processing procedures for the data are significantly different. The data is properly classified, so that the processing procedures can be simplified, the system complexity can be reduced, and data services of various data types can be supported.

[0278] It should be noted that the present application does not limit the classification of data, and data may be classified into more or fewer types, or data may be classified into types from a different perspective, or data may not be classified into types.

[0279] For example, the network service· The network element sends a first service request message to a data orchestration network element, where the first service request message is to request access to user subscription data in the data agent network element.

[0280] For example, an application belonging to an operator and used for network planning and optimization (which may be simply referred to as a network planning and optimization application) sends a first service request message to a data orchestration network element, where the first service request message is to request training of a federated learning model, where the federated learning model is used to predict service quality.

[0281] For example, a network planning and optimization application may send a first service request message to a data orchestration network element, where the first service request message is to request a prediction of quality of service for region A.

[0282] In some embodiments, the requirement to predict the service quality of region A can be decomposed into the following requirements: a requirement to train a federated learning model (requirement 1), and a requirement to predict the service quality of region A by using the (trained) federated learning model (requirement 2).

[0283] Similarly, the process of predicting the service quality of region A can be decomposed into the following phases: training a federated learning model (Phase 1); and predicting the service quality of region A by using the (trained) federated learning model (Phase 2). Thus, after receiving a request to predict the service quality of region A, if the service request network element locally stores the required federated learning model, Phase 2 can be executed directly. Alternatively, if the service request network element does not locally store the required federated learning model, Phase 2 is executed after Phase 1 is executed.

[0284] Phase 1: A request to train a federated learning model is converted into corresponding requirement information. The data orchestration network element coordinates the domain data orchestration network elements to select domain data agent network elements participating in the current data service based on the data service capabilities of the domain data agent network elements to form a dynamic logical network topology. From the domain data agent network elements participating in the current data service, a domain data agent network element with powerful computing capabilities (e.g., domain data agent network element 1) is selected as the server side to train the federated learning model. Another domain data agent network element (e.g., a domain data agent network element other than domain data agent network element 1 among the domain data agent network elements participating in the current data service) acts as the client side and provides data used to train the federated learning model. After multiple training rounds, a federated learning model is generated and sent by the domain data agent network element (e.g., domain data agent network element 1 as the server side DA) to the service request network element, or stored in the domain data agent network element or DSF as needed.

[0285] It should be noted that Phase 1 is applicable to a scenario in which a service requesting network element requests training of a federated learning model.

[0286] Phase 2: By using a federated learning model, the request to predict the service quality of region A in a future time period is converted into corresponding requirement information. The data orchestration network element coordinates the domain data agent network elements to select domain data agent network elements participating in the current data service based on the data service capabilities of the domain data agent network elements to form a dynamic logical network topology. From the domain data agent network elements participating in the current data service, a domain data agent network element with powerful computing capabilities (e.g., domain data agent network element 1) is selected to predict the service quality. Another domain data agent network element (e.g., a domain data agent network element other than domain data agent network element 1 among the domain data agent network elements participating in the current data service) may provide data (e.g., real-time network data) for predicting the service quality to domain data agent network element 1 or perform some operations on the data (e.g., processing such as desensitization). The domain data agent network element 1 performs inference by using the federated learning model and data (raw data or intermediate data) to obtain a prediction result of service quality and sends the result to the service request network element.

[0287] It should be noted that the domain data agent network element 1 may send the acquired intermediate data to the service request network element, and the service request network element performs inference by using the federated learning model and the intermediate data to acquire a predicted result of service quality. The federated learning model in the service request network element may be acquired from the domain data agent network element or may be pre-configured. This is not limited in the present application.

[0288] For example, in an abnormal behavior detection scenario for an IoT terminal device, an application network element or a network service network element sends a first service request message to a data orchestration network element to request Internet of Things data, intermediate data obtained by processing (e.g., preprocessing or analysis) the Internet of Things data, abnormal behavior detection results for the IoT terminal device, or the like.

[0289] In some embodiments, the first service request message may be a requirement that is embedded according to a standard template.

[0290] For example, a standard template may be a service level agreement.

[0291] S802: The data orchestration network element determines first requirement information and second requirement information based on the requirement information, the first data service capability information, and the second data service capability information.

[0292] For example, the requirement information may be a service requirement relating to the first data and determined based on the service requested by using the first service request message.

[0293] Optionally, the initial data may include data collected from a mobile communication network and / or synthetic data.

[0294] For example, the initial data may include, but is not limited to, one or more of the following: data on the terminal equipment side, data of each function node on the access network equipment side, data of each function node on the transport network side, data of each function node on the core network side, data of each function node of OAM, and combined data.

[0295] For example, synthetic data may be artificially synthesized data.

[0296] For example, a face may be generated through adversarial learning, and the face data may be considered synthetic data.

[0297] For example, synthetic data may be used if the amount of data of a particular type is low, such as if the amount of some anomalous data is low.

[0298] Optionally, the synthetic data may be used to train an artificial intelligence model, or the like.

[0299] For example, the initial data may be categorized, and the initial data may include, but is not limited to, one or more of the following: network data, user data, artificial intelligence model data, and Internet of Things data.

[0300] Optionally, data may be categorized along multiple dimensions, such as data type, data source, data consumer, or as orthogonal as possible.

[0301] It should be noted that in the present application, the classification of the initial data is not limited, and the initial data may be classified into more or fewer types, or the initial data may be classified into types from a different perspective, or the initial data may not be classified into types.

[0302] For example, the first data service capability information corresponds to a first domain data orchestration network element, and the second data service capability information corresponds to a second domain data orchestration network element.

[0303] In some embodiments, the first data service capability information may be determined based on one or more portions of the domain data service capability information.

[0304] In some embodiments, the second data service capability information may be determined based on one or more portions of the domain data service capability information.

[0305] For example, one or more portions of domain data service capability information may correspond one-to-one with one or more domain data agent network elements.

[0306] Optionally, the one or more domain data service capability information portions corresponding to the first data service capability information may correspond to one or more domain data agent network elements in the first domain, respectively.

[0307] Optionally, the one or more domain data service capability information portions corresponding to the second data service capability information may correspond to one or more domain data agent network elements in the second domain, respectively.

[0308] For example, assuming that the first domain data orchestration network element is a core network domain data orchestration network element and the second domain data orchestration network element is an access network domain data orchestration network element, the first data service capability information may be determined based on domain data service capability information corresponding to one or more domain data agent network elements in the core network, respectively, and the second data service capability information may be determined based on domain data service capability information corresponding to one or more data agent network elements in the access network domain, respectively.

[0309] In some embodiments, the first data service capability information may be determined by a core network domain data orchestration network element based on domain data service capability information corresponding to one or more data agent network elements, respectively, within the core network domain.

[0310] For example, the first data service capability information may be obtained by a core network domain data orchestration network element by collecting statistical information about the domain data service capability information of domain data agent network elements in the local domain.

[0311] In some embodiments, the second data service capability information may be determined by the access network domain data orchestration network element based on domain data service capability information corresponding to one or more data agent network elements, respectively, within the access network domain.

[0312] For example, the second data service capability information may be obtained by the access network domain data orchestration network element by collecting statistical information about the domain data service capability information of domain data agent network elements in the local domain.

[0313] In a possible design, the domain data service capability information of any one of the one or more domain data agent network elements may include, but is not limited to, one or more of the following: an identifier of any one of the domain data agent network elements, location information of any one of the domain data agent network elements, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0314] Optionally, there may be a correspondence between the domain data service capability information and the domain data agent network element identifier.

[0315] In this way, based on the correspondence between the domain data service capability information and the domain data agent network element identifier, the particular domain data agent network element to which the domain data service capability information belongs can be recognized.

[0316] Optionally, the location information may be information regarding a geographic location, where the location information may include longitude and latitude, and the like.

[0317] Optionally, the data collection function may include types of data that may be collected, which may include, but are not limited to, one or more of the following: network data, user data, Internet of Things data, and artificial intelligence model data.

[0318] Optionally, the data pre-processing function may include supported pre-processing methods, such as field extraction, format conversion, removal of redundant data, compression, and merging of the original data.

[0319] Optionally, the data storage capabilities may include, but are not limited to, one or more of the following: data storage capacity, encryption algorithm for storing data, and storage method.

[0320] Optionally, the data reporting capabilities may include, but are not limited to, one or more of the following: minimum reporting period, amount of data reported at one time, maximum amount of data reported, whether file uploads are supported, and whether streaming data is supported.

[0321] Optionally, the data analysis capabilities may include, but are not limited to, one or more of the following: supported analysis tasks, whether AI training is supported, and whether AI inference is supported.

[0322] Optionally, the ability to interact with the service request network element may include, but is not limited to, the ability to provide application programming interface services.

[0323] Optionally, the data protection features may include, but are not limited to, one or more of the following: supported data protection techniques, such as k-anonymity, l-diversity, differential privacy, homomorphic encryption, and private multi-party computation.

[0324] Optionally, the data compression functionality may include, but is not limited to, one or more of the following: supported data compression algorithms, such as Huffman Coding and Arithmetic Coding.

[0325] The implementation of data collection function, data preprocessing function, data storage function, data reporting function, data analysis function, function to interact with service request network elements, data protection function, and data compression function is shown in Fig. 3 It should be noted that it is necessary to further refer to the description of the functions of the data agent network element in. The fact that the data agent network element has the corresponding function may indicate that the data agent network element has the corresponding function.

[0326] For example, the first requirement information may be a service requirement related to the first data and corresponding to a first domain data orchestration network element, and the second requirement information may be a service requirement related to the first data and corresponding to a second domain data orchestration network element.

[0327] In other words, the data orchestration network element may decompose the requirement information into first requirement information and second requirement information based on the first data service capability information and the second data service capability information.

[0328] It should be noted that whether the requirement information is decomposed into first requirement information and second requirement information (used as an example for the explanation in Figures 8A to 8C) can be adjusted based on actual circumstances.

[0329] For example, if the first data service capability information does not support implementation of some or all of the service requirements indicated by the requirement information, the data orchestration network element determines second requirement information based on the requirement information, the first data service capability information, and the second data service capability information. For example, if the second data service capability information does not support implementation of some or all of the service requirements indicated by the requirement information, the data orchestration network element determines first requirement information based on the requirement information, the first data service capability information, and the second data service capability information.

[0330] In a possible design method, the requirements information may include, but is not limited to, one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0331] In some embodiments, the first requirements information may include, but is not limited to, one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0332] In some embodiments, the second requirements information may include, but is not limited to, one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0333] Optionally, the requirements information may correspond to a data service task identifier (DSID).

[0334] For example, the data service task identifier may identify the data service task corresponding to the first service request message.

[0335] Optionally, the data orchestration network element may perform a translation of requirements for the requested service by using the first service request message, where the translation (or mapping) is the service requirements to the capabilities of the domain data agent network element.

[0336] For example, assuming that the first service request message is to request predicting the service quality of region A and the data orchestration network element performs requirement transformation, the obtained requirement information may include: region A, data collection, data preprocessing, data analysis, and interaction with the service request network element.

[0337] In some embodiments, the method provided in this embodiment of the present application may further include: the data orchestration network element determining first indication information.

[0338] Optionally, the first indication information may indicate that the domain data agent network element that communicates directly with the service request network element is a data agent network element in the first domain or a data agent network element in the second domain.

[0339] For example, the first indication information may indicate that the domain data agent network element that communicates directly with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0340] Optionally, the first indication information may be determined based on the first data service capability information and the second data service capability information.

[0341] For example, the data orchestration network element may select a domain to which a domain data agent network element that communicates directly with the service requesting network element belongs based on the capabilities to interact with the service requesting network element in the first data service capability information and the second data service capability information.

[0342] It should be noted that the data orchestration network element determining the first instruction information and the data orchestration network element determining the first requirement information and the second requirement information may be performed in the same step or separately, which is not limited in the present application.

[0343] Using a scenario requiring training of a federated learning model (e.g., Phase 1 of S802) as an example, the following describes how the data orchestration network element determines the first requirement information and the second requirement information.

[0344] For example, assuming that the first service request message is to request training of an AI model and the data orchestration network element performs requirement transformation, the obtained requirement information may include the following: domain A, data collection, data preprocessing, data analysis, and interaction with the service request network element.

[0345] Assume that the first data service capability information 1 includes the following: area A, data preprocessing supported by all data agent network elements in the first domain, data storage supported by most data agent network elements in the first domain, AI training and AI inference supported by most data agent network elements in the first domain, interaction with service request network elements supported by most data agent network elements in the first domain, and data collection supported by most data agent network elements in the first domain.

[0346] Assume that the second data service function information 1 includes the following: area A, data preprocessing supported by all data agent network elements in the second domain, AI training and AI inference not supported by most data agent network elements in the second domain, interaction with service request network elements not supported by most data agent network elements in the second domain, and data collection supported by most data agent network elements in the second domain.

[0347] The data orchestration network element determines, based on the requirements information, the first data service function information 1, and the second data service function information 1, that the first requirements information 1 includes area A, data preprocessing, and AI training, and that the second requirements information 1 includes area A and data collection.

[0348] It should be noted that the above is just an example provided in the present application. In a scenario requiring training of a federated learning model, the requirement information, the first data service function information 1, the second data service function information 1, the first requirement information 1, and the second requirement information 1 is , are not limited in this application and may vary based on actual scenario requirements.

[0349] In a possible design manner, step S802 may include: if the service request network element has access to the first data, the data orchestration network element determines first requirement information and second requirement information based on the requirement information, the first data service capability information, and the second data service capability information.

[0350] In this way, the first requirement information and the second requirement information are determined only when the service requesting network element has access to the first data, or the first requirement information and the second requirement information are not determined when the service requesting network element does not have access to the first data, thereby implementing a trusted service requirement for the data.

[0351] In some embodiments, if the service request network element has access to the first data, the data orchestration network element assigns a data service task identifier to the data service task corresponding to the first service request message, or if the service request network element does not have access to the first data, the data orchestration network element does not assign a data service task identifier to the data service task corresponding to the first service request message, thereby implementing a trusted service requirement for data.

[0352] In some embodiments, the method provided in this embodiment of the present application may further include the following steps: S810: The trust anchor sends a second validation response message to the data orchestration network element. In response, the data orchestration network element receives the second validation response message from the trust anchor.

[0353] Optionally, the second validation response message may indicate that the service requesting network element has access to the original data, or may indicate that the service requesting network element does not have access to the original data.

[0354] In other words, whether the service requesting network element has access to the initial data can be obtained by the data orchestration network element from the trust anchor.

[0355] It should be noted that in this embodiment of the present application, the execution order of S810 is not limited. For example, S810 may be executed before S802.

[0356] In some embodiments, the method provided in this embodiment of the present application may further include the following steps: S811: The data orchestration network element sends a second validation request message to the trust anchor. In response, the trust anchor receives the second validation request message from the data orchestration network element.

[0357] Optionally, the second verification request message may be for requesting verification of whether the service requesting network element has access rights to the first data.

[0358] It should be noted that S811 may be executed before S810.

[0359] In some embodiments, the method provided in this embodiment of the present application may further include the following steps: S812: The first domain data orchestration network element sends first data service capability information to the data orchestration network element. In response, the data orchestration network element receives the first data service capability information from the first domain data orchestration network element.

[0360] In this way, the first domain data orchestration network element may collect statistical information about the domain data service capability information of the domain data agent network elements in the local domain to obtain first data service capability information, and send the first data service capability information to the data orchestration network element.

[0361] In some embodiments, the method provided in this embodiment of the present application may further include the following steps: S813: The second domain data orchestration network element sends second data service capability information to the data orchestration network element. In response, the data orchestration network element receives the second data service capability information from the second domain data orchestration network element.

[0362] In this way, the second domain data orchestration network element may collect statistical information on the domain data service function information of the domain data agent network elements in the local domain to obtain second data service function information, and send the second data service function information to the data orchestration network element.

[0363] It should be noted that the order of S812 and S813 is not limited in the present application.

[0364] In some embodiments, the method provided in this embodiment of the present application may further include: the first domain data agent network element sending domain data service capability information to the domain data orchestration network element, and in response, the domain data orchestration network element receiving the domain data service capability information from the first domain data agent network element.

[0365] For example, the first domain data agent network element may represent any one of the domain data agent network elements, and the domain data agent network element may transmit the domain data service capability information of the domain data agent network element to the corresponding domain data orchestration network element.

[0366] For example, the method provided in this embodiment of the present application may further include the following steps: S814: The data agent network element in the first domain sends domain data service capability information to the first domain data orchestration network element. In response, the first domain data orchestration network element receives domain data service capability information from the data agent network element in the first domain.

[0367] In this manner, the core network domain data agent network element and / or the standalone data agent network element may transmit their respective domain data service capability information to the core network domain data orchestration network element.

[0368] For example, the method provided in this embodiment of the present application may further include the following steps: S815: The second domain data agent network element sends domain data service capability information to the second domain data orchestration network element, and in response, the second domain data orchestration network element receives domain data service capability information from the second domain data agent network element.

[0369] In this manner, an access network domain data agent network element, a terminal domain data agent network element, and / or a standalone data agent network element may transmit their respective domain data service capability information to an access network domain data orchestration network element.

[0370] It should be noted that the order of S814 and S815 is not limited in the present application.

[0371] In a possible design, the method provided in this embodiment of the present application may further include: the first domain data agent network element registering with the domain data orchestration network element.

[0372] It should be noted that the first domain data agent network element registering with the domain data orchestration network element may be performed before or when the first domain data agent network element sends domain data service capability information to the first domain data orchestration network element, which is not a limitation of the present application.

[0373] S803a: The data orchestration network element sends first requirement information to a first domain data orchestration network element, and in response, the first domain data orchestration network element receives the first requirement information from the data orchestration network element.

[0374] S803b: The data orchestration network element sends the second requirements information to the second domain data orchestration network element, and in response, the second domain data orchestration network element receives the second requirements information from the data orchestration network element.

[0375] In this manner, the data orchestration network element separately transmits the first requirement information and the second requirement information to data orchestration network elements in the corresponding domains.

[0376] It should be noted that the order of S803a and S803b is not limited in the present application.

[0377] Optionally, the method provided in this embodiment of the present application may further include: the data orchestration network element sending first indication information to the domain data orchestration network element, and in response, the domain data orchestration network element receiving the first indication information from the data orchestration network element.

[0378] In this way, the data orchestration network element may inform the core network domain data orchestration network element and / or the access network domain data orchestration network element of the domain to which the domain data agent network element that communicates directly with the service requesting network element belongs.

[0379] For example, the method provided in this embodiment of the present application may further include the following steps: S816a: The data orchestration network element sends first instruction information to the first domain data orchestration network element, and in response, the first domain data orchestration network element receives the first instruction information from the data orchestration network element.

[0380] For example, the first indication information may indicate that the domain data agent network element that communicates directly with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0381] Alternatively, for example, the first indication information may indicate whether a domain data agent network element that communicates directly with the service request network element is within the domain to which the first domain data orchestration network element belongs.

[0382] For example, the method provided in this embodiment of the present application may further include the following step: S816b: The data orchestration network element sends first instruction information to the second domain data orchestration network element, and in response, the second domain data orchestration network element receives the first instruction information from the data orchestration network element.

[0383] For example, the first indication information may indicate that the domain data agent network element that communicates directly with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0384] Alternatively, for example, the first indication information may indicate whether a domain data agent network element that communicates directly with the service request network element is within the domain to which the second domain data orchestration network element belongs.

[0385] In a possible design, the method provided in this embodiment of the present application may further include: the data orchestration network element sending updated information regarding the data security and privacy technology repository and / or updated information regarding the analysis tool repository to one or more of the at least one domain data agent network elements, and in response, the one or more of the at least one domain data agent network elements receiving the updated information regarding the data security and privacy technology repository and / or updated information regarding the analysis tool repository from the data orchestration network element.

[0386] Optionally, the information regarding the data security and privacy technology repository may include, but is not limited to, one or more of the following: a data security and privacy technology repository identifier, a data security and privacy technology repository index, and a data security and privacy technology repository.

[0387] Optionally, the information about the analysis tool repository may include, but is not limited to, one or more of the following: an identifier of the analysis tool repository, an index of the analysis tool repository, and the analysis tool repository itself.

[0388] In other words, when the data security and privacy protection technology repository, the analysis tool repository, and the like are updated, the data orchestration network element may promote the updated information or any of the data security and privacy protection technology repository, the analysis tool repository, and the like to the core network domain data agent network element, the access network domain data agent network element, the terminal domain data agent network element, and / or the standalone data agent network element, thereby achieving data security protection, data privacy protection, and the like.

[0389] It should be noted that the sending of the first requirements information by the data orchestration network element to the domain data agent network element, the sending of the first instruction information, and the sending of the update information regarding the data security and privacy protection technology repository and / or the update information regarding the analysis tool repository may be performed in the same step or separately, which is not limited in the present application.

[0390] Optionally, the data orchestration network element may send updates regarding the data security and privacy protection technology repository and / or updates regarding the analysis tool repository to the domain data agent network element directly or via the domain data orchestration network element, which is not limited in this application.

[0391] For example, this embodiment of the present application may further include the following step: Step a: The domain data orchestration network element determines at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information (or the second requirements information) and one or more portions of the domain data service capability information. For example, the domain data orchestration network elements may include a first domain data orchestration network element and a second domain data orchestration network element. Both the first domain data orchestration network element and the second domain data orchestration network element may perform step a. For details, see the following descriptions of S804a and S804b.

[0392] For example, one or more portions of domain data service capability information have a one-to-one correspondence with one or more domain data agent network elements.

[0393] For example, assuming that the domain data orchestration network element is a first domain data orchestration network element, the one or more portions of the domain data service capability information may correspond to one or more data agent network elements in the first domain, respectively. For details, see the description below in S804a.

[0394] For example, assuming that the domain data orchestration network element is a second domain data orchestration network element, one or more portions of the domain data service capability information may correspond to one or more data agent network elements in the second domain, respectively. For details, see the description below in S804b.

[0395] In a possible design scheme, step a may include the following: step 1 and step 2.

[0396] Step 1: The domain data orchestration network element determines at least one domain data agent network element based on the first requirements information (or the second requirements information) and one or more portions of the domain data service capability information.

[0397] Step 2: If any one of the at least one domain data agent network elements has access to the first data, the domain data orchestration network element determines operation configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirements information (or the second requirements information) and one or more portions of the domain data service capability information.

[0398] In this way, the domain data agent network elements participating in the data service can be first determined, and then, if it is determined that the domain data agent network elements have access to the first data, the corresponding operational configuration information is determined. Alternatively, if it is determined that the domain data agent network elements do not have access to the first data, the corresponding operational configuration information is not determined. This allows for the implementation of a trusted data service.

[0399] S804a: The first domain data orchestration network element determines, based on the first requirements information and one or more portions of the domain data service capability information, at least one data agent network element in the first domain and operation configuration information corresponding to each of the at least one data agent network element in the first domain.

[0400] For example, one or more portions of domain data service capability information may each correspond to one or more data agent network elements within the first domain.

[0401] For example, take an example where the multiple parts of domain data service function information include domain data service function information 1, domain data service function information 2, and domain data service function information 3. Domain data service function information 1 corresponds to domain data agent network element 1, domain data service function information 2 corresponds to domain data agent network element 2, and domain data service function information 3 corresponds to domain data agent network element 3.

[0402] For example, domain data agent network element 1 to domain data agent network element 3 may be a mobility management network element, a session management network element, and a policy control network element, respectively.

[0403] For example, the at least one data agent network element in the first domain may be at least one of one or more data agent network elements in the first domain.

[0404] For example, the data orchestration network element determines the domain data agent network elements participating in the current data service from domain data agent network element 1, domain data agent network element 2, and domain data agent network element 3 based on the requirement information, domain data service function information 1, domain data service function information 2, and domain data service function information 3, for example, selects domain data agent network element 1 and domain data agent network element 2 to participate in the current data service, and determines operation configuration information corresponding to domain data agent network element 1 and domain data agent network element 2, respectively.

[0405] For example, the operation configuration information of any one of at least one data agent network element in the first domain may indicate an operation to be performed by any one data agent network element in the first domain on the first data.

[0406] For example, the operation configuration information corresponding to domain data agent network element 1 indicates an operation to be performed by domain data agent network element 1 on the initial data or data generated based on the initial data. The operation configuration information corresponding to domain data agent network element 2 indicates an operation to be performed by domain data agent network element 2 on the initial data or data generated based on the initial data.

[0407] For example, the first requirements information corresponds to at least one of the portions of one or more domain data service capability information.

[0408] For example, the operation configuration information may indicate an operation to be performed by a domain data agent network element on the initial data.

[0409] In this manner, the first domain data agent network element determines the data agent network elements in the first domain participating in the current data service based on the first requirements information and at least a portion of the data service capability information in the first domain, where the data service capabilities of the selected data agent network elements in the first domain must be capable of satisfying the service requirements in the first requirements information, and the selected data agent network element in the first domain and the selected data agent network element in the second domain (see S804b below) can respectively perform the operations indicated by their respective operation configuration information, thereby implementing the data service.

[0410] In some embodiments, the operations indicated by the operational configuration information may include, but are not limited to, one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with a service request network element.

[0411] It should be noted that the operations indicated by operation configuration information in this application are different from general encoding / decoding, modulation / demodulation, and rate matching.

[0412] The implementation of these operations, such as data collection, data preprocessing, data storage, data analysis, service request interaction with network elements, and data protection, is shown in Fig. 3 It should be noted that the description of the functions of the data agent network element in the above and the description of the domain data service function information in this application need to be referred to. The details will not be described again in this specification.

[0413] In a possible design scheme, S804a may include step 3 and step 4.

[0414] Step 3: The first domain data orchestration network element determines at least one data agent network element in the first domain based on the first requirements information and the one or more portions of the domain data service capability information.

[0415] Step 4: If any one of the at least one data agent network elements in the first domain has access to the first data, the first domain data orchestration network element determines operation configuration information corresponding to any one of the at least one data agent network elements in the first domain based on the first requirements information and one or more portions of the domain data service capability information.

[0416] In this way, a data agent network element in a first domain participating in a data service can be first determined, and then, if it is determined that the domain data agent network element has access to the first data, corresponding operation configuration information is determined. Alternatively, if it is determined that the domain data agent network element does not have access to the first data, corresponding operation configuration information is not determined. This allows a trusted data service to be implemented.

[0417] In some embodiments, the method provided in this embodiment of the present application may further include: the first domain data orchestration network element determining the first communication information.

[0418] In some embodiments, if the first indication information indicates that the domain data agent network element that communicates directly with the service request network element is a data agent network element in the first domain, the first domain data orchestration network element determines the first communication information.

[0419] Optionally, the first communication information may indicate information regarding a domain data agent network element within at least one data agent network element in the first domain that communicates directly with the service request network element.

[0420] For example, assuming that the domain data agent network element that directly communicates with the service requesting network element is domain data agent network element 1, the first communication information may include, but is not limited to, one or more of the following: an address of the domain data agent network element 1, an identifier of the domain data agent network element 1, and an index of the domain data agent network element 1.

[0421] Optionally, the first communication information may be determined based on domain data service capability information of at least one data agent network element in the first domain.

[0422] For example, a data agent network element in a first domain having the capability to interact with a service request network element is selected from at least one data agent network element in the first domain as the domain data agent network element that communicates directly with the service request network element.

[0423] In other words, the first domain data orchestration network element may select a domain data agent network element that communicates directly with the service requesting network element from the determined data agent network elements in the first domain that are participating in the current data service.

[0424] Using a scenario requiring training of a federated learning model (e.g., phase 1 in S802) as an example, the following describes how a first domain data orchestration network element determines the data agent network elements in the first domain that are participating in the current data service and the corresponding operational configuration information for the data agent network elements in the first domain.

[0425] For example, assume that the first requirement information 1 includes the following: Area A, data preprocessing, and AI training.

[0426] The data orchestration network element determines the domain data agent network elements participating in the current data service from the domain data agent network element 1, the domain data agent network element 2, and the domain data agent network element 3 based on the first requirement information 1, the domain data service function information 1, the domain data service function information 2, and the domain data service function information 3. The domain data service function information 1 to the domain data agent network element 3 correspond to the domain data agent network element 1 to the domain data agent network element 3, respectively.

[0427] It is assumed that the domain data service capability information 1 includes the following: domain A, supported data preprocessing, supported data storage, supported AI training and AI inference, supported interaction with service request network elements, and supported data collection.

[0428] It is assumed that the domain data service capability information 2 includes the following: domain A, supported data preprocessing, supported AI training and AI inference, unsupported interactions with service request network elements, and supported data collection.

[0429] The domain data service capability information 3 is assumed to include the following: B , supported data preprocessing, supported data storage, unsupported AI training and AI inference, supported interaction with service request network elements, and supported data collection.

[0430] The first domain data orchestration network element may determine, based on the first requirements information 1, the domain data service function information 1, the domain data service function information 2, and the domain data service function information 3, that the domain data agent network element 1 and the domain data agent network element 2 can jointly implement the service requirements in the first requirements information 1. First, the geographic location of the data agent network element 3 is area B, not area A. Second, the data agent network element 3 does not support AI training and AI inference, and the data agent network element 3 cannot participate in training of the AI ​​model.

[0431] The first domain data orchestration network element determines operation configuration information 1 corresponding to the domain data agent network element 1 and operation configuration information 2 corresponding to the domain data agent network element 2 based on the first requirements information 1, the domain data service function information 1, and the domain data service function information 2. For example, the operation configuration information 1 includes: AI training and interaction with the service request network element. The operation configuration information 2 may include data preprocessing and further include sending the preprocessing result to the domain data agent network element 1.

[0432] In a possible design manner, S804a may include: if any one of the at least one data agent network elements in the first domain has access to the first data, the first domain data orchestration network element determines, based on the first requirements information and the one or more portions of domain data service capability information, at least one data agent network element in the first domain and operation configuration information corresponding to each of the at least one data agent network element in the first domain.

[0433] In this way, the data agent network elements in the first domain participating in the data service and the corresponding operational configuration information are determined only if any one of at least one data agent network elements in the first domain has access to the first data, or if any one of at least one data agent network elements in the first domain does not have access to the first data, the data agent network elements in the first domain participating in the data service and the corresponding operational configuration information are not determined, thereby implementing a trusted service requirement for data.

[0434] In some embodiments, the method provided in this embodiment of the present application may further include the following step: S817: The trust anchor sends a first validation response message to the first domain data orchestration network element. In response, the first domain data orchestration network element receives the first validation response message from the trust anchor.

[0435] Optionally, the first validation response message indicates whether any one of the at least one data agent network element in the first domain has access to the first data.

[0436] In some embodiments, the method provided in this embodiment of the present application may further include the following step: S818: The first domain data orchestration network element sends a first validation request message to the trust anchor. In response, the trust anchor receives the first validation request message from the first domain data orchestration network element.

[0437] Optionally, the first verification request message is for requesting verification of whether any one of at least one data agent network element in the first domain has access rights to the first data.

[0438] It should be noted that S818 may be executed before S817.

[0439] S804b: The first domain data orchestration network element determines, based on the second requirements information and the one or more portions of the domain data service capability information, at least one data agent network element in the second domain and operation configuration information corresponding to each of the at least one data agent network element in the second domain.

[0440] For example, one or more portions of the domain data service capability information may correspond to one or more data agent network elements in the second domain, respectively. For specific implementations, please refer to the corresponding description in S804a. Details will not be described again in this specification.

[0441] For example, the at least one data agent network element in the second domain may be at least one of one or more data agent network elements in the second domain.

[0442] For example, the operation configuration information of any one of at least one data agent network element in the second domain may indicate an operation to be performed by any data agent network element in the second domain on the first data.

[0443] For example, the second requirements information corresponds to at least one portion of one or more domain data service capability information (corresponding respectively to one or more data agent network elements in the second domain).

[0444] In this manner, the second domain data agent network element determines the data agent network elements in the second domain participating in the current data service based on the second requirements information and at least a portion of the data service capability information in the second domain, where the data service capabilities of the selected data agent network elements in the second domain must be capable of satisfying the service requirements in the second requirements information, and the selected data agent network element in the first domain and the selected data agent network element in the second domain can respectively perform the operations indicated by the respective operation configuration information, thereby implementing the data service.

[0445] It should be noted that for the specific implementation of the operation configuration information, it is necessary to refer to the description of S804a, and the details will not be described again in this specification.

[0446] In some embodiments, the method provided in this embodiment of the present application may further include: the second domain data orchestration network element determining the first communication information.

[0447] In some embodiments, if the first indication information indicates that the domain data agent network element that communicates directly with the service request network element is a data agent network element in the second domain, the second domain data orchestration network element determines the first communication information.

[0448] It should be noted that the specific implementation of S804b is similar to the specific implementation of S804a. For details, please refer to S804a. The details will not be described again in this specification.

[0449] In a possible design manner, S804b may include: if any one of the at least one data agent network element in the second domain has access to the first data, the second domain data orchestration network element determines, based on the second requirements information and the one or more portions of the domain data service capability information, at least one data agent network element in the second domain and operation configuration information corresponding to each of the at least one data agent network element in the second domain.

[0450] In this way, the data agent network elements in the second domain participating in the data service and the corresponding operational configuration information are determined only if any one of at least one data agent network elements in the second domain has access to the first data, or if any one of at least one data agent network elements in the second domain does not have access to the first data, the data agent network elements in the second domain participating in the data service and the corresponding operational configuration information are not determined, thereby implementing the trusted service requirement for data.

[0451] In some embodiments, the method provided in this embodiment of the present application may further include the following step: S819: The trust anchor sends a first validation response message to the second domain data orchestration network element. In response, the second domain data orchestration network element receives the first validation response message from the trust anchor.

[0452] Optionally, the first validation response message indicates whether any one of the at least one data agent network element in the second domain has access to the first data.

[0453] In some embodiments, the method provided in this embodiment of the present application may further include the following steps: S820: The second domain data orchestration network element sends a first validation request message to the trust anchor. In response, the trust anchor receives the first validation request message from the second domain data orchestration network element.

[0454] Optionally, the first verification request message is for requesting verification of whether any one of at least one data agent network element in the second domain has access rights to the first data.

[0455] It should be noted that S819 may be performed before S820.

[0456] In a possible design, the method provided in this embodiment of the present application may further include: the first domain data orchestration network element may send the second communication information to the second domain data orchestration network element, and in response, the second domain data orchestration network element receives the second communication information from the first domain data orchestration network element.

[0457] Optionally, the second communication information may indicate information regarding a data agent network element in at least one data agent network element in the first domain that communicates directly with a data agent network element in the second domain.

[0458] In a possible design, the method provided in this embodiment of the present application may further include: the second domain data orchestration network element may send third communication information to the first domain data orchestration network element, and in response, the first domain data orchestration network element receives the third communication information from the second domain data orchestration network element.

[0459] Optionally, the third communication information may indicate information regarding a data agent network element in at least one data agent network element in the second domain that communicates directly with a data agent network element in the first domain.

[0460] Assume that the selected at least one data agent network element in the first domain includes domain data agent network element a and domain data agent network element b, and the selected at least one data agent network element in the second domain includes domain data agent network element c and domain data agent network element d. The second communication information may include, but is not limited to, one or more of the following: an address of domain data agent network element b, an identifier of domain data agent network element b, and an index of domain data agent network element b. The third communication information may include, but is not limited to, one or more of the following: an address of domain data agent network element c, an identifier of domain data agent network element c, and an index of domain data agent network element c. The first domain data orchestration network element and the second domain data orchestration network element exchange information about domain data agent network elements for communication between the first domain and the second domain.

[0461] In this way, domain data agent network element a can send collected data to domain data agent network element b, and domain data agent network element b sends the collected data to domain data agent network element c, and domain data agent network element c performs the corresponding operation and then sends the collected data obtained through the operation to domain data agent network element d.

[0462] It should be noted that the first domain data orchestration network element's determining the second communication information and S804a may be performed in the same step or separately, and the first domain data orchestration network element's determining the third communication information and S804b may be performed in the same step or separately, which is not limited in the present application.

[0463] S805a: The first domain data orchestration network element sends operation configuration information to the data agent network element in the first domain. The data agent network element in the first domain receives the operation configuration information from the first domain data orchestration network element.

[0464] In this manner, the first domain data orchestration network element transmits corresponding operational configuration information to each of the at least one data agent network element in the first domain.

[0465] In a possible design method, the method provided in this embodiment of the present application may further include the following steps: S821: The first domain data orchestration network element sends first communication information to the service request network element, and in response, the service request network element receives the first communication information from the first domain data orchestration network element.

[0466] In this way, the service request network element may establish a direct interaction with the data agent network element in the first domain based on the received first communication information and may receive a message directly from the data agent network element in the first domain.

[0467] It should be noted that S821 may be executed after S804a. The execution order of S821 and S805a is not limited in the present application.

[0468] S805b: The second domain data orchestration network element sends the operation configuration information to the data agent network element in the second domain. The data agent network element in the second domain receives the operation configuration information from the second domain data orchestration network element.

[0469] In this manner, the second domain data orchestration network element transmits corresponding operational configuration information to each of the at least one data agent network element in the second domain.

[0470] In a possible design, the method provided in this embodiment of the present application may further include the following steps: S822: The second domain data orchestration network element sends the first communication information to the service request network element, and in response, the service request network element receives the first communication information from the second domain data orchestration network element.

[0471] In this way, the service request network element may establish a direct interaction with the data agent network element in the second domain based on the received first communication information and may receive a message directly from the data agent network element in the second domain.

[0472] It should be noted that S822 may be executed after S804b. The execution order of S822 and S805b is not limited in the present application.

[0473] It should be noted that S821 and S822 may be in a parallel relationship. For example, if the first indication information indicates that the domain data agent network element that directly communicates with the service requesting network element is a data agent network element in a first domain, the method provided in this embodiment of the present application may include S821. If the first indication information indicates that the domain data agent network element that directly communicates with the service requesting network element is a data agent network element in a second domain, the method provided in this embodiment of the present application may include S822.

[0474] S806: The data agent network element in the first domain processes the first data based on the operation indicated by the operation configuration information to obtain first information.

[0475] For example, a data agent network element in a first domain obtains the operation indicated by the operation configuration information and coordinates the functions of the data agent network elements in the first domain to form an operation chain, where the output of the function in the previous stage is the input of the function in the next stage, and processes the first data based on the operation chain to obtain the first information.

[0476] Optionally, the first information may be raw data, intermediate data, analysis results, or the like.

[0477] It should be noted that for the specific implementation of the operation configuration information, reference should be made to the corresponding description in S804a, and the details will not be described again in this specification.

[0478] In some embodiments, the data agent network element in the second domain may perform functions similar to those of the data agent network element in the first domain, and the data agent network element in the second domain processes the first data based on the operation indicated by the operation configuration information to obtain the first information.

[0479] For example, a data agent network element in a second domain obtains the operation indicated by the operation configuration information and coordinates the functions of the data agent network elements in the second domain to form an operation chain, where the output of the function in the previous stage is the input of the function in the next stage, and processes the first data based on the operation chain to obtain the first information.

[0480] It should be noted that for the specific implementation of the operation configuration information, reference should be made to the corresponding description in S804a, and the details will not be described again in this specification.

[0481] In some embodiments, S806 may include the following steps 5 and 6.

[0482] Step 5: The first domain data agent network element sends a data request message to the third domain data agent network element based on the operation configuration information. In response, the third domain data agent network element receives the data request message from the first domain data agent network element.

[0483] Optionally, the data request message may be for requesting one or more of, but not limited to, network data, user data, Internet of Things data, and artificial intelligence model data.

[0484] For example, operational configuration information may include collecting initial data from a third domain data agent network element.

[0485] It should be noted that the first domain data agent network element and the third domain data agent network element may be data agent network elements of different types or may be domain data agent network elements of the same type.

[0486] For example, assume that the first domain data agent network element is a mobility management network element 1, and the third domain data agent network element may be a session management network element or may be an access network device.

[0487] In this way, inter-domain data agent network elements can be connected to form a cross-domain data service architecture.

[0488] Optionally, the data request message may include security information.

[0489] Optionally, the security information may be used to verify whether the first domain data agent network element has access to the first data.

[0490] For example, the security information may include, but is not limited to, a private key signature.

[0491] In this way, it can be verified whether the first domain data agent network element has access to the first data.

[0492] Step 6: The third domain data agent network element sends a data response message to the first domain data agent network element. In response, the first domain data agent network element receives a data response message from the third domain data agent network element.

[0493] Optionally, the data response message may include one or more of the data included in the data request message, for example, network data, user data, Internet of Things data, and artificial intelligence model data.

[0494] Optionally, the first information may include initial data, for example, network data, user data, Internet of Things data, and artificial intelligence model data.

[0495] In this way, the first domain data agent network element can obtain the first data from the data source (the third domain data agent network element).

[0496] Optionally, step 6 may include: if the first domain data agent network element has access to the first data of the third domain data agent network element, the third domain data agent network element sends a data response message to the first domain data agent network element; or if the first domain data agent network element does not have access to the first data of the third domain data agent network element, the third domain data agent network element rejects the request, thereby implementing the E2E trusted service requirement for data.

[0497] Optionally, whether the first domain data agent network element has access to the first data of the third domain data agent network element may be obtained by the third domain data agent network element from the trust anchor.

[0498] For example, a third domain data agent network element sends a validation request message to a trust anchor and receives a validation response message from the trust anchor.

[0499] For example, the verification request message may be for requesting verification of whether a first domain data agent network element has access to first data of a third domain data agent network element.

[0500] Optionally, the verification request message may include security information corresponding to the first domain data agent network element.

[0501] For example, the validation response message may indicate whether the first domain data agent network element has or does not have access to the first data of the third domain data agent network element.

[0502] Optionally, after receiving the validation request message, the trust anchor may check the data access policy and validate the security information to obtain whether the first domain data agent network element has or does not have access to the first data of the third domain data agent network element.

[0503] For example, based on the data type of the initial data, the trust anchor may check data access policies and verify security information.

[0504] For example, assume that the data access policy includes the following: A first domain data agent network element has access to the network data of a third domain data agent network element, and the first domain data agent network element does not have access to the user data of the third domain data agent network element. If the first data is user data, the validation response message obtained by the trust anchor may indicate that the first domain data agent network element does not have access to the user data of the third domain data agent network element. If the first data includes user data and network data, the validation response message obtained by the trust anchor may indicate that the first domain data agent network element does not have access to the user data of the third domain data agent network element and that the first domain data agent network element has access to the network data of the third domain data agent network element.

[0505] In some embodiments, step S806 may include: the first domain data agent network element processes the second information based on the operation indicated by the operation configuration information to obtain the first information.

[0506] Optionally, the second information may be received by the first domain data agent network element.

[0507] For example, the second information may be received by the first domain data agent network element from another domain data agent network element.

[0508] Optionally, second information may be obtained based on the first data.

[0509] For example, the second information may be obtained through processing (e.g., data collection, data pre-processing, data protection, data storage, and / or data analysis) performed by another domain data agent network element on the first data.

[0510] For example, operational configuration information may include, but is not limited to, one or more of the following: data collection, data pre-processing, data protection, data storage, and data analysis.

[0511] For example, the second information is obtained through data preprocessing performed by another domain data agent network element on the first data, the operation configuration information includes data analysis and data protection, and the first domain data agent network element forms an operation chain based on the operation configuration information (performing data analysis and then performing security protection) and obtains the first information by analyzing the second information and performing security protection thereon.

[0512] In some embodiments, step S806 may include: the first domain data agent network element processes the initial data and the application data based on the operation indicated by the operation configuration information to obtain the first information.

[0513] Optionally, the application data may be obtained from the application network element by the first domain data agent network element.

[0514] Optionally, the data agent network element may be deployed within the application network element.

[0515] For example, application data may include, but is not limited to, one or more of the following: user historical behavior records collected by application programs in a compliant manner (e.g., where the user is authenticated), and the like.

[0516] For example, the first domain data agent network element performs collaborative processing on Internet of Things data and application data, thereby enabling rapid and accurate determination of abnormal behavior of terminal devices in the Internet of Things.

[0517] In a possible design method, the method provided in this embodiment of the present application may further include the following step: Step c: if the operation configuration information indicates that the first domain data agent network element communicates with the second domain data agent network element, the first domain data agent network element sends the first information to the second domain data agent network element. domain Data Agent Network Elements are the first domain The data agent receives first information from the network element.

[0518] Optionally, the operational configuration information may instruct the first domain data agent network element to transmit the first information to the second domain data agent network element.

[0519] For example, operational configuration information may include: interactions with a second domain data agent network element;

[0520] In this manner, the first domain data agent network element may transmit first information to the second domain data agent network element, and the second domain data agent network element may process or forward the first data based on the operational configuration information corresponding to the second domain data agent network element.

[0521] In some embodiments, the method provided in this embodiment of the present application may further include the following step: Step d: the trust anchor sends a third validation response message to the first domain data agent network element. In response, the first domain data agent network element receives the third validation response message from the trust anchor.

[0522] Optionally, the third validation response message may indicate that the second data agent network element has access to the initial data of the first data agent network element, or may indicate that the second data agent network element does not have access to the initial data of the first data agent network element.

[0523] It should be noted that in this embodiment of the present application, the order of execution of step d is not limited. For example, step d may be executed before the first domain data agent network element transmits the first information to the second domain data agent network element.

[0524] For example, if the second domain data agent network element determines that it has access to the first data of the first domain data agent network element, the first domain data agent network element transmits the first information to the second domain data agent network element. Alternatively, if the second domain data agent network element determines that it does not have access to the first data of the first domain data agent network element, the first domain data agent network element does not transmit the first information to the second domain data agent network element. This allows the E2E trusted service requirement for data to be implemented.

[0525] In this way, if the original data contains user data, compliance detection for the user data can be implemented.

[0526] In some embodiments, the method provided in this embodiment of the present application may further include the following step: Step e: the first domain data agent network element sends a third validation request message to the trust anchor. In response, the trust anchor receives the third validation request message from the first domain data agent network element.

[0527] Optionally, the third verification request message may be for requesting verification of whether the second domain data agent network element has access to the first data of the first domain data agent network element.

[0528] Optionally, the third verification request message may include security information corresponding to the second domain data agent network element.

[0529] For example, security information corresponding to a second domain data agent network element may be obtained from the second domain data agent network element by the first domain data agent network element.

[0530] For example, the security information may include, but is not limited to, a private key signature.

[0531] Optionally, after receiving the third verification request message, the trust anchor may check the data access policy and verify the security information to obtain whether the second domain data agent network element has or does not have access to the first data of the first domain data agent network element. A specific implementation is similar to the implementation described above, and after receiving the verification request message, the trust anchor may check the data access policy and verify the security information to obtain whether the first domain data agent network element has or does not have access to the first data of the third domain data agent network element. Details will not be described again in this specification.

[0532] In a possible design method, the method provided in this embodiment of the present application may further include the following step: Step f: if the operation configuration information indicates that the first domain data agent network element communicates with the service request network element, the first domain data agent network element sends first information to the service request network element, and in response, the service request network element receives the first information from the first domain data agent network element.

[0533] For example, the first information may be obtained based on the initial data.

[0534] Optionally, the first domain data agent network element may be a domain data agent network element that communicates directly with the service requesting network element.

[0535] Optionally, the operation configuration information may instruct the first domain data agent network element to send the first information to the service request network element.

[0536] For example, the operational configuration information may include: Interactions with service request network elements.

[0537] In this way, the service request network element obtains first information, where the first information may be raw data, intermediate data, analysis results, or the like.

[0538] It should be noted that step a to step f are merely step names added for ease of understanding and do not indicate the order in which the corresponding steps are performed.

[0539] In some embodiments, the method provided in this embodiment of the present application may further include: the first domain data agent network element sending the processing behavior information to the trust anchor, and in response, the trust anchor receiving the processing behavior information from the first domain data agent network element.

[0540] Optionally, the processing behavior information may indicate a processing behavior performed by the first domain data agent network element on the first data.

[0541] For example, if the first data is user data, the processing behavior information may indicate processing behaviors performed by the first domain data agent network element on the first data, such as collection, preprocessing, storage, data analysis, data protection, desensitization, and transmission.

[0542] Optionally, the trust anchor may record transaction behavior on a distributed ledger.

[0543] In this way, any domain data agent network element can send processing behavior information to the trust anchor when handling user data in the processing process, thereby meeting GDPR / PIPL compliance requirements.

[0544] In a possible design method, the method provided in this embodiment of the present application may further include: the service request network element processes the first information to obtain an application service or a service service.

[0545] For example, the first information may not be the final result expected by the service request network element, but may be, for example, intermediate data, which the service request network element processes to obtain the final result.

[0546] In some embodiments, the service requesting network element processing the first information to obtain an application service or a service may include: the service requesting network element obtaining abnormal behavior information of a terminal device in the Internet of Things by using the first information.

[0547] For example, in an abnormal behavior detection scenario for IoT terminal devices, abnormal behavior of terminal devices in the Internet of Things, such as hijacking of IoT terminal devices or air interface signaling distributed denial of service (DDoS) attacks, can be obtained.

[0548] In some embodiments, the service requesting network element processing the first information to obtain the application service or the service may include: the service requesting network element predicting service quality by using the first information and parameter configuration information of the artificial intelligence model.

[0549] Optionally, parameter configuration information of the artificial intelligence model may be used to predict the quality of service.

[0550] In this way, the service request network element performs inference and obtains a prediction result of service quality by using the parameter configuration information of the artificial intelligence model and the first information (which is intermediate data).

[0551] Optionally, the service request network element locally stores parameter configuration information of the artificial intelligence model.

[0552] Alternatively, optionally, if the service request network element does not store the parameter configuration information of the artificial intelligence model locally, the service request network element may obtain the parameter configuration information of the artificial intelligence model through the first domain data agent network element and request the artificial intelligence model parameter configuration information from the first domain data agent network element.

[0553] Optionally, the service request network element may perform hashing on the digest of the artificial intelligence model and perform a comparison against the hash value stored in the distributed ledger to verify the consistency of the model.

[0554] After receiving the respective operation configuration information, the data agent network element in the first domain and the data agent network element in the second domain may perform the operation indicated by the operation configuration information and send intermediate data or analysis results to the service request network element. The following describes an example in which the data agent network element in the first domain obtains first information, then sends the first information to the data agent network element in the second domain, and the data agent network element in the second domain processes the first information to obtain third information, and sends the third information to the service request network element.

[0555] S807: If the operation configuration information indicates that the data agent network element in the first domain communicates with the data agent network element in the second domain, the data agent network element in the first domain sends first information to the data agent network element in the second domain. In response, the data agent network element in the second domain receives the first information from the data agent network element in the first domain.

[0556] For the specific implementation of S801, please refer to step c, and the details will not be described again in this specification.

[0557] S808: The data agent network element in the second domain processes the first information based on the operation configuration information to obtain third information.

[0558] Optionally, the third information may be intermediate data, analytical results, or the like.

[0559] In other words, the data agent network element in the second domain processes the first information based on the operation indicated by the operation configuration information (received in S805b) to obtain the third information.

[0560] In a practical application, multiple data agent network elements in the second domain may process the first information based on their respective operational configuration information to obtain the third information, the details of which are not described one by one in this application.

[0561] S809: The data agent network element in the second domain sends the third information to the service request network element, and in response, the service request network element receives the third information from the data agent network element in the second domain.

[0562] In this way, the service request network element obtains the third information, where the third information may be intermediate data, analysis results, or the like.

[0563] The specific implementation of S809 is the same as the specific implementation of step c. For details, please refer to step c. The details will not be described again in this specification.

[0564] In a possible design method, the method provided in this embodiment of the present application may further include: the service request network element processes the third information to obtain the application service or the service service. The implementation is similar to the above-mentioned implementation, in which the service request network element processes the first information to obtain the application service or the service service. The details will not be described again in this specification.

[0565] According to the method illustrated in Figures 8A to 8C, a domain data orchestration network element receives first requirements information, determines from one or more domain data agent network elements which domain data agent network elements participate in the current data service based on the first requirements information and one or more portions of domain data service capability information, and obtains operation configuration information corresponding to each domain data agent network element participating in the current data service. The operation configuration information indicates an operation to be performed by the domain data agent network element on the first data, and the first requirements information corresponds to at least one or more portions of domain data service capability information. The domain data orchestration network element transmits the operation configuration information to the corresponding domain data agent network element, and the domain data agent network element performs the operation indicated by the operation configuration information. In this manner, a data service can be implemented.

[0566] In this application, unless otherwise specified, identical or similar parts in the embodiments shall be mutually referenced. In the embodiments and implementations / methods / implementation methods in the embodiments of this application, unless otherwise specified or unless a logical conflict occurs, the terms and / or descriptions shall be consistent and mutual references may be made between various embodiments and between implementations / methods / implementation methods in the embodiments. The technical features in various embodiments and implementations / methods / implementation methods in the embodiments may be combined to form new embodiments, implementations, methods, or implementation methods based on the internal logical relationships of the technical features. The following implementations of this application are not intended to limit the protection scope of this application.

[0567] The communication method provided in this embodiment of the present application has been described in detail above with reference to Figures 1 to 8A-8C. Hereinafter, the communication device provided in this embodiment of the present application will be described in detail with reference to Figure 9.

[0568] For example, Fig. 9 is a diagram illustrating the configuration of a communication device according to an embodiment of the present application. The communication device may be used in the communication system illustrated in Fig. 1. For ease of explanation, Fig. 9 illustrates only the main components of the communication device. As illustrated in Fig. 9, the communication device 900 includes: a transceiver module 901 and a processing module 902.

[0569] In a possible design solution, the communication device 900 shown in FIG. 9 can be used in the system shown in FIG. 1 to perform the functions of the domain data orchestration network element in the communication method in FIGS. 8A to 8C.

[0570] The transceiver module 901 is configured to receive first requirement information, the first requirement information being a service requirement related to the first data and corresponding to the communication device 900.

[0571] The processing module 902 is configured to determine at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information and the one or more portions of domain data service capability information, wherein the one or more portions of domain data service capability information correspond one-to-one to the one or more domain data agent network elements, the at least one domain data agent network element is at least one of the one or more domain data agent network elements, the first requirements information corresponds to at least one of the one or more portions of domain data service capability information, and the operation configuration information of any one of the at least one domain data agent network element indicates an operation to be performed by any one domain data agent network element on the first data.

[0572] The transceiver module 901 is further configured to transmit operational configuration information.

[0573] In one possible design, the processing module 902 is configured to determine at least one domain data agent network element based on the first requirements information and the one or more portions of the domain data service capability information.

[0574] The transceiver module 901 is further configured to determine operational configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirements information and one or more portions of the domain data service capability information if any one of the at least one domain data agent network elements has access to the first data.

[0575] In one possible design, the transceiver module 901 is further configured to receive a first validation response message from the trust anchor, the first validation response message may indicate whether any one of the at least one domain data agent network element has access to the first data.

[0576] In one possible design, the transceiver module 901 is further configured to send a first validation request message to the trust anchor, the first validation request message requesting validation of whether any one of the at least one domain data agent network element has access to the first data.

[0577] In one possible design, the transceiver module 901 is further configured to receive first indication information from the data orchestration network element, where the first indication information may indicate that a domain data agent network element that directly communicates with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0578] In a possible design, the transceiver module 901 is further configured to transmit first communication information, which may indicate information about a domain data agent network element within the at least one domain data agent network element that directly communicates with the service request network element.

[0579] In a possible design, the transceiver module 901 is further configured to receive domain data service capability information corresponding to one or more domain data agent network elements.

[0580] In one possible design, the transceiver module 901 is further configured to transmit first data service capability information to the data orchestration network element, where the first data service capability information can be determined based on one or more portions of the domain data service capability information.

[0581] In a possible design, the domain data service function information of any one of the one or more domain data agent network elements may include one or more of the following: an identifier of the one domain data agent network element, location information of the one domain data agent network element, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0582] In a possible design scenario, the operations indicated by the operation configuration information include one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with service request network elements.

[0583] In a possible design manner, the first requirement information includes one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0584] In one possible design, the communications device 900 is a core network domain data orchestration network element or an access network domain data orchestration network element.

[0585] In a possible design scheme, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or one or more domain data agent network elements is a data agent network element in an access network domain.

[0586] In a possible design scenario, the initial data may include data collected from a mobile communication network or synthetic data.

[0587] It should be noted that all relevant contents of the steps in the above-mentioned method embodiments may be cited in the functional descriptions of the corresponding functional modules, and the details will not be described again in this specification.

[0588] It should be noted that the transceiver module 901 may include a receiving module and a transmitting module (not shown in FIG. 9), which is not particularly limited.

[0589] Optionally, the communications device 900 may further include a storage module (not shown in FIG. 9 ) for storing programs or instructions. When the processing module 902 executes the programs or instructions, the communications device 900 may perform the functions of a domain data orchestration network element in the communications methods illustrated in FIGS. 8A through 8C .

[0590] It should be noted that the communication device 900 may be a domain data orchestration network element, or may be a chip (system) or another component or assembly that may be disposed within a domain data orchestration network element, which is not a limitation of the present application.

[0591] For the technical effects of the communication device 900, please refer to the technical effects of the communication method shown in Figures 8A to 8C, and the details will not be described again in this specification.

[0592] In another possible design solution, the communication device 900 shown in FIG. 9 can be used in the system shown in FIG. 1 to perform the functions of the data orchestration network element in the communication method shown in FIGS. 8A to 8C.

[0593] The transceiver module 901 is configured to receive a first service request message.

[0594] The processing module 902 is configured to determine first requirement information and second requirement information based on the requirement information, first data service capability information, and second data service capability information, wherein the requirement information is a service requirement related to the first data, the service requirement being determined based on a service requested by using the first service request message, the first data service capability information corresponding to a first domain data orchestration network element, and the second data service capability information corresponding to a second domain data orchestration network element.

[0595] The transceiver module 901 is further configured to transmit first requirement information and second requirement information, the first requirement information being a service requirement related to the first data and corresponding to a first domain data orchestration network element, and the second requirement information being a service requirement related to the first data and corresponding to a second domain data orchestration network element.

[0596] In a possible design scenario, the first service request message may be for requesting an application service or a service service.

[0597] In one possible design, the transceiver module 901 is further configured to receive first data service capability information from the first domain data orchestration network element, where the first data service capability information can be determined based on one or more portions of the domain data service capability information.

[0598] In one possible design, the transceiver module 901 is further configured to receive second data service capability information from a second domain data orchestration network element, where the second data service capability information can be determined based on one or more portions of the domain data service capability information.

[0599] In a possible design, the one or more pieces of domain data service capability information have a one-to-one correspondence with one or more domain data agent network elements, and the domain data service capability information of any one of the one or more domain data agent network elements may include one or more of the following: an identifier of any one of the domain data agent network elements, location information of any one of the domain data agent network elements, a data collection function, a data pre-processing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

[0600] In a possible design manner, the first service request message is from a service requesting network element, and the transceiver module 901 is further configured to send a second verification request message to the trust anchor, The second verification request message may be to request verification of whether the service requesting network element has access to the first data.

[0601] In one possible design, the first service request message is from a service requesting network element, and the transceiver module 901 is further configured to send first indication information to the first domain data orchestration network element and / or the second domain data orchestration network element, where the first indication information may indicate that the domain data agent network element directly communicating with the service requesting network element is a data agent network element in a core network domain or a data agent network element in an access network domain.

[0602] In a possible design, the transceiver module 901 is further configured to transmit updated information regarding the data security and privacy protection technology repository and / or updated information regarding the analysis tool repository.

[0603] In a possible design scenario, the requirements information may include one or more of the following service requirements: geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0604] In a possible design scenario, the requirements information may correspond to a data service task identifier.

[0605] In a possible design scheme, the first domain data orchestration network element may be a core network domain data orchestration network element, and the second domain data orchestration network element is an access network domain data orchestration network element.

[0606] In a possible design scheme, any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or one or more domain data agent network elements is a data agent network element in an access network domain.

[0607] In a possible design scenario, the initial data may include data collected from a mobile communication network or synthetic data.

[0608] It should be noted that all relevant contents of the steps in the above-mentioned method embodiments can be cited in the functional descriptions of the corresponding functional modules, and the details will not be described again in this specification.

[0609] It should be noted that the transceiver module 901 may include a receiving module and a transmitting module (not shown in FIG. 9), but this is not particularly limited.

[0610] Optionally, the communications device 900 may further include a storage module (not shown in FIG. 9 ) for storing programs or instructions. When the processing module 902 executes the programs or instructions, the communications device 900 may perform the function of a domain data orchestration network element in the communications methods shown in FIGS. 8A through 8C .

[0611] It should be noted that the communication device 900 may be a data orchestration network element, or may be a chip (system) or another component or assembly that may be disposed within a data orchestration network element, which is not a limitation of the present application.

[0612] For the technical effects of the communication device 900, please refer to the technical effects of the communication method shown in Figures 8A to 8C, and the details will not be described again in this specification.

[0613] In yet another possible design solution, the communication device 900 shown in FIG. 9 can be used in the system shown in FIG. 1 to perform the functions of the first domain data agent network element in the communication method shown in FIGS. 8A to 8C.

[0614] The transceiver module 901 is configured to receive operation configuration information, which indicates an operation to be performed by the communication device 900 on the original data.

[0615] The processing module 902 is configured to process the original data based on the operation indicated by the operation configuration information to obtain first information.

[0616] The transceiver module 901 is further configured to transmit the first information to a second domain data agent network element if the operation configuration information indicates that the communication device 900 is to communicate with a second domain data agent network element. Alternatively, the transceiver module 901 is further configured to transmit the first information to a service request network element if the operation configuration information indicates that the communication device 900 is to communicate with a service request network element.

[0617] In a possible design scenario, the operations indicated by the operation configuration information may include one or more of the following: data collection, data pre-processing, data protection, data storage, data analysis, and interaction with service request network elements.

[0618] In one possible design, the transceiver module 901 is further configured to transmit a data request message to the third domain data agent network element based on the operational configuration information, where the data request message can be for requesting one or more of the following: network data, user data, Internet of Things data, and artificial intelligence model data.

[0619] The transceiver module 901 is further configured to receive a data response message from the third domain data agent network element, the data response message including one or more of the data included in the data request message.

[0620] In a possible design, the data request message may further include security information, which is used to verify whether the communication device 900 has access rights to the original data.

[0621] In a possible design, the processing module 902 is further configured to process the second information based on the operation indicated by the operation configuration information to obtain the first information, wherein the second information is received by the communication device 900 and the second information is obtained based on the initial data.

[0622] In one possible design, the transceiver module 901 may be further configured to receive a first validation response message from the trust anchor, the first validation response message indicating that the second domain data agent network element has access to the first data in the communication device 900.

[0623] In one possible design, the transceiver module 901 is further configured to send a third verification request message to the trust anchor, the third verification request message being for requesting verification of whether the second domain data agent network element has access to the first data of the communication device 900.

[0624] In a possible design, the transceiver module 901 is further configured to transmit domain data service capability information to a domain data orchestration network element.

[0625] In a possible design, the domain data service capability information may include one or more of the following: an identifier of the communication device 900, location information of the communication device 900, a data collection capability, a data pre-processing capability, a data storage capability, a data reporting capability, a data analysis capability, a capability to interact with a service request network element, a data protection capability, and a data compression capability.

[0626] In a possible design, the transceiver module 901 is further configured to receive updates regarding the data security and privacy protection technology repository and / or updates regarding the analysis tool repository from the data orchestration network element.

[0627] In possible design scenarios, the communications device 900 may be a core network domain data agent network element, an access network domain data agent network element, a terminal domain data agent network element, or a standalone data agent network element.

[0628] In a possible design scenario, the initial data may include data collected from a mobile communication network or synthetic data.

[0629] It should be noted that all relevant contents of the steps in the above-mentioned method embodiments can be cited in the functional descriptions of the corresponding functional modules, and the details will not be described again in this specification.

[0630] It should be noted that the transceiver module 901 may include a receiving module and a transmitting module (not shown in FIG. 9), which is not particularly limited.

[0631] Optionally, the communication device 900 may further include a storage module (not shown in FIG. 9 ) for storing programs or instructions. When the processing module 902 executes the programs or instructions, the communication device 900 may perform the function of a first domain data agent network element in the communication method shown in FIGS. 8A through 8C .

[0632] It should be noted that the communication device 900 may be a first domain data agent network element, such as a core network domain data agent network element, an access network domain data agent network element, a terminal domain data agent network element, or a standalone data agent network element, or may be a chip (system) or another component or assembly that may be disposed within the first domain data agent network element, which is not limited in this application.

[0633] For the technical effects of the communication device 900, please refer to the technical effects of the communication method shown in Figures 8A to 8C, and the details will not be described again in this specification.

[0634] An embodiment of the present application provides a communication system, including a domain data orchestration network element and a data orchestration network element, and may further include a first domain data agent network element and / or a service request network element.

[0635] The domain data orchestration network element is configured to perform the actions of the domain data orchestration network element in the above-described method embodiments, and the data orchestration network element is configured to perform the actions of the data orchestration network element in the above-described method embodiments.

[0636] Optionally, the first domain data agent network element is configured to perform the actions of the first domain data agent network element in the above-mentioned method embodiment, and the service request network element is configured to perform the actions of the service request network element in the above-mentioned method embodiment. For specific execution methods and processes, please refer to the above-mentioned method embodiment. Details will not be described again in this specification.

[0637] An embodiment of the present application provides a chip system, which includes a logic circuit and an input / output port, wherein the logic circuit can be configured to implement a processing function in a communication method provided in an embodiment of the present application, and the input / output port can be configured to implement a receiving function and a transmitting function in the communication method provided in an embodiment of the present application.

[0638] For example, the input port may be configured to implement a receiving function in the communication method provided in the embodiment of the present application, and the output port may be configured to implement a transmitting function in the communication method provided in the embodiment of the present application.

[0639] In a possible design, the chip system further includes a memory configured to store program instructions and data for implementing functions in the communication method provided in the embodiments of the present application.

[0640] A chip system may include a chip, or may include a chip and another individual device.

[0641] An embodiment of the present application provides a computer-readable storage medium, which stores a computer program or instruction, and when the computer program or instruction runs on a computer, performs the communication method provided in the embodiment of the present application.

[0642] An embodiment of the present application provides a computer program product, which includes a computer program or instructions, which, when executed on a computer, perform the communication method provided in the embodiment of the present application.

[0643] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU). The processor may also be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

[0644] It may be understood that the memory in the embodiments of the present application may be volatile memory, or may be nonvolatile memory, or may include both volatile and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct Rambus random access memory (DR RAM).

[0645] All or part of the above-described embodiments may be implemented by software, hardware (e.g., circuits, etc.), firmware, or any combination thereof. When software is used to implement an embodiment, the above-described embodiment may be implemented entirely or partially in the form of a computer program product. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., infrared, radio, microwave, or the like) manner. The computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device, such as a server or data center, that integrates one or more available media. The available media may be magnetic media (such as a floppy disk, hard disk, or magnetic tape), optical media (such as a DVD), or semiconductor media. The semiconductor media may be a solid-state drive.

[0646] It should be understood that the term "and / or" in this specification describes only an association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. A and B may be singular or plural. Furthermore, the character " / " in this specification usually indicates an "or" relationship between related objects, but may also indicate an "and / or" relationship. Please refer to the context for further understanding.

[0647] As used herein, "at least one" refers to one or more, and "plurality" refers to two or more. "At least one of the following items (moieties)" or similar expressions refers to any combination of these items, including a single item (moiety) or any combination of multiple items (moieties). For example, at least one item (moiety) of a, b, or c can refer to a, b, c, ab, ac, bc, or abc, where a, b, and c may be singular or plural.

[0648] It should be understood that the order numbers of the above processes do not mean the order of execution in various embodiments of the present application. The order of execution of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process of the embodiments of the present application.

[0649] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the design constraints of a specific application and technical solution. Those skilled in the art may use various methods to implement the functions described for each specific application, but the implementation should not be considered to go beyond the scope of this application.

[0650] For convenience and concise description, it can be obviously understood by those skilled in the art that the detailed operation processes of the above-mentioned systems, devices and units need to refer to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again in this specification.

[0651] In some embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, unit divisions are merely logical functional divisions, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, mutual couplings or direct couplings or communication connections shown or described may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0652] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, in other words, they may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0653] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0654] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or a portion contributing to the prior art, or a portion of the technical solution may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or part of the steps of the method described in the embodiments of the present application. The above-mentioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0655] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. 1. A communication method comprising: receiving, by a domain data orchestration network element, first requirement information, the first requirement information being a service requirement in initial data corresponding to the domain data orchestration network element; determining, by the domain data orchestration network element, based on the first requirements information and one or more portions of domain data service capability information, at least one domain data agent network element and operation configuration information corresponding to each of the at least one domain data agent network element, wherein the one or more portions of domain data service capability information are in one-to-one correspondence with one or more domain data agent network elements, the at least one domain data agent network element being at least one of the one or more domain data agent network elements, the first requirements information corresponding to at least one of the one or more portions of domain data service capability information, and the operation configuration information of any one of the at least one domain data agent network element indicating an operation to be performed by any one of the one or more domain data agent network elements on the initial data; transmitting, by the domain data orchestration network element, the operational configuration information; A communication method comprising:

2. determining, by the domain data orchestration network element, the at least one domain data agent network element and operational configuration information corresponding to each of the at least one domain data agent network element based on the first requirements information and one or more portions of domain data service capability information, comprising: determining, by the domain data orchestration network element, the at least one domain data agent network element based on the first requirements information and the one or more portions of domain data service capability information; determining, by the domain data orchestration network element, the operational configuration information corresponding to the one of the at least one domain data agent network elements based on the first requirements information and the one or more portions of domain data service capability information, if the one of the at least one domain data agent network elements has access to the first data; The communication method of claim 1 , comprising:

3. receiving, by the domain data orchestration network element, a first validation response message from a trust anchor, the first validation response message indicating whether the any one of the at least one domain data agent network element has access to the first data; The communication method of claim 1 further comprising:

4. sending, by the domain data orchestration network element, a first validation request message to a trust anchor, the first validation request message for requesting verification of whether the one of the at least one domain data agent network element has access to the first data; The communication method of claim 1 further comprising:

5. receiving, by the domain data orchestration network element, first indication information, the first indication information indicating that a domain data agent network element that directly communicates with a service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain; The communication method of claim 1 further comprising:

6. sending, by the domain data orchestration network element, first communication information indicating information regarding a domain data agent network element within the at least one domain data agent network element that is in direct communication with the service request network element; The communication method of claim 5 further comprising:

7. receiving, by the domain data orchestration network element, the domain data service capability information corresponding to the one or more domain data agent network elements; The communication method of claim 1 further comprising:

8. transmitting, by the domain data orchestration network element, first data service capability information, the first data service capability information determined based on the one or more portions of domain data service capability information; The communication method of claim 7 further comprising:

9. 2. The communication method of claim 1, wherein the domain data service function information of any one of the one or more domain data agent network elements includes one or more of an identifier of any one of the one or more domain data agent network elements, location information of any one of the one or more domain data agent network elements, a data collection function, a data preprocessing function, a data storage function, a data reporting function, a data analysis function, an interaction function with a service requesting network element, a data protection function, and a data compression function.

10. The communication method of claim 1 , wherein the operations indicated by the operational configuration information include one or more of data collection, data pre-processing, data protection, data storage, data analysis, and interaction with a service request network element.

11. 2. The communication method of claim 1, wherein the first requirements information includes one or more service requirements of geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with a service request network element, data protection, and data compression.

12. The communication method of claim 1 , wherein the domain data orchestration network element is a core network domain data orchestration network element or an access network domain data orchestration network element.

13. 2. The communication method of claim 1, wherein any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

14. The communication method of claim 1 , wherein the initial data comprises data collected from a mobile communication network or synthetic data.

15. A communication method receiving, by a data orchestration network element, a first service request message; determining, by the data orchestration network element, first requirement information and second requirement information based on requirement information, first data service capability information, and second data service capability information, wherein the requirement information is a service requirement in the first data that is determined based on a service requested by using the first service request message, the first data service capability information corresponding to a first domain data orchestration network element, the second data service capability information corresponding to a second domain data orchestration network element, the first requirement information is a service requirement in the first data that is corresponding to the first domain data orchestration network element, and the second requirement information is a service requirement in the first data that is corresponding to the second domain data orchestration network element; transmitting, by the data orchestration network element, the first requirements information and the second requirements information; A communication method comprising:

16. The communication method of claim 15, wherein the first service request message is for requesting an application service or a service.

17. receiving, by the data orchestration network element, the first data service capability information from the first domain data orchestration network element, the first data service capability information being determined based on one or more portions of domain data service capability information; The communication method of claim 15 further comprising:

18. receiving, by the data orchestration network element, the second data service capability information from the second domain data orchestration network element, the second data service capability information being determined based on one or more portions of domain data service capability information; The communication method of claim 15 further comprising:

19. 18. The communication method of claim 17, wherein the one or more portions of domain data service capability information are in one-to-one correspondence with one or more domain data agent network elements, and the domain data service capability information of any one of the one or more domain data agent network elements includes one or more of an identifier of any one of the one or more domain data agent network elements, location information of any one of the one or more domain data agent network elements, a data collection function, a data preprocessing function, a data storage function, a data reporting function, a data analysis function, a function for interacting with a service requesting network element, a data protection function, and a data compression function.

20. the first service request message is from a service requesting network element; sending, by the data orchestration network element, a second verification request message to a trust anchor, the second verification request message for requesting verification of whether the service request network element has access to the first data; The communication method of claim 15 further comprising:

21. the first service request message is from a service requesting network element; sending, by the data orchestration network element, first indication information, the first indication information indicating that a domain data agent network element that directly communicates with the service request network element is a data agent network element in a core network domain or a data agent network element in an access network domain; The communication method of claim 15 further comprising:

22. transmitting, by the data orchestration network element, updates regarding the data security and privacy protection technology repository and / or updates regarding the analytical tool repository. The communication method of claim 15 further comprising:

23. 16. The communication method of claim 15, wherein the requirements information includes one or more service requirements of geographic location, data collection, data pre-processing, data storage, data reporting, data analysis, interaction with a service request network element, data protection, and data compression.

24. The communication method of claim 15 , wherein the requirements information corresponds to a data service task identifier.

25. 16. The communication method of claim 15, wherein the first domain data orchestration network element is a core network domain data orchestration network element and the second domain data orchestration network element is an access network domain data orchestration network element.

26. 20. The communication method of claim 19, wherein any one of the one or more domain data agent network elements is a data agent network element in a core network domain, or the one or more domain data agent network elements is a data agent network element in an access network domain.

27. The communication method of claim 15, wherein the initial data comprises data collected from a mobile communication network or synthetic data.

28. A communication device, said communication device comprising a unit or module adapted to carry out the method according to any one of claims 1 to 14.

29. A communication device, said communication device comprising a unit or module adapted to perform a method according to any one of claims 15 to 27.

30. A communication device, the communication device comprising a processor, the processor being configured to perform a communication method according to any one of claims 1 to 27.

31. A communication system, said communication system comprising a communication device according to claim 28 and a communication device according to claim 29.

32. 28. A computer-readable storage medium storing a computer program or instructions, the computer program or instructions being executed on a computer to perform the communication method of any one of claims 1 to 27.

Images