Communication method and device

Abstract

The invention provides a communication method and device. In the method, a first data node queries routing information through a routing management node to obtain information of a second data node, and further obtains target data through the second data node, so that transmission of the target data from the second data node to a service node can be realized, a data nearby access demand can be supported, and the data access efficiency is improved. The problem that large-scale data are difficult to transfer through signaling messages is solved, and the requirements of efficient data acquisition and low-delay access of service nodes in a future communication scene are met.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] In 5G mobile communication systems, a unified data layer is defined through the 5G protocol to support access to structured data such as subscription / policy / application data, and corresponding interface specifications are defined to clarify the parameters passed by the interfaces. For unstructured data that cannot be standardized, an unstructured data storage function (UDSF) and corresponding service capabilities are defined for unstructured data access.

[0003] In the aforementioned communication system, data access is mainly achieved through service-based interfaces, which support a limited amount of data transmission, making it difficult to meet the needs of large-scale data transmission and low-latency data access. Summary of the Invention

[0004] This application provides a communication method and apparatus that can meet the needs of large-scale data transmission and low-latency access to data.

[0005] Firstly, a communication method is provided, comprising: a first data node receiving a first request message from a service node, the first request message being used to request data retrieval; the first data node sending a second request message to a routing management node based on the first request message, the second request message being used to request access to a data node that supports data access; the first data node receiving information from the routing management node about a second data node that supports access to target data; and the first data node sending the target data to the service node, the target data being retrieved from the second data node.

[0006] Based on the method in the first aspect, the first data node queries the routing information through the routing management node to obtain information about the second data node that supports access to the target data. Then, the target data is obtained through the second data node. This enables the transmission of the target data from the second data node and the first data node to the business node, which can support the requirement of accessing data nearby. It can solve the problem that large-scale data is difficult to relay through signaling messages and meet the low-latency access requirements of business nodes.

[0007] Optionally, the first request message may 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 may be data index information transmitted based on a service-oriented interface, i.e., routing information, such as information obtained in advance by the business node based on business interactions. The first data feature may be feature information of the target data, used to indicate the features of the target data that the business node needs to obtain. Through the first request message, the business node can obtain the target data that matches the first data index and / or the first data feature, thereby fulfilling its requirement for data access based on proximity.

[0008] Optionally, the second request message may include a second data index and / or a second data feature, where 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 may be the same as or different from the first data index, and the second data feature may be the same as or different from the first data feature. It should be understood that if the first request message does not include the first data index, the second request message may include the second data index. The first data node can construct the second data index based on the first data feature, and can also complete / update the first data feature to obtain the second data feature. This allows the first data node to query the routing management node for a data node (such as the second data node) that matches the second data index and / or the second data feature. The second data index and / or the second data feature may be more complete than the first data index and / or the first data feature, thereby obtaining more accurate information about the data node (such as the second data node).

[0009] Optionally, the routing management node has metadata management capabilities, 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 a second data index, and the at least one data node includes a 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 a second data feature, and the at least one data node includes a second data node.

[0010] The metadata management capabilities here include routing management, which is essentially the function of managing the first mapping relationship. The first mapping relationship can be a mapping between a domain-internal data index (at least one of the aforementioned data indexes) and a data node (at least one of the aforementioned data nodes). Metadata management capabilities also include the ability to manage the second mapping relationship, that is, the ability to manage the mapping between metadata features (at least one of the aforementioned data features) and data nodes (at least one of the aforementioned data nodes). Thus, by leveraging the metadata management capabilities of the routing management node, accurate routing query capabilities are provided for the first data node, thereby improving the accuracy of determining the second data node.

[0011] Optionally, the routing management node can also maintain information on the data nodes' capabilities for data transmission metrics to support the addressing of target nodes that meet the requirements.

[0012] Optionally, if the second request message includes a second data index, the second data node is determined based on 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 based on the second data feature and the second mapping relationship. That is, if the second request message includes a 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 includes a second data feature, the routing management node determines the second data node corresponding to the second data feature from the second mapping relationship.

[0013] Optionally, if the second request message includes a second data index and a second data feature, then the second data node is determined based on the second data index and the first mapping relationship, as well as the second data feature and the second mapping relationship.

[0014] In this way, the second data node is determined based on the different contents of the second request message, which improves the flexibility of determining the second data node.

[0015] Optionally, the routing management node has the ability to manage topology relationships and transmission capacity information. The topology relationship indicates the adjacency relationship between the first data node, the second data node, and the third data node. The third data node is one or more data nodes that are passed through when transmitting target data 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 capacity information indicates the transmission capacity of at least one data node and is used to establish a channel for transmitting target data. The at least one data node includes the second data node.

[0016] It is understandable that the topology is used to determine the second and third data nodes, that is, to determine the channel for transmitting the target data. Transmission capability information may include, for example, the bandwidth capacity, scheduling capability, resource utilization, and reverse channel capability of at least one data node. This transmission capability information is used to establish the channel for transmitting the target data, ensuring that the transmission capability information of the second data node determined by the routing management node meets the requirements. Furthermore, the transmission capability information of all nodes involved in the channel for transmitting the target data, such as the first and third data nodes, must also meet the requirements.

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

[0018] Optionally, the channel may include a relay channel and / or an update channel; the relay channel is used to transmit target data between the second data node and the first data node; the update channel is used to transmit updated target data between the second data node and the first data node.

[0019] It is understandable that the relay channel and / or update channel are established after the second data node receives the third request message and grants data access permissions. The relay channel is used to transmit the target data from the second data node to the first data node after its establishment, while the update channel is used for transmitting the updated target data between the business node, the first data node, and the second data node after the business node updates the target data. Transmitting target data through the relay channel and / or update channel can meet the needs of large-scale data transmission and low-latency data access.

[0020] Optionally, the channel includes a relay channel and / or an update channel; the relay channel is used to transmit 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; the update channel is used to transmit updated target data between the data storage node, the second data node, and the first data node.

[0021] It is understandable that the target data can be stored on the data storage node instead of the second data node. Therefore, after receiving the third request message, the second data node performs data access permission verification, and upon successful verification, requests the establishment of a relay channel and / or update channel from the backend data storage node. This establishes a relay channel and / or update channel between the data storage node, the second data node, and the first data node. Transmitting the target data through the relay channel and / or update channel can meet the needs of large-scale data transmission and low-latency data access.

[0022] Optionally, if the first request message includes requirement parameters, the third request message may also include requirement parameters, which are used to provide guarantees for the transmission of target data, or to establish a channel for transmitting target data; the requirement parameters include at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, which is used to instruct the service node to update the target data.

[0023] In other words, when transmitting target data between the first data node and the second data node, the required parameters must be met. Or, the channel between the first data node and the second data node used to transmit target data must meet the required parameters to improve transmission performance.

[0024] Optionally, if the requirement parameters include the first indication information, the communication method may further include: a first data node receiving receive address information from a second data node, the receive address information instructing the first data node to transmit updated target data. The first data node can determine the destination address for the updated target data through the receive address information, thereby ensuring that the transmission of the updated target data can be achieved.

[0025] The receiving address information of the second data node may also include the timeliness information of the address of the second data node, or the first data node may receive the address timeliness information from the second data node to instruct the first data node to complete the transmission of the updated target data before the address of the second data node expires.

[0026] In one possible implementation, the third request message includes information about a third data node, which is one or more data nodes traversed during the transmission of target data between the first and second data nodes. Optionally, the routing management node determines the third data node based on at least one of the above, namely, the first mapping relationship, the second mapping relationship, the topology relationship, or the transmission capacity information, and sends the 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.

[0027] Optionally, the channel may include a relay channel and / or an update channel; the relay channel is used to transmit target data between the second data node, the third data node and the first data node; the update channel is used to transmit updated target data between the first data node, the third data node and the second data node.

[0028] Optionally, the channel includes a relay channel and / or an update channel; the relay channel is used to transmit 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 to transmit updated target data between the first data node, the third data node, the second data node and the data storage node.

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

[0030] Optionally, the first data node sending a third request message to the second data node may include: the first data node sending a third request message to the second data node through the third data node.

[0031] It can be understood that the process by which the routing management node determines the second and third data nodes is also the process of determining the channel / path for data transmission, or the data orchestration process. The third request message can be sent via the third data node to achieve hop-by-hop channel establishment. The third request message may contain information about the third data node, and the third data node performs resource reservation / channel establishment based on the third request message.

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

[0033] It is understandable that if the second request message does not include the second data index but includes the second data feature, there may be cases where target data is not collected. In this case, the routing management node indicates to the first data node that data matching the second data feature has not been collected, and sends a second data node to the first data node. At this time, the second data node is a node that has not collected data matching the second data feature, but is capable of collecting data matching the second data feature. This application embodiment provides a method for obtaining target data by collecting data matching the second data feature through a second data node when data matching the second data feature has not been collected.

[0034] Secondly, a communication method is provided, the method comprising: a service node sending a first request message to a first data node, the first request message being used to request data, the first request message including a first data index and / or a first data feature; the service node receiving 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 feature of the target data matching the first data feature.

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

[0036] Thirdly, a communication method is provided, the method comprising: a routing management node receiving a second request message from a first data node, the second request message being used to request a data node that supports access to data, the second request message including a second data index and / or a second data feature; the routing management node sending information about 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 feature of the target data matching the second data feature.

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

[0038] The first mapping relationship is a mapping relationship between at least one data index and at least one data node, wherein the at least one data index includes a second data index and the at least one data node includes a second data node; the second mapping relationship is a mapping relationship between at least one data feature and at least one data node, wherein the at least one data feature includes a second data feature and the at least one data node includes a second data node; 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 traversed when transmitting data between the first data node and the second data node, and the topology relationship is used to determine the second data node and the third data node; the transmission capability information indicates the transmission capability of at least one data node and is used to establish a channel for transmitting data.

[0039] Optionally, before the routing management node sends the information of the second data node to the first data node, the method further includes: the routing management node determining the information of the second data node based on at least one of the following:

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

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

[0049] In another possible implementation, before the second data node obtains the target data based on the first data feature, the method further includes: the second data node receiving a fifth request message from the data producer node, the fifth request message being used to request the registration of the target data; the second data node sending a response message to the data producer node, the response message indicating that the target data registration was successful, the response message including an index allocated by the second data node for the target data, the index allocated for the target data including the first data index.

[0050] Optionally, the method also includes: the second data node sending the target data and the index assigned to the target data to the data storage node.

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

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

[0053] Fifthly, a communication device is provided. The communication device includes a processor configured to perform the method according to any one of the embodiments of the first to fourth aspects.

[0054] In one possible implementation, the communication device described in the fifth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.

[0055] In one possible implementation, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the methods of any of the embodiments of the first to fourth aspects.

[0056] Furthermore, the technical effects of the communication device described in the fifth aspect can be referred to the technical effects of any of the embodiments in the first to fourth aspects, and will not be repeated here.

[0057] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory, causing the communication device to perform the method of any one of the embodiments of the first to fourth aspects.

[0058] In one possible implementation, the communication device may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0059] In one possible implementation, the communication device further includes the memory for storing the aforementioned computer program or instructions. Optionally, the memory and processor are integrated together.

[0060] Furthermore, the technical effects of the communication device described in the sixth aspect can be referred to the technical effects of any of the embodiments in the first to fourth aspects, and will not be repeated here.

[0061] In a seventh aspect, a communication system is provided. The communication system includes a first data node, a service node, a routing management node, and a second data node. The first data node is configured to execute the method described in any embodiment of the first aspect; the service node is configured to execute the method described in any embodiment of the second aspect; the routing management node is configured to execute the method described in any embodiment of the third aspect; and the second data node is configured to execute the method described in any embodiment of the fourth aspect.

[0062] Eighthly, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed, causing the method as described in any of the first to fourth aspects above to be implemented.

[0063] Ninth aspect, a computer program product is provided, including a computer program or instructions that, when executed, cause the method as described in any of the first to fourth aspects above to be implemented. Attached Figure Description

[0064] Figure 1 This is a schematic diagram of the 5G network architecture;

[0065] Figure 2 A schematic diagram of the 5G unified data layer;

[0066] Figure 3 This is a schematic diagram of an intelligent analytics architecture;

[0067] Figure 4 This is a schematic diagram illustrating a vision of future communication scenarios;

[0068] Figure 5 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 1 ;

[0069] Figure 6 A schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable. Figure 2 ;

[0070] Figure 7 A schematic diagram of the communication method provided in the embodiments of this application Figure 1 ;

[0071] Figure 8 A schematic diagram of a data transmission channel provided in an embodiment of this application;

[0072] Figure 9 This is a schematic diagram of data link orchestration provided for an embodiment of this application;

[0073] Figure 10 A schematic diagram of the communication method provided in the embodiments of this application Figure 2 ;

[0074] Figure 11 A schematic diagram of the communication method provided in the embodiments of this application Figure 3 ;

[0075] Figure 12 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0076] Figure 13 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0077] The technical solutions of this application embodiment can be applied to various communication systems, such as Wireless Fidelity (Wi-Fi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as Long Term Evolution (LTE) systems, Worldwide Interoperability for Microwave Access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as New Radio (NR) systems, and future communication systems.

[0078] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0079] 1. 5G network architecture:

[0080] Figure 1 This is a schematic diagram of the 5G network architecture. Figure 1 As shown, this architecture mainly includes an access network (AN) and a network core (CN). Figure 1 (not shown in the diagram), and may also include: a terminal. The main functional descriptions of each network element in this architecture are as follows:

[0081] There may be one or more terminals. A terminal may be a terminal with transceiver functions, or it may be a chip or chip system installed in the terminal. The terminal may also be referred to as UE, access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, and roadside units with terminal functions. The terminal in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit that is built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in D2D communication.

[0082] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0083] The aforementioned AN (Access Network Adapter) is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission links of different quality based on user level and service requirements to transmit user data. The AN forwards control signals and user data between the terminal and the CN (Radio Access Network). The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data and providing terminals with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: User Plane Function (UPF) network element, Authentication Server Function (AUSF) network element, Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, Network Slice Selection Function (NSSF) network element, Network Exposure Function (NEF) network element, Network Function Repository Function (NRF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM) network element, Unified Data Repository (UDR) network element, and Application Function (AF).

[0084] RAN equipment, also known as access network device, can be one or more. An access network device can be a device with wireless transceiver capabilities, or it can be a chip or chip system located within the device, situated in the access network (AN) of the communication system, to provide access services to terminals. For example, an access network device can be called a radio access network (RAN) device, and it can be part of a future mobile communication system. In future mobile communication systems, access network devices may also have other naming conventions, all of which are covered within the protection scope of the embodiments of this application, and this application does not impose any limitations on them. Alternatively, the access network device may also include 5G, such as a gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it may be a network node constituting a gNB, a transmission and reception point (TRP) or transmission point (TP), or a transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), an RSU with base station functionality, or a wired access gateway, or a 5G core network element, etc. Alternatively, the access network device may also include: an access point (AP) in a 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 cells), relay stations, access points, wearable devices, vehicle-mounted equipment, etc.

[0085] In this network, CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). RU can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network equipment can be CU nodes, DU nodes, or a combination of CU and DU nodes. Furthermore, CUs can be classified as network equipment in the access network (RAN) or in the core network (CN); there are no restrictions on this classification.

[0086] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0087] UPF network elements are primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF network element can receive user data from a data network (DN) and forward that data to the terminal through access network equipment. A UPF network element can also receive user data from the terminal through access network equipment and forward that data to the DN. A DN network element refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP), IP Multimedia Service (IMS), and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminal devices.

[0088] The AUSF network element is mainly used to perform security authentication for terminals.

[0089] AMF network elements are primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0090] SMF network elements are primarily used for session management in mobile networks. This includes functions such as session establishment, modification, and release. Other functions include assigning IP addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0091] The PCF network element primarily supports providing a unified policy framework to control network behavior, delivering policy rules to control layer network functions, and acquiring user subscription information related to policy decisions. The PCF network element can provide policies to AMF and SMF network elements, such as Quality of Service (QoS) policies and slice selection policies. In this architecture, the PCFs connected to the AMF and SMF correspond to the PCF for access and mobility control (AM PCF) and the PCF for session management (SMPCF), respectively, and may not be the same PCF entity in actual deployment scenarios.

[0092] NSSF network elements are mainly used to select network slices for terminals.

[0093] NEF network elements are primarily used to support the opening of capabilities and events.

[0094] UDM network elements are mainly used to store user data, such as subscription data and authentication / authorization data.

[0095] UDR network elements are mainly used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0096] The Application Front-End (AF) primarily supports interaction with the Core Network (CN) to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. Optionally, the AF can provide Personal Identification Number (PIN) services, also known as PIN-AF. The AF is also used to convey application-side requests 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 the operator, such as IMS voice call services. For third-party application functional entities, authorization processing can also be performed through the Network Entity Framework (NEF) when interacting with the core network. For example, a third-party application function can directly send a request message to the NEF. The NEF determines whether the AF is allowed to send the request message. If the verification is successful, the request message will be forwarded to the corresponding PCF or UDM.

[0097] The functionalities of each interface in this architecture are described below:

[0098] N7: The interface between PCF and SMF, used to issue protocol data unit (PDU) session granularity and service data stream granularity control policies. The PDU session is a session service used to achieve PDU connectivity between the UE and the data network, identified by PDU session identity (session ID) information.

[0099] N15: The interface between PCF and AMF, used to issue UE policies and access control related policies.

[0100] N5: The interface between AF and PCF, used for issuing application service requests and reporting network events.

[0101] N4: The interface between SMF and UPF, used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0102] N11: The interface between SMF and AMF, used to transmit PDU session tunnel information between RAN and UPF, transmit control messages sent to UE, and transmit radio resource control information sent to RAN, etc.

[0103] N2: The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to the RAN.

[0104] N1: The interface between AMF and UE, access-independent, used to transmit QoS control rules to UE, etc.

[0105] N8: The interface between AMF and UDM, used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, as well as by AMF to register UE's current mobility management information with UDM.

[0106] N10: The interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.

[0107] N35: The interface between UDM and UDR, used by UDM to obtain user subscription data information from UDR.

[0108] N36: The interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data related information from UDR.

[0109] N52: The interface between UDM and NEF, used by 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.

[0110] In addition, NEF also has direct interfaces with AMF and SMF, corresponding to the N29 interface and N51 interface respectively. Figure 1 (Not shown in the image) is used to open up operator network capabilities to third-party application function entities. The former can be used by NEF to directly subscribe to corresponding network events from AMF and update user configuration information, while the latter can be used to update application configuration data on SMF / UPF, such as packet flow description (PFD) information corresponding to the application ID.

[0111] The general user registration process can be simply described as follows: The UE sends a registration request to the AMF via the AN. The AMF obtains subscription data from a specific UDM based on the user identifier. Upon receiving the request, the UDM can obtain the actual subscription data from the UDR. 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 to obtain UE policies and access control policies, respectively. During this process, the PCF returns the access control policy to the AMF, which then provides the UE policy to the UE.

[0112] 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 an SMF to provide services for the session, saves the mapping between the SMF and PDU sessions, and sends the session establishment request to the SMF. The SMF selects the appropriate UPF for the UE, establishes a user plane transmission path, and assigns an IP address. During this process, the SMF also initiates a policy control session establishment request to the PCF to establish a policy control session between the SMF and PCF. During the policy control session establishment process, the SMF saves the mapping between the policy control session and the PDU session. In addition, the AF can also establish an AF session with the PCF, and the PCF binds the AF session to the policy control session.

[0113] It should be noted that this application uses a 5G system as an example to introduce the relevant technical solutions, but the application of these technical solutions is not limited to 5G systems. It is understood that these technical solutions may also be applicable to future communication systems.

[0114] 2. Data Nodes

[0115] Figure 2 This is a schematic diagram of the 5G unified data layer. Figure 2 As shown, the 5G protocol defines a unified data layer to support access to data such as subscription data, policy data, structured development data, and application data, and defines corresponding interface specifications to clarify the parameters passed by the interfaces. Figure 2 The UDM function element (FE), PCF FE, and NEF FE access data from the data access provider in the UDR network element through the Nudr interface. For unstructured data that cannot be standardized, the UDSF function and corresponding service capabilities are defined for unstructured data access. For example... Figure 2 Other network functions (anyNF) access data from UDSF network elements through the Nudsf interface.

[0116] The subscription data consists of static user subscription data, corresponding to user subscriptions stored in the UDM / UDR. Policy data comprises user policy subscription data, including UE / AM / SM policy subscriptions. Structured open data refers to dynamic data (structured data) that needs to be made available. Application data includes application-related data, such as user plane routing information and application description information.

[0117] The aforementioned data access is mainly achieved through the two service interfaces, Nudr and Nudsf, and the amount of data to be transmitted is relatively limited, typically only a few KB to tens of KB.

[0118] In addition to the data mentioned above, 5G networks have introduced network data analytics function (NWDAF) network elements for intelligent analysis capabilities, and defined corresponding data collection mechanisms for analysis inference / model training needs.

[0119] Figure 3 This is a schematic diagram of an intelligent analytics architecture. Figure 3 As shown, the functions of each node are briefly described below:

[0120] The analytics data repository function (ADRF) network element has data storage capabilities and is used to store the collected raw data, analysis results data, and models.

[0121] The Data Collection Coordination Function (DCCF) network element is used for unified collection and open access to data.

[0122] The Message Framework Adaptor Function (MFAF) is a message bus used for message passing.

[0123] The Model Training Logical Function (MTLF) network element has a model training function.

[0124] The analytics logical function (AnLF) network element has data analysis capabilities and is used to obtain models from the MTLF network element. The NWDAF network element can provide machine learning (ML) model provisioning (Nnwdaf_MLModelProvision) services.

[0125] In this scenario, based on the concept of separating business logic from data, an independent data storage and exchange framework is defined, oriented towards the upper-layer business logic (i.e., Figure 3 The system provides services through NF nodes to achieve unified data collection and openness. Furthermore, the model training and data analysis functions have also been functionally separated.

[0126] However, in this architecture, apart from the non-standardized data acquisition interface between the messaging framework and the data source, the interface provided to the upper layer through the MFAF network element is still a service-oriented interface, which is difficult to meet the needs of large-scale data transmission.

[0127] 3. Future Data Function Requirements Analysis

[0128] Future communication scenarios may be expanded on the basis of existing 5G communication scenarios, such as introducing AI+communication, ubiquitous connectivity and integrated communication sensing capabilities.

[0129] Figure 4 This is a schematic diagram illustrating a vision of future communication scenarios. (For example...) Figure 4 As shown, future communication scenarios require the introduction of capabilities such as immersive communication, artificial intelligence plus (AI+) communication, ultra-reliable low-latency communication, ubiquitous connectivity, mass communication, and integrated communication and sensing.

[0130] For sensing scenarios, taking point cloud data reporting as an example, the bandwidth required for point cloud data reported by a single base station for a single target is approximately several Mbps. If multiple targets are involved, the bandwidth will increase proportionally. This bandwidth requirement far exceeds the capacity (approximately tens of Kbps) provided by existing service-oriented interface signaling messages.

[0131] For network digital twin scenarios, taking digital experience maps as an example, key indicators need to be obtained from each base station / UPF, with an estimated data scale of tens of millions. It needs to support second-level query latency and graph data storage, and the resulting data acquisition bandwidth requirements will far exceed the capabilities that existing networks can provide.

[0132] For immersive communication scenarios, the network side needs to maintain a personalized intelligent assistant at the user level, and needs to meet the access requirements of corresponding long-term and short-term memory data. The short-term memory is approximately several MB to tens of MB, and the long-term / important memory is approximately several KB. The call involves long-term / short-term memory retrieval processes, and there are latency requirements for the response to the results.

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

[0134] 4. Evolutionary Requirements Analysis

[0135] Key differences between new data in future scenarios and existing 5G data services:

[0136] Data scale: New types of data may reach tens of MB (such as user short-term memory data) or even several GB (such as base station sensing point cloud data), while the original contracted data is usually tens of KB.

[0137] Data availability: Due to data collection latency or differences in business scenarios, there is a need for asynchronous interaction between the two ends of the data service; the existing data mechanism is usually implemented by SBI real-time interaction / delayed subscription.

[0138] Timeliness differences: Existing data transmission is usually achieved through the signaling plane, while the data latency of newly added data types in future scenarios will vary significantly;

[0139] In future scenarios where various large-scale structured / unstructured data may be introduced, the network needs to provide data service capabilities to support the flow of this data within the network, so as to meet the business's needs for efficient data collection and low-latency access.

[0140] To address the aforementioned technical problems, the embodiments of this application propose the following technical solutions.

[0141] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0142] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a correlation between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0143] Furthermore, the specific instruction method can also be any existing instruction method, such as, but not limited to, the above-mentioned instruction methods and their various combinations. As described above, for example, when multiple pieces of information of the same type need to be indicated, the instruction methods for different pieces of information may differ. In the specific implementation process, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that enable the party to be instructed to obtain the information to be indicated.

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

[0145] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device sending information to logical module 2 in the network device.

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

[0147] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0148] "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0149] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0150] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0151] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or implementation described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or implementations. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0152] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0153] To facilitate understanding of the embodiments of this application, let's first take... Figure 5 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 5 This is a schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application applies.

[0154] like Figure 5 As shown, the communication system mainly includes a first data node, a service node, and a routing management node.

[0155] The first data node can be a data management function (DMF) network element or entity, used to provide data access capabilities to service nodes based on proximity. The first data node can also be other network elements or entities that can implement data management functions, and this is not limited thereto. In the embodiments of this application, the first data node can also be replaced with other possible terms, such as a data management function node, a data management function network element, or a data management function entity, etc., and this is not limited thereto.

[0156] The service node is used to initiate data access requests to the first data node. For example, it can be a service control function (SCF) node, a service port function (SPF) node, etc. In the embodiments of this application, the service node can also be replaced with other possible terms, such as a data consumer node, a network function (NF) node, a service control function node, a service port function node, etc., which are not limited here.

[0157] The routing management node can be a routing management function (RMF) network element or entity, or other network elements or entities capable of implementing routing management functions, and is not limited herein. In the embodiments of this application, the routing management node can also be replaced with other possible terms, such as routing management function node, routing management function network element, or routing management function entity, etc., and is not limited herein.

[0158] In one possible scenario, for example Figure 6 As shown, the communication system includes RMF nodes, DMF nodes, data storage function (DSF) nodes, and service nodes (such as...). Figure 6 The communication system may also include internal signaling distribution function (ISDF) nodes, external signaling distribution function (ESDF) nodes, and global RMF nodes.

[0159] The RMF node manages the mapping relationship between the data index within the domain and the DMF / DSF nodes. Multiple RMF nodes can be directly connected, or they can communicate via a global RMF node for routing requests. In practical deployment scenarios, RMF nodes can be deployed near DSF nodes or serve as index storage nodes for DSF nodes.

[0160] 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.

[0161] 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.

[0162] 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.

[0163] 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.

[0164] 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.

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

[0166] Data Index

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

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

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

[0170] >>Read / write indicator bits (read-only, read&write, write only)

[0171] Example of a transmission packet header:

[0172] Source address, destination address, source port, destination port

[0173] >Transmission Requirement Index ID

[0174] >Path Node 1

[0175] >Path Node 2

[0176] >Path nodes 3..n

[0177] >>Node address or node address index

[0178] 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 path DMF nodes based on local information and the interaction interface between RMF nodes, and returns them to the DMF1 node. The target DMF node is a DMF node that supports the target data and can obtain the corresponding data from the data source (data source node or DSF node) and return it to the DMF1 node. The path DMF nodes are a list of nodes that support data transmission based on transmission requirements, serving as data transmission pipelines. Specifically, one or more path DMF nodes can act as data transmission proxies, providing only data relay capabilities without needing to provide complete data management capabilities.

[0179] In this communication system, the first data node queries routing information through the routing management node to obtain information about the second data node that supports access to the target data. Then, the target data is obtained through the second data node. This enables the transmission of the target data from the second data node and the first data node to the service node, which supports the requirement of accessing data nearby. It can solve the problem that large-scale data is difficult to relay through signaling messages and meet the low-latency access requirements of service nodes.

[0180] The following will combine Figures 7-10 This application provides a detailed description of the interaction process between various network elements / devices in the aforementioned communication system through method embodiments. The communication method provided in this application can be applied to the aforementioned communication system and specifically to various scenarios / processes mentioned in the aforementioned communication system, which will be described in detail below.

[0181] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 1 This communication method is applicable to the aforementioned communication system and mainly involves the interaction between the first data node, the service node, and the routing management node.

[0182] like Figure 7 As shown, the flow of this communication method is as follows:

[0183] 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.

[0184] The service node is used 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, SPF node, etc. In the embodiments of this application, the service node can also be replaced with other possible terms, such as data consumption node, network function node, service control function node, service port function node, etc., which are not limited here.

[0185] The first data node can be a DMF network element or entity, used to provide data access capabilities to service nodes based on proximity. The first data node can also be other network elements or entities capable of implementing data management functions, and is not limited here. In the embodiments of this application, the first data node can also be replaced with other possible terms, such as a data management function node, a data management function network element, or a data management function entity, etc., and is not limited here.

[0186] The first request message is used to request data. The data can be long-term memory and short-term memory data, integrated communication and sensing data, point cloud data, etc., without limitation. For example, in an integrated communication and sensing scenario, the service node sends a data request message (i.e., the first request message mentioned above) to the DMF1 node. The data request message is used to request integrated communication and sensing data, also known as synesthetic data.

[0187] It is understandable that the first request message can also be replaced with other possible expressions, such as data request message, data acquisition request message, data access request message, etc., without limitation.

[0188] Optionally, the business node determines the first data node based on local configuration information, service discovery information, and the routing addressing capability of the service data function (SDF), that is, to achieve the discovery of the first data node based on proximity. In other words, among multiple data nodes, the first data node can be the node closest to the business node.

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

[0190] The first data index can be data index information transmitted based on a service-oriented interface, i.e., routing information, such as information obtained in advance by business nodes based on business interactions. For example, a business node receives the first data index information through a business message. However, since the target data corresponding to the first data index cannot be directly obtained (e.g., the data size is too large to be transmitted through the service-oriented interface), the business node sends a first request message to the first data node, carrying the first data index.

[0191] It is understandable that the first data index can be a list of data indexes, i.e., containing multiple data indexes, or it can contain only one data index; there is no limitation here.

[0192] The first data feature can be characteristic information of the target data, used to indicate the characteristics of the target data that the business node needs to acquire. The first data feature can be one or more data features, without limitation. For example, it can include information such as the target data source (e.g., the data source node corresponding to the target data), the data type information of the target data, terminal location, and time window / location area restrictions. The target data source information can be a list of target data sources supported by nodes capable of data management, such as the first data node.

[0193] For example, taking a synesthetic scenario, the SCF / SPF node (i.e., the aforementioned service node) executes the DMF node discovery process based on the NRF configuration information, discovers the nearest DMF1 node, and further sends a data acquisition request message (i.e., the aforementioned first request message) to the DMF1 node. The data acquisition request message carries synesthetic data, and may also carry information such as the terminal location, the data source node corresponding to the terminal location, and the time window. Alternatively, the data acquisition request message may carry one or more data indexes (i.e., the aforementioned first data index), and the data indicated by these one or more data indexes is synesthetic data.

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

[0195] The routing management node can be an RMF network element or entity, or other network elements or entities capable of implementing routing management functions, and is not limited herein. In the embodiments of this application, the routing management node can also be replaced with other possible terms, such as a routing management function node, a routing management function network element, or a routing management function entity, etc., and is not limited herein.

[0196] The second request message is used to request access to data nodes that support data access. This second request message can be a request message for routing information lookup, such as a routing query request message sent by node DMF1 to node RMF1. The routing information lookup process may involve interaction between different routing management nodes in different domains, such as node RMF1 sending a routing query request message to node RMF2.

[0197] It is understandable that the data node that supports access to data can be a node with the same data management function as the first data node, that is, the second data node that supports access to the target data as described below.

[0198] It is understood that the second request message can also be replaced with other possible expressions, such as data access request message, routing information query request message, routing query request message, etc., without limitation.

[0199] S703, the routing management node sends the 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 routing management node.

[0200] The second data node supports access to the target data. The information of the second data node can include its address and identification information. It may also include the data type maintained by the second data node, the data type that the second data node can collect, and the data source nodes that the second data node can connect to.

[0201] S704, the first data node sends the target data to the service node.

[0202] The target data is obtained from the second data nodes. There can be multiple second data nodes, and the target data can include data obtained from different second data nodes. Different second data nodes can correspond to different second data features.

[0203] In summary, the first data node queries routing information through the routing management node to obtain information about the second data node, and then obtains the target data through the second data node. This enables the transmission of target data from the second data node to the business node, supports the requirement of data access by proximity, solves the problem that large-scale data is difficult to relay through signaling messages, and meets the requirements of business nodes for efficient data collection and low-latency access in future communication scenarios.

[0204] The S702 will be described in detail below.

[0205] Optionally, prior to S702, the first data node performs an access permission pre-verification on the service node based on the first request message to determine that the service node has the necessary access permissions. Then, it sends a second request message to the routing management node.

[0206] For example, the DMF1 node performs access permission pre-verification based on the mapping relationship between data and access permission roles stored in its local configuration or by other nodes (such as UDM or RMF) to confirm that the service node has the necessary access permissions. For instance, based on the mapping relationship between the service node and the supported data features, it determines that the service node can access the data corresponding to the data feature in the first request message. Alternatively, based on the access permission control information between the service node and the data node / network element, it determines 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.

[0207] The following sections describe scenario 1, where the target data has been collected / prepared, and scenario 2, where the target data has not been collected / prepared.

[0208] Scenario 1:

[0209] In one possible implementation, the second request message includes a second data index and / or a second data feature, the second data index pointing to target data, and the feature of the target data matching the second data feature.

[0210] The second data index may be the same as or different from the first data index. The second data index can be a list of data indexes, i.e., it contains multiple data indexes, or it may contain only one data index; there is no limitation on this.

[0211] For example, a first data node receives a first request message, which includes a first data index and a first data feature. The first data node constructs a second data index based on the first data feature. If the number of second data indices is greater than the number of first data indices, the first data node sends a second request message to the routing management node based on the second data index and the first data feature.

[0212] It should be understood that if the first request message does not include the first data index, the second request message may include the second data index.

[0213] For example, a first data node receives a first request message, which includes a first data feature. The first data node constructs a second data index based on the first data feature, and then sends a second request message to the routing management node based on the second data index and the first data feature.

[0214] The second data feature may be the same as or different from the first data feature. The second data feature may be one or more data features, without limitation.

[0215] For example, a first data node receives a first request message, which includes a first data index and a first data feature. The first data node completes / updates the first data feature to obtain a second data feature. Then, based on the first data index and the second data feature, it sends a second request message to the routing management node.

[0216] For example, the first data node receives a first request message, which includes a first data feature. The first data node completes / updates the first data feature to obtain a second data feature. Based on the second data feature, the first data node then sends a second request message to the routing management node.

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

[0218] In this way, the first data node can query the routing management node to find a data node (such as the second data node) that matches the second data index and / or the second data feature. 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 about the data node (such as the second data node).

[0219] Optionally, the routing management node has metadata management capabilities, 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 may include a second data index, and the at least one data node may include a 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 a second data feature, and the at least one data node includes a second data node.

[0220] The metadata management capabilities here include routing management functionality, which is essentially the function of managing the first mapping relationship. The first mapping relationship can be a mapping relationship between a data index within the domain (at least one of the aforementioned data indexes) and a data node (at least one of the aforementioned data nodes).

[0221] The first mapping relationship is updated through at least one data node or data storage node. For example, the routing management node receives a routing database update instruction from at least one data node or data storage node, thereby updating the first mapping relationship between at least one data index and at least one data node. The data storage node can be a DSF network element or entity, or other network elements or entities capable of data storage functions; no limitation is made here.

[0222] Optionally, the first mapping relationship may also include a mapping relationship between at least one data index and at least one data storage node.

[0223] In the embodiments of this application, the data storage node can also be replaced with other possible terms, such as data storage function node, data storage function network element, data storage function entity, etc., which are not limited here.

[0224] Metadata management capabilities also include the ability to manage a second mapping relationship, that is, the ability to manage the mapping relationship between metadata features (at least one of the aforementioned data features) and data nodes (at least one of the aforementioned data nodes).

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

[0226] In this embodiment of the application, the data source node can be a data producer (DP) node.

[0227] In this way, by leveraging the metadata management capabilities of the routing management node, accurate routing query capabilities are provided for the first data node, thereby improving the accuracy of determining the second data node.

[0228] To meet service transmission requirements, routing management nodes may also be involved in maintaining the data node's capability information for data transmission metrics, in order to support the addressing of target nodes that meet the requirements. For example, after receiving a routing query request from DMF1 node, RMF node determines that the data transmission metrics capability of DMF2 node meets the query requirements of DMF1 node, and then sends the address information of DMF2 node to DMF1 node.

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

[0230] Optionally, if the second request message includes a second data index, the second data node is determined based on 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 based on the second data feature and the second mapping relationship.

[0231] In other words, if the second request message includes a 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 includes a 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 nodes, DMF3 nodes, DMF4 nodes, etc. For example, if there are multiple second data indices, there will be multiple second data nodes.

[0232] Optionally, if the second request message includes a second data index and a second data feature, then the second data node is determined based on the second data index and the first mapping relationship, as well as the second data feature and the second mapping relationship.

[0233] In cases where there are multiple second data features, there are multiple second data nodes.

[0234] For example, the second request message includes both a second data index and a 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 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 both at least one data node #1 and at least one data node #2.

[0235] In this way, the second data node is determined based on the different contents of the second request message, which improves the flexibility of determining the second data node.

[0236] Optionally, the routing management node has the ability to manage topology and transmission capacity information. The topology 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 that are traversed when transmitting target data between the first data node and the second data node.

[0237] It is understandable that the topology is used to determine the second and third data nodes, that is, to determine the channel for transmitting the target data. The third data node, as one or more data nodes in the path of the channel (such as DMF nodes), can act as a data transmission proxy, providing only data relay capabilities, without needing to provide full data management capabilities.

[0238] Transmission capability information indicates the transmission capability of at least one data node, used to establish a channel for transmitting target data. This at least one data node includes a second data node. Alternatively, it may include a first data node and a third data node. Transmission capability information may include, for example, the bandwidth capacity, scheduling capability, resource utilization, and reverse channel capability of each of the at least one data node. The transmission capability information is used to establish the channel for transmitting target data, and the transmission capability information of the second data node determined by the routing management node meets the requirements. Furthermore, the transmission capability information of all nodes involved in the channel for transmitting target data, such as the first data node and the third data node, must also meet the requirements.

[0239] Before the routing management node sends the information of the second data node to the first data node in S703, the communication method may further include: the routing management node receiving a registration request from at least one data node, the registration request being used to request registration of at least one of the following: a first mapping relationship, a second mapping relationship, a topology relationship, or transmission capability information.

[0240] The first mapping relationship, second mapping relationship, topology relationship, and transmission capacity information can be found in the above description and will not be repeated here. The topology relationship can be configured locally by the routing management node.

[0241] It is understood that at least one data node periodically registers data mapping information with the routing management node based on heartbeat signaling, either in full or incremental form. This data mapping information may include a first mapping relationship, a second mapping relationship, a topology relationship, or transmission capacity information. Therefore, upon receiving a data query request (i.e., a second request message), the routing management node can determine the information of the second data node based on at least one of the above, thus correctly performing data node query and data link orchestration. Here, data link orchestration may involve establishing a channel for data transmission. Additionally, the routing management node determines the information of the second data node based on at least one of the above and its local configuration information.

[0242] It can be understood that the routing management node performs a node query based on the information registered by at least one data node received, 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 at least one DMF node and data features / data indexes, and then returns the information of the DMF2 node to the DMF1 node.

[0243] Scenario 2:

[0244] In another possible implementation, the second request message does not include the second data index but includes the second data feature; the communication method may also 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 has not been collected.

[0245] It is understandable that if the second request message includes the second data index, it indicates that data corresponding to the second data index exists, meaning that the target data indicated by the second data index has been collected. Therefore, if the second request message does not include the second data index but includes the second data feature, there may be cases where the target data has not been collected. In this case, the routing management node indicates to the first data node that the data matching the second data feature has not been collected, and sends the second data node to the first data node. At this time, the second data node is the node that has not collected the data matching the second data feature, but is capable of collecting the data matching the second data feature.

[0246] For example, if an RMF node receives a routing query request message (second request message) from a DMF1 node and determines that data matching the second data feature carried in the routing query request message has not yet been collected, the response message may return one or more related DMF nodes, as well as a data not collected indication to the DMF1 node. Optionally, the RMF node may 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.

[0247] Optionally, after receiving information from the second data node of the routing management node, the first data node sends a third request message to the second data node. 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 includes the second data feature. The second data node sends a fourth request message to the data production node based on the third request message. The fourth request message is used to request data collection. The data production node is associated with the second data feature. The second data node receives the target data and sends the target data to the first data node.

[0248] It is understandable that after receiving the third request message, the second data node performs a data access permission verification. Upon successful verification, it sends a fourth request message, i.e., a data acquisition request, to one or more data production nodes. For example, the DMF2 node sends data acquisition request #1 to the DP1 node and data acquisition request #2 to the DP2 node. The data production nodes are related to the second data characteristic; that is, the data generated by the data production nodes matches the second data characteristic. There can be one or more data production nodes, without limitation.

[0249] The fourth request message may include a receiving address and allocated index information. The receiving address can be the address of the second data node or the address of the data storage node. The allocated index information can be an index assigned by the second data node to this fourth request message, used to index 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 assigns a data index #1 to this data collection request #1, so that the data collected from the DP1 node corresponds to data index #1; it sends a data collection request #2 to the DP2 node and assigns a data index #2 to this data collection request #2, so that the data collected from the DP2 node corresponds to data index #2.

[0250] Subsequently, 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. Furthermore, if the collected data needs to be relayed through a data storage node, a data relay request is also initiated to the data storage node, carrying the receiving address of the second data node.

[0251] The S704 will be described in detail below.

[0252] First, we will introduce two methods for the first data node and the second data node to transmit the third request message.

[0253] Method 1: Transmit the third request message using a seamless transit point method.

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

[0255] The third request message may include a second data index and / or a second data feature, used to indicate that data matching the second data index and / or the second data feature needs to be retrieved from the second data node.

[0256] The channel used for data transmission can be used to transmit target data. Optionally, the first data node receives target data from the second data node through this channel.

[0257] Optionally, the channel may include a relay channel and / or an update channel; the relay channel is used to transmit target data between the second data node and the first data node; the update channel is used to transmit updated target data between the second data node and the first data node.

[0258] It is understood that the relay channel and / or update channel are established after the second data node receives the third request message and grants data access permissions. The relay channel is used to transmit the target data from the second data node to the first data node after it is established, while the update channel is used to transmit the updated target data between the business node, the first data node, and the second data node after the business node updates the target data.

[0259] Optionally, the channel includes a relay channel and / or an update channel; the relay channel is used to transmit 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; the update channel is used to transmit updated target data between the data storage node, the second data node, and the first data node.

[0260] It is understandable that the target data can be stored on the data storage node instead of the second data node. Therefore, after the second data node receives the third request message, it performs data access permission verification and, after the verification is successful, requests the establishment of a relay channel and / or update channel from the backend data storage node. Thus, a relay channel and / or update channel are established between the data storage node, the second data node, and the first data node.

[0261] Optionally, the first data node receives the mapping relationship between multiple second data nodes and multiple second data features from the routing management node. Thus, the first data node can send a third request message to the second data nodes corresponding to different second data features, thereby obtaining data corresponding to different second data features from different second data nodes and obtaining the target data.

[0262] Optionally, the third request message may also include the receiving address information of the first data node. Optionally, the third request message may also include the timeliness information of the receiving address of the first data node, so as to instruct the second data node to complete the transmission of the target data before the receiving address of the first data node expires.

[0263] Wherein, if the first request message includes a requirement parameter, the third request message may also include a requirement parameter, which is used to provide a guarantee for the transmission of the target data, or to establish a channel for transmitting the target data; the requirement parameter may include at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, which is used to instruct the service node to update the target data.

[0264] In other words, when transmitting target data between the first data node and the second data node, the required parameters must be met; or, the channel between the first data node and the second data node used to transmit target data must meet the required parameters.

[0265] Optionally, if the requirement parameters include the first indication information, the communication method may further include: the first data node receiving the receiving address information from the second data node, wherein the receiving address information of the second data node instructs the first data node to transmit the updated target data.

[0266] The receiving address information of the second data node may also include the timeliness information of the address of the second data node, or the first data node may receive the address timeliness information from the second data node to instruct the first data node to complete the transmission of the updated target data before the address of the second data node expires.

[0267] It is understandable that Method 1 uses a seamless, point-to-point approach to transmit the third request message. For example, the DMF1 node directly sends a third request message to the second data node, carrying the address information of the DMF1 node, the request parameters, and the address or index information of each DMF node (third data node) along the path. This allows the points along the path to reserve resources and select paths based on the request parameters and the information of each DMF node. When each DMF node initiates the target data transmission, it adds corresponding tag information to the packet header to achieve the target data transmission under the channel. The packet header example described above can be referenced and will not be elaborated further.

[0268] For example, such as Figure 8 As shown, Channel 1 (also known as Path 1) includes DMF1, DMF3, DMF4, and DMF2 nodes. Path 2 includes DMF1 and DMF2 nodes. The third request message and its response message are transmitted through Channel 2 (also known as Path 2), and the specific nodes along the path are not limited. When the target data transmission is initiated, the DMF2 node (i.e., the second data node) carries information about each path node (i.e., the third data node) and optional requirement parameters in the packet header, realizing resource scheduling and link orchestration synchronized with the message. Specifically, the information of each path node can be carried in the form of an index. Each path node determines the address of the next-hop node by combining its local configuration information and performs the corresponding forwarding action. For example, when the DMF2 node initiates the transmission of target data, it determines the address of the next-hop DMF3 node based on the information of each path node and its local configuration information. Then, the DMF3 node determines the address of the next-hop DMF4 node in the same way, thereby realizing the transmission of target data through Channel 1.

[0269] Method 2: The third request message is sent via a transit point.

[0270] In another possible implementation, the third request message includes information about a third data node, which is one or more data nodes that are passed between the first and second data nodes when transmitting target data.

[0271] Optionally, the routing management node determines the third data node based on at least one of the above, namely the first mapping relationship, the second mapping relationship, the topology relationship, or the transmission capacity information, and sends the 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.

[0272] The second request message received by the routing management node may also include requirement parameters. The routing management node determines the third data node based on at least one of the above and the requirement parameters.

[0273] For example, after the RMF node determines the DMF2 node (i.e. the second data node), the RMF node also needs to combine the data transmission requirements (i.e. the requirement parameters), the topology relationship between DMF nodes, and the transmission capacity information of DMF nodes to perform data link orchestration, and return the address of the DMF2 node and the address information of one or more optional path nodes (i.e. the third data node) to the source DMF1 node (i.e. the first data node). Figure 9 This is a diagram illustrating data link orchestration. (For example...) Figure 9 As shown, for high-bandwidth demand scenarios, such as high-definition video scenarios, the high-bandwidth path is selected, that is, channel 3 (data nodes 1, 2, 4, 6) is used for transmission; for latency-sensitive data transmission scenarios, such as voice call scenarios, the low-latency path is used, that is, channel 4 (data nodes 1, 2, 3, 5, 6) is used for transmission.

[0274] Optionally, the channel may include a relay channel and / or an update channel; the relay channel is used to transmit target data between the second data node, the third data node and the first data node; the update channel is used to transmit updated target data between the first data node, the third data node and the second data node.

[0275] Optionally, the channel includes a relay channel and / or an update channel; the relay channel is used to transmit 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 to transmit updated target data between the first data node, the third data node, the second data node and the data storage node.

[0276] Optionally, the third request message may also include channel identification information, which is used to identify the channel, or in other words, the transmission path of the target data.

[0277] Optionally, the first data node sending a third request message to the second data node may 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.

[0278] It can be understood that the process by which the routing management node determines the second and third data nodes is also the process of determining the channel / path for data transmission, or the data orchestration process. The third request message can be sent via the third data node to achieve hop-by-hop channel establishment. The third request message may contain information about the third data node, and the third data node performs resource reservation / channel establishment based on the third request message.

[0279] For example, such as Figure 8 As shown, Channel 1 (also known as Path 1) includes DMF1 node, DMF3 node, DMF4 node, and DMF2 node. The third request message and response message are sent hop-by-hop through Path 1 to complete the end-to-end link establishment and resource allocation process before the target data transmission begins. At this time, each node can receive the data transmission request from the source DMF1 node to complete resource reservation and previous / next hop node association. Specifically, this association can be combined with the channel identifier carried in the third request message, so that only this channel identifier needs to be carried in the subsequent target data transmission process, such as carrying the data channel identifier in the packet header. This enables resource reservation and channel selection for DMF3, DMF4, and DMF2 nodes; that is, DMF3, DMF4, and DMF2 nodes determine the next hop node based on Channel 1 corresponding to the channel identifier.

[0280] Furthermore, the communication method may also include a process of registering target data to a second data node and / or a data storage node. Specifically, this may include the data source node directly registering the target data to the second data node and the storage node, or the data source node registering the target data to the second data node, and then the second data node registering the target data to the data storage node; the second data node is responsible for performing index allocation and returning it to the data source node to support subsequent access / updates.

[0281] It should be understood that the various implementation methods in the embodiments of this application can be used in combination, and the combination form of the various implementation methods in the above embodiments is not limited.

[0282] The above combination Figures 7-9 The overall flow of the communication method provided in the embodiments of this application is described below. Figure 10 and Figure 11 This paper describes the specific process of the communication method provided in the embodiments of this application in two specific scenarios.

[0283] Figure 10 A flowchart illustrating the communication method provided in this embodiment. Figure 2This communication method is applicable to the aforementioned communication system, specifically involving the interaction between data consumption nodes (i.e., the aforementioned service nodes), DMF1 nodes (i.e., the aforementioned first data nodes), RMF1 nodes (i.e., the aforementioned routing management nodes), RMF2 nodes, DMF2 nodes (i.e., the aforementioned second data nodes), DP1 nodes and DP2 nodes (i.e., the aforementioned data production nodes), and DSF nodes (i.e., the aforementioned data storage nodes).

[0284] Specifically, such as Figure 10 As shown, the flow of this communication method is as follows:

[0285] S100A, DP1 and DP2 nodes register data with DMF2 node.

[0286] For example, DP1 and DP2 nodes send registration data request messages to DMF2 node, and DMF2 node sends response messages corresponding to the data request messages to DP1 and DP2 nodes, with the response messages indicating that the data registration was successful.

[0287] S100B, the DMF2 node synchronously transfers data to the DSF node.

[0288] S100A and S100B are optional steps. S100A and S100B are methods for DP nodes to indirectly register data with DSF nodes.

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

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

[0291] In S100b, the DMF2 node performs index allocation and sends the index for data allocation to the DP1 and DP2 nodes respectively.

[0292] In S100c, DP1 and DP2 nodes register data with the DSF node respectively.

[0293] Steps S100a1-S100c are optional. S100a1-S100c is the method by which DP1 and DP2 nodes directly register data with the DSF node. Execute S100A and S100B, or execute S100a1-S100c.

[0294] S100d, DMF2 node sends routing database update information to RMF2 node.

[0295] The routing database update information may include the index of the data registered by DP1 and DP2 nodes, as well as the information of the corresponding DMF2 / DSF node.

[0296] Optionally, the DSF node sends routing database update information to the DMF2 node.

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

[0298] The data acquisition request may include data index #1 and / or data feature #1. The data acquisition request can be referenced in the description of the first data request in S701, the data index #1 can be referenced in the description of the first data index in S701, and the data feature #1 can be referenced in the description of the first data feature in S701; further details are omitted here. Optionally, the data acquisition request may also include requirement parameters, which can be referenced in the description of requirement parameters in S701; further details are omitted here.

[0299] S1002, DMF1 node performs data access permission pre-verification.

[0300] The DMF1 node performs access permission pre-verification based on the mapping relationship between data and access permission roles stored in its local configuration or by other nodes (such as UDM or RMF) to confirm that the data consumer node has the necessary access permissions. For example, based on the mapping relationship between the data consumer node and the supported data features, it determines that the data consumer node can access the data corresponding to the data feature in the data acquisition request. Alternatively, based on the access permission control information between the data consumer node and the data node / network element, it determines that the data consumer node can access the data node (such as the DMF2 node) corresponding to data index #1.

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

[0302] The routing information query request message may include data index #2 and / or data feature #2. The routing information query request can be referred to in S702 for the description of the second data request. Here, data index #2 can be referred to in S702 for the description of the second data index, and data feature #2 can be referred to in S702 for the description of the second data feature; further details are omitted. The RMF1 node must support fuzzy matching to find potential storage nodes for the target data, such as performing matching based on the perceived data information of the requested target node within a specific time period.

[0303] S1004, RMF1 node queries RMF2 node for routing information.

[0304] Step S1004 is optional. The routing information query process may involve inter-domain RMF interaction. For example, if RMF1 cannot find the DMF node corresponding to data index #2 and / or data feature #2, it sends a routing information query request to RMF2. This allows it to obtain the address information of DMF2 from RMF2.

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

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

[0307] The routing information query response message may include the address information of the DMF2 node.

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

[0309] The data acquisition request message and / or channel establishment request message may carry the receiving address and required parameters of the DMF1 node. The data acquisition request message and / or channel establishment request message may also include data index #2 and / or data feature #2. Optionally, the data acquisition request message and / or channel establishment request message may also include address expiration information of the receiving address to instruct the DMF2 node to complete data transmission before the receiving address expires.

[0310] For data acquisition request messages or channel establishment request messages, please refer to the description of the third request message in S704, which will not be repeated here.

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

[0312] Step S1007 is optional. The DMF2 node performs access permission verification based on the mapping relationship between data and access permission roles stored in its local configuration or by other nodes (such as UDM or RMF) to confirm that the data consumer node has the necessary access permissions. For example, based on the mapping relationship between the data consumer node and the supported data features, it determines that the data consumer node can access the data corresponding to the data feature in the data acquisition request. Alternatively, based on the access permission control information between the data consumer node and the data node / network element, it determines that the data consumer node can access the data node (such as the DMF2 node) corresponding to data index #2.

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

[0314] 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 channel establishment success response message to the DMF2 node.

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

[0316] The data acquisition response message is the DMF2 node's feedback to the data acquisition request message, and the channel establishment success response message is the DMF2 node's feedback to the channel establishment request message. The data acquisition response message can carry target data that matches data index #2 and / or data feature #2.

[0317] Optionally, if the requirement parameters carried in the data acquisition request message and / or channel establishment request message include an update indication, that is, the DMF2 node has received the update indication, then the corresponding update receiving address information, that is, the receiving address information of the DMF2 node, must also be carried in the data acquisition response message and / or channel establishment success response message.

[0318] S1010 establishes a data plane relay channel between the DSF node, DMF2 node, DMF1 node and the data consumer node.

[0319] Step S1010 is optional. If in S1006, node DMF1 sends a channel establishment request message to node DMF2, and in S1009, node DMF2 sends a channel establishment success response message to node DMF1, then step S1010 is executed. The data plane relay channel is used for transmitting target data matching data index #2 and / or data feature #2 between nodes DSF, DMF2, DMF1, and data consumer nodes.

[0320] Optionally, a data relay channel can be established between the DMF2 node, the DMF1 node, and the data consumption node.

[0321] S1011, establish a data plane update channel between the data consumption node, DMF1 node, DMF2 node and DSF node.

[0322] Step S1011 is optional. If the requirement parameters carried in the acquisition request message and / or channel establishment request message include an update indication, and in step S1006, node DMF1 sends a channel establishment request message to node DMF2, and in step S1009, node DMF2 sends a successful channel establishment response message to node DMF1, then step S1011 is executed. The data plane update channel is used for transmitting updated target data between data consumer nodes, nodes DMF1 and DMF2, and the DSF node.

[0323] Optionally, a data plane update channel can be established between the data consumption node, the DMF1 node, and the DMF2 node.

[0324] In summary, by querying routing information from the DMF1 node to the RMF1 node based on the data index and / or data characteristics, the DMF2 node information that supports access to the target data can be obtained. Then, the target data can be obtained through the DMF2 node, which can realize the transmission of the target data from the DMF2 node to the data consumer node. In other words, it can support the requirement of data access nearby, solve the problem that large-scale data is difficult to relay through signaling messages, and meet the requirement of low-latency data access.

[0325] Figure 11 A flowchart illustrating the communication method provided in this embodiment. Figure 3 This communication method is applicable to the aforementioned communication system, specifically involving the interaction between data consumption nodes (i.e., the aforementioned service nodes), DMF1 nodes (i.e., the aforementioned first data nodes), RMF1 nodes (i.e., the aforementioned routing management nodes), RMF2 nodes, DMF2 nodes (i.e., the aforementioned second data nodes), DP1 nodes and DP2 nodes (i.e., the aforementioned data production nodes), and DSF nodes (i.e., the aforementioned data storage nodes).

[0326] Specifically, such as Figure 11 As shown, the flow of this communication method is as follows:

[0327] S1101, the data consumer node sends a data acquisition request to the DMF1 node.

[0328] Data acquisition requests may include data feature #1. The description of the first data request in S701 and data feature #1 in S701 are similar and will not be repeated here. It is understood that in this application scenario, the target data that the data consumption node wants to acquire has not been collected, and the data acquisition request does not include a data index.

[0329] Optionally, the data acquisition request may also include requirement parameters. The requirement parameters can be found in the description of requirement parameters in S701, and will not be repeated here.

[0330] S1102, DMF1 node performs data access permission pre-verification.

[0331] S1102 can be referred to the description of S1002, and will not be repeated here.

[0332] S1103, DMF1 node sends a routing information query request message to RMF1 node.

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

[0334] S1104, RMF1 node queries RMF2 node for routing information.

[0335] S1104 is an optional step. The description of S1104 can be found in the description of S1004, and will not be repeated here.

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

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

[0338] The routing information query response message may include the address information of the DMF2 node. The DMF2 node may be a node associated with data feature #2, meaning that the DMF2 node supports accessing target data matching data feature #2. The routing information query response message may also include an indication that the target data matching data feature #2 was not collected, or an indication that the DMF2 node did not collect the target data matching data feature #2.

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

[0340] Data acquisition request messages and / or channel establishment request messages may carry the receiving address of the DMF1 node, data characteristic #2, and required parameters. Optionally, data acquisition request messages and / or channel establishment request messages may also include address expiration information of the receiving address to instruct the DMF2 node to complete data transmission before the receiving address expires.

[0341] For data acquisition request messages or channel establishment request messages, please refer to the description of the third request message in S704, which will not be repeated here.

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

[0343] S1107 is an optional step. The description of S1007 is similar to that of S1107 and will not be repeated here.

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

[0345] Data acquisition request messages are used to request data acquisition. For example, node DMF2 sends data acquisition request message #1 to node DP1 and data acquisition request message #2 to node DP2. Data acquisition request messages may include a receiving address and allocated index information; for example, data acquisition request message #1 includes index #1, and data acquisition request message #2 includes index #2. The receiving address and allocated index information can be found in the description of the fourth request message in S702, and will not be repeated here.

[0346] S1109, DP1 node and / or DP2 node send a data acquisition response message to DMF2 node.

[0347] S1109 is an optional step. The data acquisition response message is used to respond to the data acquisition request message, such as indicating whether the target data acquisition was successful or failed, or whether the target data matches data feature #2.

[0348] S1110, DP1 node and / or DP2 node send a data registration request message to DSF node.

[0349] S1110 is an optional step. DP1 and / or DP2 nodes do not send data acquisition response messages directly to the DMF2 node, but instead relay the target data to be acquired through the DSF node. The data registration request message may include target data matching data feature #2.

[0350] S1111, the DMF2 node sends a data relay request message to the DSF node.

[0351] Step S1111 is optional. If data acquisition requires relaying through the DSF node, then the DMF2 node also needs to initiate a data relay request to the DSF, which carries the receiving address of the DMF1 node.

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

[0353] S1112 is an optional step. If S1109 is executed, then S1110-S1112 can be omitted; if S1110-S1112 is executed, then S1109 can be omitted.

[0354] S1113, establish a data plane relay channel between DMF2 node, DMF1 node and data consumer node.

[0355] Step S1113 is optional. If node DMF1 sends a channel establishment request message to node DMF2 in step S1106, then step S1113 is executed. The data plane relay channel is used for the transmission and collection of target data between nodes DMF2 and DMF1 and data consumer nodes.

[0356] S1114, Establish a data plane update channel between the data consumption node, DMF1 node, DMF2 node and DSF node.

[0357] Step S1114 is optional. If the requirement parameters carried in the acquisition request message and / or channel establishment request message include an update indication, and in step S1106 the DMF1 node sends a channel establishment request message to the DMF2 node, then step S1011 is executed. The data plane update channel is used for transmitting the updated target data between the data consumer node, the DMF1 node, the DMF2 node, and the DSF node.

[0358] Optionally, a data plane update channel can be established between the data consumption node, the DMF1 node, and the DMF2 node.

[0359] In summary, by querying routing information from the DMF1 node to the RMF1 node based on data characteristics, the DMF2 node information that can collect target data can be obtained. Then, the target data can be collected through the DMF2 node, which can realize the transmission of target data from the DMF2 node to the data consumption node. This can support the requirement of data access nearby, solve the problem that large-scale data is difficult to relay through signaling messages, and meet the requirement of low-latency data access.

[0360] The above combination Figures 7-11 The methods provided in the embodiments of this application are described in detail below. Figures 12-13 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0361] Figure 12 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 For example, such as Figure 12 As shown, the communication device 1200 includes a transceiver module 1201 and a processing module 1202. For ease of explanation, Figure 12 Only the main components of the communication device are shown.

[0362] The transceiver module 1201 is used to perform the above. Figure 7 The sending and receiving functions of the method shown are executed by the processing module 1202. Figure 7 The method shown includes functions other than sending and receiving.

[0363] Optionally, the transceiver module 1201 may include a transmitting module. Figure 12 (not shown in the image) and receiving module ( Figure 12 (Not shown in the diagram). The transmitting module is used to implement the transmitting function of the communication device 1200, and the receiving module is used to implement the receiving function of the communication device 1200.

[0364] Optionally, the communication device 1200 may also include a storage module. Figure 12 (Not shown in the image), the storage module stores programs or instructions. When the processing module 1202 executes the program or instructions, the communication device 1200 can perform the above-described method. Figure 7 The methods shown describe the functions of the first data node, service node, or routing management node.

[0365] It is understood that the communication device 1200 may be a first data node, a service node, or a routing management node, or it may be a chip (system) or other component or assembly that can be set in the first data node, service node, or routing management node, or it may be a device that includes the first data node, service node, or routing management node. This application does not limit this.

[0366] In addition, the technical effects of the communication device 1200 can be referenced. Figure 7 The technical effects of the communication method shown will not be elaborated here.

[0367] Figure 13 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 For example, the communication device can be a terminal, or a chip (system) or other component or assembly that can be set in the terminal. Figure 13 As shown, the communication device 1300 may include a processor 1301. Optionally, the communication device 1300 may also include a memory 1302 and / or a transceiver 1303. The processor 1301 is coupled to the memory 1302 and / or the transceiver 1303, for example, by means of a communication bus, an on-chip interface, or other communication lines. Optionally, the memory 1302 may be integrated with the processor 1301.

[0368] The following is combined Figure 13 A detailed description of each component of the communication device 1300 is provided below:

[0369] The processor 1301 is the control center of the communication device 1300. It can be a single processor or a collective term for multiple 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 implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0370] Optionally, the processor 1301 can perform various functions of the communication device 1300 by running or executing software programs stored in the memory 1302 and calling data stored in the memory 1302, such as performing the above-mentioned functions. Figure 7 The communication method shown.

[0371] In a specific implementation, as one example, the processor 1301 may include one or more CPUs, for example... Figure 13 CPU0 and CPU1 are shown in the diagram.

[0372] In a specific implementation, as one example, the communication device 1300 may also include multiple processors, for example... Figure 13 The processors 1301 and 1304 are shown. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0373] The memory 1302 is used to store the software program that executes the solution of this application, and is controlled by the processor 1301 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0374] Optionally, the memory 1302 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1302 may be integrated with the processor 1301 or may exist independently, and may be connected via the interface circuit of the communication device 1300. Figure 13 (Not shown in the image) is coupled to processor 1301, and this embodiment of the application does not specifically limit this.

[0375] Transceiver 1303 is used for communication with other communication devices. For example, if communication device 1300 is a terminal, transceiver 1303 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1300 is a network device, transceiver 1303 can be used to communicate with a terminal or with another network device.

[0376] Optionally, transceiver 1303 may include a receiver and a transmitter. Figure 13 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0377] Optionally, the transceiver 1303 can be integrated with the processor 1301, or it can exist independently and be connected via the interface circuit of the communication device 1300. Figure 13 (Not shown in the image) is coupled to processor 1301, and this embodiment of the application does not specifically limit this.

[0378] Understandable, Figure 13 The structure of the communication device 1300 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0379] Furthermore, the technical effects of the communication device 1300 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

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

[0381] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0382] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0383] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0384] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0385] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0386] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented 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 this application.

[0387] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0388] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0389] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0390] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0391] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes all the various possible memories described above.

Claims

1. A communication method, characterized in that, include: The first data node receives a first request message from the business node, the first request message being used to request data retrieval. The first data node sends a second request message to the routing management node based on the first request message. The second request message is used to request the data node that supports data access. The first data node receives information from the second data node of the routing management node, the second data node supporting access to the target data; The first data node sends the target data to the service node, and the target data is obtained from the second data node.

2. The method according to claim 1, characterized in that, The first request message includes a first data index and / or a first data feature, wherein the first data index points to the target data and the feature of the target data matches the first data feature.

3. The method according to claim 2, characterized in that, The second request message includes a second data index and / or a second data feature, wherein the second data index points to the target data and the feature of the target data matches the second data feature.

4. The method according to claim 3, characterized in that, The routing management node has metadata management capabilities, 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.

5. The method according to claim 4, characterized in that, If the second request message includes the second data index, the second data node is determined based on the second data index and the first mapping relationship; if the second request message includes the second data feature, the second data node is determined based on 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 the ability to manage topology relationships and transmission capacity information. The topology relationship indicates the adjacency relationship between the first data node, the second data node, and the third data node. The third data node is one or more data nodes that are passed between the first data node and the second data node when transmitting the target data. The topology relationship is used to determine the relationship between the second data node and the third data node. The transmission capacity information indicates the transmission capacity 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.

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 includes: 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 request the establishment of a channel for data transmission; The first data node receives the target data from the second data node.

8. The method according to claim 7, characterized in that, The third request message includes information about the third data node, which is one or more data nodes that are passed between 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, If the first request message includes a requirement parameter, the third request message further includes a requirement parameter, which is used to provide a guarantee for the transmission of the target data, or to establish the channel for transmitting the target data; the requirement parameter includes at least one of the following: transmission delay, bandwidth, time window, service level agreement (SLA) or first indication information, wherein the first indication information is used to instruct the service node to update the target data.

10. The method according to claim 9, characterized in that, The requirement parameters include the first indication information; the method further includes: The first data node receives receive address information from the second data node, and the receive address information instructs the first data node to transmit the updated target data.

11. The method according to claim 3, characterized in that, The second request message does not include the second data index, but includes the second data feature; the method further includes: The first data node receives a second indication from the routing management node, the second indication being used to indicate that data matching the second data feature has not been collected.

12. A communication method, characterized in that, include: The routing management node receives a second request message from the first data node. The second request message is used to request a data node that supports access to data. The second request message includes a second data index and / or a second data feature. The routing management node sends information about the second data node to the first data node. The second data node supports access to the target data, the second data index points to the target data, and the characteristics of the target data match the second data characteristics.

13. The method according to claim 12, characterized in that, The method further includes: The routing management node receives a registration request from at least one data node, the registration request being used to request the registration of at least one of the following: a first mapping relationship, a second mapping relationship, a topology relationship, or transmission capability information; Wherein, the first mapping relationship is a mapping relationship between at least one data index and at least one data node, wherein 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, wherein the at least one data feature includes the second data feature, and the at least one data node includes the second data node; 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 traversed when transmitting data between the first data node and the second data node, and the topology relationship is used to determine the second data node and the third data node; the transmission capability information indicates the transmission capability of the at least one data node and is used to establish a channel for transmitting data.

14. The method according to claim 13, characterized in that, Before the routing management node sends the information of the second data node to the first data node, the method further includes: The routing management node determines the information of the second data node based on at least one of the above.

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

16. The method according to claim 15, characterized in that, The second request message also includes a requirement parameter, which is used to provide a guarantee for 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: The routing management node determines the information of the third data node based on at least one of the requirements parameters; The required parameters include at least one of the following: transmission latency, bandwidth, time window, service level agreement (SLA) or first indication information, wherein the first indication information is used to instruct the service node to update the target data.

17. A communication device, characterized in that, The apparatus includes: a module for performing the method as described in any one of claims 1-11, or a module for performing the method as described in any one of claims 12-16.

18. A communication device, characterized in that, The communication device includes a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the method as described in any one of claims 1-11 to be performed, or cause the method as described in any one of claims 12-16 to be performed.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1-11, or cause the computer to perform the method as claimed in any one of claims 12-16.

20. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1-11 to be performed, or cause the method as described in any one of claims 12-16 to be performed.

Images