WO2023024663A1 - 路由和云资源注册方法及装置、存储介质和电子装置 - Google Patents

路由和云资源注册方法及装置、存储介质和电子装置 Download PDF

Info

Publication number
WO2023024663A1
WO2023024663A1 PCT/CN2022/099005 CN2022099005W WO2023024663A1 WO 2023024663 A1 WO2023024663 A1 WO 2023024663A1 CN 2022099005 W CN2022099005 W CN 2022099005W WO 2023024663 A1 WO2023024663 A1 WO 2023024663A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud resource
cloud
node
application data
information
Prior art date
Application number
PCT/CN2022/099005
Other languages
English (en)
French (fr)
Inventor
黄光平
谭斌
彭少富
郭勇
黄兵
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023024663A1 publication Critical patent/WO2023024663A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1042—Peer-to-peer [P2P] networks using topology management mechanisms

Definitions

  • Embodiments of the present invention relate to the communication field, and in particular, relate to a routing and cloud resource registration method and device, a storage medium, and an electronic device.
  • the routing and forwarding technology under the current network architecture is essentially a specific physical address-oriented addressing technology, which solves the network transmission of business data between certain source and destination nodes.
  • Embodiments of the present invention provide a routing and cloud resource registration method and device, a storage medium and an electronic device to at least solve the problem that the traditional network routing and forwarding mechanism based on a specific physical address in the related art cannot adapt to new business and traffic models , resulting in low macro resource utilization and complicated application development and operation and maintenance.
  • a routing method including: acquiring predetermined information carried in a received application data packet, wherein the predetermined information includes: an application data packet for processing the application data packet The cloud resource identifier of the cloud resource; according to the cloud resource identifier routing table, determine the information of the cloud node and/or cloud resource instance corresponding to the predetermined information, wherein the cloud resource identifier routing table uses the cloud resource identifier as an index, Recording the information of the cloud node and/or cloud resource instance used to provide the cloud resource identified by the cloud resource identifier; routing and forwarding the application data message according to the determined information of the cloud node and/or cloud resource instance .
  • a cloud resource registration method including: receiving cloud resource information reported by a cloud resource provider, wherein the cloud resource information includes: a cloud resource identifier of the provided cloud resource, and It is used to provide information about cloud nodes and/or cloud resource instances of the cloud resource; generating or updating a cloud resource identifier routing table according to the cloud resource information, wherein the cloud resource identifier routing table is defined by the cloud resource identifier as The index records the information of the cloud node and/or the cloud resource instance used to provide the cloud resource identified by the cloud resource identifier.
  • a routing device including: a first determination module configured to obtain predetermined information carried in the received application data packet, wherein the predetermined information includes: The cloud resource identifier of the cloud resource of the application data in the application data message; the second determination module is configured to determine the information of the cloud node and/or cloud resource instance corresponding to the predetermined information according to the cloud resource identifier routing table, wherein , the cloud resource identifier routing table takes the cloud resource identifier as an index, and records the information of the cloud node and/or cloud resource instance used to provide the cloud resource identified by the cloud resource identifier; the routing and forwarding module is configured according to the determined Information routing of the cloud node and/or cloud resource instance and forwarding of the application data packet.
  • a cloud resource registration device including: a receiving module configured to receive cloud resource information reported by the cloud resource provider, wherein the cloud resource information includes: the provided cloud resource The cloud resource identification, and the information used to provide the cloud node and/or cloud resource instance of the cloud resource; the routing table maintenance module is configured to generate or update the cloud resource identification routing table according to the cloud resource information, wherein, the The cloud resource identifier routing table uses the cloud resource identifier as an index, and records information about cloud nodes and/or cloud resource instances used to provide the cloud resources identified by the cloud resource identifier.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to perform any one of the above methods when running Steps in the examples.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above Steps in the method examples.
  • the application data message received by the network carries predetermined information including a cloud resource identifier, and the cloud resource identifier can identify a cloud resource for processing application data, and the network can determine the cloud resource identifier routing table according to the cloud resource identifier. Reserving the information of the cloud node and/or cloud resource instance corresponding to the reservation information, so as to realize the routing and forwarding of the application data packet according to the determined information of the cloud node and/or cloud resource instance corresponding to the reservation information.
  • the sender of the application data message no longer needs to specify the target cloud node or cloud resource instance, but only needs to carry the cloud resource identifier of the required cloud resource, and the network calculates and determines the cloud node and cloud resource that meet the application requirements. /or cloud resource instances, and further route and forward the corresponding application data packets.
  • this solution creates a new cloud resource control scheduling mode, and the cloud resources are completed by the network.
  • the control scheduling and data flow routing and forwarding solve the problem that the application side has insufficient grasp of cloud resource status and network conditions, so it cannot schedule the most suitable cloud resources, resulting in low resource utilization. It also simplifies the development and operation process of the application side
  • the work on cloud resource scheduling and configuration solves the complex problems of application development and operation and maintenance.
  • Fig. 1 is a kind of routing method network routing of the embodiment of the present invention and the hardware structural block diagram of forwarding node;
  • Fig. 2 is a flowchart of a routing method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a routing method applied to a network entry node according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a routing method applied to a network egress node according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a cloud resource registration method according to an embodiment of the present invention.
  • Fig. 6 is a structural block diagram of a routing device according to an embodiment of the present invention.
  • Fig. 7 is a structural block diagram of a cloud resource registration device according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a routing mechanism and architecture based on resource and service identifiers according to an exemplary embodiment of the present invention.
  • FIG. 9 is a flow chart of basic routing and forwarding based on resource and service identifiers according to Exemplary Embodiment 1 of the present invention.
  • FIG. 10 is a schematic structural diagram of resource and service identifiers in a non-IP address structure according to Exemplary Embodiment 2 of the present invention.
  • Fig. 11 is a schematic diagram of a resource and service identifier structure of an Anycast (Anycast) address structure according to Exemplary Embodiment 3 of the present invention.
  • cloud resources are gradually sinking, and applications and services are gradually showing a trend of ubiquitous deployment along with cloud resources.
  • Traditional networks perform routing and forwarding based on specific physical addresses. It has been unable to adapt to new business and traffic models.
  • the separation mode of network and business based on the best-effort mode of traditional networks also needs to be improved, and application resources need to be Comprehensive selection and optimization of network resources to meet the final service experience requirements.
  • the perception, scheduling, and orchestration of cloud resources and services are currently focused on providing solutions at the application layer, that is, the control and scheduling of specific cloud resources and applications are managed by the application provider in a closed and chimney manner.
  • the advantage of this model is that it realizes the decoupling of applications from network transmission and routing, and gives full flexibility to applications.
  • the disadvantage is that under the industry trend of ubiquitous computing and storage, this island-style resource and business management and control model, As a result, the utilization rate of macro resources is low, and application development and operation and maintenance are becoming more and more complicated and costly.
  • an embodiment of the present invention provides a cloud resource identification-based routing solution and a cloud resource registration solution.
  • the sender of the application data message no longer needs to specify the target cloud node or cloud resource instance, but only needs to carry the cloud resource identifier of the required cloud resource, and the network calculates and determines the cloud node and cloud resource that meet the application requirements. /or cloud resource instances, and further route and forward the corresponding application data packets.
  • this solution creates a new cloud resource control scheduling mode, and the cloud resources are completed by the network.
  • control scheduling and data flow routing and forwarding solve the problem that the application side has insufficient grasp of cloud resource status and network conditions, so it cannot schedule the most suitable cloud resources, resulting in low resource utilization. It also simplifies the development and operation process of the application side
  • the work on cloud resource scheduling and configuration solves the complex problems of application development and operation and maintenance.
  • the method embodiment of the routing method provided in the embodiment of the application can be executed in a network routing and forwarding node (including a network entry node and/or a network exit node) or a similar computing device; the cloud provided in the embodiment of the application
  • the method embodiment of the resource registration method can be executed in a network edge node or a similar computing device.
  • Network routing and forwarding nodes and network edge nodes are all nodes in the network, and their hardware structures are similar. Taking the example of running on network routing and forwarding nodes, Figure 1 is a network of a routing method according to an embodiment of the present invention Hardware structure block diagram of routing and forwarding nodes.
  • the network routing and forwarding node may include one or more (only one is shown in Figure 1) processors 102 (the processor 102 may include but not limited to microprocessor MCU or programmable logic device FPGA, etc. processing device) and a memory 104 for storing data, wherein the above-mentioned network routing and forwarding node may also include a transmission device 106 and an input and output device 108 for communication functions.
  • processors 102 may include but not limited to microprocessor MCU or programmable logic device FPGA, etc. processing device
  • memory 104 for storing data
  • the above-mentioned network routing and forwarding node may also include a transmission device 106 and an input and output device 108 for communication functions.
  • FIG. 1 is only for illustration, and it does not limit the structure of the above-mentioned network routing and forwarding nodes.
  • a network routing and forwarding node may also include more or fewer components than shown in FIG. 1 , or have a different configuration than that shown in FIG. 1
  • the memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the routing (or cloud resource registration) method in the embodiment of the present invention, the processor 102 runs the computer program stored in the memory 104 program, so as to execute various functional applications and data processing, that is, to realize the above-mentioned method.
  • the memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely from the processor 102, and these remote memories may be connected to network routing and forwarding nodes through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 106 is configured to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the network routing and forwarding node.
  • the transmission device 106 includes a network interface controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • FIG. 2 is a flow chart of the routing method according to an embodiment of the present invention, as shown in FIG. 2 As shown, the process includes the following steps:
  • Step S202 acquiring reservation information carried in the received application data message, wherein the reservation information includes: a cloud resource identifier of a cloud resource used to process the application data in the application data message.
  • cloud resources cover all resources provided through the network, including but not limited to computing, storage, application software and services, etc., and the most typical ones are cloud resources and services.
  • the category of the cloud resource is generally divided based on the attribute of the cloud resource, and the attribute of the cloud resource includes at least one of the following: the service category of the cloud resource, the service identifier of the cloud resource, the computing resource included in the cloud resource , storage resources included in the cloud resources, and interface parameters of the cloud resources.
  • the cloud resource identifier has nothing to do with the ownership and/or location of the cloud resource, that is to say, for the application side, although it carries the cloud resource identifier in the application data message, it does not allocate and the cloud resources used for scheduling, that is, it does not specify a specific cloud node or cloud resource on a cloud resource instance, but only indicates the specific needs of these application data through an attribution and/or location-independent cloud resource identifier Which cloud resource to handle. This undoubtedly simplifies the work of scheduling and configuring cloud resources during the development and operation of the application side, and solves the complex problems of application development and operation and maintenance.
  • the application may further put forward supplementary requirements for the resource.
  • the predetermined information also includes at least one of the following: aggregation type of cloud resource, supporting resource attribute, and service parameter.
  • aggregation type of cloud resource By including the aggregation category and supporting resource attributes of cloud resources in the predetermined information, it is convenient for the network side to quickly screen the required cloud resources, improve the retrieval efficiency of cloud resource identification, and more accurately propose the required resources.
  • the requirements for the supporting properties is also sent to the network as an optional information included in the predetermined information.
  • the application data packet is generally sent by a device including an application client such as a terminal, and the device can carry the predetermined information in the application data packet in various possible ways, for example, the application data packet can be in the following ways At least one of which carries the predetermined information:
  • DOH Destination Option Header
  • IPv6-based source routing technology Segment Routing version 6, SRv6
  • the anycast address corresponding to the cloud resource identifier is carried in the destination address field of the header of the application data message, wherein the prefix of the anycast address is defined as the cloud resource identifier; or, the The anycast address corresponds to a unique cloud resource identifier, and the mapping relationship between the anycast address and the cloud resource identifier has global consistency.
  • Step S204 determine the information of the cloud node and/or cloud resource instance corresponding to the predetermined information according to the cloud resource identifier routing table, wherein the cloud resource identifier routing table uses the cloud resource identifier as an index, and records are used to provide the Information about the cloud node and/or cloud resource instance of the cloud resource identified by the cloud resource identifier.
  • the information of the cloud node may include at least one of the following: a gateway address of the cloud node, and cloud resource status data of the cloud node. That is to say, in the cloud resource identifier routing table, the gateway address of the cloud node used to provide the cloud resource indicated by the cloud resource identifier can be recorded, and the status of the cloud resource on the cloud node can also be recorded, for example, whether the cloud resource is busy Whether it is still idle, application traffic on cloud resources, etc., the cloud resource status data of the cloud node essentially reflects the usage status of cloud resources on the current cloud node, and the network can select a relatively idle cloud node as the predetermined information based on this information The corresponding cloud node.
  • the information of the cloud resource instance includes at least one of the following: the address of the cloud resource instance, the status of the cloud resource instance, and the information of the cloud node to which the cloud resource instance belongs. Since cloud resource instances can run on virtual machines, physical hosts, containers, etc., the address of the cloud resource instance mentioned here may be the virtual machine address, physical host address, container address, etc. of the cloud resource instance. The address of the cloud node to which the cloud resource instance belongs and the address of the cloud resource instance can specify which cloud node and which cloud resource instance the application data message will be sent to, so as to perform proper routing and forwarding.
  • the information of the cloud resource instance may also include the state of the cloud resource instance, that is, in the cloud resource identification routing table, the state of the cloud resource instance may be recorded, for example, whether the cloud resource instance is busy or idle, whether the cloud resource instance is The application traffic on the resource instance, etc., the status of the cloud resource instance essentially reflects the usage status of the cloud resource on the current cloud resource instance, and the network can select a relatively idle cloud resource instance as the corresponding cloud resource instance according to the predetermined information. Cloud resource instance.
  • the cloud resource identifier routing table may be maintained at a network routing and forwarding node, wherein the network routing and forwarding node includes: a network entry node and/or a network exit node of the application data message .
  • the cloud resource identification routing table can also be maintained in the network centralized control unit, and synchronized to the network routing and forwarding node periodically or based on the request, wherein the network routing and forwarding node includes: the application A network entry node and/or a network exit node for data packets.
  • the sender of the application data message no longer needs to specify the target cloud node or cloud resource instance, but only needs to carry the cloud resource identifier of the required cloud resource, which is calculated by the network and determined to meet the requirements of the application.
  • Required cloud nodes and/or cloud resource instances Since the network maintains the cloud resource identification routing table, it knows all the cloud nodes registered in the network that can provide the corresponding type of cloud resources, and even knows that there are several corresponding cloud resource instances on the cloud nodes. Therefore, the network is responsible for the current
  • the application data message selects cloud nodes and/or cloud resource instances, which has more flexible and broad freedom of choice, and has a larger scheduling range.
  • the network itself can more accurately grasp the current network topology and the network status to each cloud node, and when it is determined that there are multiple cloud nodes and/or cloud resource instances that can meet the requirements of the predetermined information
  • a cloud node and/or cloud resource instance can be selected according to the network status of the multiple cloud nodes and/or cloud resource instances (generally the one with the best network status, and other ones can also be set according to the requirements of the application) rule) as the cloud node and/or cloud resource instance corresponding to the predetermined information.
  • the cloud node and/or cloud resource instance determination scheme based on the cloud resource identification routing table and the cloud node and/or cloud resource instance determination scheme based on the network status can be jointly executed (that is, both of them serve as constraints at the same time ), it can also be performed progressively (that is, one of the determination schemes is executed first, and then another determination scheme is executed within the scope of the determined result), which is not limited in the present invention.
  • determining the information of the cloud node and/or cloud resource instance corresponding to the predetermined information may include: according to the cloud resource identification routing table and to the plurality of cloud nodes and/or cloud resource instances The network status of the predetermined information is determined to determine the information of the cloud node and/or cloud resource instance corresponding to the predetermined information.
  • a new cloud resource management, control and scheduling mode is provided, and the network completes the management, control and scheduling of cloud resources, which solves the lack of grasp of the cloud resource status and network conditions on the application side As a result, it is impossible to schedule the most suitable cloud resources, resulting in low resource utilization.
  • the network side can schedule cloud resources more autonomously and reasonably.
  • the cloud resource management and control scheduling mode in the embodiment of the present invention can support various types of cloud node and/or cloud resource instance determination policies, and there is no specific limitation on this.
  • Step S206 routing and forwarding the application data packet according to the determined information of the cloud node and/or cloud resource instance.
  • step S204 in the case that the received application data message is the first application data message in the application data flow to which it belongs, in step S204, according to the cloud resource identification routing table, it is determined that the predetermined information corresponds to After the information of the cloud node and/or cloud resource instance is obtained, the determined information of the cloud node and/or cloud resource instance is recorded in the flow affinity forwarding table.
  • step S204 when the subsequent application data message is received, that is, the received application data message is not the first application data message in the application data stream to which it belongs, step S204 can be skipped, and the The flow affinity forwarding table determines the information of the cloud node and/or cloud resource instance corresponding to the application data flow, and further routes and forwards the application data according to the determined information of the cloud node and/or cloud resource instance message.
  • the network adds the function of determining cloud nodes and/or cloud resource instances based on the cloud resource identification routing table, also known as the virtual routing function based on cloud resource identification. Therefore, it can be used in the network It is logically layered and divided into a cloud resource identification routing sublayer and an address routing sublayer.
  • determining the information of the cloud node and/or cloud resource instance corresponding to the predetermined information may include: at the cloud resource identifier routing sublayer, determining the cloud resource identifier routing table according to the Information about the cloud node and/or cloud resource instance corresponding to the predetermined information.
  • routing and forwarding the application data packet according to the determined information of the cloud node and/or cloud resource instance may include: at the address routing sublayer, according to the determined information of the cloud node and/or cloud resource instance information routing and forwarding the application data packet.
  • the execution subject of the above steps S202-S206 may be a network routing and forwarding node (including a network entry node and/or a network exit node), etc., but is not limited thereto.
  • Fig. 3 is a flowchart of a routing method applied to a network entry node according to an embodiment of the present invention. As shown in Fig. 3, when the method is applied to a network entry node, the process includes the following steps:
  • Step S302 the network entry node acquires the predetermined information carried in the received application data message.
  • the entry node may need to execute the packet header of the network layer or the cloud resource identification sublayer Parsing, or performing in-depth packet inspection at the application layer, so as to obtain predetermined information from application data packets.
  • the predetermined information carried by the application data packet received by the network entry node may include one of the following:
  • the network The entry node parses the message header to obtain the predetermined information
  • the network entry node When the terminal sending the application data message encapsulates the predetermined information in the header of the transport layer or application layer under the network layer of the application data message, the network entry node The data message is deeply inspected to obtain the predetermined information, and the predetermined information is encapsulated in the network layer header of the application data message or the cloud resource identification sublayer header above the network layer.
  • the network entry node encapsulates the predetermined information in the network layer message header of the application data message or the cloud resource identification sublayer message header above the network layer, where the message header can be an extension of the existing protocol IPv6
  • the extended definition of the message header can also be the newly defined cloud resource and service identification sublayer above the IP layer, or the extended definition of the existing Overlay tunnel protocol message header, such as VxLAN-GPE (Virtual Local Area Network-General Packet Encapsulation), GENEVE, etc.
  • Step S304 the network entry node determines the information of the cloud node and/or cloud resource instance corresponding to the predetermined information according to the cloud resource identification routing table.
  • Step S306 according to the determined information of the cloud node and/or cloud resource instance, the network entry node determines the network edge node corresponding to the cloud node and/or cloud resource instance as a network exit node, and the application The data packet is routed and forwarded to the network egress node, and the network egress node forwards the application data packet to the cloud node and/or cloud resource instance.
  • Fig. 4 is a flowchart of a routing method applied to a network egress node according to an embodiment of the present invention. As shown in Fig. 4, when the method is applied to a network egress node, the process includes the following steps:
  • Step S402 the network egress node acquires the predetermined information carried in the received application data message.
  • the predetermined information has either been encapsulated by the terminal at the network layer or the cloud resource identification sublayer above the network layer, or the network entry node has encapsulated the predetermined information parsed by itself through deep message detection at the network layer or the network layer
  • the cloud resource identification sublayer above the cloud resource identification layer so the egress node only needs to perform packet header analysis at the network layer or cloud resource identification sublayer.
  • obtaining the predetermined information carried in the received application data packet by the network egress node may include:
  • the network egress node parses the network layer header of the application data message or the cloud resource identification sublayer header above the network layer to obtain the predetermined information.
  • Step S404 the network egress node determines the information of the cloud resource instance corresponding to the predetermined information according to the cloud resource identifier routing table.
  • Step S406 the network egress node forwards the application data packet to the cloud resource instance according to the determined information of the cloud resource instance.
  • the application data message received by the network carries predetermined information including a cloud resource identifier, and the cloud resource identifier can identify the cloud resource that processes the application data, and the network can route according to the cloud resource identifier Table, determining the information of the cloud node and/or cloud resource instance corresponding to the predetermined information, so as to realize the routing of the application data message according to the determined information of the cloud node and/or cloud resource instance corresponding to the predetermined information and retweets.
  • the sender of the application data message no longer needs to specify the target cloud node or cloud resource instance, but only needs to carry the cloud resource identifier of the required cloud resource, and the network calculates and determines the cloud node and cloud resource that meet the application requirements. /or cloud resource instances, and further route and forward the corresponding application data packets.
  • this solution creates a new cloud resource control scheduling mode, and the cloud resources are completed by the network.
  • the control scheduling and data flow routing and forwarding solve the problem that the application side has insufficient grasp of cloud resource status and network conditions, so it cannot schedule the most suitable cloud resources, resulting in low resource utilization. It also simplifies the development and operation process of the application side
  • the work on cloud resource scheduling and configuration solves the complex problems of application development and operation and maintenance.
  • FIG. 5 is a flowchart of a cloud resource registration method according to an embodiment of the present invention. As shown in FIG. 5 , the process includes the following step:
  • Step S502 receiving the cloud resource information reported by the cloud resource provider, wherein the cloud resource information includes: the cloud resource identifier of the provided cloud resource, and the cloud node and/or cloud resource instance used to provide the cloud resource Information;
  • Step S504 generating or updating a cloud resource identification routing table according to the cloud resource information, wherein the cloud resource identification routing table takes the cloud resource identification as an index and records the cloud resources identified by the cloud resource identification Information about cloud nodes and/or cloud resource instances.
  • the network side should also accept the deletion of cloud nodes and/or cloud resource instances, so the process also includes the following steps:
  • the cloud resource deletion request at any time includes: the cloud resource identifier of the cloud resource to be deleted, and the cloud node and/or cloud resource used to provide the cloud resource to be deleted instance information;
  • the cloud resource identification routing table can be maintained in the network centralized control unit or the network routing and forwarding node, so the network edge node can report the cloud resource identification routing table to the network centralized control unit; and /or flood the cloud resource identification routing table between network routing and forwarding nodes.
  • the network can accept the registration of cloud resources by the cloud resource provider, and maintain the cloud resource identification routing table accordingly, so that after the application data packet received by the network carries predetermined information including cloud resource identification, it can
  • the resource identification routing table determines the information of the cloud node and/or cloud resource instance corresponding to the predetermined information, so as to implement the application datagram according to the determined information of the cloud node and/or cloud resource instance corresponding to the predetermined information file routing and forwarding.
  • This solution provides the basic support for the new cloud resource management, control and scheduling mode, making it possible to complete the management, control and scheduling of cloud resources by the network, and solves the problem that the application side cannot fully grasp the status of cloud resources and network conditions and cannot schedule the most suitable cloud resources.
  • the problem of low utilization rate also simplifies the work of cloud resource scheduling and configuration in the development and operation process of the application side, and solves the problem of complex application development and operation and maintenance.
  • a routing device is also provided, which is used to implement the above embodiments and preferred implementation modes, and what has been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • FIG. 6 is a structural block diagram of a routing device according to an embodiment of the present invention. As shown in FIG. 6, the device includes:
  • the first determination module 62 is configured to acquire predetermined information carried in the received application data message, where the predetermined information includes: a cloud resource identifier of a cloud resource used to process the application data in the application data message;
  • the second determining module 64 is configured to determine the information of the cloud node and/or cloud resource instance corresponding to the predetermined information according to the cloud resource identifier routing table, wherein the cloud resource identifier routing table takes the cloud resource identifier as an index, Recording the information of the cloud node and/or cloud resource instance used to provide the cloud resource identified by the cloud resource identifier;
  • the routing and forwarding module 66 is configured to route and forward the application data packet according to the determined information of the cloud node and/or cloud resource instance.
  • the routing device may be set at a network routing and forwarding node.
  • the above-mentioned modules can be realized by software or hardware. For the latter, it can be realized by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.
  • a cloud resource registration device is also provided, which is used to implement the above embodiments and preferred implementation modes, and those that have been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • Fig. 7 is a structural block diagram of a cloud resource registration device according to an embodiment of the present invention. As shown in Fig. 7, the device includes:
  • the receiving module 72 is configured to receive cloud resource information reported by the cloud resource provider, wherein the cloud resource information includes: the cloud resource identifier of the cloud resource provided, and the cloud node and/or Information about cloud resource instances;
  • the routing table maintenance module 74 is configured to generate or update a cloud resource identification routing table according to the cloud resource information, wherein the cloud resource identification routing table takes the cloud resource identification as an index, and records are used to provide the cloud resource identification Information about cloud nodes and/or cloud resource instances of the identified cloud resource.
  • the cloud resource registration device can be set at network edge nodes, which sometimes also serve as network routing and forwarding nodes.
  • the above-mentioned modules can be realized by software or hardware. For the latter, it can be realized by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.
  • Embodiments of the present invention also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is set to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • An embodiment of the present invention also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • the solution of the following exemplary embodiments introduces resource and service identifiers independent of home and location at the traditional network routing and forwarding layer, and introduces a virtual routing mechanism for resource and service identifiers decoupled from traditional routing and forwarding.
  • this exemplary embodiment enhances the discovery and routing capabilities of the network for ubiquitous services and resources, it does not need to change or update the routing algorithms and protocols of the existing network, and is easy to expand and upgrade.
  • This exemplary embodiment proposes a routing technology method and process based on resource and service identifiers, and several key points of implementation of the solution are described below.
  • resource and service identifiers at the network routing and forwarding layer, and define the following attributes of cloud services and resources based on the identifiers:
  • Service categories including aggregate categories, or service categories established in accordance with industry conventional category classification standards, such as video processing, AI algorithm, etc.;
  • Service name a general service identifier with global semantics, such as video rendering algorithm, Fourier transform algorithm, etc.
  • resource and service identifiers do not have resource and service attribution semantics, nor do they have resource and service node location semantics. Compared with traditional routing and forwarding addresses, this abstract semantics of resource and service identification is more suitable for the perception and scheduling of ubiquitous services and resources in the future.
  • This identifier is introduced at the network routing and forwarding layer, and the control plane maintains a service and resource status routing table indexed by this identifier, that is, the cloud side notifies or registers the above-mentioned resource and service status provided by the network edge node, and the network creates resources accordingly and service routing table.
  • the device control plane generates a corresponding forwarding table based on the above resource and service routing table, and the existing routing and forwarding mechanism completes the forwarding of business data.
  • Fig. 8 is a schematic diagram of a routing mechanism and architecture based on resource and service identifiers according to an exemplary embodiment of the present invention. As shown in Fig.
  • the service identifier routing sublayer (corresponding to the aforementioned cloud resource identifier routing sublayer) only executes the And service awareness and routing, that is, according to the resource and service routing state table, find the cloud service node that meets the application request and its corresponding network edge node, and the address routing layer (corresponding to the aforementioned address routing sublayer) performs actual path arrangement based on this. Therefore, a virtual routing sublayer based on service identification is introduced to perform efficient addressing routing of ubiquitous services and resources between clouds, while maintaining a decoupled relationship with the traditional address-based routing and forwarding layer. While adding new routing functions, It does not fundamentally change the current network routing protocols, algorithms, and processes, maximizing the protection of existing network investment and smooth evolution and upgrading.
  • the resource and service identification sublayer above the network layer encapsulates resource and service identification.
  • Extend SRv6 resource and service function programming that is, encapsulate resource and service identifiers in the Function part of the Locator+Function structure.
  • Resource and service identifiers such as NSH, GENEVE, and GRE, are encapsulated in the Overlay extension header.
  • Resource and service identifiers have global semantics, but in the inter-cloud network nodes, only the network entry and exit nodes need to maintain the semantic state of the identifier and perform encapsulation and decapsulation operations, and the intermediate nodes of the network neither need to maintain the status of the identifier, nor need to Identify the semantics of the identity.
  • the network control plane maintains a routing status table with resource and service identifiers as unique indexes, including but not limited to the following characteristic elements:
  • Instance information corresponding to service and resource identification, virtual machine address and status, and cloud node information to which it belongs;
  • the above identification routing state table can be maintained in the network centralized control unit, or can be maintained in the network routing and forwarding nodes through a distributed protocol, or can be hierarchically maintained in different nodes under the aforementioned two mixed modes according to actual deployment needs.
  • the forwarding plane can choose two modes:
  • the terminal encapsulates the resource and service identifier, and the network entry and exit nodes decapsulate and recognize the semantics of the identifier, and execute the corresponding routing and forwarding process.
  • the encapsulation method can be selected from article 4 in the exemplary embodiment (the encapsulation scheme of the resource and service identifier) ) in IPv6 and SRv6 extension headers.
  • the network entry node performs encapsulation of resources and service identifiers, and the network exit node decapsulates resource and service identifiers, and performs corresponding routing and forwarding processes respectively.
  • resource and service identifiers are abstract global identifiers that correspond to multiple distributed dynamic instances, flow affinity needs to be ensured. Specifically, there are the following two scenarios and modes:
  • the network ingress node executes the routing policy to the destination identification instance, then the network ingress node maintains the flow affinity forwarding table item of the application, and guides the subsequent message forwarding of the same application flow. Specifically, a 5-tuple (source, destination address, Source, destination port number, transport layer protocol type) or resource and service identifier + 5 tuples to identify the application flow.
  • the network ingress node only executes the routing policy to the network egress node.
  • the flow affinity forwarding table maintained by the network ingress node is the same as that of A. The only difference is that the destination address is the network egress interface. In particular, the network egress interface also needs to maintain the same flow as A Affinity forwarding table.
  • Fig. 9 is a flow chart of basic routing and forwarding based on resource and service identifiers according to Exemplary Embodiment 1 of the present invention. As shown in Fig. 9, this exemplary embodiment introduces resource and service-based Therefore, in the traditional network routing and forwarding process, the resource and service identification routing process is superimposed, and its basic data forwarding process is as follows:
  • Step S901 the application data traffic reaches the network entry node
  • Step S902 the network entry node searches the resource and service identification routing table according to the application request, calculates and determines the resource and service nodes that meet the application requirements, that is, executes virtual resource and service identification routing;
  • Step S903 the network entry node performs resource and service identifier encapsulation
  • Step S904 the network entry node implements the address routing strategy according to the resource and service identification routing strategy, and forwards the application data traffic;
  • Step S905 the network intermediate node executes stateless common traffic routing and forwarding
  • Step S906 the network egress node decapsulates the resource and service identifier
  • Step S907 the network egress node executes the corresponding identification routing policy according to the resource and service identification, and forwards the application data traffic;
  • Step S908 the application data flow reaches the resource and service nodes, and the process ends.
  • FIG 10 is a schematic structural diagram of resource and service identifiers with a non-IP address structure according to Exemplary Embodiment 2 of the present invention.
  • the resource and service identifiers with a non-IP address structure will be as in the fourth Item (encapsulation scheme of resource and service identification) is encapsulated in the extended message header, and each optional extended header encapsulation scheme will not be expanded here.
  • the identifier adopts a fixed-length structural definition. For the convenience of device chip processing, you can refer to the existing address length, such as 32 bits for IPv4 and 128 bits for IPv6.
  • the aggregation category can improve the retrieval efficiency of the identification.
  • the resource and service identification is a unique identification of a specific resource or service. It has global semantics on the control plane and forwarding plane of the network layer. Optional and reserved attributes are reserved for extended definition purposes.
  • a resource and service identifier of an Anycast (Anycast) address structure is provided.
  • the anycast address directly uses the IP address attribute of the anycast address, and is directly encapsulated in the destination address field of the IP fixed packet header, that is, the anycast address is given the dual semantics of the traditional routing address and the resource and service identifier , the network control plane also needs to implement routing of virtual resources and service identifiers based on such anycast addresses.
  • anycast addressing resource and service identifiers There are two options for anycast addressing resource and service identifiers:
  • An anycast address corresponds to a unique resource and service identifier, provided that the mapping definition relationship requires global standardization, that is, network routing and forwarding edge devices can recognize the resource and service identifier semantics of the address without any meaning;
  • Fig. 11 is a schematic diagram of the resource and service identifier structure of anycast (Anycast) address structure according to the third exemplary embodiment of the present invention.
  • Service-related attribute extensions such as service parameters, etc.
  • each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供了一种路由和云资源注册方法及装置、存储介质和电子装置，所述路由方法包括：获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识；根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。通过本发明，在不改变当前路由协议和算法的基础上，实现了网络对于云间泛在云资源的高效寻址路由，从而提高了云资源的利用率。

Description

路由和云资源注册方法及装置、存储介质和电子装置 技术领域
本发明实施例涉及通信领域，具体而言，涉及一种路由和云资源注册方法及装置、存储介质和电子装置。
背景技术
当前网络架构下的路由和转发技术本质上是一种面向特定物理地址的寻址技术，解决的是业务数据在确定的源和目的节点之间的网络传输。
然而，随着云资源的规模化部署，尤其是5G背景下的云资源逐渐下沉，应用和业务随云资源逐渐呈现一种泛在部署的趋势，在这种新型业务和流量模型下，网络从提供云间高效敏捷互连，到对云资源及其业务的泛在互连，传统的基于确定物理地址的网络寻址路由机制将面临以下挑战：
云业务及应用在云内和云间的部署高度动态化；
同一种资源和服务分布式多实例化，物理地址无法确切标识服务；
寻址路由无法敏捷感知并编排云资源及业务，传统物理地址路由效率无法适应高度动态化的泛在服务和资源。
由上述分析可知，传统的网络基于特定物理地址执行路由和转发的机制已经无法适应于新型业务和流量模型。随着应用和业务随云资源部署模式的变化，采用传统的网络路由和转发的机制会导致宏观资源利用率低下，应用开发和运营维护越来越复杂、成本高昂，对此，亟待提供相应的解决方案。
发明内容
本发明实施例提供了一种路由和云资源注册方法及装置、存储介质和电子装置，以至少解决相关技术中传统的网络基于特定物理地址执行路由和转发的机制无法适应于新型业务和流量模型，导致宏观资源利用率低下、应用开发和运营维护复杂的问题。
根据本发明的一个实施例，提供了一种路由方法，包括：获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识；根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
根据本发明的一个实施例，提供了一种云资源注册方法，包括：接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
根据本发明的另一个实施例，提供了一种路由装置，包括：第一确定模块，设置为获取 接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识；第二确定模块，设置为根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；路由转发模块，设置为根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
根据本发明的另一个实施例，提供了一种云资源注册装置，包括：接收模块，设置为接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；路由表维护模块，设置为根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
根据本发明的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本发明上述实施例，网络接收到的应用数据报文携带有包括云资源标识的预定信息，该云资源标识能够标识处理应用数据的云资源，网络可以根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，从而根据确定的所述预定信息所对应的云节点和/或云资源实例的信息实现该应用数据报文的路由和转发。该方案中，应用数据报文的发送端不再需要指定目标的云节点或云资源实例，而仅仅需要携带所需的云资源的云资源标识，由网络计算并确定满足应用需求的云节点和/或云资源实例，并进一步进行相应应用数据报文的路由和转发，相对于传统的应用对云资源的管控和调度模式，该方案开创了新的云资源管控调度模式，由网络完成云资源的管控调度以及数据流的路由转发，解决了应用侧对云资源状态和网络情况把握不足从而无法调度最适合云资源，导致资源利用率低下的问题，同时也简化了应用侧的开发和运营过程中对于云资源调度配置的工作，解决了应用开发和运营维护复杂的问题。
附图说明
图1是本发明实施例的一种路由方法的网络路由及转发节点的硬件结构框图；
图2是根据本发明实施例的路由方法的流程图；
图3是根据本发明实施例的应用于网络入口节点的路由方法的流程图；
图4是根据本发明实施例的应用于网络出口节点的路由方法的流程图；
图5是根据本发明实施例的云资源注册方法的流程图；
图6是根据本发明实施例的路由装置的结构框图；
图7是根据本发明实施例的云资源注册装置的结构框图；
图8是根据本发明示例性实施例的基于资源和服务标识的路由机制和架构示意图；
图9是根据本发明示例性实施方式1的基于资源和服务标识的基本路由转发流程图；
图10是根据本发明示例性实施方式2的非IP地址结构的资源和服务标识的结构示意图；
图11是根据本发明示例性实施方式3的任播(Anycast)地址结构的资源和服务标识结构示意图。
具体实施方式
随着云资源的规模化部署，尤其是5G背景下的云资源逐渐下沉，应用和业务随云资源逐渐呈现一种泛在部署的趋势，传统的网络基于特定物理地址执行路由和转发的方案已经无法适应于新型业务和流量模型，与此同时，未来产业互联网和各类云化应用体验和高交互性要求下，传统网络基于尽力模式的网络和业务分离模式也需要改进，需要将应用资源和网络资源综合选优来满足最终的业务体验要求。
对云资源和服务的感知、调度和编排目前主要集中在应用层提供解决方案，即特定云资源和应用的管控调度由应用提供方执行封闭式、烟囱式的管理。这一模式的优势是实现了应用与网络传输和路由的解耦，给予了应用充分的灵活性，劣势是在泛在计算和存储的产业趋势下，这种孤岛式的资源和业务管控模式，导致宏观资源利用率低下，应用开发和运营维护越来越复杂、成本高昂。
为了解决上述问题，本发明实施例提供了一种基于云资源标识的路由方案以及云资源注册方案。该方案中，应用数据报文的发送端不再需要指定目标的云节点或云资源实例，而仅仅需要携带所需的云资源的云资源标识，由网络计算并确定满足应用需求的云节点和/或云资源实例，并进一步进行相应应用数据报文的路由和转发，相对于传统的应用对云资源的管控和调度模式，该方案开创了新的云资源管控调度模式，由网络完成云资源的管控调度以及数据流的路由转发，解决了应用侧对云资源状态和网络情况把握不足从而无法调度最适合云资源，导致资源利用率低下的问题，同时也简化了应用侧的开发和运营过程中对于云资源调度配置的工作，解决了应用开发和运营维护复杂的问题。
下文中将参考附图并结合实施例来详细说明本发明的实施例。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中所提供的路由方法的方法实施例可以在网络路由及转发节点(包括网络入口节点和/或网络出口节点)或者类似的运算装置中执行；本申请实施例中所提供的云资源注册方法的方法实施例可以在网络边缘节点或者类似的运算装置中执行。网络路由及转发节点和网络边缘节点，都是网络中的节点，硬件结构都是类似的，以运行在网络路由及转发节点上为例，图1是本发明实施例的一种路由方法的网络路由及转发节点的硬件结构框图。如图1所示，网络路由及转发节点可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述网络路由及转发节点还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述网络路由及转发节点的结构造成限定。例如，网络路由及转发节点还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本发明实施例中的路由(或云资源注册)方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104 可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至网络路由及转发节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括网络路由及转发节点的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于网络路由及转发节点(包括网络入口节点和/或网络出口节点)的路由方法，图2是根据本发明实施例的路由方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识。
在本发明实施例中，云资源涵盖所有通过网络提供的资源，这些资源包括但不限于计算、存储、应用软件及服务等等，最典型的就是云资源和服务。
在该方案中，具体需要使用哪类云资源来处理当前的应用数据是通过将对应类别的云资源的云资源标识携带在应用数据报文中来指示的，所述云资源标识用于全局唯一标识一类云资源，因而能够被网络中的任意网络路由及转发节点所识别，也就是说，对于某个云资源标识对应着具体哪类云资源，即，有哪些特征和约束条件的一类云资源，对于全网是具有相同的理解的，这部分内容例如可以通过标准予以规定，或者是通过行业统一的规范来规定。
所述云资源的类别一般会基于云资源属性进行划分，所述云资源属性包括以下至少之一：所述云资源的服务类别、所述云资源的服务标识、所述云资源包括的计算资源、所述云资源包括的存储资源、所述云资源的接口参数。
另外，所述云资源标识与所述云资源的归属和/或位置无关，也就是说，对于应用侧而言，虽然其在应用数据报文中携带有云资源标识，但是，其并不分配和调度所使用的云资源，即并不会指定某一个具体的云节点或者云资源实例上的云资源，而仅仅是通过一个归属和/或位置无关的云资源标识来指示这些应用数据具体需要通过哪种云资源来处理。这无疑简化了应用侧的开发和运营过程中对于云资源调度配置的工作，解决了应用开发和运营维护复杂的问题。
当然，除了指定某类云资源，应用可能会进一步对资源提出补充要求，例如，所述预定信息还包括以下至少之一：云资源的聚合类别、支撑资源属性、服务参数。通过在预定信息中包括云资源的聚合类别和支撑资源属性，能够方便网络侧更快地筛选到所需的云资源，提高云资源标识的检索效率，此外，能够更加精确地提出对所需资源的支撑属性的要求。除此之外，服务参数也作为一个可选的信息包括在预定信息中发送给网络。
应用数据报文一般是由终端等包含应用客户端的设备发送的，设备可以通过各种可能的方式在所述应用数据报文中携带所述预定信息，例如所述应用数据报文可以通过以下方式至少之一携带所述预定信息：
在所述应用数据报文的网络层之上的云资源标识子层报文头中封装所述预定信息；
在所述应用数据报文的互联网协议第6版(Internet Protocol version 6，IPv6)扩展报文头中封装所述预定信息；
通过扩展所述应用数据报文的基于IPv6的目的选项头(Destination Option Header，DOH)报文头封装所述预定信息；
通过扩展所述应用数据报文的基于IPv6的源路由技术(Segment Routing version 6，SRv6)功能编程封装所述预定信息；
在所述应用数据报文的隧道协议(Overlay)扩展报文头中封装所述预定信息；
在所述应用数据报文的多协议标签交换(Multi-Protocol Label Switching，MPLS)扩展头中封装所述预定信息；
在所述应用数据报文的报文头的目的地址字段中携带对应于所述云资源标识的任播地址，其中，所述任播地址的前缀被定义为所述云资源标识；或者，所述任播地址对应唯一云资源标识，且所述任播地址与所述云资源标识之间的映射关系具有全局一致性。
步骤S204，根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
在本发明实施例中，所述云节点的信息可以包括以下至少之一：所述云节点的网关地址、所述云节点的云资源状态数据。也就是说，云资源标识路由表中，可以记录用于提供云资源标识所指示的云资源的云节点的网关地址，还可以记录该云节点上的云资源的状态，例如，云资源是忙碌还是空闲，云资源上的应用流量等等，所述云节点的云资源状态数据实质体现了当前云节点上云资源的使用状态，网络可以根据该信息选择较为空闲的云节点作为所述预定信息所对应的云节点。
在本发明实施例中，所述云资源实例的信息包括以下至少之一：所述云资源实例的地址、所述云资源实例的状态、所述云资源实例归属的云节点的信息。由于云资源实例可以运行在虚机、物理主机、容器等等，所以此处所说的云资源实例的地址，可能是云资源实例的虚机地址、物理主机地址、容器地址等等，通过所述云资源实例归属的云节点的地址和所述云资源实例的地址，就可以明确应用数据报文最终要被发送到哪个云节点的哪个云资源实例，从而进行恰当的路由和转发。另外，所述云资源实例的信息还可以包括所述云资源实例的状态，也就是说，云资源标识路由表中，可以记录云资源实例的状态，例如，云资源实例是忙碌还是空闲，云资源实例上的应用流量等等，所述云资源实例的状态实质体现了当前云资源实例上云资源的使用状态，网络可以根据该信息选择较为空闲的云资源实例作为所述预定信息所对应的云资源实例。
在本发明实施例中，所述云资源标识路由表可以维护在网络路由和转发节点，其中，所述网络路由和转发节点包括：所述应用数据报文的网络入口节点和/或网络出口节点。
在本发明实施例中，所述云资源标识路由表也可以维护在网络集中控制单元，并定期或基于请求向网络路由和转发节点同步，其中，所述网络路由和转发节点包括：所述应用数据报文的网络入口节点和/或网络出口节点。
在本发明实施例的方案中，应用数据报文的发送端不再需要指定目标的云节点或云资源实例，而仅仅需要携带所需的云资源的云资源标识，由网络计算并确定满足应用需求的云节点和/或云资源实例。由于网络维护了云资源标识路由表，所以掌握了网络中注册的所有能够 提供对应类型云资源的云节点，甚至掌握云节点上具有几个对应的云资源实例，所以，由网络来为当前的应用数据报文选择云节点和/或云资源实例，有更加灵活宽泛的选择自由度，具有更大的调度范围。作为一个更加推荐的实施方式，网络本身能够更加精确的掌握当前的网络拓扑和到各个云节点的网络状态，在确定有多个云节点和/或云资源实例能够满足所述预定信息的要求的情况下，可以根据到所述多个云节点和/或云资源实例的网络状态，选择一个云节点和/或云资源实例(一般是网络状态最优的，按照应用的需求也可以设置其他的规则)作为所述预定信息所对应的云节点和/或云资源实例。当然，在实际应用中，基于云资源标识路由表的云节点和/或云资源实例确定方案与基于网络状态的云节点和/或云资源实例确定方案可以联合执行(即二者同时作为约束条件)，也可以递进执行(即先执行其中一种确定方案，再在确定的结果的范围内执行另一种确定方案)，对此本发明没有限定。因此，根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息可以包括：根据云资源标识路由表和到所述多个云节点和/或云资源实例的网络状态，确定所述预定信息所对应的云节点和/或云资源实例的信息。
需要说明的是，基于本发明实施例中所述的方法，提供了一种新的云资源管控调度模式，由网络完成云资源的管控调度，解决了应用侧对云资源状态和网络情况把握不足从而无法调度最适合云资源，导致资源利用率低下的问题。基于这样的云资源管控调度模式，网络侧可以更加自主、合理的调度云资源，针对于网络侧根据云资源标识路由表，采用什么样的策略来确定所述预定信息所对应的云节点和/或云资源实例的信息，则可以由网络运营方根据实际需求来进行设定，当然也可以提供接口由应用提供方来进行设定，应当理解，在网络掌握了网络中注册的所有能够提供对应类型云资源的云节点，甚至掌握云节点上具有几个对应的云资源实例的情况下，这样的云节点和/或云资源实例的确定策略具有更加广泛的应用范围，因而更容易找到能够满足应用需求且网络状态更加良好的云节点和/或云资源实例。本发明实施例的云资源管控调度模式能够支持各种类型的云节点和/或云资源实例的确定策略，且对此没有具体的限定。
步骤S206，根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
需要说明的是，为了应用的连续处理，一般希望将相同应用数据流的应用数据报文都送往相同的云节点和/或云资源实例进行处理。为了实现这个目标，可以在接收的所述应用数据报文是所属的应用数据流中的首个应用数据报文的情况下，在步骤S204根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息之后，将确定的所述云节点和/或云资源实例的信息记录到流亲和转发表。这样，在接收后续的应用数据报文，也就是接收的所述应用数据报文是所属的应用数据流中的非首个应用数据报文的情况下，可以跳过步骤S204，而是直接根据所述流亲和转发表确定所述应用数据流对应的云节点和/或云资源实例的信息，并进一步根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
在原有的转发和路由功能的基础上，网络增加了基于云资源标识路由表来确定云节点和/或云资源实例的功能，也称基于云资源标识的虚拟路由功能，所以，可以在网络中进行逻辑分层，分为云资源标识路由子层和地址路由子层。
相应地，根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息可以包括：在云资源标识路由子层，根据所述云资源标识路由表确定所述预定信息所对 应的所述云节点和/或云资源实例的信息。
相应地，根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文可以包括：在地址路由子层，根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
需要说明的是，上述步骤S202-S206的执行主体可以为网络路由及转发节点(包括网络入口节点和/或网络出口节点)等，但不限于此。
以下分别描述将该方法应用在网络入口节点和网络出口节点时的处理。
图3是根据本发明实施例的应用于网络入口节点的路由方法的流程图，如图3所示，当将该方法应用于网络入口节点时，该流程包括如下步骤：
步骤S302，网络入口节点获取接收的所述应用数据报文携带的所述预定信息。
鉴于所述预定信息可能被终端封装在应用层，传输层和网络层，或者是网络层之上的云资源标识子层，因此入口节点可能需要执行网络层或云资源标识子层的报文头解析，或者做应用层的深度报文检测，从而从应用数据报文中获取预定信息。
网络入口节点获取接收的所述应用数据报文携带的所述预定信息可以包括以下之一：
在发送所述应用数据报文的终端将所述预定信息封装在所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头的情况下，所述网络入口节点解析所述报文头以获取所述预定信息；
在发送所述应用数据报文的终端将所述预定信息封装在所述应用数据报文的网络层之下的传输层或应用层报文头的情况下，所述网络入口节点对所述应用数据报文进行深度检测以获取所述预定信息，并将所述预定信息封装在所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头。
网络入口节点将所述预定信息封装在所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头，这里的报文头可以是如现有协议IPv6扩展报文头的扩展定义，也可以是新定义IP层之上的云资源和服务标识子层，还可以是现有Overlay隧道协议报文头的扩展定义，如VxLAN-GPE(Virtual Local Area Network-General Packet Encapsulation)，GENEVE等
步骤S304，所述网络入口节点根据所述云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息。
步骤S306，根据确定的所述云节点和/或云资源实例的信息，所述网络入口节点将所述云节点和/或云资源实例对应的网络边缘节点确定为网络出口节点，将所述应用数据报文路由并转发到所述网络出口节点，由所述网络出口节点将所述应用数据报文转发到所述云节点和/或云资源实例。
图4是根据本发明实施例的应用于网络出口节点的路由方法的流程图，如图4所示，当将该方法应用于网络出口节点时，该流程包括如下步骤：
步骤S402，网络出口节点获取接收的所述应用数据报文携带的所述预定信息。
鉴于所述预定信息或者已经被终端封装在网络层或者是网络层之上的云资源标识子层，或者网络入口节点已经将自己通过深度报文检测解析出的预定信息封装在网络层或者是网络层之上的云资源标识子层，因此出口节点只需要执行网络层或云资源标识子层的报文头解析。
因此，网络出口节点获取接收的所述应用数据报文携带的所述预定信息可以包括：
所述网络出口节点解析所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头以获取所述预定信息。
步骤S404，所述网络出口节点根据所述云资源标识路由表，确定所述预定信息所对应的云资源实例的信息。
步骤S406，所述网络出口节点根据确定的所述云资源实例的信息将所述应用数据报文转发到所述云资源实例。
综上，通过本发明实施例的路由方案，网络接收到的应用数据报文携带有包括云资源标识的预定信息，该云资源标识能够标识处理应用数据的云资源，网络可以根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，从而根据确定的所述预定信息所对应的云节点和/或云资源实例的信息实现该应用数据报文的路由和转发。该方案中，应用数据报文的发送端不再需要指定目标的云节点或云资源实例，而仅仅需要携带所需的云资源的云资源标识，由网络计算并确定满足应用需求的云节点和/或云资源实例，并进一步进行相应应用数据报文的路由和转发，相对于传统的应用对云资源的管控和调度模式，该方案开创了新的云资源管控调度模式，由网络完成云资源的管控调度以及数据流的路由转发，解决了应用侧对云资源状态和网络情况把握不足从而无法调度最适合云资源，导致资源利用率低下的问题，同时也简化了应用侧的开发和运营过程中对于云资源调度配置的工作，解决了应用开发和运营维护复杂的问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
网络需要实时维护云资源标识路由表，从而能够根据应用数据报文携带的包括云资源标识的预定信息，确定所述预定信息所对应的云节点和/或云资源实例的信息。云资源标识路由表以云资源标识为索引，记录用于提供该云资源标识所标识的云资源的云节点和/或云资源实例的信息。鉴于云资源的提供方很多，而其能够提供云资源的云节点以及所能提供的云资源的类型也可能随时变化，这就要求网络能够接受云资源提供方对云资源的注册，并相应维护云资源标识路由表。为此，在本实施例中提供了一种运行于网络边缘节点的云资源注册方法，图5是根据本发明实施例的云资源注册方法的流程图，如图5所示，该流程包括如下步骤：
步骤S502，接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；
步骤S504，根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
当然，网络侧也应接受对云节点和/或云资源实例的删除，那么，该流程还包括如下步骤：
接收云资源提供端上报的云资源删除请求，其中，随时云资源删除请求包括：要删除的云资源的云资源标识，以及用于提供要删除的所述云资源的云节点和/或云资源实例的信息；
根据所述云资源删除请求更新所述云资源标识路由表。
鉴于在本发明实施例中，所述云资源标识路由表可以维护在网络集中控制单元或网络路由和转发节点，所以网络边缘节点可以将所述云资源标识路由表上报给网络集中控制单元；和/或将所述云资源标识路由表在网络路由和转发节点之间洪泛。
通过该方案，网络能够接受云资源提供方对云资源的注册，并相应维护云资源标识路由表，从而使得网络接收到的应用数据报文携带有包括云资源标识的预定信息后，可以根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，从而根据确定的所述预定信息所对应的云节点和/或云资源实例的信息实现该应用数据报文的路由和转发。该方案为新的云资源管控调度模式提供了基础支撑，使得由网络完成云资源的管控调度成为可能，解决了应用侧对云资源状态和网络情况把握不足从而无法调度最适合云资源，导致资源利用率低下的问题，同时也简化了应用侧的开发和运营过程中对于云资源调度配置的工作，解决了应用开发和运营维护复杂的问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种路由装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的路由装置的结构框图，如图6所示，该装置包括：
第一确定模块62，设置为获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识；
第二确定模块64，设置为根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；
路由转发模块66，设置为根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
所述路由装置可以设置于网络路由和转发节点。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
在本实施例中还提供了一种云资源注册装置，该装置用于实现上述实施例及优选实施方 式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本发明实施例的云资源注册装置的结构框图，如图7所示，该装置包括：
接收模块72，设置为接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；
路由表维护模块74，设置为根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
所述云资源注册装置可以设置于网络边缘节点，它们有时也作为网络路由和转发节点。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本发明的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
以下以云资源为资源和服务，云资源标识为资源和服务标识为例，对本发明实施例的上述路由方法和云资源注册方法进行详细的说明。需要说明的是，以下示例性实施例仅仅为了便于方案的理解，不应当被理解为是对本发明的限定。
以下示例性实施例的方案在传统网络路由和转发层引入归属和位置无关的资源和服务标识，并引入了与传统路由和转发解耦的资源和服务标识虚拟路由机制。另外，值得注意的是，本示例性实施例的方案在增强网络对泛在服务和资源的发现和路由能力的同时，对现网路由算法和协议无变更和更新需求，易于拓展和升级。
本示例性实施例提出一种基于资源和服务标识的路由技术方法和流程，以下对方案实施的几个关键点进行说明。
1、资源和服务标识的定义。
在网络路由和转发层引入资源和服务标识，基于该标识定义云服务和资源的如下属性：
(1)服务类别，含聚合大类，或按照产业常规类别划分标准确立的服务类别，如视频处理类，AI算法类等；
(2)服务名称，具有全局语义的通用服务标识，如视频渲染算法，傅里叶变换算法等；
(3)(可选)支撑服务需要的计算和存储资源，如GPU，CPU等；
(4)(可选)服务所需的接口参数。
因此，上述资源和服务标识不具备资源和服务归属语义，也不具备资源和服务节点位置语义。相比传统路由和转发地址，这种资源和服务标识的抽象语义，更加适应未来泛在服务和资源的感知和调度。
2、资源和服务标识路由机制
在网络路由和转发层引入该标识，控制面维护以该标识为索引的服务和资源状态路由表，即云侧向网络边缘节点通告或注册其提供的上述资源和服务状态，网络据此创建资源和服务路由表。
设备控制面基于上述资源和服务路由表，生成对应的转发表，由现有路由和转发机制完成业务数据的转发。
3、资源和服务标识与现有路由机制的关系
上述云侧资源和服务节点与路由和转发网络在网络部署中是解耦的，即对路由和转发网络而言，云侧资源和服务只是一种应用级路由终极节点，对当前的网络路由拓扑以及路由算法无影响。因此，资源和服务标识路由本质上是一种服务和网络双重服务级别协议(Service Level Agreement，SLA)解耦叠加优化的路由机制，资源和服务标识路由只需执行一级云节点虚拟路由，实际业务数据的转发和路由仍然由传统路由机制执行。图8是根据本发明示例性实施例的基于资源和服务标识的路由机制和架构示意图，如图8所示，服务标识路由子层(对应于前述云资源标识路由子层)仅执行云间资源和服务感知和路由，即根据资源和服务路由状态表，查找符合应用请求的云服务节点及其对应的网络边缘节点，地址路由层(对应于前述地址路由子层)据此进行实际路径编排。因此，引入一个基于服务标识的虚拟路由子层，执行云间泛在服务和资源的高效寻址路由，同时与传统基于地址的路由转发层保持解耦关系，在增加全新的路由功能的同时，并不从根本上改变当前的网络路由协议、算法和流程，最大化保护现网投资和平滑演进升级。
4、资源和服务标识的封装方案
在IPv6扩展报文头中封装资源和服务标识，如目的节点扩展报文头DOH，以及基于IPv6的源路由扩展报文头SRH中扩展封装资源和服务标识。
在网络层之上的资源和服务标识子层封装资源和服务标识。
扩展SRv6资源和服务功能编程，即在Locator+Function结构中的Function部分封装资源和服务标识。
Overlay扩展报文头中封装资源和服务标识，如NSH，GENEVE，GRE等。
在MPLS扩展头中封装资源和服务标识。
5、资源和服务标识的语义适用范围
资源和服务标识具有全局语义，但在云间网络节点中，仅需网络入口和出口节点维护该标识的语义状态并执行封装和解封装的操作，网络中间节点既无需维护该标识的状态，也无 需识别该标识的语义。
6、网络控制面的资源和服务标识
网络控制面维护以资源和服务标识为唯一索引的路由状态表，包括但不限于如下特征要素：
提供对应服务和资源标识的云节点信息，含节点网关地址，及其资源和服务状态数据；
对应服务和资源标识的实例信息，虚机地址及状态，归属的云节点信息；
上述标识路由状态表可以被维护在网络集中控制单元，也可以通过分布式协议维护在网络路由和转发节点，或者根据实际部署需要层次化维护在前述两种混合模式下的不同节点中。
7、网络转发面的资源和服务标识
转发面可选两种模式：
终端封装资源和服务标识，网络入口和出口节点解封装并识别其标识语义，并执行对应的路由和转发流程，封装方式可选示例性实施例中的第4条(资源和服务标识的封装方案)中的IPv6及SRv6扩展报文头。
网络入口节点执行资源和服务标识的封装，网络出口节点解封装资源和服务标识，并分别执行对应的路由和转发流程。
8、应用流亲和(Traffic Affinity)机制
由于资源和服务标识是一种抽象的全局标识，对应多个分布式动态实例，因此需要确保流亲和。具体的，有如下两种场景和模式：
网络入口节点执行到目的标识实例的路由策略，则网络入口节点维护应用的流亲和转发表项，指导同一应用流的后续报文转发，具体的，可以采用5元组(源、目的地址，源、目的端口号，传输层协议类型)或资源和服务标识+5元组标识应用流。
网络入口节点仅执行到网络出口节点的路由策略，则网络入口节点维护的流亲和转发表同A，唯一区别是目的地址为网络出接口，特别的，网络出接口也需要维护同A的流亲和转发表。
示例性实施方式1
图9是根据本发明示例性实施方式1的基于资源和服务标识的基本路由转发流程图，如图9所示，该示例性实施方式在传统网络路由和转发机制基础上，引入基于资源和服务标识的虚拟路由，因此，在传统网络路由和转发流程中，叠加了资源和服务标识路由流程，其基础数据转发流程如下：
步骤S901，应用数据流量到达网络入口节点；
步骤S902，网络入口节点根据应用请求，查找资源和服务标识路由表，计算并确定满足应用需求的资源和服务节点，即执行虚拟资源和服务标识路由；
步骤S903，网络入口节点执行资源和服务标识封装；
步骤S904，网络入口节点根据资源和服务标识路由策略，执行地址路由策略，并转发应用数据流量；
步骤S905，网络中间节点执行服务无状态的普通流量路由和转发；
步骤S906，网络出口节点解封装资源和服务标识；
步骤S907，网络出口节点根据资源和服务标识执行对应的标识路由策略，并转发应用数据流量；
步骤S908，应用数据流量到达资源和服务节点，流程结束。
示例性实施方式2
图10是根据本发明示例性实施方式2的非IP地址结构的资源和服务标识的结构示意图，如图10所示，非IP地址结构的资源和服务标识将如示例性实施例中的第4条(资源和服务标识的封装方案)所述封装在扩展报文头中，此处不再展开每种可选扩展头封装方案。标识采用定长结构化定义，为便于设备芯片处理，可参考既有地址长度，如IPv4的32位及IPv6的128位。聚合类别可提高标识的检索效率，资源和服务标识是一种特定资源或服务的唯一标识，在网络层的控制面和转发面具备全局语义，可选及预留属性留做扩展定义用途。
示例性实施方式3
本示例性实施方式中，提供了一种任播(Anycast)地址结构的资源和服务标识。
任播地址作为资源和服务标识，直接沿用任播地址的IP地址属性，直接封装在IP固定报文头的目的地址字段中，即赋予任播地址以传统路由地址和资源及服务标识的双重语义，网络控制面同样需要执行基于此类任播地址的虚拟资源和服务标识路由。有两种任播地址标示资源和服务标识的可选方案：
一个任播地址对应唯一一种资源和服务标识，前提是这种映射定义关系需要全局标准化，即网络路由和转发边缘设备能够无异义的识别该地址的资源和服务标识语义；
图11是根据本发明示例性实施方式3的任播(Anycast)地址结构的资源和服务标识结构示意图，如图11所示，任播地址前缀定义为资源和服务标识，其余部分用于资源和服务相关的属性扩展，如服务参数等。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (22)

  1. 一种路由方法，包括：
    获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：用于处理所述应用数据报文中的应用数据的云资源的云资源标识；
    根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；
    根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
  2. 根据权利要求1所述的方法，其中，所述云资源标识用于全局唯一标识一类云资源，且与所述云资源的归属和/或位置无关。
  3. 根据权利要求2所述的方法，其中，所述云资源的类别基于云资源属性进行划分，所述云资源属性包括以下至少之一：所述云资源的服务类别、所述云资源的服务标识、所述云资源包括的计算资源、所述云资源包括的存储资源、所述云资源的接口参数。
  4. 根据权利要求1所述的方法，其中，所述预定信息还包括以下至少之一：
    云资源的聚合类别、支撑资源属性、服务参数。
  5. 根据权利要求1所述的方法，其中，所述云节点的信息包括以下至少之一：
    所述云节点的网关地址、所述云节点的云资源状态数据。
  6. 根据权利要求1所述的方法，其中，所述云资源实例的信息包括以下至少之一：
    所述云资源实例的地址、所述云资源实例的状态、所述云资源实例归属的云节点的信息。
  7. 根据权利要求1所述的方法，其中，所述应用数据报文通过以下方式至少之一携带所述预定信息：
    在所述应用数据报文的网络层之上的云资源标识子层报文头中封装所述预定信息；
    在所述应用数据报文的互联网协议第6版IPv6扩展报文头中封装所述预定信息；
    通过扩展所述应用数据报文的基于IPv6的目的选项头DOH报文头封装所述预定信息；
    通过扩展所述应用数据报文的基于IPv6的源路由技术SRv6功能编程封装所述预定信息；
    在所述应用数据报文的隧道协议Overlay扩展报文头中封装所述预定信息；
    在所述应用数据报文的多协议标签交换MPLS扩展头中封装所述预定信息；
    在所述应用数据报文的报文头的目的地址字段中携带对应于所述云资源标识的任播地址，其中，所述任播地址的前缀被定义为所述云资源标识；或者，所述任播地址对应唯一云资源标识，且所述任播地址与所述云资源标识之间的映射关系具有全局一致性。
  8. 根据权利要求1所述的方法，其中，根据云资源标识路由表，确定所述预定信息所对 应的云节点和/或云资源实例的信息包括：
    在云资源标识路由子层，根据所述云资源标识路由表确定所述预定信息所对应的所述云节点和/或云资源实例的信息。
  9. 根据权利要求1所述的方法，其中，根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文包括：
    在地址路由子层，根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
  10. 根据权利要求1所述的方法，其中，
    获取接收的应用数据报文携带的预定信息包括：网络入口节点获取接收的所述应用数据报文携带的所述预定信息；
    根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息包括：所述网络入口节点根据所述云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息；
    根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文包括：根据确定的所述云节点和/或云资源实例的信息，所述网络入口节点将所述云节点和/或云资源实例对应的网络边缘节点确定为网络出口节点，将所述应用数据报文路由并转发到所述网络出口节点，由所述网络出口节点将所述应用数据报文转发到所述云节点和/或云资源实例。
  11. 根据权利要求10所述的方法，其中，网络入口节点获取接收的所述应用数据报文携带的所述预定信息包括以下之一：
    在发送所述应用数据报文的终端将所述预定信息封装在所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头的情况下，所述网络入口节点解析所述报文头以获取所述预定信息；
    在发送所述应用数据报文的终端将所述预定信息封装在所述应用数据报文的网络层之下的传输层或应用层报文头的情况下，所述网络入口节点对所述应用数据报文进行深度检测以获取所述预定信息，并将所述预定信息封装在所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头。
  12. 根据权利要求1所述的方法，其中，
    获取接收的应用数据报文携带的预定信息包括：网络出口节点获取接收的所述应用数据报文携带的所述预定信息；
    根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息包括：所述网络出口节点根据所述云资源标识路由表，确定所述预定信息所对应的云资源实例的信息；
    根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文包括：所述网络出口节点根据确定的所述云资源实例的信息将所述应用数据报文转发到所述云资源实例。
  13. 根据权利要求12所述的方法，其中，网络出口节点获取接收的所述应用数据报文携带的所述预定信息包括：
    所述网络出口节点解析所述应用数据报文的网络层报文头或网络层之上的云资源标识子层报文头以获取所述预定信息。
  14. 根据权利要求1所述的方法，其中，在接收的所述应用数据报文是所属的应用数据流中的首个应用数据报文的情况下，根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息之后，还包括：
    将确定的所述云节点和/或云资源实例的信息记录到流亲和转发表。
  15. 根据权利要求14所述的方法，其中，在接收的所述应用数据报文是所属的应用数据流中的非首个应用数据报文的情况下，还包括：
    根据所述流亲和转发表确定所述应用数据流对应的云节点和/或云资源实例的信息；
    根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
  16. 根据权利要求1所述的方法，其中，还包括以下至少之一：
    所述云资源标识路由表维护在网络路由和转发节点，其中，所述网络路由和转发节点包括：所述应用数据报文的网络入口节点和/或网络出口节点；
    所述云资源标识路由表维护在网络集中控制单元，并定期或基于请求向网络路由和转发节点同步，其中，所述网络路由和转发节点包括：所述应用数据报文的网络入口节点和/或网络出口节点。
  17. 一种云资源注册方法，包括：
    接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；
    根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
  18. 根据权利要求17所述的方法，还包括以下至少之一：
    将所述云资源标识路由表上报给网络集中控制单元；
    将所述云资源标识路由表在网络路由和转发节点之间洪泛。
  19. 一种路由装置，包括：
    第一确定模块，设置为获取接收的应用数据报文携带的预定信息，其中，所述预定信息包括：设置为处理所述应用数据报文中的应用数据的云资源的云资源标识；
    第二确定模块，设置为根据云资源标识路由表，确定所述预定信息所对应的云节点和/或云资源实例的信息，其中，所述云资源标识路由表以云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息；
    路由转发模块，设置为根据确定的所述云节点和/或云资源实例的信息路由并转发所述应用数据报文。
  20. 一种云资源注册装置，包括：
    接收模块，设置为接收云资源提供端上报的云资源信息，其中，所述云资源信息包括：所提供的云资源的云资源标识，以及用于提供所述云资源的云节点和/或云资源实例的信息；
    路由表维护模块，设置为根据所述云资源信息生成或更新云资源标识路由表，其中，所述云资源标识路由表以所述云资源标识为索引，记录用于提供所述云资源标识所标识的云资源的云节点和/或云资源实例的信息。
  21. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至16任一项中所述的方法的步骤，或者实现权利要求17-18任一项中所述的方法的步骤。
  22. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现所述权利要求1至16任一项中所述的方法的步骤，或者实现权利要求17-18任一项中所述的方法的步骤。
PCT/CN2022/099005 2021-08-27 2022-06-15 路由和云资源注册方法及装置、存储介质和电子装置 WO2023024663A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110997355.2A CN115733786A (zh) 2021-08-27 2021-08-27 路由和云资源注册方法及装置、存储介质和电子装置
CN202110997355.2 2021-08-27

Publications (1)

Publication Number Publication Date
WO2023024663A1 true WO2023024663A1 (zh) 2023-03-02

Family

ID=85290367

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/099005 WO2023024663A1 (zh) 2021-08-27 2022-06-15 路由和云资源注册方法及装置、存储介质和电子装置

Country Status (2)

Country Link
CN (1) CN115733786A (zh)
WO (1) WO2023024663A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117041259A (zh) * 2023-09-28 2023-11-10 新华三技术有限公司 计算资源的调度方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341252A (zh) * 2015-07-10 2017-01-18 中兴通讯股份有限公司 资源管理方法、装置及控制终端
CN109981322A (zh) * 2017-12-28 2019-07-05 北京京东尚科信息技术有限公司 基于标签的云资源管理的方法和装置
CN110621045A (zh) * 2018-06-20 2019-12-27 华为技术有限公司 一种物联网业务路由的方法
CN112511596A (zh) * 2020-11-05 2021-03-16 苏州浪潮智能科技有限公司 一种云平台中创建云资源的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341252A (zh) * 2015-07-10 2017-01-18 中兴通讯股份有限公司 资源管理方法、装置及控制终端
CN109981322A (zh) * 2017-12-28 2019-07-05 北京京东尚科信息技术有限公司 基于标签的云资源管理的方法和装置
CN110621045A (zh) * 2018-06-20 2019-12-27 华为技术有限公司 一种物联网业务路由的方法
CN112511596A (zh) * 2020-11-05 2021-03-16 苏州浪潮智能科技有限公司 一种云平台中创建云资源的方法和设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117041259A (zh) * 2023-09-28 2023-11-10 新华三技术有限公司 计算资源的调度方法及装置
CN117041259B (zh) * 2023-09-28 2024-01-12 新华三技术有限公司 计算资源的调度方法及装置

Also Published As

Publication number Publication date
CN115733786A (zh) 2023-03-03

Similar Documents

Publication Publication Date Title
US11190445B2 (en) System and method to facilitate content delivery to multiple recipients in a network environment
WO2022121349A1 (zh) 算力应用流量转发方法及装置
US10404592B2 (en) System and method to facilitate content forwarding using bit index explicit replication (BIER) in an information-centric networking (ICN) environment
WO2020182086A1 (zh) 一种bier报文的发送方法和装置
US11979322B2 (en) Method and apparatus for providing service for traffic flow
CN106059924B (zh) 一种管理信息的方法，装置及系统
US20220045944A1 (en) Method for Forwarding Service Data, Network Device, and Network System
EP4207685A1 (en) Message header processing method and apparatus, storage medium and electronic device
CN112511988B (zh) 报文转发方法、设备、系统、网络设备和存储介质
CN113206787B (zh) 分段标识的处理方法及设备
CN107580079A (zh) 一种报文传输方法和装置
WO2023024663A1 (zh) 路由和云资源注册方法及装置、存储介质和电子装置
CN112261054B (zh) 基于应用业务服务质量的Ethernet/IP与IPv6协议转换系统及方法
EP3503484B1 (en) Message transmission methods and devices
US20220116308A1 (en) Bier overlay signaling enhancement
CN106211141B (zh) 一种无线局域网漫游站点的流的转发方法及装置
WO2023165244A1 (zh) 报文的发送方法、装置、存储介质及电子装置
US20210044532A1 (en) A System in a Data Processing Network and a Method Therein for Enabling Routing of Data Flows To or From a Service in the Data Processing Network
WO2024021573A1 (zh) 基于网络切片的通信方法、电子设备和存储介质
US11997005B2 (en) BIER overlay signaling enhancement
WO2023109398A1 (zh) 一种报文传输方法及装置
WO2023050981A1 (zh) 虚拟专用网络业务标识的分配方法、报文处理方法及装置
WO2022088951A1 (zh) 信息处理方法、基站、承载网设备、核心网设备及介质
CN106789705A (zh) 传输控制报文的方法和装置
CN116614432A (zh) 报文处理方法、网元设备、控制设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22860010

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022860010

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022860010

Country of ref document: EP

Effective date: 20240327