WO2023231714A1 - 通信方法、装置及系统 - Google Patents

通信方法、装置及系统 Download PDF

Info

Publication number
WO2023231714A1
WO2023231714A1 PCT/CN2023/092838 CN2023092838W WO2023231714A1 WO 2023231714 A1 WO2023231714 A1 WO 2023231714A1 CN 2023092838 W CN2023092838 W CN 2023092838W WO 2023231714 A1 WO2023231714 A1 WO 2023231714A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
network element
service
information
proxy network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/092838
Other languages
English (en)
French (fr)
Inventor
赵明宇
严学强
习燕
吴建军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP23814900.9A priority Critical patent/EP4525490A4/en
Publication of WO2023231714A1 publication Critical patent/WO2023231714A1/zh
Priority to US18/962,873 priority patent/US20250097313A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/564—Enhancement of application control based on intercepted application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method, device and system.
  • Data service can refer to collecting, preprocessing, and analyzing data and then providing the data as a service product.
  • data in the mobile communication network can be processed based on the data service architecture to implement data services.
  • data service architecture to implement data services.
  • Embodiments of the present application provide a communication method, device, and system that can process data in a mobile communication network based on a data service architecture and implement data services.
  • the first aspect is to provide a communication method.
  • the communication method includes: the data orchestration network element receives the first service request message, and the data orchestration network element determines each of at least one data proxy network element and at least one data proxy network element based on the demand information and one or more data service capability information.
  • the data proxy network element corresponds to the operation configuration information, and the data orchestration network element sends the operation configuration information.
  • the demand information is the service demand for the first data determined based on the service requested by the first service request message.
  • One or more data service capability information corresponds to one or more data agent network elements.
  • At least one data agent The network element is at least one of one or more data proxy network elements, the demand information corresponds to at least one of the one or more data service capability information, and the operation configuration information indication of any one of the at least one data proxy network element is The operation performed by any data proxy network element on the first data.
  • the data orchestration network element receives the first service request message, and determines from one or more data proxy network elements who participate in this data service based on the demand information and one or more data service capability information. Data proxy network element, and obtains the operation configuration information corresponding to each data proxy network element participating in this data service.
  • the operation configuration information indicates the operation performed by the data proxy network element on the first data.
  • the demand information is based on the first service request.
  • the service requirements for the first data determined by the service requested by the message.
  • the data orchestration network element sends the operation configuration information to the corresponding data agent network element, and the data agent network element performs the operations indicated by the operation configuration information. In this way, data services can be realized.
  • the first service request message may be used to request an application service or a business service.
  • application services may refer to services requested by applications or application servers
  • business services may refer to services requested by network service network elements.
  • the services requested by the first service request message may be different.
  • the first service request message comes from the service requesting network element.
  • the communication method provided in the first aspect may further include: the data orchestration network element receiving the first verification response message from the trusted anchor point.
  • the first verification response message may indicate that the service requesting network element has the authority to access the first data. That is to say, whether the service requesting network element has the permission to access the first data can be obtained by the data orchestration network element from the trusted anchor point, and trusted data services can be implemented.
  • the communication method provided in the first aspect may further include: the data orchestration network element sends a first verification request message to the trusted anchor point.
  • the first verification request message may be used to request verification whether the service requesting network element has the authority to access the first data. In this way, trusted data services can be implemented.
  • the first service request message comes from the service requesting network element.
  • the communication method provided in the first aspect may further include: the data orchestration network element sends the first communication information.
  • the first communication information may be used to indicate information about a data proxy network element in at least one data proxy network element that directly communicates with the service requesting network element.
  • the data orchestration network element can select the data agent network element that directly communicates with the service requesting network element from the determined data agent network elements participating in this data service, and the service requesting network element can establish direct interaction with the data agent network element.
  • the communication method provided in the first aspect may further include: the data orchestration network element receiving data service capability information corresponding to one or more data proxy network elements.
  • the data service capability information of any one of one or more data proxy network elements may include one or more of the following: the identification of any data proxy network element, any data
  • the agent network element has location information, data collection capabilities, data preprocessing capabilities, data storage capabilities, data reporting capabilities, data analysis capabilities, the ability to interact with service requesting network elements, data protection capabilities, and data compression capabilities. It should be noted that the data service capabilities of the data proxy network element are not limited to this.
  • the operations indicated by the operation configuration information may include one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service requesting network elements.
  • the data proxy network element can perform operations indicated by the operation configuration information.
  • the demand information may include one or more of the following service requirements: geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with service requesting network elements, and data protection. , and data compression.
  • the requirement information may correspond to the data service task identifier.
  • the data service task identifier may be used to identify the data service task corresponding to the first service request message.
  • the communication method provided in the first aspect may also include: the data orchestration network element sending updated data security and privacy protection technology library information to one or more of the at least one data proxy network element. and/or updated Analysis ToolPak information.
  • the data orchestration network element can be pushed to the data broker network element. In this way, data security protection, data privacy protection, etc. can be achieved.
  • the data orchestration network element can be deployed in the network service network element. In this way, the functions of the data orchestration network element can be performed by the network service network element.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • the first data may include but is not limited to one or more of the following: data on the terminal equipment side, data on each functional node on the access network equipment side, data on each functional node on the transmission network side, and data on the core network side.
  • synthetic data may refer to artificially synthesized data.
  • the second aspect is to provide a communication method.
  • the communication method includes: the first data proxy network element receives the operation configuration information, and the first data proxy network element processes the first data according to the operation indicated by the operation configuration information to obtain the first information.
  • the operation configuration information indicates that the first data proxy network element communicates with the second data proxy network element
  • the first data proxy network element sends the first information to the second data proxy network element.
  • the operation configuration information indicates that the first data proxy network element communicates with the service requesting network element
  • the first data proxy network element sends the first information to the service requesting network element.
  • the operation configuration information indicates an operation performed by the first data proxy network element on the first data.
  • the operations indicated by the operation configuration information may include one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service requesting network elements.
  • the above-mentioned first data proxy network element processes the first data according to the operation indicated by the operation configuration information, and obtains the first information, which may include: the first data proxy network element processes the first data according to the operation configuration information, A data request message is sent to the third data proxy network element, and the first data proxy network element receives a data response message from the third data proxy network element.
  • the data request message can be used to request one or more of the following data: network data, user data, Internet of Things data, and artificial intelligence model data.
  • the data response message includes one or more pieces of data included in the data request message.
  • the data request message may also include security information, and the security information may be used to verify whether the first data proxy network element has the authority to access the first data.
  • the above-mentioned first data proxy network element processes the first data according to the operation indicated by the operation configuration information, and obtains the first information, which may include: the first data proxy network element processes the first data according to the operation indicated by the operation configuration information.
  • the indicated operation processes the second information to obtain the first information.
  • the second information is received by the first data proxy network element, and the second information is obtained based on the first data.
  • the communication method provided in the second aspect may further include: the first data proxy network element receiving a second verification response message from the trusted anchor point.
  • the second verification response message may indicate that the second data proxy network element has the authority to access the first data of the first data proxy network element.
  • the communication method provided in the second aspect may further include: the first data proxy network element sends a second verification request message to the trusted anchor point.
  • the second verification request message may be used to request verification of whether the second data proxy network element has the authority to access the first data of the first data proxy network element.
  • the communication method provided in the second aspect may further include: the first data proxy network element sending data service capability information to the data orchestration network element.
  • the data service capability information may include one or more of the following: identification of the first data proxy network element, location information of the first data proxy network element, data collection capability, data preprocessing capability, Data storage capabilities, data reporting capabilities, data analysis capabilities, the ability to interact with service request network elements, data protection capabilities, and data compression capabilities.
  • the communication method provided in the second aspect may also include: the first data proxy network element receiving updated information and/or updates of the data security and privacy protection technology library from the data orchestration network element. Information about the Analysis ToolPak.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • the third aspect is to provide a communication method.
  • the communication method includes: the service requesting network element sends a first service request message to the data orchestration network element, and the service requesting network element receives the first information from the data proxy network element. Wherein, the first information is obtained based on the first data.
  • the first service request message may be used to request an application service or a business service.
  • the communication method provided in the third aspect may further include: service requesting the network element to receive the first communication information.
  • the first communication information may be used to indicate information about a data proxy network element that directly communicates with the service requesting network element.
  • the communication method provided in the third aspect may further include: service requesting the network element to process the first information to obtain application services or business services.
  • the service requesting network element processes the first information to obtain application services or business services, which may include: the service requesting network element uses the first information to obtain abnormal behavior information of the Internet of Things terminal device.
  • the above service requesting network element processes the first information to obtain application services or business services, which may include: the service requesting network element uses the first information and the artificial intelligence model parameter configuration information to perform service quality predict. Among them, the artificial intelligence model parameter configuration information is used to predict service quality.
  • the communication method provided in the third aspect may also include: the service requesting network element requests the artificial intelligence model parameter configuration information from the data brokering network element.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • a fourth aspect provides a communication device.
  • the communication device includes: a transceiver module and a processing module.
  • the transceiver module is used to receive the first service request message.
  • the processing module is configured to determine, based on the demand information and one or more data service capability information, the at least one data proxy network element and the operation configuration information corresponding to each of the at least one data proxy network element.
  • the transceiver module is also used to send operation configuration information.
  • the demand information is the service demand for the first data determined based on the service requested by the first service request message.
  • One or more data service capability information corresponds to one or more data agent network elements.
  • At least one data agent The network element is at least one of one or more data proxy network elements, the demand information corresponds to at least one of the one or more data service capability information, and the operation configuration information indication of any one of the at least one data proxy network element is The operation performed by any data proxy network element on the first data.
  • the first service request message may be used to request an application service or a business service.
  • the first service request message comes from the service requesting network element, and the transceiver module is also configured to receive the first verification response message from the trusted anchor point.
  • the first verification response message may indicate that the service requesting network element has the authority to access the first data.
  • the transceiver module is also used to send the first verification request message to the trusted anchor point.
  • the first verification request message may be used to request verification whether the service requesting network element has the authority to access the first data.
  • the first service request message comes from the service requesting network element, and the transceiver module is also used to send the first communication information.
  • the first communication information may be used to indicate information about a data proxy network element in at least one data proxy network element that directly communicates with the service requesting network element.
  • the transceiver module is also used to receive data service capability information corresponding to one or more data proxy network elements.
  • the data service capability information of any one of one or more data proxy network elements may include one or more of the following: the identification of any data proxy network element, any data
  • the agent network element has location information, data collection capabilities, data preprocessing capabilities, data storage capabilities, data reporting capabilities, data analysis capabilities, the ability to interact with service requesting network elements, data protection capabilities, and data compression capabilities.
  • the operations indicated by the operation configuration information may include one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service requesting network elements.
  • the demand information may include one or more of the following service requirements: geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with service requesting network elements, and data protection. , and data compression.
  • the requirement information may correspond to the data service task identifier.
  • the transceiver module is also used to send updated information of the data security and privacy protection technology library and/or updated information of the analysis tool library to one or more of the at least one data broker network element.
  • the communication device described in the fourth aspect may be deployed in a network service network element.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • the transceiver module described in the fourth aspect may include a receiving module and a sending module. This application does not specifically limit the specific implementation of the transceiver module.
  • the communication device described in the fourth aspect may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device described in the fourth aspect can perform the method described in the first aspect.
  • the communication device described in the fourth aspect may be a data orchestration network element, or may be a chip (system) or other components or components that can be disposed in the data orchestration network element, which is not limited in this application.
  • a communication device in a fifth aspect, includes: a transceiver module and a processing module.
  • the transceiver module is used to receive operation configuration information.
  • a processing module configured to process the first data according to the operation indicated by the operation configuration information to obtain the first information.
  • the transceiver module is also configured to send the first information to the second data proxy network element when the operation configuration information instructs the communication device to communicate with the second data proxy network element.
  • the transceiver module is further configured to send the first information to the service requesting network element when the operation configuration information instructs the communication device to communicate with the service requesting network element.
  • the operation configuration information indicates an operation performed by the communication device on the first data.
  • the operations indicated by the operation configuration information may include one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service requesting network elements.
  • the transceiver module is also used to send a data request message to the third data proxy network element according to the operation configuration information.
  • the transceiver module is also used to receive data response messages from the third data proxy network element.
  • the data request message can be used to request one or more of the following data: network data, user data, Internet of Things data, and artificial intelligence model data.
  • the data response message includes one or more pieces of data included in the data request message.
  • the data request message may also include security information, and the security information may be used to verify whether the communication device has the authority to access the first data.
  • the processing module is also configured to process the second information according to the operation indicated by the operation configuration information to obtain the first information.
  • the second information is received by the communication device, and the second information is obtained based on the first data.
  • the transceiver module is also configured to receive a second verification response message from the trusted anchor point.
  • the first verification response message may indicate that the second data proxy network element has the authority to access the first data of the first data proxy network element.
  • the transceiver module is also used to send a second verification request message to the trusted anchor point.
  • the second verification request message may be used to request verification of whether the second data proxy network element has the authority to access the first data of the communication device.
  • the transceiver module is also used to send data service capability information to the data orchestration network element.
  • the data service capability information may include one or more of the following: identification of the communication device, location information of the communication device, data collection capability, data preprocessing capability, data storage capability, data reporting capability, Data analysis capabilities, the ability to interact with service request network elements, data protection capabilities, and data compression capabilities.
  • the transceiver module is also used to receive updated information from the data orchestration network element's data security and privacy protection technology library and/or updated information from the analysis tool library.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • the transceiver module described in the fifth aspect may include a receiving module and a sending module. This application does not specifically limit the specific implementation of the transceiver module.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device described in the fifth aspect can perform the method described in the second aspect.
  • the communication device described in the fifth aspect may be the first data proxy network element, or may be a chip (system) or other components or components that can be disposed in the first data proxy network element. This application will No restrictions.
  • a sixth aspect provides a communication device.
  • the communication device includes: a sending module and a receiving module.
  • the sending module is used to send the first service request message to the data orchestration network element.
  • the receiving module is configured to receive the first information from the data proxy network element. Wherein, the first information is obtained based on the first data.
  • the first service request message may be used to request an application service or a business service.
  • the receiving module is also used to receive the first communication information.
  • the first communication information may be used to indicate information about a data proxy network element that directly communicates with the service requesting network element.
  • the processing module is used to process the first information to obtain application services or business services.
  • the processing module is also configured to use the first information to obtain abnormal behavior information of the Internet of Things terminal device.
  • the processing module is also used to use the first information and the artificial intelligence model parameter configuration information to predict service quality.
  • the artificial intelligence model parameter configuration information is used to predict service quality.
  • the receiving module is also used to request artificial intelligence model parameter configuration information from the data broker network element.
  • the first data may include data collected from a mobile communication network or synthesized data.
  • the receiving module and the sending module can be set up separately, or they can be integrated into one module, that is, the sending and receiving module. This application does not specifically limit the specific implementation methods of the receiving module and the sending module.
  • the communication device may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction, the communication device described in the sixth aspect can perform the method described in the third aspect.
  • the communication device described in the sixth aspect may be a service requesting network element, or may be a chip (system) or other components or components that can be disposed on the service requesting network element, which is not limited in this application.
  • a communication device in a seventh aspect, includes a processor coupled to a memory for storing a computer program.
  • the processor is configured to execute a computer program stored in the memory, so that the method described in any possible implementation manner of the first to third aspects is executed.
  • the communication device described in the seventh aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an input/output port.
  • the transceiver may be used for the communication device to communicate with other devices.
  • the input port can be used to implement the receiving functions involved in the first to third aspects
  • the output port can be used to implement the sending functions involved in the first to third aspects.
  • the communication device described in the seventh aspect may be a data orchestration network element, a first data proxy network element or a service requesting network element, or may be provided in a data orchestration network element, a first data proxy network element or a service requesting network element.
  • An eighth aspect provides a communication system.
  • the communication system includes a data orchestration network element and a first data proxy network element, and may also include a service requesting network element.
  • the data orchestration network element is used to implement the method described in the first aspect.
  • the first data proxy network element is used to implement the method described in the second aspect.
  • Service request network element used to implement the third methods described in this aspect.
  • the communication system includes a communication device as described in the fourth aspect for implementing the method as described in the first aspect, a communication device as described in the fifth aspect for implementing the method as described in the second aspect, and may also be It includes the communication device as described in the sixth aspect for implementing the method as described in the third aspect.
  • a chip system including a logic circuit and an input/output port.
  • the logic circuit is used to implement the processing functions involved in the first aspect to the third aspect
  • the input/output port is used to implement the transceiver functions involved in the first aspect to the third aspect.
  • the input port can be used to implement the receiving functions involved in the first to third aspects
  • the output port can be used to implement the sending functions involved in the first to third aspects.
  • the chip system further includes a memory, which is used to store program instructions and data for implementing the functions involved in the first to third aspects.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a computer-readable storage medium stores a computer program or instructions; when the computer program or instructions are run on a computer, any one of the first to third aspects is enabled. Possible implementations of the described method are executed.
  • a computer program product including a computer program or instructions.
  • the computer program or instructions are run on a computer, the method described in any one of the possible implementations of the first to third aspects is achieved. be executed.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of a data service architecture provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of the functions of a data service architecture provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of a logical network topology provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of an operation chain provided by an embodiment of the present application.
  • FIGS 6a-6d are schematic diagrams of some network architectures provided by embodiments of the present application.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 8 is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • Figure 9 is a schematic flow chart of another communication method provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • Figure 11 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as universal mobile telecommunications system (UMTS), wireless local area network (WLAN), wireless fidelity (Wi-Fi) ) system, wired network, vehicle to everything (V2X) communication system, device-to-device (D2D) communication system, Internet of Vehicles communication system, 4th generation (4G) mobile communication Systems, such as long term evolution (LTE) systems, global interoperability for microwave access (WiMAX) communication systems, fifth generation (5th generation, 5G) mobile communication systems, such as new air interfaces (new radio (NR) system, as well as future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.
  • UMTS universal mobile telecommunications system
  • WLAN wireless local area network
  • Wi-Fi wireless fidelity
  • V2X vehicle to everything
  • D2D device-to-device
  • Internet of Vehicles communication system Internet of Vehicles communication system
  • 4G 4th generation
  • 4G 4th generation
  • FIG. 1 is an architectural schematic diagram of a communication system to which the communication method provided by the embodiment of the present application is applicable.
  • the communication system includes data orchestration (DO) network elements and data agent (data agent, DA) network elements.
  • DO data orchestration
  • DA data agent
  • the number of data orchestration network elements may be one or more, and the number of data proxy network elements may be one or more.
  • the above-mentioned data orchestration network element can obtain the service request, translate the service request into a service requirement for data, determine the data proxy network element used to realize the service requirement, orchestrate the functions of each data proxy network element, and make the data proxy network element Perform corresponding operations and establish dynamic logical network topology to achieve corresponding service requirements.
  • the data orchestration network element can be deployed on any core network element, transfer network (TN) network element, access network equipment or other network element (such as operation, management and maintenance (operation administration and maintenance, OAM) ) network elements, etc.), or data orchestration network elements can be deployed independently.
  • data orchestration network elements can be deployed hierarchically on the core network or access network equipment side.
  • Data orchestration network elements can be deployed in network service (NS) network elements.
  • NS network service
  • data orchestration network elements can be independently deployed in the network as network functions (NF) or network elements. In actual deployment, one or more NFs can form a network element.
  • the above-mentioned data proxy network element can implement one or more of the following functions: data collection, preprocessing, storage, analysis, and data protection, etc.
  • Different data proxy network elements can have the same or different data service capabilities and can implement the same or different functions.
  • the data proxy network element can interact with the data orchestration network element to obtain relevant operations that need to be performed to achieve service requirements, and execute the operations.
  • the data agent network element can establish a logical network topology to form a dynamic data pipeline (also known as data flow, business logic, function chain, operation chain, etc.).
  • the data pipeline is corresponding to one or more data agent network elements.
  • the functions are composed according to service requirements, and the output of the previous function is the input of the next function, thereby realizing responsive data services.
  • the above data proxy network elements can be deployed in any core network network element, transfer network (TN) network element, terminal equipment, access network equipment or other network elements (such as operation, management and maintenance (operation administration and maintenance, OAM) ) network element, etc.), or the data proxy network element can be deployed independently.
  • the data proxy network element can be independently deployed in the network as a network function NF or network element.
  • the data proxy network element can be evolved from any core network element, transmission network element, terminal equipment, access network equipment or other network elements.
  • the data proxy network element can implement any core network element, transmission network element, etc.
  • the functions that can be realized by network elements, terminal equipment, access network equipment or other network elements, or the functions of the data proxy network element provided in this application can be implemented by any core network element, transmission network element, terminal equipment, etc. , access network equipment or other network elements.
  • the data proxy network element can be evolved from the network data analysis function (network data analysis function, NWDAF) network element, and can realize the functions of the NWDAF network element, as well as the scenario use cases implemented based on the NWDAF network element.
  • NWDAF network data analysis function
  • the data proxy network element can be optionally deployed in any core network element, transmission network element, terminal equipment, access network equipment or other network elements according to the network element's resources and/or capabilities. , which can realize cross-domain data collection. It can collect data from the whole domain and realize cross-domain data management and collaboration.
  • the data proxy network element serves as a network function NF and can match cloud-native SBI encryption, NF dynamic instantiation and encryption environment of K8S deployment. In addition, it can minimize the impact on the performance loss and security of NF.
  • some data proxy network elements can be built into the network equipment (referring to any core network network element, terminal equipment, access network equipment, or other network elements, etc.), and some can be built into the network equipment.
  • the data proxy network elements are deployed independently; or multiple data proxy network elements are built into the network device, or multiple data proxy network elements are deployed independently, and this application is not limited to this.
  • the data orchestration network element can be a logical entity or a physical entity
  • the data proxy network element can be a logical entity or a physical entity, which is not limited in this application.
  • the data proxy network element can be deployed in a centralized manner or in a distributed manner.
  • Distributed deployment methods can include distributed hash table (DHT) methods, etc.
  • DHT distributed hash table
  • Data proxy network elements are distributed and flexibly deployed on demand, which can meet diverse and flexible data service needs and reduce the cost of data collection.
  • the above-mentioned core network elements are located on the network side of the communication system and can be used to provide network services for access network equipment, terminal equipment, etc.
  • the core network elements may include but are not limited to one or more of the following: mobility management network elements, session management network elements, user plane network elements, policy control network elements, network opening network elements, application network elements, NWDAF network elements, and/or OAM network elements.
  • Mobility management network element mainly used for mobility management and access management.
  • the access management network element can be an access and mobility management function (AMF) network element, which mainly performs functions such as mobility management and access authentication/authorization.
  • AMF access and mobility management function
  • the mobility management network element can also be responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.
  • PCF policy control function
  • Session management network element Mainly used for session management (such as creation, deletion, etc.), maintaining session context and user plane forwarding pipeline information, Internet protocol (IP) address allocation and management of terminal equipment, and selecting manageable users Termination points of plane functions, policy control and charging function interfaces, and downlink data notifications, etc.
  • IP Internet protocol
  • the session management network element may be a session management function (session management function). function, SMF) network element, completes terminal IP address allocation, UPF selection, accounting and QoS policy control, etc.
  • SMF session management function
  • User plane network element As an interface with the data network, it completes functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation. That is, packet routing and forwarding and quality of service (QoS) processing of user plane data, etc.
  • the user plane network element may be a user plane function (UPF) network element.
  • UPF user plane function
  • Policy control network element including user subscription data management function, policy control function, billing policy control function, quality of service (QoS) control, etc. It is a unified policy framework used to guide network behavior and is a control plane functional network element (such as AMF, SMF network elements, etc.) to provide policy rule information, etc.
  • the policy control network element may be the PCF.
  • Network open network element It can be used to provide frameworks, authentications and interfaces related to network capability opening, and to transfer information between 5G system network functions and other network functions.
  • the network open network element can be a network element function (NEF) network element, which is mainly used to open the services and capabilities of 3GPP network functions to AF, and also allows AF to provide 3GPP network functions. information.
  • NEF network element function
  • Application network elements can be used to provide various business services, can interact with the core network through network element function (NEF) network elements, and can interact with the policy management framework for policy management.
  • the application network element can be an application function (AF) network element or a time-sensitive network application function (TSNAF) network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data, and is mainly used to convey the needs of the application side to the network side.
  • AF application function
  • TNAF time-sensitive network application function
  • NWDAF network element can be used to collect data from the core network and OAM network elements and feed back data analysis results to NF, AF or OAM.
  • the NWDAF network element can collect OAM data from the OAM network element and collect non-OAM data from the core network NF or AF.
  • the non-OAM data can include collecting non-OAM data at the terminal, terminal group, service and other levels.
  • OAM network element can collect data from access network equipment.
  • the above-mentioned access network equipment can also be called access equipment or wireless access network equipment.
  • the access network equipment can manage wireless resources, provide access services to terminal equipment, and complete data forwarding between the terminal equipment and the core network.
  • the access network equipment can also be understood as the base station in the network.
  • the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions used to communicate with terminal devices.
  • the access network equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), wireless network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI)
  • 5G can also be 5G, Such as gNB in the NR system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or it can also be the network node that constitutes the gNB or transmission point, Such as baseband unit (BBU), or distributed unit (DU), etc. It can also be a satellite, a drone, etc.
  • gNB may include centralized units (CUs) and DUs. gNB also An active antenna unit (AAU) may be included.
  • CU implements some functions of gNB
  • DU implements some functions of gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the RRC layer information is generated by the CU, and will eventually be encapsulated by the PHY layer of the DU into PHY layer information, or converted from the PHY layer information. Therefore, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by DU, or sent by DU+AAU.
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into access network equipment in the access network (radio access network, RAN), or the CU can be divided into access network equipment in the core network (core network, CN). This application does not Make limitations.
  • the above-mentioned terminal device is a terminal that is connected to the communication system and has a wireless transceiver function, or a chip or chip system that can be installed on the terminal.
  • the terminal equipment in this application may also be called terminal, user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless Communication equipment, user agent or user device.
  • UE user equipment
  • the terminal in the embodiment of the present application can be a mobile phone (mobile phone), a tablet computer (pad), a drone, a computer with wireless transceiver functions, customer premise equipment (CPE), virtual reality (virtual reality) , VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, intelligent Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, conversations Session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or connected to a wireless modem Other processing equipment, vehicle equipment, wearable devices, terminals in 5G networks or terminals in future evolution networks, etc.
  • CPE customer premise equipment
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in industrial control wireless terminals in self-driving
  • wireless terminals in remote medical intelligent Wireless terminal
  • the terminal device in this application can be an express delivery terminal in smart logistics (such as a device that can monitor the location of cargo vehicles, a device that can monitor the temperature and humidity of cargo, etc.), a wireless terminal in smart agriculture (such as a device that can collect livestock related data wearable devices, etc.), wireless terminals in smart buildings (such as smart elevators, fire monitoring equipment, and smart meters, etc.), wireless terminals in smart medical care (such as wearable devices that can monitor the physiological status of people or animals) ), wireless terminals in smart transportation (such as smart buses, smart vehicles, shared bicycles, charging pile monitoring equipment, smart traffic lights, smart monitoring and smart parking equipment, etc.), wireless terminals in smart retail (such as vending machines, Self-service checkout machines, unmanned convenience stores, etc.).
  • smart logistics such as a device that can monitor the location of cargo vehicles, a device that can monitor the temperature and humidity of cargo, etc.
  • a wireless terminal in smart agriculture such as a device that can collect livestock related data wearable devices, etc.
  • wireless terminals in smart buildings
  • the terminal device in this application may be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit built into the vehicle as one or more components or units.
  • the vehicle uses the built-in vehicle-mounted module, vehicle-mounted unit Modules, vehicle-mounted components, vehicle-mounted chips or vehicle-mounted units can implement the method provided by this application.
  • the terminal device in this application can be a smart internet of things (SIoT) terminal device or a non-SIoT terminal device, and has certain computing, storage and other capabilities.
  • Non-SIoT terminal devices can collect data through the IoT gateway.
  • non-SIoT terminal devices can be terminals with limited computing capabilities, such as sensors with a single function.
  • SIoT The terminal device can have a built-in data proxy network element, or the SIoT terminal device can implement the function of the data proxy network element.
  • FIG 1 is only a simplified schematic diagram for ease of understanding.
  • the communication system may also include other devices, such as a trusted anchor (trust anchor, TA), a service requesting network element and/or a data storage network element (specifically For implementation, please refer to the corresponding explanation in Figure 2 below), which is not shown in Figure 1.
  • trust anchor trust anchor
  • TA service requesting network element
  • data storage network element specifically For implementation, please refer to the corresponding explanation in Figure 2 below, which is not shown in Figure 1.
  • FIG. 2 is a schematic diagram of a data service architecture provided by an embodiment of the present application.
  • the communication system shown in Figure 1 can be applied to the data service architecture shown in Figure 2.
  • this application proposes to build a normalized data service architecture based on the data plane to provide data services for service requesting network elements.
  • the data service architecture may include but is not limited to one or more of the following: data orchestration network elements, data proxy network elements, trusted anchors (trust anchors, TA), service request network elements, and data storage network elements.
  • trusted anchor points can provide trusted services such as authentication, authentication and access control (authentication authorization access control, AAA), for example, they can be implemented through distributed ledger technology (DLT).
  • Trusted anchor points can store data that cannot be tampered with, such as public keys, identifiers, indexes of terminal devices or network elements, transaction-related data, or important data that cannot be tampered with.
  • the storage capabilities of distributed ledger technology can be expanded by combining on-chain and off-chain storage, such as storing original data locally in the data broker network element or in the data storage network element.
  • off-chain store the hash value of the original data, or the hash value of the digest of the packaged original data, in the extended DLT (on-chain), and at the same time save the hash value pointing to the original data in the DLT (on-chain) address.
  • the trusted anchor may be deployed in a distributed or centralized manner.
  • Trusted anchors for distributed deployment can be nodes of distributed ledger technology DLT (such as blockchain), and trusted anchors for centralized deployment can be existing security and trustworthiness mechanisms such as authentication, authorization, and access control. Achieved through transformation and evolution.
  • DLT distributed ledger technology
  • trusted anchors for centralized deployment can be existing security and trustworthiness mechanisms such as authentication, authorization, and access control. Achieved through transformation and evolution.
  • the trusted anchor point can realize the security and privacy protection mechanism of the entire data service process through data access control such as authentication, authorization, access control, etc., combined with the data security and privacy protection technology library, and can support the entire data service process.
  • Security and privacy protection can support trusted data service requirements such as traceability, auditing, and autonomous control of user data, can support the realization of data sharing and transactions, and other requirements for trustworthy mechanisms such as traceability and auditing, and can meet the requirements of the Personal Information Protection Law (personal information protection law).
  • Information protection law, PIPL Information protection law
  • General Data Protection Regulation general data protection regulation, GDPR
  • Compliance testing for user data processing can implement a decentralized verification mechanism to avoid single-point trust and failure issues.
  • the above-mentioned service requesting network elements may include applications, application servers or network service NS network elements, etc.
  • the application may be an operator (or communication service provider (communication service provider, CSP)) used for network planning, network optimization, and/or network Applications such as artificial intelligence (AI) can also be applications outside the mobile communication network (can also be called third-party applications).
  • Service requesting network elements can be independently deployed in the network as network functions or network elements.
  • the above data storage network element can support the storage of various data, such as streaming data, batch data, log information, AI model parameter configuration information, intermediate data, etc., and can expand the storage function of the data agent network element.
  • the DSF network element may be a centralized database or a distributed database, such as a distributed hash table DHT or an inter planetary file system (IPFS).
  • the data storage network element may be a data storage function (DSF) network element, or may be Evolved from the data storage function network element.
  • DSF data storage function
  • Data storage network elements can be deployed in the network as NFs or network elements.
  • FIG. 3 is a schematic diagram of the functions of a data service architecture provided by an embodiment of the present application.
  • the functions that the data orchestration network element can implement include but are not limited to one or more of the following: interface with applications, requirement translation, orchestration data agent, management data agent, data protection, and network service (NS) ), and interfaces with trusted anchors.
  • the data orchestration network element can interact with the service requesting network element through the interface with the application.
  • the data orchestration network element receives service requests from the service requesting network element.
  • the service request may be a requirement filled in based on a standard template.
  • the standard template may be a service level agreement (service level agreement, SLA).
  • the data orchestration network element translates service requests into service requirements for the functions of each data broker network element.
  • the data orchestration network element translates requirements such as service level agreements into requirements for corresponding resources and network configurations.
  • Orchestration data agent Based on the data service capabilities of data agent network elements, orchestrate each data agent network element to form a dynamic logical network topology to meet service requirements.
  • the data orchestration network element translates requirements such as service level agreements into requirements for corresponding resources and network configurations, and selects data proxy network elements to participate in this data service based on the data service capabilities of the data proxy network element, and orchestrates Each data proxy network element forms a dynamic logical network topology.
  • the data orchestration network element may negotiate with other network service network elements during the execution of the orchestration data proxy process. For example, if algorithms and computing power are needed, the data orchestration network element can collaborate with other network service network elements to select the corresponding AI algorithm and computing power, and the network service network element can push the algorithm.
  • the data orchestration network element can dynamically specify a data proxy network element that directly interacts with the service requesting network element, and send the information of the data proxy network element to the service requesting network element, so that the application can call the application of the data proxy network element.
  • Programmable interface application programming interface, API
  • Management data agent manages the registration, de-registration, etc. requested by the data agent network element from the data orchestration network element, and receives the data service capabilities reported by the management data agent network element.
  • Data protection functions can be implemented through the data protection technology repository (DPTR).
  • the data protection technology repository can include data security and privacy protection algorithm libraries, such as differential privacy, homomorphic encryption, multi-party computation, and zero-knowledge proof. and many other algorithms.
  • the data orchestration network element can push or update the information of the data protection technology library to the management data agent network element on demand, as the data protection technology (DPT) of the management data agent network element.
  • the data protection technology library can be loosely coupled with the data orchestration network elements.
  • the data protection technology library can be a common capability of network elements in the data service architecture and can be independently evolved and optimized. An independent data protection technology library facilitates end-to-end (E2E) data processing compliance testing.
  • E2E end-to-end
  • the information of the data protection technology library may include the identification, index, configuration information of the data protection technology library, the data protection technology library itself, etc.
  • Data orchestration network elements can interact with network service network elements through interfaces with network services. For example, data orchestration network elements can negotiate with network service network elements based on service requirements. For example, if algorithms and computing power are needed, data orchestration network elements can collaborate with other network service network elements.
  • Trusted anchor point proxy The interface between the data orchestration network element and the trusted anchor point.
  • the data orchestration network element can interact with the trusted anchor point through the trusted anchor point proxy function.
  • each functional module can be divided corresponding to each function, or two or more functions integrated into one module.
  • Integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of functions or modules in the embodiments of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • the functions that the data proxy network element can implement include but are not limited to one or more of the following: control, data collection, preprocessing, storage, application programmable interface, data analysis, and data protection.
  • the data agent network element can realize data service collaboration and closed-loop management, and can output data with different processing requirements on demand.
  • each function in the data orchestration network element is orchestrated to form a data pipeline.
  • the control function can be implemented by the controller of the data orchestration network element.
  • the data orchestration network element is used to orchestrate each data agent network element to form a dynamic logical network topology.
  • the data agent network element orchestrates each function in the data agent network element to form a data pipeline, which can realize automated data management and dynamic on-demand configuration. , respond quickly to new businesses and new needs, support the realization of rich application scenarios, achieve rapid launch of new data service businesses, and shorten the time to market (TTM).
  • TTM time to market
  • Data acquisition Obtain data, for example, through subscription/notification, or through request/response.
  • the request may indicate the triggering method, triggering conditions, reporting period, data volume, etc. of data reporting.
  • the data proxy network element can support stream data and batch data collection.
  • the data proxy network element can support real-time data and non-real-time data collection.
  • the data proxy network element can support the collection of various data.
  • Data can be divided into several categories. For example, data types can include but are not limited to: network data, user data, AI model data, and Internet of Things (IoT) data. This application does not limit the division of data. Divide into more or less types, or the types of data can be divided from other perspectives, or the types of data can not be divided.
  • IoT Internet of Things
  • Pre-processing refers to cleaning, filling, smoothing, merging, normalizing, consistency testing, field extraction of original data, format conversion, redundant data removal, compression, and filtering on the collected original data.
  • fusion operations are designed to improve data quality and lay the foundation for post-processing (such as analysis). Eliminating raw data may suffer from issues such as missing data, data noise, data redundancy, and/or imbalanced data sets.
  • Storage Supports centralized and distributed storage.
  • data that requires strict access protection or privacy protection such as user contract data, etc., is stored locally on the data proxy network element.
  • Each function of the data broker network element can directly provide services to service requesters through the application programmable interface API.
  • Data analysis Loosely coupled with the data agent network element, it can be deployed separately from the data agent network element as needed. It can support various data analysis technologies, such as AI training, AI reasoning, machine learning (ML), big data analysis, etc.
  • the data analysis function can call data services at various levels such as data collection, preprocessing, and storage of the data agent network element through API.
  • the AI model required for the data analysis process can be preset locally on the data proxy network element or pushed by the network service network element.
  • Data protection Use methods such as k-anonymity, l-diversity, differential hiding Private and other technologies process data so that attackers cannot directly obtain sensitive information from the desensitized data, thereby protecting data privacy.
  • the information of the data protection technology library can be pre-installed in the data agent network element, or pushed by DO on demand to provide security and privacy protection for data at each level of the data agent network element.
  • each functional module can be divided corresponding to each function, or two or more functions integrated into one module.
  • Integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of functions or modules in the embodiments of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • Figure 4 is a schematic diagram of a logical network topology provided by an embodiment of the present application. The following describes the logical network topology formed by the data orchestration network element orchestration data agent network element DA with reference to Figure 4.
  • the logical network topology may include but is not limited to: star logical network topology, mesh logical network topology, and hybrid logical network topology.
  • a DA serving as a convergence node can collect information from ordinary nodes DA, and can further process the collected information.
  • the DA as a convergence node can directly interact with the service requesting network element, and the ordinary node DA can interact with the service requesting network element through the DA as the convergence node.
  • This application is not limited to this, and the DA that directly interacts with the service requesting network element can DA can be any DA.
  • the star logical network topology can be applied to scenarios such as data aggregation and federated learning.
  • a DA as a sink node can hierarchically collect information from common nodes DA, and can further process the collected information.
  • the DA as a convergence node can directly interact with the service requesting network element, and the ordinary node DA can interact with the service requesting network element through the DA as a convergence node.
  • the DA that network elements directly interact with can be any DA.
  • the logical network topology shown in Figure 4 is only an example provided by this application.
  • the data orchestration network element can form any form of logical network topology based on the needs of the orchestration data agent network element DA, which can Just implement data services.
  • FIG 5 is a schematic diagram of an operation chain provided by an embodiment of the present application. The following describes the operation chain formed by the data proxy network element controlling each function in the data proxy network element with reference to Figure 5.
  • the operation chain is formed by the data agent network element obtaining the operations set for the data agent network element from the data orchestration network element, and orchestrating each function in the data agent network element according to the operations set by the data orchestration network element on the data agent network element.
  • the data proxy network element 1 obtains the settings for the data proxy network element 1 from the data orchestration network element, including: performing pre-processing such as fusion on data obtained from other data proxy network elements. After processing, analysis is performed to obtain the analysis results, and the analysis results are sent to the service requesting network element.
  • the data agent network element 1 arranges various functions to form an operation chain 1 as shown in Figure 5: collect data, then perform preprocessing, analyze the preprocessing results, and send the analysis results to the service requesting network element through the application programmable interface.
  • the operation includes: transmitting the collected data to the data proxy network element 2, then The data agent network element 1 arranges various functions to form an operation chain 2 as shown in Figure 5: collect data and send it to the data agent network element 2.
  • Figures 6a-6d are schematic diagrams of some network architectures provided by embodiments of the present application.
  • the communication system shown in Figure 1 can be applied to the network architecture shown in Figures 6a-6d.
  • Figure 6a shows a schematic diagram of the network architecture under the condition that the core network and access network equipment are fully serviced.
  • Figure 6b shows a schematic diagram of the network architecture under the condition that the access network equipment is not serviced and the core network is serviced.
  • Figure 6c shows Figure 6d shows a schematic diagram of the network architecture where each network element is directly interconnected.
  • the network architecture may include but is not limited to one or more of the following: service requesting network elements, terminal equipment, access network equipment, user plane network elements, data networks, core network elements, data
  • service requesting network elements terminal equipment, access network equipment, user plane network elements, data networks, core network elements, data
  • the specific implementation methods of the orchestration network element, data proxy network element, data storage network element, trusted anchor point, and service request network element can be referred to the explanations in Figures 1 to 5 above, and will not be described again here.
  • the network architecture may also include but is not limited to one or more of the following: mobility management network elements (Figure 6b and Figure 6c).
  • the network architecture may also include but is not limited to one or more of the following: session management network elements ( Figure 6c).
  • the core network elements shown in Figures 6a to 6c may include any core network elements except user plane network elements, mobility management network elements, and/or session management network elements.
  • Data proxy network elements can be deployed in any network element in the network architecture except data orchestration network elements, data storage network elements, and trusted anchor points. That is to say, in the network architecture, except data orchestration network elements, data storage network elements, , and any network element other than trusted anchor points can realize the function of data proxy network element.
  • the data orchestration network element interacts with other network elements (such as service request network elements, data proxy network elements, core network elements, and trusted anchor points, etc.) through the service interface N DO .
  • the data agent network element interacts with other network elements through the service interface N DA.
  • Interacting with other network elements such as service request network elements, data orchestration network elements, core network elements, terminal equipment, access network equipment, data storage network elements, and trusted anchor points, etc.
  • the data storage network element is service-oriented
  • the interface N DSF interacts with other network elements (such as data broker network elements, core network elements, terminal equipment, and access network equipment, etc.).
  • the trusted anchor point communicates with other network elements (such as data orchestration network) through the service interface N TA .
  • service-oriented interfaces can be used to improve the independence between network functions, achieve deployment flexibility and efficient scalability, and improve the development efficiency of new functions.
  • the network architecture may include but is not limited to one or more of the following: 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 equipment RAN, core network elements, terminal equipment, trusted anchor points, and data storage network elements.
  • service request network element data orchestration network element
  • RAN-DO access network domain data orchestration network element
  • CN-DO CN domain data orchestration network element
  • access network equipment RAN core network elements
  • terminal equipment terminal equipment
  • trusted anchor points trusted anchor points
  • data orchestration network elements are deployed hierarchically.
  • the data orchestration network elements can manage the RAN domain data orchestration network elements and the CN domain data orchestration network elements.
  • the data orchestration network elements can manage both the RAN domain data orchestration network elements and the CN domain data orchestration network elements. They can directly interact with each other.
  • the RAN domain data orchestration network element can directly interact with the access network equipment.
  • the CN domain data orchestration network element can directly interact with the core network element.
  • the trusted anchor point can directly interact with any network element in the network architecture.
  • Data storage network elements can directly interact with terminal equipment, access network equipment, and core network elements.
  • each network element is directly interconnected, which can meet the backward compatibility of the architecture.
  • FIG. 7 is a schematic structural diagram of a communication device 700 that can be used to perform the communication method provided by the embodiment of the present application.
  • the communication device 700 may be a data orchestration network element, a data proxy network element, a service requesting network element, or a trusted anchor point, or may be applied to a data orchestration network element, a data proxy network element, a service requesting network element, or a trusted anchor point.
  • the communication device 700 may include a processor 701 .
  • the communication device 700 may also include one or more of a memory 702 and a transceiver 703.
  • the processor 701 may be coupled to one or more of the memory 702 and the transceiver 703, for example, through a communication bus, or the processor 701 may be used alone.
  • the processor 701 is the control center of the communication device 700 and may be one processor or a collective name for multiple processing elements.
  • the processor 701 is one or more central processing units (CPUs), may also be an application specific integrated circuit (ASIC), or may be one or more processors configured to implement the embodiments of the present application.
  • An integrated circuit such as one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 701 can perform various functions of the communication device 700 by running or executing software programs stored in the memory 702 and calling data stored in the memory 702 .
  • the processor 701 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 7 .
  • the communication device 700 may also include multiple processors, such as the processor 701 and the processor 704 shown in FIG. 7 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor here may refer to one or more communications devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • Memory 702 may be a read-only memory (ROM) or other type of static storage communication device that can store static information and instructions, a random access memory (random access memory (RAM)) or other type that can store information and instructions.
  • type of dynamic storage communication device which can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, Optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage communication devices, or can be used to carry or store desired program codes in the form of instructions or data structures and Any other media capable of being accessed by a computer, without limitation.
  • the memory 702 may be integrated with the processor 701 or may exist independently and be coupled to the processor 701 through the input/output port (not shown in FIG. 7 ) of the communication device 700. This is not specifically limited in the embodiment of the present application.
  • the memory 702 is used to store software programs for executing the solution of the present application, and is controlled by the processor 701 for execution.
  • the memory 702 is used to store software programs for executing the solution of the present application, and is controlled by the processor 701 for execution.
  • the communication device 700 is a data orchestration network element, and the transceiver 703 can be used to communicate with a data proxy network element, a service requesting network element, and/or a trusted anchor point.
  • the communication device 700 is a data proxy network element, and the transceiver 703 can be used to communicate with the data orchestration network element, service Request communication from network elements and/or trusted anchors.
  • the communication device 700 is a service requesting network element, and the transceiver 703 can be used to communicate with a data orchestration network element, a data proxy network element, and/or a trusted anchor point.
  • the transceiver 703 may include a receiver and a transmitter (not shown separately in Figure 7). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.
  • the transceiver 703 may be integrated with the processor 701, or may exist independently and be coupled to the processor 701 through the input/output port (not shown in Figure 7) of the communication device 700. This is not specifically limited in the embodiment of the present application. .
  • the structure of the communication device 700 shown in Figure 7 does not constitute a limitation on the communication device.
  • the actual communication device may include more or less components than shown in the figure, or some components may be combined, or Different component arrangements.
  • FIG. 8 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • the communication method includes the following steps:
  • the service requesting network element sends the first service request message to the data orchestration network element.
  • the data orchestration network element receives the first service request message.
  • the first service request message may be used to request an application service or a business service.
  • the service requesting network element may be an application, an application server, or a network service network element.
  • application services may refer to services requested by applications or application servers
  • business services may refer to services requested by network service network elements.
  • the services requested by the first service request message may be different. .
  • the first service request message may be used to request, but is not limited to, one or more of the following services: network data-related services, user data-related services, artificial intelligence model data-related services, and Internet of Things data-related services.
  • network data may include but is not limited to one or more of the following: logs (such as debugging logs, security logs, call history record (CHR) logs, etc.), alarms, traffic statistics, configuration data, minimum Minimization of drive-tests (MDT) data, user session information, integrated sensing and communication (ISAC) data, digital twin network data, network metadata, network status, and network behavior.
  • logs such as debugging logs, security logs, call history record (CHR) logs, etc.
  • alarms traffic statistics, configuration data, minimum Minimization of drive-tests (MDT) data, user session information, integrated sensing and communication (ISAC) data, digital twin network data, network metadata, network status, and network behavior.
  • network data may include data collected by access network equipment, and/or data collected by terminal equipment, etc.
  • user data may include but is not limited to one or more of the following: user subscription information.
  • user subscription information For example, user portrait (profile), etc.
  • IoT data may include but is not limited to one or more of the following: environmental data, sensor data, and measurement data of IoT terminals.
  • the IoT data may include data collected by SIoT terminal devices and data collected by non-SIoT terminal devices through the IoT gateway.
  • artificial intelligence AI model data may include but is not limited to one or more of the following: training data sets corresponding to tasks, test data sets corresponding to tasks, local/global model data, and AI metadata.
  • the AI model data can be generated by training original data or preprocessed original data.
  • the data can be classified by considering multiple dimensions such as data type, data source, data consumer, and being as orthogonal as possible.
  • this application does not limit the classification of data, and it may be divided into more or fewer categories, or the types of data may be divided from other perspectives, or the types of data may not be divided.
  • the network service network element sends a first service request message to the data orchestration network element, and the first service request message is used to request access to user subscription data in the data proxy network element.
  • the operator's application for network planning and optimization (which may be referred to as the network planning and network optimization application) sends a first service request message to the data orchestration network element.
  • the first service request message is used to request training of the federated learning model.
  • Federated learning models are used for service quality prediction.
  • the network planning and network optimization application sends a first service request message to the data orchestration network element.
  • the first service request message is used to request prediction of the service quality of area A.
  • the request to predict the service quality of area A can be decomposed into the following requests: a request to train a federated learning model (request 1), and a request to use the (trained) federated learning model to predict the service quality of area A. Prediction(Request 2).
  • the process of predicting the service quality of area A can be decomposed into the following stages: training the federated learning model (stage 1), and using the (trained) federated learning model to predict the service quality of area A (stage 2 ).
  • stage 1 training the federated learning model
  • stage 2 using the (trained) federated learning model to predict the service quality of area A
  • phase 2 can be directly executed. Otherwise, phase 2 is executed after phase 1.
  • Stage 1 Translate the request for training the federated learning model into the corresponding demand information.
  • select the data agent network elements that participate in this data service and orchestrate each data agent network element to form a dynamic logic.
  • Network topology Among the data proxy network elements participating in this data service, select a data proxy network element with strong computing power (for example, data proxy network element 1) as the service (server) end to train the federated learning model.
  • Other data proxy network elements for example, data proxy network elements other than data proxy network element 1 among the data proxy network elements participating in this data service
  • the federated learning model is generated and sent to the service requesting network element by the data agent network element (for example, data agent network element 1 as the server DA), or stored in the data agent network element or DSF as required.
  • phase 1 is applicable to the scenario where the service requesting network element requests training of the federated learning model.
  • Phase 2 Translate the request for predicting the service quality of area A in the future using the federated learning model into the corresponding demand information.
  • Select a data proxy network element with strong computing power for example, data proxy network element 1
  • Other data proxy network elements for example, data proxy network elements other than data proxy network element 1 among the data proxy network elements participating in this data service
  • provide data for service quality prediction (such as real-time network data, etc.) to the data
  • the agent network element 1 can also perform some operations on the data (such as privacy removal).
  • the data agent network element 1 uses the federated learning model and data (original data or intermediate data) for reasoning. Obtain the service quality prediction result and send it to the service requesting network element.
  • the data proxy network element 1 can send the obtained intermediate data to the service requesting network element, and the service requesting network element uses the federated learning model and the intermediate data to perform inference and obtain service quality prediction results.
  • the federated learning model in the service requesting network element can be obtained from the data brokering network element or pre-configured, which is not limited by this application.
  • the application or network service network element sends a first service request message to the data orchestration network element.
  • the first service request message is used to request IoT data and process IoT data (such as pre-processing). Intermediate data obtained after processing, analysis, etc.), or abnormal behavior detection results of IoT terminal equipment, etc.
  • the first service request message may be based on requirements filled in a standard template.
  • a standard template could be a service level agreement.
  • the data orchestration network element determines at least one data agent network element and the operation configuration information corresponding to each of the at least one data agent network element based on the demand information and one or more data service capability information.
  • the demand information may be the service demand for the first data determined according to the service requested by the first service request message.
  • the first data may include data collected from the mobile communication network and/or synthesized data.
  • the first data may include but is not limited to one or more of the following: data on the terminal equipment side, data on each functional node on the access network equipment side, data on each functional node on the transmission network side, and data on the core network side. Data of each functional node, data of each functional node of OAM, and synthesized data.
  • synthetic data may refer to artificially synthesized data.
  • a face can be generated through adversarial learning, and the face data can be considered synthetic data.
  • the synthesized data can be used to train artificial intelligence models, etc.
  • the first data can be classified, and includes but is not limited to one or more of the following: network data, user data, artificial intelligence model data, and Internet of Things data.
  • the data can be classified by considering multiple dimensions such as data type, data source, data consumer, and being as orthogonal as possible.
  • this application does not limit the classification of the first data, and it can be divided into more or fewer categories, or the categories of the first data can be divided from other perspectives, or the categories of the first data may not be divided.
  • one or more data service capability information corresponds to one or more data proxy network elements.
  • data service capability information including data service capability information 1, data service capability information 2 and data service capability information 3
  • data service capability information 1 corresponds to data agent network element 1
  • data service capability information 2 corresponds to data agent Network element 2
  • data service capability information 3 correspond to data proxy network element 3.
  • the multiple data proxy network elements may be different types of data proxy network elements, or they may be the same type of data proxy network elements.
  • data proxy network element 1 to data proxy network element 3 are (or are deployed on) access network equipment.
  • data proxy network element 1 is a core network element
  • data proxy network element 2 is an access network device
  • data proxy network 3 is a terminal device.
  • data proxy network element 1 is an access network device
  • data proxy network element 2 is a terminal device
  • data proxy network element 3 is a terminal device.
  • At least one data broker network element may be at least one of one or more data broker network elements.
  • the data orchestration network element determines the participants from the data agent network element 1, data agent network element 2, and data agent network element 3 based on the demand information, data service capability information 1, data service capability information 2, and data service capability information 3.
  • the data proxy network elements of the secondary data service for example, select data proxy network element 1 and data proxy network element 2 to participate in this data service, and determine the corresponding operation configuration information of data proxy network element 1 and data proxy network element 2 respectively.
  • the operation configuration information of any one of the at least one data proxy network element may indicate the operation performed by any one of the data proxy network elements on the first data.
  • the operation configuration information corresponding to the data proxy network element 1 indicates the operation performed by the data proxy network element 1 on the first data or data generated based on the first data.
  • the operation configuration information corresponding to the data proxy network element 2 indicates the operation performed by the data proxy network element 2 on the first data or data generated based on the first data.
  • the demand information corresponds to at least one of one or more data service capability information.
  • the data proxy network element determines the data proxy network element participating in this data service based on the demand information and at least one data service capability information.
  • the data service capability of the selected data proxy network element needs to be able to realize the first data in the demand information.
  • Service requirements the selected data proxy network element needs to have the ability to complete this data service, so that the data service can be realized.
  • the data service capability information of any one of one or more data proxy network elements may include but is not limited to one or more of the following: the identity of any data proxy network element, any data The agent network element has location information, data collection capabilities, data preprocessing capabilities, data storage capabilities, data reporting capabilities, data analysis capabilities, the ability to interact with service requesting network elements, data protection capabilities, and data compression capabilities.
  • the data service capability information may have a corresponding relationship with the identity of the data proxy network element.
  • the location information may refer to geographical location information, and the location information may include longitude and latitude, etc.
  • the data collection capability may include data types that support collection, and the data types may include but are not limited to one or more of the following: network data, user data, Internet of Things data, and artificial intelligence model data.
  • data preprocessing capabilities can include supported preprocessing methods, such as field extraction, format conversion, redundant data removal, compression, fusion, etc. of original data.
  • the data storage capability may include but is not limited to one or more of the following: storable data capacity, encryption algorithm for storing data, and storage method.
  • the data reporting capability may include but is not limited to one or more of the following: minimum reporting period, amount of data reported at a time, maximum amount of data reported, whether to support file upload, and whether to support streaming data.
  • data analysis capabilities may include but are not limited to one or more of the following: supported analysis tasks, whether to support AI training, and whether to support AI inference.
  • the ability to interact with the service requesting network element may include but is not limited to: whether it can provide application programmable interface services.
  • data protection capabilities may include but are not limited to one or more of the following: supported data protection technologies, such as k-anonymity, l-diversity, differential privacy, Homomorphic encryption, and secure multi-party computation, etc.
  • supported data protection technologies such as k-anonymity, l-diversity, differential privacy, Homomorphic encryption, and secure multi-party computation, etc.
  • the data compression capability may include but is not limited to one or more of the following: supported data compression algorithms, such as Huffman Coding, arithmetic coding, etc.
  • the method can also refer to the description of the functions of the data proxy network element in Figure 2 above.
  • the data proxy network element having corresponding functions can mean having corresponding capabilities.
  • the demand information may include but is not limited to one or more of the following service requirements: geographical location, data collection, data preprocessing, data storage, data reporting, data analysis, interaction with service requesting network elements, and data protection. , and data compression.
  • the requirement information may correspond to a data service task identifier (DSID).
  • DSID data service task identifier
  • the data service task identifier may be used to identify the data service task corresponding to the first service request message.
  • the data orchestration network element can perform demand translation on the service requested by the first service request message, and translate (or map) it into a service demand for the function of the data proxy network element.
  • the first service request message is used to request prediction of service quality in area A
  • the data orchestration network element performs demand translation.
  • the obtained demand information may include: area A, data collection, data preprocessing, data analysis, and services.
  • the type of the requested network element to interact with and the first data is network data.
  • the operations indicated by the operation configuration information may include but are not limited to one or more of the following: data collection, data preprocessing, data protection, data storage, data analysis, and interaction with service requesting network elements.
  • the method provided by the embodiment of the present application may also include: the data orchestration network element determines the first communication information.
  • the first communication information may be used to indicate information of a data proxy network element in at least one data proxy network element that directly communicates with the service requesting network element.
  • the first communication information may include but is not limited to one or more of the following: the address of data proxy network element 1, data proxy network The identifier of element 1 and the index of data proxy network element 1.
  • the first communication information may be determined based on data service capability information of at least one data broker network element.
  • a data proxy network element having the ability to interact with the service requesting network element is selected from at least one data proxy network element as the data proxy network element that directly communicates with the service requesting network element.
  • the data orchestration network element can select the data agent network element that directly communicates with the service requesting network element from the determined data agent network elements participating in this data service.
  • the following describes the operation configuration information corresponding to the data proxy network element and the data proxy network element determined by the data orchestration network element to participate in this data service.
  • the obtained demand information may include: area A, data collection, data preprocessing, data analysis, and interaction with the service requesting network element. .
  • data service capability information 1, data service capability information 2 and data service capability information 3 Based on the demand information, data service capability information 1, data service capability information 2 and data service capability information 3, the data orchestration network element determines to participate in this data from the data agent network element 1, data agent network element 2 and data agent network element 3 The data proxy network element of the service. Data service capability information 1 to data service capability information 3 correspond to data agent network element 1 to data agent network element 3 respectively.
  • data service capability information 1 includes: area A, supports data preprocessing, supports data storage, supports AI training and AI reasoning, supports interaction with service requesting network elements, and supports data collection.
  • data service capability information 2 includes: area A, supports data preprocessing, does not support AI training and AI reasoning, does not support interaction with service requesting network elements, and supports data collection.
  • data service capability information 3 includes: area B, supports data preprocessing, supports data storage, does not support AI training and AI reasoning, supports interaction with service requesting network elements, and supports data collection.
  • the data orchestration network element can determine that the data proxy network element 1 and the data proxy network element 2 can jointly realize the service requirements in the demand information.
  • the geographical location of data agent network element 3 is area B, not area A.
  • data agent network element 3 does not support AI training and AI reasoning, and data agent network element 3 cannot participate in training the AI model.
  • the data orchestration network element determines the operation configuration information 1 corresponding to the data proxy network element 1 and the operation configuration information 2 corresponding to the data proxy network element 2 based on the demand information, data service capability information 1, and data service capability information 2.
  • the operation Configuration information 1 includes: collection of raw data, data preprocessing, AI training and AI reasoning, and interaction with service request network elements.
  • the operation configuration information 2 includes: collecting raw data, data preprocessing, and interacting with the data agent network element 1.
  • the data orchestration network element determines the data proxy network element and the corresponding operation configuration of the data proxy network element participating in this data service. information is explained.
  • data service capability information 1, data service capability information 2 and data service capability information 3 Based on the demand information, data service capability information 1, data service capability information 2 and data service capability information 3, the data orchestration network element determines to participate in this data from the data agent network element 1, data agent network element 2 and data agent network element 3 The data proxy network element of the service. Data service capability information 1 to data service capability information 3 correspond to data agent network element 1 to data agent network element 3 respectively.
  • the required information includes: area A, data collection, data preprocessing, data analysis, and interaction with service requesting network elements.
  • data service capability information 1 includes: area A, supports data preprocessing, supports data storage, supports AI training and AI reasoning, supports interaction with service requesting network elements, and supports data collection.
  • data service capability information 2 includes: area A, supports data preprocessing, does not support AI training and AI reasoning, does not support interaction with service requesting network elements, and supports data collection.
  • data service capability information 3 includes: area B, supports data preprocessing, supports data storage, does not support AI training and AI reasoning, supports interaction with service requesting network elements, and supports data collection.
  • the data orchestration network element can determine that the data proxy network element 1 and the data proxy network element 2 can jointly realize the service requirements in the demand information, data
  • the geographical location of proxy network element 3 is area B, not area A.
  • Data proxy network element 3 cannot participate in predicting the service quality of area A.
  • the data orchestration network element determines based on the demand information, data service capability information 1, and data service capability information 2 Operation configuration information 1 corresponding to data proxy network element 1 and operation configuration information 2 corresponding to data proxy network element 2 respectively.
  • operation configuration information 1 includes: AI training, AI reasoning, and interaction with service requesting network elements.
  • operation configuration information 2 includes: collecting raw data, data preprocessing, and interacting with the data agent network element 1.
  • the above S802 may include: in the case that the service requesting network element has the permission to access the first data, the data orchestration network element determines at least one of the following according to the demand information and one or more data service capability information.
  • the data proxy network element participating in the data service and the corresponding operation configuration information are determined only when the service requesting network element has the authority to access the first data. Otherwise, the data proxy network element participating in the data service and the corresponding operation configuration information are not determined.
  • the method provided by the embodiment of the present application may also include: S806, the trusted anchor point sends a first verification response message to the first data proxy network element.
  • the data orchestration network element receives the first verification response message from the trusted anchor point.
  • the first verification response message may indicate that the service requesting network element has the authority to access the first data, or indicates that the service requesting network element does not have the authority to access the first data.
  • whether the service requesting network element has the permission to access the first data can be obtained by the data orchestration network element from the trusted anchor point.
  • S806 may be executed before the above-mentioned S802.
  • the method provided by the embodiment of the present application may also include: S807, the data orchestration network element sends a first verification request message to the trusted anchor point.
  • the trusted anchor point receives the first verification request message from the data orchestration network element.
  • the first verification request message may be used to request verification whether the service requesting network element has the authority to access the first data.
  • S807 can be executed before the above-mentioned S806.
  • the method provided by the embodiment of the present application may also include: S808, one or more data proxy network elements send data service capability information to the data orchestration network element.
  • the data orchestration network element receives data service capability information corresponding to one or more data proxy network elements.
  • the determined at least one data proxy network element includes the first data proxy network element.
  • S808 in Figure 8 takes the first data proxy network element as an example.
  • the first data proxy network element sends data service capabilities to the data orchestration network element. information.
  • the data orchestration network element receives the data service capability information from the first data proxy network element.
  • S808 may be executed before the above-mentioned S801, or S808 may be executed before the above-mentioned S802.
  • the method provided by the embodiment of the present application may also include: one or more data proxy network elements registering with the data orchestration network element. This may be performed before or at the same time as the above S808. This application Not limited.
  • the data orchestration network element sends operation configuration information to the first data proxy network element.
  • the first data proxy network element receives the operation configuration information from the data orchestration network element.
  • the operation configuration information may indicate an operation performed by the first data proxy network element on the first data.
  • the data orchestration network element sends corresponding operation configuration information to each data proxy network element in at least one data proxy network element.
  • the method provided by the embodiment of the present application may also include: the data orchestration network element sending updated data security and privacy protection technology library information to one or more of at least one data proxy network element. and/or updated Analysis ToolPak information.
  • the data orchestration network element sending updated data security and privacy protection technology library information to one or more of at least one data proxy network element. and/or updated Analysis ToolPak information.
  • one or more of the at least one data broker network element receives updated information on the data security and privacy protection technology library and/or updated information on the analysis tool library from the data orchestration network element.
  • At least one data broker network element may include a first data broker network element, and the first data broker network element receives updated information from the data security and privacy protection technology library and/or updated analysis tools from the data orchestration network element. library information.
  • the information of the data security and privacy protection technology library may include but is not limited to one or more of the following: the identification of the data security and privacy protection technology library, the index of the data security and privacy protection technology library, and the data security and privacy Protect technology library.
  • the information of the analysis tool library may include, but is not limited to, one or more of the following: the identification of the analysis tool library, the index of the analysis tool library, and the analysis tool library itself.
  • the data orchestration network element can be pushed to the data broker network element. In this way, data security protection, data privacy protection, etc. can be achieved.
  • the data orchestration network element sends operation configuration information to the first data proxy network element, and sends updated data security and privacy protection technology library information and/or updated analysis tool library information in the same step. Execution can also be executed individually, which is not limited by this application.
  • the method provided by the embodiment of the present application may also include: S809, the data orchestration network element sends the first communication information to the service requesting network element.
  • the service requesting network element receives the first communication information from the data orchestration network element.
  • the service requesting network element can establish direct interaction with the first data proxy network element based on the received first communication information, and can directly receive messages from the first data proxy network element.
  • the first data proxy network element processes the first data according to the operation indicated by the operation configuration information to obtain the first information.
  • the first data proxy network element obtains the operations indicated by the operation configuration information, arranges each function in the first data proxy network element to form an operation chain, and the output of the previous function is the input of the next function. According to the operation chain, the The first data is processed to obtain the first information.
  • the first information may be original data, intermediate data, analysis results, etc.
  • the above S804 may include the following steps 1 to 2.
  • Step 1 The first data proxy network element sends a data request message to the third data proxy network element according to the operation configuration information.
  • the third data proxy network element receives the data request message from the first data proxy network element.
  • the data request message can be used to request but is not limited to one or more of the following data: network data, user data household data, IoT data, and artificial intelligence model data.
  • the operation configuration information may include: collecting the first data from the third data proxy network element.
  • first data proxy network element and the third data proxy network element may be different types of data proxy network elements, or may be the same type of data proxy network elements.
  • the third data proxy network element may be access network device 2, or a terminal device.
  • inter-domain data proxy network element connections can be formed to form a cross-domain data service architecture.
  • the data request message may include security information.
  • the security information may be used to verify whether the first data proxy network element has the authority to access the first data.
  • security information may include, but is not limited to, private key signatures.
  • Step 2 The third data proxy network element sends a data response message to the first data proxy network element.
  • the first data proxy network element receives the data response message from the third data proxy network element.
  • the data response message may include one or more data included in the data request message.
  • the first information may include first data, such as network data, user data, Internet of Things data, artificial intelligence model data, etc.
  • the first data proxy network element obtains the first data from the data source (the third data proxy network element).
  • the above step 2 may include: in the case that the first data proxy network element has the first data to access the third data proxy network element, the third data proxy network element sends a data response message to the first data proxy network element. , Otherwise, reject the request, which can achieve the trusted service requirements of E2E for data.
  • whether the first data proxy network element has the permission to access the first data of the third data proxy network element can be obtained by the third data proxy network element from the trusted anchor point.
  • the third proxy network element sends a verification request message to the trusted anchor point, and receives a verification corresponding message from the trusted anchor point.
  • the verification request message may be used to request verification of whether the first data proxy network element has the authority to access the first data of the third data proxy network element.
  • the verification request message may include: security information corresponding to the first data proxy network element.
  • the verification response message may indicate that the first data proxy network element has or does not have permission to access the first data of the third data proxy network element.
  • the trusted anchor point can check the data access policy, verify the security information, and obtain whether the first data proxy network element has or does not have permission to access the first data of the third data proxy network element.
  • the trusted anchor point can check the data access policy and verify the security information according to the data type of the first data.
  • the data access policy may include: the first data proxy network element has the permission to access the network data of the third data proxy network element, and the first data proxy network element does not have the permission to access the user data of the third data proxy network element. If the first data is user data, the verification response message may indicate that the first data proxy network element does not have the authority to access the user data of the third data proxy network element. If the first data includes user data and network data, the verification response message may indicate that the first data proxy network element does not have the authority to access the user data of the third data proxy network element, and the first data proxy network element has the authority to access the third data proxy network element. The network data permissions of the network element.
  • the above S804 may include: the first data proxy network element processes the second information according to the operation indicated by the operation configuration information to obtain the first information.
  • the second information may be received by the first data proxy network element.
  • the second information may be received by the first data broker network element from other data broker network elements.
  • the second information may be obtained based on the first data.
  • the second information may be obtained by other data proxy network elements after processing the first data (such as data collection, data preprocessing, data protection, data storage, and/or data analysis, etc.).
  • the operation configuration information may include, but is not limited to, one or more of the following: data collection, data preprocessing, data protection, data storage, and data analysis.
  • the second information is obtained after other data agent network elements perform data preprocessing on the first data.
  • the operation configuration information includes data analysis and data protection.
  • the first data agent network element forms an operation chain (performing data analysis) based on the operation configuration information. , and then perform security protection), analyze the second information and perform security protection to obtain the first information.
  • the above-mentioned S804 may include: the first data proxy network element processes the first data and application data according to the operation indicated by the operation configuration information to obtain the first information.
  • the application data may be obtained by the first data proxy network element from the application network element.
  • a data proxy network element can be deployed in the application network element.
  • application data may include, but is not limited to: user historical behavior records collected based on application compliance (for example, user authorization).
  • the first data agent network element collaboratively processes IoT data and application data, and can quickly and accurately determine abnormal behaviors of IoT terminal devices.
  • S805a When the operation configuration information indicates that the first data proxy network element communicates with the second data proxy network element, the first data proxy network element sends the first information to the second data proxy network element. Correspondingly, the second data proxy network element receives the first information from the first data proxy network element.
  • the operation configuration information may instruct the first data proxy network element to transmit the first information to the second data proxy network element.
  • the operation configuration information may include: interacting with the second data proxy network element.
  • the first data proxy network element can send the first information to the second data proxy network element, and the second data proxy network element can process or forward the first data according to the corresponding operation configuration information of the second data proxy network element. wait.
  • the method provided by the embodiment of the present application may also include: S810, the trusted anchor point sends a second verification response message to the first data proxy network element.
  • the first data proxy network element receives the second verification response message from the trusted anchor point.
  • the second verification response message may indicate that the second data proxy network element has the permission to access the first data of the first data proxy network element, or indicate that the second data proxy network element does not have the permission to access the first data proxy network element. The permissions of the first data.
  • S810 may be executed before the above-mentioned S805a.
  • the first data proxy network element obtains that the second data proxy network element has the authority to access the first data of the first data proxy network element, it sends the first information to the second data proxy network element; otherwise, it does not send the first information to the second data proxy network element.
  • Second data generation The management network element sends the first information, which can realize the trusted service requirements of E2E of data.
  • the method provided by the embodiment of the present application may also include: S811, the first data proxy network element sends a second verification request message to the trusted anchor point.
  • the trusted anchor point receives the second verification request message from the first data proxy network element.
  • the second verification request message may be used to request verification of whether the second data proxy network element has the authority to access the first data of the first data proxy network element.
  • the second verification request message may include: security information corresponding to the second data proxy network element.
  • the security information corresponding to the second data proxy network element may be obtained by the first data proxy network element from the second data proxy network element.
  • security information may include, but is not limited to, private key signatures.
  • the trusted anchor when it receives the second verification request message, it can check the data access policy, verify the security information, and obtain whether the second data proxy network element has or does not have the permission to access the first data of the first data proxy network element.
  • the specific implementation is the implementation in which the above-mentioned trusted anchor receives the verification request message, can check the data access policy, verify the security information, and obtain whether the first data proxy network element has or does not have the permission to access the first data of the third data proxy network element. The method is similar and will not be described again here.
  • the first information may be obtained based on the first data.
  • the first data proxy network element may be a data proxy network element that directly communicates with the service requesting network element.
  • the operation configuration information may instruct the first data proxy network element to transmit the first information to the service requesting network element.
  • the operation configuration information may include: interacting with the service requesting network element.
  • the service requesting network element obtains the first information.
  • the first information may be original data, intermediate data, analysis results, etc.
  • the method provided by the embodiment of the present application may also include: S812, the first data proxy network element sends processing behavior information to the trusted anchor point.
  • the trusted anchor point receives processing behavior information from the first data proxy network element.
  • the processing behavior information may indicate the processing behavior of the first data proxy network element on the first data.
  • the first data is user data
  • the processing behavior information may indicate the processing behavior of the first data agent network element on the first data, such as collection, preprocessing, storage, data analysis, data protection, privacy removal, and sending, etc. .
  • trusted anchors can record processing actions on a distributed ledger.
  • any data proxy network element that involves the processing of user data during the processing process can send processing behavior information to the trusted anchor point, which can meet the compliance requirements of GDPR/PIPL.
  • the method provided by the embodiment of the present application may also include: service requesting the network element to process the first information to obtain application services or business services.
  • the first information may not be the final result desired by the service requesting network element.
  • it may be intermediate data.
  • the service requesting network element processes the first information to obtain the final result.
  • the above service requesting network element processes the first information to obtain application services or business services, which may include: the service requesting network element uses the first information to obtain abnormal behavior information of the Internet of Things terminal device.
  • abnormal behaviors of IoT terminal equipment can be obtained, such as hijacking of IoT terminal equipment, air interface signaling distributed denial of service (DDoS) attacks, etc.
  • DDoS distributed denial of service
  • the service requesting network element processes the first information to obtain application services or business services, which may include: the service requesting network element uses the first information and artificial intelligence model parameter configuration information to predict service quality.
  • the artificial intelligence model parameter configuration information can be used to predict service quality.
  • the service requesting network element uses the artificial intelligence model parameter configuration information and the first information (which is intermediate data) to perform reasoning and obtain the service quality prediction result.
  • the service requesting network element locally stores the artificial intelligence model parameter configuration information.
  • the artificial intelligence model parameter configuration information can be obtained through the first data proxy network element, and the artificial intelligence model parameter configuration information can be requested from the first data proxy network element.
  • the service requesting network element can hash the abstract of the artificial intelligence model and compare it with the hash value stored on the distributed ledger to verify the consistency of the model.
  • the data orchestration network element receives the first service request message, and determines the data participating in this data service from one or more data proxy network elements based on the demand information and one or more data service capability information. Agent network element, and obtains the operation configuration information corresponding to each data agent network element participating in this data service.
  • the operation configuration information indicates the operation performed by the data agent network element on the first data.
  • the demand information is based on the first service request message.
  • the requested service determines the service requirement for the first data.
  • the data orchestration network element sends the operation configuration information to the corresponding data agent network element, and the data agent network element performs the operations indicated by the operation configuration information. In this way, data services can be realized.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Figure 9 illustrates the method shown in Figure 8 by taking the NS network element to receive the service request message and translate it into demand information, and the data orchestration network element to obtain the demand information from the NS network element as an example.
  • the communication method includes the following steps:
  • the service requesting network element sends the first service request message to the network service network element.
  • the network service network element receives the first service request message.
  • the first service request message may be used to request an application service or a business service.
  • the specific implementation method of the first service request message may refer to the corresponding description in S801 above, and will not be described again here.
  • the operator's application for network planning and optimization (which may be referred to as the network planning and network optimization application) sends a first service request message to the data orchestration network element.
  • the first service request message is used to request training of the federated learning model.
  • Federated learning models are used for service quality prediction.
  • the network planning and network optimization application sends a first service request message to the data orchestration network element.
  • the first service request message is used to request prediction of the service quality of area A.
  • the network service network element sends demand information to the data orchestration network element. Accordingly, the data orchestration network element receives Demand information from network service network elements.
  • the demand information may be the service demand for the first data determined according to the service requested by the first service request message.
  • the demand information may be the service demand for the first data determined by the network service network element according to the service requested by the first service request message.
  • the network service network element can perform demand translation on the service requested by the first service request message, and translate (or map) it into a service demand for the function of the data proxy network element.
  • the obtained demand information may include: area A, data collection, data preprocessing, data analysis, and interaction with the service requesting network element. .
  • the network service network element determines the demand information, which is applicable to but not limited to the following scenarios: requesting to train the federated learning model (for example, stage 1 in S802 above) scenario and requesting to predict the service quality of area A (for example, S802 above) The scenario in stage 2).
  • the data orchestration network element determines at least one data agent network element and the operation configuration information corresponding to each of the at least one data agent network element based on the demand information and one or more data service capability information.
  • the specific implementation method of the demand information, data service capability information, at least one data proxy network element, and operation configuration information can refer to the corresponding description in S801 above, and will not be described again here.
  • the demand information corresponds to at least one of one or more data service capability information.
  • S903 may refer to the corresponding description in S802 above, and will not be described again here.
  • the method provided by the embodiment of the present application may also include: the data orchestration network element determines the first communication information.
  • the data orchestration network element determines the first communication information.
  • the data orchestration network element sends operation configuration information to the first data proxy network element.
  • the first data proxy network element receives the operation configuration information.
  • the method provided by the embodiment of the present application may also include: S907, the network service network element sends the artificial intelligence training model parameter configuration information to the first data proxy network element.
  • the first data proxy network element receives the artificial intelligence training model parameter configuration information from the network service network element.
  • the artificial intelligence training model parameter configuration information can be used by the data proxy network element to train the AI model requested by the service requesting network element based on the artificial intelligence training model.
  • the AI model can be used for service quality prediction.
  • the first data proxy network element processes the first data according to the operation indicated by the operation configuration information to obtain the first information.
  • the operation configuration information indicates that the first data proxy network element communicates with the second data proxy network element
  • the first data proxy network element sends the first information to the second data proxy network element.
  • the second data proxy network element receives the first information from the first data proxy network element.
  • S906a may refer to the corresponding description in S805a above, and will not be described again here.
  • S906b may refer to the corresponding description in S805b above, and will not be described again here.
  • the method provided by the embodiment of the present application may also include S908-S914 as shown in Figure 9.
  • S908-S914 is similar to the above-mentioned S806-S812, and reference may be made to the above-mentioned S806-S812, which will not be described again here.
  • the network service network element receives the first service request message and sends demand information to the data orchestration network element.
  • the data orchestration network element receives the first service request message from one or more data orchestration network elements based on the demand information and one or more data service capability information. Determine the data proxy network elements participating in this data service among the data proxy network elements, and obtain the operation configuration information corresponding to each data proxy network element participating in this data service.
  • the operation configuration information instructs the data proxy network element to first
  • the operation performed on the data the demand information is the service demand for the first data determined based on the service requested by the first service request message.
  • the data orchestration network element sends the operation configuration information to the corresponding data agent network element, and the data agent network element performs the operations indicated by the operation configuration information. In this way, data services can be realized.
  • FIG. 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the communication device can be applied to the communication system shown in Figure 1.
  • Figure 10 only shows the main components of the communication device.
  • the communication device 1000 includes: a transceiver module 1001 and a processing module 1002.
  • the communication device 1000 shown in Figure 10 can be applied to the system shown in Figure 1 to perform the functions of the data orchestration network element in the communication method described in Figures 8 and 9.
  • the transceiver module 1001 is used to receive the first service request message.
  • the processing module 1002 is configured to determine at least one data proxy network element and the operation configuration information corresponding to each of the at least one data proxy network element based on the demand information and one or more data service capability information.
  • the transceiver module 1001 is also used to send operation configuration information.
  • the demand information is the service demand for the first data determined based on the service requested by the first service request message.
  • One or more data service capability information corresponds to one or more data agent network elements.
  • At least one data agent The network element is at least one of one or more data proxy network elements, and the demand information corresponds to one or At least one of the plurality of data service capability information and the operation configuration information of any one of the at least one data proxy network element indicate the operation performed by any one of the data proxy network elements on the first data.
  • transceiver module 1001 may include a receiving module and a sending module (not shown in Figure 10), which is not specifically limited.
  • the communication device 1000 may also include a storage module (not shown in FIG. 10), which stores programs or instructions.
  • the processing module 1002 executes the program or instruction, the communication device 1000 can perform the functions of the data orchestration network element in the communication method shown in FIG. 8 or FIG. 9 .
  • the communication device 1000 may be a data orchestration network element, or may be a chip (system) or other component or component that can be disposed on the data orchestration network element, which is not limited in this application.
  • the technical effects of the communication device 1000 can be referred to the technical effects of the communication method shown in FIG. 8 and FIG. 9 , which will not be described again here.
  • the communication device 1000 shown in Figure 10 can be applied to the system shown in Figure 1 to perform the communication method of the first data proxy network element in the above-mentioned Figure 8 and Figure 9. Function.
  • the transceiver module 1001 is used to receive operation configuration information.
  • the processing module 1002 is configured to process the first data according to the operation indicated by the operation configuration information to obtain the first information.
  • the transceiver module 1001 is also configured to send the first information to the second data proxy network element when the operation configuration information instructs the communication device to communicate with the second data proxy network element.
  • the transceiver module 1001 is also configured to send the first information to the service requesting network element when the operation configuration information indicates that the communication device communicates with the service requesting network element.
  • the operation configuration information indicates an operation performed by the communication device on the first data.
  • transceiver module 1001 may include a receiving module and a sending module (not shown in Figure 10), which is not specifically limited.
  • the communication device 1000 may also include a storage module (not shown in FIG. 10), which stores programs or instructions.
  • the processing module 1002 executes the program or instruction, the communication device 1000 can perform the function of the first data proxy network element in the communication method shown in FIG. 8 or FIG. 9 .
  • the communication device 1000 may be the first data proxy network element, or may be a chip (system) or other components or components that can be disposed on the first data proxy network element, which is not limited in this application.
  • the technical effects of the communication device 1000 can be referred to the technical effects of the communication method shown in FIG. 8 and FIG. 9 , which will not be described again here.
  • FIG. 11 is a schematic structural diagram of yet another communication device provided by an embodiment of the present application.
  • the communication device can be applied to the communication system shown in Figure 1.
  • Figure 11 only shows the main components of the communication device.
  • the communication device 1100 includes: a sending module 1101 and a receiving module 1102.
  • the sending module 1101 is used to send the first service request message to the data orchestration network element.
  • the receiving module 1102 is used to receive the first information from the data proxy network element. Wherein, the first information is obtained based on the first data.
  • the receiving module 1102 and the sending module 1101 can be set up separately, or they can be integrated into one module, that is, the transceiving module (not shown in Figure 11). This application does not specifically limit the specific implementation of the receiving module 1102 and the sending module 1101.
  • the communication device 1100 may also include a processing module 1103 and a storage module (not shown in Figure 11), which stores programs or instructions.
  • the processing module 1103 executes the program or instruction, the communication device 1100 can perform the function of the service requesting network element in the communication method shown in FIG. 8 or FIG. 9 .
  • the communication device 1100 may be a service requesting network element, or may be a chip (system) or other components or components that can be disposed on the service requesting network element, which is not limited in this application.
  • the technical effects of the communication device 1100 can be referred to the technical effects of the communication method shown in FIG. 8 and FIG. 9 , which will not be described again here.
  • An embodiment of the present application provides a communication system.
  • the communication system includes a data orchestration network element and a first data proxy network element, and may also include a service requesting network element.
  • the data orchestration network element is used to perform the actions of the data orchestration network element in the above method embodiment
  • the first data proxy network element is used to perform the actions of the first data proxy network element in the above method embodiment
  • the service request network element is used to To perform the action of the service requesting network element in the above method embodiment
  • the specific execution method and process may refer to the above method embodiment, and will not be described again here.
  • Embodiments of the present application provide a chip system, which includes a logic circuit and an input/output port.
  • the logic circuit can be used to implement the processing function involved in the communication method provided by the embodiment of the present application, and the input/output port can be used for the transceiver function involved in the communication method provided by the embodiment of the present application.
  • the input port can be used to implement the receiving function involved in the communication method provided by the embodiment of the present application
  • the output port can be used to implement the sending function involved in the communication method provided by the embodiment of the application.
  • the chip system further includes a memory, which is used to store program instructions and data for implementing functions involved in the communication method provided by the embodiments of the present application.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores computer programs or instructions.
  • the communication method provided by the embodiments of the present application is executed.
  • An embodiment of the present application provides a computer program product.
  • the computer program product includes: a computer program or instructions.
  • the communication method provided by the embodiment of the present application is executed.
  • the processor in the embodiment of the present application can be a central processing unit (CPU).
  • the processor can also be other general-purpose processors, digital signal processors (DSP), special-purpose integrated processors, etc.
  • Circuit application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM synchronous dynamic random access memory
  • synchronous DRAM synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory access memory serial DRAM, SLDRAM
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination.
  • the above-described embodiments may be implemented in whole or in part 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 or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • At least one refers to one or more, and “plurality” refers to two or more.
  • At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法、装置及系统，能够实现数据服务。该方法包括：数据编排网元接收第一服务请求消息，根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息，数据编排网元发送操作配置信息。需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求，一个或多个数据服务能力信息与一个或多个数据代理网元一一对应，至少一个数据代理网元是一个或多个数据代理网元中的至少一个，需求信息对应一个或多个数据服务能力信息中的至少一个，至少一个数据代理网元中任一个数据代理网元的操作配置信息指示任一个数据代理网元对第一数据执行的操作。

Description

通信方法、装置及系统
本申请要求于2022年05月31日提交国家知识产权局、申请号为202210612736.9、申请名称为“通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、装置及系统。
背景技术
数据服务(data service，DS)可指对数据进行采集、预处理、以及分析等操作后将数据作为一种服务产品提供。随着移动通信网络规模、新技术等的发展，移动通信网络中的数据越来越多，对数据服务的需求也越来越多。
为此，可以基于数据服务架构对移动通信网络中的数据进行处理，实现数据服务。但具体如何实现，还有待研究。
发明内容
本申请实施例提供一种通信方法、装置及系统，能够基于数据服务架构对移动通信网络中的数据进行处理，实现数据服务。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种通信方法。该通信方法包括：数据编排网元接收第一服务请求消息，数据编排网元根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息，数据编排网元发送操作配置信息。其中，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求，一个或多个数据服务能力信息与一个或多个数据代理网元一一对应，至少一个数据代理网元是一个或多个数据代理网元中的至少一个，需求信息对应一个或多个数据服务能力信息中的至少一个，至少一个数据代理网元中任一个数据代理网元的操作配置信息指示任一个数据代理网元对第一数据执行的操作。
基于第一方面提供的通信方法，数据编排网元接收第一服务请求消息，根据需求信息和一个或多个数据服务能力信息，从一个或多个数据代理网元中确定参与本次数据服务的数据代理网元，并获得参与本次数据服务的每个数据代理网元对应的操作配置信息，该操作配置信息指示数据代理网元对第一数据执行的操作，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。数据编排网元将操作配置信息发给对应的数据代理网元，数据代理网元执行操作配置信息所指示的操作，如此，可以实现数据服务。
在一种可能的设计方式中，第一服务请求消息可用于请求应用服务或业务服务。可选地，应用服务可指由应用、或应用服务器请求的服务，业务服务可指由网络业务网元请求的服务，在不同的场景中，第一服务请求消息所请求的服务可以不同。
在一种可能的设计方式中，第一服务请求消息来自服务请求网元，第一方面提供的通信方法，还可以包括：数据编排网元接收来自可信锚点的第一验证响应消息。其中，第一验证响应消息可指示服务请求网元具有访问第一数据的权限。也就是说，服务请求网元是否具有访问第一数据的权限可以是数据编排网元从可信锚点获取的，可以实现可信数据服务。
在一种可能的设计方式中，第一方面提供的通信方法，还可以包括：数据编排网元向可信锚点发送第一验证请求消息。其中，第一验证请求消息可用于请求验证服务请求网元是否具有访问第一数据的权限。如此，可以实现可信数据服务。
在一种可能的设计方式中，第一服务请求消息来自服务请求网元，第一方面提供的通信方法，还可以包括：数据编排网元发送第一通信信息。其中，第一通信信息可用于指示至少一个数据代理网元中与服务请求网元直接通信的数据代理网元的信息。例如，数据编排网元可以从确定的参与本次数据服务的数据代理网元中选择与服务请求网元直接通信的数据代理网元，服务请求网元可以与该数据代理网元建立直接交互。
在一种可能的设计方式中，第一方面提供的通信方法，还可以包括：数据编排网元接收一个或多个数据代理网元对应的数据服务能力信息。
在一种可能的设计方式中，一个或多个数据代理网元中任一个数据代理网元的数据服务能力信息可以包括如下一项或多项：任一个数据代理网元的标识、任一个数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力。需要说明的是，数据代理网元的数据服务能力不限于此。
在一种可能的设计方式中，操作配置信息所指示的操作可以包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与服务请求网元交互。如此，数据代理网元可以执行操作配置信息所指示的操作。
需要说明的是，本申请中操作配置信息所指示的操作与通常的编译码、调制解调操作、速率匹配不同。
在一种可能的设计方式中，需求信息可以包括如下一项或多项服务需求：地理位置、数据采集、数据预处理、数据存储、数据上报、数据分析、与服务请求网元交互、数据保护、和数据压缩。
在一种可能的设计方式中，需求信息可与数据服务任务标识对应。例如，数据服务任务标识可用于标识第一服务请求消息对应的数据服务任务。
在一种可能的设计方式中，第一方面提供的通信方法，还可以包括：数据编排网元向至少一个数据代理网元中的一个或多个发送更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。也就是说，数据安全及隐私保护技术库和分析工具库等如果有更新，数据编排网元可以推送给数据代理网元，如此，可以实现数据安全保护、数据隐私保护等。
在一种可能的设计方式中，数据编排网元可部署在网络业务网元中。如此，数据编排网元的功能可以由网络业务网元执行。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
可选地，第一数据可以包括但不限于如下一项或多项：终端设备侧的数据、接入网设备侧各功能节点的数据、传输网侧的各功能节点的数据、核心网侧的各功能节点的数据以及操作、管理和维护(operation administration and maintenance，OAM的各功能节点的数据、和合成的数据。
可选地，合成的数据可以指人工合成的数据。
第二方面，提供一种通信方法。该通信方法包括：第一数据代理网元接收操作配置信息，第一数据代理网元根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息。在操作配置信息指示第一数据代理网元与第二数据代理网元通信的情况下，第一数据代理网元向第二数据代理网元发送第一信息。或者，在操作配置信息指示第一数据代理网元与服务请求网元通信的情况下，第一数据代理网元向服务请求网元发送第一信息。操作配置信息指示第一数据代理网元对第一数据执行的操作。
在一种可能的设计方式中，操作配置信息所指示的操作可以包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与服务请求网元交互。
在一种可能的设计方式中，上述第一数据代理网元根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息，可以包括：第一数据代理网元根据操作配置信息，向第三数据代理网元发送数据请求消息，第一数据代理网元接收来自第三数据代理网元的数据响应消息。其中，数据请求消息可用于请求如下一项或多项数据：网络数据、用户数据、物联网数据、和人工智能模型数据。数据响应消息包括数据请求消息中包括的一项或多项数据。
在一种可能的设计方式中，数据请求消息还可以包括安全信息，安全信息可用于验证第一数据代理网元是否具有访问第一数据的权限。
在一种可能的设计方式中，上述第一数据代理网元根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息，可以包括：第一数据代理网元根据操作配置信息所指示的操作对第二信息进行处理，获得第一信息。其中，第二信息是第一数据代理网元接收的，第二信息是基于第一数据获得的。
在一种可能的设计方式中，第二方面提供的通信方法，还可以包括：第一数据代理网元接收来自可信锚点的第二验证响应消息。其中，第二验证响应消息可指示第二数据代理网元具有访问第一数据代理网元的第一数据的权限。
在一种可能的设计方式中，第二方面提供的通信方法，还可以包括：第一数据代理网元向可信锚点发送第二验证请求消息。其中，第二验证请求消息可用于请求验证第二数据代理网元是否具有访问第一数据代理网元的第一数据的权限。
在一种可能的设计方式中，第二方面提供的通信方法，还可以包括：第一数据代理网元向数据编排网元发送数据服务能力信息。
在一种可能的设计方式中，数据服务能力信息可以包括如下一项或多项：第一数据代理网元的标识、第一数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力。
在一种可能的设计方式中，第二方面提供的通信方法，还可以包括：第一数据代理网元接收来自数据编排网元的更新的数据安全及隐私保护技术库的信息和/或更新 的分析工具库的信息。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
此外，第二方面所述的通信方法的技术效果可以参考第一方面中任一种可能的实现方式所述的通信方法的技术效果，此处不再赘述。
第三方面，提供一种通信方法。该通信方法包括：服务请求网元向数据编排网元发送第一服务请求消息，服务请求网元接收来自数据代理网元的第一信息。其中，第一信息是基于第一数据获得的。
在一种可能的设计方式中，第一服务请求消息可用于请求应用服务或业务服务。
在一种可能的设计方式中，第三方面提供的通信方法，还可以包括：服务请求网元接收第一通信信息。其中，第一通信信息可用于指示与服务请求网元直接通信的数据代理网元的信息。
在一种可能的设计方式中，第三方面提供的通信方法，还可以包括：服务请求网元对第一信息进行处理，获得应用服务或业务服务。
在一种可能的设计方式中，上述服务请求网元对第一信息进行处理，获得应用服务或业务服务，可以包括：服务请求网元采用第一信息获取物联网终端设备的异常行为信息。
在一种可能的设计方式中，上述服务请求网元对第一信息进行处理，获得应用服务或业务服务，可以包括：服务请求网元采用第一信息和人工智能模型参数配置信息，进行服务质量预测。其中，人工智能模型参数配置信息用于对服务质量进行预测。
在一种可能的设计方式中，第三方面提供的通信方法，还可以包括：服务请求网元向数据代理网元请求人工智能模型参数配置信息。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
此外，第三方面所述的通信方法的技术效果可以参考第一方面中任一种可能的实现方式所述的通信方法的技术效果，此处不再赘述。
第四方面，提供一种通信装置。该通信装置包括：收发模块和处理模块。其中，收发模块，用于接收第一服务请求消息。处理模块，用于根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息。收发模块，还用于发送操作配置信息。其中，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求，一个或多个数据服务能力信息与一个或多个数据代理网元一一对应，至少一个数据代理网元是一个或多个数据代理网元中的至少一个，需求信息对应一个或多个数据服务能力信息中的至少一个，至少一个数据代理网元中任一个数据代理网元的操作配置信息指示任一个数据代理网元对第一数据执行的操作。
在一种可能的设计方式中，第一服务请求消息可用于请求应用服务或业务服务。
在一种可能的设计方式中，第一服务请求消息来自服务请求网元，收发模块，还用于接收来自可信锚点的第一验证响应消息。其中，第一验证响应消息可指示服务请求网元具有访问第一数据的权限。
在一种可能的设计方式中，收发模块，还用于向可信锚点发送第一验证请求消息。其中，第一验证请求消息可用于请求验证服务请求网元是否具有访问第一数据的权限。
在一种可能的设计方式中，第一服务请求消息来自服务请求网元，收发模块，还用于发送第一通信信息。其中，第一通信信息可用于指示至少一个数据代理网元中与服务请求网元直接通信的数据代理网元的信息。
在一种可能的设计方式中，收发模块，还用于接收一个或多个数据代理网元对应的数据服务能力信息。
在一种可能的设计方式中，一个或多个数据代理网元中任一个数据代理网元的数据服务能力信息可以包括如下一项或多项：任一个数据代理网元的标识、任一个数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力。
在一种可能的设计方式中，操作配置信息所指示的操作可以包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与服务请求网元交互。
在一种可能的设计方式中，需求信息可以包括如下一项或多项服务需求：地理位置、数据采集、数据预处理、数据存储、数据上报、数据分析、与服务请求网元交互、数据保护、和数据压缩。
在一种可能的设计方式中，需求信息可与数据服务任务标识对应。
在一种可能的设计方式中，收发模块，还用于向至少一个数据代理网元中的一个或多个发送更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
在一种可能的设计方式中，第四方面所述的通信装置可部署在网络业务网元中。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
需要说明的是，第四方面所述的收发模块可以包括接收模块和发送模块。本申请对于收发模块的具体实现方式，不做具体限定。
可选地，第四方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得第四方面所述的通信装置可以执行第一方面所述的方法。
需要说明的是，第四方面所述的通信装置可以是数据编排网元，也可以是可设置于数据编排网元中的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，第四方面所述的通信装置的技术效果可以参考第一方面中任一种可能的实现方式所述的通信方法的技术效果，此处不再赘述。
第五方面，提供一种通信装置。该通信装置包括：收发模块和处理模块。其中，收发模块，用于接收操作配置信息。处理模块，用于根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息。收发模块，还用于在操作配置信息指示通信装置与第二数据代理网元通信的情况下，向第二数据代理网元发送第一信息。或者，收发模块，还用于在操作配置信息指示通信装置与服务请求网元通信的情况下，向服务请求网元发送第一信息。其中，操作配置信息指示通信装置对第一数据执行的操作。
在一种可能的设计方式中，操作配置信息所指示的操作可以包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与服务请求网元交互。
在一种可能的设计方式中，收发模块，还用于根据操作配置信息，向第三数据代理网元发送数据请求消息。收发模块，还用于接收来自第三数据代理网元的数据响应消息。其中，数据请求消息可用于请求如下一项或多项数据：网络数据、用户数据、物联网数据、和人工智能模型数据。数据响应消息包括数据请求消息中包括的一项或多项数据。
在一种可能的设计方式中，数据请求消息还可以包括安全信息，安全信息可用于验证通信装置是否具有访问第一数据的权限。
在一种可能的设计方式中，处理模块，还用于根据操作配置信息所指示的操作对第二信息进行处理，获得第一信息。其中，第二信息是通信装置接收的，第二信息是基于第一数据获得的。
在一种可能的设计方式中，收发模块，还用于接收来自可信锚点的第二验证响应消息。其中，第一验证响应消息可指示第二数据代理网元具有访问第一数据代理网元的第一数据的权限。
在一种可能的设计方式中，收发模块，还用于向可信锚点发送第二验证请求消息。其中，第二验证请求消息可用于请求验证第二数据代理网元是否具有访问通信装置的第一数据的权限。
在一种可能的设计方式中，收发模块，还用于向数据编排网元发送数据服务能力信息。
在一种可能的设计方式中，数据服务能力信息可以包括如下一项或多项：通信装置的标识、通信装置的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力。
在一种可能的设计方式中，收发模块，还用于接收来自数据编排网元的更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
需要说明的是，第五方面所述的收发模块可以包括接收模块和发送模块。本申请对于收发模块的具体实现方式，不做具体限定。
可选地，第五方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得第五方面所述的通信装置可以执行第二方面所述的方法。
需要说明的是，第五方面所述的通信装置可以是第一数据代理网元，也可以是可设置于第一数据代理网元中的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，第五方面所述的通信装置的技术效果可以参考第二方面中任一种可能的实现方式所述的通信方法的技术效果，此处不再赘述。
第六方面，提供一种通信装置。该通信装置包括：发送模块和接收模块。发送模块，用于向数据编排网元发送第一服务请求消息。接收模块，用于接收来自数据代理网元的第一信息。其中，第一信息是基于第一数据获得的。
在一种可能的设计方式中，第一服务请求消息可用于请求应用服务或业务服务。
在一种可能的设计方式中，接收模块，还用于接收第一通信信息。其中，第一通信信息可用于指示与服务请求网元直接通信的数据代理网元的信息。
在一种可能的设计方式中，处理模块，用于对第一信息进行处理，获得应用服务或业务服务。
在一种可能的设计方式中，处理模块，还用于采用第一信息获取物联网终端设备的异常行为信息。
在一种可能的设计方式中，处理模块，还用于采用第一信息和人工智能模型参数配置信息，进行服务质量预测。其中，人工智能模型参数配置信息用于对服务质量进行预测。
在一种可能的设计方式中，接收模块，还用于向数据代理网元请求人工智能模型参数配置信息。
在一种可能的设计方式中，第一数据可以包括从移动通信网络采集的数据或合成的数据。
需要说明的是，接收模块和发送模块可以分开设置，也可以集成在一个模块中，即收发模块。本申请对于接收模块和发送模块的具体实现方式，不做具体限定。
可选地，第六方面所述的通信装置还可以包括存储模块，该存储模块存储有程序或指令。当处理模块执行该程序或指令时，使得第六方面所述的通信装置可以执行第三方面所述的方法。
需要说明的是，第六方面所述的通信装置可以是服务请求网元，也可以是可设置于服务请求网元的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，第六方面所述的通信装置的技术效果可以参考第三方面中任一种可能的实现方式所述的通信方法的技术效果，此处不再赘述。
第七方面，提供一种通信装置。该通信装置包括：处理器，该处理器与存储器耦合，存储器用于存储计算机程序。
处理器用于执行存储器中存储的计算机程序，以使得如第一方面至第三方面中任一种可能的实现方式所述的方法被执行。
在一种可能的设计中，第七方面所述的通信装置还可以包括收发器。该收发器可以为收发电路或输入/输出端口。所述收发器可以用于该通信装置与其他设备通信。
需要说明的是，输入端口可用于实现第一方面至第三方面所涉及的接收功能，输出端口可用于实现第一方面至第三方面所涉及的发送功能。
在本申请中，第七方面所述的通信装置可以为数据编排网元、第一数据代理网元或服务请求网元，或者设置于数据编排网元、第一数据代理网元或服务请求网元内部的芯片或芯片系统。
此外，第七方面所述的通信装置的技术效果可以参考第一方面中任一种实现方式所述的方法的技术效果，此处不再赘述。
第八方面，提供一种通信系统。该通信系统包括数据编排网元和第一数据代理网元，还可以包括服务请求网元。其中，数据编排网元，用于实现如第一方面所述方法。第一数据代理网元，用于实现如第二方面所述方法。服务请求网元，用于实现如第三 方面所述方法。
或者，该通信系统包括如第四方面所述的用于实现如第一方面所述方法的通信装置、如第五方面所述的用于实现如第二方面所述方法的通信装置，还可以包括如第六方面所述的用于实现如第三方面所述方法的通信装置。
第九方面，提供了一种芯片系统，该芯片系统包括逻辑电路和输入/输出端口。其中，逻辑电路用于实现第一方面至第三方面所涉及的处理功能，输入/输出端口用于实现第一方面至第三方面所涉及的收发功能。具体地，输入端口可用于实现第一方面至第三方面所涉及的接收功能，输出端口可用于实现第一方面至第三方面所涉及的发送功能。
在一种可能的设计中，该芯片系统还包括存储器，该存储器用于存储实现第一方面至第三方面所涉及功能的程序指令和数据。
该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第十方面，提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序或指令；当该计算机程序或指令在计算机上运行时，使得第一方面至第三方面中任意一种可能的实现方式所述的方法被执行。
第十一方面，提供一种计算机程序产品，包括计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得第一方面至第三方面中任意一种可能的实现方式所述的方法被执行。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图；
图2为本申请实施例提供的一种数据服务架构的示意图；
图3为本申请实施例提供的一种数据服务架构的功能的示意图；
图4为本申请实施例提供的一种逻辑网络拓扑的示意图；
图5为本申请实施例提供的一种操作链的示意图；
图6a-图6d为本申请实施例提供的一些网络架构的示意图；
图7为本申请实施例提供的一种通信装置的结构示意图；
图8为本申请实施例提供的一种通信方法的流程示意图；
图9为本申请实施例提供的另一种通信方法的流程示意图；
图10为本申请实施例提供的另一种通信装置的结构示意图；
图11为本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如通用移动通信系统(universal mobile telecommunications system，UMTS)、无线局域网(wireless local area network，WLAN)、无线保真(wireless fidelity，Wi-Fi)系统、有线网络、车到任意物体(vehicle to everything，V2X)通信系统、设备间(device-to-device，D2D)通信系统、车联网通信系统、第4代(4th generation，4G)移动通信系统，如长期演进(long term evolution，LTE)系统、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统，第五代(5th generation，5G)移动通信系统，如新空口(new  radio，NR)系统，以及未来的通信系统，如第六代(6th generation，6G)移动通信系统等。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例地”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为便于理解本申请实施例，首先以图1中示出的通信系统为例详细说明适用于本申请实施例的通信系统。示例性地，图1为本申请实施例提供的通信方法所适用的一种通信系统的架构示意图。
如图1所示，该通信系统包括数据编排(data orchestration，DO)网元和数据代理(data agent，DA)网元。其中，数据编排网元的数量可以为一个或多个，数据代理网元的数量可以为一个或多个。
其中，上述数据编排网元可以获取服务请求，将服务请求转译为对数据的服务需求，确定用于实现该服务需求的数据代理网元，编排各个数据代理网元的功能，使数据代理网元执行相应操作并建立动态的逻辑网络拓扑，实现相应的服务需求。
示例性地，数据编排网元可以部署在任意核心网网元、传输网(transfer network，TN)网元、接入网设备或其他网元(例如操作、管理和维护(operation administration and maintenance，OAM)网元等)中，或者数据编排网元可以独立部署。例如，数据编排网元可以分级部署在核心网或接入网设备侧。数据编排网元可以部署在网络业务(network service，NS)网元中。又例如，数据编排网元可以作为网络功能(network function，NF)或网元独立部署在网络中。在实际部署时，一个或多个NF可以组成一个网元。
其中，上述数据代理网元可以实现如下一项或多项功能：数据采集、预处理、存储、分析、和数据保护等。不同的数据代理网元可以具有相同或不同的数据服务能力，可以实现相同或不同的功能。数据代理网元可以与数据编排网元交互，获得为实现服务需求需要执行的相关操作，并执行该操作。数据代理网元可建立逻辑网络拓扑，形成动态的数据管道(data pipeline)(或称为数据流、业务逻辑、功能链、操作链等)，该数据管道由一个或多个数据代理网元对应的功能按服务需求组成，前一个功能的输出是下一个功能的输入，从而实现响应的数据服务。
上述数据代理网元可以部署在任意核心网网元、传输网(transfer network，TN)网元、终端设备、接入网设备或其他网元(例如操作、管理和维护(operation administration and maintenance，OAM)网元等)中，或者数据代理网元可以独立部署。例如，数据代理网元可以作为网络功能NF或网元独立部署在网络中。
例如，数据代理网元可以是由任意核心网网元、传输网网元、终端设备、接入网设备或其他网元等演进而来的，数据代理网元可以实现任意核心网网元、传输网网元、终端设备、接入网设备或其他网元等的能够实现的功能，或者，本申请中提供的数据代理网元的功能可以由任意核心网网元、传输网网元、终端设备、接入网设备或其他网元等实现。
例如，数据代理网元可以是由网络数据分析功能(network data analysis function，NWDAF)网元演进而来的，能够实现NWDAF网元具有的功能、以及基于NWDAF网元实现的场景用例等。
可选地，可以根据网元的资源、和/或能力等，将数据代理网元可选地部署在任意核心网网元、传输网网元、终端设备、接入网设备或其他网元中，可以实现跨域数据收集。可以对全域进行数据采集，实现跨域数据管理及协同。
示例性地，数据代理网元作为网络功能NF，能够匹配云原生的SBI加密，NF动态实例化和K8S部署的加密环境。另外，又能最小化地影响NF的性能损失和安全性。
当通信系统中数据代理网元的数量为多个时，可以部分数据代理网元内置于网络设备(指任意核心网网元、终端设备、接入网设备、或其他网元等)中，部分数据代理网元独立部署；或者，多个数据代理网元均内置于网络设备中，或者，多个数据代理网元均独立部署，本申请对此不限定。
需要说明的是，数据编排网元可以是逻辑实体或者物理实体，数据代理网元可以是逻辑实体或者物理实体，本申请对此不限定。
示例性地，数据代理网元可以集中式部署，也可以分布式部署。分布式部署方式可以包括分布式哈希表(distributed hash table，DHT)方式等。
数据代理网元分布式按需灵活部署，可以满足多样性及灵活的数据服务需求，可以减少收集数据的开销。
其中，上述核心网网元位于通信系统的网络侧，可用于为接入网设备、终端设备等提供网络服务。核心网网元可以包括但不限于如下一项或多项：移动性管理网元、会话管理网元、用户面网元、策略控制网元、网络开放网元、应用网元、NWDAF网元、和/或OAM网元。
移动性管理网元：主要用于移动性管理和接入管理等。在5G移动通信系统中，该接入管理网元可以是接入和移动性管理功能(access and mobility management function，AMF)网元，主要进行移动性管理、接入鉴权/授权等功能。此外，移动性管理网元还可以负责在终端与策略控制功能(policy control function，PCF)网元间传递用户策略。
会话管理网元：主要用于会话管理(例如创建、删除等)、维护会话上下文及用户面转发管道信息、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(session management  function，SMF)网元，完成终端IP地址分配，UPF选择，及计费与QoS策略控制等。
用户面网元：作为和数据网络的接口，完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。即分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。
策略控制网元：包括用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等，用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。在5G移动通信系统中，该策略控制网元可以是PCF。
网络开放网元：可用于提供网络能力开放相关的框架、鉴权和接口，在5G系统网络功能和其他网络功能之间传递信息。在5G通信系统中，该网络开放网元可以是网络开放功能(network element function,NEF)网元，主要用于向AF开放3GPP网络功能的业务和能力，同时也可以让AF向3GPP网络功能提供信息。
应用网元：可用于提供各种业务服务，能够通过网络开放功能(network element function,NEF)网元与核心网交互，以及能够和策略管理框架交互进行策略管理。在5G通信系统中，该应用网元可以是应用功能(application function,AF)网元、或时间敏感应用功能(time sensitive network application function，TSNAF)网元，表示第三方或运营商的应用功能，是5G网络获取外部应用数据的接口，主要用于传递应用侧对网络侧的需求。
NWDAF网元：可用于从核心网和OAM网元收集数据，向NF或者AF或者OAM反馈数据分析结果。例如，NWDAF网元可从OAM网元采集OAM数据，从核心网NF或AF收集非OAM数据，非OAM数据可以包括收集终端、终端群组、业务等级别的非OAM数据。
OAM网元：可从收集来自接入网设备的数据。
其中，上述接入网设备也可以称为接入设备或无线接入网设备，接入网设备能够管理无线资源，为终端设备提供接入服务，完成数据在终端设备和核心网之间的转发，接入网设备也可以理解为网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与终端设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如NR系统中的gNB，或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或分布式单元(distributed unit，DU)等，还可以为卫星、或无人机等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还 可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。RRC层的信息由CU生成，最终会经过DU的PHY层封装变成PHY层信息，或者，由PHY层的信息转变而来。因而，在这种架构下，高层信令如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
其中，上述终端设备为接入通信系统，且具有无线收发功能的终端或可设置于该终端的芯片或芯片系统。本申请中的终端设备也可以称为终端、用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端可以是手机(mobile phone)、平板电脑(pad)、无人机、带无线收发功能的电脑、客户前置设备(customer premise equipment，CPE)、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端或者未来演进网络中的终端等。
又例如，本申请中的终端设备可以是智慧物流中的快递终端(例如可监控货物车辆位置的设备、可监控货物温湿度的设备等)、智慧农业中的无线终端(例如可收集禽畜的相关数据的可穿戴设备等)、智慧建筑中的无线终端(例如智慧电梯、消防监测设备、以及智能电表等)、智能医疗中的无线终端(例如可监测人或动物的生理状态的可穿戴设备)、智能交通中的无线终端(例如智能公交车、智能车辆、共享单车、充电桩监测设备、智能红绿灯、以及智能监控以及智能停车设备等)、智能零售中的无线终端(例如自动售货机、自助结账机、以及无人便利店等)。又例如，本申请中的终端设备可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元，车辆通过内置的所述车载模块、车载模组、车载部件、车载芯片或者车载单元可以实施本申请提供的方法。本申请中的终端设备可以是智能物联网(smart internet of things，SIoT)终端设备或非SIoT终端设备，具有一定的计算、存储等能力。非SIoT终端设备可以通过物联网网关收集数据，例如，非SIoT终端设备可以为计算能力受限的终端，例如功能单一的传感器等。可选地，SIoT 终端设备可以内置数据代理网元，或者SIoT终端设备可以实现数据代理网元的功能。
应理解，图1仅为便于理解而示例的简化示意图，该通信系统中还可以包括其他设备，例如可信锚点(trust anchor，TA)、服务请求网元和/或数据存储网元(具体实现可参照下述图2中对应的阐述)，图1中未予以画出。
示例性的，图2是本申请实施例提供的一种数据服务架构的示意图。图1所示的通信系统可以适用于图2所示数据服务架构中。
如图2所示，本申请提出基于数据面构建归一化的数据服务架构为服务请求网元提供数据服务。该数据服务架构中可以包括但不限于如下一项或多项：数据编排网元、数据代理网元、可信锚点(trust anchor，TA)、服务请求网元和数据存储网元。
上述可信锚点可提供鉴权、认证和接入控制(authentication authorization access control，AAA)等可信服务，例如，可以通过分布式账本技术(distributed ledge technology，DLT)来实现。可信锚点可以存储不可被纂改的数据，例如终端设备或者网元的公钥、标识、索引，交易相关数据、或不能被篡改的重要数据等。
可选地，可以通过链上(on-chain)结合链下(off-chain)存储的方式来扩展分布式账本技术的存储能力，例如在数据代理网元本地或数据存储网元中存储原始数据(链下)，将原始数据的哈希值，或打包后的原始数据的摘要的哈希值存储在扩展DLT(链上)上，并同时在DLT(链上)保存用于指向原始数据的地址。通过对链下存储的原始数据或其摘要生成的新哈希值，与链上保存的哈希值进行对比，从而防止链下原始数据被篡改。
示例性地，可信锚点可以是分布式或集中式的部署形式。分布式部署的可信锚点可以是分布式账本技术DLT(比如区块链)的节点等，集中式部署的可信锚点可以是现有的认证、授权、接入控制等安全可信机制经过改造演进而实现的。
示例性地，可信锚点通过认证、授权、接入控制等数据访问控制，结合数据安全及隐私保护技术库，可以实现数据服务全流程的安全和隐私保护机制，可支持对数据服务全流程的安全和隐私保护，可支持溯源、审计、用户数据自主控制等可信数据服务要求，能够支撑实现数据共享及交易等对溯源及审计等可信机制的要求，可满足个人信息保护法(personal information protection law，PIPL)、通用数据保护条例(general data protection regulation，GDPR)等合规要求，可提供可信的数据服务。对用户数据处理的合规检测，可以实现去中心化的验证机制，避免单点可信及失效问题。
上述服务请求网元可以包括应用、应用服务器或网络业务NS网元等，应用可以是运营商(或通信服务提供商(communication service provider，CSP))的用于网规网优、和/或网络人工智能(artificial intelligence，AI)等的应用，也可以是移动通信网络外部的应用(也可以称为第三方应用)。服务请求网元可以作为网络功能或网元独立部署在网络中。
上述数据存储网元可支持存储各种数据，例如流(streaming)数据、批(batch)数据、日志(log)信息、AI模型参数配置信息、中间数据等，可以扩展数据代理网元的存储功能。示例性地，DSF网元可以是集中式数据库，也可以是分布式数据库，如分布式哈希表DHT或星际文件系统(inter planetary file system，IPFS)等。示例性地，该数据存储网元可以是数据存储功能(data storage function，DSF)网元，或者可以是 由数据存储功能网元演进的。数据存储网元可以作为NF或网元部署在网络中。
示例性的，图3为本申请实施例提供的一种数据服务架构的功能的示意图。
下面结合图3对数据编排网元的功能进行阐述。
结合图3，数据编排网元可以实现的功能包括但不限于如下一项或多项：与应用的接口、需求转译、编排数据代理、管理数据代理、数据保护、与网络业务(network service，NS)的接口、和与可信锚点的接口。
与应用的接口：数据编排网元可通过与应用的接口与服务请求网元交互，例如数据编排网元接收来自服务请求网元的服务请求。示例性地，服务请求可以是基于标准模板填写的需求，例如标准模板可以是服务等级协议(service level agreement，SLA)。
需求转译：数据编排网元将服务请求转译为对各个数据代理网元的功能的服务需求。示例性地，数据编排网元将服务等级协议等需求转译为对相应资源和网络配置的需求。
编排数据代理：基于数据代理网元的数据服务能力，编排各个数据代理网元形成动态的逻辑网络拓扑，实现服务需求。
示例性地，数据编排网元将服务等级协议等需求转译为对相应资源和网络配置的需求，并基于数据代理网元的数据服务能力，选择参与本次数据服务的数据代理网元,并编排各个数据代理网元形成动态的逻辑网络拓扑。
可选地，数据编排网元在执行编排数据代理过程中可与其他网络业务网元进行协商。例如，如果需要用到算法、算力，数据编排网元可以与其他网络业务网元进行协作，选择相应的AI算法、算力，并由网络业务网元进行算法推送。
可选地，数据编排网元可动态指定与服务请求网元直接交互的数据代理网元，将该数据代理网元的信息发给服务请求网元，使应用可以调用该数据代理网元的应用可编程接口(application programming interface，API)，获得数据或处理结果等。
管理数据代理：管理数据代理网元向数据编排网元请求的注册、去注册等，接收管理数据代理网元上报的数据服务能力等。
数据保护：可通过数据保护技术库(data protection technology repository，DPTR)实现数据保护功能，数据保护技术库可以包括数据安全和隐私保护算法库，例如差分隐私、同态加密、多方计算、零知识证明等多种算法。数据编排网元可将数据保护技术库的信息按需推送或更新给管理数据代理网元，作为管理数据代理网元的数据保护技术(data protection technology，DPT)。数据保护技术库可与数据编排网元松耦合。数据保护技术库可以是数据服务架构中网元的公共能力，可以独立演进和优化。独立的数据保护技术库便于实现端到端(end to end，E2E)的数据处理合规检测。
例如，数据保护技术库的信息可以包括数据保护技术库的标识、索引、配置信息、数据保护技术库本身等。
与网络业务的接口：数据编排网元可通过与网络业务的接口与网络业务网元交互。例如，数据编排网元可根据服务需求与网络业务网元协商，例如，如果需要用到算法、算力，数据编排网元可以与其他网络业务网元进行协作。
可信锚点代理：数据编排网元与可信锚点的接口，数据编排网元可通过与可信锚点代理功能与可信锚点交互。
需要说明的是，本申请实施例可以根据上述功能或下述方法实施例对数据编排网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对功能或模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
下面结合图3对数据代理网元的功能进行阐述。
结合图3，数据代理网元可以实现的功能包括但不限于如下一项或多项：控制、数据采集、预处理、存储、应用可编程接口、数据分析、和数据保护。
数据代理网元通过执行上述功能，可以实现数据服务协同及闭环管理，可以按需输出不同处理要求的数据。
控制：根据数据编排网元对数据代理网元设定的操作，编排数据代理网元中各个功能形成数据管道。控制功能可以由数据编排网元的控制器来实现。
示例性地，通过数据编排网元编排各个数据代理网元形成动态的逻辑网络拓扑，数据代理网元编排数据代理网元中各个功能形成数据管道，可实现自动化数据管理，可实现动态按需配置，对新业务、新需求敏捷响应，支撑实现丰富的应用场景，实现新数据服务业务快速的快速上市，缩短上市时间(time to market，TTM)。
数据采集(acquisition)：获取数据，例如，通过订阅/通知的方式，也可以通过请求/响应的方式获取数据。可选地，请求中可以指示数据上报的触发方式、触发条件、上报的周期、数据量等。可选地，数据代理网元可支持流数据、批数据采集。可选地，数据代理网元可支持实时数据和非实时数据采集。可选地，数据代理网元可支持各种数据的采集。可将数据划分为几类，例如，数据类型可以包括但不限于：网络数据、用户数据、AI模型数据、和物联网(internet of things，IoT)数据，本申请不对数据的划分进行限定，可以划分为更多或更少的类型，或者可以从其他角度划分数据的类型，也可以不划分数据的类型。
如此，通过本申请提供的归一化的数据服务架构可以实现对各类数据的数据服务。
预处理(pre-processing)：指对采集到的原始数据进行诸如清洗、填补、平滑、合并、规格化、一致性检验、对原始数据的字段提取、格式转化、冗余数据清除、压缩、过滤、和/或融合等操作，旨在提高数据质量，为后期处理(例如分析)奠定基础。消除原始数据可能存在如数据缺失、数据噪声、数据冗余、和/或数据集不均衡等问题。
存储(storage)：支持集中式和分布式存储。可选地，需要进行严格访问保护或隐私保护的数据，如用户签约数据等，存储在数据代理网元本地。
应用可编程接口：数据代理网元的每一功能都可以直接通过应用可编程接口API对服务请求者提供服务。
数据分析(analytics)：与数据代理网元松耦合，可以根据需要与数据代理网元分开部署。可支持各类数据分析技术，例如AI训练、AI推理、机器学习(machine learning，ML)、大数据分析等。数据分析功能可以通过API调用数据代理网元的数据采集、预处理、存储等各层级的数据服务。可选地，数据分析过程所需的AI模型可以预设置在数据代理网元本地、或由网络业务网元推送。
数据保护：采用诸如k-匿名化(k-anonymity)、l-多样化(l-diversity)、差分隐 私等技术对数据进行处理，使得攻击者无法从经过脱敏处理的数据中直接获取敏感信息，从而实现对数据隐私的防护。数据保护技术库的信息可以预装在数据代理网元中，或由DO按需推送，对数据代理网元的每一层级的数据进行安全和隐私保护。
需要说明的是，本申请实施例可以根据上述功能或下述方法实施例对数据代理网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对功能或模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图4为本申请实施例提供的一种逻辑网络拓扑的示意图。下面结合图4对数据编排网元编排数据代理网元DA形成的逻辑网络拓扑进行阐述。
如图4所示，逻辑网络拓扑可以包括但不限于：星式逻辑网络拓扑、网(mesh)式逻辑网络拓扑、和混合式逻辑网络拓扑。
示例性地，星式逻辑网络拓扑中，作为汇聚节点的DA可以收集普通节点DA的信息，还可以对收集的信息进行进一步处理。可选地，作为汇聚节点的DA可与服务请求网元直接交互，普通节点DA可通过作为汇聚节点的DA与服务请求网元交互，本申请对此不限定，与服务请求网元直接交互的DA可以是任意DA。星式逻辑网络拓扑可适用于数据汇聚、联邦学习等场景。
示例性地，网式逻辑网络拓扑中，DA间进行数据协作，可以选择任意DA与服务请求网元直接交互。示例性地，混合式(或称为混合分级式)逻辑网络拓扑中，作为汇聚节点的DA可以分级收集普通节点DA的信息，可以对收集的信息进行进一步处理。与星式逻辑网络拓扑中类似，作为汇聚节点的DA可与服务请求网元直接交互，普通节点DA可通过作为汇聚节点的DA与服务请求网元交互，本申请对此不限定，与服务请求网元直接交互的DA可以是任意DA。
需要说明的是，图4所示的逻辑网络拓扑仅为本申请提供的示例，在实际应用中，数据编排网元可以根据需求将编排数据代理网元DA形成的任意形式的逻辑网络拓扑，能够实现数据服务即可。
图5为本申请实施例提供的一种操作链的示意图。下面结合图5对数据代理网元控制数据代理网元中各个功能形成的操作链进行阐述。
操作链是数据代理网元从数据编排网元获取到对该数据代理网元设定的操作，根据数据编排网元对数据代理网元设定的操作编排数据代理网元中各个功能形成的。示例性地，如图5所示，假设数据代理网元1从数据编排网元获取到对该数据代理网元1设定的操作包括：将从其他数据代理网元获取的数据进行融合等预处理后，再进行分析，获得分析结果，并将分析结果发给服务请求网元。数据代理网元1编排各个功能形成如图5所示的操作链1：采集数据，然后进行预处理，对预处理的结果进行分析，将分析结果通过应用可编程接口发给服务请求网元。
又示例性地，如图5所示，假设数据代理网元1从数据编排网元获取到对该数据代理网元1设定的操作包括：将采集的数据传给数据代理网元2，则数据代理网元1编排各个功能形成如图5所示的操作链2：采集数据，发给数据代理网元2。
需要说明的是，图5中示出的操作链1和操作链2仅为本申请提供的示例，不构 成对数据代理网元中的各个功能执行的先后顺序的限定，数据代理网元执行各个功能的顺序可根据服务需求动态调整。
示例性的，图6a-图6d是本申请实施例提供的一些网络架构的示意图。图1所示的通信系统可以适用于图6a-图6d所示网络架构中。
图6a示出了核心网和接入网设备全服务化条件下的网络架构示意图，图6b示出了接入网设备未服务化、核心网服务化条件下的网络架构示意图，图6c示出了接入网设备未服务化、核心网服务化(保留N4接口)条件下的网络架构示意图，图6d示出了各网元直接互联的网络架构示意图。
结合图6a至图6c，该网络架构中可以包括但不限于如下一项或多项：服务请求网元、终端设备、接入网设备、用户面网元、数据网络、核心网网元、数据编排网元、数据代理网元、数据存储网元、可信锚点、和服务请求网元，具体实现方式可参照上述图1-图5的阐述，此处不再赘述。该网络架构中还可以包括但不限于如下一项或多项：移动性管理网元(图6b和图6c)。该网络架构中还可以包括但不限于如下一项或多项：会话管理网元(图6c)。图6a至图6c所示的核心网网元可以包括除用户面网元、移动性管理网元、和/或会话管理网元以外的任意核心网网元。
数据代理网元可部署在网络架构中除数据编排网元、数据存储网元、和可信锚点以外的任意网元中，也就是说，网络架构中除数据编排网元、数据存储网元、和可信锚点以外的任意网元均可实现数据代理网元的功能。
数据编排网元通过服务化接口NDO与其他网元(例如服务请求网元、数据代理网元、核心网网元、和可信锚点等)交互，数据代理网元通过服务化接口NDA与其他网元(例如服务请求网元、数据编排网元、核心网网元、终端设备、接入网设备、数据存储网元、和可信锚点等)交互，数据存储网元通过服务化接口NDSF与其他网元(例如数据代理网元、核心网网元、终端设备、和接入网设备等)交互，可信锚点通过服务化接口NTA与其他网元(例如数据编排网元、数据代理网元、核心网网元、终端设备、接入网设备、数据存储网元、和可信锚点等)交互。
图6a至图6c所示的网络架构中，可通过服务化接口来提高网络功能间的独立性，实现部署的灵活性和高效的可扩展性，可以提高新功能的开发效率。
结合图6d，该网络架构中可以包括但不限于如下一项或多项：服务请求网元、数据编排网元、接入网域数据编排网元(RAN-DO)、CN域数据编排网元(CN-DO)、接入网设备RAN、核心网网元、终端设备、可信锚点、和数据存储网元。
在图6d所示的架构中，数据编排网元分级部署，数据编排网元可以管理RAN域数据编排网元和CN域数据编排网元，RAN域数据编排网元和CN域数据编排网元之间可以直接交互，RAN域数据编排网元可与接入网设备直接交互，CN域数据编排网元可以核心网网元直接交互，可信锚点可以与网络架构中的任意网元直接交互，数据存储网元可与终端设备、接入网设备、和核心网网元直接交互。
图6d所示的网络架构中各网元直接互联，可以满足架构的后向兼容。
需要说明的是，本申请实施例提供的通信方法，可以适用于图1-图6d所示的任意两个节点之间，具体实现可以参考下述方法实施例，此处不再赘述。
应当指出的是，本申请实施例中的方案还可以应用于其他通信系统中，相应的名 称也可以用其他通信系统中的对应功能的名称进行替代。
图7为可用于执行本申请实施例提供的通信方法的一种通信装置700的结构示意图。通信装置700可以是数据编排网元、数据代理网元、服务请求网元、或可信锚点，也可以是应用于数据编排网元、数据代理网元、服务请求网元、或可信锚点中的芯片或者其他部件或组件。
如图7所示，通信装置700可以包括处理器701。可选地，通信装置700还可以包括存储器702和收发器703中的一个或多个。其中，处理器701可以与存储器702和收发器703中的一个或多个耦合，如可以通过通信总线连接，处理器701也可以单独使用。
下面结合图7对通信装置700的各个构成部件进行具体的介绍：
处理器701是通信装置700的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器701是一个或多个中央处理器(central processing unit，CPU)，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
其中，处理器701可以通过运行或执行存储在存储器702内的软件程序，以及调用存储在存储器702内的数据，执行通信装置700的各种功能。
在具体的实现中，作为一种实施例，处理器701可以包括一个或多个CPU，例如图7中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置700也可以包括多个处理器，例如图7中所示的处理器701和处理器704。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个通信设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器702可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储通信设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储通信设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储通信设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器702可以和处理器701集成在一起，也可以独立存在，并通过通信装置700的输入/输出端口(图7中未示出)与处理器701耦合，本申请实施例对此不作具体限定。
其中，所述存储器702用于存储执行本申请方案的软件程序，并由处理器701来控制执行。上述具体实现方式可以参考下述方法实施例，此处不再赘述。
收发器703，用于与其他通信装置之间的通信。例如，通信装置700为数据编排网元，收发器703可以用于与数据代理网元、服务请求网元、和/或可信锚点等通信。又例如，通信装置700为数据代理网元，收发器703可以用于与数据编排网元、服务 请求网元、和/或可信锚点等通信。又例如，通信装置700为服务请求网元，收发器703可以用于与数据编排网元、数据代理网元、和/或可信锚点等通信。此外，收发器703可以包括接收器和发送器(图7中未单独示出)。其中，接收器用于实现接收功能，发送器用于实现发送功能。收发器703可以和处理器701集成在一起，也可以独立存在，并通过通信装置700的输入/输出端口(图7中未示出)与处理器701耦合，本申请实施例对此不作具体限定。
需要说明的是，图7中示出的通信装置700的结构并不构成对该通信装置的限定，实际的通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面将结合图8-图9对本申请实施例提供的通信方法进行具体阐述。
示例性地，图8为本申请实施例提供的一种通信方法的流程示意图。
如图8所示，该通信方法包括如下步骤：
S801，服务请求网元向数据编排网元发送第一服务请求消息。相应地，数据编排网元接收第一服务请求消息。
可选地，第一服务请求消息可用于请求应用服务或业务服务。
可选地，服务请求网元可以为应用、应用服务器或网络业务网元等。
本申请实施例中，应用服务可指由应用、或应用服务器请求的服务，业务服务可指由网络业务网元请求的服务，在不同的场景中，第一服务请求消息所请求的服务可以不同。
示例性地，第一服务请求消息可用于请求但不限于如下一项或多项服务：网络数据相关的服务、用户数据相关的服务、人工智能模型数据相关服务、和物联网数据相关的服务。
可选地，网络数据可以包括但不限于如下一项或多项：日志(例如调试日志、安全日志、呼叫历史记录(call history record，CHR)日志等)、告警、话统、配置数据、最小化路测(minimization of drive-tests，MDT)数据、用户会话信息、通信感知一体化(integrated sensing and communication，ISAC)数据、数字孪生网络数据、网络元数据、网络状态、和网络行为。
示例性地，网络数据可以包括接入网设备采集的数据、和/或终端设备采集的数据等。
可选地，用户数据可以包括但不限于如下一项或多项：用户签约信息。例如，用户画像(profile)等。
可选地，物联网数据可以包括但不限于如下一项或多项：环境数据、传感器类数据、和物联网终端的测量数据。
示例性地，物联网数据可以包括SIoT终端设备收集的数据、以及非SIoT终端设备通过物联网网关收集的数据。
可选地，人工智能AI模型数据可以包括但不限于如下一项或多项：对应任务的训练数据集、对应任务的测试数据集、本地/全局模型数据、和AI元数据。
可选地，AI模型数据可以是通过对原始数据或预处理后的原始数据进行训练后生成的。
可选地，可以从数据类型、数据源、数据消费者、尽量正交等多个维度进行考量，对数据进行分类。
如此，网络中数据源多样，数据种类繁多，从而对数据的处理流程大不相同，合理对数据进行分类，可以简化处理流程，降低系统复杂度，可以支持各种数据类型的数据服务。
需要说明的是，本申请不对数据的划分进行限定，可以划分为更多或更少的种类，或者可以从其他角度划分数据的种类，也可以不划分数据的种类。
例如，网络业务网元向数据编排网元第一服务请求消息，该第一服务请求消息用于请求访问数据代理网元中的用户签约数据。
例如，运营商的用于网规网优的应用(可简称为网规网优应用)向数据编排网元发送第一服务请求消息，该第一服务请求消息用于请求训练联邦学习模型，该联邦学习模型用于进行服务质量预测。
例如，网规网优应用向数据编排网元发送第一服务请求消息，该第一服务请求消息用于请求对区域A的服务质量进行预测。
一些实施例中，可以将对区域A的服务质量进行预测的请求分解为如下请求：请求训练联邦学习模型(请求1)、和请求采用(已训练的)联邦学习模型对区域A的服务质量进行预测(请求2)。
类似的，可以将对区域A的服务质量进行预测的过程分解为如下阶段：训练联邦学习模型(阶段1)、和采用(已训练的)联邦学习模型对区域A的服务质量进行预测(阶段2)。如此，收到对区域A的服务质量进行预测的请求后，若服务请求网元本地存储有需要的联邦学习模型，可以直接执行阶段2，否则执行阶段1后执行阶段2。
阶段1：将训练联邦学习模型的请求转译为对应的需求信息，基于数据代理网元的数据服务能力，选择出参与本次数据服务的数据代理网元，编排各个数据代理网元形成动态的逻辑网络拓扑。在参与本次数据服务的数据代理网元中选择一个计算能力较强的数据代理网元(例如数据代理网元1)作为服务(server)端，训练联邦学习模型。其他数据代理网元(例如参与本次数据服务的数据代理网元中除数据代理网元1以外的数据代理网元)作为客户(client)端，来提供用于训练联邦学习模型的数据。经多轮训练后，生成联邦学习模型，由数据代理网元(例如作为服务端DA的数据代理网元1)发送给服务请求网元，或按需求存储在数据代理网元或DSF中。
需要说明的是，阶段1适用于服务请求网元请求训练联邦学习模型的场景。
阶段2：将采用联邦学习模型对区域A的未来一段时间的服务质量进行预测的请求转译为对应的需求信息，基于数据代理网元的数据服务能力，选择出参与本次数据服务的数据代理网元，编排各个数据代理网元形成动态的逻辑网络拓扑。在参与本次数据服务的数据代理网元中选择一个计算能力较强的数据代理网元(例如数据代理网元1)来进行服务质量预测。其他数据代理网元(例如参与本次数据服务的数据代理网元中除数据代理网元1以外的数据代理网元)，提供用于服务质量预测的数据(例如实时的网络数据等)给数据代理网元1，也可以对数据进行一些操作(例如去隐私等处理)。数据代理网元1采用联邦学习模型和数据(原始数据或中间数据)进行推理， 获得服务质量预测结果并发给服务请求网元。
需要说明的是，数据代理网元1可以将获得的中间数据发送服务请求网元，由服务请求网元采用联邦学习模型和中间数据进行推理，获得服务质量预测结果。服务请求网元中的联邦学习模型可以是从数据代理网元取得、或者是预配置的，本申请不限定。
例如，IoT终端设备异常行为检测场景中，应用或网络业务网元向数据编排网元发送第一服务请求消息，该第一服务请求消息用于请求物联网数据、对物联网数据处理(例如预处理、分析等)后获得的中间数据、或IoT终端设备异常行为检测结果等。
在一些实施例中，第一服务请求消息可以是基于标准模板填写的需求。
例如标准模板可以是服务等级协议。
S802，数据编排网元根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息。
示例性地，需求信息可以是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。
可选地，第一数据可以包括从移动通信网络采集的数据、和/或合成的数据。
示例性地，第一数据可以包括但不限于如下一项或多项：终端设备侧的数据、接入网设备侧各功能节点的数据、传输网侧的各功能节点的数据、核心网侧的各功能节点的数据以及OAM的各功能节点的数据、和合成的数据。
示例性地，合成的数据可以指人工合成的数据。
例如，通过对抗学习可以生成人脸，该人脸的数据可以认为是合成的数据。
例如在某类数据比较少，如一些异常数据较少的情况下，可以合成数据。
可选地，合成的数据可用于训练人工智能模型等。
示例性地，可以对第一数据进行分类，第一数据以包括但不限于如下一项或多项：网络数据、用户数据、人工智能模型数据和物联网数据。
可选地，可以从数据类型、数据源、数据消费者、尽量正交等多个维度进行考量，对数据进行分类。
需要说明的是，本申请不对第一数据的划分进行限定，可以划分为更多或更少的种类，或者可以从其他角度划分第一数据的种类，也可以不划分第一数据的种类。
示例性地，一个或多个数据服务能力信息与一个或多个数据代理网元一一对应。
例如，以多个数据服务能力信息包括数据服务能力信息1、数据服务能力信息2和数据服务能力信息3为例，数据服务能力信息1对应数据代理网元1，数据服务能力信息2对应数据代理网元2，数据服务能力信息3对应数据代理网元3。
需要说明的是，本申请实施例中，多个数据代理网元可以为不同类型的数据代理网元，也可以为相同类型的数据代理网元。
例如，数据代理网元1至数据代理网元3均为(或部署在)接入网设备。又例如，数据代理网元1为核心网网元，数据代理网元2为接入网设备，数据代理网3为终端设备。又例如，数据代理网元1为接入网设备，数据代理网元2为终端设备，数据代理网元3为终端设备。
示例性地，至少一个数据代理网元可以是一个或多个数据代理网元中的至少一个。
例如，数据编排网元根据需求信息、数据服务能力信息1、数据服务能力信息2和数据服务能力信息3，从数据代理网元1、数据代理网元2和数据代理网元3中确定参与本次数据服务的数据代理网元，例如选择数据代理网元1和数据代理网元2参与本次数据服务，并确定数据代理网元1和数据代理网元2分别对应的操作配置信息。
示例性地，至少一个数据代理网元中任一个数据代理网元的操作配置信息可指示任一个数据代理网元对第一数据执行的操作。
例如，数据代理网元1对应的操作配置信息指示数据代理网元1对第一数据或基于第一数据生成的数据执行的操作。数据代理网元2对应的操作配置信息指示数据代理网元2对第一数据或基于第一数据生成的数据执行的操作。
示例性地，需求信息对应一个或多个数据服务能力信息中的至少一个。
例如，数据代理网元根据需求信息和至少一个数据服务能力信息确定参与本次数据服务的数据代理网元，选择出的数据代理网元的数据服务能力需要能够实现需求信息中对第一数据的服务需求，选择出的数据代理网元需要具备完成本次数据服务的能力，如此能够实现数据服务。
在一些实施例中，一个或多个数据代理网元中任一个数据代理网元的数据服务能力信息可以包括但不限于如下一项或多项：任一个数据代理网元的标识、任一个数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力。
可选地，数据服务能力信息可与数据代理网元的标识存在对应关系。
可选地，位置信息可以指地理位置的信息，位置信息可以包括经纬度等。
可选地，数据采集能力可以包括支持采集的数据类型，数据类型可以包括但不限于如下一项或多项：网络数据、用户数据、物联网数据、和人工智能模型数据。
可选地，数据预处理能力可以包括支持的预处理方式，例如对原始数据的字段提取、格式转化、冗余数据清除、压缩、融合等。
可选地，数据存储能力可以包括但不限于如下一项或多项：可存储的数据容量、存储数据的加密算法、和存储方式。
可选地，数据上报能力可以包括但不限于如下一项或多项：最小上报周期、单次上报的数据量、最大上报的数据量、是否支持文件上传、和是否支持流式数据。
可选地，数据分析能力可以包括但不限于如下一项或多项：支持的分析任务、是否支持AI训练、和是否支持AI推理。
可选地，与服务请求网元交互的能力可以包括但不限于：是否能够提供应用可编程接口服务。
可选地，数据保护能力可以包括但不限于如下一项或多项：支持的数据保护技术，例如，k-匿名化(k-anonymity)、l-多样化(l-diversity)、差分隐私、同态加密、和安全多方计算等。
可选地，数据压缩能力可以包括但不限于如下一项或多项：支持的数据压缩算法，例如，哈夫曼编码(Huffman Coding)、和算术编码等。
需要说明的是，数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与服务请求网元交互的能力、数据保护能力、和数据压缩能力的实现 方式还可以参考上述图2中对数据代理网元的功能的阐述，数据代理网元具有相应的功能可表示具有对应的能力。
在一些实施例中，需求信息可以包括但不限于如下一项或多项服务需求：地理位置、数据采集、数据预处理、数据存储、数据上报、数据分析、与服务请求网元交互、数据保护、和数据压缩。
可选地，需求信息可以与数据服务任务标识(data service task Identify，DSID)对应。
例如，数据服务任务标识可用于标识第一服务请求消息对应的数据服务任务。
可选地，数据编排网元可以对第一服务请求消息所请求的服务进行需求转译，转译(或映射)为对数据代理网元的功能的服务需求。
例如，假设第一服务请求消息用于请求对区域A的服务质量进行预测，数据编排网元进行需求转译，获得的需求信息可以包括：区域A、数据采集、数据预处理、数据分析、与服务请求网元交互、和第一数据的类型为网络数据。
在一些实施例中，操作配置信息所指示的操作可以包括但不限于如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与服务请求网元交互。
需要说明的是，本申请中操作配置信息所指示的操作与通常的编译码、调制解调操作、速率匹配不同。
需要说明的是，数据采集、数据预处理、数据存储、数据分析、与服务请求网元交互、数据保护这些操作的实现方式还可以参考上述图2中对数据代理网元的功能的阐述、以及本申请中对数据服务能力信息的阐述，此处不再赘述。
一些实施例中，本申请实施例提供的方法，还可以包括：数据编排网元确定第一通信信息。
可选地，第一通信信息可用于指示至少一个数据代理网元中与服务请求网元直接通信的数据代理网元的信息。
示例性地，假设与服务请求网元直接通信的数据代理网元为数据代理网元1，第一通信信息可以包括但不限于如下一项或多项数据代理网元1的地址、数据代理网元1的标识和数据代理网元1的索引。
可选地，第一通信信息可以是根据至少一个数据代理网元的数据服务能力信息确定的。
例如，从至少一个数据代理网元中选择具有与服务请求网元交互的能力的数据代理网元，作为与服务请求网元直接通信的数据代理网元。
也就是说，数据编排网元可以从确定的参与本次数据服务的数据代理网元中选择与服务请求网元直接通信的数据代理网元。
下面以请求训练联邦学习模型(例如上述S802中的阶段1)场景为例，对数据编排网元确定参与本次数据服务的数据代理网元和数据代理网元对应的操作配置信息进行阐述。
例如，假设第一服务请求消息用于请求训练AI模型，数据编排网元进行需求转译，获得的需求信息可以包括：区域A、数据采集、数据预处理、数据分析、和与服务请求网元交互。
数据编排网元根据需求信息、数据服务能力信息1、数据服务能力信息2和数据服务能力信息3，从数据代理网元1、数据代理网元2和数据代理网元3中确定参与本次数据服务的数据代理网元。数据服务能力信息1至数据服务能力信息3与数据代理网元1至数据代理网元3分别对应。
假设数据服务能力信息1包括：区域A、支持数据预处理、支持数据存储、支持AI训练和AI推理、支持与服务请求网元交互、和支持数据采集。
假设数据服务能力信息2包括：区域A、支持数据预处理、不支持AI训练和AI推理、不支持与服务请求网元交互、和支持数据采集。
假设数据服务能力信息3包括：区域B、支持数据预处理、支持数据存储、不支持AI训练和AI推理、支持与服务请求网元交互、和支持数据采集。
数据编排网元根据需求信息、数据服务能力信息1、数据服务能力信息2和数据服务能力信息3，可以确定数据代理网元1和数据代理网元2联合可以实现需求信息中的服务需求，首先数据代理网元3的地理位置为区域B不是区域A，其次数据代理网元3不支持AI训练和AI推理，数据代理网元3并不能参与训练AI模型。
数据编排网元根据需求信息、数据服务能力信息1、和数据服务能力信息2，确定数据代理网元1对应的操作配置信息1和数据代理网元2分别对应的操作配置信息2，例如，操作配置信息1包括：采集原始数据、数据预处理、AI训练和AI推理、与服务请求网元交互。操作配置信息2包括：采集原始数据、数据预处理、与数据代理网元1交互。
下面以请求对区域A的服务质量进行预测(例如上述S802中的阶段2)的场景为例，对数据编排网元确定参与本次数据服务的数据代理网元和数据代理网元对应的操作配置信息进行阐述。
数据编排网元根据需求信息、数据服务能力信息1、数据服务能力信息2和数据服务能力信息3，从数据代理网元1、数据代理网元2和数据代理网元3中确定参与本次数据服务的数据代理网元。数据服务能力信息1至数据服务能力信息3与数据代理网元1至数据代理网元3分别对应。
假设需求信息包括：区域A、数据采集、数据预处理、数据分析、和与服务请求网元交互。
假设数据服务能力信息1包括：区域A、支持数据预处理、支持数据存储、支持AI训练和AI推理、支持与服务请求网元交互、和支持采集数据。
假设数据服务能力信息2包括：区域A、支持数据预处理、不支持AI训练和AI推理、不支持与服务请求网元交互、和支持采集数据。
假设数据服务能力信息3包括：区域B、支持数据预处理、支持数据存储、不支持AI训练和AI推理、支持与服务请求网元交互、和支持采集数据。
数据编排网元根据需求信息、数据服务能力信息1、数据服务能力信息2和数据服务能力信息3，可以确定数据代理网元1和数据代理网元2联合可以实现需求信息中的服务需求，数据代理网元3的地理位置为区域B不是区域A，数据代理网元3并不能参与预测区域A的服务质量。
数据编排网元根据需求信息、数据服务能力信息1、和数据服务能力信息2，确定 数据代理网元1对应的操作配置信息1和数据代理网元2分别对应的操作配置信息2，例如，操作配置信息1包括：AI训练和AI推理、与服务请求网元交互。操作配置信息2包括：采集原始数据、数据预处理、与数据代理网元1交互。
在一种可能的设计方式中，上述S802可以包括：在服务请求网元具有访问第一数据的权限的情况下，数据编排网元根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息。
如此，在服务请求网元具有访问第一数据的权限的情况下，才确定参与数据服务的数据代理网元以及对应的操作配置信息，否则，不确定参与数据服务的数据代理网元以及对应的操作配置信息，可以实现数据的E2E的可信服务要求。
在一些实施例中，本申请实施例提供的方法，还可以包括：S806，可信锚点向第一数据代理网元发送第一验证响应消息。相应地，数据编排网元接收来自可信锚点的第一验证响应消息。
可选地，第一验证响应消息可指示服务请求网元具有访问第一数据的权限，或者指示服务请求网元不具有访问第一数据的权限。
也就是说，服务请求网元是否具有访问第一数据的权限可以是数据编排网元从可信锚点获取的。
需要说明的是，本申请实施例不限定S806的执行顺序，例如S806可以在上述S802之前执行。
在一些实施例中，本申请实施例提供的方法，还可以包括：S807，数据编排网元向可信锚点发送第一验证请求消息。相应地，可信锚点接收来自数据编排网元的第一验证请求消息。
可选地，第一验证请求消息可用于请求验证服务请求网元是否具有访问第一数据的权限。
需要说明的是，S807可以在上述S806之前执行。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：S808，一个或多个数据代理网元向数据编排网元发送数据服务能力信息。相应地，数据编排网元接收一个或多个数据代理网元对应的数据服务能力信息。
假设确定出的至少一个数据代理网元包括第一数据代理网元，图8中S808，以第一数据代理网元为例进行阐述，第一数据代理网元向数据编排网元发送数据服务能力信息。相应地，数据编排网元接收来自第一数据代理网元的数据服务能力信息。
需要说明的是，本申请不限定S808执行顺序，例如S808可以在上述S801之前执行，或者，S808可以在上述S802之前执行。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：一个或多个数据代理网元向数据编排网元进行注册，这可在上述S808之前执行或同时执行，本申请不限定。
S803，数据编排网元向第一数据代理网元发送操作配置信息。相应地，第一数据代理网元接收来自数据编排网元的操作配置信息。
示例性地，操作配置信息可指示第一数据代理网元对第一数据执行的操作。
如此，数据编排网元向至少一个数据代理网元中的每个数据代理网元发送对应的操作配置信息。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：数据编排网元向至少一个数据代理网元中的一个或多个发送更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。相应地，至少一个数据代理网元中的一个或多个接收来自数据编排网元的更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
示例性地，至少一个数据代理网元可以包括第一数据代理网元，第一数据代理网元接收来自数据编排网元的更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
可选地，数据安全及隐私保护技术库的信息可以包括但不限于如下一项或多项：数据安全及隐私保护技术库的标识、数据安全及隐私保护技术库的索引、和数据安全及隐私保护技术库。
可选地，分析工具库的信息可以包括但不限于如下一项或多项：分析工具库的标识、分析工具库的索引、和分析工具库本身。
也就是说，数据安全及隐私保护技术库和分析工具库等如果有更新，数据编排网元可以推送给数据代理网元，如此，可以实现数据安全保护、数据隐私保护等。
需要说明的是，数据编排网元向第一数据代理网元发送操作配置信息，以及发送更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息，可以在同一步骤中执行，也可以单独执行，本申请不限定。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：S809，数据编排网元向服务请求网元发送第一通信信息。相应地，服务请求网元接收来自数据编排网元的第一通信信息。
如此，服务请求网元可以根据收到的第一通信信息，与第一数据代理网元建立直接交互，可以直接接收来自第一数据代理网元的消息。
需要说明的是，上述S809可以在上述S802之后执行，本申请不限定上述S809与上述S803的执行顺序。
S804，第一数据代理网元根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息。
示例性地，第一数据代理网元获取操作配置信息所指示的操作，编排第一数据代理网元中各个功能形成操作链，前一个功能的输出是下一个功能的输入，按照该操作链对第一数据进行处理，获得第一信息。
可选地，第一信息可以是原始数据、中间数据、或分析结果等。
需要说明的是，操作配置信息的具体实现方式可参照上述S802中对应的阐述，此处不再赘述。
在一些实施例中，上述S804可以包括下述步骤一至步骤二。
步骤一，第一数据代理网元根据操作配置信息，向第三数据代理网元发送数据请求消息。相应地，第三数据代理网元接收来自第一数据代理网元的数据请求消息。
可选地，数据请求消息可用于请求但不限于如下一项或多项数据：网络数据、用 户数据、物联网数据、和人工智能模型数据。
示例性地，操作配置信息可以包括：从第三数据代理网元采集第一数据。
需要说明的是，第一数据代理网元和第三数据代理网元可以为不同类型的数据代理网元，也可以为相同类型的数据代理网元。
例如，假设第一数据代理网元为接入网设备1，则第三数据代理网元可以是接入网设备2，或者是终端设备。
如此，可以形成域间数据代理网元衔接，形成跨域的数据服务架构。
可选地，数据请求消息可以包括安全信息。
可选地，安全信息可用于验证第一数据代理网元是否具有访问第一数据的权限。
例如，安全信息可以包括但不限于私钥签名。
如此，可以验证第一数据代理网元是否具有访问第一数据的权限。
步骤二，第三数据代理网元向第一数据代理网元发送数据响应消息。相应地，第一数据代理网元接收来自第三数据代理网元的数据响应消息。
可选地，数据响应消息可以包括数据请求消息中包括的一项或多项数据。
可选地，第一信息可以包括第一数据，例如，网络数据、用户数据、物联网数据、和人工智能模型数据等。
如此，可以实现第一数据代理网元从数据源(第三数据代理网元)获取第一数据。
可选地，上述步骤二可以包括：在第一数据代理网元具有访问第三数据代理网元的第一数据的情况下，第三数据代理网元向第一数据代理网元发送数据响应消息，否则，拒绝请求，可以实现数据的E2E的可信服务要求。
可选地，第一数据代理网元是否具有访问第三数据代理网元的第一数据的权限可以是第三数据代理网元从可信锚点获取的。
示例性地，第三数代理网元向可信锚点发送验证请求消息，并接收来自可信锚点的验证相应消息。
例如，验证请求消息可用于请求验证第一数据代理网元是否具有访问第三数据代理网元的第一数据的权限。
可选地，验证请求消息可以包括：第一数据代理网元对应的安全信息。
例如，验证响应消息可指示第一数据代理网元具有或不具有访问第三数据代理网元的第一数据的权限。
可选地，可信锚点收到验证请求消息，可以检查数据访问策略，验证安全信息，获得第一数据代理网元具有或不具有访问第三数据代理网元的第一数据的权限。
示例性地，可信锚点可以根据第一数据的数据类型，来检查数据访问策略，验证安全信息。
例如，数据访问策略可以包括：第一数据代理网元具有访问第三数据代理网元的网络数据的权限，第一数据代理网元不具有访问第三数据代理网元的用户数据的权限。若第一数据为用户数据，则验证响应消息可指示第一数据代理网元不具有访问第三数据代理网元的用户数据的权限。若第一数据包括用户数据和网络数据，则验证响应消息可指示第一数据代理网元不具有访问第三数据代理网元的用户数据的权限,第一数据代理网元具有访问第三数据代理网元的网络数据的权限。
在一些实施例中，上述S804可以包括：第一数据代理网元根据操作配置信息所指示的操作对第二信息进行处理，获得第一信息。
可选地，第二信息可以是第一数据代理网元接收的。
例如，第二信息可以是第一数据代理网元从其他数据代理网元接收的。
可选地，第二信息可以是基于第一数据获得的。
例如，第二信息可以是其他数据代理网元对第一数据进行处理(例如数据采集、数据预处理、数据保护、数据存储、和/或数据分析等)后获得的。
示例性地，操作配置信息可以包括但不限于如下一项或多项：数据采集、数据预处理、数据保护、数据存储、和数据分析。
例如，第二信息是其他数据代理网元对第一数据进行数据预处理后获得的，操作配置信息包括数据分析和数据保护，第一数据代理网元根据操作配置信息形成操作链(进行数据分析，然后进行安全保护)，对第二信息进行分析并进行安全保护后获得第一信息。
在一些实施例中，上述S804可以包括：第一数据代理网元根据操作配置信息所指示的操作对第一数据和应用数据进行处理，获得第一信息。
可选地，该应用数据可以是第一数据代理网元从应用网元获取的。
可选地，应用网元中可以部署数据代理网元。
示例性地，应用数据可以包括但不限于：应用程序合规(例如用户已授权)收集到的用户历史行为记录。
例如，第一数据代理网元对物联网数据和应用数据进行协同处理，能够快速准确地判断物联网终端设备的异常行为。
S805a，在操作配置信息指示第一数据代理网元与第二数据代理网元通信的情况下，第一数据代理网元向第二数据代理网元发送第一信息。相应地，第二数据代理网元接收来自第一数据代理网元的第一信息。
可选地，操作配置信息可指示第一数据代理网元将第一信息传输给第二数据代理网元。
示例性地，操作配置信息可包括：与第二数据代理网元交互。
如此，第一数据代理网元可以将第一信息发给第二数据代理网元，第二数据代理网元可以根据第二数据代理网元对应的操作配置信息，对第一数据进行处理或转发等。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：S810，可信锚点向第一数据代理网元发送第二验证响应消息。相应地，第一数据代理网元接收来自可信锚点的第二验证响应消息。
可选地，第二验证响应消息可指示第二数据代理网元具有访问第一数据代理网元的第一数据的权限，或者指示第二数据代理网元不具有访问第一数据代理网元的第一数据的权限。
需要说明的是，本申请实施例不限定S810的执行顺序，例如S810可以在上述S805a之前执行。
例如，第一数据代理网元获得第二数据代理网元具有访问第一数据代理网元的第一数据的权限的情况下，向第二数据代理网元发送第一信息，否则，不向第二数据代 理网元发送第一信息，可以实现数据的E2E的可信服务要求。
如此，在第一数据包括用户数据的情况下，可以实现对用户数据E2E的合规检测。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：S811，第一数据代理网元向可信锚点发送第二验证请求消息。相应地，可信锚点接收来自第一数据代理网元的第二验证请求消息。
可选地，第二验证请求消息可用于请求验证第二数据代理网元是否具有访问第一数据代理网元的第一数据的权限。
可选地，第二验证请求消息可以包括：第二数据代理网元对应的安全信息。
例如，第二数据代理网元对应的安全信息可以是第一数据代理网元从第二数代理网元获取的。
例如，安全信息可以包括但不限于私钥签名。
可选地，可信锚点收到第二验证请求消息，可以检查数据访问策略，验证安全信息，获得第二数据代理网元具有或不具有访问第一数据代理网元的第一数据的权限。具体实现与上述可信锚点收到验证请求消息，可以检查数据访问策略，验证安全信息，获得第一数据代理网元具有或不具有访问第三数据代理网元的第一数据的权限的实现方式类似，此处不再赘述。
S805b，在操作配置信息指示第一数据代理网元与服务请求网元通信的情况下，第一数据代理网元向服务请求网元发送第一信息。相应地，服务请求网元接收来自数据代理网元的第一信息。
示例性地，第一信息可以是基于第一数据获得的。
可选地，第一数据代理网元可以是与服务请求网元直接通信的数据代理网元。
可选地，操作配置信息可指示第一数据代理网元将第一信息传输给服务请求网元。
示例性地，操作配置信息可包括：与服务请求网元交互。
如此，服务请求网元获得第一信息，第一信息可以是原始数据、中间数据、或分析结果等。
在一些实施例中，本申请实施例提供的方法，还可以包括：S812，第一数据代理网元向可信锚点发送处理行为信息。相应地，可信锚点接收来自第一数据代理网元的处理行为信息。
可选地，处理行为信息可指示第一数据代理网元对第一数据的处理行为。
示例性地，第一数据为用户数据，处理行为信息可以指示第一数据代理网元对第一数据的处理行为，例如采集、预处理、存储、数据分析、数据保护、去隐私、和发送等。
可选地，可信锚点可以将处理行为记录到分布式账本上。
如此，任意数据代理网元在处理过程中(例如上述S804-S805b)涉及到对用户数据的处理，均可以向可信锚点发送处理行为信息，可以满足GDPR/PIPL的合规要求。
在一种可能的设计方法中，本申请实施例提供的方法，还可以包括：服务请求网元对第一信息进行处理，获得应用服务或业务服务。
示例性地，第一信息可能不是服务请求网元想要的最终结果，例如可能是中间数据，服务请求网元对第一信息进行处理，获得最终结果。
在一些实施例中，上述服务请求网元对第一信息进行处理，获得应用服务或业务服务，可以包括：服务请求网元采用第一信息获取物联网终端设备的异常行为信息。
例如，IoT终端设备异常行为检测场景中，可以获得物联网终端设备的异常行为，例如劫持IoT终端设备、空口信令分布式拒绝服务(distributed denial of service，DDoS)攻击等。
在一些实施例中，上述服务请求网元对第一信息进行处理，获得应用服务或业务服务，可以包括：服务请求网元采用第一信息和人工智能模型参数配置信息，进行服务质量预测。
可选地，人工智能模型参数配置信息可用于对服务质量进行预测。
如此，服务请求网元采用人工智能模型参数配置信息和第一信息(为中间数据)进行推理，获得服务质量预测结果。
可选地，服务请求网元本地存储有人工智能模型参数配置信息。
或者，可选地，服务请求网元本地未存储人工智能模型参数配置信息，可以通过第一数据代理网元获取人工智能模型参数配置信息，向第一数据代理网元请求人工智能模型参数配置信息。
可选地，服务请求网元可以对人工智能模型的摘要进行哈希，与分布式账本上存储的哈希值进行对比，以验证模型的一致性。
基于图8所示的方法，数据编排网元接收第一服务请求消息，根据需求信息和一个或多个数据服务能力信息，从一个或多个数据代理网元中确定参与本次数据服务的数据代理网元，并获得参与本次数据服务的每个数据代理网元对应的操作配置信息，该操作配置信息指示数据代理网元对第一数据执行的操作，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。数据编排网元将操作配置信息发给对应的数据代理网元，数据代理网元执行操作配置信息所指示的操作，如此，可以实现数据服务。
示例性地，图9为本申请实施例提供的一种通信方法的流程示意图。图9以NS网元接收服务请求消息并转译为需求信息，数据编排网元从NS网元获取需求信息为例对图8所示的方法进行阐述。
如图9所示，该通信方法包括如下步骤：
S901，服务请求网元向网络业务网元发送第一服务请求消息。相应地，网络业务网元接收第一服务请求消息。
可选地，第一服务请求消息可用于请求应用服务或业务服务。第一服务请求消息的具体实现方式可参照上述S801中对应的阐述，此处不再赘述。
例如，运营商的用于网规网优的应用(可简称为网规网优应用)向数据编排网元发送第一服务请求消息，该第一服务请求消息用于请求训练联邦学习模型，该联邦学习模型用于进行服务质量预测。
例如，网规网优应用向数据编排网元发送第一服务请求消息，该第一服务请求消息用于请求对区域A的服务质量进行预测。具体实现方式可参照上述S801中对应的阐述，此处不再赘述。
S902，网络业务网元向数据编排网元发送需求信息。相应地，数据编排网元接收 来自网络业务网元的需求信息。
示例性地，需求信息可以是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。
例如，需求信息可以是网络业务网元根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。
可选地，网络业务网元可以对第一服务请求消息所请求的服务进行需求转译，转译(或映射)为对数据代理网元的功能的服务需求。
例如，假设第一服务请求消息用于请求训练AI模型，网络业务网元进行需求转译，获得的需求信息可以包括：区域A、数据采集、数据预处理、数据分析、和与服务请求网元交互。
需要说明的是，需求信息的具体实现方式可参照上述S902中对应的阐述，此处不再赘述。
可选地，由网络业务网元确定需求信息，可适用但不限于如下场景：请求训练联邦学习模型(例如上述S802中的阶段1)场景和请求对区域A的服务质量进行预测(例如上述S802中的阶段2)的场景。
S903，数据编排网元根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息。
需求信息、数据服务能力信息、至少一个数据代理网元、操作配置信息的具体实现方式可参照上述S801中对应的阐述，此处不再赘述。
示例性地，需求信息对应一个或多个数据服务能力信息中的至少一个。
需要说明的是，S903的具体实现方式可参照上述S802中对应的阐述，此处不再赘述。
一些实施例中，本申请实施例提供的方法，还可以包括：数据编排网元确定第一通信信息。具体实现方式可参照上述S802中对应的阐述，此处不再赘述。
S904，数据编排网元向第一数据代理网元发送操作配置信息。相应地，第一数据代理网元接收操作配置信息。
需要说明的是，S904的具体实现方式可参照上述S803中对应的阐述，此处不再赘述。
可选地，本申请实施例提供的方法，还可以包括：S907，网络业务网元向第一数据代理网元发送人工智能训练模型参数配置信息。相应地，第一数据代理网元接收来自网络业务网元的人工智能训练模型参数配置信息。
示例性地，人工智能训练模型参数配置信息可用于数据代理网元基于人工智能训练模型训练出服务请求网元所请求的AI模型，例如可用于进行服务质量预测的AI模型。
S905，第一数据代理网元根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息。
需要说明的是，S905的具体实现方式可参照上述S804中对应的阐述，此处不再赘述。
S906a，在操作配置信息指示第一数据代理网元与第二数据代理网元通信的情况下， 第一数据代理网元向第二数据代理网元发送第一信息。相应地，第二数据代理网元接收来自第一数据代理网元的第一信息。
需要说明的是，S906a的具体实现方式可参照上述S805a中对应的阐述，此处不再赘述。
S906b，在操作配置信息指示第一数据代理网元与服务请求网元通信的情况下，第一数据代理网元向服务请求网元发送第一信息。相应地，服务请求网元接收来自数据代理网元的第一信息。
需要说明的是，S906b的具体实现方式可参照上述S805b中对应的阐述，此处不再赘述。
在一些实施例中，本申请实施例提供的方法，还可以包括如图9所示的S908-S914。S908-S914的具体实现方式与上述S806-S812类似，可参照上述S806-S812，此处不再赘述。
基于图9所示的方法，网络业务网元接收第一服务请求消息，并向数据编排网元发送需求信息，数据编排网元根据需求信息和一个或多个数据服务能力信息，从一个或多个数据代理网元中确定参与本次数据服务的数据代理网元，并获得参与本次数据服务的每个数据代理网元对应的操作配置信息，该操作配置信息指示数据代理网元对第一数据执行的操作，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求。数据编排网元将操作配置信息发给对应的数据代理网元，数据代理网元执行操作配置信息所指示的操作，如此，可以实现数据服务。
本申请中，除特殊说明外，各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中，如果没有特殊说明以及逻辑冲突，不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以下所述的本申请实施方式并不构成对本申请保护范围的限定。
以上结合图1-图9详细说明了本申请实施例提供的通信方法。以下结合图10-图11详细说明本申请实施例提供的通信装置。
示例性地，图10是本申请实施例提供的另一种通信装置的结构示意图。该通信装置可适用于图1所示出的通信系统中，为了便于说明，图10仅示出了该通信装置的主要部件。如图10所示，该通信装置1000包括：收发模块1001和处理模块1002。
在一种可能的设计方案中，图10所示出的通信装置1000可适用于图1所示出的系统中，执行上述图8和图9所述的通信方法中数据编排网元的功能。
其中，收发模块1001，用于接收第一服务请求消息。处理模块1002，用于根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和至少一个数据代理网元中每个数据代理网元对应的操作配置信息。收发模块1001，还用于发送操作配置信息。其中，需求信息是根据第一服务请求消息所请求的服务确定的对第一数据的服务需求，一个或多个数据服务能力信息与一个或多个数据代理网元一一对应，至少一个数据代理网元是一个或多个数据代理网元中的至少一个，需求信息对应一个或 多个数据服务能力信息中的至少一个，至少一个数据代理网元中任一个数据代理网元的操作配置信息指示任一个数据代理网元对第一数据执行的操作。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
需要说明的是，收发模块1001可以包括接收模块和发送模块(图10中未示出)，不做具体限定。
可选地，通信装置1000还可以包括存储模块(图10中未示出)，该存储模块存储有程序或指令。当处理模块1002执行该程序或指令时，使得通信装置1000可以执行图8或图9所示的通信方法中数据编排网元的功能。
需要说明的是，通信装置1000可以是数据编排网元，也可以是可设置于数据编排网元的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，通信装置1000的技术效果可以参考图8和图9所示的通信方法的技术效果，此处不再赘述。
在一种可能的设计方案中，图10所示出的通信装置1000可适用于图1所示出的系统中，执行上述图8和图9所述的通信方法中第一数据代理网元的功能。
其中，收发模块1001，用于接收操作配置信息。处理模块1002，用于根据操作配置信息所指示的操作对第一数据进行处理，获得第一信息。收发模块1001，还用于在操作配置信息指示通信装置与第二数据代理网元通信的情况下，向第二数据代理网元发送第一信息。或者，收发模块1001，还用于在操作配置信息指示通信装置与服务请求网元通信的情况下，向服务请求网元发送第一信息。其中，操作配置信息指示通信装置对第一数据执行的操作。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
需要说明的是，收发模块1001可以包括接收模块和发送模块(图10中未示出)，不做具体限定。
可选地，通信装置1000还可以包括存储模块(图10中未示出)，该存储模块存储有程序或指令。当处理模块1002执行该程序或指令时，使得通信装置1000可以执行图8或图9所示的通信方法中第一数据代理网元的功能。
需要说明的是，通信装置1000可以是第一数据代理网元，也可以是可设置于第一数据代理网元的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，通信装置1000的技术效果可以参考图8和图9所示的通信方法的技术效果，此处不再赘述。
示例性地，图11是本申请实施例提供的又一种通信装置的结构示意图。该通信装置可适用于图1所示出的通信系统中，为了便于说明，图11仅示出了该通信装置的主要部件。如图11所示，该通信装置1100包括：发送模块1101和接收模块1102。
其中，发送模块1101，用于向数据编排网元发送第一服务请求消息。接收模块1102，用于接收来自数据代理网元的第一信息。其中，第一信息是基于第一数据获得的。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
需要说明的是，接收模块1102和发送模块1101可以分开设置，也可以集成在一个模块中，即收发模块(图11中未示出)。本申请对于接收模块1102和发送模块1101的具体实现方式，不做具体限定。
可选地，通信装置1100还可以包括处理模块1103和存储模块(图11中未示出)，该存储模块存储有程序或指令。当处理模块1103执行该程序或指令时，使得通信装置1100可以执行图8或图9所示的通信方法中服务请求网元的功能。
需要说明的是，通信装置1100可以是服务请求网元，也可以是可设置于服务请求网元的芯片(系统)或其他部件或组件，本申请对此不做限定。
此外，通信装置1100的技术效果可以参考图8和图9所示的通信方法的技术效果，此处不再赘述。
本申请实施例提供一种通信系统。该通信系统包括数据编排网元和第一数据代理网元，还可以包括服务请求网元。其中，数据编排网元用于执行上述方法实施例中数据编排网元的动作，第一数据代理网元用于执行上述方法实施例中第一数据代理网元的动作，服务请求网元用于执行上述方法实施例中服务请求网元的动作，具体执行方法和过程可参照上述方法实施例，此处不再赘述。
本申请实施例提供一种芯片系统，该芯片系统包括逻辑电路和输入/输出端口。其中，逻辑电路可用于实现本申请实施例提供的通信方法所涉及的处理功能，输入/输出端口可用于本申请实施例提供的通信方法所涉及的收发功能。
示例性地，输入端口可用于实现本申请实施例提供的通信方法所涉及的接收功能，输出端口可用于实现本申请实施例提供的通信方法所涉及的发送功能。
在一种可能的设计中，该芯片系统还包括存储器，该存储器用于存储实现本申请实施例提供的通信方法所涉及功能的程序指令和数据。
该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得本申请实施例提供的通信方法被执行。
本申请实施例提供一种计算机程序产品，该计算机程序产品包括：计算机程序或指令，当计算机程序或指令在计算机上运行时，使得本申请实施例提供的通信方法被执行。
应理解，在本申请实施例中的处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically  EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件(如电路)、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (39)

  1. 一种通信方法，其特征在于，包括：
    数据编排网元接收第一服务请求消息；
    所述数据编排网元根据需求信息和一个或多个数据服务能力信息，确定至少一个数据代理网元和所述至少一个数据代理网元中每个数据代理网元对应的操作配置信息；其中，所述需求信息是根据所述第一服务请求消息所请求的服务确定的对第一数据的服务需求，所述一个或多个数据服务能力信息与一个或多个数据代理网元一一对应，所述至少一个数据代理网元是所述一个或多个数据代理网元中的至少一个，所述需求信息对应所述一个或多个数据服务能力信息中的至少一个，所述至少一个数据代理网元中任一个数据代理网元的所述操作配置信息指示所述任一个数据代理网元对所述第一数据执行的操作；
    所述数据编排网元发送所述操作配置信息。
  2. 根据权利要求1所述的通信方法，其特征在于，所述第一服务请求消息用于请求应用服务或业务服务。
  3. 根据权利要求1或2所述的通信方法，其特征在于，所述第一服务请求消息来自服务请求网元，所述方法还包括：
    所述数据编排网元接收来自可信锚点的第一验证响应消息；其中，所述第一验证响应消息指示所述服务请求网元具有访问所述第一数据的权限。
  4. 根据权利要求3所述的通信方法，其特征在于，所述方法还包括：
    所述数据编排网元向可信锚点发送第一验证请求消息；其中，所述第一验证请求消息用于请求验证所述服务请求网元是否具有访问所述第一数据的权限。
  5. 根据权利要求1-4中任一项所述的通信方法，其特征在于，所述第一服务请求消息来自服务请求网元，所述方法还包括：
    所述数据编排网元发送第一通信信息；其中，所述第一通信信息用于指示所述至少一个数据代理网元中与所述服务请求网元直接通信的数据代理网元的信息。
  6. 根据权利要求1-5中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述数据编排网元接收所述一个或多个数据代理网元对应的数据服务能力信息。
  7. 根据权利要求1-6中任一项所述的通信方法，其特征在于，所述一个或多个数据代理网元中任一个数据代理网元的数据服务能力信息包括如下一项或多项：所述任一个数据代理网元的标识、所述任一个数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与所述服务请求网元交互的能力、数据保护能力、和数据压缩能力。
  8. 根据权利要求1-7中任一项所述的通信方法，其特征在于，所述操作配置信息所指示的操作包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与所述服务请求网元交互。
  9. 根据权利要求1-8中任一项所述的通信方法，其特征在于，所述需求信息包括如下一项或多项服务需求：地理位置、数据采集、数据预处理、数据存储、数据上报、数据分析、与服务请求网元交互、数据保护、和数据压缩。
  10. 根据权利要求1-9中任一项所述的通信方法，其特征在于，所述需求信息与数 据服务任务标识对应。
  11. 根据权利要求1-10中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述数据编排网元向所述至少一个数据代理网元中的一个或多个发送更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
  12. 根据权利要求1-11中任一项所述的通信方法，其特征在于，所述数据编排网元部署在网络业务网元中。
  13. 根据权利要求1-12中任一项所述的通信方法，其特征在于，所述第一数据包括从移动通信网络采集的数据或合成的数据。
  14. 一种通信方法，其特征在于，包括：
    第一数据代理网元接收操作配置信息；其中，所述操作配置信息指示所述第一数据代理网元对第一数据执行的操作，
    所述第一数据代理网元根据所述操作配置信息所指示的操作对所述第一数据进行处理，获得第一信息；
    在所述操作配置信息指示所述第一数据代理网元与第二数据代理网元通信的情况下，所述第一数据代理网元向所述第二数据代理网元发送所述第一信息；或者，
    在所述操作配置信息指示所述第一数据代理网元与服务请求网元通信的情况下，所述第一数据代理网元向所述服务请求网元发送所述第一信息。
  15. 根据权利要求14所述的通信方法，其特征在于，所述操作配置信息所指示的操作包括如下一项或多项：数据采集、数据预处理、数据保护、数据存储、数据分析、和与所述服务请求网元交互。
  16. 根据权利要求14或15所述的通信方法，其特征在于，所述第一数据代理网元根据所述操作配置信息所指示的操作对所述第一数据进行处理，获得第一信息，包括：
    所述第一数据代理网元根据所述操作配置信息，向第三数据代理网元发送数据请求消息；其中，所述数据请求消息用于请求如下一项或多项数据：网络数据、用户数据、物联网数据、和人工智能模型数据；
    所述第一数据代理网元接收来自所述第三数据代理网元的数据响应消息；其中，所述数据响应消息包括所述数据请求消息中包括的一项或多项数据。
  17. 根据权利要求16所述的通信方法，其特征在于，所述数据请求消息还包括安全信息，所述安全信息用于验证所述第一数据代理网元是否具有访问所述第一数据的权限。
  18. 根据权利要求14或15所述的通信方法，其特征在于，所述第一数据代理网元根据所述操作配置信息所指示的操作对所述第一数据进行处理，获得第一信息，包括：
    所述第一数据代理网元根据所述操作配置信息所指示的操作对第二信息进行处理，获得所述第一信息；其中，所述第二信息是所述第一数据代理网元接收的，所述第二信息是基于所述第一数据获得的。
  19. 根据权利要求14-18中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述第一数据代理网元接收来自可信锚点的第二验证响应消息；其中，所述第二验证响应消息指示所述第二数据代理网元具有访问所述第一数据代理网元的所述第一数据的权限。
  20. 根据权利要求14-19中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述第一数据代理网元向可信锚点发送第二验证请求消息；其中，所述第二验证请求消息用于请求验证所述第二数据代理网元是否具有访问所述第一数据代理网元的所述第一数据的权限。
  21. 根据权利要求14-20中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述第一数据代理网元向数据编排网元发送数据服务能力信息。
  22. 根据权利要求21所述的通信方法，其特征在于，所述数据服务能力信息包括如下一项或多项：所述第一数据代理网元的标识、所述第一数据代理网元的位置信息、数据采集能力、数据预处理能力、数据存储能力、数据上报能力、数据分析能力、与所述服务请求网元交互的能力、数据保护能力、和数据压缩能力。
  23. 根据权利要求14-22中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述第一数据代理网元接收来自数据编排网元的更新的数据安全及隐私保护技术库的信息和/或更新的分析工具库的信息。
  24. 根据权利要求14-23中任一项所述的通信方法，其特征在于，所述第一数据包括从移动通信网络采集的数据或合成的数据。
  25. 一种通信方法，其特征在于，包括：
    服务请求网元向数据编排网元发送第一服务请求消息；
    所述服务请求网元接收来自数据代理网元的第一信息；其中，所述第一信息是基于第一数据获得的。
  26. 根据权利要求25所述的通信方法，其特征在于，所述第一服务请求消息用于请求应用服务或业务服务。
  27. 根据权利要求25或26所述的通信方法，其特征在于，所述方法还包括：
    所述服务请求网元接收第一通信信息；其中，所述第一通信信息用于指示与所述服务请求网元直接通信的数据代理网元的信息。
  28. 根据权利要求25-27中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述服务请求网元对所述第一信息进行处理，获得应用服务或业务服务。
  29. 根据权利要求28所述的通信方法，其特征在于，所述服务请求网元对所述第一信息进行处理，获得应用服务或业务服务，包括：
    所述服务请求网元采用所述第一信息获取物联网终端设备的异常行为信息。
  30. 根据权利要求28所述的通信方法，其特征在于，所述服务请求网元对所述第一信息进行处理，获得应用服务或业务服务，包括：
    所述服务请求网元采用所述第一信息和人工智能模型参数配置信息，进行服务质量预测；其中，所述人工智能模型参数配置信息用于对服务质量进行预测。
  31. 根据权利要求30所述的通信方法，其特征在于，所述方法还包括：
    所述服务请求网元向所述数据代理网元请求所述人工智能模型参数配置信息。
  32. 根据权利要求25-31中任一项所述的通信方法，其特征在于，所述第一数据包括从移动通信网络采集的数据或合成的数据。
  33. 一种通信装置，其特征在于，所述通信装置包括用于执行如权利要求1-13中任一项所述方法的单元或模块。
  34. 一种通信装置，其特征在于，所述通信装置包括用于执行如权利要求14-24中任一项所述方法的单元或模块。
  35. 一种通信装置，其特征在于，所述通信装置包括用于执行如权利要求25-32中任一项所述方法的单元或模块。
  36. 一种通信装置，其特征在于，所述通信装置包括：处理器；所述处理器，用于执行如权利要求1-32中任一项所述的通信方法。
  37. 一种通信系统，其特征在于，所述通信系统包括以下至少一项：用于执行如权利要求33所述的通信装置，如权利要求34所述的通信装置，或如权利要求35所述的通信装置。
  38. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-32中任一项所述的通信方法被执行。
  39. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-32中任一项所述的通信方法被执行。
PCT/CN2023/092838 2022-05-31 2023-05-08 通信方法、装置及系统 Ceased WO2023231714A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23814900.9A EP4525490A4 (en) 2022-05-31 2023-05-08 Communication method, apparatus, and system
US18/962,873 US20250097313A1 (en) 2022-05-31 2024-11-27 Communication method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210612736.9A CN117202135A (zh) 2022-05-31 2022-05-31 通信方法、装置及系统
CN202210612736.9 2022-05-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/962,873 Continuation US20250097313A1 (en) 2022-05-31 2024-11-27 Communication method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2023231714A1 true WO2023231714A1 (zh) 2023-12-07

Family

ID=89004001

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092838 Ceased WO2023231714A1 (zh) 2022-05-31 2023-05-08 通信方法、装置及系统

Country Status (4)

Country Link
US (1) US20250097313A1 (zh)
EP (1) EP4525490A4 (zh)
CN (1) CN117202135A (zh)
WO (1) WO2023231714A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025222522A1 (zh) * 2024-04-26 2025-10-30 北京小米移动软件有限公司 通信方法、核心网设备、网络节点、网元及系统
WO2025247209A1 (zh) * 2024-05-27 2025-12-04 大唐移动通信设备有限公司 数据服务编排方法、装置及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118803690A (zh) * 2024-02-06 2024-10-18 中国移动通信有限公司研究院 一种数据服务的实现方法、装置、电子设备和存储介质
CN118803668A (zh) * 2024-04-25 2024-10-18 中国移动通信有限公司研究院 通信系统、通信方法及装置
CN120881634A (zh) * 2024-04-29 2025-10-31 大唐移动通信设备有限公司 数据传输方法、装置、设备及存储介质
CN118660284B (zh) * 2024-08-19 2024-12-24 中国电信股份有限公司 通信方法及装置、存储介质及电子设备
CN121644371A (zh) * 2024-09-05 2026-03-10 华为技术有限公司 通信编排方法、装置及计算机程序产品
CN119922215B (zh) * 2025-03-20 2025-08-26 北京融威众邦科技股份有限公司 一种基于ai的医疗自助服务终端

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109314715A (zh) * 2016-07-02 2019-02-05 英特尔公司 用于物联网的资源编排代理
US20200067779A1 (en) * 2018-08-24 2020-02-27 Swisscom Ag Methods and systems for service policy orchestration in a communication network
US20210026614A1 (en) * 2019-07-23 2021-01-28 Paypal, Inc. Container orchestration framework
CN113726843A (zh) * 2021-07-13 2021-11-30 阿里巴巴新加坡控股有限公司 边缘云系统、数据传输方法、设备及存储介质
CN114466005A (zh) * 2020-11-10 2022-05-10 国际商业机器公司 物联网设备编排

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9197522B1 (en) * 2012-03-21 2015-11-24 Emc Corporation Native storage data collection using multiple data collection plug-ins installed in a component separate from data sources of one or more storage area networks
US11416740B2 (en) * 2018-04-13 2022-08-16 Adtran, Inc. Artificial intelligence optimized telecommunications systems
US10965558B2 (en) * 2019-03-30 2021-03-30 Wipro Limited Method and system for effective data collection, aggregation, and analysis in distributed heterogeneous communication network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109314715A (zh) * 2016-07-02 2019-02-05 英特尔公司 用于物联网的资源编排代理
US20200067779A1 (en) * 2018-08-24 2020-02-27 Swisscom Ag Methods and systems for service policy orchestration in a communication network
US20210026614A1 (en) * 2019-07-23 2021-01-28 Paypal, Inc. Container orchestration framework
CN114466005A (zh) * 2020-11-10 2022-05-10 国际商业机器公司 物联网设备编排
CN113726843A (zh) * 2021-07-13 2021-11-30 阿里巴巴新加坡控股有限公司 边缘云系统、数据传输方法、设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "5G Network and Service Management including Orchestration", NGMN THE ENGINE OF BROADBAND WIRELESS INNOVATION., 7 March 2017 (2017-03-07), XP093117194, Retrieved from the Internet <URL:https://ngmn.org/wp-content/uploads/Publications/2017/170307_5G_Network_and_Service_Management__including_Orchestration_2.12.7.pdf> [retrieved on 20240109] *
See also references of EP4525490A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025222522A1 (zh) * 2024-04-26 2025-10-30 北京小米移动软件有限公司 通信方法、核心网设备、网络节点、网元及系统
WO2025247209A1 (zh) * 2024-05-27 2025-12-04 大唐移动通信设备有限公司 数据服务编排方法、装置及存储介质

Also Published As

Publication number Publication date
US20250097313A1 (en) 2025-03-20
EP4525490A1 (en) 2025-03-19
EP4525490A4 (en) 2025-08-13
CN117202135A (zh) 2023-12-08

Similar Documents

Publication Publication Date Title
WO2023231714A1 (zh) 通信方法、装置及系统
US11811873B2 (en) Distribution hub for internet-of-things data
WO2023231770A1 (zh) 通信方法及装置
US20260019879A1 (en) Radio Access Network Architecture and Terminal Apparatus
WO2023231713A1 (zh) 通信方法、装置及系统
US20250267512A1 (en) Communication method, apparatus, and system
US20260107126A1 (en) Relationship entity management systems and methods for telecommunications network user equipment
WO2025059850A1 (zh) 一种网络设备会话管理的通信方法、设备和介质
WO2023169122A1 (zh) 通信方法和装置
CN117580043A (zh) 通信方法及装置
EP4727184A1 (en) Communication method and apparatus
CN118200930B (zh) 一种云计算的数据安全传输方法
CN117580079B (zh) 一种基于网络环境的电力态势感知方法
EP4661503A1 (en) Communication method and device
WO2025103209A1 (zh) 通信方法及装置
CN121890225A (zh) 数据传输方法及通信装置
CN121264081A (zh) 一种通信方法及装置
WO2025209408A1 (zh) 通信方法及装置
CN121643990A (zh) 数据传输方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23814900

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023814900

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 202437098296

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2024137831

Country of ref document: RU

ENP Entry into the national phase

Ref document number: 2023814900

Country of ref document: EP

Effective date: 20241211

NENP Non-entry into the national phase

Ref country code: DE