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] This application relates to the field of communications, and in particular, to a communication method, a communication device, and a communication system.

Background Art

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

[0003] In data service (DS), operations such as collection, preprocessing, analysis, and other operations on data may be performed, and the obtained data is provided as a service product. With the expansion of the scale of the mobile communication network, the development of new technologies, and the like, the data in the mobile communication network has been increasing, and the requirements for data services have also been increasing.

[0004] Therefore, the data in the mobile communication network can be processed based on the data service architecture to implement data services. However, the specific implementation still has room for consideration.

Summary of the Invention

[0005] Embodiments of this application provide a communication method, a communication device, and a communication system for processing data in a mobile communication network based on a data service architecture to implement data services.

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

[0007] According to a first aspect, a communication method is provided. The communication method includes the following. That is, a domain data orchestration network element receives first requirement information. 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 requirement information and a part of one or more domain data service function information. The domain data orchestration network element transmits the operation configuration information. The first requirement information is a service requirement regarding 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 corresponds one-to-one to one or more domain data agent network elements, and at least one of 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 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 element indicates an operation to be executed on the initial data by any one of the domain data agent network elements.

[0008] According to the communication method provided in the first aspect, the 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, from one or more domain data agent network elements, the domain data agent network elements participating in the current data service, and obtains operation configuration information corresponding to each domain data agent network element participating in the current data service. The operation configuration information indicates the operations to be executed by the domain data agent network element on the original data, and the first requirement information corresponds to at least a part of one or more domain data service function 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 executes the operations indicated by the operation configuration information. In this way, the data service can be implemented.

[0009] In a possible design method, for the domain data orchestration network element to determine at least one domain data agent network element and the operation configuration information corresponding to each of the at least one domain data agent network element based on the first requirement information and a part of one or more domain data service function information, it may include the following. That is, the domain data orchestration network element determines at least one domain data agent network element based on the first requirement information and a part of one or more domain data service function information. If any one of the at least one domain data agent network elements has access rights to the original data, the domain data orchestration network element determines the operation configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirement information and a part of one or more domain data service function information.

[0010] In this way, the domain data orchestration network element first determines the domain data agent network elements participating in the data service, and then, if it is determined that a domain data agent network element has access rights to the first data, corresponding operation configuration information can be determined. Or, if the domain data orchestration network element determines that a domain data agent network element does not have access rights to the first data, it does not determine the corresponding operation configuration information. Thereby, a reliable data service can be implemented.

[0011] In a possible design approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element receives a first verification response message from the trust anchor. The first verification response message may indicate whether any one of at least one domain data agent network element has access rights to the first data. A reliable data service can be implemented.

[0012] In a possible design approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element sends a first verification request message to the trust anchor. The first verification request message is for requesting verification of whether any one of at least one domain data agent network element has access rights to the first data. A reliable data service can be implemented.

[0013] In a possible design approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element receives first indication information from the data orchestration network element. 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 within the core network domain or a data agent network element within the access network domain.

[0014] In this way, the domain data orchestration network element can recognize 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 approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element transmits first communication information. The first communication information may indicate information about the domain data agent network element that is within at least one domain data agent network element and communicates directly 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 request network element from the domain data agent network elements determined to be participating in the current data service.

[0017] In a possible design approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element receives domain data service function information corresponding to one or more domain data agent network elements. In this way, the domain data orchestration network element can receive the data service functions reported by the domain data agent network elements.

[0018] In a possible design approach, the communication method provided in the first aspect may further include the following. That is, the domain data orchestration network element transmits first data service function information to the data orchestration network element. The first data service function information may be determined based on a part of one or more domain data service function information.

[0019] In this way, the domain data orchestration network element can collect statistical information on the domain data service function information of the domain data agent network elements within the local domain, obtain the first data service function information, and transmit the first data service function information to the data orchestration network element.

[0020] In a possible design approach, the domain data service function information of any one of one or more domain data agent network elements may include, but is not limited to, one or more of the following. That is, the identifier of any one domain data agent network element, the location information of any one domain data agent network element, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

[0021] In a possible design approach, the operations indicated by the operation configuration information include one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service request network elements. It should be noted that the data service functions of the domain data agent - network elements are not limited to these. In this way, the domain data agent - network elements can execute 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 operations, and rate matching.

[0023] In a possible design approach, the first requirement information includes one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0024] In a possible design approach, 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 approach, any one of one or more domain data agent - network elements is a data agent - network element within the core network domain. Or, one or more domain data agent - network elements are data agent - network elements within the access network domain.

[0026] For example, the data agent network elements within the core network domain may include, but are not limited to, one or more of the following. That is, core network domain data agent network elements and stand-alone data agent network elements. The data agent network elements within the access network domain may include, but are not limited to, one or more of the following. That is, access network domain data agent network elements, terminal domain data agent network elements, and stand-alone data agent network elements.

[0027] In a possible design approach, the initial data may include the following. That is, 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. That is, data on the terminal device side, data of each functional node on the access network device side, data of each functional node on the transfer network side, data of each functional node on the core network side, data of each functional node for operations, administration and maintenance (OAM), and synthetic data.

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

[0030] According to a second aspect, a communication method is provided. The present communication method includes the following. That is, a data orchestration network element receives a first service request message. The data orchestration network element determines first requirement information and second requirement information based on requirement information, first data service function information, and second data service function information. The data orchestration network element transmits the first requirement information and the second requirement information. The requirement information is a service requirement related to first data, which is a service requirement determined based on the service requested by using the first service request message. The first data service function information corresponds to a first domain data orchestration network element, the second data service function information corresponds to a second domain data orchestration network element, the first requirement information is a service requirement related to first data, which is a service requirement corresponding to the first domain data orchestration network element, and the second requirement information is a service requirement related to first data, which is a service requirement corresponding to the second domain data orchestration network element.

[0031] In a possible design, 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 the following. That is, the data orchestration network element receives the first data service function information from the first domain data orchestration network element. The first data service function information may be determined based on a part of one or more domain data service function information.

[0033] In a possible design approach, the communication method provided in the second aspect may further include the following. That is, the data orchestration network element receives second data service function information from the second domain data orchestration network element. The second data service function information may be determined based on a part of one or more domain data service function information.

[0034] In a possible design approach, a part of one or more domain data service function information corresponds one-to-one with one or more domain data agent network elements, and 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. That is, the identifier of any one domain data agent network element, the location information of any one domain data agent network element, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

[0035] In a possible design approach, the first service request message is from the service request network element, and the communication method provided in the second aspect may further include the following. That is, the data orchestration network element sends a second verification request message to the trust anchor. The second verification request message may be for requesting to verify whether the service request network element has the access right to the first data.

[0036] In a possible design approach, 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 following. That is, the data orchestration network element sends first instruction information to the first domain data orchestration network element and / or the second domain data orchestration network element. The first instruction 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 within the core network domain or a data agent network element within the access network domain.

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

[0038] In a possible design approach, the requirement information may include one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with the service request network element, data protection, and data compression.

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

[0040] In a possible design approach, 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 may be an access network domain data orchestration network element.

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

[0042] In a possible design approach, the first data may include the following. That is, data collected from a mobile communication network or synthetic data.

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

[0044] According to a third aspect, a communication method is provided. This communication method includes the following. That is, a first domain data agent network element receives operation configuration information. The first domain data agent network element processes the first data based on the operation indicated by the operation configuration information to obtain first information. When the operation configuration information indicates that the first domain data agent network element communicates 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, when the operation configuration information indicates that the first domain data agent network element communicates 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 the operation to be performed by the first domain data agent network element on the first data.

[0045] In a possible design approach, the operations indicated by the operation configuration information may include one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interactions with service request network elements.

[0046] In a possible design approach, for the first domain data agent network element to process the first data based on the operations indicated by the operation configuration information and obtain the first information includes the following. That is, 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, and the first domain data agent network element receives 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. That is, 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 approach, the data request message may further include security information, and the security information is used to verify whether the first domain data agent network element has the access right to the first data.

[0048] In a possible design approach, for the first domain data agent network element to process the first data based on the operations indicated by the operation configuration information and obtain the first information includes the following. That is, the first domain data agent network element processes the second information based on the operations indicated by the operation configuration information and obtains the first information. 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 approach, the communication method provided in the third aspect may further include the following. That is, the first domain data agent network element receives a first verification response message from the trust anchor. The first verification response message may indicate that the second domain data agent network element has the right to access the first data of the first domain data agent network element.

[0050] In a possible design approach, the communication method provided in the third aspect may further include the following. That is, the first domain data agent network element sends a third verification request message to the trust anchor. The third verification request message may be for requesting to verify whether the second domain data agent network element has the right to access the first data of the first domain data agent network element.

[0051] In a possible design approach, the communication method provided in the third aspect may further include the following. That is, the first domain data agent network element sends domain data service function information to the domain data orchestration network element.

[0052] In a possible design approach, the domain data service function information may include one or more of the following. That is, the identifier of the first domain data agent network element, the location information of the first domain data agent network element, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

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

[0054] In a possible design approach, the first domain data agent network element can 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 stand-alone data agent network element.

[0055] In a possible design approach, the initial data may include the following. That is, data collected from a mobile communication network, or synthetic data.

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

[0057] According to a fourth aspect, a communication device is provided. The present communication device includes the following. That is, a transceiver module and a processing module. The transceiver module is configured to receive first requirement 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 elements based on the first requirement information and a part of one or more domain data service function information. The transceiver module is further configured to transmit the operation configuration information. The first requirement information is a service requirement regarding first data and is a service requirement corresponding to the communication device. The part of one or more domain data service function information corresponds one-to-one with 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 requirement information corresponds to at least one of the parts of one or more domain data service function information. 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 first data by any one of the domain data agent network elements.

[0058] In a possible design manner, the processing module is configured to determine at least one domain data agent network element based on the first requirement information and a part of one or more domain data service function information. The transceiver module is further configured to perform the following. That is, when any one of the at least one domain data agent network elements has an access right to the first data, based on the first requirement information and a part of one or more domain data service function information, determine operation configuration information corresponding to any one of the at least one domain data agent network elements.

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

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

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

[0062] In a possible design approach, the transceiver module is further configured to send first communication information. The first communication information may indicate information regarding a domain data agent network element that is within at least one domain data agent network element and that communicates directly with the service request network element.

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

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

[0065] In a possible design approach, the domain data service function information of any one of one or more domain data agent network elements may include one or more of the following. That is, the identifier of any one domain data agent network element, the location information of any one domain data agent network element, a data collection function, a data preprocessing function, a data storage function, a data reporting function, a data analysis function, a function to interact with a service request network element, a data protection function, and a data compression function.

[0066] In a possible design approach, 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 a service request network element.

[0067] In a possible design approach, the first requirement information includes one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with a service request network element, data protection, and data compression.

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

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

[0070] In a possible design approach, the initial data may include the following. That is, 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 the following. That is, a receiving module and a transmitting module. 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. The storage module stores programs or instructions. When the processing module executes the programs or instructions, the communication device according to the fourth aspect can execute 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, for example, a core network domain data orchestration network element or an access network domain data orchestration network element, or a chip (system), another component, or an assembly that can be disposed within the domain data orchestration network element. This is not limited in this application.

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

[0075] According to a fifth aspect, a communication device is provided. The present communication device includes the following. That is, 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 function information, and second data service function 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 regarding first data, which is a service requirement determined based on the service requested by using the first service request message. The first data service function information corresponds to a first domain data orchestration network element, and the second data service function information corresponds to a second domain data orchestration network element. The first requirement information is a service requirement regarding first data, which is a service requirement corresponding to the first domain data orchestration network element. The second requirement information is a service requirement regarding first data, which is a service requirement corresponding to the second domain data orchestration network element.

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

[0077] In a possible design, the transceiver module is further configured to receive the first data service function information from the first domain data orchestration network element. The first data service function information may be determined based on a part of one or more domain data service function information.

[0078] In a possible design approach, the transceiver module is further configured to receive second data service function information from a second domain data orchestration network element. The second data service function information may be determined based on a portion of one or more domain data service function information.

[0079] In a possible design approach, a portion of one or more domain data service function information corresponds one-to-one with one or more domain data agent network elements, and 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. That is, the identifier of any one domain data agent network element, the location information of any one domain data agent network element, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

[0080] In a possible design approach, the first service request message is from a service request 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 for requesting to verify whether the service request network element has the access right to the first data.

[0081] In a possible design approach, the first service request message is from a service request network element, and the transceiver module is further configured to send the first indication information to a first domain data orchestration network element and / or a second domain data orchestration network element. 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 within the core network domain or a data agent network element within the access network domain.

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

[0083] In a possible design approach, the requirement information may include one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with the service request network element, data protection, and data compression.

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

[0085] In a possible design approach, 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 may be an access network domain data orchestration network element.

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

[0087] In a possible design approach, the initial data may include the following. That is, 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 the following. That is, a receiving module and a transmitting module. 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. The storage module stores programs or instructions. When the processing module executes the programs or instructions, the communication device according to the fifth aspect can execute 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), another component, or an assembly that can be disposed within the data orchestration network element. This 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 in the second aspect. For details, it will not be described again in this specification.

[0092] According to a sixth aspect, a communication device is provided. The present communication device includes the following. That is, a transceiver module and a processing module. The transceiver module is configured to receive operation configuration information. The processing module is configured to process first data based on the operation indicated by the operation configuration information to obtain first information. The transceiver module is further configured to perform the following. That is, when the operation configuration information indicates that the communication device communicates with a second domain data agent network element, to transmit the first information to the second domain data agent network element. Alternatively, the transceiver module is further configured to perform the following. That is, when the operation configuration information indicates that the communication device communicates with a service request network element, to transmit the first information to the service request network element. The operation configuration information indicates an operation to be performed by the communication device on the first data.

[0093] In a possible design manner, the operation indicated by the operation configuration information may include one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interaction with a service request network element.

[0094] In a possible design manner, the transceiver module is further configured to transmit a data request message to a third domain data agent network element based on the operation 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 may be for requesting one or more of the following data. That is, 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 approach, the data request message may further include security information, and the security information is used to verify whether the communication device has access rights to the original data.

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

[0097] In a possible design approach, the transceiver module is further configured to receive a first verification response message from the trust anchor. The first verification response message may indicate that the second domain data agent network element has access rights to the original data of the communication device.

[0098] In a possible design approach, the transceiver module is further configured to send a third verification request message to the trust anchor. The third verification request message may be for requesting to verify whether the second domain data agent network element has access rights to the original data of the communication device.

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

[0100] In a possible design approach, the domain data service function information may include one or more of the following: namely, the identifier of the communication device, the location information of the communication device, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

[0101] In a possible design approach, the transceiver module is further configured to receive, 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.

[0102] In a possible design approach, the present communication device can 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 stand-alone data agent network element.

[0103] In a possible design approach, the first data can include the following. That is, data collected from the mobile communication network or synthetic data.

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

[0105] Optionally, the communication device according to the sixth aspect may further include a storage module. The storage module stores programs or instructions. When the processing module executes the programs or instructions, the communication device according to the sixth aspect can execute 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, for example, 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 stand-alone data agent network element, or it may also be a chip (system), another component, or an assembly that can be disposed within the first domain data agent network element. This is not limited in this application.

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

[0108] According to a seventh aspect, a communication device is provided. This communication device includes a processor. The processor is coupled to a memory, and the memory is configured to store a computer program.

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

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

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

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

[0113] In the present application, the communication device according to the seventh aspect can 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 a domain data orchestration network element, a data orchestration network element, or a first domain data agent network element.

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

[0115] According to the eighth aspect, a communication system is provided. This 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. This communication system may further include a service request network element.

[0116] Alternatively, the present communication system includes the following. That is, a communication device according to a fourth aspect, which is configured to implement the method according to the first aspect. And a communication device according to a fifth aspect, which is configured to implement the method according to the second aspect. The present communication system may further include a communication device according to a sixth aspect, which is configured to implement the method according to the third aspect. The present communication system may further include a service request network element.

[0117] According to a ninth aspect, a chip system is provided. The present chip system includes a logic circuit and input / output ports. The logic circuit is configured to implement the processing functions in the first aspect to the third aspect, and the input / output ports are configured to implement the receiving function and the transmitting function in the first aspect to the third aspect. Specifically, the input port may be configured to implement the receiving function in the first aspect to the third aspect, and the output port may be configured to implement the transmitting function in the first aspect to the third aspect.

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

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

[0120] According to a tenth aspect, a computer-readable storage medium is provided. The present computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed on a computer, a method according to any possible implementation in the first aspect to the third aspect is executed.

[0121] According to an eleventh aspect, there is provided a computer program product including a computer program or instructions. When the computer program or instructions are executed on a computer, a method according to any possible implementation in the first aspect to the third aspect is executed.

Brief Description of the Drawings

[0122]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6a

Figure 6b

Figure 6c

Figure 6d

Figure 6e

Figure 7

Figure 8A

Figure 8B

Figure 8C

Figure 9

Embodiments for Carrying Out the Invention

[0123] Hereinafter, with reference to the accompanying drawings, the technical solution of the present application will be described.

[0124] The technical solution in the embodiment of the present application can be applied to various communication systems, such as 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 vehicle Internet 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] In this application, all aspects, embodiments, or features are presented by describing a system that may include a plurality of devices, assemblies, modules, and the like. It should be recognized and understood that each system may include another device, assembly, module, and the like, and / or may not include all of the devices, assemblies, modules, and the like described with reference to the accompanying drawings. Also, combinations of these solutions may be further used.

[0126] In the embodiments of this application, terms such as "example" and "for example" are used to give examples, illustrations, or explanations. No embodiment or design solution described as an "example" in this application should be described as being more preferred or having more advantages than another embodiment or design solution. Exactly, the term "example" is used to present a concept in a specific manner.

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

[0128] The network architectures and service scenarios described in the embodiments of this application are intended to more clearly explain the technical solutions in the embodiments of this application and do not constitute a limitation to the technical solutions provided in the embodiments of this application. A person skilled in the art can recognize the following. That is, with the development of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0129] To facilitate understanding of the embodiments of the present application, the communication system shown in FIG. 1 will first be used as an example to describe in detail a communication system applicable to the embodiments of the present application. For example, FIG. 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 FIG. 1, the communication system includes a data orchestration (DO) network element and a data agent (DA) network element. There may be only one or more data orchestration network elements, and there may be only one or more data agent network elements.

[0131] The data orchestration network element obtains a service request, converts the service request into a service requirement for data, determines a data agent network element for implementing the service requirement, and may adjust the function of the data agent network element, whereby the data agent network element executes corresponding operations, establishes a dynamic logical network topology, and implements the corresponding service requirement.

[0132] For example, the data orchestration network element may be deployed within any core network element, transfer network (TN) network element, or access network device, or another network element (such as 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 hierarchically deployed on the core network side, or may be hierarchically deployed on the access network device side. 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 independently deployed within the network as a network function (NF), or may be independently deployed within the network as a network element. In an actual deployment, one or more NFs may form a network element.

[0133] The data agent network element may implement one or more of the following functions, namely, data collection, preprocessing, storage, analysis, data protection, and the like. Different data agent network elements may have the same data service function, or may have different data service functions, and may implement the same function or different functions. The data agent network element may interact with the data orchestration network element to obtain related operations that need to be executed to meet service requirements and execute the operations. The data agent network element may establish a logical network topology to form a dynamic data pipeline (or also called a data flow, service logic, function chain, operation chain, or the like). The data pipeline includes functions corresponding to one or more data agent network elements based on service requirements, and the output of the previous function serves as 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 device, or access network device, or another network element (such as an operations, administration and maintenance (OAM) network element, etc.), or the data agent network element may be deployed independently. For example, the data agent network element may be deployed independently in the network as a network function NF, or may be deployed independently in the network as a network element.

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

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

[0137] Optionally, the data agent network element can be optionally deployed within any core network element, transport network network element, terminal device, or access network device, or another network element based on the resources and / or functions of the network element to implement cross-domain data collection. The data agent network element can collect data from across the domain and implement the management and coordination of cross-domain data.

[0138] For example, as a network function NF, the data agent network element can align cloud-native SBI encryption, NF dynamic instantiation, and the K8S deployment encryption environment. Also, the performance loss and impact on the security of the NF can be minimized.

[0139] When there are multiple data agent network elements in a communication system, some data agent network elements can be disposed within a network device (referring to any core network element, terminal device, access network device, or another network element), and some data agent network elements are deployed independently. Alternatively, all of the multiple data agent network elements can be disposed within the network device, or all of the multiple data agent network elements are deployed independently. This is not limited in this 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. This is not limited in this application.

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

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

[0143] The core network element is arranged on the network side of the communication system and can be configured to provide network services to access network devices, terminal devices, and the like. The core network element may include one or more of the following, but is not limited thereto. That is, 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, and mainly executes functions such as mobility management and access authentication / authorization. Further, the mobility management network element may also be responsible for transferring user policies between the terminal and the policy control function (PCF) network element.

[0145] The session management network element is mainly used for session management (such as creation or deletion), maintaining session context and user plane transfer tunnel information, allocating and managing Internet protocol (IP) addresses for terminal devices, managing the user plane function interface, and selecting terminations that can manage the policy control interface and the charging function interface, downlink data notification, and the like.

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

[0147] The user plane network element, as an interface to the data network, finishes functions such as user plane data transfer, session / flow level-based charging statistics information 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 can be a user plane function (UPF) network element.

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

[0149] The network exposure network element can be configured to perform the following. That is, it provides a framework, authentication, and interfaces related to the network function exposure, and transfers information between the 5G system network function and another network function. In a 5G communication system, the network exposure network element can be a network exposure function (NEF) network element, and is mainly configured to expose the services and functions of 3GPP network functions to the AF, and can further enable the AF to provide information to 3GPP network functions.

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

[0151] The NWDAF network element can be configured to perform the following. That is, collect data from the core network and the OAM network element and feedback the data analysis result to the NF, AF network element, or OAM network element. For example, the NWDAF network element can collect OAM data from the OAM network element and non-OAM data from the NF in the core network or the AF network element. The non-OAM data can include non-OAM data collected at the levels of terminals, terminal groups, and services.

[0152] The OAM network element can collect data from the access network device.

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

[0154] For example, the access network device in the embodiments of the present application can be any communication device having a wireless transceiver function and configured to communicate with a terminal device. The access network device includes, but is not limited to, the following. That is, 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) in a wireless fidelity (Wi-Fi) system, a wireless relay node, a wireless backhaul node, and a transmission point (TP) or a transmission reception point (TRP). Alternatively, the access network device may be a gNB or a transmission point (TRP or TP) in a 5G system such as an NR system, one or a group of antenna panels (including a plurality of antenna panels) of a base station in a 5G system, or a network node that forms a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), or may be a satellite and a drone.

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

[0156] The terminal device is a terminal having a wireless transceiver function that accesses a communication system, or a chip or chip system that can be disposed within the terminal. In this application, the 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 device, user agent, or user device. The terminal in the embodiments of this application includes a mobile phone, tablet computer (tablet), unmanned aerial vehicle, computer having a wireless transceiver function, customer premise equipment (CPE), virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, mobile phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device or computing device having a wireless communication function, another processing device, in-vehicle device, or 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 can be a courier terminal in intelligent logistics (for example, a device capable of monitoring the position of a freight vehicle, or a device capable of monitoring the temperature and humidity of goods, etc.), a wireless terminal in intelligent agriculture (for example, a wearable device capable of collecting relevant data of poultry and livestock, etc.), a wireless terminal in intelligent architecture (for example, a smart elevator, a fire monitoring device, or a smart meter, etc.), a wireless terminal in intelligent healthcare (for example, a wearable device capable of monitoring the physiological state of humans or animals, etc.), a wireless terminal in intelligent transportation (for example, an intelligent bus, an intelligent vehicle, a shared bicycle, a charging stand monitoring device, an intelligent traffic signal, or an intelligent monitoring and intelligent parking device, etc.), or a wireless terminal in intelligent retail (for example, a vending machine, a self-service checkout machine, or an unmanned convenience store, etc.). As another example, the terminal device in the present application can be an in-vehicle module, an in-vehicle assembly, an in-vehicle component, an in-vehicle chip, or an in-vehicle unit disposed in a vehicle as one or more components or units. The vehicle can implement the method provided in the present application by using an in-vehicle module, an in-vehicle assembly, an in-vehicle component, an in-vehicle chip, or an in-vehicle unit disposed in the vehicle. The terminal device in the present application may be a smart internet of things (SIoT) terminal device or a non-SIoT terminal device, and has specific computing, storage, and other functions. The non-SIoT terminal device can collect data by using a gateway of the internet of things. For example, the non-SIoT terminal device may be a terminal with limited computing functions, such as a sensor with a single function. Optionally, a data agent network element may be disposed in the SIoT terminal device, or the SIoT terminal device may implement the function of the data agent network element.

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

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

[0160] As shown in FIG. 2, the present application proposes a case where a normalized data service architecture is constructed based on a data plane to provide a data service to a service request network element. The data service architecture may include one or more of the following, but is not limited thereto. That is, 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] The 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). The trust anchor may store data that cannot be tampered with, such as public keys, identifiers, or indexes of terminal devices or network elements, transaction-related data, or important data that cannot be tampered with.

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

[0163] For example, the trust anchor may be deployed in a distributed manner or in a centralized manner. A trust anchor deployed in a distributed manner can be a node within the distributed ledger technology ( DLT ) (such as a blockchain, etc.) or something similar. A trust anchor deployed in a centralized manner can be implemented through the reconstruction and development 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 procedure through data access control such as authentication, authorization, and access control, and in combination with a data security and privacy protection technology repository, can support the security and privacy protection of the entire data service procedure, can support trusted data service requirements such as source tracing, auditing functions, and user data self-control, can support meeting the requirements of data sharing and transactions in trusted mechanisms such as source tracing and auditing functions, can meet compliance requirements such as the Personal Information Protection Law (PIPL) and the General Data Protection Regulation (GDPR), and can provide trusted data services. Compliance detection of user data processing can implement a decentralized verification mechanism to avoid the problems of centralization reliability and failures.

[0165] The service request network element may include an application, an application server, a network service ( NS ) network element, or the like. The application may be an application of an operator (or a communication service provider (CSP)) and may be used for network planning and optimization, network artificial intelligence (AI), and / or the like, or may be an application outside the mobile communication network (sometimes also referred to as a third-party application). The service request network element may be independently deployed in the network as a network function or a network element.

[0166] The data storage network element can store various types of data, such as streaming data, batch data, log information, parameter configuration information of the AI model, and intermediate data, and can expand the storage function of the data agent network element. For example, the DSF network element may be a centralized database, or may also be a distributed database, such as a distributed hash table DHT or an interplanetary file system (IPFS). For example, the data storage network element may be a data storage function (DSF) network element, or may also be developed from a data storage function network element. The data storage network element can be deployed in the network as an NF or a network element.

[0167] For example, FIG. 3 is a diagram showing the functions of the data service architecture according to the embodiments of the present application.

[0168] Hereinafter, with reference to FIG. 3, the functions of the data orchestration network element will be described.

[0169] Referring to FIG. 3, the functions that can be implemented by the data orchestration network element include, but are not limited to, one or more of the following. That is, the interface for the application, the conversion of requirements, the data agent orchestration, the data agent management, the data protection, the interface for the network service (NS), and the interface for the trust anchor.

[0170] Interface to the Application: The data orchestration network element can interact with the service request network element through the interface to the application. For example, the data orchestration network element receives a service request from the service request network element. For example, the service request can be a requirement embedded according to a standard template. For example, the standard template can be a service level agreement (SLA).

[0171] Requirement Transformation: The data orchestration network element transforms the service request into a service requirement for the functions of the data agent network element. For example, the data orchestration network element transforms requirements such as a service level agreement into requirements for the corresponding resources and network configurations.

[0172] Data Agent Orchestration: The data agent network element is adjusted based on the data service functions of the data agent network element to form a dynamic logical network topology to meet the service requirements.

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

[0174] Optionally, a data orchestration network element may negotiate with another network service network element in the process of executing data agent orchestration. For example, when it is necessary to use algorithms and computing capabilities, the data orchestration network element may cooperate with another network service network element to select corresponding AI algorithms and computing capabilities, and the network service network element promotes the algorithms.

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

[0176] Data agent management: Manage the registration, deregistration, and the like of requests requested by the data orchestration network element by the data agent network element, and receive data service functions and the like reported by the data agent network element.

[0177] Data protection: The data protection function can be implemented by using a data protection technology repository (DPTR). The data protection technology repository may include a plurality of algorithms, such as differential privacy, homomorphic encryption, multiparty computation, and zero-knowledge proof, in a data security and privacy protection algorithm repository. The data orchestration network element can, if necessary, promote or update information about the data protection technology repository to the data agent network element, which functions as the data protection technology (DPT) of the data agent network element. The data protection technology repository can be loosely coupled with the data orchestration network element. The data protection technology repository can be a common function of network elements in the data service architecture and can develop and optimize independently. The independent data protection technology repository facilitates compliance detection for end-to-end (E2E) data processing.

[0178] For example, the information about the data protection technology repository may include an identifier, an index, and configuration information that are those of the data protection technology repository, as well as the data protection technology repository itself.

[0179] Interface to network services: The data orchestration network element can interact with the network service network element through an interface to network services. For example, the data orchestration network element can negotiate with the network service network element based on service requirements. For example, when it is necessary to use algorithms and computing capabilities, the data orchestration network element can cooperate with another network service network element.

[0180] Trust Anchor Agent: The Trust Anchor Agent is an interface between the data orchestration network element and the Trust Anchor. The data orchestration network element can interact with the Trust Anchor by using the Trust Anchor Agent function.

[0181] It should be noted that in the embodiments of the present application, the data orchestration network element can be divided into functional modules based on the functions described above or the embodiments of the following methods. 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 the division into functions or modules in the embodiments of the present application is only an example and is merely a logical function division. At the actual implementation, another division method may be used.

[0182] Hereinafter, with reference to FIG. 3, the functions of the data agent network element will be described.

[0183] Referring to FIG. 3, the functions that can be implemented by the data agent network element include, but are not limited to, one or more of the following. That is, control, data collection, preprocessing, storage, application programming interface, data analysis, and data protection.

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

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

[0186] For example, the data orchestration network elements adjust the data agent network elements to form a dynamic logical network topology, and the data agent network elements adjust the functions of the data agent network elements to form a data pipeline to implement automatic data management and dynamic on-demand configuration, quickly respond to new services and new requirements, support the implementation of rich application scenarios, enable new data services to quickly enter the market, and shorten the time to market (TTM).

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

[0188] In this application, it should be noted that without being limited to the classification of data, the data may be classified into more types, or may be classified into fewer types, or the data may be classified into types from another perspective, or the data may not need to be classified into types.

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

[0190] Pre-processing: Pre-processing refers to performing cleaning, filling, smoothing, combination, normalization, and consistency checking on the collected original data, field extraction of the original data, format conversion, elimination of redundant data, compression, filter extraction, merging, and / or other operations to improve data quality and build a foundation for subsequent processing (such as analysis, etc.). The original data is deleted, which may result in problems such as data loss, data noise, data redundancy, and / or imbalance of the data set.

[0191] Storage: Supports centralized storage and distributed storage. Optionally, data that requires strict access protection or privacy protection, such as user subscription data, etc., is locally stored within the data agent network element.

[0192] Application programming interface: Each function of the data agent network element can directly provide services to service requesters through the application programming interface ( API ) in a direct manner.

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

[0194] Data protection: Data is processed by using techniques such as k-anonymity, l-diversity, and differential privacy, which prevent attackers from directly obtaining confidential information from the de-identified data and protect data privacy. Information about the data protection technology repository may be pre-installed in the data agent network elements or may be driven by the DO as needed, and security and privacy protection for the data are implemented at each level of the data agent network elements.

[0195] In the embodiments of the present application, it should be noted that 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. In the embodiments of the present application, it should be noted that the division into functions or modules is an example and is merely a logical function division. At the actual implementation, another division method may be used.

[0196] FIG. 4 is a schematic diagram showing a logical network topology according to an embodiment of the present application. Hereinafter, with reference to FIG. 4, the logical network topology formed by adjusting the data agent network element by the data orchestration network element ( D A) will be described.

[0197] As shown in FIG. 4, the logical network topology may include, but is not limited to, the following. That is, a star-type logical network topology, a mesh-type logical network topology, and a hybrid-type logical network topology.

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

[0199] For example, in a mesh-type logical network topology, data linkage is executed between DAs, and any DA can be selected to directly interact with service request network elements.

[0200] For example, in a hybrid-type (or also called hybrid hierarchical type) logical network topology, the DA as an aggregation node can hierarchically collect information regarding the common node DA and further process the collected information. Similar to the star-type logical network topology, the DA as an aggregation node can directly interact with service request network elements, and the common node DA can interact with service request network elements via the DA as an aggregation node. This is not limited in the present application. The DA that directly interacts with service request network elements can be any DA.

[0201] It should be noted that the logical network topology shown in FIG. 4 is merely an example provided in the present application. In actual applications, as long as the data orchestration network elements can implement data services, they can adjust the data agent network elements ( D A) as needed to form a logical network topology in any form.

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

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

[0204] For example, as shown in FIG. 5, the operation set for data agent network element 1, which is obtained by data agent network element 1 from the data orchestration network element, includes the following. That is, after performing preprocessing such as merging on the data obtained from another data agent network element, analyzing the data to obtain an analysis result, and sending the analysis result to the service request network element. Data agent network element 1 adjusts its function to form operation chain 1 shown in FIG. 5. That is, collecting data, then preprocessing the data, analyzing the preprocessing result, and sending the analysis result to the service request network element through an application programming interface.

[0205] In another example, as shown in FIG. 5, assume that the operation set for data agent network element 1, which is obtained by data agent network element 1 from the data orchestration network element, includes the following. That is, when the collected data is transmitted to data agent network element 2, data agent network element 1 adjusts its function to form operation chain 2 shown in FIG. 5. That is, collecting data and sending the data to data agent network element 2.

[0206] It should be noted that the operation chains 1 and 2 shown in FIG. 5 are merely examples provided in this application and do not constitute restrictions on the order in which the functions of the data agent network elements are executed. The order in which the functions of the data agent network elements are executed can be dynamically adjusted based on service requirements.

[0207] For example, FIGS. 6a to 6e are diagrams showing some network architectures according to embodiments of the present application. The communication system shown in FIG. 1 is applicable to the network architectures shown in FIGS. 6a to 6e.

[0208] FIG. 6a is a diagram showing a network architecture used when all of the core network devices and access network devices are service-oriented. FIG. 6b is a diagram showing a network architecture used when the access network devices are not service-oriented and the core network is service-oriented. FIG. 6c is a diagram showing a network architecture used when the access network devices are not service-oriented and the core network is service-oriented (the N4 interface is optional). FIG. 6d is a diagram showing a network architecture in which network elements are directly interconnected.

[0209] Referring to FIGS. 6a to 6c, the network architecture may include one or more of the following, but is not limited thereto. That is, 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, refer to the descriptions in FIGS. 1 to 5. Details will not be described again in this specification. The network architecture may further include one or more of the following, but is not limited thereto. That is, a mobility management network element (FIGS. 6b and 6c). The network architecture may further include one or more of the following, but is not limited thereto. That is, a session management network element (FIG. 6c). The core network elements shown in FIGS. 6a to 6c may include any core network elements other than the user plane network element, the mobility management network element, and / or the session management network element.

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

[0211] The data orchestration network element is a service-oriented interface N DOThrough interaction with another network element (e.g., service request network element, data agent network element, core network element, and trust anchor, etc.), the data agent network element has a service-oriented interface N DA Through interaction with another network element (e.g., service request network element, data orchestration network element, core network element, terminal device, access network device, data storage network element, and trust anchor, etc.), the data storage network element has a service-oriented interface N DSF Through interaction with another network element (e.g., data agent network element, core network element, terminal device, and access network device, etc.), the trust anchor has a service-oriented interface N TA Through interaction with another network element (e.g., data orchestration network element, data agent network element, core network element, terminal device, access network device, data storage network element, and trust anchor, etc.).

[0212] In the network architecture shown in FIGS. 6a to 6c, the service-oriented interface can be used to improve the independence between network functions, realize deployment flexibility and efficient expandability, and improve the development efficiency of new functions.

[0213] Referring to FIG. 6d, the network architecture may include one or more of the following, but is not limited thereto. That is, service request network element, data orchestration network element, access network domain data orchestration network element (RAN-DO), CN domain data orchestration network element (CN-DO), access network device ( RAN ), a core network element, a terminal device, a trust anchor, and a data storage network element.

[0214] In the architecture shown in FIG. 6d, the data orchestration network element is hierarchically deployed. The data orchestration network element can manage a RAN domain data orchestration network element and a CN domain data orchestration network element. The RAN domain data orchestration network element can directly interact with the CN domain data orchestration network element. The RAN domain data orchestration network element can directly interact with access network devices. The CN domain data orchestration network element can directly interact with core network elements. The trust anchor can directly interact with any network element within the network architecture. The data storage network element can directly interact with terminal devices, access network devices, and core network elements.

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

[0216] FIG. 6e is a diagram showing a network architecture in which a data orchestration network element is hierarchically deployed according to an embodiment of the present application.

[0217] Referring to FIG. 6e, the network architecture may include, but is not limited to, one or more of the following. That is, 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 stand-alone 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 FIG. 6e, the data orchestration network element is hierarchically deployed. The data orchestration network element may manage the RAN domain data orchestration network element and the CN domain data orchestration network element. The RAN domain data orchestration network element may directly interact with the CN domain data orchestration network element. The RAN domain data orchestration network element may directly interact with the access network domain data agent network element, the terminal domain data agent network element (UE-DA), and a stand-alone data agent network element (not shown in FIG. 6e). The CN domain data orchestration network element may directly interact with the core network domain data agent network element and the stand-alone data agent network element. In FIG. 6e, an example where the CN domain data orchestration network element directly interacts with the stand-alone data agent network element is used.

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

[0220] Optionally, in the architecture shown in FIG. 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 collectively referred to as domain data orchestration network elements. The access network domain data agent network element, the terminal domain data agent network element, the core network domain data agent network element, and the stand-alone data agent network element may also be collectively referred to as domain data agent network elements.

[0221] Optionally, the domain data agent network element may be classified into a data agent network element within the core network domain and a data agent network element within the access network domain. The data agent network element within the core network domain may include one or more of the following, but is not limited thereto. That is, the core network domain data agent network element and the stand-alone data agent network element. The data agent network element within the access network domain may include one or more of the following, but is not limited thereto. That is, the access network domain data agent network element, the terminal domain data agent network element, and the stand-alone data agent network element.

[0222] It should be noted that the domain data agent network element can implement the functions of the data agent network element described in FIGS. 1 to 6d. In this specification, the data agent network element is simply referred to as the domain data agent network element.

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

[0224] In the network architecture shown in FIG. 6e, the cross-domain data orchestration network element and the domain data orchestration network element can execute automatic orchestration for the domain data agent network element (a network element capable of implementing the functions of the data agent network element), configure corresponding operations, and implement data service automation. For example, a series of functional actions are stored in the data orchestration network element ( Cross-domain data orchestration network element and / or domain data orchestration network element) in the form of a "pre-defined" template. After receiving a service request, the cross-domain data orchestration network element coordinates the domain data orchestration network element to adjust the domain data agent network element, implement the configuration between terminals of the data service, form a logical network topology, thereby implementing the automation of data service provision.

[0225] Hereinafter, the functions of the cross-domain data orchestration network element and the functions of the domain data orchestration network element will be described.

[0226] For example, the functions that can be implemented by the cross-domain data orchestration network element include, but are not limited to, one or more of the following. That is, an interface for an application, requirement conversion, data protection, an interface for a trust anchor, and management of the life cycle of a data service task, for example, assignment or deletion of a data service task ID.

[0227] Requirement conversion: Service requests are converted 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 communicates directly with the service requester belongs is determined.

[0228] For example, the data service type may include, but is not limited to, one or more of the following. That is, output of raw data, provision of preprocessed data, data storage, data analysis, tracing of data sources, data dictionaries, privacy and security of data, and data sharing or transactions.

[0229] Data protection: Refer to the description of the functions of the data orchestration network element in FIG. 2. Details will not be described again in this specification.

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

[0231] Data agent management: Manages registrations, deregistrations, and the like requested by the domain data agent network element, and receives data service functions and the like reported by the domain data agent network element.

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

[0233] Data agent orchestration: Receives requirements from the cross-domain data orchestration network element, and the data agent network element is adjusted based on the requirements and the data service function of the data agent network element to form a dynamic logical network topology in order to meet the service requirements.

[0234] Data protection: Refer to the description of the function of the data orchestration network element in FIG. 2. Details will not be described again in this specification.

[0235] Selection of Cross-Domain Next-Hop Data Agent Network Elements: The domain data orchestration network element may be a data agent network element within one or more data agent network elements in a local domain, and may select a data agent network element that interacts with a data agent network element in another domain.

[0236] For example, CN-DO may be a data agent network element within one or more data agent network elements in the CN domain, and may select a data agent network element (such as CN domain data agent network element 1) that interacts with a data agent network element in the access network domain. RAN-DO may be a data agent network element within one or more data agent network elements in the RAN domain, and may select a data agent network element (such as RAN domain data agent network element 1) that interacts with a data agent network element in the core network domain. The selected CN domain data agent network element 1 may directly interact 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 through the CN domain data agent network element 1 and the RAN domain data agent network element 1.

[0237] The service-oriented interface in a scenario where the data orchestration network element is hierarchically expanded will be described below.

[0238] Service - Oriented Interface between Cross - Domain Data Orchestration Network Elements and Service - Request Network Elements: The service - oriented interface can be used by the cross - domain data orchestration network element to receive service requests from the service - request network element, to send information about data agent network elements that communicate directly with the service - request network element to the service - request network element, and for similar purposes.

[0239] Service - Oriented Interface between Cross - Domain Data Orchestration Network Elements and Domain Data Orchestration Network Elements: The service - oriented interface can be used by the cross - domain data orchestration network element to send to the domain data orchestration network element a data service task identifier, data service tasks / functions within the local domain, and a notification indicating whether data agent network elements that directly interact with the service - request network element are within this domain. This service - oriented interface can be used by the domain data orchestration network element to send to the cross - domain data orchestration network element statistical information about the functions of data agent network elements within the local domain and selected domain data agent network elements that directly interact with the service - request network element.

[0240] Service - Oriented Interface between Domain Data Orchestration Network Elements: Among domain data orchestration network elements, information about cross - domain next - hop data agent network elements, such as the address or identifier of the data agent network element, is exchanged.

[0241] Service - oriented interface between the domain data orchestration network element and the domain data agent network element: The service - oriented interface can be used for the interaction between the domain data agent network element and the domain data orchestration network element. For example, the service - oriented interface can be used by the domain data agent network element to request registration, deregistration, and the like from the domain data orchestration network element, and can be used to receive the data service functions reported by the domain data agent network element. This service - oriented interface can be used by the domain data agent network element to periodically report the heartbeat to the domain data orchestration network element. This service - oriented interface may be used by the domain data orchestration network element to send a data service task identifier to the domain data agent network element and to assign a data service task, the operation to be executed (for details, refer to the following operation configuration information), the output data format requirement, the data next - hop address, and the like to the domain data agent network element.

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

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

[0244] It should be noted that the communication method provided in the embodiments of this application is applicable to any two nodes shown in FIGS. 1 to 6e. For specific implementations, please refer to the following method embodiments. For details, they will not be described again in this specification.

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

[0246] FIG. 7 is a diagram showing the configuration of a communication device 700 that can be configured to execute the communication method according to the embodiments of this 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, another component, or an 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] As shown in FIG. 7, the communication device 700 may include a processor 701. Optionally, the communication device 700 may further include one or more of a memory 702 and a transceiver 703. The processor 701 and one or more of the memory 702 and the transceiver 703 may be coupled, for example, through a communication bus, or the processor 701 may be used independently.

[0248] Each component of the communication device 700 will be described in detail below with reference to FIG. 7.

[0249] The processor 701 is the control center of the communication device 700, and it may be a single processor or a composite relationship of multiple processing elements. For example, the processor 701 may be one or more central processing units (CPUs) or an application-specific integrated circuit (ASIC), or one or more integrated circuits implementing the 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 can execute or perform the software programs stored in the memory 702, call the data stored in the memory 702, and execute 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. 7.

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

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

[0254] Memory 702 is configured to store a software program for executing the solution of the present application, and processor 701 controls its execution. For the specific implementation described above, refer to the embodiments of the following methods. 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. Further, the transceiver 703 may include a receiver and a transmitter (not shown separately in FIG. 7). The receiver is configured to implement a receiving function, and the transmitter is configured to implement a transmitting function. The transceiver 703 may be integrated with the processor 701 or may exist independently and is coupled to the processor 701 through an input / output port (not shown in FIG. 7) of the communication device 700. This is not particularly limited in the present embodiment of the present application.

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

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

[0258] For example, FIGS. 8A to 8C are schematic flowcharts showing a communication method according to an embodiment of the present application.

[0259] The method shown in FIGS. 8A to 8C is applicable to a scenario in which data orchestration network elements are hierarchically deployed. The data orchestration network element may sometimes be called a cross-domain data orchestration network element. 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 of a core network domain, and the second domain data orchestration network element may be a data orchestration network element of an access network domain.

[0260] The first domain data orchestration network element can coordinate and manage data agent network elements within the first domain. For example, the data agent network elements within the first domain can be data agent network elements within the core network domain. The core network domain data agent network elements can include, but are not limited to, one or more of the following. That is, core network domain data agent network elements and stand-alone data agent network elements. The second domain data orchestration network element can coordinate and manage data agent network elements within the second domain. For example, the data agent network elements within the second domain can be data agent network elements within the access network domain. The data agent network elements within the access network domain can include, but are not limited to, one or more of the following. That is, access network domain data agent network elements, terminal domain data agent network elements, and stand-alone data agent network elements.

[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. Primarily, the first domain data orchestration network element, or the domain data orchestration network element (which can represent the first domain data orchestration network element or the second domain data orchestration network element) will be used as an example to explain below. 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 elements within the first domain are similar to those of the data agent network elements within the second domain. Primarily, the data agent network elements within the first domain or the domain data agent network elements (which can represent the data agent network elements within the first domain or the data agent network elements within the second domain) will be used as an example for the following explanation. For the implementation of the functions of the data agent network elements within the second domain, please refer to the specific implementation of the functions of the data agent network elements within the first domain.

[0263] In the following embodiments, the first domain data agent network element represents any one of the domain data agent network elements, for example, any data agent network element within the first domain, or any data agent network element within the second domain. Similarly, the second domain data agent network element represents any one of the domain data agent network elements, and the third domain data agent network element represents any one of the domain data agent network elements. The first domain data agent network element, the second domain data agent network element, and the third domain data agent network element are mutually different.

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

[0265] S801: The service request network element transmits a first service request message to the data orchestration network element. Accordingly, 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 the present embodiment of the present application, the application service may be a service requested by an application or an application server, and the service service may be a service requested by a network service - network element. In various scenarios, the services requested by using the first service request message may be different.

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

[0270] Optionally, the network data may include one or more of the following, but is not limited thereto. That is, logs (e.g., debug logs, security logs, or call history record (CHR) logs, etc.), alarms, traffic statistical information, 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 devices, data collected by terminal devices, and the like.

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

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

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

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

[0276] Optionally, data can be classified from 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. Therefore, the processing procedures for data are significantly different. Data is appropriately classified, so that the processing procedures can be simplified, the complexity of the system can be reduced, and data services of various data types can be supported.

[0278] In this application, it should be noted that the classification of data is not limited, and the data may be classified into more types, or fewer types, or the data may be classified into types from another perspective, or the data may not be classified into types.

[0279] For example, a network Service· The network element sends a first service request message to the data orchestration network element. Here, the first service request message is for requesting access to user subscription data within the data agent network element.

[0280] For example, an application that belongs to an operator and is used for network planning and optimization (sometimes simply called network planning and optimization application) sends a first service request message to the data orchestration network element. Here, the first service request message is for requesting the training of an association learning model, and the association learning model is used to predict the service quality.

[0281] For example, the network planning and optimization application sends a first service request message to the data orchestration network element. Here, the first service request message is for requesting the prediction of the service quality in area A.

[0282] In some embodiments, the request for predicting the service quality in area A can be decomposed into the following requests. That is, a request for training an association learning model (request 1) and a request for predicting the service quality in area A by using the (trained) association learning model (request 2).

[0283] Similarly, the process of predicting the service quality of area A can be decomposed into the following phases. That is, training of the federated learning model (phase 1) and prediction of the service quality of area A by using the (trained) federated learning model (phase 2). In this way, after receiving a request to predict the service quality of area A, if the service request network element locally stores the required federated learning model, phase 2 can be directly executed. Or, if the service request network element does not locally store the required federated learning model, after phase 1 is executed, phase 2 is executed.

[0284] Phase 1: The requirements for training the federated learning model are converted into corresponding requirement information. The data orchestration network element adjusts the domain data orchestration network element to select the domain data agent network elements participating in the current data service based on the data service functions of the domain data agent network elements, forming 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 strong computing capabilities (such as domain data agent network element 1, etc.) is selected as the server side to train the federated learning model. Another domain data agent network element (such as a domain data agent network element other than domain data agent network element 1 within the domain data agent network elements participating in the current data service, etc.) functions as the client side to provide the data used to train the federated learning model. After multiple trainings, a federated learning model is generated and sent to the service requirement network element by a domain data agent network element (such as domain data agent network element 1 as the server-side DA, etc.), or saved in the domain data agent network element or DSF as needed.

[0285] It should be noted that Phase 1 is applicable to the scenario where the service requirement network element requests the training of the federated learning model.

[0286] Phase 2: By using the federated learning model, the requirements for predicting the service quality of Region A in future time periods are converted into corresponding requirement information. The data orchestration network element adjusts the domain data agent network element to select the domain data agent network elements participating in the current data service based on the data service functions of the domain data agent network elements, and forms 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 strong computing capabilities (such as domain data agent network element 1, etc.) is selected to predict the service quality. Another domain data agent network element (such as a domain data agent network element other than domain data agent network element 1 within the domain data agent network elements participating in the current data service, etc.) can provide data (such as real-time network data, etc.) for predicting the service quality to domain data agent network element 1 or perform some operations on the data (such as processing like reducing sensitivity, etc.). Domain data agent network element 1 executes inference by using the federated learning model and data (original data or intermediate data) to obtain the prediction result of the service quality, and sends the result to the service requirement network element.

[0287] It should be noted that domain data agent network element 1 may send the obtained intermediate data to the service requirement network element, and the service requirement network element executes inference by using the federated learning model and the intermediate data to obtain the prediction result of the service quality. The federated learning model in the service requirement network element may be obtained from the domain data agent network element or may be pre-configured. This is not limited in this application.

[0288] For example, in an abnormal behavior detection scenario of 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. The first service request message is for requesting data of the Internet of Things, intermediate data obtained by processing (such as preprocessing or analysis) of the Internet of Things data, an abnormal behavior detection result of the IoT terminal device, or the like.

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

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

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

[0292] For example, the requirement information may be service requirements related to the first data, which are service requirements determined based on the service requested by using the first service request message.

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

[0294] For example, the first data may include one or more of the following, but is not limited thereto. That is, data on the terminal device side, data of each functional node on the access network device side, data of each functional node on the transfer network side, data of each functional node on the core network side, data of each functional node of OAM, and synthetic data.

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

[0296] For example, a face may be generated through adversarial learning, and the data of that face can be regarded as synthetic data.

[0297] For example, when the amount of a specific type of data is small, or when the amount of some abnormal data is small, synthetic data may be used.

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

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

[0300] Optionally, data can be classified from multiple dimensions such as data type, data source, data consumer, or as orthogonal as possible.

[0301] It should be noted that in this application, without limitation on the classification of the first data, the first data may be classified into more types, or may be classified into fewer types, or the first data may be classified into types from another perspective, or the first data may not be classified into types.

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

[0303] In some embodiments, the first data service function information can be determined based on a part of one or more domain data service function information.

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

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

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

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

[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 function information may be determined based on domain data service function information respectively corresponding to one or more domain data agent network elements within the core network, and the second data service function information may be determined based on domain data service function information respectively corresponding to one or more data agent network elements within the access network domain.

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

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

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

[0312] For example, the second data service function information may be obtained by an access network domain data orchestration network element by collecting statistical information regarding the domain data service function information of the domain data agent network elements within the local domain.

[0313] In a possible design method, the domain data service function 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. That is, the identifier of any one of the domain data agent network elements, the location information of any one of the 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 of interacting with a service request network element, a data protection function, and a data compression function.

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

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

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

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

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

[0319] Optionally, the data storage function may include, but is not limited to, one or more of the following. That is, data storage capacity, encryption algorithm for data storage, and storage method.

[0320] Optionally, the data reporting function may include, but is not limited to, one or more of the following. That is, minimum reporting period, amount of data reported at one time, maximum amount of data reported, support for file upload, and support for streaming data.

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

[0322] Optionally, the function that interacts with the service request network element may include, but is not limited to, whether it can provide an application programming interface service.

[0323] Optionally, the data protection function may include, but is not limited to, one or more of the following, namely, supported data protection technologies, such as k-anonymity, l-diversity, differential privacy, homomorphic encryption, and secure multiparty computation.

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

[0325] Regarding the implementation of the data collection function, data preprocessing function, data storage function, data reporting function, data analysis function, function that interacts with the service request network element, data protection function, and data compression function, it should be noted that further reference needs to be made to the description of the functions of the data agent network element in FIG. 3 It should be noted that 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 service requirements related to the first data, which are service requirements corresponding to the first domain data orchestration network element, and the second requirement information may be service requirements related to the first data, which are service requirements corresponding to the second domain data orchestration network element.

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

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

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

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

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

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

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

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

[0335] Optionally, the data orchestration network element may perform a requirement transformation for the service requested by using the first service request message. Here, the transformation (or mapping) is a service requirement for the function of the domain data agent network element.

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

[0337] In some embodiments, the method provided in the present embodiment of the present application may further include the following. That is, the data orchestration network element determines first instruction information.

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

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

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

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

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

[0343] Using as an example a scenario that requires training of a federated learning model (such as Phase 1 of S802), the following will explain 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 for requesting training of an AI model and the data orchestration network element performs requirement transformation, the obtained requirement information may include the following. That is, Region A, data collection, data preprocessing, data analysis, and interaction with the service request network element.

[0345] Assume that the first data service function information 1 includes the following. That is, Region A, data preprocessing supported by all data agent network elements within the first domain, data storage supported by most data agent network elements within the first domain, AI training and AI inference supported by most data agent network elements within the first domain, interaction with the service request network element supported by most data agent network elements within the first domain, and data collection supported by most data agent network elements within the first domain.

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

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

[0348] It should be noted that the above is merely an example provided in this application. 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 in scenarios that require training of the federated learning model 1 is are not limited in this application and may vary based on actual scenario requirements.

[0349] In a possible design approach, S802 may include the following. That is, when the service request network element has access rights to the first data, the data orchestration network element determines the first requirement information and the second requirement information based on the requirement information, the first data service function information, and the second data service function information.

[0350] In this way, the first requirement information and the second requirement information are determined only when the service request network element has access rights to the first data. Or, when the service request network element does not have access rights to the first data, the first requirement information and the second requirement information are not determined. Thereby, reliable service requirements for the data can be implemented.

[0351] In some embodiments, if the service request network element has access rights 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 rights 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, reliable service requirements for the data can be implemented.

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

[0353] Optionally, the second verification response message may indicate that the service request network element has access rights to the first data, or may indicate that the service request network element does not have access rights to the first data.

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

[0355] It should be noted that in the present embodiment of this 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. That is, S811: The data orchestration network element sends a second verification request message to the trust anchor. In response, the trust anchor receives the second verification request message from the data orchestration network element.

[0357] Optionally, the second verification request message may be for requesting verification of whether the service request 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. That is, S812: The first domain data orchestration network element sends the first data service function information to the data orchestration network element. In response, the data orchestration network element receives the first data service function information from the first domain data orchestration network element.

[0360] In this way, the first 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, obtain the first data service function information, and send the first data service function information to the data orchestration network element.

[0361] In some embodiments, the method provided in the present embodiment of the present application may further include the following steps. That is, S813: The second domain data orchestration network element transmits the second data service function information to the data orchestration network element. Accordingly, the data orchestration network element receives the second data service function information from the second domain data orchestration network element.

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

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

[0364] In some embodiments, the method provided in the present embodiment of the present application may further include the following. That is, the first domain data agent network element transmits the domain data service function information to the domain data orchestration network element. Accordingly, the domain data orchestration network element receives the domain data service function information from the first domain data agent network element.

[0365] For example, the first domain data agent network element represents any one of the domain data agent network elements. In this way, the domain data agent network element may transmit the domain data service function information of the domain data agent network element to the corresponding domain data orchestration network element.

[0366] For example, the method provided in the present embodiment of the present application may further include the following steps. That is, S814: The data agent network element in the first domain transmits the domain data service function information to the first domain data orchestration network element. Accordingly, the first domain data orchestration network element receives the domain data service function information from the data agent network element in the first domain.

[0367] In this way, the core network domain data agent network element and / or the stand-alone data agent network element may transmit their respective domain data service function information to the core network domain data orchestration network element.

[0368] For example, the method provided in the present embodiment of the present application may further include the following steps. That is, S815: The second domain data agent network element transmits the domain data service function information to the second domain data orchestration network element. Accordingly, the second domain data orchestration network element receives the domain data service function information from the second domain data agent network element.

[0369] In this way, the data agent network element of the access network domain, the data agent network element of the terminal domain, and / or the stand-alone data agent network element may transmit their respective domain data service function information to the access network domain data orchestration network element.

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

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

[0372] It should be noted that the registration of the first domain data agent network element with the domain data orchestration network element can be executed before or when the first domain data agent network element sends domain data service function information to the first domain data orchestration network element. This is not limited in this application.

[0373] S803a: The data orchestration network element sends the first requirement information to the first domain data orchestration network element. Accordingly, 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 requirement information to the second domain data orchestration network element. Accordingly, the second domain data orchestration network element receives the second requirement information from the data orchestration network element.

[0375] In this way, the data orchestration network element separately sends the first requirement information and the second requirement information to the data orchestration network elements within the corresponding domains.

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

[0377] Optionally, the method provided in the embodiments of the present application may further include the following. That is, the data orchestration network element sends first instruction information to the domain data orchestration network element. In response, the domain data orchestration network element receives the first instruction information from the data orchestration network element.

[0378] In this way, the data orchestration network element may notify 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 directly communicates with the service request network element belongs.

[0379] For example, the method provided in the embodiments of the present application may further include the following steps. That is, S816a: The data orchestration network element sends first instruction information to the first domain data orchestration network element. 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 instruction information may indicate whether the domain data agent network element that directly communicates with the service request network element is a data agent network element within the core network domain or a data agent network element within the access network domain.

[0381] Alternatively, for example, the first instruction information may indicate whether the domain data agent network element that directly communicates 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 the present embodiment of the present application may further include the following steps. That is, S816b: The data orchestration network element transmits the first instruction information to the second domain data orchestration network element. Accordingly, the second domain data orchestration network element receives the first instruction information from the data orchestration network element.

[0383] For example, the first instruction 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 within the core network domain or a data agent network element within the access network domain.

[0384] Alternatively, for example, the first instruction information may indicate whether the 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 method, the method provided in the present embodiment of the present application may further include the following. That is, the data orchestration network element transmits update information regarding the data security and privacy protection technology repository and / or update information regarding the analysis tool repository to one or more of at least one domain data agent network element. Accordingly, one or more of at least one domain data agent network element receives the update information regarding the data security and privacy protection technology repository and / or the update information regarding the analysis tool repository from the data orchestration network element.

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

[0387] Optionally, information about an analysis tool repository may include, but is not limited to, one or more of the following: namely, 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 a data security and privacy protection technology repository, an analysis tool repository, and the like are updated, the data orchestration network element may push the update 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 stand-alone data agent network element. In this way, data security protection, data privacy protection, and the like can be realized.

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

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

[0391] For example, the present embodiment of this application may further include the following steps. That is, step a: The domain data orchestration network element determines, based on the first requirement information (or the second requirement information) and a part of the one or more domain data service function information, at least one domain data agent network element corresponding to each of the at least one domain data agent network elements and operation configuration information. For example, the domain data orchestration network element 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 execute step a. For details, refer to the following description in S804a and S804b.

[0392] For example, a part of the one or more domain data service function information corresponds one-to-one to the one or more domain data agent network elements.

[0393] For example, assuming that the domain data orchestration network element is the first domain data orchestration network element, a part of the one or more domain data service function information may respectively correspond to one or more data agent network elements within the first domain. For details, refer to the following description in S804a.

[0394] For example, assuming that the domain data orchestration network element is the second domain data orchestration network element, portions of one or more domain data service function information may respectively correspond to one or more data agent network elements within the second domain. For details, please refer to the following description in S804b.

[0395] In a possible design approach, step a may include the following. That is, 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 requirement information (or the second requirement information) and portions of one or more domain data service function information.

[0397] Step 2: If any one of the at least one domain data agent network elements has access rights 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 requirement information (or the second requirement information) and portions of one or more domain data service function information.

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

[0399] S804a: The first domain data orchestration network element determines, based on the first requirement information and a part of the one or more domain data service function information, at least one data agent network element within the first domain and operation configuration information corresponding to each of the at least one data agent network element within the first domain.

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

[0401] For example, an example where a plurality of parts of the domain data service function information includes domain data service function information 1, domain data service function information 2, and domain data service function information 3 is used. Domain data service function information 1 corresponds to the domain data agent network element 1, domain data service function information 2 corresponds to the domain data agent network element 2, and domain data service function information 3 corresponds to the domain data agent network element 3.

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

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

[0404] For example, based on requirement information, domain data service function information 1, domain data service function information 2, and domain data service function information 3, the data orchestration network element determines the domain data agent network elements participating in the current data service from among domain data agent network element 1, domain data agent network element 2, and domain data agent network element 3. For example, in order to participate in the current data service, domain data agent network element 1 and domain data agent network element 2 are selected, and operation configuration information corresponding to domain data agent network element 1 and domain data agent network element 2 is determined 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 executed by any one of the data agent network elements 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 executed by domain data agent network element 1 on the first data or data generated based on the first data. The operation configuration information corresponding to domain data agent network element 2 indicates an operation to be executed by domain data agent network element 2 on the first data or data generated based on the first data.

[0407] For example, the first requirement information corresponds to at least one of parts of one or more domain data service function information.

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

[0409] In this way, the first domain data agent network element determines the data agent network elements within the first domain participating in the current data service based on at least one part of the first requirement information and the data service function information within the first domain. Here, the data service function of the selected data agent network element within the first domain needs to be able to meet the service requirements within the first requirement information, and the selected data agent network element within the first domain and the selected data agent network element within the second domain (see S804b below) each execute the operations indicated by their respective operation configuration information, whereby the data service can be implemented.

[0410] In some embodiments, the operations indicated by the operation configuration information may include, but are not limited to, one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service request network elements.

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

[0412] Regarding the implementation of these operations such as data collection, data preprocessing, data storage, data analysis, interaction with service request network elements, and data protection, it should be noted that reference needs to be made to the description of the functions of the data agent network elements in the figure 3 and the description of the domain data service function information in this application. Details will not be described again in this specification.

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

[0414] Step 3: Based on the first requirement information and a part of one or more domain data service function information, the first domain data orchestration network element determines at least one data agent network element within the first domain.

[0415] Step 4: If any one of at least one data agent network element within the first domain has access rights to the first data, the first domain data orchestration network element determines operation configuration information corresponding to any one of at least one data agent network element within the first domain based on the first requirement information and a part of one or more domain data service function information.

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

[0417] In some embodiments, the method provided in the present embodiment of the present application may further include the following. That is, the first domain data orchestration network element determines the first communication information.

[0418] In some embodiments, when the first instruction information indicates that the domain data agent network element directly communicating with the service request network element is a data agent network element within 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 that is within at least one data agent network element in the first domain and that communicates directly with the service request network element.

[0420] For example, assuming that the domain data agent network element that communicates directly with the service request 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: namely, the address of domain data agent network element 1, the identifier of domain data agent network element 1, and the index of domain data agent network element 1.

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

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

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

[0424] Using as an example a scenario that requires training of a federated learning model (such as Phase 1 in S802), the following will explain how a first domain data orchestration network element determines a data agent network element within a first domain that is participating in a current data service and operation configuration information corresponding to the data agent network element within the first domain.

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

[0426] Based on the first requirement information 1, domain data service function information 1, domain data service function information 2, and domain data service function information 3, the data orchestration network element determines, from among domain data agent network element 1, domain data agent network element 2, and domain data agent network element 3, the domain data agent network element that is participating in the current data service. Domain data service function information 1 to domain data service function information 3 respectively correspond to domain data agent network element 1 to domain data agent network element 3.

[0427] Assume that the domain data service function information 1 includes the following: namely, Region 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] Assume that the domain data service function information 2 includes the following: namely, Region A, supported data preprocessing, supported AI training and AI inference, unsupported interaction with service request network elements, and supported data collection.

[0429] Assume that the domain data service function information 3 includes the following. That is, the area 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] 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 first domain data orchestration network element may determine that the domain data agent network element 1 and the domain data agent network element 2 can jointly implement the service requirements within the first requirement information 1. First, the geographical location of the data agent network element 3 is region B rather than region 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 the training of the AI model.

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

[0432] In a possible design approach, S804a may include the following. If any one of at least one data agent network element within the first domain has access rights to the first data, the first domain data orchestration network element determines, based on the first requirement information and a part of the one or more domain data service function information, at least one data agent network element within the first domain and the operation configuration information corresponding to each of the at least one data agent network element within the first domain.

[0433] In this way, the data agent network element within the first domain participating in the data service and the corresponding operation configuration information are determined only if any one of at least one data agent network element within the first domain has access rights to the first data. Or, if any one of at least one data agent network element within the first domain does not have access rights to the first data, the data agent network element within the first domain participating in the data service and the corresponding operation configuration information are not determined. Thereby, reliable service requirements for the data can be implemented.

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

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

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

[0437] Optionally, the first verification request message is for verifying whether any one of at least one data agent network element in the first domain has the right to access 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 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 based on the second requirement information and a part of the one or more domain data service function information.

[0440] For example, the part of the one or more domain data service function information may respectively correspond to one or more data agent network elements in the second domain. For specific implementation, refer to the corresponding description in S804a. Details are not described again in this specification.

[0441] For example, 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 requirement information corresponds to at least one of one or more portions of domain data service function information (each corresponding to one or more data agent network elements in the second domain).

[0444] In this way, the second domain data agent network element determines the data agent network elements in the second domain that are participating in the current data service based on the second requirement information and at least one portion of the data service function information in the second domain. Here, the data service function of the selected data agent network element in the second domain needs to be able to meet the service requirements in the second requirement information, and the selected data agent network element in the first domain and the selected data agent network element in the second domain each execute the operations indicated by their respective operation configuration information, whereby the data service can be implemented.

[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. Details will not be described again in this specification.

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

[0447] In some embodiments, when 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 within a 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 the same as that of S804a. For details, please refer to S804a. Details will not be described again in this specification.

[0449] In a possible design approach, S804b may include the following. That is, when any one of at least one data agent network element within the second domain has access rights to the first data, the second domain data orchestration network element, based on the second requirement information and a part of one or more domain data service function information, determines at least one data agent network element within the second domain and operation configuration information corresponding to each of at least one data agent network element within the second domain.

[0450] In this way, the operation configuration information corresponding to the data agent network element within the second domain participating in the data service is determined only when any one of at least one data agent network element within the second domain has access rights to the first data. Or, when any one of at least one data agent network element within the second domain does not have access rights to the first data, the operation configuration information corresponding to the data agent network element within the second domain participating in the data service is not determined. Thereby, reliable service requirements for data can be implemented.

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

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

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

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

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

[0456] In a possible design manner, the method provided in the present embodiment of the present application may further include the following. That is, the first domain data orchestration network element may send second communication information to the second domain data orchestration network element. Accordingly, 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 be a data agent network element within at least one data agent network element in the first domain, indicating information about a 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 approach, the method provided in the present embodiment of the present application may further include the following. That is, the second domain data orchestration network element may send third communication information to the first domain data orchestration network element. Accordingly, 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 be a data agent network element within at least one data agent network element in the second domain, indicating information about a data agent network element in the second domain that communicates directly with a data agent network element in the first domain.

[0460] Assume that at least one selected data agent network element within the first domain includes domain data agent network element a and domain data agent network element b, and at least one selected data agent network element within 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. That is, the address of domain data agent network element b, the identifier of domain data agent network element b, and the 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. That is, the address of domain data agent network element c, the identifier of domain data agent network element c, and the 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 regarding the 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 may send the collected data to domain data agent network element b, domain data agent network element b may send the collected data to domain data agent network element c, domain data agent network element c may perform the corresponding operation, and then send the collected data obtained through the operation to domain data agent network element d.

[0462] The first domain data orchestration network element may execute the determination of the second communication information and S804a in the same step, or may execute them separately. It should be noted that the first domain data orchestration network element may execute the determination of the third communication information and S804b in the same step, or may execute them separately. This is not limited in this application.

[0463] S805a: The first domain data orchestration network element transmits the operation configuration information to the data agent network elements within the first domain. The data agent network elements within the first domain receive the operation configuration information from the first domain data orchestration network element.

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

[0465] In a possible design method, the method provided in the present embodiment of this application may further include the following steps. That is, S821: The first domain data orchestration network element transmits the first communication information to the service request network element. Accordingly, 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 elements within the first domain based on the received first communication information, and may directly receive messages from the data agent network elements within 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 this application.

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

[0469] In this way, the second domain data orchestration network element sends the corresponding operation configuration information to each of at least one data agent network element within the second domain.

[0470] In a possible design method, the method provided in the present embodiment of this application may further include the following steps. That is, S822: The second domain data orchestration network element sends the first communication information to the service request network element. Correspondingly, 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 elements within the second domain based on the received first communication information and may directly receive messages from the data agent network elements within 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 this application.

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

[0474] S806: The data agent network element within the first domain processes the initial data and obtains the first information based on the operation indicated by the operation configuration information.

[0475] For example, the data agent network element within the first domain obtains the operation indicated by the operation configuration information, adjusts the function of the data agent network element within the first domain to form an operation chain. Here, the output of the previous function is the input of the next function, and the initial data is processed based on the operation chain to obtain the first information.

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

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

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

[0479] For example, the data agent network elements within the second domain obtain the operations indicated by the operation configuration information, adjust the functions of the data agent network elements within the second domain, and form an operation chain. Here, the output of the previous function is the input of the next function, and the first data is processed 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, it is necessary to refer to the corresponding description in S804a. 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. Accordingly, 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 the following, but is not limited thereto. That is, network data, user data, Internet of Things data, and artificial intelligence model data.

[0484] For example, the operation configuration information may include collecting first 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 different types of data agent network elements, or may be the same type of domain data agent network elements.

[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 an access network device.

[0487] In this way, the inter-domain data agent network element can be connected, and a cross-domain data service architecture can be formed.

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

[0489] Optionally, the security information can be used to verify whether the first domain data agent network element has access rights 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 rights 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 the 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, such as network data, user data, Internet of Things data, and artificial intelligence model data.

[0494] Optionally, the first information may include initial data, such as 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 initial data from the data source (the third domain data agent network element).

[0496] Optionally, Step 6 may include the following. If the first domain data agent network element has access rights to the initial 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 rights to the initial data of the third domain data agent network element, the third domain data agent network element rejects this request. Thereby, the E2E trusted service requirements for the data can be implemented.

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

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

[0499] For example, the verification request message may be for requesting verification of whether the first domain data agent network element has access rights to the first data of the 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 verification response message may indicate whether the first domain data agent network element has access rights to the first data of the third domain data agent network element or not.

[0502] Optionally, after receiving the verification request message, the trust anchor checks the data access policy, verifies the security information, and can obtain whether the first domain data agent network element has access rights to the first data of the third domain data agent network element or not.

[0503] For example, based on the data type of the first data, the trust anchor can check the data access policy and verify the security information.

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

[0505] In some embodiments, S806 may include the following. That is, the first domain data agent network element processes second information based on an operation indicated by operation configuration information to obtain 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, the second information may be obtained based on the first data.

[0509] For example, the second information can be obtained through processing (such as data collection, data preprocessing, data protection, data storage, and / or data analysis, etc.) performed on the first data by another domain data agent network element.

[0510] For example, the operation configuration information can include one or more of the following, but is not limited thereto. That is, data collection, data preprocessing, data protection, data storage, and data analysis.

[0511] For example, the second information is obtained through data preprocessing performed on the first data by another domain data agent network element, 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 (performs data analysis and then performs security protection), analyzes the second information, and performs security protection on it to obtain the first information.

[0512] In some embodiments, S806 may include the following. That is, the first domain data agent network element processes the first 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 can be obtained from the application network element by the first domain data agent network element.

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

[0515] For example, the application data may include, but is not limited to, one or more of the following. That is, user history action records collected by an application program 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 cooperation processing on the data of the Internet of Things and application data, whereby it is possible to quickly and accurately determine abnormal behavior of terminal devices in the Internet of Things.

[0517] In a possible design method, the method provided in the present embodiment of the present application may further include the following steps. That is, step c: when 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 transmits the first information to the second domain data agent network element. Accordingly, the second Domain domain data agent network element receives the first Domain information from the first domain data agent network element.

[0518] Optionally, the operation 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, the operation configuration information may include the following. That is, an interaction with the second domain data agent network element.

[0520] In this way, the first domain data agent network element can send the first information to the second domain data agent network element, and the second domain data agent network element can process or transfer the first data based on the operation configuration information corresponding to the second domain data agent network element.

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

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

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

[0524] For example, when it is obtained that the second domain data agent network element has the access right 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. Or, when it is obtained that the second domain data agent network element does not have the access right 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. Thereby, the E2E trusted service requirement for data can be implemented.

[0525] In this way, when the first data includes user data, compliance detection for the user data can be implemented.

[0526] In some embodiments, the method provided in the present embodiment of the present application may further include the following steps. That is, step e: The first domain data agent network element transmits a third verification request message to the trust anchor. Accordingly, the trust anchor receives the third verification 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 the access right to the first data of the first domain data agent network element.

[0528] Optionally, the third verification request message may include the 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 can be obtained by a first domain data agent network element from the second 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 a third verification request message, the trust anchor may check a data access policy and verify the security information to obtain whether a second domain data agent network element has or does not have access rights to the first data of the first domain data agent network element. The specific implementation is the same as the implementation described above. After receiving the verification request message, the trust anchor may check the data access policy and verify the security information to obtain whether a first domain data agent network element has or does not have access rights to the first data of a third domain data agent network element. Details thereof will not be described again in this specification.

[0532] In a possible design method, the method provided in the present embodiment of the present application may further include the following steps. That is, step f: When the operation configuration information indicates that a first domain data agent network element communicates with a service request network element, the first domain data agent network element transmits first information to the service request network element. Correspondingly, 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 first data.

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

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

[0536] For example, the operation configuration information can include the following. That is, the interaction with the service request network element.

[0537] In this way, the service request network element obtains the first information. Here, the first information can be original data, intermediate data, analysis results, or the like.

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

[0539] In some embodiments, the method provided in the present embodiment of this application can further include the following. That is, the first domain data agent network element sends the processing behavior information to the trust anchor. Accordingly, the trust anchor receives the processing behavior information from the first domain data agent network element.

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

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

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

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

[0544] In a possible design method, the method provided in the present embodiment of the present application may further include the following. That is, 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, and may be, for example, intermediate data. The service request network element processes the first information to obtain the final result.

[0546] In some embodiments, the service request network element processes the first information to obtain an application service or a service service may include the following. That is, the service request network element obtains abnormal behavior information of terminal devices in the Internet of Things by using the first information.

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

[0548] In some embodiments, the service request network element processing the first information to obtain an application service or a service service may include the following. That is, the service request network element predicts the service quality by using the first information and the parameter configuration information of the artificial intelligence model.

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

[0550] In this way, the service request network element uses the parameter configuration information of the artificial intelligence model and the first information (which is intermediate data) to perform an inference and obtain the prediction result of the service quality.

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

[0552] Alternatively, optionally, if the service request network element does not locally store the parameter configuration information of the artificial intelligence model, the service request network element can obtain the parameter configuration information of the artificial intelligence model via 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 can perform hashing on the digest of the artificial intelligence model and perform a comparison with 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 elements in the first domain and the data agent network elements in the second domain may execute the operations indicated by the operation configuration information and transmit intermediate data or analysis results to the service request network elements. An example will be used to explain below, where the data agent network elements in the first domain obtain the first information, then transmit the first information to the data agent network elements in the second domain, and the data agent network elements in the second domain process the first information to obtain the third information and transmit the third information to the service request network elements.

[0555] S807: When the operation configuration information indicates that the data agent network elements in the first domain communicate with the data agent network elements in the second domain, the data agent network elements in the first domain transmit the first information to the data agent network elements in the second domain. Accordingly, the data agent network elements in the second domain receive the first information from the data agent network elements in the first domain.

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

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

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

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

[0560] In actual applications, a plurality of data agent network elements within the second domain may obtain third information by processing first information based on their respective operation configuration information. Details are not described one by one in this application.

[0561] S809: The data agent network elements within the second domain send the third information to the service request network elements. Accordingly, the service request network elements receive the third information from the data agent network elements within the second domain.

[0562] In this way, the service request network elements obtain the third information. Here, 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, refer to step c. Details will not be described again in this specification.

[0564] In a possible design method, the method provided in the present embodiment of this application may further include the following. That is, the service request network elements process the third information to obtain an application service or a service service. The implementation is the same as the above-described implementation, where the service request network elements process the first information to obtain an application service or a service service. Details will not be described again in this specification.

[0565] Based on the method shown in FIGS. 8A to 8C, the 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, from one or more domain data agent network elements, the domain data agent network elements participating in the current data service, 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 executed by the domain data agent network element on the initial data, and the first requirement information corresponds to at least one part of one or more domain data service function 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 executes the operation indicated by the operation configuration information. In this way, the data service can be implemented.

[0566] In this application, unless otherwise specified, for the same or similar parts in the embodiments, they should be referred to each other. In the embodiments of this application and the implementations / methods / implementation methods in the embodiments, unless otherwise specified or logical conflicts do not occur, the terms and / or descriptions are consistent and can be referred to each other among various embodiments and among the implementations / methods / implementation methods in the embodiments. The technical features in various embodiments and in the implementations / methods / implementation methods in the embodiments can 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] Regarding the communication method provided in the present embodiment of this application, it has been described in detail above with reference to FIGS. 1 to 8A - 8C. Hereinafter, with reference to FIG. 9, the communication device provided in the embodiment of this application will be described in detail.

[0568] For example, FIG. 9 is a diagram showing the configuration of a communication device according to an embodiment of the present application. This communication device can be used in the communication system shown in FIG. 1. For ease of explanation, FIG. 9 shows only the main components of the communication device. As shown in FIG. 9, the communication device 900 includes the following. That is, 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 and executes the functions of the domain data orchestration network elements in the communication methods in FIGS. 8A to 8C.

[0570] The transceiver module 901 is configured to receive first requirement information. The first requirement information is service requirements regarding the first data and is the service requirements 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 requirement information and a part of one or more domain data service function information. The part of one or more domain data service function information corresponds one-to-one with 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 requirement information corresponds to at least one of the parts of the one or more domain data service function information. 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 first data by any one of the domain data agent network elements.

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

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

[0574] The transceiver module 901 is further configured to determine operation configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirement information and a part of the one or more domain data service function information when any one of the at least one domain data agent network elements has access rights to the first data.

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

[0576] In a possible design, the transceiver module 901 is further configured to transmit a first verification request message to the trust anchor. The first verification request message is for requesting verification of whether any one of the at least one domain data agent network elements has access rights to the first data.

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

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

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

[0580] In a possible design approach, the transceiver module 901 is further configured to transmit first data service function information to the data orchestration network element. The first data service function information may be determined based on a portion of the domain data service function information of one or more domain data service function information.

[0581] In a possible design approach, the domain data service function information of any one of one or more domain data agent network elements may include one or more of the following. That is, the identifier of any one of the domain data agent network elements, the location information of any one of the domain data agent network elements, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with service request network elements, the data protection function, and the data compression function.

[0582] In a possible design approach, the operations indicated by the operation configuration information include one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service request network elements.

[0583] In a possible design approach, the first requirement information includes one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with service request network elements, data protection, and data compression.

[0584] In a possible design approach, the communication 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 approach, any one of one or more domain data agent network elements is a data agent network element within the core network domain, or one or more domain data agent network elements are data agent network elements within the access network domain.

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

[0587] It should be noted that all the relevant content of the steps in the embodiments of the above-described method may be cited in the function descriptions of the corresponding functional modules. For details, they 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). This is not particularly limited.

[0589] Optionally, the communication device 900 may further include a storage module (not shown in FIG. 9). The storage module stores programs or instructions. When the processing module 902 executes the programs or instructions, the communication device 900 may execute the functions of the domain data orchestration network elements in the communication method shown in FIGS. 8A to 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), another component, or an assembly that can be disposed within the domain data orchestration network element. This is not limited in this application.

[0591] Note that for the technical effects of the communication device 900, refer to the technical effects of the communication method shown in FIGS. 8A to 8C. For details, they 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 and execute the functions of the data orchestration network elements 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 requirement information, first data service function information, and second data service function information. The requirement information is a service requirement related to the first data, which is a service requirement determined based on the service requested by using a first service request message. The first data service function information corresponds to a first domain data orchestration network element, and the second data service function information corresponds to a second domain data orchestration network element.

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

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

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

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

[0599] In a possible design approach, portions of one or more domain data service function information correspond one-to-one with one or more domain data agent network elements, and 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. That is, the identifier of any one domain data agent network element, the location information of any one domain data agent network element, a data collection function, a data preprocessing function, a data storage function, a data reporting function, a data analysis function, a function to interact with a service request network element, a data protection function, and a data compression function.

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

[0601] In a possible design approach, the first service request message is from a service request network element, and the transceiver module 901 is further configured to send the first instruction information to the first domain data orchestration network element and / or the second domain data orchestration network element. The first instruction information may indicate whether the domain data agent network element that communicates directly with the service request network element is a data agent network element within the core network domain or a data agent network element within the access network domain.

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

[0603] In a possible design approach, the requirement information may include one or more of the following service requirements. That is, geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with the service request network element, data protection, and data compression.

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

[0605] In a possible design approach, 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 may be an access network domain data orchestration network element.

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

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

[0608] It should be noted that all the relevant content of the steps in the above-described method embodiments can be cited in the function descriptions of the corresponding function modules. For details, they 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). This is not particularly limited.

[0610] Optionally, the communication device 900 may further include a storage module (not shown in FIG. 9). The storage module stores programs or instructions. When the processing module 902 executes the programs or instructions, the communication device 900 may perform the functions of the domain data orchestration network elements in the communication method shown in FIGS. 8A to 8C.

[0611] It should be noted that the communication device 900 may be a data orchestration network element, or may be a chip (system), another component, or an assembly that can be disposed within the data orchestration network element. This is not limited in this application.

[0612] Regarding the technical effects of the communication device 900, please refer to the technical effects of the communication method shown in FIGS. 8A to 8C. For details, they 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 and performs the functions of the first domain data agent network element in the communication methods shown in FIGS. 8A to 8C.

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

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

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

[0617] In a possible design approach, the operations indicated by the operation configuration information may include one or more of the following. That is, data collection, data preprocessing, data protection, data storage, data analysis, and interaction with the service request network element.

[0618] In a possible design approach, the transceiver module 901 is further configured to send a data request message to a third domain data agent network element based on the operation configuration information. The data request message may be for requesting one or more of the following. That is, network data, user data, Internet of Things data, and data of an artificial intelligence model data.

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

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

[0621] In a possible design approach, 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. The second information is received by the communication device 900, and the second information is obtained based on the first data.

[0622] In a possible design approach, the transceiver module 901 is further configured to receive a first verification response message from a trust anchor. The first verification response message may indicate that the second domain data agent network element has the right to access the first data in the communication device 900.

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

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

[0625] In a possible design approach, the domain data service function information may include one or more of the following. That is, the identifier of the communication device 900, the location information of the communication device 900, the data collection function, the data preprocessing function, the data storage function, the data reporting function, the data analysis function, the function of interacting with the service request network element, the data protection function, and the data compression function.

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

[0627] In a possible design approach, the communication 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 stand-alone data agent network element.

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

[0629] It should be noted that all the content related to the steps in the above-described method embodiments can be cited in the functional descriptions of the corresponding functional modules. For details, they 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). This is not particularly limited.

[0631] Optionally, the communication device 900 may further include a storage module (not shown in FIG. 9). The storage module stores programs or instructions. When the processing module 902 executes the programs or instructions, the communication device 900 may perform the functions of the first domain data agent - network element in the communication methods shown in FIGS. 8A to 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 stand - alone data agent - network element, or may be a chip (system), another component, or an assembly that can be disposed within the first domain data agent - network element. This is not limited in this application.

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

[0634] One embodiment of the present application provides a communication system. This 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 and / or a service request network element.

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

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

[0637] One embodiment of the present application provides a chip system. This chip system includes a logic circuit and input / output ports. The logic circuit may be configured to implement the processing functions in the communication method provided in the embodiments of the present application, and the input / output ports may be configured to implement the receiving and transmitting functions in the communication method provided in the embodiments of the present application.

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

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

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

[0641] One embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the communication method provided in the embodiments of the present application is executed.

[0642] One embodiment of the present application provides a computer program product. The computer program product includes a computer program or instructions. When the computer program or instructions are executed on a computer, the communication method provided in the embodiments of the present application is executed.

[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 further 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] The memory in the embodiments of the present application may be a volatile memory, or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. Without limitation, by way of example, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (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 the embodiments, the above-described embodiments may be fully or partially implemented in the form of a computer program product. The 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 dedicated computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, a computer, a server, or a data center to another website, a computer, a server, or a data center in a wired (e.g., infrared, wireless, and microwave, or the like) manner. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape, etc.), an optical medium (e.g., a DVD, etc.), or a semiconductor medium. The semiconductor medium may be a solid-state drive.

[0646] The term "and / or" in this specification is to explain only the relevant relationship between related objects, and it should be understood that three relationships can exist. For example, A and / or B can represent the following three cases. That is, only A exists, both A and B exist, and only B exists. A and B may be singular or plural. Further, the character " / " in this specification usually indicates the "or" relationship between related objects, but may also indicate the "and / or" relationship. For details, please refer to the context for understanding.

[0647] In this application, "at least one" refers to one or more, and "a plurality" refers to two or more. "At least one of the following items (parts)" or a similar expression thereof refers to any combination of these items, including any combination of a single item (part) or a plurality of items (parts). For example, at least one item (part) of a, b, or c can represent a, b, c, a-b, a-c, b-c, or a-b-c. Here, a, b, and c may be singular or plural.

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

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

[0650] For the sake of convenience and concise description, it can be clearly understood by those skilled in the art that, for the detailed operation processes of the systems, devices, and units described above, it is necessary to refer to the corresponding processes in the embodiments of the methods described above. Details will not be described again in this specification.

[0651] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the described embodiments of the devices are merely examples. For example, the unit division is merely a logical function division, and in actual implementation, other divisions may be used. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not executed. Further, the shown or described mutual coupling, direct coupling, or communication connection can be implemented through some interfaces. The indirect coupling or communication connection between devices or units can be implemented in an electronic form, a mechanical form, or other forms.

[0652] A unit described as a separate component may or may not be physically separate, and a component represented as a unit may or may not be a physical unit. In other words, it may be located at one position or may be distributed over a plurality of network units. To achieve the object of the solution of the embodiment, part or all of the units may be selected based on actual requirements.

[0653] Also, in the embodiments of the present application, the functional units may be integrated into one processing unit, or each of the units may physically exist 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 such understanding, essentially the technical solution of the present application, or the part contributing to the prior art, or a part 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 execute 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 capable of storing program codes, 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 protection scope of the present application. Any modifications or alternatives that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall fall within the protection scope of the present application. Therefore, the protection scope of the present application shall comply with the protection scope of the claims.

Claims

1. A communication method, comprising: receiving, by a domain data orchestration network element, first requirement information, wherein the first requirement information is a service requirement in initial data and is a service requirement corresponding to the domain data orchestration network element; determining, by the domain data orchestration network element, 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 requirement information and a part of one or more domain data service function information, wherein the part of the 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 performed on the initial data by any one of the domain data agent network elements; transmitting, by the domain data orchestration network element, the operation configuration information; and a communication method comprising the above.

2. The step of determining, by the domain data orchestration network element, 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 requirement information and a part of one or more domain data service function information comprises: determining, by the domain data orchestration network element, the at least one domain data agent network element based on the first requirement information and the part of the one or more domain data service function information; If any one of the at least one domain data agent network elements has access rights to the first data, the domain data orchestration network element determines the operation configuration information corresponding to any one of the at least one domain data agent network elements based on the first requirement information and a part of the one or more domain data service function information. The communication method according to claim 1, including this.

3. The step of receiving, by the domain data orchestration network element, a first verification response message from a trust anchor, where the first verification response message indicates whether any one of the at least one domain data agent network elements has the access rights to the first data. The communication method according to claim 1 or 2, further comprising this.

4. The step of transmitting, by the domain data orchestration network element, a first verification request message to the trust anchor, where the first verification request message is for requesting verification of whether any one of the at least one domain data agent network elements has the access rights to the first data. The communication method according to any one of claims 1 to 3, further comprising this.

5. The step of receiving, by the domain data orchestration network element, first instruction information, where the first instruction information indicates whether a domain data agent network element that communicates directly with a service request network element is a data agent network element within a core network domain or a data agent network element within an access network domain. The communication method according to any one of claims 1 to 4, further comprising this.

6. A step of transmitting first communication information by the domain data orchestration network element, wherein the first communication information indicates information regarding a domain data agent network element that is within the at least one domain data agent network element and that communicates directly with the service request network element The communication method according to claim 5, further comprising this

7. A step of receiving, by the domain data orchestration network element, the domain data service function information corresponding to the one or more domain data agent network elements The communication method according to any one of claims 1 to 6, further comprising this

8. A step of transmitting, by the domain data orchestration network element, first data service function information, wherein the first data service function information is determined based on a part of the one or more domain data service function information The communication method according to claim 7, further comprising this

9. The domain data service function information of any one of the one or more domain data agent network elements includes one or more of the identifier of any one of the domain data agent network elements, the location information of any one of the 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 respect to the service request network element, a data protection function, and a data compression function. The communication method according to any one of claims 1 to 8

10. The operation indicated by the operation configuration information includes one or more of data collection, data preprocessing, data protection, data storage, data analysis, and the interaction with respect to the service request network element. The communication method according to any one of claims 1 to 9

11. The communication method according to any one of claims 1 to 10, wherein the first requirement information includes one or more service requirements among geographical location, the data collection, the data preprocessing, the data storage, the data reporting, the data analysis, the interaction with the service request network element, the data protection, and the data compression.

12. The communication method according to any one of claims 1 to 11, 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. The communication method according to any one of claims 1 to 12, wherein any one of the one or more domain data agent network elements is a data agent network element within the core network domain, or the one or more domain data agent network elements are data agent network elements within the access network domain.

14. The communication method according to any one of claims 1 to 13, wherein the first data includes 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; A step of determining first requirement information and second requirement information based on requirement information, first data service function information, and second data service function information by the data orchestration network element, where the requirement information is a service requirement in first data, and is a service requirement determined based on a service requested by using the first service request message; the first data service function information corresponds to a first domain data orchestration network element; the second data service function information corresponds to a second domain data orchestration network element; the first requirement information is a service requirement in the first data and is a service requirement corresponding to the first domain data orchestration network element; and the second requirement information is a service requirement in the first data and is a service requirement corresponding to the second domain data orchestration network element. A step of transmitting the first requirement information and the second requirement information by the data orchestration network element. A communication method comprising the above. **Claim 16** The communication method according to claim 15, wherein the first service request message is for requesting an application service or a service service. **Claim 17** A step of receiving the first data service function information from the first domain data orchestration network element by the data orchestration network element, where the first data service function information is determined based on a part of one or more domain data service function information. The communication method according to claim 15 or 16, further comprising the above. **Claim 18** A step of receiving the second data service function information from the second domain data orchestration network element by the data orchestration network element, where the second data service function information is determined based on a part of one or more domain data service function information. The communication method according to any one of claims 15 to 17, further comprising the above. **Claim 19** The portion of the one or more domain data service function information has a one-to-one correspondence with one or more domain data agent network elements, and any one of the domain data service function information among the one or more domain data agent network elements includes any one identifier of the domain data agent network element, any one location information of the domain data agent network element, a data collection function, a data preprocessing function, a data storage function, a data reporting function, a data analysis function, an interacting function with a service request network element, a data protection function, and one or more of a data compression function. The communication method according to claim 17 or 18.

20. The first service request message is from the service request network element. The step of transmitting, by the data orchestration network element, a second verification request message to a trust anchor, where the second verification request message is for requesting verification of whether the service request network element has access rights to the first data. The communication method according to any one of claims 15 to 19, further comprising.

21. The first service request message is from the service request network element. The step of transmitting, by the data orchestration network element, first instruction information, where the first instruction information indicates that the domain data agent network element that directly communicates with the service request network element is a data agent network element within a core network domain or a data agent network element within an access network domain. The communication method according to any one of claims 15 to 20, further comprising.

22. The step of transmitting, by the data orchestration network element, update information regarding a data security and privacy protection technology repository and / or update information regarding an analysis tool repository. The communication method according to any one of claims 15 to 21, further comprising.

23. The requirement information includes one or more service requirements among geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, the interaction with the service request network element, data protection, and data compression, for the communication method according to any one of claims 15 to 22.

24. The requirement information corresponds to a data service task identifier, for the communication method according to any one of claims 15 to 23.

25. 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, for the communication method according to any one of claims 15 to 24.

26. Any one of the one or more domain data agent network elements is a data agent network element within a core network domain, or the one or more domain data agent network elements are data agent network elements within an access network domain, for the communication method according to claim 19.

27. The first data includes data collected from a mobile communication network or synthetic data, for the communication method according to any one of claims 15 to 26.

28. A communication device, comprising a unit or module configured to execute the method according to any one of claims 1 to 14.

29. A communication device, comprising a unit or module configured to execute the method according to any one of claims 15 to 27.

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

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

32. A computer-readable storage medium storing a computer program or instructions, wherein when the computer program or the instructions are executed on a computer, the communication method according to any one of claims 1 to 27 is executed.

33. A computer program product including a computer program or instructions, wherein when the computer program or the instructions are executed on a computer, the communication method according to any one of claims 1 to 27 is executed.

Images