Space-time multi-dimensional identification network-oriented control plane full-process control method and system

Abstract

The application discloses a control plane whole-process control method and system for a space-time multi-dimensional identification network, and belongs to the technical field of novel identification networks and routing. The method comprises the following steps: constructing an identification attribute space, and generating a request intention; based on the identification attribute space, matching the attributes in the request intention with the registered attributes in the whole network, generating a minimum attribute set, a whole attribute set and an identification hash corresponding to the whole attribute set, which meet the business requirements; constructing an identification packet header, and generating a basic task strategy; based on the identification packet header in the encapsulated business data, performing distributed routing data forwarding, and when the distributed routing data forwarding path is unavailable, performing data forwarding through the basic task strategy; based on an identification recycling intention, searching for identification resources, and recycling the found identification resources when the data forwarding is completed. Through the identification generation mechanism and the dual-mode routing mechanism, the application takes into account the network forwarding efficiency, transmission reliability and identification resource whole life cycle closed-loop management and control.

Description

Technical Field

[0001] This invention relates to the field of novel identification networks and routing technology, and in particular to a control plane full-process control method and system for spatiotemporal multidimensional identification networks. Background Technology

[0002] With the rapid evolution of new business models such as computing-network convergence, the Industrial Internet, and deterministic networks, the core demands of network communication have shifted from basic end-to-end connectivity to a comprehensive need for business attribute awareness, multi-dimensional resource matching, deterministic transmission assurance, and dynamic resource scheduling. The business side not only requires the network to achieve data reachability but also needs to accurately match target nodes and intelligently schedule paths based on the differentiated characteristics of the business, such as service quality levels, security requirements, and computing resource needs.

[0003] Traditional TCP / IP network architecture uses IP addresses as unique addressing identifiers, deeply binding node identity with network location semantics, inherently lacking the ability to express business and resource attributes. Under this architecture, the network can only make forwarding decisions based on addresses, unable to perceive differentiated business needs, and struggling to dynamically match node resources with business requirements, making it unsuitable for the diversified and refined communication requirements of new network scenarios. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a control plane full-process control method and system for spatiotemporal multidimensional identification networks. Through a flexible and selectable identification generation mechanism and a dual-mode routing mechanism, it takes into account both network forwarding efficiency and transmission reliability, and at the same time realizes closed-loop management and control of the entire life cycle of identification resources.

[0005] To achieve the above objectives, the present invention is implemented using the following technical solution:

[0006] On the one hand, this invention provides a full-process control method for the control plane of a spatiotemporal multidimensional identification network, including:

[0007] Based on the registered spatiotemporal multidimensional identifier attribute data, an identifier attribute space is constructed;

[0008] Standardize and encapsulate business requests for intent activation and policy generation to generate request intents;

[0009] Based on the aforementioned identifier attribute space, the attributes in the request intent are matched with the attributes already registered across the entire network to generate an attribute set and corresponding identifier hash that meet the business requirements.

[0010] In response to the attribute set being a minimal attribute set, an identifier header is constructed based on the minimal attribute set and the corresponding identifier hash;

[0011] In response to the attribute set being a full attribute set, a basic task strategy is generated based on the full attribute set and the corresponding identifier hash;

[0012] Add the identifier header to the process-generated business data, generate encapsulated business data, and parse the identifier header in the encapsulated business data;

[0013] Based on the identifier header in the encapsulated business data, distributed routing data forwarding is performed. When the distributed routing data forwarding path is unavailable, the basic task strategy is matched by the identifier hash corresponding to the full attribute set, and data forwarding is performed.

[0014] The identifier recycling service request is standardized and encapsulated to generate an identifier recycling intent. Identifier resources are searched based on the identifier recycling intent. When data forwarding is completed, the identifier recycling mechanism is triggered to recycle the found identifier resources.

[0015] Optionally, the spatiotemporal multidimensional identifier attribute data includes device attribute data of the service terminal / server, service attribute data of the service process, device attribute data of the execution terminal, and network device attribute data of the forwarding device;

[0016] The device attribute data of the service terminal / server includes the QoS, security level, and service type of the service terminal / server;

[0017] The service attribute data of the service process includes the QoS, security level, and service type of the service process;

[0018] The device attribute data of the execution terminal includes the device type, task type, capability level, security level, and QoS of the execution terminal;

[0019] The network device attribute data of the forwarding device includes the device capabilities and topology information of the forwarding device.

[0020] Optionally, based on the identifier attribute space, the attributes in the request intent are matched with the attributes already registered across the entire network to generate an attribute set and corresponding identifier hash that meet the business requirements, including:

[0021] Based on the aforementioned identifier attribute space, the attributes in the request intent are matched with the attributes already registered across the entire network to generate an attribute set that meets business requirements; the attribute set includes a minimum attribute set and a full attribute set.

[0022] Based on the attribute set, corresponding identifier hashes are generated through template configuration, mapping functions, or learning cognitive models.

[0023] Optionally, based on the identifier packet header in the received encapsulated service data, distributed routing data forwarding is performed. When the distributed routing data forwarding path is unavailable, data forwarding is performed by matching the identifier hash corresponding to the full attribute set with the basic task strategy, including:

[0024] Based on the identifier packet header in the received encapsulated service data, the next hop exit is determined through distributed domain coordinate forwarding logic, and distributed routing data forwarding is executed. When the distributed routing data forwarding path is unavailable, the basic task strategy is matched by the identifier hash corresponding to the full attribute set, and data forwarding is executed.

[0025] Optionally, finding identifier resources based on identifier recycling intent includes:

[0026] Search for identifier resources based on identifier recycling intent;

[0027] If the identification resource is found successfully, subsequent data forwarding will be performed based on the found identification resource;

[0028] If the identification resource lookup fails, the attribute matching and discovery process is re-executed to generate a new identification resource, and subsequent data forwarding is performed based on the new identification resource.

[0029] Optionally, it also includes updating the identifier attribute space based on the found identifier resources.

[0030] On the other hand, the present invention provides a control plane full-process control system for spatiotemporal multidimensional identification networks, comprising:

[0031] The identifier proxy is used for: standardizing and encapsulating received intent activation and policy generation business requests, generating request intents, and sending the request intents to the identifier server; receiving and caching the minimum attribute set and corresponding identifier hashes, and constructing identifier headers; adding identifier headers to the business data generated during the receiving process, generating encapsulated business data, parsing the identifier headers in the encapsulated business data, and sending it to the forwarding device; standardizing and encapsulating received identifier reclamation business requests, generating identifier reclamation intents, searching for identifier resources based on identifier reclamation intents, and triggering the identifier reclamation mechanism when data forwarding is completed to reclaim the found identifier resources;

[0032] The forwarding device is used to: receive the basic task policy and the corresponding identifier hash; perform distributed routing data forwarding based on the identifier packet header in the received encapsulated business data; and when the distributed routing data forwarding path is unavailable, perform data forwarding by matching the basic task policy with the identifier hash corresponding to the full attribute set.

[0033] The identifier server is used to: construct an identifier attribute space based on the registered spatiotemporal multidimensional identifier attribute data; and, based on the identifier attribute space, match the attributes in the received request intent with the attributes registered in the entire network to generate a minimum attribute set and corresponding identifier hash, a full attribute set and corresponding identifier hash that meet business requirements, and send the minimum attribute set and corresponding identifier hash to the identifier proxy, and send the full attribute set and corresponding identifier hash to the network cognitive proxy.

[0034] The network cognitive agent is used to: receive the full attribute set and the corresponding identifier hash, generate a basic task policy based on the full attribute set and the corresponding identifier hash, and send the basic task policy and the corresponding identifier hash to the forwarding device.

[0035] Optionally, the identifier proxy is also used to: send the received identifier attribute registration request to the identifier server; and send the found identifier resources to the identifier server.

[0036] The forwarding device is also used to: send a network device registration request to the identification server;

[0037] The identifier server is also used for: registering spatiotemporal multidimensional identifier attribute data and constructing an identifier attribute space based on received identifier attribute registration requests and network device registration requests from forwarding devices; and updating the identifier attribute space based on received identifier resources.

[0038] Optional, also includes:

[0039] The service terminal / server is used to: send device attribute registration requests, intent activation and policy generation service requests, and identifier revocation service requests to the identifier agent during identifier attribute registration.

[0040] The business process is used for: sending business attribute registration requests to the identifier agent during the identifier attribute registration process, and generating business data in the process.

[0041] The execution terminal is used to: send a device attribute registration request for the execution terminal in the identification attribute registration to the identification agent, and receive forwarding data sent by the forwarding device;

[0042] The device attribute registration request for the service terminal / server includes registration requests for the QoS, security level, and service type of the service terminal / server; the service attribute registration request for the service process includes registration requests for the QoS, security level, and service type of the service process; the device attribute registration request for the execution terminal includes registration requests for the device type, task type, capability level, security level, and QoS of the execution terminal; and the network device registration request for the forwarding device includes registration requests for the device capabilities and topology information of the forwarding device.

[0043] Optionally, the network cognitive agent is also used to: send attribute space synchronization requests to the identity server and receive the identity attribute space sent by the identity server.

[0044] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0045] This invention constructs a spatiotemporal multidimensional unified identifier system and a globally standardized identifier attribute space, breaking through the semantic limitations of the single IP identifier in traditional TCP / IP networks. It can fully carry multi-dimensional attribute information such as device, service, security, and computing power, achieving fine-grained matching of service intent and network node attributes, effectively supporting differentiated deterministic transmission services such as computing-network convergence and the Industrial Internet. A dual-mode routing mechanism combining distributed forwarding and control plane policy forwarding, coupled with an identifier hashing generation scheme, balances the low forwarding latency of distributed routing with the transmission reliability of centralized policy routing. Compared to a single forwarding architecture, it significantly improves network packet forwarding efficiency and service connectivity assurance capabilities. It covers identifier registration, intent... The system features a closed-loop management process covering the entire lifecycle of matching, data forwarding, and resource recycling. It introduces an identifier reuse retrieval mechanism to reduce the computational overhead of repeated matching, optimize the utilization rate of identifier resources across the entire network, reduce the pressure on control plane signaling interaction, and adapt to large-scale, high-concurrency network operation scenarios. Relying on three core mechanisms—unified representation of multi-dimensional attributes, dual-mode collaborative routing, and closed-loop management of the entire identifier lifecycle—it overcomes the technical shortcomings of traditional IP networks, such as lack of service awareness, single forwarding mechanism, and fragmented resource management. It balances the real-time performance of network transmission with the reliability of service operation and can be widely adapted to various complex network scenarios such as future integrated computing and networking and industrial deterministic communication. It has good engineering implementation value and prospects for expanded applications. Attached Figure Description

[0046] Figure 1 This is a flowchart illustrating the full-process control method for the control surface of a spatiotemporal multidimensional identification network provided in an embodiment of the present invention.

[0047] Figure 2 This is a schematic diagram of the structure of the control surface full-process control system for spatiotemporal multidimensional identification networks provided in an embodiment of the present invention. Detailed Implementation

[0048] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations thereof. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0049] The term "and / or" simply describes 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, or B alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0050] Example 1

[0051] like Figure 1 As shown in the figure, this embodiment introduces a full-process control method for the control plane of a spatiotemporal multidimensional identification network, including the following steps:

[0052] Step 1: Identifier attribute registration phase, specifically:

[0053] In the spatiotemporal multidimensional identifier intelligent network architecture, the registration of spatiotemporal multidimensional identifier attribute data is performed first. The registration of device attribute data of business terminals / servers, business attribute data of business processes, device attribute data of execution terminals, and network device attribute data of forwarding devices is completed in sequence, and then a unified identifier attribute space is built.

[0054] Spatiotemporal multidimensional identifier attribute data includes device attribute data of business terminals / servers, business attribute data of business processes, device attribute data of execution terminals, and network device attribute data of forwarding devices.

[0055] The device attribute data of the business terminal / server includes the Quality of Service (QoS), security level, and service type. After verifying the legality of the device attribute data based on the hardware capabilities and service requirements of the business terminal / server, the registration of the device attribute data of the business terminal / server is completed.

[0056] Similarly, the registration of business attribute data for completing the business process, device attribute data for the execution terminal, and network device attribute data for the forwarding device is also required.

[0057] The business attribute data of a business process includes the business process's QoS, security level, and business type;

[0058] The device attribute data of the execution terminal includes the device type, task type, capability level, security level, and QoS of the execution terminal;

[0059] The network device attribute data of the forwarding device includes the device capabilities and topology information of the forwarding device, providing basic data for subsequent network topology construction and path calculation.

[0060] Based on the registered spatiotemporal multidimensional identifier attribute data, an identifier attribute space is constructed, and all attribute data is aggregated and standardized.

[0061] Step Two: Intent Activation and Policy Generation Phase, specifically:

[0062] Based on intent activation and policy generation, business requests are encapsulated, attribute matched, identifier generated, and policy issued, providing standardized identifier headers and forwarding policy support for subsequent data forwarding.

[0063] The intent activation and policy generation business requests are standardized and encapsulated to generate request intents, providing standardized input for subsequent attribute matching and discovery.

[0064] Based on the attribute space, the attributes in the request intent are matched with the attributes registered across the entire network to generate a minimum attribute set, a full attribute set, and an identifier hash corresponding to the full attribute set that meet business requirements.

[0065] Based on the identifier attribute space, the attributes in the request intent are matched with the attributes registered across the entire network to generate an attribute set that meets business requirements; the attribute set includes a minimum attribute set and a full attribute set.

[0066] Based on the full attribute set, an identifier hash corresponding to the full attribute set is generated through template configuration, mapping functions, or a learned cognitive model. This identifier hash is a 128-bit hash, used in the preparation phase for both routing methods.

[0067] Specifically, an identifier header is constructed based on the identifier hashes corresponding to the minimum attribute set and the full attribute set, providing a matching basis for the subsequent distributed domain coordinate routing in this mode.

[0068] Based on the full attribute set and the corresponding identifier hash, combined with the network status information, a basic task strategy is generated. This basic task strategy is used for subsequent data forwarding. The network status information is the attribute information in the identifier attribute space.

[0069] Step 3: Identify the addressing and routing during the usage phase, specifically:

[0070] This phase, based on the identifier packet header, utilizes a dual-mode approach: distributed routing using the minimum attribute identifier and policy routing using identifier hashes. This ensures deterministic forwarding of business data, guaranteeing high efficiency and reliability of data transmission. The minimum attribute identifier refers to the smallest set of attributes selected from the attribute space based on business requirements, necessary for resolution, addressing, routing, or forwarding. Distributed routing refers to a routing mode where forwarding nodes perform path calculation, entry maintenance, and packet forwarding based on local routing information, neighbor information, or identifier cache entries, without relying on centralized policy calculation.

[0071] The identifier hash refers to the identifier hash corresponding to the entire attribute set.

[0072] The identifier header is added to the process-generated business data to generate encapsulated business data. The identifier header in the encapsulated business data is then parsed. The identifier header contains two types of routing identifier information: the minimum attribute identifier and the identifier hash.

[0073] Based on the identifier header in the encapsulated business data, distributed routing data forwarding is performed. When the distributed routing data forwarding path is unavailable, data forwarding is performed by matching the identifier hash corresponding to the full attribute set with the basic task strategy.

[0074] Based on the identifier packet header in the received encapsulated service data, the next hop exit is determined through distributed network coordinate forwarding logic, and distributed routing data forwarding is executed. When the distributed routing data forwarding path is unavailable, the basic task strategy is matched by the identifier hash corresponding to the full attribute set to ensure the connectivity of data transmission.

[0075] Step 4: The identification recycling phase, specifically:

[0076] This phase achieves closed-loop management of the lifecycle of identifier resources through a synchronized process of identifier lookup, reuse verification, and recycling. This means managing the entire process of identifiers from planning, generation, registration, activation, use, and modification, to freezing, invalidation, revocation, recycling, and archiving, in order to improve the reuse rate of identifier resources and ensure the efficient use of network resources.

[0077] The identifier recycling service request is standardized and encapsulated to generate an identifier recycling intent. Based on the identifier recycling intent, identifier resources are searched, and attempts are made to reuse existing identifier resources.

[0078] Search for identifier resources based on identifier recycling intent;

[0079] If the identification resource is found successfully, subsequent data forwarding will be performed based on the found identification resource, without needing to re-initiate the attribute matching and discovery process;

[0080] If the identification resource lookup fails, the attribute matching and discovery process is re-executed to generate a new identification resource, and subsequent data forwarding is performed based on the new identification resource.

[0081] When data forwarding is complete, the identifier recycling mechanism is triggered to reclaim the found identifier resources.

[0082] Update the resource status in the identifier attribute space based on the found identifier resources to complete the closed-loop management of the identifier resource lifecycle.

[0083] This embodiment collaboratively manages the entire process of identifier attribute registration, intent parsing and matching, policy generation and distribution, dual-mode data forwarding, and identifier recycling and reuse, achieving closed-loop management of identifier resources throughout their entire lifecycle. The dual-mode routing mechanism consists of distributed forwarding based on the smallest attribute identifier and control plane policy forwarding based on identifier hashes. It also supports three identifier hash generation methods: template configuration, mapping functions, and learning-based cognitive models, allowing for flexible adaptation to business needs. This improves forwarding efficiency while ensuring transmission reliability and resource utilization, supporting intelligent network operation and multi-scenario adaptability.

[0084] Example 2

[0085] This embodiment introduces a control plane full-process control system for spatiotemporal multidimensional identification networks, including seven modules: business terminal / server, business process, identification agent, forwarding device, identification server, network cognitive agent, and execution terminal.

[0086] The system comprises the following components: a business terminal / server for submitting device attribute registration requests and initiating business requests; a business process for submitting business attribute registration requests and generating business data; an identifier proxy for carrying or assisting in identifier-related functions such as identifier generation, parsing, mapping, verification, caching, and interface adaptation in a spatiotemporal multidimensional identifier network; a forwarding device for submitting network device attribute registration requests, storing policies issued by the network cognitive agent, and synchronizing identifier hashes; an identifier server for constructing a network-wide identifier attribute space, performing attribute matching, and generating identifier hashes. The attribute space is a multidimensional set of attributes used to organize objects, connections, services, and spatiotemporal related attributes, supporting attribute classification, mapping, combination, inheritance, reference, version management, and constraint expression; a network cognitive agent for generating and issuing basic task policies based on global attributes and network status; and an execution terminal for submitting device attribute registration requests and receiving business data.

[0087] Each module works in sequence to complete the entire process of identifier attribute registration, intent activation and policy generation, identifier usage, and identifier recycling, thereby achieving deterministic business data transmission and full lifecycle management of identifiers.

[0088] The service terminal / server is used to send device attribute registration requests, intent activation and policy generation service requests, and identifier revocation service requests to the identifier agent during identifier attribute registration.

[0089] The device attribute registration request for the business terminal / server includes registration requests for the business terminal / server's QoS, security level, and service type.

[0090] The business process is used to: send business attribute registration requests for the business process in the identity attribute registration to the identity agent, and generate business data in the process.

[0091] The business attribute registration request for a business process includes registration requests for the business process's QoS, security level, and business type.

[0092] The execution terminal is used to: send a device attribute registration request for the execution terminal in the identifier attribute registration to the identifier agent, and receive forwarding data sent by the forwarding device.

[0093] The device attribute registration request for the execution terminal includes registration requests for the execution terminal's device type, task type, capability level, security level, and QoS.

[0094] The identifier proxy is used for: sending received identifier attribute registration requests to the identifier server; standardizing and encapsulating received intent activation and policy generation business requests to generate request intents and sending them to the identifier server; receiving and caching the identifier hashes corresponding to the minimum and full attribute sets, and constructing identifier headers; adding identifier headers to the received process-generated business data, generating encapsulated business data, parsing the identifier headers in the encapsulated business data, and sending it to the forwarding device; standardizing and encapsulating received identifier recycling business requests to generate identifier recycling intents, searching for identifier resources based on the identifier recycling intents, triggering the identifier recycling mechanism when data forwarding is complete, recycling the found identifier resources, and sending the found identifier resources to the identifier server.

[0095] The forwarding device is used to: send a network device registration request to the identification server; receive the basic task policy and the identifier hash corresponding to the full attribute set; perform distributed routing data forwarding based on the identifier packet header in the received encapsulated service data; and when the distributed routing data forwarding path is unavailable, perform data forwarding by matching the basic task policy with the identifier hash corresponding to the full attribute set.

[0096] The network device registration request for the forwarding device includes a registration request for the device's capabilities and topology information.

[0097] The identifier server is used for: registering spatiotemporal multidimensional identifier attribute data and constructing an identifier attribute space based on received identifier attribute registration requests and network device registration requests from forwarding devices; matching the attributes in the received request intent with the attributes already registered across the entire network based on the identifier attribute space, generating a minimum attribute set, a full attribute set, and an identifier hash corresponding to the full attribute set that meet business requirements, sending the minimum attribute set and the identifier hash corresponding to the full attribute set to the identifier proxy, and sending the full attribute set and the identifier hash corresponding to the full attribute set to the network cognitive proxy; and updating the identifier attribute space based on received identifier resources.

[0098] The network cognitive agent is used to: receive the full attribute set and the corresponding identifier hash; generate a basic task policy based on the full attribute set and the corresponding identifier hash; send the basic task policy and the corresponding identifier hash to the forwarding device; send an attribute space synchronization request to the identifier server; receive the identifier attribute space sent by the identifier server; and obtain the attribute information for generating the basic task policy.

[0099] In one specific embodiment:

[0100] First, in the spatiotemporal multidimensional identifier intelligent network architecture, the registration of spatiotemporal multidimensional identifier attribute data is performed. This involves sequentially registering the device attribute data of the business terminal / server, the business attribute data of the business process, the device attribute data of the execution terminal, and the network device attribute data of the forwarding device. Then, the identifier server builds a unified identifier attribute space and synchronizes this identifier attribute space to the network cognitive agent, laying the data foundation for subsequent policy calculation and data forwarding.

[0101] Business terminals / servers, business processes, and execution terminals register their own attribute information with the identifier agent.

[0102] Based on its hardware capabilities and service requirements, the service terminal / server submits a device attribute registration request to the identifier agent, including key information such as QoS, security level, and service type. After verifying the validity of the request, the identifier agent forwards the standardized device attribute data to the identifier server, completing the registration of the service terminal / server device attributes.

[0103] The service process submits a service attribute registration request to the identifier agent, including key information such as QoS, security level, and service type. After verifying the validity of the request, the identifier agent forwards the standardized device attribute data to the identifier server, completing the registration of the service attributes.

[0104] The execution terminal submits a device attribute registration request to the identification agent, including key information such as device type, task type, capability level, security level, and QoS. After verifying the validity of the request, the identification agent forwards the standardized device attribute data to the identification server, thus completing the registration of the execution terminal's device attributes.

[0105] The forwarding device submits a network device attribute registration request to the identification server, including key information such as device capabilities and topology. After verifying the validity of the request, the identification server completes the registration of the forwarding device attributes, providing basic data for subsequent network topology construction and path calculation.

[0106] The identification server receives attribute registration data from business terminals / servers, business processes, and execution terminals from the identification agent, as well as network device attribute registration data from the forwarding device. It then aggregates and standardizes all attribute data to build a unified identification attribute space.

[0107] The network cognitive agent initiates an attribute space synchronization request to the identification server. The identification server synchronizes the completed identification attribute space data to the network cognitive agent, enabling the network cognitive agent to obtain complete attribute information of all network devices, services, and forwarding nodes, providing data support for subsequent network policy calculations, resource scheduling, and intelligent decision-making.

[0108] Then, after the identification attribute registration phase is completed, the intent activation and policy generation phase begins. This phase, based on the business requests from the business terminal / server, completes request intent encapsulation, attribute matching, identification generation, and policy distribution through the collaborative interaction of the business process, identification proxy, identification server, and network cognitive proxy. This provides standardized identification headers and forwarding policies to support subsequent data forwarding.

[0109] Based on business requirements, the business terminal / server sends an intent activation and policy generation business request to the identifier agent.

[0110] The identifier agent receives intent activation and policy generation business requests from business terminals / servers, parses and standardizes them to generate request intents, providing standardized input for subsequent attribute matching and discovery.

[0111] The identifier proxy sends the request intent to the identifier server. Based on the identifier attribute space, the identifier server matches the attributes in the request intent with the attributes registered in the entire network to find the attribute set that meets the business requirements, including the minimum attribute set and the full attribute set. It generates a 128-bit identifier hash corresponding to the full attribute set through three methods: template configuration, mapping function, or learning cognitive model. These hashes are used in the preparation phase of the two routing methods respectively.

[0112] The preparation phase of the routing method based on the minimum attribute set includes:

[0113] The identifier server will send the generated minimum attribute set and the identifier hash corresponding to the full attribute set to the identifier proxy;

[0114] The identifier proxy receives and caches the identifier hash and business requirements corresponding to the minimum attribute set and the full attribute set, providing a matching basis for subsequent distributed domain coordinate routing in this mode.

[0115] The identifier proxy constructs the identifier header based on the identifier hash corresponding to the cached minimum attribute set and full attribute set, as well as business requirements.

[0116] Preparation phase of routing methods based on full attribute sets:

[0117] The identifier server will send the generated full attribute set and the corresponding identifier hash to the network cognitive agent.

[0118] The network cognitive agent generates basic task strategies that adapt to current business needs based on the full attribute set and the corresponding identifier hash, combined with the network-wide status information.

[0119] The network cognitive agent distributes the generated basic task policy to the forwarding device, which receives the policy and synchronizes the identifier hash corresponding to the full attribute set.

[0120] Secondly, the identification usage phase. This phase, based on the identification packet header, utilizes a dual-mode approach: distributed routing based on the minimum attribute identifier and policy-based routing based on identifier hashes. This ensures deterministic forwarding of business data, guaranteeing high efficiency and reliability of data transmission. The minimum attribute identifier refers to the minimum set of attributes selected from the attribute space based on business requirements, necessary for resolution, addressing, routing, or forwarding. Distributed routing refers to a routing mode where forwarding nodes perform path calculation, entry maintenance, and packet forwarding based on local routing information, neighbor information, or identifier cache entries, without relying on centralized policy calculation. The identifier hash refers to the identifier hash corresponding to the full attribute set.

[0121] The business process generates business data and adds an identifier header to the business data generated by the business process to complete the data encapsulation. The identifier header contains two types of routing identifier information: the minimum attribute identifier and the identifier hash.

[0122] The identifier agent receives the encapsulated service data, parses the minimum attribute identifier and identifier hash in the identifier packet header, and synchronizes the minimum attribute identifier and identifier hash to the forwarding device.

[0123] Data forwarding is performed using a dual-mode routing mechanism based on the minimum attribute identifier and identifier hash:

[0124] Mode 1: Distributed forwarding based on the minimum attribute identifier. The forwarding device matches the minimum attribute identifier in the identifier packet header, determines the next hop exit through distributed domain coordinate forwarding logic, and executes efficient distributed routing.

[0125] Mode 2: Control plane policy path forwarding based on identifier hashes corresponding to the full attribute set. When the distributed routing path is unavailable, the forwarding device matches the identifier hash with the basic task policy issued by the network cognitive agent to ensure data transmission connectivity.

[0126] The terminal receives and forwards service data transmitted by the device, ensuring deterministic reception of the service data and guaranteeing the normal execution of the service.

[0127] Finally, the identifier recycling phase. This phase achieves closed-loop management of identifier resources throughout their lifecycle through a synchronized process of identifier lookup, reuse verification, and recycling. This includes the management of the entire process from identifier planning, generation, registration, activation, use, and modification, to freezing, invalidation, revocation, recycling, and archiving, thereby improving the reuse rate of identifier resources and ensuring the efficient use of network resources.

[0128] The business terminal / server initiates an identifier revocation request to the identifier agent based on business needs.

[0129] The identifier agent receives identifier recycling service requests, parses and standardizes the identifier recycling service requests to form identifier recycling intent, and performs identifier lookup to attempt to reuse existing identifier resources.

[0130] The identifier agent performs different processing based on the lookup results:

[0131] If the identification resource is successfully found, the subsequent data forwarding process will be executed directly based on the existing identification, without the need to re-initiate the attribute matching and discovery process;

[0132] If the identification resource lookup fails, the identification recycling intention is forwarded to the identification server to re-execute the attribute matching and discovery process and generate new identification information.

[0133] When data forwarding is complete, the identifier agent triggers the identifier reclamation mechanism and initiates an identifier reclamation request.

[0134] After the identifier agent reclaims the identifier resources corresponding to the business, it synchronizes the identifier reclamation status to the identifier server, updates the resource status in the identifier attribute space, and completes the closed-loop management of the identifier resource lifecycle.

[0135] Example 3

[0136] Based on Example 2, this example introduces an experimental example of a control surface full-process control system for spatiotemporal multidimensional identification networks:

[0137] Taking a predictive maintenance scenario in a smart factory as an example, a smart factory has deployed a spatiotemporal multi-dimensional identification intelligent network architecture, with a large number of intelligent sensors, industrial robots, edge computing nodes, and cloud analytics servers distributed throughout the factory. Now, let's take an industrial robot, numbered R-1023, initiating a vibration data analysis task to an edge computing node as an example:

[0138] During the identification attribute registration phase, the industrial robot R-1023, acting as a business terminal / server, submits a device attribute registration request to the identification agent based on its hardware capabilities and business carrying requirements. The registered attributes include the device type being IndustrialRobot_V2, QoS level being 3, high reliability and security level being 2, industrial intranet, geographical location being workshop A area coordinates being (125.36, 32.78), and task type being vibration data acquisition. After verifying the validity of the request, the identification agent forwards the standardized device attribute data to the identification server.

[0139] At the same time, the vibration data analysis service process deployed on the robot also submits a service attribute registration request to the identification agent. The service type is PredictiveMaintenance, the QoS level is 3, the security level is 2, the bandwidth requirement is 2Mbps, and the latency requirement is ≤10ms. After verification, it is forwarded to the identification server.

[0140] The edge computing node, acting as the execution terminal, submits a device attribute registration request to the identification agent, including the device type as EdgeNode_V1, computing power of 16 cores / 64GB, security level of 2, QoS level of 3, and geographical location of workshop A area coordinates (125.40, 32.75), which is then forwarded by the identification agent after verification.

[0141] The forwarding devices in the workshop, namely industrial switches, directly submit network device attribute registration requests to the identification server, including device capabilities of gigabit switching and topology information connecting robot R-1023, edge node E-01, and core switch.

[0142] After receiving all the above attribute registration data, the identification server completes the aggregation and standardization to build a unified identification attribute space. Subsequently, the network cognitive agent initiates an attribute space synchronization request to the identification server to obtain complete attribute information of all network devices, services and forwarding nodes, laying the data foundation for subsequent processes.

[0143] During the intent activation and policy generation phase, the industrial robot R-1023 sends a business request to the identification agent based on production task requirements: requesting the edge computing node to perform vibration data analysis, task ID=Vib_20260629_001. Upon receiving this business request, the identification agent parses and standardizes the request intent, extracting key attributes such as the target device type (EdgeNode_V1), QoS level (3), geographical location range (Workshop A area, latitude and longitude 125.35~125.45, 32.70~32.80), and task type (vibration data analysis). The agent then sends the encapsulated request intent to the identification server.

[0144] The identification server matches the attributes in the request intent against all registered attributes across the network based on the constructed identification attribute space. It finds that the edge computing node E-01, with coordinates (125.40, 32.75), perfectly matches the business requirements. Subsequently, the identification server generates a corresponding 128-bit identification hash using a template configuration method: incorporating all attributes such as device type, geographic location, QoS level, security level, and computing power. The hash generated by this mapping function is 0x8C2E4A6F1D3B5E7C9072AD46CF1835BE.

[0145] The identification server sends the identification hashes corresponding to the minimum attribute set and the full attribute set to the identification agent. The identification hashes corresponding to the full attribute set will be referred to as "identification hashes" in the following text. The identification agent receives and caches the identification hash and its corresponding business requirement information, constructing an identification packet header containing both the minimum attribute set identifier and the identification hash. Simultaneously, the identification server sends the full attribute set and identification hash to the network cognitive agent. Based on the full attribute set and identification hash, and combined with the network topology status information, including the link bandwidth, latency, and congestion status of each forwarding device, the network cognitive agent generates a basic task policy adapted to the current business requirements. This policy specifies the preferred path for data packets to be forwarded from robot R-1023 to edge node E-01 via industrial switches SW-03 and SW-07, and the alternative path via forwarding devices SW-02, SW-05, and SW-09. The basic task policy is then distributed to each forwarding device, which simultaneously receives the policy and saves the identification hash.

[0146] During the identification usage phase, the vibration data analysis process on robot R-1023 generates business data, namely time-series data collected by vibration sensors, and adds the identification packet header constructed by the identification agent to the business data to complete data encapsulation. After receiving the encapsulated business data, the identification agent parses the minimum attribute identifier and identifier hash in the identification packet header and synchronizes the identification information to the forwarding device SW-03. The forwarding device SW-03 uses a dual-mode routing mechanism to forward data based on the routing identifier information in the identification packet header.

[0147] The first mode is distributed forwarding based on the minimum attribute identifier: Forwarding device SW-03 matches the minimum attribute identifier in the identifier packet header, i.e., device type plus QoS plus security level, and queries the local distributed network coordinate forwarding table. Since the minimum attribute identifier and next-hop mapping relationship corresponding to edge node E-01 have been cached before, in this embodiment the next hop is forwarding device SW-07. Forwarding device SW-03 directly forwards the data packet to forwarding device SW-07 according to the distributed network coordinate forwarding logic. Forwarding device SW-07 also matches the local cached table entry based on the minimum attribute identifier to confirm that the target is edge node E-01, and completes the data delivery, realizing efficient distributed routing.

[0148] When the distributed routing path becomes unavailable, it automatically switches to the second mode, namely control plane policy path forwarding based on identifier hashes. Assuming that at a certain moment, the link between forwarding devices SW-03 and SW-07 is momentarily interrupted due to industrial electromagnetic interference, forwarding device SW-03 automatically switches after detecting the link failure. It matches the identifier hash 0x8C2E4A6F1D3B5E7C9072AD46CF1835BE corresponding to the full attribute set with the backup path policy previously issued by the network cognitive agent, forwarding the data packet via forwarding devices SW-02→SW-05→SW-09 to edge node E-01. Although this mode increases latency due to path length, it ensures the connectivity and reliability of data transmission. Finally, edge node E-01 receives the service data transmitted by the forwarding devices, completes vibration data analysis, and returns the analysis results to robot R-1023, ensuring the normal execution of predictive maintenance services.

[0149] During the tag recycling phase, after the predictive maintenance task is completed, robot R-1023 initiates a service termination request to the tag agent. The tag agent triggers the tag recycling mechanism, reclaims the tag hash 0x8C2E4A6F1D3B5E7C9072AD46CF1835BE resource under this service, and synchronizes the tag recycling status to the tag server, updates the resource status in the tag attribute space, and completes the closed-loop management of the tag resource lifecycle.

[0150] If other industrial robots subsequently initiate similar business requests, requiring the device type to be Industrial Robot, QoS level to be 3, and security level to be 2, the identifier agent can directly reuse the existing identifier resource 0x8C2E4A6F1D3B5E7C9072AD46CF1835BE when performing identifier lookup, without needing to re-initiate attribute matching and identifier generation, significantly improving the reuse rate of identifier resources.

[0151] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A full-process control method for the control surface of a spatiotemporal multidimensional identifier network, characterized in that, include: Based on the registered spatiotemporal multidimensional identifier attribute data, an identifier attribute space is constructed; Standardize and encapsulate business requests for intent activation and policy generation to generate request intents; Based on the aforementioned identifier attribute space, the attributes in the request intent are matched with the attributes registered across the entire network to generate a minimum attribute set, a full attribute set, and an identifier hash corresponding to the full attribute set that meet business requirements. Construct the identifier header based on the identifier hashes corresponding to the minimum attribute set and the full attribute set; Based on the full attribute set and the corresponding identifier hash, a basic task strategy is generated. Add the identifier header to the process-generated business data, generate encapsulated business data, and parse the identifier header in the encapsulated business data; Based on the identifier packet header in the encapsulated business data, distributed routing data forwarding is performed. When the distributed routing data forwarding path is unavailable, the basic task strategy is matched by the identifier hash corresponding to the full attribute set, and data forwarding is performed. The identifier recycling service request is standardized and encapsulated to generate an identifier recycling intent. Identifier resources are searched based on the identifier recycling intent. When data forwarding is completed, the identifier recycling mechanism is triggered to recycle the found identifier resources.

2. The full-process control method for the control surface of a spatiotemporal multidimensional identification network according to claim 1, characterized in that, The spatiotemporal multidimensional identifier attribute data includes device attribute data of the service terminal / server, business attribute data of the service process, device attribute data of the execution terminal, and network device attribute data of the forwarding device; The device attribute data of the service terminal / server includes the QoS, security level, and service type of the service terminal / server; The service attribute data of the service process includes the QoS, security level, and service type of the service process; The device attribute data of the execution terminal includes the device type, task type, capability level, security level, and QoS of the execution terminal; The network device attribute data of the forwarding device includes the device capabilities and topology information of the forwarding device.

3. The full-process control method for the control surface of a spatiotemporal multidimensional identification network according to claim 1, characterized in that, Based on the aforementioned identifier attribute space, the attributes in the request intent are matched with the attributes already registered across the entire network to generate a minimum attribute set, a full attribute set, and an identifier hash corresponding to the full attribute set that meet business requirements, including: Based on the aforementioned identifier attribute space, the attributes in the request intent are matched with the attributes already registered across the entire network to generate an attribute set that meets business requirements; the attribute set includes a minimum attribute set and a full attribute set. Based on the full attribute set, the identifier hash corresponding to the full attribute set is generated through template configuration, mapping function or learning cognitive model.

4. The full-process control method for the control surface of a spatiotemporal multidimensional identification network according to claim 1, characterized in that, Based on the identifier packet header in the received encapsulated service data, distributed routing data forwarding is performed. When the distributed routing data forwarding path is unavailable, data forwarding is performed by matching the identifier hash corresponding to the full attribute set with the basic task strategy, including: Based on the identifier packet header in the received encapsulated service data, the next hop exit is determined through distributed domain coordinate forwarding logic, and distributed routing data forwarding is executed. When the distributed routing data forwarding path is unavailable, the basic task strategy is matched by the identifier hash corresponding to the full attribute set, and data forwarding is executed.

5. The full-process control method for the control surface of a spatiotemporal multidimensional identification network according to claim 1, characterized in that, Locating identifier resources based on identifier recycling intent includes: Search for identifier resources based on identifier recycling intent; If the identification resource is found successfully, subsequent data forwarding will be performed based on the found identification resource; If the identification resource lookup fails, the attribute matching and discovery process is re-executed to generate a new identification resource, and subsequent data forwarding is performed based on the new identification resource.

6. The full-process control method for the control surface of a spatiotemporal multidimensional identification network according to claim 1, characterized in that, It also includes updating the identifier attribute space based on the found identifier resources.

7. A full-process control system for a spatiotemporal multidimensional identification network, characterized in that, include: The identifier proxy is used for: standardizing and encapsulating received intent activation and policy generation business requests, generating request intents, and sending the request intents to the identifier server; receiving and caching the identifier hashes corresponding to the minimum attribute set and the full attribute set, and constructing identifier headers; adding identifier headers to the business data generated during the receiving process, generating encapsulated business data, parsing the identifier headers in the encapsulated business data, and sending it to the forwarding device; standardizing and encapsulating received identifier reclamation business requests, generating identifier reclamation intents, searching for identifier resources based on the identifier reclamation intents, and triggering the identifier reclamation mechanism when data forwarding is completed to reclaim the found identifier resources; The forwarding device is used to: receive the basic task policy and the identifier hash corresponding to the full attribute set; perform distributed routing data forwarding based on the identifier packet header in the received encapsulated business data; and when the distributed routing data forwarding path is unavailable, perform data forwarding by matching the basic task policy with the identifier hash corresponding to the full attribute set. The identifier server is used to: construct an identifier attribute space based on the registered spatiotemporal multidimensional identifier attribute data; Based on the aforementioned identifier attribute space, the attributes in the received request intent are matched with the attributes registered across the entire network to generate a minimum attribute set, a full attribute set, and an identifier hash corresponding to the full attribute set that meet business requirements. The minimum attribute set and the identifier hash corresponding to the full attribute set are sent to the identifier proxy, and the full attribute set and the identifier hash corresponding to the full attribute set are sent to the network cognitive proxy. The network cognitive agent is used to: receive the full attribute set and the corresponding identifier hash, generate a basic task policy based on the full attribute set and the corresponding identifier hash, and send the basic task policy and the corresponding identifier hash to the forwarding device.

8. The full-process control system for the control surface of a spatiotemporal multidimensional identification network according to claim 7, characterized in that, The identifier proxy is also used for: sending received identifier attribute registration requests to the identifier server; and sending found identifier resources to the identifier server. The forwarding device is also used to: send a network device registration request to the identification server; The identifier server is also used for: registering spatiotemporal multidimensional identifier attribute data and constructing an identifier attribute space based on received identifier attribute registration requests and network device registration requests from forwarding devices; and updating the identifier attribute space based on received identifier resources.

9. The full-process control system for the control surface of a spatiotemporal multidimensional identification network according to claim 8, characterized in that, Also includes: The service terminal / server is used to: send device attribute registration requests, intent activation and policy generation service requests, and identifier revocation service requests to the identifier agent during identifier attribute registration. The business process is used for: sending business attribute registration requests to the identifier agent during the identifier attribute registration process, and generating business data in the process. The execution terminal is used to: send a device attribute registration request for the execution terminal in the identification attribute registration to the identification agent, and receive forwarding data sent by the forwarding device; The device attribute registration request for the service terminal / server includes registration requests for the QoS, security level, and service type of the service terminal / server; the service attribute registration request for the service process includes registration requests for the QoS, security level, and service type of the service process; the device attribute registration request for the execution terminal includes registration requests for the device type, task type, capability level, security level, and QoS of the execution terminal; and the network device registration request for the forwarding device includes registration requests for the device capabilities and topology information of the forwarding device.

10. The full-process control system for the control surface of a spatiotemporal multidimensional identification network according to claim 7, characterized in that, The network cognitive agent is also used to: send attribute space synchronization requests to the identification server, receive the identification attribute space sent by the identification server, and obtain attribute information for generating basic task strategies.

Images