Data transmission method and device and related equipment

Abstract

The invention provides a data transmission method and device and related equipment, and relates to the technical field of wireless communication, the method is applied to a data service network system, the data service network system comprises a request network element and a collaborative network element, and the method comprises the following steps: responding to a data service task request received by the request network element; obtaining an access token sent by the collaborative network element; and carrying the access token to obtain a data service result corresponding to the data service task request from the collaborative network element. According to the invention, the data service task can be completed by utilizing the mutual cooperation of the data service capabilities among the networks.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies, and in particular to a data transmission method, apparatus, and related equipment. Background Art

[0002] The logical architecture diagram of the existing fifth generation mobile communication technology (5G) network system is as follows: Figure 1 As shown in the figure, it does not include data plane-related network elements and cannot support new scenarios of the sixth generation mobile communication technology (6G) related to future machines, artificial intelligence (AI), and perception data processing. Therefore, it is necessary to add data service-related network elements such as data service orchestration management functions and data processing functions to flexibly support end-to-end unified data collection, global data transmission, processing, storage and sharing through a unified data service architecture, and provide data conveniently, efficiently and securely for use by internal network functions or external network functions.

[0003] In addition, the existing 5G network service architecture is Figure 2 As shown, a two-level network repository function (NRF) is adopted - backbone NRF and provincial NRF. The provincial NRF is responsible for the registration and discovery of control plane network elements within the province, while the backbone NRF is responsible for transferring network element discovery queries and responses between provinces. The user number segments of each province are statically configured in the backbone NRF, which cannot adapt to the dynamic changes of network services in future distributed network networking scenarios. In addition, the current service-oriented architecture only supports the registration and discovery of 5G communication network functions (NF), and is not suitable for the collaboration of data service capabilities in future 6G distributed network networking scenarios.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to ordinary technicians in the field. Summary of the Invention

[0005] The present disclosure provides a data transmission method, apparatus and related equipment, which, at least to a certain extent, overcome the problem that related technologies do not include network elements related to the data plane, cannot support future new 6G scenarios related to machine, AI, and perception data processing, and are not suitable for data service capability collaboration in future 6G distributed network networking scenarios.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a data transmission method is provided, which is applied to a data service network system, wherein the data service network system includes a requesting network element and a collaborative network element, and comprises: obtaining an access token sent by the collaborative network element in response to a data service task request received by the requesting network element; and carrying the access token to obtain a data service result corresponding to the data service task request from the collaborative network element.

[0008] In some exemplary embodiments of the present disclosure, based on the aforementioned scheme, after responding to the data service task request received by the requesting network element, the method also includes: decomposing the task in the data service task request into at least one subtask according to the data service task request received by the requesting network element; determining the collaborative network element corresponding to the at least one decomposed subtask, and the collaborative network element is used to execute the at least one decomposed subtask.

[0009] In some exemplary embodiments of the present disclosure, based on the aforementioned scheme, before determining the collaborative network element corresponding to at least one sub-task after disassembly, the method also includes: the service agent in the requesting network and the service agent in the collaborative network pre-store the configuration information of the network element in the corresponding network and establish an intercommunication link.

[0010] In some exemplary embodiments of the present disclosure, based on the aforementioned scheme, the collaborative network element corresponding to at least one subtask after disassembly is determined, including: mapping at least one subtask after disassembly to configuration information of the corresponding network element; based on the intercommunication link, determining the collaborative network element corresponding to at least one subtask after disassembly according to the configuration information of the network element.

[0011] In some exemplary embodiments of the present disclosure, based on the aforementioned scheme, the service agent in the requesting network and the service agent in the collaborative network pre-store the configuration information of the network elements in the corresponding networks and establish an intercommunication link, including: the service agent in the requesting network pre-stores the configuration information of each network element in the requesting network; generates network-level configuration information based on the configuration information of each network element in the requesting network; the service agent in the collaborative network pre-stores the configuration information of each network element in the collaborative network; generates network-level configuration information based on the configuration information of each network element in the collaborative network; sends the network-level configuration information of the requesting network and the network-level configuration information of the collaborative network to the service agent of the central network for storage, and the service agent of the central network forwards them between networks to realize an intercommunication link between networks.

[0012] In some exemplary embodiments of the present disclosure, based on the aforementioned scheme, after determining the collaborative network element corresponding to at least one subtask after disassembly according to the configuration information of the network element, the method also includes: combining the collaborative network elements corresponding to at least one subtask after disassembly into a complete working chain; and sending the at least one subtask after disassembly to the corresponding collaborative network element in the working chain.

[0013] According to another aspect of the present disclosure, a data transmission device is also provided, which is applied to a data service network system. The data service network system includes a requesting network element and a collaborative network element, including: a data service task request receiving module, which is used to obtain an access token sent by the collaborative network element in response to the data service task request received by the requesting network element; and a data service result acquisition module, which is used to carry the access token to obtain the data service result corresponding to the data service task request from the collaborative network element.

[0014] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any one of the above-mentioned data transmission methods by executing the executable instructions.

[0015] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, any one of the above-mentioned data transmission methods is implemented.

[0016] According to another aspect of the present disclosure, a computer program product is provided, including: a computer program or instructions, wherein when the computer program or instructions are executed by a processor, any one of the above-mentioned data transmission methods is implemented.

[0017] A data transmission method, apparatus and related equipment provided in the embodiments of the present disclosure, for network elements that collaborate across networks, obtains an access token sent by the collaborative network element after the requesting network element receives the data service task request; then, carries the access token to obtain the data service result corresponding to the data service task request from the collaborative network element. Compared with the related technologies that do not include network elements related to the data plane, they cannot support future new 6G scenarios related to machine, AI, and perception data processing, and are not suitable for the collaboration of data service capabilities in future 6G distributed network networking scenarios. The embodiments of the present disclosure not only obtain the corresponding data service result from the collaborative network after receiving the data service task request to collaboratively complete the data service task, but also solve the problem of the network elements of the collaborative network verifying the legitimacy of the cross-network data service collaboration request through access token verification.

[0018] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification, are used to explain the principles of the present disclosure. Obviously, the drawings described below are only some embodiments of the present disclosure, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0020] Figure 1 A schematic diagram of a 5G network architecture in related technologies is shown;

[0021] Figure 2 A schematic diagram of a 5G network service registration and discovery framework in related technologies is shown;

[0022] Figure 3 A schematic diagram of a data transmission method according to an embodiment of the present disclosure is shown;

[0023] Figure 4 A data service network system architecture diagram and corresponding network element schematic diagram according to an embodiment of the present disclosure are shown;

[0024] Figure 5 A schematic diagram of a distributed networking architecture and a service proxy structure in an embodiment of the present disclosure is shown;

[0025] Figure 6 A schematic diagram of intra-network / inter-network data service network element discovery interaction according to an embodiment of the present disclosure is shown;

[0026] Figure 7 A schematic diagram illustrating an intra-network / cross-network data plane function (DPF) / data storage function (DSF) discovery interaction diagram via an enhanced network service storage function (eNRF) is shown in an embodiment of the present disclosure;

[0027] Figure 8 A schematic diagram of network element-level and network-level capability registration and synchronization interaction according to an embodiment of the present disclosure is shown;

[0028] Figure 9 A schematic diagram illustrating registration and synchronization interaction between a network element-level NF / DPF and a network-level capability through an eNRF in an embodiment of the present disclosure is shown;

[0029] Figure 10A schematic diagram of intra-network / inter-network data service network element collaborative interaction according to an embodiment of the present disclosure is shown;

[0030] Figure 11 A schematic diagram of DPF / DSF service call interaction within a network / across networks according to an embodiment of the present disclosure is shown;

[0031] Figure 12 A schematic diagram of a data transmission device according to an embodiment of the present disclosure is shown;

[0032] Figure 13 A schematic diagram of an electronic device to which a data transmission method is applied in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0033] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0034] In addition, the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, well-known methods, devices, implementations or operations are not shown or described in detail to avoid blurring various aspects of the present disclosure.

[0035] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0036] First of all, in response to the above-mentioned problems, the embodiments of the present disclosure combine the enhanced service agent function and the newly added 6G data service function, and propose a data transmission method suitable for the future 6G distributed network architecture. In addition to being responsible for the internal network element-level service configuration registration, the service agent of each network also needs to synchronize the network-level configuration information of the entire network. After receiving the data service task request, the data service management network element first splits the data service task and discovers the data service network element corresponding to its own network / other networks through the network element-level / network-level configuration information of the service agent, and then sends down the data service subtask information to control the orchestrated data service network element to execute the subtask and establish a data transmission pipeline to transmit the processed data. The method in the embodiments of the present disclosure can make full use of the mutual coordination of data service capabilities between distributed networks to complete data service tasks. The embodiments of the present disclosure also solve the legitimacy problem of network elements of collaborative networks verifying cross-network data service collaboration requests through access token verification.

[0037] Figure 3 A schematic diagram of a data transmission method according to an embodiment of the present disclosure is shown. Figure 3 As shown, the data transmission method provided in the embodiment of the present disclosure is applied to a data service network system, the data service network system including a requesting network element and a coordinating network element, and includes the following steps:

[0038] S302 : In response to the data service task request received by the requesting network element, obtain an access token sent by the cooperating network element.

[0039] It should be noted that the network architecture of the data service network system in the embodiment of the present disclosure is as follows: Figure 4As shown, it mainly includes: service exposure function (SEF), connection management function network element (CSMF), data service management network element (DSMF), data plane network element (DPF), data storage network element (DSF), application network element (AF), etc.; in more detail, the network element in the embodiment of the present disclosure can be a network element in any network, wherein the DSMF translates and decomposes the data service demand into a data service task, and selects a specific DPF, DSF and other network element services with different data capabilities by querying its own cache or querying the enhanced network storage function (eNRF), thereby forming an executable UE, radio access network (RAN) and so on. The AF is used to initiate data service requests. The AF cannot directly access network elements within the core network and can only call internal network services through the SEF. Secondly, the requesting network in the embodiment of the present disclosure can be understood as a system or mechanism through which a user sends a request to a central node or service and obtains the corresponding data or service. For example, the requesting network in the embodiment of the present disclosure can be any distributed network. The collaborative network is a network structure in which multiple nodes or entities collaborate and share resources and information. For example, the collaborative network in the embodiment of the present disclosure can be any distributed network or central network that can provide the required data service to the requesting network. In addition, the data service task request in the embodiment of the present disclosure refers to a request sent by one network or application to another network or application service for the purpose of obtaining, processing or managing specific data.

[0040] S304: Carry the access token to obtain the data service result corresponding to the data service task request from the collaborative network element.

[0041] It should be noted that the access token in the embodiment of the present disclosure is a security credential used to verify the identity of a user or application and authorize it to access specific resources. When the requesting network sends a data service task request to the collaborative network, the collaborative network can determine whether the request comes from a legitimate user or application by checking the access token.

[0042] The data transmission method provided in the embodiment of the present disclosure first obtains an access token sent by the collaborative network element in response to the data service task request received by the requesting network element; then, the access token is carried to the collaborative network element to obtain the data service result corresponding to the data service task request. Compared with the related technology that does not include network elements related to the data plane, it cannot support the new 6G scenarios related to future machine, AI, and perception data processing, and is not suitable for the collaboration of data service capabilities in the future 6G distributed network networking scenario. The embodiment of the present disclosure not only obtains the corresponding data service result from the collaborative network after receiving the data service task request to collaboratively complete the data service task, but also solves the problem of the network element of the collaborative network verifying the legitimacy of the cross-network data service collaboration request through access token verification.

[0043] In some embodiments, the disclosed embodiments can call the service of the data service producer network element based on the OAuth2.0 (Open Authorization, an open authorization protocol that allows third-party applications to access HTTP services in a limited manner) token access authorization mechanism for cross-network collaborative network elements, such as data service consumer network elements, data service management network elements, and data service execution network elements. Specifically, the data service consumer network element first applies for an access token from the service agent of the collaborative network, and then carries the access token to initiate sub-task control / data pipeline creation and other requests to the cross-network collaborative producer network element. The producer network element verifies the legitimacy and validity of the access token before processing the request of the cross-network consumer network element.

[0044] In some embodiments, after responding to the data service task request received by the requesting network element, the data transmission method in the embodiment of the present disclosure further includes: decomposing the task in the data service task request into at least one subtask according to the data service task request received by the requesting network element; determining the collaborative network element corresponding to the at least one decomposed subtask, and the collaborative network element is used to execute the at least one decomposed subtask. Specifically, by decomposing the task into multiple subtasks, different subtasks can be executed in parallel on different collaborative network elements, making full use of the computing resources of the distributed data service network system, reducing single-point bottlenecks, and thus significantly improving overall processing efficiency.

[0045] In some embodiments, the disassembly of data service tasks in the embodiments of the present disclosure includes: a translation process and a disassembly process, wherein the translation process is that the data service task request only includes necessary requirement information, such as sensing area requirements, sensing time requirements, sensing data type requirements, and sensing result accuracy requirements. The translation process is to expand the requirement information in the data service task request into a specific data service capability indication list through direct or indirect means, including data collection capabilities, data preprocessing capabilities, data analysis capabilities, data storage capabilities, and open capabilities, and specific information corresponding to each capability. Direct methods include, for example, filling in data collection capability information based on sensing area requirements, sensing time requirements, and sensing data type requirements, including data collection area, collection type, collection duration, and collection reporting interval; filling in data analysis capability information based on sensing result accuracy requirements, indicating the accuracy of the sensing model; indirect methods include, for example, deriving the preprocessing data type and service quality (QoS) required for the preprocessing capability based on the sensing type requirements, sensing accuracy requirements, and sensing time requirements, including data preprocessing methods and data noise filtering quality; and deriving the storage space required for the data storage capability based on the sensing result accuracy requirements.

[0046] In some embodiments, the disassembly process in the embodiments of the present disclosure is to split the data service capability indication list into single or multiple data service capabilities, such as acquisition-preprocessing capability, analysis capability, storage-open capability, etc., thereby splitting the complete data service capability indication list into multiple required data service subtasks.

[0047] In some embodiments, before determining the collaborative network element corresponding to at least one disassembled subtask, the data transmission method in the embodiment of the present disclosure further includes: requesting the service agent in the network and the service agent in the collaborative network to pre-store configuration information of the network element in the corresponding network and establish an intercommunication link. Specifically, the pre-storage of configuration information by the service agent in the embodiment of the present disclosure means that when communication or task execution is actually required, there is no need to temporarily obtain this information, which can significantly reduce the time for initializing connection and configuration, speed up response, and the existence of the intercommunication link ensures that information can be exchanged smoothly between different networks.

[0048] In some embodiments, the distributed networking architecture in the embodiments of the present disclosure is as follows: Figure 5 As shown in the figure, in addition to deploying network elements that meet 5G communication services, each network will also deploy new data service network elements. The service agent eNRF, as the externally exposed endpoint of each participating network, needs to establish communication links on demand for cross-network collaboration. Specific functions include but are not limited to:

[0049] 1) The network element-level configuration registration center is used for service configuration information registration and service discovery within the network. Network element-level services include traditional 5G communication network element services and 6G new data network element services.

[0050] 2) Synchronization of network-level configuration information. The central network's service agent acts as the network-level configuration registration center. The service agents of each distributed network dynamically update their own network-level configuration information based on their own service changes and initiate registration / changes to the central network. The central network then forwards the information to all participating networks.

[0051] 3) Cross-network service discovery: discover and obtain the target network element configuration information of the target collaborative network based on the synchronized network-level configuration information to complete cross-network service collaboration.

[0052] 4) The token access authorization server manages the issuance of data service access tokens, used to verify the legitimacy of external network requests when data services collaborate across networks. The token authorization framework is based on OAuth 2.0, and the token uses the JWT format (a format used to securely transmit information between parties, consisting of three parts: header, payload, and signature).

[0053] In more detail, the configuration information of the 6G data service network element in the embodiments of the present disclosure includes but is not limited to:

[0054] 1) Instance identifier (the identifier carries the network number of the network element, instance type and number, etc.);

[0055] 2) Network element type, such as DSMF, DPF, DSF, eAMF (additional configuration data service collection capability), etc.

[0056] 3) Network element SBI (service-based interface) address information (IP address or fully qualified domain name), used for receiving and sending SBI control signaling;

[0057] 4) Network element service area and scope;

[0058] 5) A list of data service capabilities supported by the network element, such as collection, preprocessing, analysis, and storage. The specific information under each service capability identifier includes but is not limited to: a list of supported processing types, such as supported collection data types (AI data, operation and maintenance data, etc.), supported preprocessing types (filtering, compression, etc.), supported analysis types (mean variance calculation, model training, etc.), supported storage capacity and storage data type, etc.; service QoS, such as perception accuracy and perception service range, compression rate, and model training accuracy, etc.;

[0059] 6) A list of supported data transmission protocol types, such as HTTP, FTP, QUIC, etc., used for establishing data service task pipelines and data transmission.

[0060] In some embodiments, the network-level configuration information in the embodiments of the present disclosure includes but is not limited to:

[0061] 1) Network identification (MCC+MNC+specific number);

[0062] 2) Network type: central network / distributed network;

[0063] 3) Service proxy address information (IP or fully qualified domain name), each network is interconnected through the service proxy;

[0064] 4) Location and coverage information;

[0065] 5) Service capability information exposed on demand: 5G communication network element service list, each service includes the network element type, a list of supported service names and supported service parameters (such as UE number segment, session DNN and service area), etc., excluding privacy information such as instance identifier and SBI address; 6G data network element service list, each service includes the network element type, a list of supported data capabilities (such as collection, preprocessing, analysis, etc.), supported transmission protocols and service area, etc., excluding privacy information such as instance identifier and address.

[0066] In some embodiments, compared with the network element level configuration information, the network level configuration information in the embodiments of the present disclosure has a service exposure service information that only includes necessary information for service discovery parameter matching.

[0067] In some embodiments, the complete information of the data service task in the embodiments of the present disclosure includes but is not limited to:

[0068] 1) Task identification (AF identification + request network identification + task index); It should be noted that the AF identification is used to mark the task demander, the request network identification is used by the data service network element to identify whether the current task-related request is issued by an external network, thereby determining whether token verification is required, and the task index is used by the data service network element to distinguish multiple execution tasks.

[0069] 2) Task type, such as AI model training / inference tasks, perception tasks, etc.

[0070] 3) Service capability list, which is used to indicate the data service types required by data service tasks, such as collection, preprocessing, analysis, storage and external exposure. Each capability may carry additional specific requirement information, such as: Collection capability: collection area range, data type, time and accuracy; Preprocessing capability: preprocessing capability type (such as filtering, data cleaning and compression, etc.), preprocessing QoS such as processing rate, compression rate, etc.; Analysis capability: supported analysis types (simple such as mean and variance, complex such as model training and inference, etc.), analysis QoS such as model training accuracy, etc.; Storage capability: storage capacity, storage data type (preprocessed data and training models, etc.).

[0071] In some embodiments, the data service subtask information in the embodiments of the present disclosure includes but is not limited to:

[0072] 1) Task identification;

[0073] 2) Task type;

[0074] 3) Service capability sublist: one or more capabilities derived from the complete data service information, which are independently executed by each orchestrated network element;

[0075] 4) Basic configuration information of the cooperating adjacent data service network elements, including identification, SBI address information and supported transmission protocols, etc., which are used for control signaling interactions such as data transmission channel establishment negotiation.

[0076] In some embodiments, as Figure 6 As shown, the embodiment of the present disclosure is described by taking a scenario where a data service task requires three data service execution network elements to jointly execute and complete it as an example. Among them, network element 1 is cached in the local data service management network element (such as previously cached through the discovery process), network element 2 is only stored in the local service agent, and network element 3 belongs to the external collaborative network and is stored by the collaborative network service agent. The discovery process of the data service network element during the data service task orchestration and execution process is as follows:

[0077] S602: The data service demand direction requests the data service management network element of the network (eg, distributed network A) to initiate a data service task request.

[0078] S604, requesting the data service management network element of the network to translate and decompose the data service requirement into multiple subtasks, and map them into multiple data service capability discovery parameters, which include service area, data service capability list and supported transmission protocol types.

[0079] S606: The data service management network element can directly query the configuration information of the data service network element 1 in the internal cache according to the discovery parameter 1 for subsequent service orchestration and calling.

[0080] S608: If the data service management network element cannot find the configuration information of data service network elements 2 and 3 in the internal cache according to the discovery parameters 2 and 3, it will initiate discovery requests for service network elements 2 and 3 to the local service agent respectively with the service discovery parameters.

[0081] S610 , the service agent of the requesting network can query the registration configuration information of the data service network element 2 .

[0082] S612: The service agent of the requesting network returns a response to the data service management network element indicating that the data service network element 2 has been successfully discovered, which carries the configuration information of the network element 2.

[0083] S614: Request the data service management network element of the network to cache the configuration information of network element 2 for subsequent service work chain arrangement and calling.

[0084] S616, the service agent of the requesting network cannot directly query the configuration information of data service network element 3, but discovers through synchronized network-level configuration information that the data service network element of the target collaborative network (such as other distributed networks or central networks) meets the requirements, and then chooses to forward the service network element 3 discovery request to the target collaborative network.

[0085] S618: The service agent of the requesting network forwards the discovery request of the serving network element 3 to the service agent of the target cooperative network, and the discovery parameters are additionally added with the requesting network and cooperative network identifiers.

[0086] S620: The service agent of the collaborative network verifies the validity of the cross-network discovery request through the network identifier, and queries the configuration information of the service network element 3 through the discovery parameters.

[0087] S622 , the service agent of the collaborative network returns a response indicating successful discovery of service network element 3 to the service agent of the requesting network, carrying configuration information of network element 3 .

[0088] S624: The service agent of the requesting network forwards the service network element 3 discovery success response to the data service management network element.

[0089] S626 , requesting the data service management network element of the network to cache the configuration information of the data network element 3 for subsequent work chain arrangement and calling.

[0090] S628, the data service management network element of the requesting network learns from the configuration information of network element 3 that data service network element 3 belongs to the collaborative network, and then initiates a request to obtain the access token a of data service network element 3 to the network service agent for subsequent task issuance. The token acquisition request parameters include its own identification, its own network element service type, service network element 3 identification, requesting network identification, collaborative network identification, applied service permissions (data service subtask orchestration control and data service external opening result acquisition), etc.

[0091] S630: The service agent of the requesting network verifies the legitimacy of the access token a obtained by the serving network element 3, and forwards the token acquisition request to the service agent of the collaborative network.

[0092] S632, the service agent of the collaborative network verifies the validity of the access token a acquisition request based on the token acquisition parameters, and encrypts the access token with its own private key. The token includes service permissions, timeout period, etc.

[0093] S634 , the service agent of the collaborative network returns the access token a of the data service network element 3 to the service agent of the requesting network in response, carrying the access token encrypted with the private key.

[0094] S636: Request the service agent of the network to forward the token to obtain the response to the data service management network element.

[0095] S638: Request the data service management network element of the network to cache the access token a of the data service network element 3 for verification when subsequently issuing a task creation request.

[0096] S640: The data service management element of the requesting network replies with a successful data service task creation response, which carries an API open to the outside world for the service result.

[0097] In some embodiments, as Figure 7 As shown, the embodiment of the present disclosure is described by taking the scenario where the data service task requires three DPFs / DSFs to be jointly executed as an example, wherein DPF / DSF 1 is cached in the local DSMF (such as previously cached through the discovery process), DPF / DSF 2 is only stored in the local service eNRF, and DPF / DSF 3 belongs to the external collaborative network and is stored by the eNRF of the collaborative network. The specific discovery process includes the following steps:

[0098] S702: The third-party AF initiates a data service task creation request based on SBI signaling to the SEF of the requesting network according to the configured SEF address port.

[0099] S704: The SEF verifies the legitimacy of the AF and the data service task request and then forwards the data service task creation request to the selected DSMF.

[0100] S706: The DSMF of the requesting network translates and decomposes the data service request into multiple subtasks, and maps them into multiple data service capability discovery parameters (in this embodiment, it is assumed that the mapping is discovery parameter 1 corresponding to DPF / DSF 1, discovery parameter 2 corresponding to DPF / DSF 2, and discovery parameter 3 corresponding to DPF / DSF). The discovery parameters include service area, data service capabilities, and supported transmission protocol types. A detailed description of the translation and decomposition process is provided in "Technical Method and Process 2."

[0101] S708, DSMF can directly query the configuration information of DPF / DSF 1 in the internal cache according to the discovery parameter 1 for subsequent orchestration.

[0102] S710, if the DSMF of the requesting network cannot query the configuration information of DPF 2 and DPF / DSF3 in the internal cache based on discovery parameters 2 and 3, it initiates discovery requests for DPF / DSF 2 and 3 to the local eNRF respectively, and adds discovery parameters 2 and 3 in the SBI message header respectively.

[0103] S712, the eNRF of the requesting network can directly query the configuration information of the local DPF / DSF 2.

[0104] S714: The eNRF of the requesting network returns a DPF / DSF 2 discovery success response to the data service management network element, and the response message body carries DPF / DSF 2 configuration information.

[0105] S716: Request the DSMF of the network to cache DPF / DSF 2 configuration information.

[0106] S718, the eNRF of the requesting network cannot directly query the configuration information of DPF / DSF 3. It finds that the target DPF / DSF 3 is located in the target collaborative network (such as other distributed networks or central networks) through the synchronized network-level configuration information, and then chooses to forward the DPF / DSF 3 discovery request to the target collaborative network.

[0107] S720: The eNRF of the requesting network adds the requesting network and the cooperative network identifiers to the discovery parameter field of the SBI message header of the DPF / DSF 3 discovery request and forwards it to the eNRF of the cooperative network.

[0108] S722 , the eNRF of the collaborative network verifies the validity of the cross-network discovery request through the network identifier, and queries the DPF / DSF 3 configuration information through the discovery parameter 3.

[0109] S724: The eNRF of the cooperative network returns a DPF / DSF 3 discovery success response to the eNRF of the requesting network, carrying the DPF / DSF 3 configuration information.

[0110] S726: The eNRF of the requesting network forwards the DPF / DSF 3 discovery success response to the DSMF.

[0111] S728: Request the DSMF of the network to cache the configuration information of DPF / DSF 3 for subsequent work chain arrangement and calling.

[0112] S730, the requesting network DSMF learns that DPF / DSF 3 belongs to an external collaborative network, and then initiates a request to the eNRF to obtain the access token a of DPF / DSF3 for subsequent service calls. The request parameters include its own identifier, its own network element type, DPF / DSF 3 identifier, requesting network identifier, collaborative network identifier, applied service authority (data service control), etc.

[0113] S732: The eNRF of the requesting network acts as an authorization server to verify the legitimacy of the access token acquisition request client based on the DSMF identifier, and forwards the token acquisition request to the eNRF of the collaborative network.

[0114] S734, the eNRF of the collaborative network verifies the validity of the access token a acquisition request based on the token acquisition parameters, and uses its own private key to encrypt the JSON format token declaration content to form a JWT format access token. The token declaration content includes the actual authorization server (eNRF of the collaborative network) identifier, the client (DSMF of the requesting network) identifier, the resource server (DPF / DSF 3) identifier, the requesting network identifier, the collaborative network identifier, the authorization authority (DSMF subtask control) and the timeout period, etc. It should be noted that the service agents of the requesting network and the collaborative network have mutually verified and established an intercommunication link in the network-level capability registration and synchronization process, which is equivalent to achieving implicit authentication. Therefore, the requesting network verifying the legitimacy of the token acquisition request is equivalent to the collaborative network indirectly verifying the legitimacy of the token acquisition request.

[0115] S736, the eNRF of the collaborative network returns the DPF / DSF 3 access token a to obtain the response to the eNRF of the requesting network, carrying the JWT access token.

[0116] S738: The eNRF of the requesting network forwards the token acquisition response to the DSMF.

[0117] S740: Request the DSMF of the network to cache the access token a of the data service network element 3, which is used to send to the other party for verification when making subsequent task requests.

[0118] S742: The DSMF of the requesting network replies to the SEF with a successful data service task creation response, which carries an API open to the outside world for the service result, and the API address is its own address.

[0119] S744: Request the SEF of the network to replace the API address with its own address to prevent the AF from directly accessing the internal DSMF, and bind the current task identifier with the current DSMF for subsequent addressing.

[0120] S746 , the SEF of the requesting network forwards the task creation response to the third-party AF, carrying the externally open API after the address is replaced.

[0121] In some embodiments, the embodiments of the present disclosure determine the collaborative network element corresponding to at least one subtask after disassembly, including: mapping the at least one subtask after disassembly to the configuration information of the corresponding network element; based on the intercommunication link, determining the collaborative network element corresponding to the at least one subtask after disassembly according to the configuration information of the network element. Specifically, the embodiments of the present disclosure can help balance the load through reasonable subtask allocation and network element configuration, avoid overloading of some nodes and idleness of other nodes, thereby more efficiently using existing network resources. Furthermore, by accurately configuring each network element, it is ensured that different types of traffic can be properly processed according to their priority.

[0122] In some embodiments, the service agent in the requesting network and the service agent in the collaborative network in the embodiments of the present disclosure pre-store the configuration information of the network elements in the corresponding networks and establish an intercommunication link, including: the service agent in the requesting network pre-stores the configuration information of each network element in the requesting network; generates network-level configuration information based on the configuration information of each network element in the requesting network; the service agent in the collaborative network pre-stores the configuration information of each network element in the collaborative network; generates network-level configuration information based on the configuration information of each network element in the collaborative network; sends the network-level configuration information of the requesting network and the network-level configuration information of the collaborative network to the service agent of the central network for storage, and the service agent of the central network forwards them between networks to realize an intercommunication link between networks. Specifically, the service agent of each distributed network in the embodiments of the present disclosure generates / changes its own network-level configuration information based on the registration information of its own communication service class and data service class network elements and registers / updates it to the central network service agent, which forwards it to the entire network by the central network service agent, thereby realizing synchronization of network-level configuration information by service agents across the entire network.

[0123] In some embodiments, the network element level and network level capability registration and synchronization process in the embodiments of the present disclosure is as follows: Figure 8 As shown, the specific steps include:

[0124] S802: 5G communication network elements and 6G data service-related network elements of each distributed network initiate registration with the service agent of this network, carrying their own configuration information.

[0125] S804: The service agent of the distributed network stores the network element level configuration information.

[0126] S806: The service agent of the distributed network generates network-level configuration information based on the network-element-level configuration information registered in the network.

[0127] S808: After the network startup is completed, the service agent of the distributed network initiates network-level configuration information registration to the service agent of the central network.

[0128] S810 , the service agent of the central network and the service agent of the distributed network establish an intercommunication link after mutual authentication, and store network-level configuration information.

[0129] S812: The service agent of the central network notifies the service agents of each distributed network about the service configuration information of other registered networks.

[0130] S814, the service agent of the distributed network stores the network-level configuration information of other networks.

[0131] S816: The service agent of the distributed network initiates mutual authentication based on the service agent address of the other network and establishes an intercommunication link.

[0132] In some embodiments, as Figure 9 As shown, the specific embodiment of the present disclosure regarding registration and synchronization of network element-level NF / DPF and network-level capabilities through eNRF includes the following steps:

[0133] S902: The 5G communication NF and 6G data DSMF / DPF / DSF of each distributed network initiate registration with the eNRF of this network through SBI signaling, carrying their own configuration information.

[0134] S904, the eNRF of the distributed network stores the network element level configuration information of each network element, wherein the network element instance identifier is used as the client ID for the subsequent OAuth2.0 authorization server (eNRF) to verify the legitimacy of the client (the network element as a service consumer).

[0135] S906 , the eNRF of the distributed network generates network-level configuration information based on each registered network element-level configuration information.

[0136] S908, after the network startup is completed, the eNRF of the distributed network initiates network-level configuration information registration to the eNRF of the central network through SBI signaling, carrying the network configuration information and callback URI for subscribing to network-level configuration change notifications of other networks.

[0137] S910: The eNRF of the central network and the eNRF of the distributed network establish an intercommunication link after TLS bidirectional verification, and store network-level configuration information.

[0138] S912, the eNRF of the central network notifies the eNRFs of each distributed network about the service configuration information of other registered networks according to the callback URI provided by each distributed network registration.

[0139] S914, the eNRF of the distributed network parses and stores the network-level configuration information of other networks.

[0140] S916, after the eNRF of the distributed network obtains the SBI address and port information of the service agent of the other network, it performs TLS bidirectional authentication with the service agent of the other network and establishes an intercommunication link, thereby verifying the legitimacy of the peer network.

[0141] In some embodiments, after the embodiment of the present disclosure determines the collaborative network element corresponding to at least one disassembled subtask based on the configuration information of the network element, the data transmission method in the embodiment of the present disclosure further includes: combining the collaborative network elements corresponding to the at least one disassembled subtask into a complete working chain; and sending the at least one disassembled subtask to the corresponding collaborative network element in the working chain. Specifically, after the data service management network element in the embodiment of the present disclosure receives the data service task request from the demander, it breaks the task into subtasks and discovers the corresponding data service execution network element of the network / cross-network through the network element-level / network-level configuration information synchronized by the service agent; after the data service management network element combines the selected execution network elements into a complete working chain, it sends the subtasks to each execution network element, and the execution network element independently processes its own subtask and establishes a data transmission pipeline to transmit the processed data, thereby collaboratively completing the data service task.

[0142] In some embodiments, as Figure 10 As shown, the embodiment of the present disclosure is described by taking the data service orchestration to form a work chain of "data service network element 1 -> data service network element 2 -> data service network element 3" as an example, which specifically includes the following steps:

[0143] S10020: Request the data service management network element of the network to combine the selected data service network elements into a complete working chain.

[0144] S10042: The data service management network element of the requesting network initiates a subtask 1 creation request to data service network element 1 of the same network, carrying subtask 1 configuration information.

[0145] S10062, data service network element 1 parses the configuration information of subtask 1 and creates subtask 1, adding the current data service to-be-processed subtask and network element 2 information.

[0146] S10082: Data service network element 1 returns a response indicating that subtask 1 was successfully created.

[0147] S10044: The data service management network element of the requesting network initiates a subtask 2 creation request to the data service network element 2 of the same network, carrying the subtask 2 configuration information.

[0148] S10064, data service network element 2 parses the configuration information of subtask 2 and creates subtask 2, adding the current data service to-be-processed subtask and network element 3 information.

[0149] S10084, data service network element 2 returns a response indicating that subtask 2 was successfully created.

[0150] S10046: The data service management network element of the requesting network initiates a subtask 3 creation request to the data service network element 3 of the same network, and additionally carries the access token of the data service network element 3 of the cooperative network for authority verification.

[0151] S10066, the data service network element 3 of the collaborative network decrypts the access token using the public key of the network service agent (obtained through pre-configuration or previous service registration process), and verifies that the data service management network element of the requesting network has the authority to create the data service subtask.

[0152] S10086, data service network element 3 of the collaborative network parses the configuration information of subtask 3 and creates subtask 3, and adds the current data service subtask to be processed.

[0153] S10106, the data service network element 3 of the collaborative network returns a response indicating that subtask 3 was successfully created to the data service management network element of the requesting network.

[0154] S10122, the data service network element 1 of the requesting network initiates a data pipe establishment request to the data service network element 2 to negotiate and process the data transmission protocol. The request content must carry the data protocol type supported by itself and service QoS and other parameters.

[0155] S10142: Data service network element 2 selects an appropriate transmission protocol and service QoS based on the data protocol and data service task type supported by both network elements.

[0156] S10162, data service network element 2 returns a data pipe establishment response, which carries the selected transmission protocol and the address port of the protocol for pipe creation.

[0157] S10182: Data service network element 1 and data service network element 2 establish a data transmission pipeline.

[0158] S10124, the data service network element 2 of the requesting network knows that the network element belongs to the collaborative network based on the configuration information of the adjacent collaborative network element 3, and then initiates a request to the service agent to obtain the data service network element 3 access token b. The token acquisition request parameters include its own identification, its own network element type, service network element 3 identification, requesting network identification, collaborative network identification, applied service permissions (data service transmission pipeline establishment), etc.

[0159] S10144: After the service agent of the requesting network verifies the legitimacy of the token acquisition, it forwards the access token b acquisition request of network element 3 to the service agent of the collaborative network.

[0160] S10164, the service agent of the collaborative network verifies the legitimacy of the request to obtain the access token b, and encrypts the access token with its own private key. The token includes service permissions, timeout period, etc.

[0161] S10184, the service agent of the collaborative network returns a token acquisition response to the service agent of the requesting network, carrying the access token b encrypted with the private key.

[0162] S10204: The service agent of the requesting network forwards the access token b to the data service network element 2 of the requesting network to obtain a response.

[0163] S10224, requesting the data service network element 2 of the network to cache the access token b.

[0164] S10244, the data service network element 2 of the requesting network initiates a data pipe establishment request to the data service network element 3 of the collaborative network, carrying the access token b for authority verification.

[0165] S10264, the data service network element 3 of the collaborative network extracts the access token b from the data pipe establishment request and decrypts it using the public key of the service agent to verify that the data service network element 2 of the requesting network has the authority to establish the data pipe.

[0166] S10284: The data service network element 3 of the collaborative network selects an appropriate transmission protocol and service QoS based on the data protocol and data service task type supported by both network elements.

[0167] S10304, the data service network element 3 returns a data pipe establishment response, which carries the selected transmission protocol and the address port of the protocol for pipe creation.

[0168] S10324: Data service network element 2 of the requesting network and data service network element 3 of the collaborative network establish a data transmission pipeline.

[0169] S10340: The data service network elements 1 and 2 of the requesting network and the data service network element 3 of the coordinated network jointly perform the data service task. Each network element independently performs a data service subtask and transmits the processed data.

[0170] S10360: The data service demander obtains the data service result from the service agent of the requesting network through an open API.

[0171] S10382: If the network element open to the outside belongs to the requesting network (such as data service network element 2), the service agent of the requesting network directly obtains the data service result from the network element open to the outside.

[0172] S10384: If the externally open network element belongs to the collaborative network (such as data service network element 3), the service agent of the requesting network carries the access token a to initiate a data service result acquisition request to the data service network element 3.

[0173] S10404, the data service network element 3 decrypts the access token a using the public key to verify that the service agent of the requesting network has the authority to obtain the external opening result.

[0174] S10424, data service network element 3 replies with a data service result acquisition response.

[0175] S10440, requesting the data service agent of the network to reply the data service result to the data service demander.

[0176] In some embodiments, as Figure 11 As shown, the embodiment of the present disclosure is described by taking the data service task arrangement to form a work chain of "DPF / DSF1->DPF / DSF 2->DPF / DSF 3" as an example. The specific process includes the following steps:

[0177] S11020, requesting the data service management network element of the network to combine the selected data service network elements into a complete working chain.

[0178] S11042: The DSMF of the requesting network initiates a subtask 1 creation request based on SBI signaling to the DPF / DSF 1 of the same network, carrying the subtask 1 configuration information.

[0179] S11062, DPF / DSF 1 parses the configuration information of subtask 1 and creates subtask 1, adding the current data service to-be-processed subtask and basic configuration information of DPF / DSF 2.

[0180] S11082, DPF / DSF 1 returns a response indicating that subtask 1 was successfully created.

[0181] S11044: The DSMF of the requesting network initiates a subtask 2 creation request based on SBI signaling to the DPF / DSF 2 of the same network, carrying the subtask 2 configuration information.

[0182] S11064, DPF / DSF 2 parses the configuration information of subtask 2 and creates subtask 2, adding the current data service to-be-processed subtask and basic configuration information of DPF / DSF 3.

[0183] S11084, DPF / DSF 2 returns a response indicating that subtask 2 was successfully created.

[0184] S11104, the DSMF of the requesting network initiates a subtask 3 creation request based on SBI signaling to the DPF / DSF 3 of the collaborative network, and additionally carries the collaborative network identifier. The SBI message header needs to carry the access token a of DPF / DSF 3 for authority verification.

[0185] S11066, the DPF / DSF 3 of the collaborative network extracts the request network identifier from the task identifier of the subtask creation request, thereby identifying that the current data service task is a cross-network task, and thus triggers an additional token verification process: extracting the access token a from the request message header, and decrypting the access token a through the public key of the eNRF (obtained through the registration process exchange) to obtain the access statement a in JSON format; by comparing the request + collaborative network identifier of the access statement a with the request + collaborative network identifier extracted from the request message to see if they are consistent, the legitimacy of the cross-network forwarding is verified, by comparing the service producer identifier of the access statement a with its own identifier to see if they are consistent, the validity of the target network element is verified, by comparing its own service capabilities and the authority of the access statement a, it is verified that it can handle the DSMF dispatching task of the request network, and by verifying through the validity period that the current service authorization period has not been exceeded.

[0186] S11086, DPF / DSF 3 of the collaborative network parses the configuration information of subtask 3 and creates subtask 3, adding the current data service to-be-processed subtask.

[0187] S11106, the DPF / DSF 3 of the cooperative network returns a response indicating that subtask 3 was successfully created to the DSMF of the requesting network.

[0188] S11122: DPF / DSF 1 of the requesting network initiates a data pipe establishment request based on SBI signaling to DPF / DSF 2. The request message body must carry parameters such as the data protocol type supported by itself and service QoS.

[0189] S11142, DPF / DSF 2 selects an appropriate transmission protocol and service QoS based on the data protocols and data service task types supported by both network elements.

[0190] S11162, DPF / DSF 2 returns a data pipe establishment response, which carries the selected transmission protocol and configuration information such as protocol address port and encryption parameters for pipe creation.

[0191] S11182, DPF / DSF 1 establishes a data transmission channel with DPF / DSF 2 according to the data protocol configuration information.

[0192] S11124, the DPF / DSF 2 of the requesting network knows that the network element belongs to the collaborative network based on the configuration information of DPF / DSF 3, and then initiates a request to the eNRF to obtain the access token b of DPF / DSF 3. The token acquisition request parameters include its own identification, its own network element type, DPF / DSF 3 identification, requesting network identification, collaborative network identification, applied service permissions (data service transmission pipeline establishment), etc.

[0193] S11144 , the eNRF of the requesting network acts as the authorization server and verifies the legitimacy of the request to obtain the access token b based on the identifier of DPF / DSF 2 and forwards it to the eNRF of the collaborative network.

[0194] S11164, the collaborative network's eNRF verifies the validity of the access token b acquisition request, and uses its own private key to encrypt the JSON format token declaration content to form a JWT format access token. The token declaration content includes the actual authorization server (collaborative network's eNRF) identifier, the client (DPF / DSF 2 of the requesting network) identifier, the resource server (DPF / DSF 3) identifier, the requesting network identifier, the collaborative network identifier, the authorization authority (data service transmission pipeline establishment) and the timeout period, etc.

[0195] S11184, the eNRF of the collaborative network returns an access token b acquisition response, and the message body carries the access token b in the JWT format.

[0196] S11204: Request the network's eNRF to forward the access token b to obtain a response to DPF / DSF 2.

[0197] S11224, request the network's DPF / DSF 2 to cache access token b.

[0198] S11244, the DPF / DSF 2 of the requesting network initiates a data pipe establishment request based on SBI signaling to the DPF / DSF 3 of the collaborative network. The request message body needs to carry the data protocol type supported by itself and service QoS parameters, and the message header needs to additionally carry an access token b for verification.

[0199] S11264, the DPF / DSF 3 of the collaborative network identifies from the task identifier of the data pipeline establishment request that the current data service pipeline establishment request is a cross-network request, and therefore triggers an additional token verification process: extracting the access token b from the request message header, and decrypting the access token b using the public key of the eNRF to obtain the access statement b in JSON format; DPF / DSF 3 verifies the legitimacy of the cross-network forwarding by comparing the request + collaborative network identifier of the access statement b with the request + collaborative network identifier extracted from the request message, verifies the validity of the target network element by comparing the service producer identifier of the access statement b with its own identifier, verifies that it can establish a data pipeline with DPF / DSF 2 by comparing its own service capabilities with the permissions of the access statement b, and verifies that the service authorization period has not been exceeded through the validity period.

[0200] S11284, DPF / DSF 3 selects an appropriate transmission protocol and service QoS based on the data protocols and data service task types supported by both network elements.

[0201] S11304, DPF / DSF 3 returns a data pipe establishment response, which carries the selected transmission protocol and configuration information such as protocol address port and encryption parameters for pipe creation.

[0202] S11324, DPF / DSF 2 establishes a data transmission channel with DPF / DSF 3 according to the data protocol configuration information.

[0203] S11340, DPF / DSF 1, DPF / DSF 2, and DPF / DSF 3 collaborate to complete data service tasks. Each network element independently processes its own subtask and transmits the processed data through the data pipeline.

[0204] S11360: The third-party AF initiates a data service result acquisition request to the SEF of the requesting network through the data service open API.

[0205] S11380: The SEF of the requesting network maps the task identifier in the API to the target DSMF address and forwards the data service result acquisition request to the DSMF.

[0206] S11402: If the data service result is stored in the requesting network (such as DPF / DSF 2), the data service result is directly obtained from the network element.

[0207] S11404: If the data service result is stored in the collaborative network (such as DPF / DSF 3), the DSMF of the requesting network needs to additionally carry the access token b to obtain the service result from DPF / DSF 3.

[0208] S11424, the DPF / DSF 3 of the collaborative network extracts the access token b and verifies that the DSMF of the requesting network has the authority to obtain the result of the data service opening to the outside world.

[0209] S11444: The DPF / DSF 3 of the cooperative network returns an opening result response to the DSMF of the requesting network.

[0210] S11460: Request the DSMF of the network to forward the external opening result response to the SEF.

[0211] S11480, SEF will ultimately feed back the results of the opening to the outside world to the third-party AF.

[0212] Based on the same inventive concept, the present disclosure also provides a data transmission device, such as the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0213] Figure 12 A schematic diagram of a data transmission device according to an embodiment of the present disclosure is shown. Figure 12 As shown, the device is applied to a data service network system, which includes a requesting network element and a coordinating network element, including:

[0214] The data service task request receiving module 1201 is configured to obtain an access token sent by the collaborative network element in response to the data service task request received by the requesting network element;

[0215] The data service result acquisition module 1202 is configured to carry the access token and acquire the data service result corresponding to the data service task request from the collaborative network element.

[0216] A data transmission device provided in an embodiment of the present disclosure obtains an access token sent by a collaborative network element in response to a data service task request received by a requesting network element through a data service task request receiving module; and obtains a data service result corresponding to the data service task request from a collaborative network element by carrying the access token through a data service result obtaining module. Compared with the related art that does not include network elements related to the data plane, it cannot support new 6G scenarios related to future machine, AI, and perception data processing, and is not suitable for the collaboration of data service capabilities in future 6G distributed network networking scenarios. The embodiment of the present disclosure not only obtains the corresponding data service result from the collaborative network after receiving the data service task request to collaboratively complete the data service task, but also solves the problem of the network elements of the collaborative network verifying the legitimacy of the cross-network data service collaboration request through access token verification.

[0217] In some embodiments, the data transmission device in the embodiments of the present disclosure also includes: a disassembly module, which is used to disassemble the task in the data service task request into at least one subtask according to the data service task request received by the requesting network network element after responding to the data service task request received by the requesting network network element; a subtask execution module, which is used to determine the collaborative network network element corresponding to the at least one disassembled subtask, and the collaborative network network element is used to execute the at least one disassembled subtask.

[0218] In some embodiments, the data transmission device in the embodiments of the present disclosure also includes: a link intercommunication module, which is used to request the service agent in the network and the service agent in the collaborative network to pre-store the configuration information of the network element in the corresponding network and establish an intercommunication link before determining the collaborative network element corresponding to at least one disassembled subtask.

[0219] In some embodiments, the subtask execution module in the embodiment of the present disclosure is also used to map at least one disassembled subtask to the configuration information of the corresponding network element; based on the intercommunication link, the collaborative network element corresponding to the at least one disassembled subtask is determined according to the configuration information of the network element.

[0220] In some embodiments, the link intercommunication module in the embodiments of the present disclosure is further configured to request a service agent in the network to pre-store configuration information of each network element in the requesting network;

[0221] Generate network-level configuration information based on the configuration information of each network element in the requesting network; the service agent in the collaborative network pre-stores the configuration information of each network element in the collaborative network; generate network-level configuration information based on the configuration information of each network element in the collaborative network; send the network-level configuration information of the requesting network and the network-level configuration information of the collaborative network to the service agent of the central network for storage, and the service agent of the central network forwards the information between networks to realize inter-network communication links.

[0222] In some embodiments, the data transmission device in the embodiments of the present disclosure further includes: a work chain combination module, which is used to combine the collaborative network network elements corresponding to at least one disassembled subtask into a complete work chain after determining the collaborative network network elements corresponding to at least one disassembled subtask based on the configuration information of the network element; and a subtask sending module, which is used to send at least one disassembled subtask to the corresponding collaborative network network element in the work chain.

[0223] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods, or program products. Therefore, various aspects of the present disclosure may be implemented in the following forms: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which may be collectively referred to herein as "circuits," "modules," or "systems."

[0224] Based on the same inventive concept, an embodiment of the present disclosure further provides an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any of the aforementioned data transmission methods by executing the executable instructions. Since the principles for solving the problem in this electronic device embodiment are similar to those in the aforementioned method embodiment, the implementation of this electronic device embodiment can refer to the implementation of the aforementioned method embodiment, and any repetitions will not be repeated.

[0225] Refer to the following Figure 13 1300 according to this embodiment of the present disclosure will be described. Figure 13 The electronic device 1300 shown is merely an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0226] like Figure 13 As shown, electronic device 1300 is implemented as a general-purpose computing device. Components of electronic device 1300 may include, but are not limited to, at least one processing unit 1301, at least one storage unit 1302, and a bus 1303 connecting various system components (including storage unit 1302 and processing unit 1301).

[0227] The storage unit stores program codes, which can be executed by the processing unit 1301, so that the processing unit 1301 executes the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification.

[0228] In some embodiments, when the electronic device is used to control, for example, the data transmission method disclosed above, the processing unit 1301 may perform the following steps of the above method embodiment:

[0229] In response to the data service task request received by the requesting network element, the access token sent by the cooperative network element is obtained; and the data service result corresponding to the data service task request is obtained from the cooperative network element by carrying the access token.

[0230] The storage unit 1302 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 13021 and / or a cache memory unit 13022 , and may further include a read-only memory unit (ROM) 7023 .

[0231] The storage unit 1302 may also include a program / utility 13024 having a set (at least one) of program modules 13025, such program modules 13025 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0232] The bus 1303 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0233] Electronic device 1300 may also communicate with one or more external devices 1304 (e.g., a keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 1300, and / or any device that enables electronic device 1300 to communicate with one or more other computing devices (e.g., a router, modem, etc.). Such communication may occur via input / output (I / O) interface 1305. Furthermore, electronic device 1300 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via network adapter 1306. As shown, network adapter 1306 communicates with other modules of electronic device 1300 via bus 1303. It should be understood that, although not shown, other hardware and / or software modules may be used in conjunction with electronic device 1300, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0234] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0235] Based on the same inventive concept, embodiments of the present disclosure further provide a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements any of the aforementioned data transmission methods. Because the principles underlying the problems solved by this computer-readable storage medium embodiment are similar to those of the aforementioned method embodiment, the implementation of this computer-readable storage medium embodiment can be referenced to the implementation of the aforementioned method embodiment, and any repetitions will not be repeated.

[0236] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fibers, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0237] In the present disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0238] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.

[0239] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, and the like, as well as conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0240] Based on the same inventive concept, embodiments of the present disclosure further provide a computer program product, including a computer program or instructions, which, when executed by a processor, implements the data transmission method of any one of the above-mentioned method embodiments. Because the principles for solving the problems of this computer program product embodiment are similar to those of the above-mentioned method embodiments, the implementation of this computer program product embodiment can refer to the implementation of the above-mentioned method embodiments, and any repetitions will not be repeated here.

[0241] It should be noted that although several modules or units of the device for action execution are mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be concretized in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0242] Furthermore, although the steps of the method of the present disclosure are described in a particular order in the accompanying drawings, this does not require or imply that the steps must be performed in this particular order, or that all steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0243] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0244] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the appended claims.

Claims

1. A data transmission method, characterized in that: Applied to a data service network system, the data service network system includes a requesting network element and a coordinating network element, including: In response to the data service task request received by the requesting network element, obtaining an access token sent by the cooperating network element; Carrying the access token, obtain the data service result corresponding to the data service task request from the collaborative network element.

2. The data transmission method according to claim 1, wherein: After responding to the data service task request received by the requesting network element, the method further includes: Decomposing the data service task request received by the requesting network element into at least one subtask; A collaborative network element corresponding to the at least one decomposed subtask is determined, where the collaborative network element is used to execute the at least one decomposed subtask.

3. The data transmission method according to claim 2, wherein: Before determining the collaborative network element corresponding to the at least one decomposed subtask, the method further includes: The service agent in the requesting network and the service agent in the collaborative network pre-store configuration information of network elements in corresponding networks and establish an intercommunication link.

4. The data transmission method according to claim 3, wherein: Determining a collaborative network element corresponding to at least one of the decomposed subtasks includes: At least one of the disassembled subtasks is mapped to configuration information of a corresponding network element; Based on the intercommunication link, a collaborative network element corresponding to the at least one disassembled subtask is determined according to configuration information of the network element.

5. The data transmission method according to claim 3, wherein: The service agent in the requesting network and the service agent in the collaborative network pre-store configuration information of network elements in corresponding networks and establish an intercommunication link, including: The service agent in the requesting network pre-stores configuration information of each network element in the requesting network; Generating network-level configuration information according to configuration information of each network element in the requesting network; The service agent in the collaborative network pre-stores configuration information of each network element in the collaborative network; generating network-level configuration information according to configuration information of each network element in the collaborative network; The network-level configuration information of the requesting network and the network-level configuration information of the cooperative network are sent to the service agent of the central network for storage, and the service agent of the central network forwards the information between networks to realize intercommunication links between networks.

6. The data transmission method according to claim 4, characterized in that After determining the collaborative network element corresponding to the at least one disassembled subtask according to the configuration information of the network element, the method further includes: Combining the collaborative network elements corresponding to at least one of the decomposed subtasks into a complete work chain; The at least one disassembled subtask is sent to a corresponding collaborative network element in the work chain.

7. A data transmission device, characterized in that: Applied to a data service network system, the data service network system includes a requesting network element and a coordinating network element, including: A data service task request receiving module, configured to obtain an access token sent by a collaborative network element in response to a data service task request received by a requesting network element; The data service result acquisition module is used to carry the access token to obtain the data service result corresponding to the data service task request from the collaborative network element.

8. An electronic device, characterized in that: include: processor; as well as a memory for storing executable instructions of the processor; The processor is configured to execute the data transmission method according to any one of claims 1 to 6 by executing the executable instructions.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 6 is implemented.

10. A computer program product comprising: A computer program or instruction, characterized in that when the computer program or instruction is executed by a processor, it implements the data transmission method according to any one of claims 1 to 6.

Images