Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. In the method, a first data node receives a first request message from a service node. The first data node performs a routing information query by means of a routing management node to acquire information of a second data node, and further acquires target data by means of the second data node. In this way, the target data can be transmitted from the second data node to the service node, and the requirement for proximate data access can be supported, thereby resolving the issue of large-scale data being difficult to relay via signaling messages, and meeting the demands for efficient data collection and low-latency data access by service nodes in future communication scenarios.

Description

A communication method and apparatus

[0001] The present application claims priority to the Chinese Patent Application No. 202411121024.2, filed on August 14, 2024, and entitled “A communication method and apparatus”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0003] In the fifth generation (5G) mobile communication system, a unified data layer is defined by the 5G protocol to support access to structured data such as subscription / policy / application data, and corresponding interface specifications are defined to clarify the parameter content transmitted by the interface. For unstructured data that cannot be standardized, an unstructured data storage function (UDSF) function and corresponding service capabilities are defined for unstructured data access.

[0004] In the above communication system, data access is mainly implemented through a service interface, and the amount of data supported by the transmission is limited, which is difficult to meet the demand for large-scale data transmission and the demand for low-latency access to data. SUMMARY

[0005] The present application provides a communication method and apparatus, which can meet the demand for large-scale data transmission and the demand for low-latency access to data.

[0006] In a first aspect, a communication method is provided, which includes: a first data node receiving a first request message from a service node, the first request message being used to request to obtain data. The first data node sends a second request message to a routing management node according to the first request message, the second request message being used to request to obtain a data node supporting access to data. The first data node receives information of a second data node from the routing management node, the second data node supporting access to target data. The first data node sends the target data to the service node, the target data being obtained from the second data node.

[0007] According to the method of the first aspect, the first data node queries routing information through the routing management node to obtain information of the second data node supporting access to the target data, and then obtains the target data through the second data node, so that the transmission of the target data from the second data node to the first data node to the service node can be realized, that is, the data access requirement in proximity can be supported, the problem that large-scale data is difficult to transfer through signaling messages can be solved, and the low-latency access requirement of the service node for data can be met.

[0008] Optionally, the first request message can include a first data index and / or a first data feature, the first data index points to the target data, and the feature of the target data matches the first data feature. The first data index can be data index information delivered based on a service interface, that is, routing information, which is obtained by the service node in advance based on business interaction. The first data feature can be feature information of the target data, which is used to indicate the feature of the target data required by the service node. The service node can obtain the target data matching the first data index and / or the first data feature through the first request message, so as to complete the data access requirement in proximity.

[0009] Optionally, the second request message can include a second data index and / or a second data feature, the second data index points to the target data, and the feature of the target data matches the second data feature. The second data index is the same as or different from the first data index, and the second data feature is the same as or different from the first data feature. It should be understood that, in the case that the first request message does not include the first data index, the second request message can include the second data index. The first data node can construct the second data index according to the first data feature, and can also complete / update the first data feature to obtain the second data feature. In this way, the first data node queries the data node (such as the second data node) matching the second data index and / or the second data feature from the routing management node, and the second data index and / or the second data feature can be more complete than the first data index and / or the first data feature, so that more accurate information of the data node (such as the second data node) can be obtained.

[0010] Optionally, the routing management node has a metadata management capability, and the metadata includes a first mapping relationship and / or a second mapping relationship. The first mapping relationship is a mapping relationship between at least one data index and at least one data node, the at least one data index includes the second data index, and the at least one data node includes the second data node. The second mapping relationship is a mapping relationship between at least one data feature and at least one data node, the at least one data feature includes the second data feature, and the at least one data node includes the second data node.

[0011] The metadata management capability herein includes a routing management function, i.e., a function of managing the first mapping relationship. The first mapping relationship can be a mapping relationship between the data index (the at least one data index) in the domain and the data node (the at least one data node). The metadata management capability also includes a capability of managing a second mapping relationship, i.e., a capability of managing a mapping relationship between the metadata feature (the at least one data feature) and the data node (the at least one data node). In this way, the metadata management capability of the routing management node provides the first data node with accurate routing query capability, i.e., improves the accuracy of determining the second data node.

[0012] Optionally, the routing management node can also maintain capability information of the data nodes for the data transmission index to support addressing of the target node meeting the requirement.

[0013] Optionally, if the second request message includes the second data index, the second data node is determined according to the second data index and the first mapping relationship; and if the second request message includes the second data feature, the second data node is determined according to the second data feature and the second mapping relationship. That is, if the second request message includes the second data index, the routing management node determines the second data node corresponding to the second data index from the first mapping relationship; and if the second request message includes the second data feature, the routing management node determines the second data node corresponding to the second data feature from the second mapping relationship.

[0014] Optionally, if the second request message includes the second data index and the second data feature, the second data node is determined according to the second data index and the first mapping relationship, and the second data feature and the second mapping relationship.

[0015] In this way, the second data node is determined according to different contents in the second request message, improving the flexibility of determining the second data node.

[0016] Optionally, the routing management node has a capability of managing a topology relationship and transmission capability information. The topology relationship indicates an adjacency relationship between the first data node, the second data node, and a third data node. The third data node is one or more data nodes through which the target data is transmitted between the first data node and the second data node. The topology relationship is used to determine the second data node and the third data node. The transmission capability information indicates transmission capability of at least one data node, and is used to establish a channel for transmitting the target data. The at least one data node includes the second data node.

[0017] It can be understood that the topological relationship is used to determine the second data node and the third data node, i.e., to determine the channel for transmitting the target data. The transmission capability information may, for example, include bandwidth capacity, scheduling capability, resource utilization, reverse channel capability, etc. of each of the at least one data node. The transmission capability information is used to establish the channel for transmitting the target data, so that the transmission capability information of the second data node determined by the routing management node meets the requirement. In addition, the transmission capability information of the nodes involved in the channel for transmitting the target data by the first data node, the third data node, etc. also needs to meet the requirement.

[0018] In a possible implementation, before the first data node transmits the target data to the service node, the communication method can further include: the first data node sends a third request message to the second data node, the third request message being used to request data and / or to request establishment of a channel for transmitting the data; and the first data node receives the target data from the second data node.

[0019] Optionally, the channel can include a relay channel and / or an update channel; the relay channel is used for transmitting the target data between the second data node and the first data node; and the update channel is used for transmitting the updated target data between the second data node and the first data node.

[0020] It can be understood that the relay channel and / or the update channel are established after the second data node receives the third request message and performs the data access permission. The relay channel is used for transmitting the target data from the second data node to the first data node after being established, and the update channel is used for transmitting the updated target data between the service node, the first data node and the second data node after the target data is updated by the service node. The target data can be transmitted through the relay channel and / or the update channel, so as to meet the requirement of large-scale data transmission and low-latency access to the data.

[0021] Optionally, the channel includes a relay channel and / or an update channel; the relay channel is used for transmitting the target data between the data storage node, the second data node and the first data node, wherein the data storage node stores the target data; and the update channel is used for transmitting the updated target data between the data storage node, the second data node and the first data node.

[0022] It can be understood that the target data can be stored in the data storage node instead of the second data node, so that the second data node performs the data access permission verification after receiving the third request message, and requests the establishment of the relay channel and / or the update channel to the backend data storage node after the verification is passed, so as to establish the relay channel and / or the update channel between the data storage node, the second data node and the first data node. The target data can be transmitted through the relay channel and / or the update channel, so as to meet the requirement of large-scale data transmission and low-latency access to the data.

[0023] Optionally, in the case that the first request message comprises the requirement parameter, the third request message further comprises the requirement parameter, the requirement parameter being used for providing guarantee for transmission of the target data, or being used for establishing a channel for transmitting the target data; the requirement parameter comprises at least one of the following: a transmission delay, a bandwidth, a time window, a service level agreement (SLA) or first indication information, the first indication information being used for indicating that the service node updates the target data.

[0024] That is, when the target data is transmitted between the first data node and the second data node, the requirement parameter needs to be met, or in other words, the channel for transmitting the target data between the first data node and the second data node meets the requirement parameter, thereby improving the transmission performance.

[0025] Optionally, in the case that the requirement parameter comprises the first indication information, the communication method can further comprise: the first data node receives receiving address information from the second data node, the receiving address information indicating that the first data node transmits the updated target data. The first data node can determine the transmission destination address of the updated target data through the receiving address information, so as to ensure that the transmission of the updated target data can be realized.

[0026] The receiving address information of the second data node can further comprise time effectiveness information of the address of the second data node, or the first data node receives the address time effectiveness information from the second data node, so as to indicate that the first data node completes the transmission of the updated target data before the address of the second data node is invalid.

[0027] In a possible implementation, the third request message comprises information of a third data node, the third data node being one or more data nodes through which the target data is transmitted between the first data node and the second data node. Optionally, the routing management node determines the third data node according to the at least one of the following: the first mapping relationship, the second mapping relationship, the topology relationship or the transmission capability information, and sends the information of the third data node to the first data node, and correspondingly, the first data node receives the information of the third data node from the routing management node.

[0028] Optionally, the channel can comprise a transit channel and / or an update channel; the transit channel being used for transmitting the target data between the second data node, the third data node and the first data node; the update channel being used for transmitting the updated target data between the first data node, the third data node and the second data node.

[0029] Optionally, the channel includes a transfer channel and / or an update channel; the transfer channel is used for transmitting the target data between the data storage node, the second data node, the third data node and the first data node, wherein the data storage node stores the target data; the update channel is used for transmitting the updated target data between the first data node, the third data node, the second data node and the data storage node.

[0030] Optionally, the third request message can include identification information of the channel. The identification information of the channel is used to identify the channel, or in other words, to identify the transmission path of the target data.

[0031] Optionally, the first data node sending the third request message to the second data node can include: the first data node sending the third request message to the second data node through the third data node.

[0032] It can be understood that the above process of the routing management node determining the second data node and the third data node, that is, the process of determining the channel / path of transmitting data, or in other words, the data orchestration process. The third request message can be sent through the third data node to achieve hop-by-hop channel establishment. The third request message can include information of the third data node, and the third data node performs resource reservation / channel establishment based on the third request message.

[0033] In a possible implementation, the second request message does not include the second data index and includes the second data feature; the communication method can further include: the first data node receiving second indication information from the routing management node, the second indication information being used to indicate that data matching the second data feature is not collected.

[0034] It can be understood that in the case that the second request message does not include the second data index and includes the second data feature, there can be a case that the target data is not collected. At this time, the routing management node indicates to the first data node that data matching the second data feature is not collected, and sends the second data node to the first data node, at this time, the second data node is a node that does not collect data matching the second data feature and can collect data matching the second data feature. The embodiment of the present application provides a way of collecting data matching the second data feature through the second data node in the case that data matching the second data feature is not collected, so as to obtain the target data.

[0035] In a second aspect, a communication method is provided. The method comprises: sending, by a service node, a first request message to a first data node, the first request message being used to request data, the first request message comprising a first data index and / or a first data feature; and receiving, by the service node, target data from the first data node, the target data being obtained from a second data node according to the first data index and / or the first data feature, the second data node supporting access to the target data, the first data index pointing to the target data, and the target data matching the first data feature.

[0036] It can be understood that the technical effects of the method of the second aspect described above can also be referred to the above-mentioned first aspect, which will not be repeated here.

[0037] In a third aspect, a communication method is provided. The method comprises: receiving, by a routing management node, a second request message from a first data node, the second request message being used to request a data node supporting access to data, the second request message comprising a second data index and / or a second data feature; and sending, by the routing management node, information of a second data node to the first data node, the second data node supporting access to target data, the second data index pointing to the target data, and the target data matching the second data feature.

[0038] In a possible implementation, the method further comprises: receiving, by the routing management node, a registration request from at least one data node, the registration request being used to register at least one of the following: a first mapping relationship, a second mapping relationship, a topology relationship, or transmission capability information.

[0039] The first mapping relationship is a mapping relationship between at least one data index and at least one data node, the at least one data index comprising the second data index, and the at least one data node comprising the second data node; the second mapping relationship is a mapping relationship between at least one data feature and at least one data node, the at least one data feature comprising the second data feature, and the at least one data node comprising the second data node; the topology relationship indicates an adjacency relationship between the first data node, the second data node, and a third data node, the third data node being one or more data nodes passed through when the first data node and the second data node transmit data, and the topology relationship being used to determine the second data node and the third data node; and the transmission capability information indicates transmission capability of the at least one data node, and is used to establish a channel for transmitting data.

[0040] Optionally, before the routing management node sends the information of the second data node to the first data node, the method further comprises: determining, by the routing management node, the information of the second data node according to at least one of the following: the first data index, the first data feature, the second data index, the second data feature, the topology relationship, and the transmission capability information.

[0041] Optionally, the method further includes: the routing management node determining the information of the third data node based on at least one of the following: the routing management node sending the information of the third data node to the first data node.

[0042] Optionally, the second request message may also include requirement parameters, which are used to ensure data transmission or to establish a channel for data transmission; the routing management node determines the information of the third data node based on at least one of the following, which may include: the routing management node determines the information of the third data node based on at least one of the following and the requirement parameters; the requirement parameters include at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, the first indication information being used to instruct the service node to update the target data.

[0043] In one possible implementation, the second request message does not include the first data index but includes the first data feature; the method further includes: the routing management node sending a first indication message to the first data node, the first indication message being used to indicate that data matching the first data feature has not been collected.

[0044] It is understandable that the technical effects of the method in the third aspect mentioned above can also be referred to the relevant introduction in the first aspect mentioned above, and will not be repeated here.

[0045] Fourthly, a communication method is provided, comprising: a second data node receiving a third request message from a first data node, the third request message being used to request data; the second data node acquiring target data and sending the target data to the first data node.

[0046] In one possible implementation, the third request message may include the second data feature; the second data node acquiring the target data may include: the second data node sending a fourth request message to the data production node based on the third request message, the fourth request message being used to request data collection, wherein the data production node is associated with the second data feature. The second data node then receives the target data.

[0047] It is understandable that if the second data node does not collect data, it is necessary to collect data from the data production node that is related to the second data feature, such as the data produced by the data production node that is related to the second data feature.

[0048] Optionally, the fourth request message includes the receiving address of the second data node and / or the receiving address of the data storage node; if the fourth request message includes the receiving address of the second data node, the target data comes from the data production node; if the fourth request message includes the receiving address of the data storage node, the target data comes from the data storage node.

[0049] The fourth request message includes the index allocated by the second data node for the target data.

[0050] In another possible implementation, before the second data node acquires the target data according to the first data feature, the method further includes: receiving, by the second data node, a fifth request message from the data production node, the fifth request message being used to request registration of the target data; and sending, by the second data node, a response message to the data production node, the response message indicating that the target data is successfully registered, the response message including an index allocated to the target data by the second data node, the index allocated to the target data including the first data index.

[0051] Optionally, the method further includes: sending, by the second data node, the target data and the index allocated to the target data to the data storage node.

[0052] Optionally, the method further includes: sending, by the second data node, a sixth request message to the data storage node, the sixth request message being used to request establishment of a channel for transmitting the target data; and receiving, by the second data node, the target data from the data storage node through the channel.

[0053] It can be understood that the technical effects of the method of the fourth aspect described above can also be referred to the above-mentioned first aspect, and will not be repeated here.

[0054] In a fifth aspect, a communication apparatus is provided. The communication apparatus includes a processor configured to perform the method in any one of the first aspect to the fourth aspect.

[0055] In a possible implementation, the communication apparatus of the fifth aspect can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus of the fifth aspect to communicate with other communication apparatuses.

[0056] In a possible implementation, the communication apparatus of the fifth aspect can further include a memory. The memory can be integrated with the processor, or can be separately arranged. The memory can be configured to store a computer program and / or data related to the method in any one of the first aspect to the fourth aspect.

[0057] In addition, the technical effects of the communication apparatus of the fifth aspect can be referred to the technical effects of any one of the first aspect to the fourth aspect, and will not be repeated here.

[0058] In a sixth aspect, a communication apparatus is provided. The communication apparatus includes a processor coupled to a memory, and the processor is configured to execute a computer program or instructions stored in the memory, so that the communication apparatus performs the method in any one of the first aspect to the fourth aspect.

[0059] In a possible implementation, the communication apparatus further includes a transceiver. The transceiver can be a transceiving circuit or an interface circuit. The transceiver can be used for the communication apparatus to communicate with other communication apparatuses.

[0060] In a possible implementation, the communication apparatus further includes the memory for storing the computer program or the instructions. Optionally, the memory and the processor are integrated together.

[0061] In addition, the technical effects of the communication apparatus of the sixth aspect can refer to the technical effects of any of the embodiments of the first aspect to the fourth aspect, which will not be repeated here.

[0062] In a seventh aspect, a communication system is provided. The communication system includes a first data node, a service node, a route management node, and a second data node. The first data node is configured to perform the method of any of the embodiments of the first aspect. The service node is configured to perform the method of any of the embodiments of the second aspect. The route management node is configured to perform the method of any of the embodiments of the third aspect. The second data node is configured to perform the method of any of the embodiments of the fourth aspect.

[0063] In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions. When the computer program or instructions are executed, the method of any of the embodiments of the first aspect to the fourth aspect is implemented.

[0064] In a ninth aspect, a computer program product is provided. The computer program product includes a computer program or instructions. When the computer program or instructions are executed, the method of any of the embodiments of the first aspect to the fourth aspect is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0065] FIG. 1 is a schematic diagram of a network architecture of 5G;

[0066] FIG. 2 is a schematic diagram of a unified data layer of 5G;

[0067] FIG. 3 is a schematic diagram of an intelligent analysis architecture;

[0068] FIG. 4 is a schematic diagram of a vision for future communication scenarios;

[0069] FIG. 5 is a schematic diagram of an architecture of a communication system to which a method provided by an embodiment of the present application is applied;

[0070] FIG. 6 is a schematic diagram of an architecture of a communication system to which a method provided by an embodiment of the present application is applied;

[0071] FIG. 7 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0072] FIG. 8 is a schematic diagram of a channel for transmitting data provided by an embodiment of the present application;

[0073] FIG. 9 is a schematic diagram of data link arrangement provided by an embodiment of the present application;

[0074] FIG. 10 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0075] FIG. 11 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0076] FIG. 12 is a schematic diagram of a structure of a communication apparatus provided by an embodiment of the present application;

[0077] FIG. 13 is a schematic diagram of a structure of a communication apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0078] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a Wireless Fidelity (Wi-Fi) system, a vehicle to everything (V2X) communication system, a device-to-device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system such as a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system.

[0079] For the convenience of understanding, the technical terms involved in the embodiments of the present application are introduced first.

[0080] 1. 5G network networking architecture:

[0081] FIG. 1 is a schematic diagram of a network architecture of 5G. As shown in FIG. 1, the architecture mainly includes an access network (AN) and a CN (not shown in FIG. 1), and can also include a terminal. The main functions of the network elements of the architecture are described as follows:

[0082] The terminal can be one or more. The terminal can be a terminal having a transceiver function, or can also be a chip or chip system provided in the terminal. The terminal can also be referred to as a UE, an access terminal, a subscriber unit, a user station, a mobile station (MS), a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user equipment. The terminal in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a Pad, a wireless data card, a personal digital assistant (PDA), a wireless modem, a handset, a laptop computer, a machine type communication (MTC) terminal, a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart home device (for example, a refrigerator, a television, an air conditioner, an electricity meter, etc.), a smart robot, a mechanical arm, a plant device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a vehicle-mounted terminal, a roadside unit (RSU) with a terminal function, etc., a flight device (for example, a smart robot, a hot air balloon, a drone, an airplane), etc. The terminal of the present application can also be a vehicle-mounted module, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions, for example, the terminal device can also be a device with terminal functions in D2D communication.

[0083] The embodiments of the present application do not limit the device form of the terminal, and the device for realizing the function of the terminal device can be a terminal device; it can also be a device capable of supporting the terminal device to realize the function, such as a chip system. The device can be installed in the terminal device or used in matching with the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0084] The AN is used to implement access-related functions, can provide network access functions for authorized users in a specific area, and can determine transmission links of different qualities to transmit user data according to the level of a user, the demand of a service, and the like. The AN forwards control signals and user data between a terminal and a CN. The AN can include an access network device, which can also be referred to as a radio access network (RAN) device. The CN is mainly responsible for maintaining subscription data of a mobile network, and provides a terminal with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: a user plane function (UPF) network element, an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a network slice selection function (NSSF) network element, a network exposure function (NEF) network element, a network function repository function (NRF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a unified data repository (UDR), and an application function (AF).

[0085] The RAN device, i.e., the access network device, can be one or more. The access network device can be a device with wireless transceiver function, or can also be a chip or chip system arranged in the device, located in the access network (AN) of the communication system, and used to provide access services for terminals. For example, the access network device can be referred to as a radio access network (RAN) device, and can be a future mobile communication system, or in the future mobile communication system, the access network device can also have other naming ways, which are all included in the protection scope of the embodiments of the present application, and the present application does not make any limitation on this. Or, the access network device can also include the gNB in the new radio (NR) system of 5G, or one or a group (including multiple antenna panels) of antenna panels of the base station in 5G, or can also be a network node constituting the gNB, transmission and reception point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (transmission measurement function, TMF), such as a centralized unit (central unit, CU), a distributed unit (distributed unit, DU), a CU-control plane (control plane, CP), a CU-user plane (user plane, UP), or a radio unit (radio unit, RU), an RSU with base station function, or a wired access gateway, or a core network element of 5G, etc. Or, the access network device can also include an access point (access point, AP) in a wireless fidelity (wireless fidelity, WiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, etc.

[0086] The CU and the DU can be separately arranged, or can also be included in the same network element, such as a baseband unit (baseband unit, BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (remote radio unit, RRU), an active antenna unit (active antenna unit, AAU) or a remote radio head (remote radio head, RRH). It can be understood that the network device can be a CU node, or a DU node, or a device including the CU node and the DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the core network CN, which is not limited here.

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

[0088] The UPF network element is mainly responsible for user data processing (forwarding, receiving, charging, etc.). For example, the UPF network element can receive user data from a data network (DN), and forward the user data to a terminal through an access network device. The UPF network element can also receive user data from the terminal through the access network device, and forward the user data to the DN. The DN network element refers to an operator network that provides data transmission services for users. For example, internet protocol (IP) multi-media service (IMS), Internet, etc. The DN can be an operator external network or an operator controlled network, which is used to provide service services to terminal devices.

[0089] The AUSF network element is mainly used to perform security authentication of the terminal.

[0090] The AMF network element is mainly used for mobility management in a mobile network. For example, user location update, user registration network, user handover, etc.

[0091] The SMF network element is mainly used for session management in a mobile network. For example, session establishment, modification, release. Functions such as allocating IP addresses for users, selecting UPF network elements that provide packet forwarding functions, etc.

[0092] The PCF network element mainly supports providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and being responsible for obtaining user subscription information related to policy decision. The PCF network element can provide policies, such as quality of service (QoS) policies, slice selection policies, and the like, to the AMF network element and the SMF network element. In this architecture, the PCF connected to the AMF and the SMF is respectively the PCF for access and mobility control (AM PCF) and the PCF for session management (SM PCF), which may not be the same PCF entity in actual deployment scenarios.

[0093] The NSSF network element is mainly used for selecting network slices for terminals.

[0094] The NEF network element is mainly used for supporting the opening of capabilities and events.

[0095] The UDM network element is mainly used for storing user data, such as subscription data, authentication / authorization data, and the like.

[0096] The UDR network element is mainly used for storing structured data, and the stored content includes subscription data and policy data, externally exposed structured data, and application-related data.

[0097] The AF mainly supports interaction with the CN to provide services, such as affecting data routing decisions, policy control functions, or providing some services of third parties to the network side. Optionally, the AF can provide a personal identification number (PIN) service, which can also be referred to as a PIN-AF. The AF is also used to deliver the requirements of the application side to the network side, such as QoS requirements or user state event subscriptions. The AF can be a third-party functional entity or an application service deployed by an operator, such as an IMS voice call service. For the application function entity of the third-party application, when it interacts with the core network, it can also be authorized by the NEF, for example, the third-party application function directly sends a request message to the NEF, the NEF judges whether the AF is allowed to send the request message, and if the verification is passed, the request message is forwarded to the corresponding PCF or UDM.

[0098] The functions of the interfaces in the architecture are described as follows:

[0099] N7: interface between PCF and SMF, used for issuing protocol data unit (PDU) session granularity and service data flow granularity control policies. Among them, the PDU session is a session service used for realizing PDU connectivity between the UE and the data network, identified by PDU session identity (session ID) information.

[0100] N15: interface between PCF and AMF, used for issuing UE policies and access control related policies.

[0101] N5: interface between AF and PCF, used for application service request issuance and network event reporting.

[0102] N4: interface between SMF and UPF, used for transferring information between the control plane and the user plane, including the issuance of control plane forwarding rules, QoS control rules, traffic statistics rules, and the reporting of user plane information.

[0103] N11: interface between SMF and AMF, used for transferring PDU session tunnel information between the RAN and the UPF, transferring control messages sent to the UE, and transferring radio resource control information sent to the RAN.

[0104] N2: interface between AMF and RAN, used for transferring radio bearer control information from the core network side to the RAN, etc.

[0105] N1: interface between AMF and UE, access independent, used for transferring QoS control rules to the UE, etc.

[0106] N8: interface between AMF and UDM, used for AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information to UDM, etc.

[0107] N10: interface between SMF and UDM, used for SMF to obtain session management related subscription data from UDM, and SMF to register UE current session related information to UDM, etc.

[0108] N35: interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.

[0109] N36: interface between PCF and UDR, used for PCF to obtain policy related subscription data and application data related information from UDR.

[0110] N52: interface between UDM and NEF, used for NEF to open network capabilities to third-party application functions, such as third-party application functions subscribing to reachability events of all users in a specific group through NEF to UDM.

[0111] In addition, the NEF also has a direct interface with the AMF and the SMF, corresponding to the N29 interface and the N51 interface (not shown in FIG. 1) respectively, for opening operator network capabilities to third-party application function entities, the former can be used for NEF to directly subscribe to the AMF for corresponding network events and update user configuration information, and the latter can be used to update application configuration data on the SMF / UPF, such as packet flow description (PFD) information corresponding to the application ID.

[0112] The general user registration process can be simply described as follows: the UE sends a registration request to the AMF through the AN, the AMF obtains the subscription data from the specific UDM according to the user identifier, and the UDM obtains the actual subscription data from the UDR after receiving the request. In addition, the AMF can also initiate a user policy control establishment request (UEPolicyControl_Create) and an access management policy control establishment request (AMPolicyControl_Create) to the PCF, respectively, for obtaining the UE policy and the access control policy. The PCF returns the access control policy to the AMF in this process, and provides the UE policy to the UE through the AMF.

[0113] The general session establishment process can be simply described as follows: the UE sends a session establishment request to the AMF through the RAN, the AMF selects the SMF to provide services for the session, saves the correspondence between the SMF and the PDU session, and sends the session establishment request to the SMF, the SMF selects the corresponding UPF for the UE and establishes the user plane transmission path, and allocates an IP address for it. In this process, the SMF also initiates a policy control session establishment request to the PCF, for establishing a policy control session between the SMF and the PCF, and the SMF saves the correspondence between the policy control session and the PDU session in the policy control session establishment process. In addition, the AF can also establish an AF session with the PCF, and the PCF binds the AF session with the policy control session.

[0114] It should be noted that the present application takes the 5G system as an example to introduce the related technical solutions, but the application of the related technical solutions is not limited to the 5G system. It can be understood that the related technical solutions can also be applied to future communication systems.

[0115] 2. Data node

[0116] Figure 2 is a schematic diagram of a 5G unified data layer. As shown in Figure 2, the 5G protocol defines a unified data layer to support access to subscription data, policy data, structured development data, application data, and the like, and defines corresponding interface specifications to specify the parameter content transmitted by the interface. As shown in Figure 2, the UDM function element (FE), the PCF FE, and the NEF FE implement data access to the data access provider in the UDR network element through the Nudr interface. For unstructured data that cannot be standardized, a UDSF function and corresponding service capability are defined for unstructured data access. As shown in Figure 2, any network functions (any NF) implement data access to the UDSF network element through the Nudsf interface.

[0117] Among them, the subscription data is the static subscription data of the user, corresponding to the user subscription saved by the UDM / UDR. The policy data is the user policy subscription data, including the UE / AM / SM policy subscription, the structured open data is the dynamic data (structured data) that needs to be opened. The application data is the application related data, such as user plane routing information, application description information, etc.

[0118] The above data access is mainly implemented through the two service interfaces of Nudr / Nudsf, and the required data transmission amount is relatively limited, usually only several KB to several tens of KB.

[0119] In addition to the above data, the 5G network introduces a network data analytics function (NWDAF) network element for intelligent analysis capability, and defines a corresponding data collection mechanism for analysis inference / model training requirements.

[0120] Figure 3 is a schematic diagram of an intelligent analysis architecture. As shown in Figure 3, the node functions are briefly described as follows:

[0121] The analytics data repository function (ADRF) network element has a data storage function, and is used to store collected raw data, analysis result data, and models.

[0122] The data collection coordination function (DCCF) network element is used to collect and open data uniformly.

[0123] The messaging framework adaptor function (MFAF) is a message bus for messaging.

[0124] The model training logical function (MTLF) is a model training function.

[0125] The analytics logical function (AnLF) is a data analytics function for obtaining a model from the MTLF. The NWDAF can provide a machine learning (ML) model provisioning (Nnwdaf_MLModelProvision) service.

[0126] In this scenario, based on the idea of separating services and data, an independent data storage and exchange framework is defined to provide services for upper-layer services (i.e., the NF nodes in FIG. 3) to achieve unified data collection and opening. In addition, the model training and data analysis functions are also functionally split.

[0127] However, in this architecture, in addition to the non-standardized interface between the messaging framework and the data source for data collection, the interface provided by the MFAF to the upper layer is still a service interface, which is difficult to meet the large-scale data transmission demand.

[0128] 3. Analysis of future data function requirements

[0129] Future communication scenarios can be extended on the basis of the original 5G communication scenarios, such as the introduction of AI+ communication, ubiquitous connection, and communication perception integration capabilities.

[0130] FIG. 4 is a schematic diagram of a vision for future communication scenarios. As shown in FIG. 4, for future communication scenarios, immersive communication, artificial intelligence plus (AI+) communication, ultra-reliable low-latency communication, ubiquitous connection, massive communication, and communication perception integration capabilities need to be introduced.

[0131] For the communication perception scenario, taking point cloud data reporting as an example, the bandwidth required for the point cloud data reported by a single base station for a single target is about several Mbps, and if multiple targets are involved, the bandwidth will also be multiplied by a certain proportion. This bandwidth requirement far exceeds the capability (about several Kbps) that can be provided by the signaling messages of the existing service interface.

[0132] For the network digital twin scene, taking the digital experience map as an example, key indicators need to be obtained from each base station / UPF, and the data scale is expected to be about ten million levels, which needs to support second-level query delay, graph data storage, and the data collection bandwidth demand generated will far exceed the capacity that the existing network can provide.

[0133] For the immersive communication scene, the network side needs to maintain a personalized intelligent assistant at the user granularity, and needs to meet the access of corresponding long-term memory and short-term memory data, wherein the short-term memory is about several MB to tens of MB, and the long-term / important memory is about several KB. The long-term memory / short-term memory acquisition process is involved in the call process, and there is a time delay demand for the result response.

[0134] Based on the above scenarios and the new scenarios that may be introduced in the future, it is urgent to introduce independent data plane capabilities to support efficient collection and low-latency access of the above data and even new types of data to meet business needs.

[0135] 4. Evolution demand analysis

[0136] The main differences between the new data in the future scenario and the original 5G data service are:

[0137] Data size: New types of data may reach tens of MB levels (such as user short-term memory data) or even several GB levels (such as base station perception point cloud data), while the original subscription data is usually tens of KB levels;

[0138] Data availability: Due to data collection delay or business scenario difference, there is an asynchronous interaction demand between the two ends of the data service; the existing data mechanism is usually realized by SBI real-time interaction / delay subscription mode;

[0139] Time difference: The original data transmission is usually realized through the signaling plane, while the new data types in the future scenario have a large difference in data delay;

[0140] For the large-scale structured / unstructured data that may be introduced in the future scenario, the network needs to provide data service capabilities to support the internal flow of these data in the network to meet the efficient collection and low-latency access needs of the business to the data.

[0141] To solve the above technical problems, the embodiments of the present application propose the following technical solutions.

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

[0143] In the embodiments of the present application, the indication can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by certain information is referred to as to-be-indicated information. In the implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol), thereby reducing the indication overhead to a certain extent. Meanwhile, a common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separate indication of the same information.

[0144] In addition, the specific indication manner can also be various existing indication manners, for example, but not limited to, the above indication manners and various combinations thereof. As described above, for example, when multiple information of the same type needs to be indicated, the indication manners of different information can be different. In the implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited in the embodiments of the present application. In this way, the indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated information to be known by the to-be-indicated party.

[0145] It should be understood that the to-be-indicated information can be sent as a whole, or can be divided into multiple sub-information and sent separately, and the sending period and / or sending occasion of the sub-information can be the same or different. The specific sending method is not limited in the embodiments of the present application. The sending period and / or sending occasion of the sub-information can be predefined, for example, predefined according to a protocol, or configured by the sending node device by sending configuration information to the receiving node device.

[0146] In the present application, the "sending information" can be understood as that a device sends information to another device, or can also be understood as that a logical module in a device sends information to another logical module. For example, "the network device sends information" can be understood as that the network device sends information to another device (such as a terminal or another network device), or can be understood as that a logical module 1 in the network device sends information to a logical module 2 in the network device.

[0147] In the present application, "receiving information" can be understood as a device receiving information from another device, or can also be understood as a logical module in a device receiving information from another logical module. For example, "a network device receiving information" can be understood as the network device receiving information from another device (such as a terminal or another network device), or can be understood as a logical module 1 in the network device receiving information from a logical module 2 in the network device.

[0148] In the present application, "sending information to (for example, a terminal)" or related illustrations in the drawings can be understood as that the destination of the information is the terminal. It can include directly or indirectly sending information to the terminal. "Receiving information from (for example, a terminal)" or "receiving information sent by (for example, a terminal)" or "receiving (for example, a terminal) sending information" or related illustrations in the drawings can be understood as that the source of the information is the terminal, and can include directly or indirectly receiving information from the terminal. The information can be processed as necessary between the source and the destination of the information sending, such as format change, etc., but the destination can understand the valid information from the source. Similar expressions in the present application can be similarly understood, and will not be repeated here.

[0149] "Predefined" or "preconfigured" can be realized by pre-storing corresponding codes, tables or other means that can be used to indicate related information in the device, and the embodiments of the present application do not limit the specific implementation manner. Wherein, "storing" can mean storing in one or more memories. The one or more memories can be separately arranged, or can be integrated in the encoder or decoder, processor, or communication device. The one or more memories can be part of the separately arranged, and part of the integrated in the decoder, processor, or communication device. The type of memory can be any form of storage medium, and the embodiments of the present application do not limit this.

[0150] The "protocol" involved in the embodiments of the present application can refer to a protocol family in the communication field, a standard protocol similar to the frame structure of the protocol family, or a related protocol applied to a future communication system, and the embodiments of the present application do not specifically limit this.

[0151] In the embodiments of the present application, "when", "in the case of", "if", and "if" and the like all refer to the device making corresponding processing under certain objective circumstances, and are not limited by time, and do not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0152] In the description of the embodiments of the present application, unless otherwise specified, " / " represents that the objects before and after the " / " are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In addition, in the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single item or multiple items. For example, at least one of a, b or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second", and the like are used to distinguish the same items or similar items with basically the same function and role. Those skilled in the art can understand that "first", "second", and the like do not limit the quantity and execution order, and "first", "second", and the like do not necessarily mean different. At the same time, in the embodiments of the present application, "exemplary" or "for example" means to serve as an example, illustration or description. Any embodiment or implementation described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or implementations. Rather, "exemplary" or "for example" is used to present the relevant concept in a specific manner, for understanding.

[0153] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0154] In order to understand the embodiments of the present application, first, the communication system shown in FIG. 5 is taken as an example to describe the communication system applicable to the embodiments of the present application in detail. For example, FIG. 5 is a schematic diagram of the architecture of a communication system applicable to the method provided by the embodiments of the present application.

[0155] As shown in FIG. 5, the communication system mainly includes a first data node, a service node, and a routing management node.

[0156] The first data node can be a data management function (DMF) network element or entity, and is configured to provide data access capability for a service node. The first data node can also be another network element or entity that can implement data management function, and is not limited herein. In the embodiments of the present application, the first data node can also be replaced by other possible expressions, such as a data management function node, a data management function network element or a data management function entity, and is not limited herein.

[0157] The service node is configured to initiate a data access request to the first data node, and can be a service control function (SCF) node, a service port function (SPF) node, or the like. In the embodiments of the present application, the service node can also be replaced by other possible expressions, such as a data consumer node, a network function (NF) node, a service control function node, a service port function node, and is not limited herein.

[0158] The routing management node can be a routing management function (RMF) network element or entity, or another network element or entity that can implement routing management function, and is not limited herein. In the embodiments of the present application, the routing management node can also be replaced by other possible expressions, such as a routing management function node, a routing management function network element or a routing management function entity, and is not limited herein.

[0159] In a possible scenario, for example, as shown in FIG. 6, the communication system includes an RMF node, a DMF node, a data storage function (DSF) node and a service node (such as an NF node in FIG. 6). The communication system can also include an internal signaling distribution function (ISDF) node, an external signaling distribution function (ESDF) node, and a global RMF node.

[0160] The RMF node manages the mapping relationship between the intra-domain data index and the DMF / DSF node. There can be a direct connection between multiple RMF nodes, or the routing request interconnection can be implemented through a global RMF node. In an actual deployment scenario, the RMF node can be deployed near the DSF node or as an index storage node of the DSF node.

[0161] Furthermore, for scenarios involving dynamic index construction, RMF nodes need to provide metadata management capabilities to manage the mapping relationship between metadata features and nodes, thereby enabling routing queries based on fuzzy matching when target data has not been collected. To meet business transmission requirements, RMF nodes may also be involved in maintaining information about the nodes' capabilities for data transmission metrics, in order to support the addressing of target nodes that meet the requirements.

[0162] DMF nodes are front-end nodes that provide data access capabilities to business nodes and, through collaboration with RMF nodes, other DMF nodes, and DSF nodes, fulfill the needs for flexible data storage and retrieval and proximity access.

[0163] DSF nodes support data storage based on a distributed mechanism and allow internal data distribution rules to be registered with RMF nodes through DSF nodes.

[0164] In this communication system, data query requests are transmitted through multiplexed service interfaces between network elements such as service nodes and DMF nodes, and data plane link channels are established to avoid the signaling interface being unable to meet the needs of large-scale data transmission. For intra-domain access requests, the DMF node can be used to find the intra-domain RMF node to achieve data routing and addressing, thereby completing data access. For cross-domain access requests, it may also involve inter-domain RMF node interaction, inter-domain DMF node service address lookup, and dynamic establishment of data links to support large-scale cross-domain data transmission.

[0165] When a business node queries / retrieves data from the DMF1 node, it needs to determine whether the data has already been collected. This determination can rely on the query results from the RMF node. If the data has been collected, the DMF node obtains the data address and the corresponding target DMF node information based on the query results. Then, the DMF1 node initiates a request to the target DMF node and executes the data acquisition process. If the data has not been collected, the DSF node assigns an index identifier and triggers the corresponding DMF node (such as the DMF2 node) to perform data acquisition from the target data source node (such as the data production node), ultimately completing the aggregation and generating a mapping relationship between the index and the data.

[0166] For example, data transmission between DMF nodes is achieved through data channels, and the specific format can be as follows:

[0167] Data Index

[0168] >>Data type (Type-length-value)

[0169] >>Permission configuration information (Type-length-value)

[0170] >>Data content (Type-length-value)

[0171] >> read-only, read & write, write only

[0172] Transmission packet header example:

[0173] > source address, destination address, source port, destination port

[0174] > transmission requirement index ID

[0175] > way node 1

[0176] > way node 2

[0177] > way node 3..n

[0178] >> node address or node address index

[0179] After the DMF1 node sends a data query request to the RMF node, the RMF node determines the target DMF node and the list of way DMF nodes based on local information and the interaction interface between the RMF nodes, and returns to the DMF1 node. The target DMF node is a DMF node supporting target data, which can obtain corresponding data from the data source (data source node or DSF node) and return to the DMF1 node; the way DMF node is a list of nodes supporting data transmission based on transmission requirements, serving as a data transmission pipeline. Specifically, one or more DMF nodes of the way can serve as a data transmission agent, only providing data transfer capability, without providing complete data management capability.

[0180] In the communication system, the first data node queries routing information through the routing management node to obtain information of the second data node supporting access to target data, and then obtains the target data through the second data node, which can realize transmission of the target data from the second data node, the first data node to the service node, that is, can support data access close to the target data, can solve the problem that large-scale data is difficult to transfer through signaling messages, and can meet the low-latency access requirement of the service node to data.

[0181] The interaction process between the network elements / devices in the communication system will be specifically introduced below by combining FIG. 7-FIG. 10 through method embodiments. The communication method provided in the embodiments of the present application can be applied to the above-mentioned communication system, and specifically applied to various scenes / processes mentioned in the above-mentioned communication system, which will be specifically introduced below.

[0182] FIG. 7 is a flowchart of a communication method provided by an embodiment of the present application. The communication method is applied to the above-mentioned communication system, and mainly involves the interaction between the first data node, the service node and the routing management node.

[0183] As shown in FIG. 7, the flow of the communication method is as follows:

[0184] S701, the service node sends a first request message to the first data node, and correspondingly, the first data node receives the first request message from the service node.

[0185] The service node is configured to initiate a first request message (such as a data access request) to the first data node. For example, it can be an SCF node, an SPF node, etc. In the embodiments of the present application, the service node can also be replaced by other possible expressions, such as a data consumption node, a network function node, a service control function node, a service port function node, etc., which are not limited herein.

[0186] The first data node can be a DMF network element or entity, configured to provide the service node with data access capability nearby. The first data node can also be other network elements or entities that can implement data management functions, which are not limited herein. In the embodiments of the present application, the first data node can also be replaced by other possible expressions, such as a data management function node, a data management function network element or a data management function entity, etc., which are not limited herein.

[0187] The first request message is configured to request to obtain data. The data can be long-term memory and short-term memory data, communication and perception integrated data, point cloud data, etc., which are not limited. For example, in the communication and perception integrated scenario, the service node sends a data request message (i.e. the first request message) to the DMF1 node, and the data request message is configured to request communication and perception integrated data, also known as sensing data.

[0188] It can be understood that the first request message can also be replaced by other possible expressions, such as a data request message, a data acquisition request message, a data access request message, etc., which are not limited.

[0189] Optionally, the service node determines the first data node based on local configuration information, service discovery information, and service data function (SDF) routing addressing capability, that is, to realize the nearby discovery of the first data node. That is, among multiple data nodes, the first data node can be the node closest to the service node.

[0190] Optionally, the first request message can include a first data index and / or a first data feature, the first data index points to target data, and the feature of the target data matches the first data feature.

[0191] The first data index can be data index information delivered based on a service interface, that is, routing information, which is obtained by the service node in advance based on service interaction. For example, the service node receives information of the first data index through a service message. However, the target data corresponding to the first data index cannot be directly obtained (for example, the data scale is too large to be delivered through the service interface), and therefore, the service node sends a first request message to the first data node and carries the first data index.

[0192] It can be understood that the first data index can be a data index list, that is, contains multiple data indexes, or can contain only one data index, which is not limited here.

[0193] The first data feature can be feature information of the target data, which is used to indicate the feature of the target data that needs to be obtained by the service node. The first data feature can be one or more data features, which are not limited. For example, it can contain target data source (such as the data source node corresponding to the target data) information, target data type information, terminal location, time window / position area restriction, and the like. Among them, the target data source information can be a target data source list supported by the first data node and the like, which can implement data management functions.

[0194] For example, in the case of a sensing scenario, the SCF / SPF node (that is, the above-mentioned service node) performs a DMF node discovery process based on NRF configuration information, discovers DMF1 node nearby, and further sends a data acquisition request message (that is, the above-mentioned first request message) to the DMF1 node. The data type carried by the data acquisition request message is sensing data, and the data acquisition request message can also carry terminal location, data source node corresponding to the terminal location, and time window, and the like. Alternatively, the data acquisition request message can carry one or more data indexes (that is, the above-mentioned first data index), which indicate the data as sensing data.

[0195] In S702, the first data node sends a second request message to the routing management node according to the first request message, and correspondingly, the routing management node receives the second request message from the first data node.

[0196] The routing management node can be an RMF network element or entity, or other network elements or entities that can implement routing management functions, which are not limited here. In the embodiments of the present application, the routing management node can also be replaced by other possible expressions, such as a routing management function node, a routing management function network element, or a routing management function entity, which are not limited here.

[0197] The second request message is used to request to obtain a data node supporting access to data. The second request message can be a request message used for a route information query, such as that the DMF1 node sends a route query request message to the RMF1 node. The process of the route information query can involve an interaction process between different route management nodes in different domains, such as that the RMF1 node sends a route query request message to the RMF2 node.

[0198] It can be understood that the data node supporting access to data can be a node having the same data management function as the first data node, that is, the second data node supporting access to target data hereinafter.

[0199] It can be understood that the second request message can also be replaced by other possible expressions, such as a data access request message, a route information query request message, a route query request message, and the like, without limitation.

[0200] S703. The route management node sends information of the second data node to the first data node, and correspondingly, the first data node receives the information of the second data node from the route management node.

[0201] The second data node supports access to target data. The information of the second data node can be address information or identification information of the second data node. The information of the second data node can also include a data type of data maintained by the second data node, a data type of data collectable by the second data node, and a data source node connectable by the second data node.

[0202] S704. The first data node sends the target data to the service node.

[0203] The target data is obtained from the second data node. The second data node can be multiple, and the target data can include data obtained from different second data nodes. Different second data nodes can correspond to different second data characteristics.

[0204] In summary, the first data node performs a route information query through the route management node to obtain information of the second data node, and then obtains target data through the second data node, which can realize transmission of the target data from the second data node to the service node, can support a data access requirement in proximity, and can solve a problem that large-scale data is difficult to be transferred through a signaling message, and can meet a requirement of efficient data collection and low-latency access of the service node in a future communication scenario.

[0205] S702 is specifically introduced below.

[0206] Optionally, before S702, the first data node performs an access permission pre-check on the service node according to the first request message to determine that the service node has access permission. Then, the first data node sends the second request message to the route management node.

[0207] For example, the DMF1 node performs access permission pre-checking based on the mapping relationship between the local configuration or the data maintained by other nodes (such as the UDM or the RMF) and the access permission role, and confirms that the service node has access permission. For example, based on the mapping relationship between the service node and the data features supported for access, it is determined that the service node can access the data corresponding to the data features in the first request message. Alternatively, based on the access permission control information between the service node and the data node / network element, it is determined that the service node can access the data node (such as the second data node) corresponding to the data index in the first request message.

[0208] The following describes case 1 in which the target data has been collected / prepared, and case 2 in which the target data has not been collected / prepared.

[0209] Case 1:

[0210] In a possible implementation, the second request message includes a second data index and / or a second data feature, the second data index points to the target data, and the feature of the target data matches the second data feature.

[0211] The second data index is the same as or different from the first data index. The second data index can be a list of data indexes, that is, it includes multiple data indexes, or it can include only one data index, which is not limited herein.

[0212] For example, the first data node receives the first request message, and the first request message includes the first data index and the first data feature. The first data node constructs the second data index according to the first data feature, such as the number of the second data index is more than that of the first data index, so as to send the second request message to the routing management node according to the second data index and the first data feature.

[0213] It should be understood that when the first request message does not include the first data index, the second request message can include the second data index.

[0214] For example, the first data node receives the first request message, and the first request message includes the first data feature. The first data node constructs the second data index according to the first data feature, so as to send the second request message to the routing management node according to the second data index and the first data feature.

[0215] The second data feature is the same as or different from the first data feature. The second data feature can be one or more data features, which is not limited.

[0216] For example, the first data node receives a first request message, the first request message comprising a first data index and a first data feature. The first data node supplements / updates the first data feature to obtain a second data feature. The first data node sends a second request message to the routing management node according to the first data index and the second data feature.

[0217] For another example, the first data node receives a first request message, the first request message comprising a first data feature. The first data node supplements / updates the first data feature to obtain a second data feature. The first data node sends a second request message to the routing management node according to the second data feature.

[0218] It should be understood that the above are only some examples of the first request message, and all possible cases are not described here.

[0219] In this way, the first data node queries from the routing management node to a data node (such as a second data node) matching the second data index and / or the second data feature, and the second data index and / or the second data feature can be more complete than the first data index and / or the first data feature, thereby obtaining more accurate information of the data node (such as the second data node).

[0220] Optionally, the routing management node has a metadata management capability, and the metadata comprises a first mapping relationship and / or a second mapping relationship. The first mapping relationship is a mapping relationship between at least one data index and at least one data node, and the at least one data index can comprise the second data index and the at least one data node can comprise the second data node. The second mapping relationship is a mapping relationship between at least one data feature and at least one data node, and the at least one data feature comprises the second data feature and the at least one data node comprises the second data node.

[0221] The metadata management capability herein includes a routing management function, that is, a function of managing the first mapping relationship. The first mapping relationship can be a mapping relationship between a data index (the at least one data index) in a domain and a data node (the at least one data node).

[0222] The first mapping relationship is updated by at least one data node or a data storage node. For example, the routing management node receives a routing library update indication from at least one data node or a data storage node, so that the routing management node updates the first mapping relationship between the at least one data index and the at least one data node. The data storage node can be a DSF network element or entity, or other network element or entity capable of realizing a data storage function, which is not limited herein.

[0223] Optionally, the first mapping relationship can further comprise a mapping relationship between at least one data index and at least one data storage node.

[0224] The data storage node in the embodiments of the present application can also be replaced by other possible expressions, such as a data storage function node, a data storage function network element, a data storage function entity, and the like, which are not limited herein.

[0225] The metadata management capability also includes a capability of managing a second mapping relationship, that is, a capability of managing a mapping relationship between a metadata feature (the at least one data feature) and a data node (the at least one data node).

[0226] Optionally, the second mapping relationship can also include a mapping relationship between the at least one data feature and the at least one data source node. For example, a mapping relationship between perception data of a target base station and one or more DMF nodes, or a mapping relationship between a target data type and one or more DMF nodes.

[0227] The data source node in the embodiments of the present application can be a data producer (DP) node.

[0228] In this way, the metadata management capability of the routing management node provides accurate routing query capability for the first data node, that is, the accuracy of determining the second data node is improved.

[0229] To meet the business transmission requirements, the routing management node can also involve maintaining capability information of the data node for a data transmission index to support addressing of a target node meeting the requirements. For example, after the RMF node receives the routing query request of the DMF1 node, it is determined that the data transmission index capability of the DMF2 node meets the query requirements of the DMF1 node, and thus the address information of the DMF2 node is sent to the DMF1 node.

[0230] In addition, the routing management node needs to support fuzzy matching to find a target data potential storage node. For example, the RMF node performs matching based on the perception data information of a specific time period requested by the DMF1 node to obtain the DMF2 node (the second data node).

[0231] Optionally, if the second request message includes a second data index, the second data node is determined according to the second data index and the first mapping relationship; if the second request message includes a second data feature, the second data node is determined according to the second data feature and the second mapping relationship.

[0232] That is, if the second request message comprises the second data index, the routing management node determines the second data node corresponding to the second data index from the first mapping relationship; if the second request message comprises the second data feature, the routing management node determines the second data node corresponding to the second data feature from the second mapping relationship. The second data node can be one or more data nodes, such as DMF2 node, DMF3 node, DMF4 node, etc. For example, if the second data index is multiple, the second data node is multiple.

[0233] Optionally, if the second request message comprises the second data index and the second data feature, the second data node is determined according to the second data index and the first mapping relationship, and the second data feature and the second mapping relationship.

[0234] In the case of multiple second data features, the second data node is multiple.

[0235] For example, the second request message comprises the second data index and the second data feature. The routing management node determines at least one data node #1 corresponding to the second data index from the first mapping relationship, and determines at least one data node #2 corresponding to the second data feature from the second mapping relationship, and then determines the second data node contained in at least one data node #1 and at least one data node #2.

[0236] In this way, the second data node is determined according to different contents in the second request message, which improves the flexibility of determining the second data node.

[0237] Optionally, the routing management node has the ability to manage the topology relationship and the transmission capability information. The topology relationship indicates the adjacency relationship between the first data node, the second data node and the third data node, wherein the third data node is one or more data nodes through which the target data is transmitted between the first data node and the second data node.

[0238] It can be understood that the topology relationship is used to determine the second data node and the third data node, that is, to determine the channel for transmitting the target data. The third data node as one or more data nodes (such as DMF node) in the channel can serve as a data transmission agent and only provide data transfer capability without providing complete data management capability.

[0239] The transmission capability information indicates transmission capability of at least one data node, and is used for establishing a channel for transmitting the target data, and the at least one data node includes the second data node. Of course, the at least one data node can also include the first data node and the third data node. The transmission capability information can include, for example, bandwidth capacity, scheduling capability, resource utilization, reverse channel capability, etc. of each of the at least one data node. The transmission capability information is used for establishing the channel for transmitting the target data, and the transmission capability information of the second data node determined by the routing management node meets the requirement. In addition, the transmission capability information of the nodes involved in the channel for transmitting the target data, such as the first data node and the third data node, also needs to meet the requirement.

[0240] Before the routing management node sends the information of the second data node to the first data node at S703, the communication method can further include: the routing management node receives a registration request from at least one data node, and the registration request is used for registering at least one of the following: the first mapping relationship, the second mapping relationship, the topology relationship or the transmission capability information.

[0241] The first mapping relationship, the second mapping relationship, the topology relationship and the transmission capability information can refer to the above description, and will not be described here. The topology relationship can be configured locally by the routing management node.

[0242] It can be understood that the at least one data node periodically registers data mapping information in full or incremental form based on heartbeat signaling to the routing management node, and the data mapping information can include the first mapping relationship, the second mapping relationship, the topology relationship or the transmission capability information. Therefore, the routing management node can determine the information of the second data node according to the at least one item after receiving the data query request (i.e. the second request message), that is, correctly perform data node query and data link arrangement, and the data link arrangement here can be establishing a channel for transmitting data. In addition, the routing management node determines the information of the second data node according to the at least one item and the local configuration information.

[0243] It can be understood that the routing management node performs node query based on the information registered by the at least one data node, and obtains the second data node, for example, the RMF node determines that the DMF2 node supports returning the target data content based on the mapping relationship between the at least one DMF node and the data feature / data index, and thus returns the information of the DMF2 node to the DMF1 node.

[0244] Case 2:

[0245] In another possible implementation, the second request message does not include the second data index and includes the second data feature; the communication method can further include: the first data node receives second indication information from the routing management node, and the second indication information is used for indicating that the data matched with the second data feature is not collected.

[0246] It can be understood that if the second request message includes the second data index, it means that there is data corresponding to the second data index, that is, the target data indicated by the second data index has been collected. Therefore, in the case that the second request message does not include the second data index and includes the second data feature, there may be a case that the target data is not collected. At this time, the routing management node indicates to the first data node that the data matching the second data feature is not collected, and sends the first data node the second data node, at this time the second data node is a node that has not collected the data matching the second data feature and is capable of collecting the data matching the second data feature.

[0247] For example, the RMF node receives a routing query request message (second request message) from the DMF1 node, and determines that the data matching the second data feature carried in the routing query request message has not been collected, and then returns one or more related DMF nodes and a data not collected indication to the DMF1 node in the response message. Optionally, the RMF node can also return the mapping relationship between the data source node and the data feature, such as the DMF2 information corresponding to the DP1 node and the DMF3 information corresponding to the DP2 node.

[0248] Optionally, after the first data node receives the information of the second data node from the routing management node, the first data node sends a third request message to the second data node, and correspondingly, the second data node receives the third request message from the first data node. The third request message is used to request data, and the third request message includes the second data feature. The second data node sends a fourth request message to the data production node according to the third request message, and the fourth request message is used to request to collect data. The data production node is related to the second data feature. The second data node receives the target data and sends the target data to the first data node.

[0249] It can be understood that after the second data node receives the third request message, the data access permission check is performed. After the check is passed, the fourth request message, that is, the data collection request, is sent to one or more data production nodes. For example, the DMF2 node sends a data collection request #1 to the DP1 node and a data collection request #2 to the DP2 node. The data production node is related to the second data feature, that is, the data produced by the data production node matches the second data feature. The data production node can be one or more, without limitation.

[0250] The fourth request message can include a receiving address and allocated index information, where the receiving address can be an address of the second data node or an address of the data storage node, and the allocated index information can be an index allocated by the second data node for the fourth request message, used for indexing the data collected by the data production node, that is, the allocated index information corresponds to the data collected by the data production node. For example, the DMF2 node sends a data collection request #1 to the DP1 node and allocates a data index #1 for the data collection request #1, so that the data collected from the DP1 node corresponds to the data index #1; and sends a data collection request #2 to the DP2 node and allocates a data index #2 for the data collection request #2, so that the data collected from the DP2 node corresponds to the data index #2.

[0251] Further, the second data node receives the target data from one or more data production nodes and sends the target data to the first data node. In addition, if the collected data needs to be transferred through the data storage node, a data transfer request is further initiated to the data storage node, where the receiving address of the second data node is carried.

[0252] The following specifically introduces S704.

[0253] First, two ways of transmitting the third request message by the first data node and the second data node are introduced.

[0254] Method 1: The third request message is transmitted by using a point-to-point non-inductive mode.

[0255] In a possible implementation, before the first data node sends the target data to the service node, the communication method can further include: the first data node sends a third request message to the second data node, where the third request message is used for requesting data and / or requesting to establish a channel for transmitting data; and the first data node receives the target data from the second data node.

[0256] The third request message can include a second data index and / or a second data feature, used for indicating that data matching the second data index and / or the second data feature needs to be obtained from the second data node.

[0257] The channel for transmitting data can be used for transmitting the target data. Optionally, the first data node receives the target data from the second data node through the channel.

[0258] Optionally, the channel can include a transfer channel and / or an update channel; the transfer channel is used for transmitting the target data between the second data node and the first data node; and the update channel is used for transmitting updated target data between the second data node and the first data node.

[0259] It can be understood that the transit channel and / or the update channel are established after the second data node receives the third request message and performs the data access permission. The transit channel is used for transmitting the target data from the second data node to the first data node after being established, and the update channel is used for transmitting the updated target data between the service node, the first data node and the second data node after the service node updates the target data.

[0260] Optionally, the channel includes the transit channel and / or the update channel; the transit channel is used for transmitting the target data between the data storage node, the second data node and the first data node, wherein the data storage node stores the target data; and the update channel is used for transmitting the updated target data between the data storage node, the second data node and the first data node.

[0261] It can be understood that the target data can be stored in the data storage node instead of the second data node, so that the second data node receives the third request message, performs the data access permission check, and requests the data storage node in the back end to establish the transit channel and / or the update channel after the check passes, so that the transit channel and / or the update channel are established between the data storage node, the second data node and the first data node.

[0262] Optionally, the first data node receives a mapping relationship between a plurality of second data nodes and a plurality of second data features from the routing management node. Therefore, the first data node can send the third request message to the second data node corresponding to different second data features, so as to obtain the data corresponding to different second data features from different second data nodes to obtain the target data.

[0263] Optionally, the third request message can also include the receiving address information of the first data node. Optionally, the third request message can also include the timeliness information of the receiving address of the first data node, to indicate the second data node to complete the transmission of the target data before the receiving address of the first data node is invalid.

[0264] In the case that the first request message includes the demand parameter, the third request message can also include the demand parameter, which is used to provide guarantee for the transmission of the target data, or is used to establish the channel for transmitting the target data; the demand parameter can include at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, the first indication information being used to indicate the service node to update the target data.

[0265] That is, when the target data is transmitted between the first data node and the second data node, the demand parameter needs to be met, or the channel used for transmitting the target data between the first data node and the second data node needs to meet the demand parameter.

[0266] Optionally, in the case that the requirement parameter comprises the first indication information, the communication method can further comprise: the first data node receiving receiving address information from the second data node, the receiving address information of the second data node indicating the first data node to transmit the updated target data.

[0267] The receiving address information of the second data node can further comprise time validity information of the address of the second data node, or the first data node receives the time validity information of the address from the second data node to indicate the first data node to complete the transmission of the updated target data before the address of the second data node is invalid.

[0268] It can be understood that in the mode 1, the third request message is transmitted in a manner of passing through a point without sensing, for example, the DMF1 node directly transmits the third request message to the second data node, wherein the third request message carries the address information of the DMF1 node, the requirement parameter, and the address information or index information of each passing DMF node (the third data node), so that each passing DMF node completes resource reservation and path selection based on the requirement parameter and the DMF node information of each passing DMF node. When the target data is started to be transmitted, each DMF node adds corresponding label information in the packet header to implement the target data transmission under the channel. The packet header can refer to the above-mentioned transmission packet header example, and will not be described here.

[0269] For example, as shown in FIG. 8, the channel 1 (also referred to as the path 1) comprises the DMF1 node, the DMF3 node, the DMF4 node, and the DMF2 node. The path 2 comprises the DMF1 node and the DMF2 node. The third request message and the response message of the third request message are transmitted through the channel 2 (also referred to as the path 2), and the specific passing nodes are not limited. When the target data is started to be transmitted, the DMF2 node (i.e., the second data node) carries the information of each passing node (i.e., the third data node) and the optional requirement parameter information in the packet header, to implement the resource scheduling processing and link arrangement synchronized with the packet. Specifically, each passing node information can be carried in the form of an index, and each passing node determines the address of the next hop node in combination with the local configuration information and performs the corresponding forwarding action. For example, when the DMF2 node starts to transmit the target data, the DMF2 node determines the address of the DMF3 node as the next hop node according to the information of each passing node and the local configuration information, and then the DMF3 node determines the address of the DMF4 node as the next hop node in the same manner, so as to implement the transmission of the target data through the channel 1.

[0270] Mode 2: a mode in which the third request message is transmitted through a passing point.

[0271] In another possible implementation, the third request message comprises the information of the third data node, and the third data node is one or more data nodes passed through when the first data node transmits the target data to the second data node.

[0272] Optionally, the routing management node determines the third data node according to the at least one of the first mapping relationship, the second mapping relationship, the topology relationship, or the transmission capability information, and sends information of the third data node to the first data node. Correspondingly, the first data node receives the information of the third data node from the routing management node.

[0273] The second request message received by the routing management node can further include a requirement parameter. The routing management node determines the third data node according to the at least one of the first mapping relationship, the second mapping relationship, the topology relationship, or the transmission capability information, and the requirement parameter.

[0274] For example, after determining the DMF2 node (i.e., the second data node), the RMF node needs to combine the data transmission requirement (i.e., the requirement parameter), the topology relationship between the DMF nodes, and the transmission capability information of the DMF nodes to perform data link arrangement, and return the address of the DMF2 node and the address information of the address of one or more optional path nodes (i.e., the third data node) to the source DMF1 node (i.e., the first data node). FIG. 9 is a schematic diagram of data link arrangement. As shown in FIG. 9, for a large bandwidth requirement scenario, such as a high-definition video scenario, a large bandwidth path is selected, i.e., channel 3 (data nodes 1, 2, 4, and 6) performs transmission; for a time-sensitive data transmission scenario, such as a voice call scenario, a low-latency path is used, i.e., channel 4 (data nodes 1, 2, 3, 5, and 6) performs transmission.

[0275] Optionally, the channel can include a transfer channel and / or an update channel; the transfer channel is used for transmitting the target data between the second data node, the third data node, and the first data node; and the update channel is used for transmitting the updated target data between the first data node, the third data node, and the second data node.

[0276] Optionally, the channel includes a transfer channel and / or an update channel; the transfer channel is used for transmitting the target data between the data storage node, the second data node, the third data node, and the first data node, wherein the data storage node stores the target data; and the update channel is used for transmitting the updated target data between the first data node, the third data node, the second data node, and the data storage node.

[0277] Optionally, the third request message can further include identification information of the channel, the identification information of the channel being used to identify the channel, or in other words, the transmission path of the target data.

[0278] Optionally, the first data node sending the third request message to the second data node can include: the first data node sending the third request message to the second data node through the third data node. Correspondingly, the target data is obtained from the second data node through the third data node.

[0279] It can be understood that the above process of determining the second data node and the third data node, i.e., the process of determining the channel / path of transmitting data, or the data orchestration process. The third request message can be sent via the third data node to complete the hop-by-hop channel establishment. The third request message can include information of the third data node, and the third data node performs resource reservation / channel establishment based on the third request message.

[0280] For example, as shown in FIG. 8, the channel 1 (also referred to as path 1) includes DMF1 node, DMF3 node, DMF4 node and DMF2 node. The third request message and the response message are sent hop by hop through the path 1 to complete the end-to-end link establishment process and resource allocation process before the target data starts transmission. At this time, each node can receive the data transmission requirement from the source DMF1 node to complete the resource reservation action and the association of the previous hop / next hop node. Specifically, the association action can be combined with the channel identifier carried in the third request message, and then only the channel identifier needs to be carried in the subsequent target data transmission process, such as the data channel identifier carried in the packet header, so as to realize the resource reservation, channel selection of the DMF3 node, DMF4 node and DMF2 node, i.e., the DMF3 node, DMF4 node and DMF2 node determine the next hop node according to the channel 1 corresponding to the channel identifier.

[0281] In addition, the communication method can further include a process of registering the target data to the second data node and / or the data storage node. Specifically, the data source node can directly register the target data to the second data node and the storage node, or the data source node can register the target data to the second data node and register the target data to the data storage node through the second data node; the second data node is responsible for performing index allocation and returning to the data source node to support subsequent access / update.

[0282] It should be understood that the various implementation manners in the embodiments of the present application can be combined, and the combination of the various implementation manners of the above embodiments is not limited.

[0283] The above describes the overall process of the communication method provided by the embodiments of the present application in combination with FIGS. 7-9. The specific process of the communication method provided by the embodiments of the present application in two specific scenarios is introduced in combination with FIGS. 10 and 11.

[0284] FIG. 10 is a flowchart of a communication method provided by the embodiments of the present application. The communication method is applicable to the above communication system, and specifically relates to the interaction between the data consumer node (i.e., the above business node), DMF1 node (i.e., the above first data node), RMF1 node (i.e., the above routing management node), RMF2 node, DMF2 node (i.e., the above second data node), DP1 node and DP2 node (the above data production node), and DSF node (i.e., the above data storage node).

[0285] Specifically, as shown in FIG. 10, the flow of the communication method is as follows:

[0286] S100A, the DP1 and DP2 nodes register data to the DMF2 node.

[0287] For example, the DP1 and DP2 nodes respectively send a data registration request message to the DMF2 node, and the DMF2 node respectively sends a response message corresponding to the data registration request message to the DP1 and DP2 nodes, and the response message indicates that the data registration is successful.

[0288] S100B, the DMF2 node synchronously stores the data to the DSF node.

[0289] S100A and S100B are optional steps. S100A and S100B are a way of indirectly registering data to the DSF node between the DP nodes.

[0290] S100a1, the DP2 node sends a data registration request message to the DMF2 node.

[0291] S100a2, the DP1 node sends a data registration request message to the DMF2 node.

[0292] S100b, the DMF2 node performs index allocation and respectively sends an index allocated for the data to the DP1 node and the DP2 node.

[0293] S100c, the DP1 node and the DP2 node respectively register the data to the DSF node.

[0294] S100a1-S100c are optional steps. S100a1-S100c are a way of directly registering data to the DSF node by the DP1 node and the DP2 node. S100A and S100B are executed, or S100a1-S100c are executed.

[0295] S100d, the DMF2 node sends routing table update information to the RMF2 node.

[0296] The routing table update information can include an index of the data registered by the DP1 node and the DP2 node, and information of the DMF2 node / DSF node corresponding to the data.

[0297] Optionally, the DSF node sends the routing table update information to the DMF2 node.

[0298] S1001, the data consumer node sends a data acquisition request to the DMF1 node.

[0299] The data acquisition request can include data index #1 and / or data feature #1. The data acquisition request can refer to the description of the first data request in S701, the data index #1 can refer to the description of the first data index in S701, and the data feature #1 can refer to the description of the first data feature in S701, and details are not repeated. Optionally, the data acquisition request can also include demand parameters, which can refer to the description of the demand parameters in S701, and details are not repeated.

[0300] S1002, the DMF1 node performs data access permission pre-checking.

[0301] The DMF1 node performs access permission pre-checking based on the mapping relationship between the data saved by the local configuration or other nodes (such as UDM or RMF) and the access permission role, and confirms that the data consumer node has access permission. For example, based on the mapping relationship between the data consumer node and the supported data features, it is determined that the data consumer node can access the data corresponding to the data features in the data acquisition request. Or, based on the access permission control information between the data consumer node and the data node / network element, it is determined that the data consumer node can access the data node (such as DMF2 node) corresponding to data index #1.

[0302] S1003, the DMF1 node sends a routing information query request message to the RMF1 node.

[0303] The routing information query request message can include data index #2 and / or data feature #2, and the routing information query request can refer to the description of the second data request in S702. Here, the data index #2 can refer to the description of the second data index in S702, and the data feature #2 can refer to the description of the second data feature in S702, and details are not repeated. The RMF1 node needs to support fuzzy matching to find the target data potential storage node, such as performing matching based on the perceived data information of the requested target node in a specific time period.

[0304] S1004, the RMF1 node queries the routing information from the RMF2 node.

[0305] S1004 is an optional step. The routing information query process can involve inter-domain RMF interaction procedures, such as when the RMF1 node cannot query the DMF node corresponding to the data index #2 and / or data feature #2, the routing information query request is sent to the RMF2 node. Thus, the address information of the DMF2 node is obtained from the RMF2 node.

[0306] Optionally, the DMF1 node can also perform index construction, such as index construction according to data feature #2, to obtain data index #3, and perform routing information query based on the constructed data index #3.

[0307] S1005, the RMF1 node sends a routing information query response message to the DMF1 node.

[0308] The routing information query response message can include address information of the DMF2 node.

[0309] S1006, the DMF1 node sends a data acquisition request message and / or a channel establishment request message to the DMF2 node.

[0310] The data acquisition request message and / or the channel establishment request message can carry a receiving address and a requirement parameter of the DMF1 node. The data acquisition request message and / or the channel establishment request message can also include data index #2 and / or data feature #2. Optionally, the data acquisition request message and / or the channel establishment request message can also include address timeliness information of the receiving address, to indicate that the DMF2 node completes data transmission before the receiving address is invalid.

[0311] The data acquisition request message or the channel establishment request message can also refer to the description of the third request message in S704, and details are not repeated.

[0312] S1007, the DMF2 node performs data access permission verification.

[0313] S1007 is an optional step. The DMF2 node performs access permission verification based on a mapping relationship between data and access permission roles saved by a local configuration or other nodes (such as UDM or RMF), and confirms that the data consumer node has access permission. For example, based on a mapping relationship between the data consumer node and supported data features, it is determined that the data consumer node can access data corresponding to the data features in the data acquisition request. Alternatively, based on access permission control information between the data consumer node and the data node / network element, it is determined that the data consumer node can access the data node (such as the DMF2 node) corresponding to data index #2.

[0314] S1008, the DMF2 node requests the DSF node to establish a channel.

[0315] S1008 is an optional step. For example, the DMF2 node sends a channel establishment request message to the DSF node, and the DSF node sends a response message of successful channel establishment to the DMF2 node.

[0316] S1009, the DMF2 node sends a data acquisition response message and / or a response message of successful channel establishment to the DMF1 node.

[0317] The data acquisition response message is a feedback of the data acquisition request message by the DMF2 node, and the response message of successful channel establishment is a feedback of the channel establishment request message by the DMF2 node. The data acquisition response message can carry target data matched with data index #2 and / or data feature #2.

[0318] Optionally, if the requirement parameter carried in the acquisition request message and / or the channel establishment request message includes the update indication, that is, the DMF2 node receives the update indication, the corresponding update receiving address information, that is, the receiving address information of the DMF2 node, also needs to be carried in the data acquisition response message and / or the response message of the successful channel establishment.

[0319] S1010, a data plane transit channel is established between the DSF node, the DMF2 node, the DMF1 node and the data consumption node.

[0320] S1010 is an optional step. If the DMF1 node sends the channel establishment request message to the DMF2 node in S1006, and the DMF2 node sends the response message of the successful channel establishment to the DMF1 node in S1009, S1010 is executed. The data plane transit channel is used for transmitting the target data matching the data index #2 and / or the data feature #2 between the DSF node, the DMF2 node, the DMF1 node and the data consumption node.

[0321] Optionally, a data transit channel is established between the DMF2 node, the DMF1 node and the data consumption node.

[0322] S1011, a data plane update channel is established between the data consumption node, the DMF1 node, the DMF2 node and the DSF node.

[0323] S1011 is an optional step. If the requirement parameter carried in the acquisition request message and / or the channel establishment request message includes the update indication, the DMF1 node sends the channel establishment request message to the DMF2 node in S1006, and the DMF2 node sends the response message of the successful channel establishment to the DMF1 node in S1009, S1011 is executed. The data plane update channel is used for transmitting the target data updated by the data consumption node between the data consumption node, the DMF1 node, the DMF2 node and the DSF node.

[0324] Optionally, a data plane update channel is established between the data consumption node, the DMF1 node and the DMF2 node.

[0325] In summary, by querying the routing information of the RMF1 node according to the data index and / or the data feature through the DMF1 node, the information of the DMF2 node supporting the access to the target data is obtained, and then the target data is obtained through the DMF2 node, so that the transmission of the target data from the DMF2 node to the data consumption node can be realized, that is, the data access demand in proximity can be supported, the problem that large-scale data is difficult to transit through signaling messages is solved, and the low-latency access demand for data is met.

[0326] FIG. 11 is a flow diagram of a communication method provided by the embodiments of the present application. The communication method is applicable to the communication system described above, and specifically relates to the interaction between a data consumer node (i.e., the service node described above), a DMF1 node (i.e., the first data node described above), a RMF1 node (i.e., the routing management node described above), a RMF2 node, a DMF2 node (i.e., the second data node described above), a DP1 node and a DP2 node (i.e., the data production node described above), and a DSF node (i.e., the data storage node described above).

[0327] Specifically, as shown in FIG. 11, the communication method has the following procedure:

[0328] S1101. The data consumer node sends a data acquisition request to the DMF1 node.

[0329] The data acquisition request can include data feature #1. The data acquisition request can refer to the description of the first data request in S701, and the data feature #1 can refer to the description of the first data feature in S701, which will not be repeated here. It can be understood that in this application scenario, the target data that the data consumer node wants to acquire is not collected, and the data acquisition request does not contain the data index.

[0330] Optionally, the data acquisition request can also include a requirement parameter, which can refer to the description of the requirement parameter in S701, which will not be repeated here.

[0331] S1102. The DMF1 node performs data access permission pre-verification.

[0332] S1102 can refer to the description of S1002, which will not be repeated here.

[0333] S1103. The DMF1 node sends a routing information query request message to the RMF1 node.

[0334] The routing information query request message can include data feature #2, and the routing information query request can refer to the description of the second data request in S702. Here, the data feature #2 can refer to the description of the second data feature in S702, which will not be repeated here.

[0335] S1104. The RMF1 node queries the RMF2 node for routing information.

[0336] S1104 is an optional step. S1104 can refer to the description of S1004, which will not be repeated here.

[0337] Optionally, the DMF1 node can also perform index construction, such as index construction according to the data feature #2, to obtain a data index #3, and perform routing information query based on the constructed data index #3.

[0338] S1105, the RMF1 node sends a routing information query response message to the DMF1 node.

[0339] The routing information query response message can include address information of the DMF2 node. The DMF2 node can be a node related to data feature #2, that is, the DMF2 node supports access to target data matching data feature #2. The routing information query response message can also include an indication that the data is collected, indicating that the target data matching data feature #2 is not collected, or indicating that the DMF2 node does not collect the target data matching data feature #2.

[0340] S1106, the DMF1 node sends a data acquisition request message and / or a channel establishment request message to the DMF2 node.

[0341] The data acquisition request message and / or the channel establishment request message can carry the receiving address of the DMF1 node, data feature #2, and the requirement parameter. Optionally, the data acquisition request message and / or the channel establishment request message can also include address timeliness information of the receiving address to indicate that the DMF2 node completes data transmission before the receiving address expires.

[0342] The data acquisition request message or the channel establishment request message can also refer to the description of the third request message in S704, which is not repeated.

[0343] S1107, the DMF2 node performs data access permission verification.

[0344] S1107 is an optional step. S1107 can refer to the description of S1007, which is not repeated.

[0345] S1108, the DMF2 node sends a data collection request message to the DP1 node and / or the DP2 node.

[0346] The data collection request message is used to request collection of data. For example, the DMF2 node sends a data collection request message #1 to the DP1 node and a data collection request message #2 to the DP2 node. The data collection request message can include a receiving address and assigned index information, such as data collection request message #1 including index #1 and data collection request message #2 including index #2. The receiving address and the assigned index information can refer to the description of the fourth request message in S702, which is not repeated.

[0347] S1109, the DP1 node and / or the DP2 node sends a data collection response message to the DMF2 node.

[0348] S1109 is an optional step. The data collection response message is used to respond to the data collection request message, such as a data collection response message indicating that target data collection is successful or failed, and the target data matches data feature #2.

[0349] S1110, the DP1 node and / or the DP2 node sends a data registration request message to the DSF node.

[0350] S1110 is an optional step. The DP1 node and / or the DP2 node does not send the data collection response message to the DMF2 node directly, but transmits the target data collected through the DSF node. The data registration request message can include the target data matching the data feature #2.

[0351] S1111, the DMF2 node sends a data transmission request message to the DSF node.

[0352] S1111 is an optional step. If the data collection needs to be transmitted through the DSF node, the DMF2 node also initiates a data transmission request to the DSF, which carries the receiving address of the DMF1 node.

[0353] S1112, the DSF node sends the target data to the DMF2 node.

[0354] S1112 is an optional step. If S1109 is performed, S1110-S1112 can not be performed, and if S1110-S1112 is performed, S1109 can not be performed.

[0355] S1113, a data plane transmission channel is established between the DMF2 node, the DMF1 node and the data consumption node.

[0356] S1113 is an optional step. If the DMF1 node sends a channel establishment request message to the DMF2 node in S1106, S1113 is performed. The data plane transmission channel is used for transmitting the target data collected between the DMF2 node, the DMF1 node and the data consumption node.

[0357] S1114, a data plane update channel is established between the data consumption node, the DMF1 node, the DMF2 node and the DSF node.

[0358] S1114 is an optional step. If the requirement parameter carried in the acquisition request message and / or the channel establishment request message includes an update indication, the DMF1 node sends a channel establishment request message to the DMF2 node in S1106, S1011 is performed. The data plane update channel is used for transmitting the target data updated by the data consumption node between the data consumption node, the DMF1 node, the DMF2 node and the DSF node.

[0359] Optionally, a data plane update channel is established between the data consumption node, the DMF1 node and the DMF2 node.

[0360] In summary, by querying the RMF1 node for routing information according to the data characteristics by the DMF1 node, information of the DMF2 node capable of collecting the target data is obtained, and then the target data is collected by the DMF2 node, so that the transmission of the target data from the DMF2 node to the data consumer node can be implemented, that is, the data access requirement in proximity can be supported, the problem that large-scale data is difficult to transit through signaling messages is solved, and the low-latency access requirement for data is met.

[0361] The method provided by the embodiments of the present application is described in detail above in combination with FIG. 7-FIG. 11. The communication apparatus for performing the communication method provided by the embodiments of the present application is described in detail below in combination with FIG. 12-FIG. 13.

[0362] FIG. 12 is a structural schematic diagram of the communication apparatus provided by the embodiments of the present application. As shown in FIG. 12, the communication apparatus 1200 includes a transceiver module 1201 and a processing module 1202. For the convenience of description, FIG. 12 only shows the main components of the communication apparatus.

[0363] The transceiver module 1201 is configured to perform the transceiving function of the method shown in FIG. 7, and the processing module 1202 is configured to perform other functions of the method shown in FIG. 7 except the transceiving function.

[0364] Optionally, the transceiver module 1201 can include a sending module (not shown in FIG. 12) and a receiving module (not shown in FIG. 12). The sending module is configured to implement the sending function of the communication apparatus 1200, and the receiving module is configured to implement the receiving function of the communication apparatus 1200.

[0365] Optionally, the communication apparatus 1200 can further include a storage module (not shown in FIG. 12), which stores a program or instructions. When the processing module 1202 executes the program or instructions, the communication apparatus 1200 can perform the functions of the first data node, the service node or the routing management node in the method shown in FIG. 7 in the above method.

[0366] It can be understood that the communication apparatus 1200 can be the first data node, the service node or the routing management node, or a chip (system) or other components or assemblies that can be arranged in the first data node, the service node or the routing management node, or an apparatus containing the first data node, the service node or the routing management node, and the present application does not limit this.

[0367] In addition, the technical effects of the communication apparatus 1200 can refer to the technical effects of the communication method shown in FIG. 7, which will not be described herein again.

[0368] FIG. 13 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application. The communication apparatus can be a terminal, a chip (system) or other components or assemblies that can be arranged in the terminal. As shown in FIG. 13, the communication apparatus 1300 can include a processor 1301. Optionally, the communication apparatus 1300 can further include a memory 1302 and / or a transceiver 1303. The processor 1301 is coupled with the memory 1302 and / or the transceiver 1303, for example, through a communication bus, through an intra-chip interface, or through other communication lines. Optionally, the memory 1302 can be integrated with the processor 1301.

[0369] The components of the communication apparatus 1300 will be described in detail below in conjunction with FIG. 13.

[0370] The processor 1301 is the control center of the communication apparatus 1300, and can be one processor or a plurality of processing elements. For example, the processor 1301 can be one or more central processing units (CPUs), application specific integrated circuits (ASICs), or one or more integrated circuits configured to perform the embodiments of the present application, such as one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0371] Optionally, the processor 1301 can perform various functions of the communication apparatus 1300 by running or executing software programs stored in the memory 1302 and calling data stored in the memory 1302, such as the communication method shown in FIG. 7.

[0372] In a specific implementation, as an embodiment, the processor 1301 can include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 13.

[0373] In a specific implementation, as an embodiment, the communication apparatus 1300 can also include a plurality of processors, such as the processor 1301 and the processor 1304 shown in FIG. 13. Each of the processors can be a single-CPU or a multi-CPU. The processor herein can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0374] The memory 1302 is configured to store a software program for implementing the solutions of the present application, and the processor 1301 is configured to control the execution of the software program. The specific implementation can refer to the method embodiments described above, and will not be described here.

[0375] Optionally, the memory 1302 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, and can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this. The memory 1302 can be integrated with the processor 1301 or exist independently and be coupled to the processor 1301 through the interface circuit (not shown in FIG. 13) of the communication device 1300. The embodiments of the present application are not limited in this regard.

[0376] The transceiver 1303 is configured to communicate with other communication devices. For example, the communication device 1300 is a terminal, and the transceiver 1303 can be configured to communicate with a network device or another terminal device. For another example, the communication device 1300 is a network device, and the transceiver 1303 can be configured to communicate with a terminal or another network device.

[0377] Optionally, the transceiver 1303 can include a receiver and a transmitter (not shown separately in FIG. 13). The receiver is configured to implement the receiving function, and the transmitter is configured to implement the transmitting function.

[0378] Optionally, the transceiver 1303 can be integrated with the processor 1301 or exist independently and be coupled to the processor 1301 through the interface circuit (not shown in FIG. 13) of the communication device 1300. The embodiments of the present application are not limited in this regard.

[0379] It can be understood that the structure of the communication device 1300 shown in FIG. 13 does not constitute a limitation on the communication device, and the actual communication device can include more or fewer components than those shown, or combine certain components, or different component arrangements.

[0380] In addition, the technical effects of the communication apparatus 1300 can refer to the technical effects of the methods described in the above method embodiments, which will not be repeated here.

[0381] It should be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and the processor can also be other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0382] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a ROM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an EEPROM or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

[0383] The above-described embodiments can be implemented in part or in whole through software, hardware (e.g., circuitry), firmware, or any combination thereof. When implemented in software, the above-described embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When loaded and executed by a computer, the computer instructions or computer programs can produce the processes or functions described above in accordance with the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, such as from a website site, a computer, a server, or a data center to another website site, a computer, a server, or a data center through a wired (e.g., infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium or a collection of medium accessible by a computer or a data storage device such as a server, a data center, etc. containing one or more available medium. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state disk.

[0384] It should be understood that the term "and / or" in this document is merely used to describe an associated relationship between associated objects, and can represent three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone, where A and B can be singular or plural. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects, but can also represent an "and / or" relationship. The specific meaning can be understood according to the context before and after.

[0385] In this application, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

[0386] It should be understood that in various embodiments of the present application, the size of the sequence number of the above-described processes does not mean the order of execution, and the execution order of the processes should be determined according to their functions and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0387] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0388] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0389] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0390] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. they can be located in one place or distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0391] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0392] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the essential part of the technical solutions or the part of the technical solutions that make contributions to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes the above-mentioned various possible memories.

Claims

1. A communication method characterized by comprising: The method comprises: a first data node receives a first request message from a service node, the first request message being used to request to obtain data; the first data node sends a second request message to a routing management node according to the first request message, the second request message being used to request to obtain a data node supporting access to data; the first data node receives information of a second data node from the routing management node, the second data node supporting access to target data; the first data node sends the target data to the service node, the target data being obtained from the second data node.

2. The method of claim 1, wherein, The first request message comprises a first data index and / or a first data feature, the first data index pointing to the target data, and the feature of the target data matching the first data feature.

3. The method of claim 2, wherein, The second request message comprises a second data index and / or a second data feature, the second data index pointing to the target data, and the feature of the target data matching the second data feature.

4. The method of claim 3, wherein, The routing management node has a metadata management capability, and the metadata comprises a first mapping relationship and / or a second mapping relationship; the first mapping relationship is a mapping relationship between at least one data index and at least one data node, the at least one data index comprising the second data index, and the at least one data node comprising the second data node; the second mapping relationship is a mapping relationship between at least one data feature and at least one data node, the at least one data feature comprising the second data feature, and the at least one data node comprising the second data node.

5. The method of claim 4, wherein, If the second request message comprises the second data index, the second data node is determined according to the second data index and the first mapping relationship; if the second request message comprises the second data feature, the second data node is determined according to the second data feature and the second mapping relationship.

6. The method according to any one of claims 1 to 5, characterized in that, The routing management node has a capability of managing a topology relationship and transmission capability information, the topology relationship indicating an adjacency relationship between the first data node, the second data node and a third data node, the third data node being one or more data nodes passed through when the first data node and the second data node transmit the target data, and the topology relationship being used to determine the second data node and the third data node; the transmission capability information indicating transmission capability of at least one data node, and being used to establish a channel for transmitting the target data, the at least one data node comprising the second data node.

7. The method according to any one of claims 1 to 6, characterized in that, Before the first data node sends the target data to the service node, the method further comprises: the first data node sends a third request message to the second data node, the third request message being used to request data and / or to request to establish a channel for transmitting data; the first data node receives the target data from the second data node.

8. The method of claim 7, wherein, The third request message comprises information of the third data node, wherein the third data node is one or more data nodes passed through by the first data node and the second data node when transmitting the target data.

9. The method according to claim 7 or 8, characterized in that, When the first request message comprises a requirement parameter, the third request message further comprises a requirement parameter, wherein the requirement parameter is used for providing guarantee for transmission of the target data or is used for establishing a channel for transmitting the target data; and the requirement parameter comprises at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information used for instructing the service node to update the target data.

10. The method of claim 9, wherein, The requirement parameter comprises the first indication information; and the method further comprises: The first data node receives receiving address information from the second data node, wherein the receiving address information instructs the first data node to transmit the updated target data.

11. The method of claim 3, wherein, The second request message does not comprise the second data index and comprises the second data feature; and the method further comprises: The first data node receives second indication information from the routing management node, wherein the second indication information is used for instructing that data matched with the second data feature is not collected.

12. A communication method characterized by comprising: Comprise: The routing management node receives a second request message from the first data node, wherein the second request message is used for requesting a data node supporting access to data, and the second request message comprises a second data index and / or a second data feature; The routing management node sends information of a second data node to the first data node, wherein the second data node supports access to target data, the second data index points to the target data, and a feature of the target data matches the second data feature.

13. The method of claim 12, wherein, The method further comprises: The routing management node receives a registration request from at least one data node, wherein the registration request is used for registering at least one of the following: a first mapping relationship, a second mapping relationship, a topology relationship or transmission capability information; The first mapping relationship is a mapping relationship between at least one data index and at least one data node, the at least one data index comprises the second data index, and the at least one data node comprises the second data node; the second mapping relationship is a mapping relationship between at least one data feature and at least one data node, the at least one data feature comprises the second data feature, and the at least one data node comprises the second data node; the topology relationship instructs an adjacency relationship between the first data node, the second data node and a third data node, the third data node is one or more data nodes passed through by the first data node and the second data node when transmitting data, and the topology relationship is used for determining the second data node and the third data node; and the transmission capability information instructs transmission capability of the at least one data node and is used for establishing a channel for transmitting data.

14. The method of claim 13, wherein, Before the routing management node sends the information of the second data node to the first data node, the method further comprises: The routing management node determines information of the second data node according to the at least one.

15. The method according to claim 13 or 14, characterized in that, The method further comprises: The routing management node determines information of the third data node according to the at least one; The routing management node sends the information of the third data node to the first data node.

16. The method of claim 15, wherein, The second request message further comprises a requirement parameter, the requirement parameter being used for providing guarantee for transmission of data, or being used for establishing a channel for transmitting data; The routing management node determines information of the third data node according to the at least one, comprising: The routing management node determines information of the third data node according to the at least one and the requirement parameter; The requirement parameter comprises at least one of transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, the first indication information being used for indicating that the service node updates the target data.

17. A method of communication, comprising: Comprising: The service node sends a first request message to a first data node, the first request message being used for requesting data, the first request message comprising a first data index and / or a first data feature; The service node receives target data from the first data node, the target data being acquired from a second data node according to the first data index and / or the first data feature, the second data node supporting access to the target data, the first data index pointing to the target data, and a feature of the target data matching the first data feature.

18. A method of communication, comprising: Comprising: A second data node receives a third request message from a first data node, the third request message being used for requesting data; The second data node acquires target data; The second data node sends the target data to the first data node.

19. The method of claim 18, wherein, The third request message comprises a second data feature; the second data node acquires target data, comprising: The second data node sends a fourth request message to a data production node according to the third request message, the fourth request message being used for requesting to collect data, wherein the data production node is related to the second data feature; The second data node receives the target data.

20. The method of claim 19, wherein, The fourth request message comprises a receiving address of the second data node and / or a receiving address of a data storage node; if the fourth request message comprises the receiving address of the second data node, the target data comes from the data production node; if the fourth request message comprises the receiving address of the data storage node, the target data comes from the data storage node.

21. The method of claim 19 or 20, wherein, The fourth request message comprises an index allocated by the second data node for the target data.

22. The method of claim 18, wherein, Before the second data node acquires target data, the method further comprises: The second data node receives a fifth request message from the data production node, the fifth request message being used for requesting to register the target data; The second data node sends a response message to the data production node, the response message indicating that the target data registration is successful, the response message including an index allocated to the target data by the second data node, the index allocated to the target data including a first data index.

23. The method of claim 22, wherein, The method further includes: The second data node sends the target data and the index allocated to the target data to a data storage node.

24. The method of any one of claims 18-23, wherein, The method further includes: The second data node sends a sixth request message to the data storage node, the sixth request message being used to request establishment of a channel for transmitting the target data; The second data node receives the target data from the data storage node through the channel.

25. A communication system, characterized by The communication system includes at least one of a first data node configured to perform the method of any one of claims 1-11, a routing management node configured to perform the method of any one of claims 12-16, a service node configured to perform the method of claim 17, or a second data node configured to perform the method of any one of claims 18-24.

26. A communications device, characterized by The apparatus includes means for performing the method of any one of claims 1-11, or means for performing the method of any one of claims 12-16, or means for performing the method of claim 17, or means for performing the method of any one of claims 18-24.

27. A communications device, characterized by The communication apparatus includes a processor and a memory, the memory being configured to store computer instructions, when the processor executes the instructions, to cause the method of any one of claims 1-11 to be performed, or to cause the method of any one of claims 12-16 to be performed, or to cause the method of claim 17 to be performed, or to cause the method of any one of claims 18-24 to be performed.

28. A computer-readable storage medium, characterized in that, The computer readable storage medium includes a computer program or instructions, when the computer program or instructions are run on a computer, to cause the computer to perform the method of any one of claims 1-11, or to cause the computer to perform the method of any one of claims 12-16, or to cause the computer to perform the method of claim 17, or to cause the computer to perform the method of any one of claims 18-24.

29. A computer program product, characterised in that, The computer program product includes a computer program or instructions, when the computer program or instructions are run on a computer, to cause the method of any one of claims 1-11 to be performed, or to cause the method of any one of claims 12-16 to be performed, or to cause the method of claim 17 to be performed, or to cause the method of any one of claims 18-24 to be performed.

Images