A cloud-native network identification mapping method

Abstract

The application provides a cloud native network identification mapping method, realizes intelligent connection from a physical terminal to a cloud service, and guarantees service continuity in a cloud native environment. The method comprises the following steps: a cloud native network generates and stores terminal attribute identification and access attribute identification of a terminal, generates service attribute identification corresponding to each service of the terminal based on a plurality of service provided by a network twin space for the terminal, and registers the service attribute identification to a distributed DNS system; the cloud native network generates a global ID for the terminal, and establishes and maintains a mapping relationship between the global ID and the terminal attribute identification, the access attribute identification, the service attribute identification, channel attribute identification, connection attribute identification and service attribute identification of the terminal; and the terminal realizes service connection establishment and data transmission through the service attribute identification, and the mapping relationship is updated in real time in the process.

Description

Technical Field

[0001] This application relates to the field of cloud-native technology, specifically to a cloud-native network identifier mapping method. Background Technology

[0002] In the traditional Internet architecture, IP addresses serve as an important tool for identifying user identity and location, and are used for connection management of various services and authentication of user identity.

[0003] However, in scenarios where user locations frequently change, the resulting IP address changes not only lead to service connection instability but may also trigger a series of security vulnerabilities, including user identity spoofing and malicious attacks. For example, when users switch networks between different geographical locations, they may face frequent IP address changes, leading to connection interruptions or delays and impacting the user experience. Furthermore, frequent IP address changes make it difficult to maintain stable service connections, especially for online games and video conferencing where stability is critical. Additionally, while some websites or services may record IP addresses to identify user login status and security, the volatility of IP addresses allows malicious users to bypass authentication mechanisms by forging or dynamically changing their IP addresses, enabling attacks such as identity theft and data tampering.

[0004] Therefore, in order to overcome the above problems, how to build a more reliable identity authentication mechanism and ensure the stability of service connections is an issue that needs to be addressed. Summary of the Invention

[0005] This application provides a cloud-native network identifier mapping method to ensure the stability of service connections.

[0006] To achieve the above objectives, this application adopts the following technical solution: Firstly, this application provides a cloud-native network identifier mapping method, wherein the cloud-native network includes a network twin space providing various service functions, and the method includes: The cloud-native network generates and stores terminal attribute identifiers and access attribute identifiers for the terminal, and based on the network twin space, it provides various service services for the terminal, generates service attribute identifiers for each service service, and registers them to the distributed DNS system. Cloud-native networks generate a global ID for each terminal and establish and maintain a mapping relationship between the global ID and the terminal's terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and service attribute identifier. Establishing and maintaining the mapping relationship between the global ID and the terminal's attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and service attribute identifier. The process includes: The terminal's upper-layer application initiates a connection request to the cloud-native network through a unique service attribute identifier; Cloud-native networks are based on a distributed DNS system to resolve the network twin space corresponding to the unique service attribute identifier; and generate the connection attribute identifier of the corresponding service based on the pre-defined service level agreement; then select a path based on the connection attribute identifier to generate a channel attribute identifier composed of multiple physical links. Cloud-native networks add service attribute identifiers to the data streams transmitted by terminals, and select physical links for data transmission based on channel attribute identifiers and service attribute identifiers; During the process, the mapping relationship is updated in real time.

[0007] Secondly, a cloud-native network identifier mapping system is provided, which includes unified identifier management service, terminal management service, access management service, network twin identifier management service, domain name management service, channel management service, connection management service, and service management service. Terminal management service, used to generate and store terminal attribute identifiers; Access management service, used to generate and store the access attribute identifiers of terminals; Network twin identifier management service is used to generate service attribute identifiers for each service provided to the terminal based on the network twin space for various business services provided to the terminal. Domain name management service is used to register the service attribute identifiers corresponding to each business service to the distributed DNS system; The unified identifier management service is used to generate a global ID for a terminal and to establish and maintain the mapping relationship between the global ID and the terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier and service attribute identifier. The connection management service is used to receive connection requests initiated by the terminal's upper-layer application through a unique service attribute identifier; Domain name management service is used to resolve the network twin space corresponding to the unique service attribute identifier based on the distributed DNS system; The connection management service is also used to generate connection attribute identifiers for corresponding services based on pre-defined service level agreements. Channel management service is used to select paths based on connection attribute identifiers and generate channel attribute identifiers composed of multiple physical links; The service management service is used to add service attribute identifiers to the data streams transmitted by the terminal, and select physical links for data transmission based on channel attribute identifiers and service attribute identifiers; The mapping relationship is updated in real time.

[0008] In this embodiment, a global ID is used as the core anchor point. Through dynamic mapping of the global ID and multiple dynamic attribute identifiers (terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and business attribute identifier), intelligent connection from physical terminal to cloud service is achieved, while ensuring the continuity of services in the cloud-native environment.

[0009] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a schematic diagram of a cloud-native network identifier mapping system provided in an embodiment of this application. Detailed Implementation

[0012] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. At the same time, in the description of the embodiments of this application, the terms "first," "second," etc., are only used to distinguish descriptions and should not be construed as indicating or implying relative importance. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0013] Figure 1 This is a schematic diagram of a cloud-native network identifier mapping method provided in an embodiment of this application.

[0014] The cloud-native network includes a network twin space that provides various business services. The process of this cloud-native network identifier mapping method is as follows: I. Terminal registration, identifier initialization, and network twin space construction The cloud-native network generates and stores terminal attribute identifiers and access attribute identifiers for the terminal. Based on the network twin space, it provides various service services for the terminal, generates service attribute identifiers for each service service, and registers them with the distributed DNS system.

[0015] Cloud-native networks generate a global ID for each terminal and establish and maintain a mapping relationship between the global ID and the terminal's attribute identifiers, access attribute identifiers, service attribute identifiers, channel attribute identifiers, connection attribute identifiers, and service attribute identifiers.

[0016] Among them, the terminal attribute identifier and access attribute identifier of the cloud-native network generation and storage terminal can be understood as, The terminal registers its terminal attribute identifier with the cloud-native network and stores the terminal attribute identifier. Specifically, the stored terminal attribute identifier is stored in the terminal attribute database within the cloud-native network.

[0017] In addition, terminal attribute identifiers include information such as device type, model, serial number, MAC address, and capability characteristics (supported communication protocols, storage capacity, etc.), which are not specifically limited here.

[0018] Cloud-native networks assign physical layer access attribute identifiers and network twin service access attribute identifiers to terminals based on terminal attribute identifiers, thereby completing the physical-virtual dual-domain address mapping of terminals.

[0019] Among them, based on the network twin space, various service services are provided to the terminal. A service attribute identifier corresponding to each service service is generated for the terminal and registered to the distributed DNS system. This can be understood as: The network twin space provides various services to the terminal, including mobile agent, transport agent, and security agent. There may be other services as well, which will not be listed here. This application takes mobile agent, transport agent, and security agent as examples. Then, a unique service attribute identifier is generated for each of the mobile agent, transport agent, and security agent on the terminal, and these are registered with the distributed DNS system. This makes it convenient for the upper-layer application of the terminal to determine the corresponding service of the network twin space when it initiates a connection request to the cloud-native network through the unique service attribute identifier. Please refer to the following introduction for understanding.

[0020] In addition, the service attribute identifier mentioned above can be in URN format. The service attribute identifier can uniquely identify a type of service in the cloud-native network, regardless of the location of the terminal.

[0021] II. Dynamic updates of mapping relationships (service connection establishment, data transmission) The aforementioned mapping relationship between the global ID and the terminal's attribute identifiers (terminal, access, service, channel, connection, and service attributes) is updated in real time during the establishment of service connections and data transmission between the terminal and the cloud-native network. Specifically: The terminal's upper-layer application initiates a connection request to the cloud-native network through a unique service attribute identifier; Cloud-native networks are based on a distributed DNS system to resolve the network twin space corresponding to the unique service attribute identifier; and generate the connection attribute identifier of the corresponding service based on a pre-defined service level agreement; then select a path based on the connection attribute identifier to generate a channel attribute identifier composed of multiple physical links. Cloud-native networks add service attribute identifiers to the data streams transmitted by terminals, and select physical links for data transmission based on channel attribute identifiers and service attribute identifiers.

[0022] The pre-established service level agreement can be either manually created or a formal contract or agreement reached between the service provider and the end user. It clearly stipulates the quality standards, performance indicators, availability requirements, support services, fault handling, and other aspects of the network service to ensure that the network service meets the expectations of both parties.

[0023] The above process generates connection attribute identifiers for corresponding services based on pre-defined service level agreements; then, based on these connection attribute identifiers, a path is selected to generate channel attribute identifiers composed of multiple physical links. This can be understood as follows: Based on pre-defined service level agreements (SLAs), cloud-native networks can generate connection attribute identifiers corresponding to services. These identifiers are used to precisely configure connection quality within the network to meet the needs of different services. The connection attribute identifiers include metadata such as session context and QoS policies. Subsequently, based on these connection attribute identifiers, and considering comprehensive analysis of network topology, latency, bandwidth, and other dimensions, a channel attribute identifier (i.e., a transmission channel composed of multiple physical links) is generated.

[0024] The aforementioned cloud-native network adds service attribute identifiers to the data streams transmitted by the terminals, and selects physical links for data transmission based on channel attribute identifiers and service attribute identifiers. This can be understood as follows: The service attribute identifiers include: data classification, data priority, and data encryption strategy. During actual data transmission, the cloud-native network will automatically select the most suitable physical link based on the attached channel attribute identifiers and service attribute identifiers to ensure fast and stable data transmission.

[0025] Furthermore, cloud-native networks rely on an adaptive dynamic scheduling mechanism, which can dynamically adjust connection attribute identifiers and update transmission paths based on changes in network load, service demands, and quality of service during operation, while also adjusting channel attribute identifiers accordingly. Moreover, when a physical link fails, the cloud-native network can automatically switch to a backup path to ensure service continuity.

[0026] It should also be noted that cloud-native networks also verify the identity of terminals and assign terminal access permissions. When a terminal sends a connection request, the system determines whether to connect based on the pre-assigned terminal access permissions.

[0027] Furthermore, the names of the terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and service attribute identifier in this application are merely examples, and may be other names such as terminal identifier, access identifier, service identifier, channel identifier, connection identifier, and service identifier, or other possible names, without limitation.

[0028] In summary, this application uses a global ID as the core anchor point and dynamically maps the global ID to multiple dynamic attribute identifiers (terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and business attribute identifier) ​​to achieve intelligent connection from physical terminals to cloud services, while ensuring service continuity in the cloud-native environment.

[0029] The above combination Figure 1 This application provides a detailed description of the cloud-native network identifier mapping method provided in its embodiments. The following, in conjunction with... Figure 1 This document provides a detailed description of the cloud-native network identifier mapping method system used to execute the embodiments of this application.

[0030] like Figure 1 As shown, the system includes unified identifier management service, terminal management service, access management service, network twin identifier management service, domain name management service, channel management service, connection management service, and service management service.

[0031] Terminal management service, used to generate and store terminal attribute identifiers; Access management service, used to generate and store the access attribute identifiers of terminals; Network twin identifier management service is used to generate service attribute identifiers for each service provided to the terminal based on the network twin space for various business services provided to the terminal. Domain name management service is used to register the service attribute identifiers corresponding to each business service to the distributed DNS system; The unified identifier management service is used to generate a global ID for a terminal and to establish and maintain the mapping relationship between the global ID and the terminal's terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and service attribute identifier. The connection management service is used to receive connection requests initiated by the terminal's upper-layer application through a unique service attribute identifier; Domain name management service is used to resolve the network twin space corresponding to the unique service attribute identifier based on a distributed DNS system; The connection management service is also used to generate connection attribute identifiers for corresponding services based on pre-defined service level agreements. Channel management service is used to select paths based on connection attribute identifiers and generate channel attribute identifiers composed of multiple physical links; The service management service is used to add service attribute identifiers to the data streams transmitted by the terminal, and select physical links for data transmission based on channel attribute identifiers and service attribute identifiers; The mapping relationship is updated in real time.

[0032] It should be noted that the aforementioned terminal management service is used to generate and store the terminal attribute identifier, and the access management service is used to generate and store the terminal's access attribute identifier, including: The terminal management service is used to receive registration information sent by the terminal, generate terminal attribute identifiers based on the registration information, and store the terminal attribute identifiers. Access management service is used to assign physical layer access attribute identifiers and network twin service access attribute identifiers to terminals based on terminal attribute identifiers, thereby completing the physical-virtual dual-domain address mapping of the terminal.

[0033] In addition, the system also includes an authentication management service for verifying the identity of terminals and assigning terminal access permissions.

[0034] Furthermore, the specific implementation of the above system is basically similar to the method implementation, so the description is relatively simple. For relevant details, please refer to the description of the method implementation.

[0035] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences between it and other embodiments.

[0036] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than those shown in the embodiments and still achieve the desired result. Furthermore, the specific order or sequential order shown in the drawings is not necessarily required to achieve the desired result; in some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0037] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A cloud-native network identifier mapping method, characterized in that, The cloud-native network includes a network twin space that provides multiple service functions, and the method includes: The cloud-native network generates and stores the terminal attribute identifier and access attribute identifier of the terminal, and generates a service attribute identifier corresponding to each service service for the terminal based on the various service services provided by the network twin space, and registers it to the distributed DNS system. The cloud-native network generates a global ID for the terminal and establishes and maintains a mapping relationship between the global ID and the terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier and service attribute identifier of the terminal; The process of establishing and maintaining the mapping relationship between the global ID and the terminal attribute identifier, access attribute identifier, service attribute identifier, channel attribute identifier, connection attribute identifier, and service attribute identifier of the terminal includes: The upper-layer application of the terminal initiates a connection request to the cloud-native network through a unique service attribute identifier; The cloud-native network is based on a distributed DNS system to resolve the network twin space corresponding to the unique service attribute identifier; and generates a connection attribute identifier for the corresponding service based on a pre-defined service level agreement; then selects a path based on the connection attribute identifier to generate a channel attribute identifier composed of multiple physical links. The cloud-native network adds a service attribute identifier to the data stream transmitted by the terminal, and selects a physical link for data transmission based on the channel attribute identifier and the service attribute identifier. During this process, the mapping relationship is updated in real time.

2. The cloud-native network identifier mapping method according to claim 1, characterized in that, The terminal attribute identifier and access attribute identifier of the cloud-native network generating and storing terminals include: The terminal registers a terminal attribute identifier with the cloud-native network and stores the terminal attribute identifier; The cloud-native network assigns physical layer access attribute identifiers and network twin service access attribute identifiers to the terminal based on the terminal attribute identifiers, thereby completing the physical-virtual dual-domain address mapping of the terminal.

3. The cloud-native network identifier mapping method according to claim 1, characterized in that, The cloud-native network also verifies the identity of the terminal and assigns access permissions to the terminal.

4. The cloud-native network identifier mapping method according to claim 1, characterized in that, The network twin space provides the terminal with various service functions, including mobile proxy, transport proxy, and security proxy.

5. The cloud-native network identifier mapping method according to claim 1, characterized in that, The business attribute identifiers include: data classification, data priority, and data encryption strategy.

Images