CN105812261A - Message forwarding method and system in information center network - Google Patents

Abstract

The embodiment of the present invention provides a message forwarding method and system in an information center network. The method mainly includes: the resource manager queries the service registry it manages according to the service identifier carried in the service request packet; when it finds that the service corresponding to the service identifier is in the autonomous domain, it provides forward the service request packet to the corresponding exit; when it is determined that the service corresponding to the service identifier is not in the autonomous domain, query the inter-domain path identifier notification table to obtain the inter-domain route to the next autonomous domain of the service provider corresponding to the service identifier. The path identifier and related forwarding port information forward the service request packet to the next autonomous domain. The embodiment of the present invention realizes the parsing, searching and forwarding of the service request packet in the resource manager in the information center network, and each RM only needs to manage information such as the service identification registered on it, which reduces the registration of the service content of the RM, Update, delete and other operational burden.

Description

Message forwarding method and system in information center network

technical field

The invention relates to the field of network communication, in particular to a message forwarding method and system in an information center network.

Background technique

Resource access and service acquisition are important core functions of Internet services. The traditional domain name system (DNS: Domain Name System) completes the mapping between domain names and host IP addresses, rather than directly facing resources; if the host address storing a certain resource changes, the corresponding resource needs to be re-registered. This analysis method makes the network insufficient support for resource mobility, reduces flexibility, and lacks description of resource characteristics, which is not conducive to users' acquisition of resources. In addition, DNS also has problems such as slow response speed, poor error correction capability, and error-prone configuration.

In the process of network resource access and data acquisition, users actually focus on the resource itself, without knowing the location of the physical host where the resource is located. In response to this problem, the academic community has proposed an Information-Centric Networking (ICN: Information-CentricNetworking) architecture. The information center network assigns a unique service identifier (SID: ServiceIdentifier) to each resource, and when a user needs to obtain a certain service content, a service request packet (GETPacket) is sent to the network. The network node will use the SID carried in the service request packet to forward the service request packet (GET) to the next autonomous domain.

There are two existing naming mechanisms for resources: hierarchical naming mechanism and flat naming mechanism. The hierarchical naming structure can reflect the relationship between different data blocks, facilitate effective aggregation, reduce routing table entries, have good scalability, and adapt to complex network environments. However, this naming method has a certain relationship with the service provider. If the service provider changes, problems may easily occur in the user's retrieval of the actual content of the name, and it cannot support mobility well. The flat naming mechanism is far superior to the hierarchical naming mechanism in table lookup speed, and has the advantages of permanent naming and security. Since the content corresponds to a globally unique identifier, when the user obtains the service through a certain resolution mechanism, there is no case that the service cannot be obtained due to the change of the provider. At the same time, the naming mechanism has a self-certification function, and the verification method does not depend on the network, ensuring the reliability of the content.

In the information center network, a resource manager (RM: ResourceManager) can be used to complete service registration and search, as well as response and routing to service requests. RM adopts a hierarchical design and is connected to each other in a tree structure. The service provider first registers with its own RM, and registers to the highest level RM step by step. When a user requests a service, a query request is initiated, and the RM tree structure is searched up level by level until the corresponding RM is found. FIG. 1 is a registration search process of an information center network in the prior art. The parsing and forwarding mechanism of service request packets can be divided into two situations: intra-domain service parsing and inter-domain service parsing.

When the service requested by the user is in the local domain, the relevant forwarding information is obtained by searching the service registry in the RM of the local domain, and the service request packet (GET) is sent to the corresponding egress border router, and then forwarded to the service provider of the corresponding service Or, the service provider satisfies the request, so as to realize the service resolution in the domain.

When the domain RM cannot find the service requested by the user, according to the policy independently selected by the autonomous domain, the service request packet is sent to the resource manager of its Provider or Peer for search, and forwarded to the resource manager of the highest-level domain . The service request packet implements inter-domain routing by adding an inter-domain path identifier (PID, PacketIdentifier), and finally service providers in other autonomous domains respond to the service request to implement inter-domain service resolution.

However, the tree structure of RM means that each RM needs to maintain all registered service identification information of its subordinate RMs. Therefore, operations such as registration, update, and deletion of service content will increase the burden on the RM, especially the closer to the highest level, the heavier the burden on the RM. Therefore, the analysis, search and forwarding performance of RM to GET packets will become the bottleneck of the information center network architecture.

Contents of the invention

Embodiments of the present invention provide a message forwarding method and system in an information center network, so as to realize efficient forwarding of data packets in the information center network.

In order to achieve the above object, the present invention adopts the following technical solutions.

According to one aspect of the present invention, a message forwarding method in an information center network is provided, including:

After the resource manager receives the service request packet sent by the service requester in the information center network, it parses the service request packet, and queries the service registry it manages according to the service identifier carried in the service request packet;

When the resource manager finds the service identifier in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service identifier corresponding to the service identifier in the service registry, The service provider information forwards the service request packet to the corresponding exit;

When the resource manager determines that the service provider corresponding to the service identifier is not in the autonomous domain by querying the service registry it manages, it queries the inter-domain path identifier notification table managed by it to obtain the route to the service provider. The inter-domain path identifier and related forwarding port information of the next autonomous domain, according to the inter-domain path identifier and related forwarding port information, the service request packet is forwarded to the resource management of the next autonomous domain of the service provider device.

Further, after the resource manager receives the service request packet sent by the service requester in the information center network, it parses the service request packet, including:

After receiving the data packet sent by the service requester in the information center network, the ingress border router of the local autonomous domain encapsulates the routing protocol header of the local domain to the data packet, and sends the data packet to the resource manager of the local autonomous domain After the resource manager receives the data packet, it parses the protocol header of the data packet, obtains the contents of the Version and Type fields in the protocol header, and judges the type of the data packet according to the contents of the Version and Type fields;

After the resource manager determines that the data package is a service registration package, it extracts the service identification information contained in the service registration package to form a registry entry, and inserts and adds the registry entry into the service registry it manages; judging After the data packet is a service request packet, the service request packet is parsed to extract the service identification information contained in the service request packet.

Further, when the resource manager finds the service identifier in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service registry The service provider information corresponding to the service identifier forwards the service request packet to the corresponding exit, including:

The resource manager manages the service registry, and each entry in the service registry includes a service identifier SID, a flag bit Flag, a component identifier NID or an autonomous domain AS number, autonomous domain information, a forwarding port, and a corresponding autonomous domain route Address information and entry lifetime TTL;

The resource manager queries the service identifier in the service registry managed by it, and determines that the service provider corresponding to the service identifier is in this autonomous In the domain, the data packet is routed according to the component identification NID information in the entry corresponding to the service identification, and the data packet is forwarded to the service provider corresponding to the component identification NID information.

Further, when the resource manager determines that the service corresponding to the service identifier is not in the autonomous domain by querying the service registry managed by it, it queries the inter-domain path identifier notification table managed by it to obtain the route to the service provider. According to the inter-domain path identifier and related forwarding port information of the next autonomous domain, the service request packet is forwarded to the next autonomous domain resource management server of the service provider. devices, including:

The resource manager manages an inter-domain path identification notification table, and the inter-domain path identification notification table includes the AS number of the autonomous domain, the number of path identification PIDs, the path identification PID, the protocol forwarding information of the corresponding autonomous domain, and the forwarding port;

The resource manager queries the service identifier in the service registry managed by it, and determines that the service provider corresponding to the service identifier is not in this autonomous region according to the flag bit Flag included in the entry corresponding to the service identifier. In the domain, the AS number corresponding to the next autonomous domain to the service provider is searched in the service registry, and the inter-domain path identification notification table is queried through the AS number to obtain the next AS number to the service provider. An inter-domain path identifier of an autonomous domain and related forwarding port information;

The resource manager adds the inter-domain path identifier PID to the next autonomous domain of the service provider to the path identifier information at the end of the service request packet, and forwards the service request packet to the an egress border router, the egress border router decapsulates the domain routing protocol header of the service request packet, and forwards the service request packet to the next autonomous domain destined for the service provider through the relevant forwarding port information ingress border router.

Further, when the resource manager determines that the service provider corresponding to the service identifier is not in the autonomous domain by querying the service registry it manages, it queries the inter-domain path identifier notification table managed by it to obtain the route to The inter-domain path identifier and related forwarding port information of the next autonomous domain of the service provider, and forward the service request packet to the next server of the service provider according to the inter-domain path identifier and related forwarding port information. A resource manager for an autonomous domain, including:

The resource manager manages an inter-domain path identification notification table, and the inter-domain path identification notification table includes the AS number of the autonomous domain, the number of path identification PIDs, the path identification PID, the protocol forwarding information of the corresponding autonomous domain, and the forwarding port;

The resource manager cannot find the service identifier in the service registry managed by it, and the autonomous domain where the resource manager is located is a Tier-1 autonomous domain, then send a search failure message to the service requester, and discarding the service request packet; if the autonomous domain where the resource manager is located is not a Tier-1 autonomous domain, then according to the policy of the autonomous domain where the resource manager is located, select the next-hop Provider autonomous domain of the service request packet, and pass Look up the inter-domain path identification notification table to obtain the PID and related forwarding port information leading to the Provider autonomous domain, encapsulate the PID to the Provider autonomous domain at the end of the service request packet, and send the service request packet Forwarding to the egress border router of the autonomous domain, the egress border router decapsulates the routing protocol header of the domain, obtains the interdomain path identifier PID to the Provider autonomous domain from the path identifier information in the service request packet, Query the inter-domain path identifier notification table according to the path identifier, obtain the forwarding information to the ingress border router of the Provider autonomous domain, and send the service request packet to the ingress border router of the Provider autonomous domain, in the In the above-mentioned Provider autonomous domain, the service request packet is sent from the ingress border router to the resource manager in its autonomous domain, and the resource manager queries its service registry. If the service identification information cannot be found, then according to the autonomous domain policy , and continue forwarding to its Provider autonomous domain until the service request packet is forwarded to the autonomous domain where the service provider is located or the Tier-1 autonomous domain.

Further, the method also includes:

In the case of concurrent data packets, the resource manager uses a high-concurrency CuckooHashing algorithm to query the service identifier in the service registry.

Further, the method also includes:

The ingress border router of the autonomous domain where the service identifier is located encapsulates the domain routing protocol header for the service request packet, and sends the service request packet to the resource manager of the autonomous domain where the service provider is located, and the autonomous domain where the service provider is located After receiving the service request packet, the resource manager of the domain extracts the service identifier SID in the service request packet, queries the service identifier in the service registry it manages, and according to the corresponding SID in the service registry item The component identification NID information is used to route the service request packet, and forward the service request packet to the service provider;

After receiving the service request packet, the service provider extracts the service identification SID and service behavior description SBD information in the service request packet, finds the corresponding data, generates a service data packet, and extracts the service request The path identification information at the end of the packet, the path identification information is encapsulated into the header of the service data packet, the domain routing protocol header is encapsulated for the service data packet, and the service data packet is sent to the egress border router of the domain, so The egress border router of the local domain strips the domain routing protocol header in the service data packet, and obtains the inter-domain path identification to the next autonomous domain of the service requester from the path identification information in the service data packet PID, querying the inter-domain routing table according to the path identifier, obtaining the ingress border router of the next autonomous domain, stripping off the inter-domain path identifier PID to the next autonomous domain, and sending the service data packet to the next autonomous domain The ingress border router of the next autonomous domain;

After receiving the service data packet, the ingress border router of the next autonomous domain encapsulates the domain routing protocol header in the service data packet, and obtains the route to the next autonomous domain from the path identification information in the service data packet. The inter-domain path identifier PID of the domain, query the inter-domain routing table according to the path identifier, and obtain the egress border router of the domain going to the next autonomous domain, and send the service data packet to the egress border router of the domain; The egress border router of the local domain strips off the domain routing protocol header in the service data packet, obtains the inter-domain path identification PID to the next autonomous domain from the path identification information in the service data packet, and according to the The path identifier queries the inter-domain routing table, and obtains the ingress border router of the next autonomous domain, strips off the inter-domain path identifier PID to the next autonomous domain, and sends the service data packet to the next The ingress border router of the autonomous domain;

And so on, until the service data packet is sent to the ingress border router of the autonomous domain where the service requester is located, at this time, the ingress border router sends the packet according to the NID information contained in the data packet to the access router of the service requester, and the access router sends the data packet to the service requester.

According to another aspect of the present invention, a message forwarding device in an information center network is provided, the device is set in an autonomous domain, and the device includes: an ingress border router, a resource manager and an egress border router;

The ingress border router is configured to, after receiving the data packet sent by the service requester in the information center network, encapsulate the header of the local domain routing protocol on the data packet, and send the data packet to the resource manager of the local autonomous domain, The egress border router of the autonomous domain, or other network nodes of the autonomous domain;

The resource manager is configured to parse the service request packet after receiving the service request packet sent by the ingress border router, and query the service registry managed by it according to the service identifier carried in the service request packet;

When the service identifier is queried in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service provider information corresponding to the service identifier in the service registry, the The service request packet is forwarded to the corresponding exit;

When it is determined by querying the service registry managed by it that the service provider corresponding to the service identifier is not in the autonomous domain, then query the inter-domain path identifier notification table managed by it to obtain the route to the next autonomous domain of the service provider. An inter-domain path identifier and related forwarding port information, forwarding the service request packet to the egress border router according to the inter-domain path identifier and related forwarding port information;

The egress border router is configured to strip the header of the local routing protocol in the service data packet, and obtain the inter-domain path identifier PID to the next autonomous domain from the path identification information in the service data packet, according to The path identifier queries the inter-domain routing table, and obtains the ingress border router of the next autonomous domain, strips off the inter-domain path identifier PID to the next autonomous domain, and sends the service data packet to the next autonomous domain An ingress border router of an autonomous domain; or obtain the inter-domain path identifier to the next autonomous domain of the service provider from the service request packet, query the inter-domain routing table according to the path identifier, and obtain the next The ingress border router of the autonomous domain, and sends the service request packet to the ingress border router of the next autonomous domain.

Further, the resource manager includes:

The autonomous domain protocol header processing module is used to manage the source and destination address fields, the path identification field, and the message length field in the protocol header of the data packet, and the data packet includes a service request packet and a service registration packet;

The inter-domain path identification negotiation and calculation distribution module is used for the negotiation and calculation of inter-domain path information, and maintains and updates the inter-domain path identification notification table information;

The strategy library module is used to determine the negotiation and calculation strategy of inter-domain path information and the update search strategy of the service registry;

The service registration package processing module is used for parsing and processing the arriving service registration package, extracting the registration information in the service registration package, and inserting or updating the service registry managed by it according to the extracted registration information;

The service request packet processing module is used to analyze the arriving service request packet, first decapsulate the routing protocol header of the domain, extract the service identification SID information in the service request packet, and query the service identification in the service registry managed by it , according to the flag bit Flag contained in the entry of the service registry, it is determined that the service provider corresponding to the service identifier is in the autonomous domain, and then the data packet is processed according to the component identifier NID information corresponding to the SID in the service registry entry Routing, forwarding the data packet to the service provider corresponding to the component identification NID information;

Inquire the service identifier in the service registry, and determine that the service provider corresponding to the service identifier is not in the autonomous domain according to the flag bit Flag contained in the table item of the service registry, then find out in the service registry Go to the AS number corresponding to the next autonomous domain of the service provider; query the inter-domain path identification notification table through the AS number, and obtain the PID and related forwarding port information leading to the next autonomous domain of the service provider ; Add the inter-domain path identifier PID to the path identifier information at the end of the service request packet, and forward the service request packet to the egress border router of the autonomous domain;

The service identification cannot be found in the service registry, and the PID and related forwarding port information of the Provider domain leading to the autonomous domain are obtained by searching the inter-domain path identification notification table, and the connection information is encapsulated at the end of the data packet. The PID of the Provider domain forwards the data packet to the egress border router of the autonomous domain, and the egress border router decapsulates the routing protocol header of the domain, and forwards the service request packet to the egress border router through the relevant forwarding port information. The ingress border router of the Provider domain, the ingress border router encapsulates the domain routing protocol header to the service request packet, sends the service request packet to the resource manager of the Provider domain, until the service request packet forward to the ingress border router of the autonomous domain where the service provider is located.

According to another aspect of the present invention, a message forwarding system in an information center network is provided, including: a plurality of autonomous domains, each of which includes the message forwarding device.

It can be seen from the technical solutions provided by the above-mentioned embodiments of the present invention that the embodiments of the present invention realize the analysis, search and forwarding of the service request packet (GET) in the resource manager in the information center network, and each RM only needs to manage the The service identification and other information registered on it greatly reduces the operational burden of registering, updating, and deleting RM's service content. This method can support large-scale networks while ensuring high efficiency in the analysis and forwarding of data packets in the information center network. Environment scalability.

Additional aspects and advantages of the invention will be set forth in part in the description which follows, and will become apparent from the description, or may be learned by practice of the invention.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without any creative effort.

FIG. 1 is a schematic diagram of a registration search process of an information center network in the prior art;

Fig. 2 is a schematic diagram of a definition method of a service request packet (GET packet) provided by an embodiment of the present invention;

FIG. 3 is a schematic diagram of a parsing process of a service request packet (GET packet) in an inter-domain service parsing process provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of an organization mode of an inter-domain path identification notification table (PIDTable) provided by an embodiment of the present invention;

FIG. 5 is a schematic diagram of an organization mode of a service registry (SIDTable) provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of an intra-domain service parsing and forwarding mechanism provided by an embodiment of the present invention;

FIG. 7 is a schematic diagram of an inter-domain service resolution and forwarding mechanism provided by an embodiment of the present invention;

FIG. 8 is a schematic diagram of a high-concurrency CuckooHashing search process provided by an embodiment of the present invention;

FIG. 9 is a schematic diagram of a highly concurrent CuckooHashing insertion process provided by an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a message forwarding device in an information center network provided by an embodiment of the present invention;

FIG. 11 is a schematic diagram of functional modules of a resource manager RM provided by an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a message forwarding system in an information center network provided by an embodiment of the present invention.

detailed description

Embodiments of the present invention are described in detail below, examples of which are shown in the drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present invention and should not be construed as limiting the present invention.

Those skilled in the art will understand that unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the word "comprising" used in the description of the present invention refers to the presence of said features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Additionally, "connected" or "coupled" as used herein may include wirelessly connected or coupled. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

Those skilled in the art can understand that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It should also be understood that terms such as those defined in commonly used dictionaries should be understood to have a meaning consistent with the meaning in the context of the prior art, and unless defined as herein, are not to be interpreted in an idealized or overly formal sense Explanation.

In order to facilitate the understanding of the embodiments of the present invention, several specific embodiments will be taken as examples for further explanation below in conjunction with the accompanying drawings, and each embodiment does not constitute a limitation to the embodiments of the present invention.

The embodiment of the present invention mainly aims at the situation that resource naming adopts a flat naming mechanism in the information center network, and expounds the analysis, search and forwarding scheme of the service request packet (GET) in the resource manager RM.

The service request package (GET) contains relevant information such as the service identification SID corresponding to a required service. Figure 2 is a definition method of the service request package (GET), including the following fields:

Version: The version number of the data packet, 4bit. The Version value of the service request packet (GET) can be designed as 1010.

Type: packet type, 4bit. The Type value of the service request packet (GET) can be designed as 0000.

TTL: Time-to-live, time to live, 8bit, that is, the maximum number of network segments allowed to pass before the specified service request packet (GET) is discarded.

Total_Length: The total length of the GET package, 16bit, up to 65535 bytes.

Port_Number: Port number, 16bit, identifying the source and destination application process.

MinimalPIDChangePeriod: Minimum PID update period, 16bit.

PIDs: The number of PIDs included at the end of the GET packet, 8bit.

O: Flag bit, indicating whether to fragment, 1 bit. This field and the 32-bit Offset field are designed for packet fragmentation. O=0, the Offset field indicates the entire content block corresponding to the SID (ie: Offset=0); O=1: indicates that the request starts from the value of the Offset field, and the length is a part of the Length field.

Reserved: Reserved field, 7bit.

Offset: slice offset, 32bit, is an optional field. Combined with the O field, if the data packet requires fragmentation, this field indicates the offset distance from the original data packet.

Length: The length of the data packet starting from the slice offset, 32bit, is an optional field. Combined with the O field, if the data packet requires fragmentation, a content block with a length of Length is extracted from Offset.

LengthofContentCharacteristics: Service behavior description length, 16bit.

MTU: Maximum Transmission Unit (MaximumTransmissionUnit), 16bit, indicates the maximum data packet size that can pass, if it exceeds, the data packet needs to be fragmented.

LengthofPublicKey: public key length, 16bit.

Checksum: Indicates the checksum of the GET packet header, 16bit.

NIDPartofanSID: The component ID corresponding to the service provider, 128bit.

SID: Service ID, 160bit.

NID: The component ID corresponding to the service requester, 128bit.

ContentCharacteristics: service behavior description, optional field, the length is determined by the LengthofContentCharacteristics field.

PublicKey: public key, the length is determined by the LengthofPublicKey field.

PID: Inter-domain path identifier, with a length of 32 bits. Each time an autonomous domain is passed, a PID is added.

Based on the above definition of the service request packet, the embodiments of the present invention provide a message forwarding method, device and system, so as to realize efficient parsing, searching and forwarding of the service request packet.

When a user needs to obtain a certain service, he will send a service request packet (GET) to the resource manager RM in the domain for service query. The resource manager RM of each autonomous domain will analyze the arriving service request packet, extract service identification (SID) and other related information, perform matching search, and execute related actions.

When the data packet arrives at the resource manager, the resource manager first decapsulates the header of the autonomous domain protocol encapsulated before the data packet, and then judges the type of the data packet. If it is a service registration package (Registration), register the service identification SID and other information contained in it into the service registry (SIDTable); if it is a service request package (GET), first extract the corresponding service identification SID and other information, and then Look up the service registry (SIDTable). During the search process, if the service request requires cross-domain resolution, it is necessary to query the inter-domain path identification notification table (PIDTable) to obtain the path information required for inter-domain routing, and encapsulate the path identification PID at the end of the GET packet. Finally, after parsing and searching, the GET packet will encapsulate the protocol header of the autonomous domain and forward it to the next node.

The service registry managed by the resource manager maintains the service registration information of the autonomous domain and the registration information of its customer domain (Customer) or neighbor domain (Peer). Therefore, the parsing mechanism for the service request packet (GET) can be divided into two situations: intra-domain service parsing and inter-domain service parsing. The intra-domain service resolution process is mainly for the situation that the service is in the autonomous domain.

The inter-domain service resolution process is mainly aimed at the situation that the service cannot be found in other autonomous domains or in this domain. The specific process is shown in Figure 3, and the analysis steps are as follows:

Step 1, obtain the data packet arriving by the network card.

The autonomous domain protocol header processing module decapsulates the autonomous domain protocol header in the data packet, analyzes the Version and Type fields of the data packet, and determines whether it is a service request packet (GET). If it is a GET package, then perform step 2; if it is a registration package, analyze and extract the corresponding service identification information according to the definition of the registration package, form a registry entry, and insert the registry entry into the service registry (SIDTable).

Step 2, extracting the service identifier SID. Parse the corresponding field in the GET packet to obtain the content of the service identifier SID field, which is used to find a match.

Step 3, look up the service registry (SIDTable), and match the SID information. The SID information is searched in the service registry, and the entry of the service registry includes a flag bit Flag. If the value of Flag is 1, it means that the service is in this autonomous domain; if the value of Flag is 0, it means that the service is registered from other autonomous domains. According to the SID matching result, if the search is successful and the Flag value is 1, go to Step 4; if the search is successful and the Flag value is 0, go to Step 5; if the search fails, go to Step 6.

Step 4, if the SID matches and the service is in the local domain, routing is performed according to the NID information corresponding to the SID in the service registry entry, and forwarded to the corresponding exit.

Step 5, the SID matches and the service is not in the local domain. At this time, the inter-domain path identifier PID needs to be encapsulated to complete the inter-domain routing. The relevant information of the inter-domain path identifier (PID) is stored in the inter-domain path identifier notification table (PIDTable), which includes information such as the path identifier and forwarding port corresponding to the communication between the autonomous domains. If the SID matches and is not in the local domain, the AS (Autonomous System, autonomous domain) number corresponding to the autonomous domain where the SID is located is first searched in the service registry. Query the inter-domain path identification notification table (PIDTable) through the AS number to obtain the PID and related forwarding port information leading to the autonomous domain. If the autonomous domain is an IPv4 domain, modify the corresponding source and destination IP address information in the IP header. The value of the PIDs field in the GET packet is increased by 1, and the value of the Total_Length field is modified accordingly according to the packet length. The corresponding PID is encapsulated at the end of the GET packet, and then forwarded to the corresponding port.

Step 6, the SIDs do not match. At this time, by default, the GET packet is sent to its Provider domain for search, and the inter-domain path identifier PID needs to be encapsulated to complete inter-domain routing. Similarly, information related to the path identifier leading to the Provider domain is obtained by searching the inter-domain path identifier notification table (PIDTable). Increase the value of the PIDs field by 1, modify the TotalLength length, encapsulate the PID, and then forward the GET packet to its Provider domain. If the autonomous domain is already Tier-1 and the relevant information corresponding to the service cannot be queried, a query failure message will be returned.

Considering large-scale service requests and massive registration information searches, the process of searching the service registry (SIDTable) and matching SID information in the resource manager can use the optimized high-concurrency CuckooHashing algorithm, combined with the Intel data plane development kit ( DPDK) forwarding advantages, such as user space polling, data packet zero copy, multi-core CPU affinity and other features, optimize the CuckooHashing algorithm for large page memory, preprocessing, batch processing, SSE instruction set operations, etc., to achieve efficient search and forwarding .

Embodiment 1: the organization mode of the inter-domain path identification notification table (PIDTable)

The inter-domain path identification notification table (PIDTable) is obtained through mutual negotiation and calculation between resource managers. A design method of an inter-domain path identification notification table (PIDTable) provided by an embodiment of the present invention is shown in FIG. Forwarding information (such as source and destination IP addresses included in the IPv4 domain) and forwarding ports.

Embodiment 2: the organization mode of the service registry (SIDTable)

A design method of a service registry (SIDTable) provided by an embodiment of the present invention is shown in FIG. domain registration), component identifier NID or AS number of autonomous domain, autonomous domain information, forwarding port, routing address information of corresponding autonomous domain (for example, in IPv4 domain, it includes source and destination IP addresses), and entry lifetime TTL, etc.

Embodiment three:

This embodiment describes the intra-domain service parsing and forwarding mechanism, as shown in FIG. 6 .

When a user (Client) needs to obtain a certain service, it will first send a service request packet (GET) to the RM in the domain for service query. In this embodiment, the GET packet sent by the user is used to request the service corresponding to the service identifier SID1.

The service request packet (GET) sent by the user first arrives at the ingress border router Switch3. The border router Switch3 judges and recognizes the arriving service request packet (GET). Because it is a service request packet, according to the design of the information center network, the service request packet sent by the user does not contain any protocol headers, so the resource manager RM uses the GET packet parsing module to perform separate mapping processing of identity and location, and encapsulates the service request packet The header of the autonomous domain protocol corresponding to the domain is forwarded to the resource manager of the domain, as shown in RM1 in Figure 6.

The resource manager RM in this domain uses the GET packet parsing module to extract relevant information such as the service identifier SID1 in the service request packet, and performs query matching in the service registry (SIDTable) stored and maintained by it.

The resource manager RM searches for the service identifier SID1 according to the designed search algorithm. If the service identifier SID1 is queried, and the flag bit Flag of the corresponding entry is 1, it means that the requested service is in the local domain. Therefore, modify the address information in the header of the autonomous domain protocol according to the corresponding component identifier NID1 and the forwarding information stored in RM (for example, the IPv4 domain contains source and destination IP address information and forwarding port), and send GET to the corresponding egress boundary router.

The egress border router first judges the arriving data packet. If it is a normal data packet, it forwards it according to the intra-domain routing protocol; The header is forwarded to the component node corresponding to the component identifier NID1.

After the component node receives the service request packet, it extracts information such as the service identifier SID1 therein, encapsulates the service data corresponding to the service identifier SID1 into a service data packet (DATA), and sends it to the user.

Embodiment four:

This embodiment describes the inter-domain service parsing and forwarding mechanism, as shown in FIG. 7 .

If the user cannot find the corresponding service information in the resource manager RM of the local domain, the service request packet will be sent to the resource manager of the provider (Provider) domain to search according to the policy independently selected by the autonomous domain, until the highest layer domain.

The user initiates a service request, and sends the GET packet containing the service identifier SID1 to the resource manager RM4 of the domain for query.

Because the service registry (SIDTable) in RM4 does not contain the relevant information of SID1, the query fails. Extract the AS number corresponding to the Provider domain in the D4 domain, query the inter-domain path identification notification table (PIDTable), and obtain the inter-domain path identification PID corresponding to the corresponding Provider domain and related forwarding information. In this example, the AS number corresponding to the Provider domain (D5) of the D4 domain is used.

Encapsulate the inter-domain path identifier P2 corresponding to the D4 domain to the Provider domain (D5) at the end of the GET packet, increase the value of the PIDs field by 1, and modify the corresponding Total_Length value accordingly. The service request packet (GET) is forwarded to the egress border router of the autonomous domain, and the egress border router decapsulates the routing protocol header of the domain, and obtains the route to the Provider autonomous domain from the path identification information in the service request packet. The inter-domain path identifier PID of the domain, query the inter-domain routing table according to the path identifier, obtain the ingress border router of the Provider autonomous domain, and send the service request packet to the ingress border router of the Provider autonomous domain, the The ingress border router sends the service request packet to the resource manager RM5 in the Provider domain to continue the query. until forwarding the service request packet to the ingress border router of the autonomous domain where the service identifier is located.

Similarly, if the search fails, it will continue to forward to its Provider domain until it is forwarded to the resource manager in the highest domain for query.

The resource manager RM6 of the highest domain extracts the service identification SID1 and other relevant information in the service request package, and performs query matching in the service registry (SIDTable) stored and maintained by the search algorithm designed. If the service identifier SID is queried, the flag bit Flag of the table entry where it is located is detected. If the value of the Flag is 0, the AS number corresponding to the service is queried, which is registered by the resource manager RM3 of the D3 domain. Therefore, according to the inter-domain path identification notification table (PIDTable), the inter-domain routing information of the resource manager RM3 in the D3 domain is obtained, the corresponding inter-domain path identification P3 is encapsulated, the corresponding fields of the GET packet are modified accordingly, and then sent to RM3. If the service cannot be queried, a query failure message will be returned.

RM3 queries the local service registry (SIDTable), and then queries the inter-domain path identification notification table (PIDTable) according to the registration information, obtains the inter-domain routing information, encapsulates the inter-domain path identification P4, and forwards it to the resource manager RM1 of the D1 domain.

RM1 performs intra-domain service analysis, and forwards the service request to the service provider according to the component identification NID1 information.

Since the requested service is not in the local domain, the service request packet needs to be queried and forwarded through autonomous domains with different protocols. Each time an autonomous domain is passed, the path identifier required for inter-domain routing needs to be encapsulated at the end of the service request packet. As shown in the process of (i)-(vii) in Figure 7, the end of the service request packet will add the inter-domain path identifiers in sequence, such as P2, P1, P3 and P4 in Figure 7.

After receiving the service request packet, the service provider Server will extract the service identification SID and service behavior description SBD and other information, find the corresponding data, and generate a service data packet (DATA). At the same time, the path identification information at the end of the service request packet is extracted, and the path identification information is encapsulated in the header of the service data packet in sequence, such as P4, P3, P1 and P2 in FIG. 7 .

The server first sends the service data packet to the border router of the domain (D1), strips the IP protocol header of the domain, and performs inter-domain routing through the path identifier P4.

When the data packet arrives at the ingress border router of the D3 domain, the path identifier P4 is stripped off, the LSP (namely LSP1) of MPLS in the local domain is encapsulated, and sent to the egress border router R3 of the domain (D3). Similarly, after the MPLS header of the local domain is stripped, the path identifier P3 is used to perform inter-domain routing to the next autonomous domain.

Through this method, the data packet finally arrives at the requesting user, completing the analysis and forwarding of the inter-domain service.

Every time it passes through an autonomous domain, it will go through the process of encapsulating the routing protocol header of this domain and stripping the routing protocol header of this domain. At the same time, the corresponding path identification information will be deleted each time an autonomous domain is passed. The advantage of this is that the service requester cannot be traced to the specific location of the service provider, which effectively improves the security of the network.

Embodiment five:

This embodiment describes an implementation manner of encapsulation and decapsulation of routing protocol headers of nodes in an autonomous domain.

Taking the IPv4 domain as an example, after the ingress border router receives a service request packet (GET) that does not contain any routing protocol header, it recognizes it as a service request packet (GET) according to the Version and Type fields, queries its intra-domain routing table, and obtains the destination resource The relevant information such as the IP address of the manager encapsulates the IP header for the service request packet, and then forwards the packet according to the IP header.

After the service request packet (GET) arrives at the resource manager, it first decapsulates the IP header, extracts the service identifier from the service request packet (GET), queries the service registry, and performs corresponding operations according to the query result.

1) If the service identifier is queried from the service registry, and the service provider is in the autonomous domain, extract the NID of the service provider, use the IP address of the service provider as the destination address, and encapsulate the IP header for the service request packet , and send the service request packet to the service provider;

2) If the service identifier is queried from the service registry, but the service provider is not in the autonomous domain, then obtain the AS number of the next autonomous domain to the service provider, and query the inter-domain routing table according to the AS number , obtaining the inter-domain path to the next autonomous domain, and attaching the path to the end of the service request packet; then, according to the path identification PID information of the inter-domain path, querying the egress router corresponding to the PID, and Using the IP address of the egress router as the destination address, encapsulating the IP header for the service request packet, and sending the service request packet to the egress router;

3) If the service identifier cannot be found from the service registry and the autonomous domain is a Tier-1 autonomous domain, send a query failure message to the service requester and discard the service request; if the autonomous domain is not a Tier-1 autonomous domain 1 autonomous domain, then according to the policy of the autonomous domain, select a Provider autonomous domain, query the inter-domain path identifier to the autonomous domain, query the inter-domain path table according to the inter-domain path identifier, and obtain the provider autonomous domain The egress border router, and use the IP address of the egress router as the destination address, encapsulate the IP header for the service request packet, and send the service request packet to the egress router.

After identifying the arriving service request packet (GET), the egress border router first performs decapsulation operation, strips off the IP header, identifies the PID according to the inter-domain path at the end of the service request packet (GET), and performs domain Inter-routing, the packet is sent to the ingress border router of the service provider's next autonomous domain.

Embodiment six:

This embodiment mainly implements a solution for fast parsing, searching and forwarding of a service request packet (GET) for a large-scale network and a large amount of registration information.

The CuckooHashing algorithm satisfies concurrent access, fast search, and occupies a small memory space. Different from the traditional "space for time" hash algorithm, the CuckooHashing algorithm not only has a lookup complexity and an insertion complexity of O(1), but also handles The design of hash collision makes the utilization of hash table space high. In view of the characteristics of the flat naming of the service identifier SID, the use of this algorithm and data structure is to meet the search performance requirements of the implementation scheme. Since this solution solves the situation where the reading load is heavy, the optimistic lock based on the counter is selected to realize the multi-threaded high concurrent access of the CuckooHashing table.

This embodiment describes the search process of the optimized high-concurrency CuckooHashing algorithm, as shown in FIG. 8 .

First, pass in the Key value to be looked up.

Obtain the values of the two Buckets _index_hash and _alt_hash through calculation, and read the corresponding Counter VersionCounter value to record v1 and v2.

When the value of the counter is even, the search starts.

First check whether it matches the Tag field corresponding to b1, if yes, continue, if not, return.

Query and compare in b1. If it does not match, check whether it matches the Tag field corresponding to b2. If yes, enter b2 and then match. If it matches, get the corresponding port value (Val).

Finally, it is necessary to re-read the values v1' and v2' of the counter again. If they are equal, the search is successful, otherwise, return to the search again.

This embodiment describes the insertion process of the optimized high-concurrency CuckooHashing algorithm, as shown in FIG. 9 .

To find empty nodes, use BFS (breadth-first traversal algorithm) to find insertable empty nodes in the hash bucket.

After finding an empty node, all nodes move in reverse order along the search path to insert the Key value.

Before inserting the Key, the counter value corresponding to b1 or b2 is first increased by 1, and the value of the counter is an odd number at this time. If there is a read operation at this time, return to wait until the value of the counter becomes an even number, and then perform the read operation again.

After the entire insertion process is completed, the corresponding counter value is increased by 1 to make it back to an even number.

At the same time, combined with the characteristics of DPDK user space polling, zero copy of data packets, and multi-core CPU affinity, the CuckooHashing algorithm is optimized for large page memory, preprocessing, batch processing, and SSE instruction set operations, which can make large-scale service requests, In the case of massive registration information, the parsing, searching and forwarding speed of GET packets reaches the limit speed of DPDK forwarding data packets.

Embodiment seven:

An embodiment of the present invention provides a message forwarding device in an information center network. The structural diagram of the device is shown in FIG. 10 , and it is set in an autonomous domain. border router;

The ingress border router is configured to, after receiving the data packet sent by the service requester in the information center network, encapsulate the header of the local domain routing protocol on the data packet, and send the data packet to the resource manager of the local autonomous domain, The egress border router of the autonomous domain, or other network nodes of the autonomous domain;

The resource manager is configured to parse the service request packet after receiving the service request packet sent by the ingress border router, and query the service registry managed by it according to the service identifier carried in the service request packet;

When the service identifier is queried in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service provider information corresponding to the service identifier in the service registry, the The service request packet is forwarded to the corresponding exit;

When it is determined by querying the service registry managed by it that the service provider corresponding to the service identifier is not in the autonomous domain, then query the inter-domain path identifier notification table managed by it to obtain the route to the next autonomous domain of the service provider. An inter-domain path identifier and related forwarding port information, forwarding the service request packet to the egress border router according to the inter-domain path identifier and related forwarding port information;

The egress border router is configured to strip the header of the local routing protocol in the service data packet, and obtain the inter-domain path identifier PID to the next autonomous domain from the path identification information in the service data packet, according to The path identifier queries the inter-domain routing table, and obtains the ingress border router of the next autonomous domain, strips off the inter-domain path identifier PID to the next autonomous domain, and sends the service data packet to the next autonomous domain An ingress border router of an autonomous domain; or obtain the inter-domain path identifier to the next autonomous domain of the service provider from the service request packet, query the inter-domain routing table according to the path identifier, and obtain the next The ingress border router of the autonomous domain, and sends the service request packet to the ingress border router of the next autonomous domain.

Taking the implementation based on the IntelDPDK (DataPlaneDevelopmentKit, data plane development kit) platform as an example, the embodiment of the present invention provides a message forwarding device in the information center network. The structural diagram of the device is shown in FIG. manager, including:

The autonomous domain protocol header processing module is used to manage the source and destination address fields, the path identification field, and the message length field in the protocol header of the data packet, and the data packet includes a service request packet and a service registration packet;

The inter-domain path identification negotiation and calculation distribution module is used for the negotiation and calculation of inter-domain path information, and maintains and updates the inter-domain path identification notification table information;

The strategy library module is used to determine the negotiation and calculation strategy of inter-domain path information and the update search strategy of the service registry;

The service registration package processing module is used for parsing and processing the arriving service registration package, extracting the registration information in the service registration package, and inserting or updating the service registry managed by it according to the extracted registration information;

The service request packet processing module is used to analyze the arriving service request packet, first decapsulate the routing protocol header of the domain, extract the service identification SID information in the service request packet, and query the service identification in the service registry managed by it , according to the flag bit Flag contained in the entry of the service registry, it is determined that the service provider corresponding to the service identifier is in the autonomous domain, and then the data packet is processed according to the component identifier NID information corresponding to the SID in the service registry entry Routing, forwarding the data packet to the service provider corresponding to the component identification NID information;

Inquire the service identifier in the service registry, and determine that the service provider corresponding to the service identifier is not in the autonomous domain according to the flag bit Flag contained in the table item of the service registry, then find out in the service registry Go to the AS number corresponding to the next autonomous domain of the service provider; query the inter-domain path identification notification table through the AS number, and obtain the PID and related forwarding port information leading to the next autonomous domain of the service provider ; Add the inter-domain path identifier PID to the path identifier information at the end of the service request packet, and forward the service request packet to the egress border router of the autonomous domain;

The service identification cannot be found in the service registry, and the PID and related forwarding port information of the Provider domain leading to the autonomous domain are obtained by searching the inter-domain path identification notification table, and the connection information is encapsulated at the end of the data packet. The PID of the Provider domain forwards the data packet to the egress border router of the autonomous domain, and the egress border router decapsulates the routing protocol header of the domain, and forwards the service request packet to the egress border router through the relevant forwarding port information. The ingress border router of the Provider domain, the ingress border router encapsulates the domain routing protocol header to the service request packet, sends the service request packet to the resource manager of the Provider domain, until the service request packet forward to the ingress border router of the autonomous domain where the service provider is located.

A schematic structural diagram of a message forwarding system in an information center network provided by this embodiment is shown in FIG. 12 , including: multiple autonomous domains, each of which includes the message forwarding device described in FIG. 11 .

The specific process of message forwarding in the information center network using the device and system of the embodiment of the present invention is similar to the foregoing method embodiment, and will not be repeated here.

In summary, the embodiment of the present invention realizes the parsing, searching and forwarding of the service request packet (GET) in the resource manager in the information center network, and each RM only needs to manage information such as the service identification registered on it, greatly The operational burden of registering, updating, and deleting RM's service content is reduced. This method can support scalability in a large-scale network environment while ensuring high efficiency in parsing and forwarding data packets in the information center network.

In this method, in the case of large-scale service requests and massive registration information, the analysis, search and forwarding of GET packets can be performed by combining and optimizing the data plane development kit (DPDK) and the high-concurrency CuckooHashing algorithm.

In the information center network, the resource manager RM is in the core position in the search process of the service. The present invention proposes a node structure organization of the resource manager RM and a method for searching and forwarding the service identification, which ensures the service in the information center network. Parsing efficiency and reliability, a large-scale service request, massive registration information parsing scheme is proposed, and scalability under large-scale network conditions is supported.

Those skilled in the art can understand that the accompanying drawing is only a schematic diagram of an embodiment, and the modules or processes in the accompanying drawing are not necessarily necessary for implementing the present invention.

It can be seen from the above description of the implementation manners that those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in storage media, such as ROM/RAM, disk , CD, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments of the present invention.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device or system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for relevant parts, please refer to part of the description of the method embodiments. The device and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present invention can easily think of changes or Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. A message forwarding method in an information center network, characterized in that, comprising: After the resource manager receives the service request packet sent by the service requester in the information center network, it parses the service request packet, and queries the service registry it manages according to the service identifier carried in the service request packet; When the resource manager finds the service identifier in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service identifier corresponding to the service identifier in the service registry, The service provider information forwards the service request packet to the corresponding exit; When the resource manager determines that the service provider corresponding to the service identifier is not in the autonomous domain by querying the service registry it manages, it queries the inter-domain path identifier notification table managed by it to obtain the route to the service provider. The inter-domain path identifier and related forwarding port information of the next autonomous domain, according to the inter-domain path identifier and related forwarding port information, the service request packet is forwarded to the resource management of the next autonomous domain of the service provider device. 2. The message forwarding method in the information center network according to claim 1, characterized in that, after the resource manager receives the service request packet sent by the service requester in the information center network, The service request package is parsed, including: After receiving the data packet sent by the service requester in the information center network, the ingress border router of the local autonomous domain encapsulates the routing protocol header of the local domain to the data packet, and sends the data packet to the resource manager of the local autonomous domain After the resource manager receives the data packet, it parses the protocol header of the data packet, obtains the contents of the Version and Type fields in the protocol header, and judges the type of the data packet according to the contents of the Version and Type fields; After the resource manager determines that the data package is a service registration package, it extracts the service identification information contained in the service registration package to form a registry entry, and inserts and adds the registry entry into the service registry it manages; judging After the data packet is a service request packet, the service request packet is parsed to extract the service identification information contained in the service request packet. 3. The message forwarding method in the information center network according to claim 2, characterized in that, when the resource manager finds the service identifier in the service registry managed by it, and the If the service provider corresponding to the service identifier is in the autonomous domain, forward the service request packet to the corresponding exit according to the service provider information corresponding to the service identifier in the service registry, including: The resource manager manages the service registry, and each entry in the service registry includes a service identifier SID, a flag bit Flag, a component identifier NID or an autonomous domain AS number, autonomous domain information, a forwarding port, and a corresponding autonomous domain route Address information and entry lifetime TTL; The resource manager queries the service identifier in the service registry managed by it, and determines that the service provider corresponding to the service identifier is in this autonomous In the domain, the data packet is routed according to the component identification NID information in the entry corresponding to the service identification, and the data packet is forwarded to the service provider corresponding to the component identification NID information. 4. The message forwarding method in the information center network according to claim 2, wherein, when the resource manager determines that the service corresponding to the service identifier is not in the autonomous domain by querying the service registry managed by it, Then query the inter-domain path identification notification table managed by it, obtain the inter-domain path identification and related forwarding port information going to the next autonomous domain of the service provider, and forward all the information according to the inter-domain path identification and related forwarding port information The above service request packet is forwarded to the next autonomous domain resource manager destined for the service provider, including: The resource manager manages an inter-domain path identification notification table, and the inter-domain path identification notification table includes the AS number of the autonomous domain, the number of path identification PIDs, the path identification PID, the protocol forwarding information of the corresponding autonomous domain, and the forwarding port; The resource manager queries the service identifier in the service registry managed by it, and determines that the service provider corresponding to the service identifier is not in this autonomous region according to the flag bit Flag included in the entry corresponding to the service identifier. In the domain, the AS number corresponding to the next autonomous domain to the service provider is searched in the service registry, and the inter-domain path identification notification table is queried through the AS number to obtain the next AS number to the service provider. An inter-domain path identifier of an autonomous domain and related forwarding port information; The resource manager adds the inter-domain path identifier PID to the next autonomous domain of the service provider to the path identifier information at the end of the service request packet, and forwards the service request packet to the an egress border router, the egress border router decapsulates the domain routing protocol header of the service request packet, and forwards the service request packet to the next autonomous domain destined for the service provider through the relevant forwarding port information ingress border router. 5. The message forwarding method in the information center network according to claim 2, characterized in that, when the resource manager determines the service provider corresponding to the service identifier by querying its managed service registry Not within the autonomous domain, then query the inter-domain path identification notification table managed by it to obtain the inter-domain path identification and related forwarding port information to the next autonomous domain of the service provider, according to the inter-domain path identification and related The forwarding port information forwards the service request packet to the resource manager of the next autonomous domain destined for the service provider, including: The resource manager manages an inter-domain path identification notification table, and the inter-domain path identification notification table includes the AS number of the autonomous domain, the number of path identification PIDs, the path identification PID, the protocol forwarding information of the corresponding autonomous domain, and the forwarding port; The resource manager cannot find the service identifier in the service registry managed by it, and the autonomous domain where the resource manager is located is a Tier-1 autonomous domain, then send a search failure message to the service requester, and discarding the service request packet; if the autonomous domain where the resource manager is located is not a Tier-1 autonomous domain, then according to the policy of the autonomous domain where the resource manager is located, select the next-hop Provider autonomous domain of the service request packet, and pass Look up the inter-domain path identification notification table to obtain the PID and related forwarding port information leading to the Provider autonomous domain, encapsulate the PID to the Provider autonomous domain at the end of the service request packet, and send the service request packet Forwarding to the egress border router of the autonomous domain, the egress border router decapsulates the routing protocol header of the domain, obtains the interdomain path identifier PID to the Provider autonomous domain from the path identifier information in the service request packet, Query the inter-domain path identifier notification table according to the path identifier, obtain the forwarding information to the ingress border router of the Provider autonomous domain, and send the service request packet to the ingress border router of the Provider autonomous domain, in the In the above-mentioned Provider autonomous domain, the service request packet is sent from the ingress border router to the resource manager in its autonomous domain, and the resource manager queries its service registry. If the service identification information cannot be found, then according to the autonomous domain policy , and continue forwarding to its Provider autonomous domain until the service request packet is forwarded to the autonomous domain where the service provider is located or the Tier-1 autonomous domain. 6. the message forwarding method in the information center network according to claim 2, is characterized in that, described method also comprises: In the case of concurrent data packets, the resource manager uses a high-concurrency CuckooHashing algorithm to query the service identifier in the service registry. 7. according to the message forwarding method in the information center network described in claim 4 or 5, it is characterized in that, described method also comprises: The ingress border router of the autonomous domain where the service identifier is located encapsulates the domain routing protocol header for the service request packet, and sends the service request packet to the resource manager of the autonomous domain where the service provider is located, and the autonomous domain where the service provider is located After receiving the service request packet, the resource manager of the domain extracts the service identifier SID in the service request packet, queries the service identifier in the service registry it manages, and according to the corresponding SID in the service registry item The component identification NID information is used to route the service request packet, and forward the service request packet to the service provider; After receiving the service request packet, the service provider extracts the service identification SID and service behavior description SBD information in the service request packet, finds the corresponding data, generates a service data packet, and extracts the service request The path identification information at the end of the packet, the path identification information is encapsulated into the header of the service data packet, the domain routing protocol header is encapsulated for the service data packet, and the service data packet is sent to the egress border router of the domain, so The egress border router of the local domain strips the domain routing protocol header in the service data packet, and obtains the inter-domain path identification to the next autonomous domain of the service requester from the path identification information in the service data packet PID, querying the inter-domain routing table according to the path identifier, obtaining the ingress border router of the next autonomous domain, stripping off the inter-domain path identifier PID to the next autonomous domain, and sending the service data packet to the next autonomous domain The ingress border router of the next autonomous domain; After receiving the service data packet, the ingress border router of the next autonomous domain encapsulates the domain routing protocol header in the service data packet, and obtains the route to the next autonomous domain from the path identification information in the service data packet. The inter-domain path identifier PID of the domain, query the inter-domain routing table according to the path identifier, and obtain the egress border router of the domain going to the next autonomous domain, and send the service data packet to the egress border router of the domain; The egress border router of the local domain strips off the domain routing protocol header in the service data packet, obtains the inter-domain path identification PID to the next autonomous domain from the path identification information in the service data packet, and according to the The path identifier queries the inter-domain routing table, and obtains the ingress border router of the next autonomous domain, strips off the inter-domain path identifier PID to the next autonomous domain, and sends the service data packet to the next The ingress border router of the autonomous domain; And so on, until the service data packet is sent to the ingress border router of the autonomous domain where the service requester is located, at this time, the ingress border router sends the packet according to the NID information contained in the data packet to the access router of the service requester, and the access router sends the data packet to the service requester. 8. A message forwarding device in an information center network, characterized in that the device is set in an autonomous domain, and the device includes: an ingress border router, a resource manager and an egress border router; The ingress border router is configured to, after receiving the data packet sent by the service requester in the information center network, encapsulate the header of the local domain routing protocol on the data packet, and send the data packet to the resource manager of the local autonomous domain, The egress border router of the autonomous domain, or other network nodes of the autonomous domain; The resource manager is configured to parse the service request packet after receiving the service request packet sent by the ingress border router, and query the service registry managed by it according to the service identifier carried in the service request packet; When the service identifier is queried in the service registry managed by it, and the service provider corresponding to the service identifier is in the autonomous domain, then according to the service provider information corresponding to the service identifier in the service registry, the The service request packet is forwarded to the corresponding exit; When it is determined by querying the service registry managed by it that the service provider corresponding to the service identifier is not in the autonomous domain, then query the inter-domain path identifier notification table managed by it to obtain the route to the next autonomous domain of the service provider. An inter-domain path identifier and related forwarding port information, forwarding the service request packet to the egress border router according to the inter-domain path identifier and related forwarding port information; The egress border router is configured to strip the header of the local routing protocol in the service data packet, and obtain the inter-domain path identifier PID to the next autonomous domain from the path identification information in the service data packet, according to The path identifier queries the inter-domain routing table, and obtains the ingress border router of the next autonomous domain, strips off the inter-domain path identifier PID to the next autonomous domain, and sends the service data packet to the next autonomous domain An ingress border router of an autonomous domain; or obtain the inter-domain path identifier to the next autonomous domain of the service provider from the service request packet, query the inter-domain routing table according to the path identifier, and obtain the next The ingress border router of the autonomous domain, and sends the service request packet to the ingress border router of the next autonomous domain. 9. The message forwarding device in the information center network according to claim 8, wherein the resource manager comprises: The autonomous domain protocol header processing module is used to manage the source and destination address fields, the path identification field, and the message length field in the protocol header of the data packet, and the data packet includes a service request packet and a service registration packet; The inter-domain path identification negotiation and calculation distribution module is used for the negotiation and calculation of inter-domain path information, and maintains and updates the inter-domain path identification notification table information; The strategy library module is used to determine the negotiation and calculation strategy of inter-domain path information and the update search strategy of the service registry; The service registration package processing module is used for parsing and processing the arriving service registration package, extracting the registration information in the service registration package, and inserting or updating the service registry managed by it according to the extracted registration information; The service request packet processing module is used to analyze the arriving service request packet, first decapsulate the routing protocol header of the domain, extract the service identification SID information in the service request packet, and query the service identification in the service registry managed by it , according to the flag bit Flag contained in the entry of the service registry, it is determined that the service provider corresponding to the service identifier is in the autonomous domain, and then the data packet is processed according to the component identifier NID information corresponding to the SID in the service registry entry Routing, forwarding the data packet to the service provider corresponding to the component identification NID information; Inquire the service identifier in the service registry, and determine that the service provider corresponding to the service identifier is not in the autonomous domain according to the flag bit Flag contained in the table item of the service registry, then find out in the service registry Go to the AS number corresponding to the next autonomous domain of the service provider; query the inter-domain path identification notification table through the AS number, and obtain the PID and related forwarding port information leading to the next autonomous domain of the service provider ; Add the inter-domain path identifier PID to the path identifier information at the end of the service request packet, and forward the service request packet to the egress border router of the autonomous domain; The service identification cannot be found in the service registry, and the PID and related forwarding port information of the Provider domain leading to the autonomous domain are obtained by searching the inter-domain path identification notification table, and the connection information is encapsulated at the end of the data packet. The PID of the Provider domain forwards the data packet to the egress border router of the autonomous domain, and the egress border router decapsulates the routing protocol header of the domain, and forwards the service request packet to the egress border router through the relevant forwarding port information. The ingress border router of the Provider domain, the ingress border router encapsulates the domain routing protocol header to the service request packet, sends the service request packet to the resource manager of the Provider domain, until the service request packet forward to the ingress border router of the autonomous domain where the service provider is located. 10. A message forwarding system in an information center network, characterized by comprising: a plurality of autonomous domains, each of which includes the message forwarding device according to claim 8 or 9.