ES2344263T3 - METHOD FOR SELECTING A ROAD OF TRANSMISSION OF SERVICE DATA IN REAL TIME. - Google Patents

Abstract

Method for selecting a real-time service data transmission path on the basis of tag switching, where an independent carrier network control layer is established, comprising more than one carrier network resource manager (1001, 1002 , 1003, 1004, 1005) between a service control layer and a bearer network, a bearer network resource manager corresponding to a single domain and when a bearer network resource manager receives a connection resource request ( 1201, 1401, 1500) for a real-time service from the service control layer, the method comprising: from a source carrier network resource manager, which determines (1202, 1204, 1206, 1402, 1404, 1406 , 1408, 1411,1501) an inter-domain tag switching path, LSP, between each hop carrier network resource manager and a next hop carrier network resource manager, which sends (1203, 1205, 1403, 1405, 1502) a request for connection resource to the next hop bearer network resource manager, until the destination bearer network resource manager receives the connection resource request, said method being characterized by: from the destination bearer network resource manager, sending (1207, 1208, 1210, 1407, 1409, 1410, 1506) the inter-domain LSP and an intra-domain LSP of the carrier network resource manager in a connection resource response to the previous carrier network resource manager of jump, until a connection resource response is sent to the source carrier network resource manager, the source carrier network resource manager receiving the connection resource response, obtaining a global aggregation of LSP routes for the request for connection resource, which is from the carrier network resource manager at source to the carrier network resource manager at destination.

Description

Method to select a transmission path of real-time service data.

Technology field

The present invention relates to the technique of selection of routing routes, more particularly to a method to select and determine a data transmission path of service, in real time, in an Internet protocol network (IP)

Background of the invention

With the development of the Internet, several advanced network and multimedia system services have been offered. Since a real-time service is sensitive to some functions, such as network transmission delay and the so-called delay jitter , when there are services such as File Transfer Protocol (FTP), with high quality burst, or Hypertext Transfer Protocol (HTTP) with image files, etc., real-time services will be greatly affected. In addition, given that multimedia services occupy a wide range of bandwidths, the critical services to be guaranteed cannot be transmitted reliably in previous networks. Therefore, in order to ensure reliable transmission for critical services, several Quality of Service (QoS) techniques have been proposed. The Internet Engineering Working Group (IETF) has established numerous service models and mechanisms for the Quality of Service (QoS) requirements. Currently, a fairly recognized technique in this area is to adopt an Integrated Service (Int-Serv) model in the access area or edge area of a network, while a Differentiated Services (Diff-Serv) model is adopted in the Basic network configuration area.

The Diff-Serv (Differentiated Services) model guarantees quality of service (QoS) only by setting priorities, which makes the real effect unpredictable, even if the line utilization ratio is high. Consequently, an independent carrier network control layer is introduced for the Diff-Serv model of a Backbone network, a dedicated Diff-Serve QoS signaling mechanism is established as well as a dedicated resource management level to manage the resources of network topology for the Diff-Serv network. Said Diff-Service resource management mode is called the Diff-Service model with an independent carrier network control layer. Figure 1 illustrates said Diff-Service model with an independent carrier network control layer. As shown in Figure 1, a carrier network control layer 102 is located between a carrier network 103 and a service control layer 101 in this model. A Call Agent (CA), in the service control layer 101, is a service server, such as a software switch that can establish a software control function. The bearer network control layer 102 comprises one or more bearer network resource managers, which is responsible for configuring the management rules and the topology of the network, allocating resources for the request of a client's service bandwidth, controlling and managing all the resource managers of the carrier network to transmit the application request of the client's service bandwidth and its result, as well as the itinerary information assigned for the application of the mutual service, by way of signaling, for example, by controlling and managing the communications between the bearer network resource managers 1, 2 and 3. In the bearer network 103, each bearer network resource manager manages a given bearer network area, which is called the domain of management of the corresponding carrier network resource manager, for example, the carrier network resource manager 1 manages the management domain 105, the resource manager The carrier network 2 manages the management domain 106 and the carrier network resource manager 3 manages the management domain 107. The carrier network 103 includes an Edge Router (ER), a Border Router (BR) and a basic router 104, All ER, BR and basic router routers belong to the carrier network and are often referred to as Connection Nodes (CNs).

The carrier network control layer will determine a route for a user service when processing the Application of user service bandwidth and manager Carrier network resources will notify ER to send a flow of service according to the specified route. The routes in a Bearer network resource manager include two types: path of signaling and service route. The signaling route means a procedure of how each carrier network resource manager find the next one of the bearer network resource manager of jump. The service path means a procedure of how a Bearer network resource manager finds a Route Label switching (LSP) of appropriate carrier network, in accordance with the information of the service flow. A service route comprises an intra-domain route and a route inter-domains

Generally speaking, the carrier network send user service streams with a specified route, according to the route determined by the network control layer carrier Currently, an LSP is established along the route of the service flow that is specified by the control layer of carrier network as a way to reserve resources, using the Multiprotocol Label Switching (MPLS) technique or a LSP path of the "end-to-end" type is set using an explicit route mechanism based on the Protocol of Resource Reservation with Traffic Engineering extensions (RSVP-TE) or the Distribution Protocol of Restricted Route Labels (CR-LDP).

Currently, there are several systems for establishment of itineraries and allocation of resources of a manager of carrier network resources as follows:

A scheme is a technique to establish a itinerary according to operational needs, that is, when a calling party initiates a call, a resource manager carrier network acquires information from LSP, in real time, from a router of a carrier network, according to the topology of Current network and management rule, select an appropriate LSP route for the current call from the LSP information and issues this LSP once the current call is over. In this scheme, since a carrier network resource manager acquires LSP information directly from a carrier network and it required to reacquire and select the corresponding one again LSP route for each call, LSP information cannot be use repeatedly, which results in a high load of routing and poor performance of a network resource manager carrier

Another scheme uses the Agent model of Bandwidth of a Backbone Service Quality Network (QBone) experimental. Your network structure model is represented in the Figure 2. In this model, a bandwidth agent corresponding is set for each management domain of Diff-Serv, such as 1, 2 bandwidth agents and 3. The bandwidth agent is responsible for processing the bandwidth application requests from user hubs, service servers or responsible network maintenance and to determine whether or not to authorize the User bandwidth request according to the status of reserve of resources of the current network, the strategy configured thus as the Service Level Agreement (SLA) signed with the user. This bandwidth agent records several kinds of information static or dynamic, such as SLA configuration information, physical network topology information, information on router configuration and strategy information, User authentication information, reservation information for current resources, information on the occupation status of the network and also records route information so that it confirm the user's service flow path and location of the bandwidth agent downstream of the domains crossed.

The internal structure of the width agent of band, in Figure 2, is represented in Figure 3, in which includes: an inter-domain interface, which communicates with bandwidth agents and other levels of network control carrier A user service interface, which communicates with a service server, a hub / user and a device network maintenance; a strategy interface used for strategy control; a network management interface, a route information storage, which records the intra-domain route information in a manager carrier network resources; a data base; an interface inter-domain and a strategy service module simple. The modules inside the bandwidth agent They cooperate with each other. This bandwidth agent records several kinds of static or dynamic information, such as information from SLA agreement configuration, network topology information physics, configuration information and strategy information of the router (router), user authentication information, current resource reservation information, status information of network occupation and also records information on routes of so that the user's service flow path is confirmed and the location of the bandwidth agent located downstream of cross domains

In the network structure domain depicted in Figure 2, a router, in a carrier network, report route resources to a bandwidth agent in real time. The bandwidth agent acquires information about the appropriate route for the client's calling service to from the route resource information provided, select an itinerary for the customer's call service and Reserve a bandwidth resource on the route. This technique has inconveniences such as topology and selection are very complicated because a bandwidth agent directly manages resources and configuration information of all routers in this area; a route table needs to be updated frequently because a bandwidth agent needs record dynamic route information of the local area, which would give place to an unstable network reservation; the service path determined by a bandwidth agent, according to the dynamic route information of the local area, it is difficult to be identical with the actual shipping route of the service flow.

An alternative scheme is the Rich QoS presented by NEC Company. Your network structure model is represented in Figure 4, including a QoS 401 server as the component key, a strategy server 402, a catalog server 403 and a network management monitoring server 404 which are auxiliary with the QoS server. In this case, the QoS server will responsible for assigning a desirable carrier route for QoS service requests according to the topology and the resource condition of the carrier network. The server of strategy 402 sets parameters and configuration of relevant routers according to the information in configuration of strategies and the QoS 401 server, such as the management interface This catalog server 403 is a base of unified data and great content that is used to store Network device configuration information, information of the user and QoS information. The monitoring server of 404 network management is responsible for collecting information, such as the congestion status of routers and network links carrier, for QoS server reference when selecting a route for a service request.

In this scheme, the LSP information is configured on the QoS server. The QoS server acquires information  LSP suitable for customer calling service from LSP information and select an LSP for the service client caller and reserves bandwidth resources in the LSP. After a service server sends a wide request from band to the QoS server, the QoS server records the request for connection resources for this call, assign a carrier path for the service request according to the QoS requirements as well as the current topology and the current resource condition of the server network and then provides the result of the assignment to the service server. LSP information configured on the QoS server is divided into several levels based in the priority and the QoS server selects the information from High priority LSP for service requests with high priority and low priority LSP information for Service requests with low priority. However, if it exists a large number of service requests with low priorities and small number of service requests with high priorities, will lead to a congestion of the network in services with low priorities and inactive bandwidth for services with high priorities; therefore, this scheme is inflexible and of poor performance in routing.

In addition, this Rich QoS scheme is related to a fairly complex carrier network with a large number of routers Meanwhile, the QoS server and the server strategies notify so-called edge routers, using an explicit route setting technique MPLS LSP and a mode of establishing an "end-to-end" LSP extreme ", which results in poor expandability and scale Limited network. Therefore, this scheme is not applicable for "end-to-end" service needs in a network public

The above are several schemes to establish and allocate resources. Multiple algorithms can be adopted with regarding how to include the service route and the route of signaling on multiple itineraries and how to select a route adequate. The selection of the service itinerary and the route of Signaling can adopt the same or other algorithms. Without However, since each domain is simply managed by a certain carrier network resource manager, a manager of carrier network resources cannot know the conditions of LSP resources in other domains managed by other managers of carrier network resources, which will lead to factors uncertain for route availability and therefore will affect to network service performance.

For example, when a mode of adoption is adopted direct forwarding routing between a resource manager carrier network at source and a carrier network resource manager at destination, with reference to the network structure illustrated in the Figure 5, intra-domain routes and routes inter-domains are selected sequentially from a source ER to a destination ER, in the so-called "jump" mode to jump ", but this way of route selection is responsible that a route selection failure occurs. This is the reason whereby if a service flow is to be transmitted from ER2 to ER3, the four inter-domain LSP routes, that is,  LSP11, LSP12, LSP13 and LSP14, among network resource managers Carrier 1 and 2 are all selectable. However when LSP resources between BR3 and ER3 are exhausted inside the bearer network resource manager 2 while resources between BR4 and ER3 are in an inactive state, the resource manager of carrier network 1 will still select an LSP inter-domains, according to the algorithm of shared use of the route load, since it does not know the condition of occupation of LSP resources, within the domain managed by the carrier network resource manager 2. Yes LSP11 or LSP13 is selected, the route selection from the manager from carrier network resources 1 to the network resource manager Carrier 2 will be failed, leading to a routing failure full. Therefore, in the previous case, adopting only a way of shipping route selection can not get a reasonable allocation of resources and the main reason is that a only carrier network resource manager does not know the condition of use of LSP resources in domains managed by other bearer network resource managers. In addition, there may be some rule limitations for certain requirements of specified performance and services in domains managed by certain bearer network resource managers, for example some specified currents are assigned or prohibited for stage in a determined intra-domain LSP, which it can also lead to failures in the selection of routes. Without However, if the shipping route selection is simply replaced with the selection of forwarding route, the problem mentioned above. In this way, they cannot be satisfied adequately the operational needs of various services.

For another case, in the prior art, the route through which a service request will be transmitted as well As the bandwidth occupied on this route, they are calculated according with routing tables on each router. In this case, while route selection is implemented inter-domain, once the information is updated of a particular router, for example when a new service or a service is updated, which may result in reserve instability of the network. Meanwhile, the manager of Carrier network resources need to record route information dynamics in the local domain, which can lead to the problem of that will be updated, too frequently, the table of routing In this case, the network reservation will be unstable and it will also be difficult to guarantee the determined service route to be the same as the actual shipping route of the flow of service.

In the prior art, a document (Ibrahim Taner Okumus et al : "Configuring inter-domain LSP routes using bandwidth management points", XP - 001090208) discloses that bandwidth management points (BMP ) are required to manage intra-domain and inter-domain resources on the Internet, a way is offered to configure the inter-domain LSP route with the help of a BMP in an MPLS network over Diff-Serv; an extended single inter-domain bandwidth (SIBBS) agent signaling protocol is used to distribute the inter-domain tags and a BMP is also used to interact with the MPLS to establish the intra-domain LSP route and for provision of intra-domain traffic.

       \ vskip1.000000 \ baselineskip
    

Summary of the invention

In view of the foregoing considerations, An objective of the present invention is to disclose a method to select a service data transmission path in real time based on tag switching, which not only you can establish a routing in a network resource manager carrier, but also increase the success rate of the routing

       \ newpage
    

The present invention discloses a method to select a service data transmission path in real time based on tag switching, where a independent carrier network control layer, which comprises more of a carrier network resource manager, it is established between a service control layer and a carrier network, corresponding a bearer network resource manager to a single domain, and when a carrier network resource manager at source receives a request connection resource for a real-time service from the layer of service control, the method comprising:

from a carrier network resource manager in origin, determine a label switching path inter-domains between each network resource manager jump carrier and a next network resource manager jump carrier and record the label switching path inter-domains, sending a resource request for connection to the following network resource manager jump, until the destination carrier network resource manager receive the request for connection resources;

from the bearer network resource manager of destination, send the label switching path inter-domains and a switching path of intra-domain resource manager tags carrier network, in a connection resource response, to the manager of carrier network resources from the previous hop, until it is sent a connection resource response to the network resource manager carrier in origin; receiving the network resource manager bearer in origin the response of connection resource, obtaining with obtaining a complete aggregation of LSP routes for the connection resource request, which is from the resource manager from the carrier network at source to the carrier network resource manager in destination.

In addition, the present invention discloses a bearer network resource manager to select a route from real-time service data transmission based on the tag switching, where a network control layer independent carrier, comprising more than one resource manager of carrier network, is established between a control layer of service and a carrier network, corresponding to a single manager of carrier network resources to a single domain, the manager being Carrier network resources adapted to:

receive a connection resource request, for a real-time service, from the control layer of service, determining an inter-domain LSP between the carrier network resource manager and a resource manager of next hop carrier network;

send the inter-domain LSP and an intra-domain LSP of the network resource manager carrier to the previous jump carrier network resource manager, that is transported in the connection resource response.

The present invention is applicable for networks with any topology structure, including networks with several complicated structures and is easy to implant, maintain and manage.

Brief description of the drawings

Figure 1 illustrates a service model differentiated with an independent carrier network control layer in the prior art.

Figure 2 illustrates a network structure of a bandwidth agent model, in QBone network, in the prior art.

Figure 3 is a schematic diagram that illustrates the internal structure of the bandwidth agent represented in Figure 2.

Figure 4 illustrates the network structure of the Rich QoS scheme presented by NEC Company in the art previous.

Figure 5 is a schematic diagram that illustrates the routing by a network resource manager carrier

Figure 6 is a flow chart of the establishing routes between network resource managers carrier according to an example for better understanding of the present invention

Figure 7 is a schematic diagram that illustrates the interaction of messages between multiple managers of carrier network resources according to an example for the better Understanding of the present invention.

Figure 8 is a flow chart of the establishment of signaling path in a control layer of carrier network according to an example for better understanding of The present invention.

Figure 9 is a schematic diagram that illustrates the interaction of messages between multiple managers of carrier network resources during the process of establishing signaling routes according to an example for the better Understanding of the present invention.

Figure 10 is a schematic diagram that illustrates the establishment of signaling path in a layer of carrier network control, according to an example for the better Understanding of the present invention.

Figure 11 is a flow chart of the establishment of service path in a network control layer carrier, according to an example for better understanding of the present invention

Figure 12 illustrates a configuration flow route information and resource allocation by a manager carrier network resources according to an example for the better Understanding of the present invention.

Figure 13 is a schematic diagram that illustrates a route selection procedure in a control layer carrier network according to an example for better understanding of the present invention.

Figure 14 illustrates another configuration flow of route information and that allocates resources by a manager carrier network resources according to an example for the better Understanding of the present invention.

Figure 15 is a flow chart of route selection by a bearer network resource manager of according to an example of realization for a better understanding of the present invention

Figure 16 is a schematic diagram that illustrates the structure of the network for the implementation of networks of independent cross-route selection operations, according with an example for better understanding of the present invention.

Figure 17 is a flow chart of networks of independent cross-operation route selection agreement with an example for better understanding of the present invention.

Figure 18 is a schematic diagram that illustrates the constitutive structure of an IP data packet in IPv4 according to an example for better understanding of the present invention

Figure 19 is a flow chart of the method network route control according to an example for the better Understanding of the present invention.

Figure 20 is a flow chart illustrating a calling procedure between users in different areas of management, according to an example for better understanding of the present invention

Figure 21 illustrates a control procedure network route according to an example for better understanding of The present invention.

Figure 22 is a schematic diagram that illustrates a carrier network control layer in a manner of service route selection in accordance with this invention.

Figure 23 illustrates a procedure for establish an LSP in a carrier network under the conditions represented in Figure 22.

Figure 24 is a schematic diagram that illustrates an intra-domain route in another way of service routing in accordance with this invention.

       \ vskip1.000000 \ baselineskip
    

Detailed description of the invention

To make the objectives clearer, schemes Techniques and advantages of the present invention will be described with detail, hereafter, referring to the attached drawings and specific embodiments.

The basic idea of the present invention is: in the network topology structure, represented in Figure 1, after receiving a connection request, for a service in real time, sent by a call agent in a layer of service control, a carrier network resource manager in source sends the connection request to a resource manager of carrier network at destination sequentially from itself, select in an orderly manner and determine a route intra-domain, for real-time service, in a management domain, which corresponds to each resource manager of carrier network, and an inter-domain route, between adjacent management domains, which correspond to managers of adjacent carrier network resources, thus selecting an optimal itinerary route from the network resource manager carrier at source to the carrier network resource manager in destination.

In this case, the route from the manager carrier network resources at source to the network resource manager carrier in destination can also be referred to as a route of "end to end". An optimal route "end to end" it can be determined by means of a plurality of different ways routing, such as a backward routing with restricted forwarding, a jump-to-hop routing or a static configuration routing. The itinerary can be a tag switching path or other network path carrier

       \ vskip1.000000 \ baselineskip
    

The first example for a better understanding of this invention: backward routing and forwarding restricted

The main idea of this method of Routing is as follows. Each network resource manager carrier, including a carrier network resource manager in source, select a jump carrier network resource manager next, according to the destination address in a message from request and network topology structure after detect, by itself, that it is not a network resource manager carrier at destination, according to the request message from connection resource received, that is, after detecting the service flow in this request message, should not be transmitted to external networks through any management domain inside the ER of this carrier network resource manager and to then send the connection resource request message to the bearer network resource manager of the next hop and reserve  inter-domain route resources between itself and the carrier network resource manager of the next hop. Yes it is detected that he himself is the bearer network resource manager in destination, according to the resource request message from connection received, that is, by detecting that the service flow, In this request message, it needs to be transmitted to a network external through a specific internal management domain of the ER of this carrier network resource manager, a certain bearer network resource manager selects an input BR and an LSP inside the domain managed by this manager carrier network resources, according to the request message and then send a connection resource response message  which includes information about the BR input to the manager of carrier network resources from the previous jump. The resource manager The carrier network of the previous jump selects a specific LSP, inside your domain, according to this entry BR, retrieve inter-domain route resources reserved and also sends a resource response message from connection, which contains information about the input BR in the LSP, selected by itself, to your network resource manager carrier of the previous jump. The rest can be deducted by analogy, until the carrier network resource manager at source also receive a connection resource response message. TO then the source carrier network resource manager select an intra-domain LSP, using the same method, retrieve route resources reserved inter-domains and finally, send a call resource connection response message AC. In this way, a complete itinerary has been established.

Figure 6 is a flow chart of the establishment of signaling route between the managers of carrier network resources using the routing method of type of backward routing and with restricted forwarding.

In step 601, a network resource manager carrier at source receives a resource request message from connection from a CA, including the request message from connection information, QoS parameters, type of service, etc. In this case, the connection information comprises the ID of session, the IP address or domain name of a party that call, the IP address or domain name of a called party. The QoS parameters include a flow descriptor and information from bandwidth requirement

In step 602, after receiving the message connection resource request, a network resource manager carrier judges whether he is the network resource manager himself carrier in destination, that is, if the service flow in this request message, must be transmitted to an external network, through of a given internal management domain of the ER of this manager of carrier network resources. If so, step 605 will be executed; otherwise, step 603 will be executed.

In step 603, the network resource manager carrier selects a carrier network resource manager from the next jump, according to the destination address in the connection resource request message, and select an LSP for each BR selectable on the side of the network resource manager carrier of the next hop, when an LSP is selected intra-domain between himself and the resource manager of carrier network of the next jump, and reserves some widths of band in each selected LSP, that is, reserves resources of intra-domain route

In step 604, this network resource manager bearer sends a connection resource request message to the bearer network resource manager of the next hop and to Then, it will execute step 602.

In step 605, this network resource manager carrier judges whether he is the network resource manager himself carrier in origin. If so, step 610 will be executed; if not thus, step 609 will be executed.

In step 606, according to the BR of input, provided in the reply message, the manager of carrier network resources, which receives the response message from connection resource, retrieve bandwidths reserved for LSP routes that are related to edge routers (BR) other than the incoming BR provided between himself and the manager of bearer network resources of the next hop, which returns the reply message, that is, reserve route resources intra-domain

In step 607, this network resource manager carrier judges whether he is the network resource manager himself carrier in origin. If so, step 610 will be executed; if not thus, step 608 will be executed.

In step 608, this network resource manager bearer finds the connection resource request message corresponding received, according to the reply message of connection resource.

In step 609, according to the route of signaling between himself and the carrier network resource manager  of the next jump, as well as according to the information on selectable edge routers, provided in the connection resource request information, this manager carrier network resources select an LSP adequate intra-domain, inside the domain of self-management and then determines an input BR according to the selected intra-domain LSP. After determining the bearer network resource manager of the previous jump, according to the resource request message from connection, the carrier network resource manager returns a connection resource response message to the resource manager of carrier network of the previous jump, including the message of response information on the input BR selected by this bearer network resource manager and the information of path selection of carrier network resource managers located in the downward flow and then performs the return to execute step 606.

In step 610, the establishment is concluded of the route. More specifically, the network resource manager carrier at source sends a flow mapping order to the ER in the inside the local domain. In this case, the ER is the input ER of the route established above. The order includes QoS, current information, route information, etc. Manager of carrier network resources at source returns a message from connection resource response to the CA, after receiving a response to the flow mapping order from the ER in the Inside your domain.

In this case, the resource request message connection, in step 604, includes an aggregation of BR called restriction aggregation. Each BR in this aggregation of restrictions is an output BR of each LSP intra-domain selectable, between the manager of Current carrier network resources and the network resource manager carrier of the next jump and each output BR belongs to the bearer network resource manager of the next hop. In actually, this aggregation of restrictions provides a condition restrictive for the next carrier network resource manager. That is, the jump network carrier resource manager next you can only select one input BR from the LSP intra-domain from this aggregation of restrictions

Alternatively, in step 609, after select an input edge router (BR), on its own management domain, according to the request message from connection resource, this carrier network resource manager select an intra-domain LSP and then determines the carrier network resource manager from the previous step, according to the connection resource request message.

Figure 7 is a schematic diagram illustrating the interaction of messages between multiple carrier network resource managers. In this case, the carrier network resource manager 1 is the carrier network resource manager at source and the carrier network resource manager n is the carrier network resource manager at destination, the other network resource managers being carrier intermediate network manager resources.

When the carrier network resource manager in origin, e.g., the carrier network resource manager 1, judging that he himself is not the carrier network resource manager in destination, after receiving the resource request message from connection sent by a CA call agent, select a manager of carrier network resources of the next hop, according to the destination address in this connection request and structure of network topology. When an LSP is selected inter-domains between himself and the manager of bearer network resources of the next hop, such as the manager of carrier network 2 resources, if you exit these LSP routes they are different BR routers on the side of the network resource manager carrier 2, the carrier network resource manager 1 will notify, to the bearer network resource manager of the next hop, the presence of an aggregation constituted by the BR routers of departure of all inter-domain LSP routes available on the side of carrier network resource manager 2, e.g., an aggregation of restrictions, by means of a message of connection resource request. Meanwhile, the manager of carrier network resources 1 notifies the network resource manager carrier 2 for routing inter-domains and that entry BR of the LSP inter-domains, which is selected, must be a BR in the aggregation of restrictions cited above, when the manager of carrier network resources 2 conducts a routing intra-domain Then the manager of carrier network resources 1 select an LSP inter-domains for each BR selectable in the aggregation of restrictions, reserve some bandwidths in each LSP inter-domains selected, i.e. reservation inter-domain route resources and send a message request for connection resource to network resource manager carrier 2. After receiving the connection resource request sent by the carrier network resource manager 1, the manager of carrier network resources 2 determines that he himself is not the manager of carrier network resources at destination and select a manager bearer network resources of the next hop with the same method which was used by carrier network resource manager 1, is say select carrier network resource manager 3, reserve inter-domain route resources and send a message request for connection resource to network resource manager carrier 3. The rest of the process can be deduced by analogy. Is say, if it is determined that he is not the resource manager of carrier network at destination, after receiving a request from connection resource sent by the network resource manager jump carrier, each carrier network resource manager select a leap carrier network resource manager following with the same method used by the resource manager of carrier network 1, reserve some route resources inter-domains and send a request message from connection resource to the jump carrier network resource manager next.

When it determines that it is the carrier network resource manager at destination, according to the connection resource request message sent by the previous hop carrier network resource manager, the carrier network resource manager at destination, that is, the carrier network resource manager n , will select an input BR from the aggregation of restrictions provided in this message and determine an intra-domain LSP in accordance with the connection resource request message, return a response message connection resource to the carrier network resource manager of the previous hop, after determining the carrier network resource manager of the previous jump, and notify the carrier network resource manager of the previous jump of the presence of the input BR selected by middle of this reply message. According to the incoming BR, provided in the received connection resource response message, the previous hop carrier network resource manager, of the carrier network resource manager n , retrieves the inter-domain route resources reserved for LSP routes in relation to said BR routers, other than the incoming BR provided between itself and the carrier network resource manager and then judge whether it is the source carrier network manager itself. If not, you will find the connection resource request message corresponding to the received connection resource response message, returned by the carrier network resource manager n and then select an input BR and an intra-domain LSP route , using the same method used by the carrier network resource manager n, determines its previous jump carrier network resource manager and then returns a connection resource response message to its carrier network resource manager of the previous jump and notifies the carrier of network resources carrier of the previous jump the presence of the selected input BR by means of the reply message. The rest of the process can be deduced by analogy. That is, each carrier network resource manager, other than the carrier network resource manager at source, retrieves resources from inter-domain routes using the method described above, selects an incoming BR and an intra-domain LSP route, returns a connection resource response message to your previous hop carrier network resource manager, until a connection resource response message arrives at the source carrier network resource manager. After receiving the connection resource response message, the source carrier network resource manager retrieves the inter-domain route resources reserved for the LSP routes in relation to the BR routers other than the incoming BR provided between it. same and the next hop carrier network resource manager, which sends the connection resource response message, according to the input BR provided in the message and then selects an intra-domain LSP route and finally, ends the establishment of the complete itinerary. Next, the source carrier network resource manager sends a flow mapping order to the ER inside the local domain, and returns a connection resource response message to the CA after receiving a response to the mapping order. service flow from the intra-domain ER.

In the procedure described above, yes there is excessive information on selectable routes inter-domain or intra-domain, will lead to a complex calculation and increase overhead of the system. In this case, some restriction conditions, such as type of service, priority, some strategies of routing configured locally, some requirements of specified QoS as well as the operational status of the current network, such as the conditions of resource availability and flow of service can be added in order to simplify the calculation.

An example of concrete realization for a better understanding of the routing method indicated above is will describe, from now on, referring to Figure 5. In the assumption that the carrier network resource manager 1 manages the edge servers ER1 and ER2, while the manager of Bearer network resources 2 manages the ER3 edge servers and ER4 and that the address segments connected by ER1-ER4 are respectively 10.1.0.0-10.1.255.255, 10.2.0.0-10.2.255.255, 10.3.0.0-10.3.255.255 and 10.4.0.0-10.4.255.255, as represented in the Figure 5

Now, if a CA call agent sends a connection resource request message to the resource manager of carrier network 1, requiring the transmission of a certain service flow from ER2 through the network resource manager carrier 1 to ER3 managed by the network resource manager carrier 2, the carrier network resource manager 1 will determine that he himself is not the carrier network resource manager in destination, according to this resource request message from connection, that is, determines that this service flow should not be transmitted to an external network through any ER on its own domain and then select a network resource manager carrier of the next hop, such as the network resource manager carrier 2, according to the destination address in the message request and network topology structure. After select the jump carrier network resource manager next, carrier network resource manager 1 detects that This service flow can be transmitted from ER2 to BR1 or BR2 by means of an intra-domain LSP route and that the manager of carrier network resources 2 can receive the service flow transmitted by carrier network resource manager 1 using BR3 or BR4, that is, there are four LSP routes inter-domains selectable between the managers of Carrier network resources 1 and 2: LSP11, LSP12, LSP13 and LSP14. Without However, the four inter-domain LSP routes they present two outputs that are BR3 and BR4 managed by the manager of carrier network resources 2, more specifically, the output of LSP11 and LSP13 is BR3, while the output of routes LSP12 and LSP14 is BR4. In this case, the carrier network resource manager 1 select an inter-domain LSP route for each BR selectable according to the BR selectable on the side of the  carrier network resource manager 2, for example only select LSP11 and LSP12 or LSP11 and LSP14 or LSP12 and LSP13 or LSP13 and LSP14. Next, the carrier network resource manager 1 will reserve some bandwidths for each LSP route selected inter-domains, i.e. reservation inter-domain route resources and then sends a connection resource request message to the manager carrier network resources 2. This message includes an aggregation of restrictions (BR3, BR4) for the carrier network resource manager  2 to select a BR from aggregation. While I know performs the intra-domain route selection, the carrier network resource manager 2 must ensure that the BR of input of the selected LSP route comes from aggregation before aforementioned.

After receiving the connection resource request message sent by the carrier network resource manager 1, according to this message, the carrier network resource manager 2 determines that the service flow to be transmitted must be transmitted to an external network through an ER inside the domain managed by itself, ie ER3, and detects that in the domain under its management, there is an intra-domain LSP route selectable between BR3 and ER3 and an selectable intra-domain LSP route between BR4 and ER3. Next, the carrier network resource manager 2 can select BR3 or BR4 as the input BR of the intra-domain LSP route, according to a certain condition or algorithm. If BR4 is selected and an intra-domain LSP route from BR4 to ER3 is determined, the carrier network resource manager 2 sends a connection resource response message to the carrier network resource manager 1 and provides BR4 information to the manager of carrier network resources 1 by means of this message. According to the result of the previous selection, the carrier network resource manager 1 recovers the bandwidths reserved for all LSP routes, whose output BR is BR3, determines an output BR of an LSP route inside its own domain, select an intra-domain LSP route from ER2 to this exit BR, thus ending the establishment of the complete route. And then, the bearer network resource manager 1 sends a flow mapping order to ER2 within its own domain, including the order information such as QoS, flow information and itinerary. After receiving a response for the service flow mapping order from ER2, the manager of
Bearer network resources 1 returns a connection resource response message to the CA call agent.

In the previous procedure, if the manager of carrier network resources 2 select BR3 as the input BR of the intra-domain LSP route and determines an LSP route intra-domain from BR3 to ER3, the resource manager  bearer network 2 a connection resource response message to bearer network resource manager 1 and provide information from BR3 to carrier network resource manager 1 by means of this message. According to the previous selection result, the carrier network resource manager 1 recovers bandwidths reserved for all LSP routes whose departure BR is BR4, determines an output BR of an LSP route inside its own domain and select an LSP route intra-domain from ER2 to this output BR, finishing, in this way, the establishment of the global itinerary. TO then, the bearer network resource manager 1 sends a flow mapping order to ER2 within its own domain, including order information such as QoS and itinerary. After receiving a response to the flow mapping order of ER2 service, carrier network resource manager 1 returns a AC resource connection response message.

Although the example described above, for better understanding of the invention, is described by taking a service flow transmission procedure between two managers of carrier network resources, which respectively include two BR routers as an example, the present example for the better understanding of the invention is also applicable for a service flow transmission procedure between two or more of two carrier network resource managers that include, respectively one or more BR edge routers.

In addition, if there is a plurality of LSP routes inter-domains between two network resource managers carrier, such as carrier network resource managers 1 and 2, and the input BR of each LSP route inter-domains is on the manager side of carrier network resources 1, while the output BR is in the carrier network resource manager side 2, you can select one or more of an inter-domain LSP route for each selectable output BR and some widths are reserved of band for each selected LSP, that is, resources are reserved of inter-domain routes. In the practical application, the way described above can lead to a great amount of waste of inter-domain resources, and thus, the carrier network resource manager 1 can select an optimal aggregation of incoming BR routers, in the side of the carrier network resource manager 1, according to a certain algorithm, so that an aggregation of BR routers output LSP routes inter-domains, which corresponds to all BRs of entry into the optimal aggregation described above, includes all Outbound BR available on the network resource manager side carrier 2.

The present routing scheme provides a way of routing backward type and With restricted forwarding. In detail, a network resource manager carrier will reserve some route resources inter-domains when selecting an LSP route inter-domains and informs the exit BRs of all LSP routes available to a following resource manager jump carrier network. After selecting an LSP route, the Next jump carrier network resource manager will inform the Output BR selected for the network resource manager previous jump carrier. Then the resource manager from previous jump carrier network retrieves route resources reserved for said LSP routes that relate to others BR routers. This method of reserving route resources inter-domains beforehand and determine, to then the intra-domain route e inter-domains allows full use and reasonable resources of each network resource manager carrier and increase the success rate of routing.

Adopting the merge mechanism forward and backward routing and, for that purpose, reserve route resources in advance inter-domains and then determine the route inter-domain and inter-domains, the Current routing method can make full and reasonable use of the resources of each carrier network resource manager, guarantee the reliable establishment of the route, enabling this mode, reasonably use network resources and increase the efficiency and success rate of routing. The method of Current routing is applicable for networks of any Topology structure and is easy to implement, maintain and manage.

       \ vskip1.000000 \ baselineskip
    

The second example for a better understanding of the invention: "jump-to-jump" routing way

The present routing scheme provides a "jump-by-hop" routing method in a carrier network, being its fundamental idea: under the condition of that each bearer network resource manager, in a layer of carrier network control, just know the structure of topology of your own management domain or under the condition of that each bearer network resource manager, in a control layer of carrier, only knows its adjacent CN nodes, the manager of carrier network resources or the CN will only select and will determine a following network resource manager carrier of jump or a next jump CN node.

       \ global \ parskip0.900000 \ baselineskip
    

Figure 8 is a flow chart of establishment of signaling path in a control layer of carrier network using the "jump to routing method jump "from the current example for better understanding of the invention.

In step 801, a network resource manager carrier at source receives a resource request message from connection from a CA call agent, including the message from request connection information, QoS parameters, type of service, etc. In this case, the connection information includes the Session ID, IP address or domain name of a calling party as well as the IP address or domain name of a called party The QoS parameters include a descriptor of the flow and information of bandwidth requirements.

In step 802, the network resource manager current carrier, which receives the resource request message from connection, judge whether the connection between itself and the device that Send this request message is available; if it is not available, step 805 will be executed; otherwise, it will run step 803. Unavailability means the connection between the Current carrier network resource manager and resource manager of previous jump carrier network is not available due to the lack of network resource manager resource availability Current carrier, its own functional anomaly or other reasons.

In step 803, according to the address of destination in the connection resource request message, the Current carrier network resource manager judges whether he himself is the carrier network resource manager at destination and if so, it will execute step 807; otherwise, the stage will be executed 804

In step 804, according to the address of destination in the connection resource request message, the Current carrier network resource manager determines the following jump carrier network resource manager and send a message from connection resource request to the following resource manager selected carrier network. Then the stage will run 802.

In step 805, the network resource manager current carrier, which receives the resource request message from connection, return a connection resource rejection message to the carrier network resource manager, which sends this message from connection resource request.

In step 806, according to this message from connection resource rejection, the network resource manager current carrier, which receives the resource rejection message from connection, find the corresponding request message from connection resource received. Then the stage will run 804

In step 807, according to the message of connection resource request, the network resource manager Current carrier returns a resource response message from connection to the carrier network resource manager, which sends this request message

In step 808, the network resource manager current carrier, which receives the resource response message from connection, judge if he is the network resource manager himself carrier in origin. If so, step 810 will be executed; if not thus, step 809 will be executed.

In step 809, according to the message of connection resource response the network resource manager current carrier finds the resource request message from corresponding connection received. Then, the Stage 807

In step 810, the establishment is completed of the signaling route.

Once the signaling route is established, from agree with the connection resource request message before described, sent by the CA, the bearer network resource manager at source it will send a flow mapping order to the incoming ER corresponding, within its own domain, including said order the session ID, current information, parameters of QoS, flow descriptor and route label stacking complete.

The mechanism described above, in which a manager of carrier network resources sends a response message from connection resource to the jump carrier network resource manager Previously, sequentially, can be referred to as a mechanism confirmation and the mechanism described above in which a manager of carrier network resources sends a resource rejection message from connection to the previous jump carrier network resource manager sequentially and the carrier network resource manager returns to select a following carrier network resource manager of jump, can be called a recoil mechanism. Adding said  recoil mechanism and a confirmation mechanism to the method of "jump-to-jump" type routing, the present example for a better understanding of the invention you can maximize the connection establishment reliability and save resources from the net. Of course, an unrestricted recoil of so that the number of setbacks or a certain limitation of the time interval can be preset in order to guarantee the efficiency of consultation of the type "jump to jump". For example, if the number of setbacks exceeds the number preset, or if a particular network resource manager carrier receives a connection resource rejection message, but find that the time interval between this rejection message received and the corresponding connection request message exceeds the preset time interval limitation, the Current routing will be considered as failure and the Next routing. Or, an indicator of recoil and said indicator can be used for recoil by just one time.

       \ global \ parskip1.000000 \ baselineskip
    

In practical application, some networks, such Like reticular networks, they have a complex structure. In the routing procedure described above, in order to avoid the carrier network resource manager already selected is reselected on the routes also selected as the following bearer network resource manager jump a certain carrier network resource manager on this route, you can establish a global aggregation of network resource managers carrier that is sought. In this case, step 804 may comprise in addition: before sending a resource request message from connection to the next jump carrier network resource manager, the current carrier network resource manager judges whether the following selected jump carrier network resource manager is in the aforementioned global set of network resource managers carrier wanted; if so, the network resource manager Current carrier leaves the next network resource manager selected jump carrier and reselect a next manager of jump carrier network resources in step 804; if not thus, the current carrier network resource manager adds its own information to the global set of network resource managers bearer wanted and then send a request message connection resource to the following network resource manager selected carrier.

Figure 9 is a schematic diagram that illustrates the interaction of messages between multiple managers of carrier network resources, according to the present example to Better understanding of the invention. In Figure 9, the manager of carrier network resources 1 is the network resource manager carrier at source, the carrier network resource manager n is the carrier network resource manager at destination and others are intermediate carrier network resource managers.

When the carrier network resource manager in origin, that is, the carrier network resource manager 1, receives a connection resource request message sent by an agent AC, judge whether the connection between itself and the transmitting end of This request message, that is, the CA, is available from according to its own operational state. After finishing that he same is not the carrier network resource manager in destination, of According to this request message, the network resource manager Bearer 1 selects a following network resource manager carrier according to the information such as type of service, resource availability status, priority, strategy local configuration routing as well as the address of destination in the connection resource request message received and then send a resource request message from connection to the next hop carrier network resource manager selected, that is, the carrier network resource manager 2. After receiving the connection resource request message sent by carrier network resource manager 1, in accordance with its own operational status, such as unavailability of resources, its own functional anomaly or other reasons, the resource manager of carrier network 2 determines that the connection between itself and the transmitting end of this request message, that is, the bearer network resource manager 1, not available and to then return a connection resource rejection message to the bearer network resource manager 1. According to the message connection resource rejection, returned by the manager carrier network resources 2, the carrier network resource manager 1 reselect a following carrier network resource manager of jump and send a connection resource request message to next jump carrier network resource manager reselected, that is, the carrier network resource manager 3. The rest of the process can be deduced by analogy. After receive a connection resource request message sent by your previous jump carrier network resource manager, each intermediate carrier network resource manager will judge whether the connection between itself and the bearer network resource manager of Previous jump is available according to your own situation. If a particular intermediate carrier network resource manager determines that the connection between himself and the resource manager of previous jump carrier network is not available according to your own situation, will send a resource rejection message from connection to the previous jump carrier network resource manager. The previous jump carrier network resource manager will reselect a following carrier network resource manager from jump according to the connection resource rejection message returned and will send a connection resource request message to the next carrier network resource manager selected. If a certain intermediate carrier network resource manager determines, after receiving a resource request message from connection, sent by your carrier network resource manager previous jump, that the connection between himself and the manager of previous carrier network resources is available with its own situation and that he himself is not the network resource manager carrier at destination, according to this request message, select a following carrier network resource manager from jump, according to information such as type of service, resource availability status, priority, strategy routing configured locally as well as the address of destination in the connection resource request message received and then you will send a resource request message from connection to the next hop carrier network resource manager selected.

After the carrier network resource manager at destination, that is, the carrier network resource manager n, you receive a connection resource request message, sent by your previous jump carrier network resource manager, will determine that the connection between himself and the resource manager Previous jump carrier network is available. When he carrier network resource manager n determines that he himself is the carrier network resource manager at destination, according to this request message, will return a resource response message for connection to the bearer network resource manager, which you have sent this request message, that is, the network resource manager previous carrier of the carrier network resource manager n. He previous jump carrier carrier network resource manager carrier network resources n determines that he himself is not the manager of carrier network resources at source, according to the message of connection resource response received and then find the connection resource request message corresponding received, according to the reply message of connection returned by the carrier network resource manager n and a then returns a resource response message from connection to the carrier network resource manager, which you have sent this connection resource request message, that is, at previous jump carrier carrier network resource manager Current carrier network resources. The rest of the process can be deduct by analogy. Each carrier network resource manager intermediate returns a connection resource response message to your previous jump carrier network resource manager, of according to the method described above. When the resource manager carrier network at source, that is, the network resource manager carrier 1, receives a connection resource response message returned by your next carrier network resource manager jump, you will find the connection resource request message corresponding received, according to this reply message, and then returns a resource response message from connection to the CA, which has sent this resource request message of connection. In this way, the entire process is concluded to Establish a signaling route.

In Figure 9 it can be seen that, each carrier network resource manager must provide a message from connection resource response or a resource rejection message connection for each connection resource request message received and that each bearer network resource manager sends a connection resource response message or rejection message connection resource to your carrier network resource manager previous jump only after receiving the reply message connection resource or resource rejection message connection from your jump carrier network resource manager. TO through this confirmation mechanism and the mechanism of recoil, the reliability of the allocation of resources is assured  and waste of resources is avoided. Figure 10 is a diagram schematic illustrating the establishment of signaling route in a carrier network control layer, in accordance with the present example. In this example, the method of establishing a route for Signage is as follows.

When you receive a resource request message Connection sent by a CA, the network resource manager carrier 1001 determines that he himself is not the resource manager of carrier network at destination, according to this request message and then select all network resource managers carrier that can be selected as a following manager jump carrier network resources, according to the address of destination in this request message as well as the topology of others bearer network resource managers adjacent to the manager carrier network resources 1001. As depicted in Figure 10, since the carrier network resource manager 1002 and 1004 are adjacent to the carrier network resource manager 1001, the manager of carrier network resources 1001 takes both resource managers from carrier network 1002 and 1004 as the following resource managers selectable jump carrier network and then select carrier network resource manager 1002 or 1004 as the next jump carrier network resource manager, of agreement with information such as type of service, status of resource availability, priority and strategy of routing with local configuration. In the present example, assuming the following network resource manager jump carrier selected by the network resource manager carrier 1001 is the carrier network resource manager 1002, the carrier network resource manager 1001 sends a message from connection resource request to the network resource manager carrier 1002. The request message includes information such such as session ID, fivefold, type of service, QoS parameters and address of the exit BR of the LSP route inter-domains selected and used to make the carrier network resource manager 1002 perform a routing intra-domain Similarly, the manager of carrier network resources 1002 determines that he himself is not the carrier network resource manager at destination, according to the connection resource request message sent by the manager of carrier network resources 1001, so that you also follow the rule described above to select all resource managers carrier network that can be selected as the next manager of jump carrier network resources. In this case, the managers of selectable carrier network resources are resource managers of carrier network 1003 and 1005, as shown in Figure 10 and then the carrier network resource manager 1002 select carrier network resource manager 1003 or 1005 as the next jump carrier network resource manager. At present example, assuming that the resource manager of carrier network 1002 selects the network resource manager carrier 1003 as the next carrier network resource manager jump and send a connection resource request message to same. According to the connection resource request message sent by the carrier network resource manager 1002, the manager of carrier network resources 1003 determines that he himself is only the carrier network resource manager at destination and to then returns a resource response message from connection to carrier network resource manager 1002. So similar the carrier network resource manager 1002 returns a connection resource response message to the resource manager of carrier network 1001; carrier network resource manager 1001 returns a connection resource response message to the CA and by Finally, the complete procedure of establishing the route of signaling. Then, according to the message of connection resource request received above, the manager of carrier network resources 1001 sends a flow mapping order of service to ER 1006, which is a local domain entry, including the order the session ID, flow information of service, QoS parameters, flow descriptor and stacking of full path tags.

In the previous procedure, if a certain carrier network resource manager, in this signaling path, detects that the connection between himself and his resource manager previous jump carrier network is not available due to the lack of availability of resources, its own functional anomaly or other reasons, this carrier network resource manager will send a connection resource rejection message to your resource manager of previous jump carrier network, notifying the manager of previous jump carrier network resources the selection of another carrier network resource manager, on selectable routes, as the next jump carrier network resource manager. By example, in the example cited above, if the resource manager of carrier network 1002 detects its own functional anomaly, or detects that the resources in the LSP between himself and the resource manager of carrier network 1001 are depleted, the network resource manager carrier 1002 will send a connection resource rejection message to carrier network resource manager 1001 and the latter can reselect a following carrier network resource manager of jump, according to this rejection message. In the previous example, carrier network resource manager 1001 can select carrier network resource manager 1004 as the next jump carrier network resource manager. The rest of the process can be deduced by analogy, being able to establish the signaling route through the red route, from the manager carrier network resources 1004 to the network resource manager carrier 1003, through the carrier network resource manager 1005

The mechanism described above, in which a carrier network resource manager sends a rejection message connection resource to the carrier network resource manager of previous jump, sequentially, is called a mechanism of recoil, which can maximize establishment reliability of connection. In practical application, they can be preset several setbacks or a certain limitation of the interval of time in order to ensure the efficiency of type queries jump by jump

The above describes the procedure of establish a signaling route by adopting the method of "jump-to-jump" type routing according to the present example. The principle and mechanism of this method are also applicable for routing intra-domain of a particular resource manager carrier network in your managed domain, being the only one difference that each carrier network resource manager completes, independently, your intra-domain routing instead of implementing a message interaction between bearer network resource managers. In a domain managed by a carrier network resource manager, each CN node stores its own routing table. Therefore, in the method given to know by the present example, each network resource manager carrier simulates a routing table for each CN in its domain, that is, the carrier network resource manager obtains the routing information stored by CN and stored in it same. Next, a carrier network resource manager performs intra-domain routing according with the routing table of each CN. While doing the intra-domain routing, each manager of Carrier network resources can use a routing method of type "jump to jump" to select routes between several CN connection nodes and select an aggregation of LSP routes to transport this service flow.

Figure 11 is a flow chart of the establishment of service routes in a network control layer carrier, in accordance with the present example. Specific stages They are as follows.

In step 1101, the network resource manager carrier, which is conducting the routing intra-domain, judge if he is the manager of carrier network resources at source. If so, this manager Carrier network resources find an input ER, in the inside your domain, according to the address information IP in the connection resource request message received from a CA, and take the input ER found as the CN of input and add information from this input ER to an aggregation of routers sought. Otherwise, the resource manager of Current carrier network finds an incoming BR according to the information contained in the resource request message from connection received, take the input BR found as CN of input and add information from this input ER to the aggregation of Routers sought. In this case, any LSP intra-domain comprises an incoming CN and a CN of exit.

In step 1102, an LSP is selected intra-domain according to the incoming CN current. This intra-domain LSP can be selected randomly, or according to the same conditions such as user address, activation status of the LSP route, routing priority, bandwidth requirements, etc.

In step 1103 it is judged whether the router selected at the other end, that is, the output CN, is a BR or an ER within the domain managed by the manager of Current carrier network resources. If so, this LSP intra-domain is selected successfully and it will execute step 1106; otherwise, the stage will be executed 1104.

In step 1104, it is judged whether the exit CN cited above is already added to the aggregation, cited above, of Routers wanted. If so, the selection of the LSP route previously selected and step 1102 will be executed in which an LSP is reselected; otherwise, the stage will be executed 1105

In step 1105, the output CN in the stage 1103, is taken as input CN and step 1102 will be executed.

In step 1106, the procedure is completed. of establishing a service route and the flow will be terminated of current routing.

In short, the type routing method "jump to jump", according to the present example, you can adopt to select the signaling path inter-domains and service routing intra-domain or the method of adopting "jump-to-jump" routing in accordance with this example to select the signaling path while use other algorithms to select the service path or it adopt the "jump-to-jump" routing method, okay with the present example, to select the service route, while other algorithms are used to select the route Signaling. Now, the routing method is adopted "jump to jump", according to the present example, to select the intra-domain route while they use other algorithms to select the route inter-domains and vice versa. The schemes of Specific routing can be determined according to the network situation and service requirements.

Using the application mechanisms and "jump to jump" confirmation as well as the recoil method and reselection, with the current routing scheme, is guaranteed the allocation of resources and improved the inter-domain routing success rate e intra-domain for each network resource manager carrier in the carrier network control layer. Adopting this routing method, since there is a mechanism for setback and reselection in this method, even when a functional anomaly for a particular node or link in the network, this functional anomaly will exert very little influence on Provide exact route information. In addition, the method of "jump-to-jump" routing, disclosed herein For example, it has no special requirements for the structure of the network and is applicable for networks of any structure of topology, which includes several complex networks.

       \ vskip1.000000 \ baselineskip
    

The third example: static routing way

The basic idea of the present example is how follow. The route information is pre-configured in a bearer network resource manager statically or using a dedicated database. A network resource manager carrier acquires the configured route information when activate and select an appropriate route from the information in the pre-configured route, after receiving a connection resource request or a resource response from connection, so that the establishment is completely separated and The route selection. In this case, the route information configured can be inserted into a route table with inbound and outbound routers as column elements and Row elements, respectively. The table can be a table of routes that indicates the relationship between ER and BR or be a table that indicate the relationship between BR routers.

In the present example, data transmission it is done through a network based on the model "Diff-Serv" depicted in Figure 1. The route, in the carrier network control layer of this model, includes the signaling path between network resource managers carrier, that is, inter-domain route and route of service between CN connection nodes, e.g. route intra-domain As depicted in Figure 1, the carrier network resource manager 1 is the resource manager of carrier network at source and carrier network resource manager 2, which can be called carrier network resource manager intermediate, it is the carrier network resource manager through the which passes the current request not being the network resource manager  carrier 1 or the carrier network resource manager at destination and the carrier network resource manager 3 is the resource manager of carrier network at destination. Management domains 105, 106 and 107 are respectively managed by the network resource managers carrier 1, 2 and 3. There may be several resource managers of intermediate carrier network and there may also be none. At In this example, there is only one network resource manager intermediate carrier.

In the present example, you must preconfigure the route information required by the network resource manager carrier In this case, the itinerary information includes LSP information and route information. Also in this case, the LSP information indicates the itinerary information specific and route information indicates a kind of information restriction for service routing, which indicates the corresponding relationship between the LSP identifier and each of the user's IP address, flow information, information of the bandwidth and service type information. Since the This example mainly refers to the information of LSP, will be illustrated, in future, in terms of LSP information.

There are two ways to preconfigure the LSP information as follows.

One way is to configure, statically, the LSP information in a carrier network resource manager, is that is, a network administrator statically configures the LSP information in a carrier network resource manager. The LSP information, statically configured, includes LSP route information, which is already established in the network of carrier, and information of LSP routes that are not yet established. If the LSP is not established, a resource manager bearer network sends a request to a CN connection node in the carrier network After receiving this request, the CN node establishes an LSP in the carrier network, in accordance with the LSP information contained in the request and returns a response indicating a successful establishment or manager of Carrier network resources transmits this LSP information configured to the CN node and the CN node establishes the LSP. If LSP is set successfully, the CN node will return a response indicating said satisfactory establishment; otherwise, the CN will return a fault message requesting to delete this information from LSP configured.

The other way is to use a database dedicated to configure LSP information. In this method, it establish a dedicated database of itinerary information, where you configure the information of the LSP routes that are already established in the carrier network and route information LSPs that are not yet established and the LSP information provided in real time by a CN in the carrier network is receives and stores in this database information of the itineraries

If the information database of the itineraries stores information on routes not established in the carrier network, will send a request to the CN in the network of carrier After receiving this request, the CN establishes a LSP in the carrier network according to the LSP information contained in the request and returns a response indicating a successful establishment or carrier network resource manager transmit this configured LSP information to the CN and the CN set the LSP. If LSP is successfully established, the CN will return a response indicating that establishment satisfactory; otherwise, the CN will return a fault message requesting to delete this configured LSP information.

To clearly describe the information in LSP preconfigured, the contents of the LSP route information are present in the form of a matrix table at present example.

The LSP information includes information from Intra-domain LSP of the network resource manager Current carrier and LSP information inter-domains between the network resource manager Current carrier and the next carrier network resource manager of jump. Intra-domain LSP information is stores in an LSP route matrix table intra-domain and LSP route information inter-domains is stored in a matrix table of LSP inter-domains.

After receiving a resource request from connection or a connection resource response, a manager carrier network resources select the appropriate LSP information for the user's call service based on the information LSP configured and reserves bandwidth resources in the LSP For this call service. Figure 12 illustrates a flow of configuration of itinerary information and assignment of resources by a carrier network resource manager. Is according depicted in Figures 1 and 12, the procedure of selecting an itinerary from a carrier network resource manager at source to a carrier network resource manager in destination is like follow.

In step 1201, a CA receives a request from call sent by a user and sends a resource request for connection to the bearer network resource manager 1. The request for connection resource includes connection information, parameters of QoS, type of service, etc. The connection information includes the Session ID, IP address or domain name of the party caller as well as the IP address or domain name of the called party The QoS parameter includes the flow descriptor e Bandwidth requirements information.

In step 1202, after receiving the connection resource request sent by the call agent CA, carrier network resource manager 1 selects, according with the IP address or domain name of the calling party, in this connection resource request, an ER router corresponding to the IP address or domain name of the calling party from management domain 105 and take this ER as input router of the global LSP route, meaning usually the input router a center router calling end, or a tandem central router calling, in this case it is the ER1 router. In the present example, the specific information content of the LSP intra-domain in management 105 can be verified from the matrix table illustrated in table 1. In this case, ER3 and BR5 are not presented in Figure 1.

TABLE 1

one

It can be seen from table 1 that There are three LSP routes that take ER1 as an input router: LSPa, LSP1 and LSP, from which one with a special method, comprising: use the charging principle shared, polling polling or priority way configured according to the needs of the service. In this In this case, the principle of shared load means equalizing loads of all LSP routes and preferably select the LSP with less loads; polling polling means select a selectable LSP in order; use priority configured, according to the requirement of the service is select the corresponding LSP according to the requirements specials based on service priority.

In the event that LSP1 is selected and the LSP1's output router is BR1 and then the resources of Bandwidth are reserved in LSP1 according to the parameters of QoS in the connection resource request.

The carrier network resource manager 1 takes BR1 as an LSP route entry router inter-domains, between management domains 105 and 106 and select an inter-domain LSP route between management domains 105 and 106 from a matrix table of intra-domain LSP routes illustrated in Table 2, in which BR6 and BR7 are not represented in Figure 1. This table Matrix of inter-domain LSP and the matrix table Intra-domain LSP can be integrated into a single table.

TABLE 2

2

It can be seen from table 2 that There are two LSP routes that take BR1 as an incoming router. LSP3 and LSP10 and then the corresponding LSP is selected adopting the principle of shared load or the way of polling interrogation or priority set according to The service needs. in the event that it is selected LSP3 and the output router of LSP3 is BR2 and some are reserved bandwidth resources in LSP3, according to the parameters of QoS, in the connection resource request.

In step 1203, the network resource manager bearer 1 sends a connection resource request to the manager carrier network resources 2. The connection resource request includes the original QoS parameters, the type of service and connection information. In this case, information about the connection also includes the address of the network resource manager carrier 2 and that of BR2.

In step 1204, the network resource manager Bearer 2 receives the connection resource request sent by the carrier network resource manager 1 and take BR2, in this connection resource request, as input router for Intra-domain LSP of management domain 106 and a then select an intra-domain LSP from management domain 106 from the LSP route matrix table intra-domain network resource manager carrier 2 with the same method that was used in step 1202. In the event that LSP16 is selected and the router LSP16 output is BR3, and some resources are reserved for width of band in LSP16, according to the QoS parameters in the request of connection resource.

The carrier network resource manager 2 takes BR3 as the input router of the LSP inter-domains between management domains 106 and 107 and select an inter-domain LSP among the management domains 106 and 107 from the matrix table of inter-domain LSP routes of the resource manager carrier network 2 with the same method that was used in the stage 1202. In the event that LSP17 and the router are selected LSP17 output is BR4 and some resources are reserved width of band in LSP17, according to the QoS parameters in the request of connection resource.

In step 1205, the network resource manager bearer 2 sends a connection resource request to the manager carrier network resources 3. The connection resource request includes the original QoS parameters, the type of service and connection information. In this case, information about the connection also includes the address of the network resource manager carrier 3 and that of BR4.

In step 1206, the network resource manager Bearer 3 receives the connection resource request sent by the carrier network resource manager 2 and take BR4, in this connection resource request, as input router for Intra-domain LSP of management domain 107 and a then select an ER corresponding to the IP address or domain name of the called party in the management domain 107 and take this ER as the output router of the entire LSP, said outbound router usually refers to a so-called router "end office" or a so-called central router in central in tandem, in this case it is ER2. The network resource manager Carrier 3 takes ER2 as the output router of the LSP intra-domain management domain 107 and select an intra-domain LSP domain from management 107 from the matrix table of LSP intra-domain network resource manager carrier 3, with the same method that was used in the stage 1202. In the event that LSP18 is selected and reserved some bandwidth resources in LSP18, according to the QoS parameters in the connection resource request.

In step 1207, the network resource manager carrier 3 returns a connection resource response to the manager of carrier network resources 2, including the resource response connection information of BR4 and LSP18.

In step 1208, the network resource manager bearer 2 receives the connection resource response returned by the carrier network resource manager 3 confirms the resources of bandwidth reserved by the network resource manager carrier 2 for this request and sends a resource response from connection to the bearer network resource manager 1. The response of connection resource includes information from BR2, information from LSP18 in the connection resource response returned by the manager of carrier network resources 3, information of LSP16 and LSP17 selected by the carrier network resource manager 2.

In step 1209, the network resource manager Bearer 1 receives the connection resource response returned by the carrier network resource manager 2 confirms the resources of bandwidth reserved for this request by the manager carrier network resources 1 and complete the aggregation selection of LSP routes for this request. LSP route aggregation Includes: LSP18, LSP17 and LSP16 in the resource response of connection received by the carrier network resource manager 1, the LSP3 and LSP1 routes selected by the network resource manager bearer 1. Next, the bearer network resource manager 1 transmits this aggregation of LSP routes as well as information about the connection and QoS parameters in the resource request of connection to ER1 by means of a service flow mapping order and complete the resource allocation, so that ER1 obtains the LSP information assigned by the carrier network control network for the current call.

As depicted in Figure 13, ER1 acquires LSP 1301 information of the current call, where the Information 1301 includes LSP1, LSP2, LSP3, LSP4 and LSP5. The LSP selected in the previous stage is from ER1 to BR1 through LSP1. The information on LSP1 tags is modified to LSP1 ', while the LSP passes through the basic router 1303, including the information of LSP 1302 that arrives at BR1, the routes LSP2, LSP3, LSP4 and LSP5. Then the LSP moves from BR1 to BR2 through LSP2, the label information is modified from LSP2 to LSP2 ', while LSP passes through the router basic 1304. The information of LSP 1303, which reaches BR1, includes LSP3, LSP4 and LSP5. The rest of the process can be deducted by analogy, that is, the LSP moves, then from BR2 to BR3 through LSP3 and then to BR4 through LSP4 and finally to ER2 through LSP5. In this way, the calling party can send information to the called party through this LSP route.

In step 1210, after receiving a service flow mapping order response from ER1, the carrier network resource manager 1 sends a response from AC connection resource, indicating the successful acquisition of the LSP information and resource allocation also with success.

Figure 14 illustrates another configuration flow of LSP information and resource allocation by a manager carrier network resources, according to the present example. In this flow, the specific method is similar to that illustrated in the Figure 12, being the only difference that the resource manager of carrier network first selects an LSP inter-domains and then select an LSP intra-domain, after receiving a response from connection resource. Therefore, the stages of this flow will be Concisely illustrated, as depicted in Figure 14, this routing procedure being as follows.

In step 1401, a CA sends a request for connection resource to the carrier network resource manager 1.

In step 1402, the network resource manager carrier 1 selects an inter-domain LSP among management domains 105 and 106.

In step 1403, the network resource manager bearer 1 sends a connection resource request to the manager carrier network resources 2.

In step 1404, the network resource manager Carrier 2 selects an inter-domain LSP among management domains 106 and 107.

In step 1405, the network resource manager bearer 2 sends a connection resource request to the manager carrier network resources 3.

In step 1406, the network resource manager carrier 3 selects an intra-domain LSP from management domain 107 from an LSP matrix table intra-domain

In step 1407, the network resource manager carrier 3 returns a connection resource response to the manager of carrier network resources 2.

In step 1408, the network resource manager Carrier 2 selects an intra-domain LSP from management domain 106 from an LSP matrix table intra-domain

In step 1409, the network resource manager bearer 2 returns a connection resource response to the manager of carrier network resources 1.

In step 1410, the network resource manager carrier 1 selects an intra-domain LSP from management domain 105 from an LSP matrix table intra-domain, transmits aggregation of LSP routes global as well as information about the connection and parameters of QoS, in the connection resource request, to a router input and complete the allocation of resources.

In step 1411, the network resource manager Bearer 1 returns a connection resource response to the CA.

Since the LSP information required by bearer network resource managers will pre-configure in the present example, when a carrier network resource manager selects LSP or allocates resources of bandwidth and LSP for a customer’s call service, will acquire information from LSP directly from the managers of carrier network resources and select an appropriate LSP for the Current call from the LSP information. Therefore, the LSP information can be used repeatedly, thereby the routing load of resource managers is reduced of carrier network, increasing routing efficiency and maintaining the stability of the network. In addition, there is no priority restriction for the LSP information configured in bearer network resource managers, and thus, can complete routing and resource allocation operations with flexibility and high performance.

       \ vskip1.000000 \ baselineskip
    

The fourth example: switching routing way of labels

This scheme adopts the model "Diff-serv", represented in Figure 1, for illustrate data transmission, where the path of the layer of Carrier network control of this model includes: signaling between the bearer network resource managers and the service routes between the CN connection nodes, comprising the service route specifically intra-domain routes and inter-domain routes There are two aspects to determine the routes in the carrier network resource manager: a aspect is to determine the routes between the resource managers of carrier network and determine the following network resource manager jump carrier, thus establishing a route of signaling; another aspect is that each network resource manager carrier determines the itinerary for the service in the layer of carrier thus establishing a service itinerary. In In this case, the CN can be ER, BR and other routers, such as switching routers.

Figure 15 is a flow chart of routing by a carrier network resource manager, of according to the current routing way. The stages Specific are as follows.

In step 1500, a CA sends a request for connection resource to a carrier network resource manager in origin, including the request for connection resource address Destination IP or the domain name of this user.

In step 1501, according to this IP address, or domain name, the bearer network resource manager, whose end-office router / end-office router in tandem accesses the service initiated by the CA call agent , it is determined and also, the outgoing router of this service in the source carrier network resource manager is determined. The BR of this carrier network resource manager at source can be determined according to information such as type of service and service parameters, in the connection resource request sent by the CA agent, as well as the route information in the carrier network resource manager at source. The route information of this carrier network resource manager at source can be preset and stored in the carrier network resource manager at source or the carrier network resource manager at source is informed by the CN in said manager.

In step 1502, a network resource manager carrier performs inter-domain routing between the current carrier network resource manager and the next jump carrier network resource manager, for the service initiated by the CA. While routing is taking place inter-domains, between the network resource manager Current carrier and the next carrier network resource manager jump, for the service initiated by the CA, it can be determined an available LSP route according to the type of service, status of resource availability, priority, strategy of configured routing and QoS requirements and are reserved some bandwidths in this LSP in the resource manager of Current carrier network, for this application. The resource manager Current carrier network sends a connection resource request to the next hop carrier network resource manager, including the request the route entry router inter-domains to the following resource manager of jump carrier network, QoS parameters and the type of this service as well as the destination IP address of the following jump carrier network resource manager.

In step 1503, according to the router selected output of LSP, in the network resource manager carrier in step 1502, an input router is determined of the next hop carrier network resource manager and the information from this router is transported in the message of connection resource request to be sent to the next bearer network resource manager.

In step 1504, a router is determined from output of the next hop carrier network resource manager, according to the type of service and the service parameters in the connection resource request sent by the manager previous jump carrier network resources as well as information of the path of the current carrier network resource manager. Is judged if this bearer network resource manager is the manager of carrier network resources at destination, that is, router of "end office" / central router in tandem. If so, it will will execute step 1506; otherwise, the stage will be executed 1505

In step 1505, this network resource manager Bearer is taken as the current carrier network resource manager and then step 1502 will be executed.

In step 1506, after the completion of the inter-domain LSP routing, between bearer network resource managers, according to the intra-domain input router and the intra-domain exit router of each manager of carrier network resources, the LSP route is determined intra-domain of each network resource manager carrier, a carrier network resource manager will be applied to bandwidth resources and will record information from LSP resources and then transmit the LSP resources registered by you and the following network resource manager carrier of jump to its network resource manager carrier of previous jump by means of a connection resource response, until the response reaches the bearer network resource manager in origin.

In step 1507, the network resource manager carrier selects an intra-domain LSP from this carrier network resource manager as a route intra-domain and start a flow mapping order service, send the session ID, flow information to an ER of service, QoS parameters, the flow descriptor as well as the  aggregation of global LSP routes of this service from the manager carrier network resources at source to the network resource manager carrier in destination thus completing the routing among the bearer network resource managers for this service.

When the method is applied according to the present example to perform the routing of LSP intra-domain of a network resource manager carrier, different algorithms of routing For example, a method of pre-calculation of the route that includes: presentation of a table of intra-domain routes of a network resource manager carrier and determine an LSP by consulting BR and ER of this manager of carrier network resources in the table; you can adopt a "jump-to-jump" route algorithm, comprising: select an LSP from a given intra-domain CN node to another CN and repeating this procedure until a router Output of this LSP is a certain BR in this management domain; a matrix route algorithm can be adopted, comprising: presetting a route table intra-domain network resource manager carrier and determine an LSP by consulting the BR of this manager carrier network resources in the table. In addition, it can be adopted also the Dijakstra algorithm, the algorithm of Bellman-Ford or the configuration algorithm static

When the method is applied, according to the present example, to perform routing inter-domains of the network resource manager carrier, different route algorithms can be adopted. By For example, a "jump to" route algorithm can be adopted jump ", which comprises: selecting an LSP from a given BR inter-domains to another CN and repeating this procedure until an outgoing router of this LSP is a BR of a given carrier network resource manager.

Although routing intra-domain and routing inter-domains, for the network resource manager carrier, be independent, are also inseparable, that is, After receiving a connection resource request, a manager of carrier network resources you don't just have to determine a Intra-domain LSP of this network resource manager carrier but also determine an LSP inter-domains between himself and the next manager of jump carrier network resources.

The routing method, according to the This example will be described with reference to a specific example and to Figure 5 which is a schematic diagram illustrating the routing by a carrier network resource manager.

There are ER1, ER2, BR1 and BR2, in the domain of bearer network resource manager 1, there are BR3, BR4, ER3 and ER4 in the domain of carrier network resource manager 2 and there are other CN connection nodes (not shown in Figure 5) as well as between the LSP routes (not shown in Figure 5) in the domain of carrier network resource managers 1 and 2. The routes between bearer network resource managers 1 and 2 include LSP11, LSP12, LSP13 and LSP14.

When a resource request is received from connection sent by the CA with IP address such as 10.1.0.0/16,  the carrier network resource manager 1 will determine the router input as ER1, according to the IP address of this request and then determine the outbound router as BR1 according to the destination address, type of service and service parameters of this connection resource request. The service parameters may include width requirements band, priority, etc. If the carrier network resource manager 1 detects that both LSP11 and LSP22 routes can reach the manager of Carrier network 2 resources, according to the type of service, resource availability status, priority, strategy Configured routing and QoS requirements of this service initiated by the CA, will determine an available LSP and register it, for example LSP11 is selected as the route inter-domains from BR1 to BR3 and thus, the Carrier network resource manager 2 input router Determine how BR3. Carrier network resource manager 1 sends a connection resource request to the network resource manager bearer 2 and this bearer network resource manager 2 learns that Its output router is ER4, according to its own route information and then the network resource manager Carrier 1 selects an LSP according to ER1 and BR1 and registers the LSP and the carrier network resource manager 2 selects a intra-domain route of LSP according to BR3 and the destination address of the service in the request, for example, ER4. Finally, carrier network resource manager 2 returns a connection resource response to the network resource manager carrier 1, including the LSP response intra-domain network resource manager carrier 2, so that the carrier network resource manager 1, that is, the carrier network resource manager at source can get the service route of this CA and complete the routing among the bearer network resource managers for this CA.

The method, disclosed herein example, it is applicable to networks with complex structure, where determine, first, inter-domain routes between bearer network resource managers and then selected intra-domain routes of the network resource manager carrier The intra-domain routing and the inter-domain routing of a manager carrier network resources, can be performed, respectively, with different routing algorithms, according to situations factual, so that they ensure that the data is properly transmitted between the bearer network resource managers and that the network resources of the carrier network resource manager are use reasonably, with a higher success rate of routing, easy implementation and convenient maintenance.

       \ vskip1.000000 \ baselineskip
    

The fifth example for a better understanding of the invention: routing way with user address segment of virtual destination

There are edge routers in a network of Independent operation in general. Edge routers are used to connect to the edge routers of other networks of independent operations and interconnection between networks of independent operations. When a network of independent operation, in the present example for the better understanding of the invention, a virtual destination user, who it has networks of independent cross-information operations of target user address segments, preset in a carrier network resource manager. This resource manager carrier network manages edge routers in the network of Current independent operations and virtual destination user Preset is linked to an edge router. While therefore, a route to the real destination user is configured in the destination independent network operations gateway (gateway) and the gateway of this network of destination independent operations is connect to this network resource manager edge router Current carrier

There can be multiple edge routers in a network of independent operations, so that the user of virtual destination and the corresponding edge router must be linked together and the corresponding edge router is connected to an independent operations network gateway destination, which manages the actual destination user. In this way, the resource manager of the current independent operations network you can determine a virtual destination user of the network current independent operations, according to the address of transmitted destination of the independent operations networks of cross services; in this way, they determine the router of edge that is connected to this virtual destination user and assign  a route in the current independent operations network from the user who sends the service to this edge router.

In the present example for better understanding of the invention, the destination user address segment, set by the virtual destination user, it can be a single address or a segment of addresses.

When a carrier network resource manager, at a carrier network control layer, you receive a request from connection resource through independent operation networks crossed, sent by a user of the operations network Current independent through a service server, the manager of carrier network resources, of this network of operations independent, determines that this service has to be sent to a virtual destination user, according to the destination address of service in this application; this way, you get the router border that links this network of independent operations with the virtual destination user to whom this service is sent. From agreement with the property of QoS, the destination address and the source address, the carrier network resource manager assigns network resources and routes them in the carrier layer of this network of independent operations from the user sending the request to this edge router, transmitting this service to this edge router, from the network of operations Current independent, according to network resources assigned and routes them in the carrier layer of this network of independent operations This edge router, from the network of Current independent operations, transmits this service to a gateway of the destination independent operations network and the gateway of the destination independent operations network transmits this service to the real destination user, in accordance with the preset route.

When the network edge router of Current independent operations connects to routers edge of multiple networks of independent operations, because a corresponding relationship table between the information in the address segment of the destination user and the gateways of the destination network is preset at the network edge router of current independent operations in the prior art, the Edge router of the current independent operations network You can consult this table according to the destination address of the service, determine the gateway of the network of operations independent of destination to which this service is to be sent and to then send this service to the specific gateway of the Destination independent operations network.

When the network of independent operations of destination is a carrier network, with guarantee of Quality of Services QoS, the gateway in the destination independent operations network It is an edge router. Alternatively, no route from the Edge router to the target user is previously set in the destination independent operations network, but the layer of Carrier network control performs routing in accordance with the destination address and the QoS parameters of the service you have to be transmitted over the edge router and allocate resources from carrier and routes them according to the current state of the network of independent destination operations and then the Edge router transmits this service to the target user, in accordance with this allocation of carrier and route resources.

The route selection scheme will be described with reference to a concrete example for better understanding of the invention and Figure 16 which is a schematic diagram illustrating the network structure to perform the routing through networks of independent operations, according to the scheme of current routing In this case, the network of operations current independent and network independent operations of Destination are guaranteed by QoS. As illustrated in Figure 16, assuming that USER1, of the network of independent operations current, transmits data to USER2 of the destination network, the resource managers of carrier network 1 and 2 of the network of current independent operations, control the allocation of resources and the routing of the carrier layer of the network of current independent operations while the manager of carrier network resources 3, from the operations network independent of destination, controls the allocation of resources and the routing of the carrier layer of the operating network Destination independent. USER1 is connected to ER1 edge router of the independent operations network current as well as service server CA1, a virtual USER2 of independent cross-user networks of users of destination is set in carrier network resource manager 2 of the current independent operations network and links to BR1. He carrier network resource manager 2 controls BR1, according to the established virtual USER2, BR1 is connected to ER2 of the network Destination independent operations, the actual USER2 in the network of Destination independent operations connect to ER3 and CA2, while CA1 connects to CA2.

As illustrated in Figure 17, adopting the network structure depicted in Figure 16, the procedure of routing through operations networks independent includes the steps indicated below, in the assumption that USER1 sends a USER2 service.

In step 1700, USER1 sends a connection resource request to the network resource manager carrier 1 through CA1, including the information request such as QoS parameters, source address and destination address of this service.

In step 1701, after receiving this request, the carrier network resource manager 1 negotiates with the other bearer network resource managers in the operations network independent current, judge whether the destination address included in This request is an address managed by the network of operations current independent; if so, step 1702 will be executed and of otherwise, step 1703. In this case, the bearer network resource manager procedure 1, which negotiates with other carrier network resource managers, in the network of Current independent operations, may be a negotiation between bearer network resource managers 1 and 2 and such negotiation is You can perform with any prior technique.

In step 1702, according to the information of the QoS parameters, the source address and the address destination of this service, the carrier network resource manager 1 and other bearer network resource managers in the network of current independent operations, allocate layer resources of carrier and route it for this service, and the service sent by USER1 is transmitted to the user with the destination address of according to the allocated resources of the carrier layer and the They walk through the carrier layer.

In step 1703, in the case that this destination address is managed by another network of operations independent, carrier network resource manager 1 and others bearer network resource managers in the operations network independent current, determine the preset virtual USER2 according to the parameters of QoS, source address and address destination of this service, thereby determining the router BR1 edge of the current independent operations network, which It is linked to the virtual USER2 and to which this service, allocate carrier layer resources and route them in the current independent operations network between the USER1 that send this request to the BR1 edge router for this service.

The procedure to determine the USER2 preset virtual can understand judge if the address of destination of this service is in the address segment of the Virtual USER2.

In step 1704, after the end of the routing of the current independent operations network, the route from the BR1 edge router of the operating network current independent, to the BR2 edge router of the network destination independent operations, is determined according to the corresponding preset relationship table and finally CA1 sends a service resource request to CA2. Application service resource is sent to the network resource manager carrier 3, of the destination independent operations network, and then, the bearer network resource manager 3 assigns network resources and routes them from ER2 to USER2, in the network of independent destination operations for this service, of According to the parameters of QoS, source address and information of the ER2 network segment of this service.

In step 1705, according to the resources of the carrier layer and the path from the user who sends this request to the BR1 edge router assigned in step 1704, the route established between BR1 of the independent operations network current to ER2 of the destination independent operations network and the carrier layer and route resources from the router ER2 border to the destination USER2 that is assigned by the network of destination independent operations, the service sent by USER1 is transmitted to the USER2 of destination through the BR1 edge router of the independent operations network current in the carrier and ER2 layer of the operating network Destination independent.

The destination independent operations network it can also be another network without QoS guarantee, such as a network IP. In this case, the service sent to the network of operations destination independent is transmitted to the destination user of according to the route established by the operations network itself Destination independent.

The method disclosed in the present example for a better understanding of the invention you can establish a route of communication with the QoS guarantee in the network control layer carrier and can protect topology structures from different networks of independent operations performing, of this mode, the transmission of services with QoS guarantee through networks of independent operations.

In the present example for better understanding of the invention, a virtual destination user, with information from the address segment, is set in the resource manager of the Current independent operations network. When a user of the current independent operations network sends a service to a target user of other independent operations networks, the resource manager of the current independent operations network determine the virtual destination user, according to the address of destination transmitted in the service and then according with the QoS parameters, the source address and the address destination of this service, the resource manager can assign bearer resources and virtual destination user path for this service. This service is then transmitted to the user. virtual destination, according to carrier resources and routes that are assigned, transmitting the edge router, with network segment information of the virtual destination user, this service to a gateway of the network of independent operations  destination and the gateway of the network of independent operations of destination transmits this service to the actual destination user of according to the preset route. Therefore the routing of a service, with QoS guarantee, through networks of independent operations can be performed by this example for a better understanding of the invention.

       \ vskip1.000000 \ baselineskip
    

The sixth example for a better understanding of the invention: combination of E.164 addressing and route routing IP

The way to route the IP address is address through the destination IP address included in an IP packet, the IP address being the only address assigned for each central computer connected to the Internet. The Figure 18 represents the IPv4 IP datagram format, as illustrated in said Figure 18, an IP datagram being constituted by header and data. As for IPv4, four bytes are used in the header to indicate the IP address of the destination station and an IP route simply uses this station IP address destination for addressing, where the network is located, in First, according to the network ID at the IP address of the destination station and then the central computer will found according to host-id.

The method of addressing the carrier path in a carrier network, using the IP address mode, in a network With carrier network control layer, the method of addressing according to the IP address on the server carrier network control. Stored route information is usually be the information in the IP route table, with the IP address as the destination address and the routing table is use to select a carrier network carrier path.

Although the IP address structure facilitates Internet addressing, the IP address cannot reflect any geographic information regarding the location of the host (hub). All current networks are established in terms of geographic locations, so the number of IP route tables, in the current network, depends on the degree of aggregation of IP addresses, which indicates the ability to combine IP addresses in terms of Network segments The aggregation capacity of IP addresses will be less and less as new IP segments are added and the increase in the number of IP route tables will make the stability of IP routes more poor and increase the time interval and the difficulty of addressing IP routes

E.164 is a class of labeling way and addressing in the current telecommunications network and applies widely in the Public Switched Telephone Network (PSTN) and the Network Digital Integrated Services (ISDN). E.164 is a class of user number that includes the geographic information of user location, but is not currently applied in the network of IP.

The basic idea of this scheme of routing is to divide the network into multiple management areas different and adopt different control modes in the addressing; more specifically, selecting a route between different management areas, according to the mode of E.164 addressing, and selecting a route inside of a management area, according to the addressing mode of IP routes

With reference to Figure 19, the procedure network routing, in the present scheme of routing, includes the following stages:

Stages 1901-1902: divide a network into multiple different management areas and establish a corresponding carrier network control server for each management area. The management area can be a metropolitan area network, a provincial backbone network or a national backbone network.

Stage 1903: establishment of an area code for each management area according to E.164 mode.

       \ global \ parskip0.900000 \ baselineskip
    

As is well known by experts in this technique, E.164 evolves from the telephone labeling system standard and is a standard recommended by ITU-T for the labeling of international telecommunications, in particular for labeling in the ISDN network, Data Service Switched on Multimegabits (SMDB) and Broadband ISDN. A E.164 number consists of the following elements: country code (1-3 digits), area code (n digits) and phone number (15-n digits). A E.164 number includes geographic location information and a telecommunications network is established in accordance with the geographical location, which makes the routing of network routes using E.164 mode.

If other countries also use the same network framework to establish a network called cross-country through interconnection, country codes can be specified to facilitate addressing between different countries.

A management area corresponds to only one carrier management server, so the management server Carrier also has the corresponding label. For the therefore, labeling different carrier management servers, the corresponding management areas can obtain area codes also corresponding.

Stage 1904: establish a relationship table of topology that includes management area codes corresponding and other management areas on each server carrier network control. The table includes: area code destination, the following jump area code, route and other information, using the table to store information on route between this management area and other management areas within the net.

Stage 1905: establish an information table corresponding intra-area route of a management area in each carrier network control server. This table includes: destination IP address, the next hop route and another information. This table is used to store the information of configured route of this management area.

Stage 1906: in case there are services of Users from different management areas, routing inter-area between different management areas, it is done according with the established area codes of the management areas and the intra-area routing, within the management area, is carried out of according to the route information table established within This area of management.

Stage 1907: in case there are services of users of the same management area, intra-area routing within the management area, it is done according to the table of route information established within this area of management.

The route control mode, in step 1906, is will describe in detail below, referring to a User calling procedure in different areas of management.

As depicted in Figure 20, the User call procedure, in different management areas It comprises the following stages.

In stage 2001, the user making the call send a call request to a service server in an area management, where said caller is located. Application Call includes the area code of the management area where you are located the called user and a called user number.

In stage 2002, after receiving the call request, the service server sends a message from route request to a carrier network control server corresponding to the current management area, in accordance with this call request This route request message includes: area code of the management area where the user is located who makes the call, the caller's number, the code of area of the management area where the called user is located and the called user number. The number of the user who makes the called and the number of the called user can be assigned by any other service provider or in a previous way, such as the IP address of the user making the call and that of the called user or other internal numbers. If the user who does the called and the called user are in the same management area, the area code of the management area, where the user is located called, may be omitted.

In stage 2003, the network control server carrier obtains the area code of the management area, where it is located the called user, according to the request message of route received.

In stage 2004, the network control server carrier judges whether the called user is a user of the area of current management; if so, stage 2005 will be executed and if not thus, stage 2006 will be executed.

In step 2005, a route is selected, from according to the route information table established within the management area, and the relevant routers are notified to the user service forwarding to the called user, according to the selected route.

In stage 2006, according to the message of received route request and topology relationship table stored, the carrier network control server assigns a route for the user making the call and in the meantime, notify the carrier network control server corresponding to the following jump area code of the called user information and to then it goes back to stage 2004 in which the server of carrier network control corresponding to the following area code judge if the called user is a user of this area of management.

The previous stage 2006 is repeated until the service is routed to the management area where the called user and then the service is sent to the user called, according to the mode established in stage 2005.

       \ global \ parskip1.000000 \ baselineskip
    

As is known by experts in this technique, using a carrier network control layer independent, you can avoid important updates and reform in the basic equipment of a carrier network and the ability to Carrier network control processing can be more powerful, safe and stable. Therefore, in order to provide better carrier network control capability, control servers carrier network, in the present example for a better understanding of the invention can be separated from the carrier layer, that is, that the bearer network control servers constitute a layer of independent carrier network control to perform control on the routing of carrier network.

The routing procedure of this method will be described, then, with reference to a concrete application of this example for better understanding of the invention. With reference to Figure 21, it is assumed that there are four areas of management, which are respectively the areas of management A, B, C and D. In the present example for the better understanding of the invention, a network resource manager Carrier is a carrier network control server.

First, a planning of E.164 mode labels in these four management areas by assigning an area code for each management area, assuming that Management areas A, B, C and D are labeled 01, 02, 03 and 04 respectively, each management area corresponding to a single  carrier network control server and servers can be name bearer network control servers A, B, C and D. By therefore, the bearer network control servers also obtains the corresponding tags and tag planning are you can consider as done with network control servers carrier The management area and topology relationship tags they are stored on the bearer network control servers, the topology relationship that describes the interrelation between these management areas, for example, the specific configuration of the carrier network control server A represents the destination area 04 that can be reached through areas 02 and 03. The routes to each management area, according to the code addressing area, they are also configured on each network control server carrier and this kind of routing operates as a route that used for switching equipment in a public telephone network switched (PSTN) to perform retransmission routing to long distance, using a long distance area code. In the present example the possible relationship of topology and labels management area, that is, the configuration status of the Routing is as follows:

3

       \ newpage
    

In the event that user S1 starts a call to user S2:

1) User S1 dials the user's number called S2, where the dialed number comprises an area code of the management area where the S2 user is located and the format To dial can be: called area code of the user + number of the called user. In this case, the number of the called user will be assigned by service providers or networks according to a prior art and can be the IP address or other numbers internal, such as a defined number "234544" or a name of self-defined domain "liyiming", etc. If the user who does the call and the called user are in the same management area, you can skip the area code of the management area where it is located the called user.

2) The service server analyzes the request of the user and negotiates the capabilities of the two extremes, such as an acceptable transmission rate, with compression coding from the terminal and then send an application to the server carrier network control Once the success of the negotiation, where the application comprises the IP addresses of the user making the call and the called user as well as the area codes of the management areas, where the user who makes the call and the user called, respectively.

3) The carrier network control server A address according to the area code of the Management area called first. The address in the current example is from management area 01 to management area 04, which is like the long distance area code that addresses on the PSTN network. In detail, area code 03 is addresses by code carrier network control server A of area 01, according to the self-registered route to the area code 04; Area code 04 is addressed by the control server of carrier network of area 03, in accordance with the area code of destination, so that it is addressed from the area code of origin to the destination area code and the route from the area of lorkigen to the destination area is also selected accordingly, on the assumption that the current selected route is "LSPa1 / LSPac / LSPcd".

4) The carrier network control server D address in its own management area, according with the IP address of the called user. In this way, it is addressed E2

Therefore, the current selected route is "LSPa1 / LSPac / LSPcd / LSPd1".

5) After selecting a route for the current service, the carrier network control layer sends this route to the E1 edge router, if it is a service flow bidirectional, the route must also be sent to the router E2 edge. Edge router encapsulates route information in a data packet header and then the edge router and intermediate router transmit the flow of service according to the specified route.

In this way, the procedure of service routing and shipment.

Integrating the E.164 addressing mode with the IP network, in this example for a better understanding of the invention, during the procedure of selecting a route of carrier in a carrier network, combining the advantages of the mode of E.164 addressing and IP route, the control server of carrier network uses the E.164 number and the IP address to it time, where the carrier network control server is routed  to the management domain, where it is placed by addressing with the number E.164, so that a lot of addresses of IP are protected and it becomes simple and fast mode of routing to the destination domain. Then the server carrier network control locates a specific user within of the management domain using the IP address, so that reserve several advantages of using the IP address in the IP network current. Therefore, the routing operation is more simple and fast in large-scale networking frameworks and complexity and instability in the large-scale network are overcome when you simply use the IP address for the addressing. At the same time, the capacity of network expansion

From the routing procedure described above from the carrier network resource manager in source to the carrier network resource manager at destination, you can Note that the "end-to-end" routing It mainly comprises two parts: routing intra-domain within each resource manager of carrier network and inter-domain routing between different carrier network resource managers. exist also different routing modes in terms of intra-domain routing or routing inter-domains, for example, matrix mode of routes, IP identifier mode of outbound / inbound router, mode of restriction condition routing, establishment of the routing strategy, etc. In these modes, some are applicable to intra-domain routing and inter-domain routing while others only applicable to intra-domain routing or to inter-domain routing.

The specific implementation procedure and the applicability of each intra-domain routing or inter-domain routing will be described, more forward, with reference to the corresponding network structure of the "Diff-serv" model.

       \ newpage
    

The first mode: routing mode by adopting a table of route matrix

This routing mode adopts the model "Diff-serv", represented in Figure 1, for Perform data transmission over the network. In this model, a carrier network control layer path comprises the signaling path between network resource managers carrier and service path between CN connection nodes. The route service includes the inter-domain route and the intra-domain route while the present mode routing refers mainly to the route intra-domain The basic idea of the present method is: establish and maintain a matrix table of attainable routes between intra-domain CN connection nodes in a carrier network resource manager, routing completion intra-domain of each network resource manager carrier using this matrix table and determining, from this mode, the intra-domain service path of each bearer network resource manager. In this case, the CN node can be ER, BR or other routers, such as direct routers Forwarding

With reference to Figure 5, the managers of Carrier network resources 1 and 2 respectively manage the metropolitan area networks 1 and 2 and each metropolitan area network It comprises more than one ER or BR. Taking the management domain managed by carrier network resource manager 1 as For example, there are ER1, ER2, BR1 and BR2 routers that can be take as outbound routers or inbound routers, in the management domain of the carrier network resource manager 1 and there are also other CN connection nodes intra-domain as well as the Switching Protocol of Labels (LSP) between them. Before the intra-domain service route routing, an aggregation of said LSP routes is established in advance between each entry and each exit, within this domain, and to then routing is done intra-domain according to this aggregation of established routes. In the present example, this route aggregation LSP is established and stored in a matrix mode and the procedure setting this aggregation of LSP routes is like follow:

Stage 11: random selection of any of the routers ER1, ER2, BR1 and BR2, which can be take as input or output or as the input router. At In this example, ER1 is selected as the input router at the beginning and the information of ER1 is added to an aggregation of Search object routers.

Stage 12: select an LSP route from all LSP routes connected to ER1 without repetition.

Stage 13: judge whether the router on the other end of the selected LSP is a BR or ER intra-domain and if the information in this router is not included in the aggregation of routers that Wanted; If so, finish the current search, register the LSP selected and return to stage 12 in which the search for other possible LSP routes of the ER1 router until All possible LSP routes of ER1 are searched. If not, take the router at the other end of the LSP selected as the current router, record the information of this router in the set of routers sought and execute the stage 14.

Stage 14: select an LSP from all LSP routes that the current router takes as the starting point, judging whether the route information at the other end of the LSP selected is included in the aggregation of object routers search if so, it means that the selected LSP can constitute a loop route, leaving then the LSP selected and returning to stage 14 in which the selection of the following LSP and the trial is made correspondent; otherwise, stage 15 is executed.

Stage 15: judge if this router is a BR or ER of the current domain; if so, end the current search and return to stage 12; if not, take this router as the Current router, record the information of this router in the set of routers searched and rerun the stage 14 in which the search continues with this router as the starting point until the route at the other end of the LSP Wanted be an intra-domain BR or ER.

Similarly, according to the previous method since stage 11 to stage 15, an aggregation of LSP routes with ER2, BR1 and BR2, like the incoming routers, is obtained by corresponding search.

The aggregation of LSP routes obtained through of the previous method, from stage 11 to stage 15, it is stored in a matrix table as indicated in table 3.

TABLE 3

5

       \ vskip1.000000 \ baselineskip
    

In this table, the row element and the element column represent, respectively, the output router and the inbound router within the resource manager domain of carrier network 1. The element of the routers table of input and output table router element comprise, respectively, all ER or BR routers in this management domain, indicating the crossing points of rows and columns in the aggregation of routes from one ER / BR to another ER / BR. The route aggregation, obtained, from stage 11 to stage 15, is fill in corresponding places in this table and thus, the  route aggregation between inbound and outbound routers It is recorded in this table. Said set of routes, in this table, It can have the following operational status:

(1) Null. The "__" or a space in the table 3 means that there is no route available between the inbound router and outbound router.

(2) There is only one route available. By example, {(LSP1)} in table 3 means that there is only one optimal route between the input router and the router exit; {(LSP3, LSP4)} in Table 3 means that this route transmits a plurality of LSP routes intra-domain

(3) There are multiple routes. For example, {(LSP5), (LSP2, LSP4)} in Table 3, which are separated by parenthesis, means that there are multiple optimal routes between the inbound router and outbound router.

       \ vskip1.000000 \ baselineskip
    

The carrier network resource manager 1 performs intra-domain routing, according to the route aggregation previously calculated and stored in the table 3. In the present example, the carrier network resource manager 1 is a source carrier network resource manager for the call, so that the carrier network resource manager 1 finds, in First, the ER2 input router, according to the IP address of the party making the call, and then check the Table 3 to discover that aggregation of LSP routes, through the which is possible to reach the domain of the network resource manager Carrier 2 from ER2 comprises: the LSP route from ER2 to BR1: {(LSP5), (LSP2, LSP4)}; the route from ER2 to BR2: {(LSP3, LSP4)}.

In the present example, LSP5 is selected as the intra-domain route of the network resource manager carrier 1, in accordance with the regime of shared loads or type of service, priority, routing strategy set to local level, the operational status of the current network and requirements of specified QoS. In this case the operational status of the network current can understand the status of resource availability and The current service flow. In other embodiments that use the present routing mode, it can be performed also the previous routing procedure according to other conditions.

In the present routing mode, you can also use the Dijakstra algorithm, the algorithm of Bellman-Ford or the configuration algorithm static to determine route aggregation intra-domain beyond the stages before described.

After the routing procedure intra-domain, in the network resource manager carrier 1, is completed by adopting this mode of routing, and routing can also be performed intra-domain between network resource managers carrier 1 and 2. Of course, it is also applicable to perform the  inter-domain routing between the managers of carrier network resources first and then perform intra-domain routing by adopting the present routing mode, according to the routers input and output determined by the result of the routing

For this routing scheme to use the route matrix, according to the practical situation of each bearer network resource manager, you can perform the intra-domain routing through the intra-domain route information pre-established, presenting this method advantages such as high speed, easy realization, convenient application, easy maintenance and management and being suitable for application in complicated networks.

       \ vskip1.000000 \ baselineskip
    

The second mode: routing mode adopting the IP identifier of outbound / inbound router

This routing mode adopts the model Diff-serv, illustrated in Figure 1, to perform Data transmission over the network. In this model, a carrier network control layer path comprises the route of signaling between bearer network resource managers and the route of service between CN connection nodes. The service path understand the inter-domain route and the route intra-domain, while the present mode of routing mainly refers to the route intra-domain The basic idea of the present method is: establish and maintain a table of attainable routes between intra-domain CN connection nodes in a manager of carrier network resources, performing the routing intra-domain of each network resource manager carrier in the carrier network control layer using this route table and thus determining the service route intra-domain of each network resource manager carrier In this case, the connection node CN may be ER, BR or other routers, such as forwarding routers.

With reference again to Figure 5, the Bearer network resource managers 1 and 2 manage, respectively, metropolitan networks 1 and 2. Taking control management, managed by the carrier network resource manager 1 as an example, there are routers ER1, ER2, BR1 and BR2 that they can take as outbound or inbound routers in the Bearer network resource manager management domain 1. In actually, there are other CN connection nodes (not represented in Figure 5) as well as LSP routes between them (also not represented in Figure 5) in the management domain of the resource manager of carrier network 1. Before routing is performed intra-domain service, is established, of beforehand, within this domain, an aggregation of these routes LSP between each outgoing router and each inbound router and then the IP identifiers are set according with the IP address segments managed by all outbound and inbound routers intra-domain

In the present example, this route aggregation LSP is established by means of a route table. Any ER1, ER2, BR1 and BR2 router, which can be taken as input router, is selected as the router of input and ER1 is selected as the input router in the present embodiment example. The procedure to establish the LSP route aggregation comprises the following stages:

Stage 21: establishment of the segment of IP addresses managed by ER1 in the network resource manager carrier as IP1 and add the information from ER1 to the aggregation of routers sought.

Stage 22: Select an LSP route from all LSP routes connected to ER1.

Stage 23: judge whether the router on the other end of the selected LSP route is a BR or ER intra-domain and if the information in this router is not included in the aggregation of routers that Wanted; If so, finish the current search, register the route LSP selected and return to stage 22 in which the search for other possible ER1 LSP routes until they are searched all possible LSP routes of ER1; if not, take the router at the other end of the LSP route selected as the Current router, record the information of this router in aggregation of routers that are searched and execute the stage 24.

Stage 24: select an LSP from among all LSP that takes the current router as the starting point, judging whether the route information at the other end of the LSP selected is included in the aggregation of routers that are search; if so, it means that the selected LSP is possible that constitute a loop route, then abandoning the LSP selected and returning to stage 24 in which the selection of the following LSP and the trial is made correspondent; otherwise, stage 25 is executed.

Stage 15: judge if this router is a BR or ER of the current domain; if so, end the current search and return to stage 22; if not, take this router as the Current router, record the information of this router in the aggregation of routers that are searched and rerun the stage 24 in which the search continues with this router as the starting point until the route at the other end of the LSP sought is an intra-domain BR or ER.

In the current routing mode, you can also use the Dijakstra algorithm, the algorithm of Bellman-Ford or the configuration algorithm static to get aggregation of LSP routes intra-domain network resource manager carrier beyond the stage described above.

According to the method mentioned above for set aggregation routes LSP, ER2, BR1 and BR2 are taken as input routers, respectively, the segments of addresses managed by ER2, BR1 and BR2 are set, respectively, such as IP2, IP3 and IP4 and all LSP routes are searched of ER2, BR1 and BR2.

       \ newpage
    

The IP address segments, managed by the carrier network resource manager, are assigned to ER1, ER2, BR1 and BR2 in this carrier network resource manager. The identifier IP1 is assigned for ER1, IP2 for ER2, IP3 for BR1 and IP4 for BR2. The IP address segment table, in the management domain of the carrier network resource manager is set as represented in table 4.

       \ vskip1.000000 \ baselineskip
    

TABLE 4

6

       \ vskip1.000000 \ baselineskip
    

In table 4 the IP address segment of 10.1.0.1-10.1.255.255 is assigned for IP1, that of 10.2.0.1-10.2.255.255 for IP2, 10.3.0.1-10.3.255.255 for IP3 and 10.4.0.1-10.4.255.255 for IP4. Thus, a service flow with an IP address can find the IP identifier of the outgoing router and the router of entry into the network management domain of network resources carrier

In the present routing mode, set an intra-domain manager LSP table of carrier network resources according to the relationship between the aggregation of established LSP routes and the IP, as indicated in the table 5:

       \ vskip1.000000 \ baselineskip
    

TABLE 5

7

       \ vskip1.000000 \ baselineskip
    

In table 5, the IP addresses of the outbound router and inbound router are represented both by IP identifiers, that is, that the element of the table column represents the input IP identifier intra-domain network resource manager carrier and the row table element represents the manager intra-domain IP output identifier of carrier network resources, being able to find the desired LSP at the crossing point of the table according to the IP identifier output and the incoming IP identifier of this flow of service. When two LSP routes are based on table 5, according to the outgoing IP identifier and the IP identifier input of this service flow, for example, the identifier Output IP and the input IP identifier of this flow of service are respectively IP3 and IP2, then you get to from table 5 that this service flow can select the LSP5 route or route (LSP2, LSP4). This routing mode can select the LSP route according to the loading regime shared, type of service, availability of resources, priority, configuration routing strategy locally or some specified QoS requirements, etc. For example, the LSP5 route is selected as an intra-domain route of the carrier network resource manager.

A concrete example will be taken to describe the routing procedure using tables 4 and 5 before indicated in the present routing mode.

In the event that a calling user sends a request to send a service flow to a manager carrier network resources, through a CA, and that the IP address of the user making the call is 10.2.0.0, then the intra-domain routing procedure, in the Bearer network resource manager, is as follows:

Step 210: obtain the IP identifier of current service flow entry as IP2 looking in table 4 according to the IP address of the user making the call.

Step 220: set the IP address of the outbound router to transmit the current service flow and look in table 4, according to this IP address to get the outgoing IP identifier to transmit the service flow current, assuming the outgoing IP identifier is IP1

Stage 230: look in table 5 according to the incoming IP identifier and the outgoing IP identifier of the Current service flow, get the route for the service flow current, which is LSP4 and thus, the current service flow is transmits through route LSP4 in the management domain of the bearer network resource manager.

In the present routing mode, the route LSP is not determined directly according to the router of inbound and outbound router of the service flow that is going to transmit, but in accordance with IP identifiers. Of this mode is flexible to establish the corresponding relationship between the segment of IP and ER or BR addresses in the resource manager of carrier network and therefore, there is no need to know exactly the inbound router and outbound router of the service flow; instead, know the incoming IP address and the outgoing IP address of the service flow is sufficient.

When table 5 is established, each segment of IP addresses, managed by a network resource manager carrier, may correspond to a specific ER or BR or correspond to multiple BR or ER routers. In the same way, Each BR or ER can correspond to multiple address segments IP. But different modes of correspondence give rise to different LSP in table 5.

Since it is required in the mode of Current routing to calculate all LSP routes between nodes CN connection within the resource manager management domain of carrier network, when a network presents a large scale, the scale of table 4 and table 5 can be very large, so It is not comfortable to consult the tables. Therefore, this mode routing is suitable for application in networks with not very big scale.

In this kind of routing scheme using the IP identifier of the outbound / inbound router, IP address segments managed by management domain of the carrier network resource manager are assigned to all outbound routers and inbound routers within the management domain of this carrier network resource manager and it set with IP identifiers and then set an intra-domain route table of the manager carrier network resources, according to all identifiers Outbound IP, incoming IP identifiers and LSP routes. When processes a connection resource request, an LSP is selected according to the intra-domain route table of the carrier network resource manager, so that routing intra-domain of each network resource manager carrier is performed in the carrier network control layer, with Easy implementation and convenient management and maintenance.

       \ vskip1.000000 \ baselineskip
    

The third mode: routing mode according to the restricted resource condition

This method adopts the model "Diff-serv", illustrated in Figure 1, for Perform data transmission over a network. In this model, the path of the carrier network control layer comprises the signaling path between network resource managers carrier and service path between CN connection nodes, the service route comprising a route inter-domains and a route intra-domain When the application is processed User service bandwidth, network control layer carrier will determine the service path of the user and the manager of carrier network resources will notify ER to send the flow of service according to the specified service path. The method in this way routing can be applied to the route of service and signaling route. However, since the Inter-domain network topology is usually simple, to perform the resource constraint on the signaling path it is not necessary and will increase the cost of maintenance management the network, the embodiment of this routing mode only illustrates the routing of service route, that is, the intra-domain routing. In this case the node CN connection above can be ER, BR or other routers such as forwarding routers.

As illustrated in Figure 22, in a form of realization of the present routing mode, it is needed set a route itinerary of "CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager carrier 2 \ rightarrow carrier network resource manager 4 ". In Figure 22, the dotted line represents a route of connection resource request setting with a width of 10M band as service requirement. With reference to the Figure 23, the procedure to establish this itinerary in a embodiment of this routing mode comprises the following stages.

In step 31, according to a request for called from a CA, the carrier network resource manager 1 determines ER1 as a calling center end router or central router in tandem. According to this router determined input, the carrier network resource manager 1 determines an intra-domain LSP, based on 10M bandwidth requirements. The specific procedure of the carrier network resource manager 1 that determines an LSP Intra-domain is as follows.

As shown in table 6, the information of all intra-domain routes is stored in the Carrier network resource manager 1, in advance. From contained in this table, the carrier network resource manager 1 get three LSP routes with ER1 as the office router Extreme caller: LSP1, LSPa and LSP3. The three LSP routes are respectively configured with a restriction condition of resources, in advance, and the resource restriction condition on this embodiment of the routing mode refers to bandwidth requirements In detail, the bandwidth Total LSP1 is 50000M and the maximum allowable bandwidth for Each service flow is 50M; the total bandwidth of LSPa is 10000M and the maximum allowable bandwidth for each flow of service is 10M; The total bandwidth of LSP3 is 1000M and the Maximum permissible bandwidth for each service flow is 1M. Since the maximum allowable bandwidth for each flow of LSPa service is 10M, which is equivalent to the requirement of 10M service bandwidth, the network resource manager carrier selects LSPa as the intra-domain route in the bearer network resource manager 1. Among the above three selectable LSP routes, the maximum allowable bandwidth for each service flow of LSP1 is 50M, which is sufficient for meet the service bandwidth requirement of 10M, but in terms of saving resources, resources will be wasted of the network if LSP1 is adopted. Therefore, LSPa is selected as the intra-domain path in the resource manager of carrier network 1 in the embodiment of the present mode of routing In addition, the current network status can also be take into consideration during the routing procedure. If the LSPa bandwidth is almost fully allocated, While there are still inactive resources in LSP1, you can select then LSP1.

In summary, during the procedure of routing according to a resource restriction condition, you can  be admissible that the resource restriction condition is not less than the service requirement. When there is a plurality of available LSP routes, other conditions, including that of resource consumption, can be taken into consideration for Select an optimal LSP.

After selecting LSPa as the route intra-domain in the network resource manager carrier 1, BR1 is determined as the output router of the bearer network resource manager 1, according to the content in table 6.

       \ vskip1.000000 \ baselineskip
    

TABLE 6

8

       \ vskip1.000000 \ baselineskip
    

In table 6, the row and column represent, respectively, the output router and the inbound router within the resource manager domain of carrier network 1. The element of the incoming router table and the element of the output router table comprise, respectively, all ER or BR routers in this domain of management, indicating the crossing points of rows and columns in the route aggregation from one ER / BR to another ER / BR. The aggregation of routes, in this table, can have the following status:

(1) Null. The "__" or a space in the table 6 means that there is no route available between the inbound router and outbound router.

(2) There is only one route available. By example, {(LSP1)} in table 6 means that there is only one optimal route between the input router and the router exit; {(LSP3, LSP4)} in table 6 means that this route transmits a plurality of intra-domain LSP.

(3) There are multiple routes. For example, {(LSP5), (LSP2, LSP4)} in Table 6, which are separated by parenthesis, means that there are multiple optimal routes between the inbound router and outbound router.

       \ vskip1.000000 \ baselineskip
    

In step 32, according to the requirement inter-domain LSP bandwidth pre-set, the network resource manager Carrier 1 or 2 selects an LSP that meets the requirement of all inter-domain LSPs between the managers of carrier network resources 1 and 2.

In detail, since BR1 has already been determined as the output router of the resource manager of carrier network 1 in step 31, in the current phase, all inter-domain LSP routes, with BR1 as the point of departure. The bandwidth requirements of these LSP routes and an LSP is selected from these LSP routes of according to the 10M bandwidth requirement and determined carrier network resource manager input router 2 according to the endpoint of the selected LSP route. In In this case, LSP13 is selected as the LSP inter-domains between resource managers of carrier network 1 and 2 and BR3 is determined as input router of the carrier network resource manager 2.

In step 33, according to the requirement of service bandwidth, the network resource manager Carrier 2 selects an LSP that meets the width requirement of service band between all LSP routes intra-domain network resource manager carrier 2 and the output router of the manager of Carrier network 2 resources based on the selected LSP. He method to select an LSP, at the current stage, is similar to the of stage 31 and the determined intra-domain LSP of the carrier network resource manager 2 is LSPb and BR4 and it determines BR4 as the output router of the resource manager of carrier network 2 based on LSPb.

In step 34, adopting the method similar to from step 32, LSP23 is determined as the LSP inter-domains between resource managers of carrier network 2 and 4 and BR5 is determined as the router of carrier network resource manager input 4 based on LSP23, then adopting the method similar to that of the stage 31, the carrier network resource manager 4 determines the LSP route intra-domain network resource manager carrier 4 as LSPc and the output router of the manager carrier network resources 4 as ER3.

In the present example, the information of the LSP bandwidth requirement is stored in each manager of carrier network resources. In other embodiments of the present routing mode, a basis of dedicated data to store the information requirements of LSP bandwidth.

In the present example, if detected, during the routing procedure, which none of the LSP routes selectable can meet the bandwidth requirement of service, the current ER or BR will report a rejection response of recourse to the ER or BR upstream, including the response of resource rejection information about routing failure. TO then the bearer network resource manager, which manages the ER or BR, flow up reports a rejection response of connection resource request to the network resource manager previous jump carrier or CA, which rejects this connection resource request.

According to the method described above, you can set an itinerary "CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager carrier 2 \ rightarrow carrier network resource manager 4 "that meets the service bandwidth requirement. In other embodiments of the current routing mode, the Service bandwidth requirement can be taken in consideration when routing intra-domain or routing inter-domains In addition, other requirements of service can also be taken as conditions of restriction of resources for routing, for example, the condition of resource restriction can be a rule restriction on LSP, specifying the rule which service streams are supported to transmit this LSP and which are not supported.

Adopting the present method, the provider of network services can select a special route for a user with important service requirements for the realization of this service, as for loading this user of according to its service requirements. When establish network plans, service providers can estimate the future flow and limit the LSP accordingly, so that service and performance requirements are met.

Therefore, the present method can perform routing based on resource constraint in terms service request, in terms of selecting a route that meets the bandwidth requirement, so that the Quality Desirable Service can be achieved after the acceptance of the user call In addition, the service provider can set loading criteria, according to the condition of resource constraint preset, in order to implement a Rated load and get the best economic performance. This method is easy to implement, maintain and manage.

       \ vskip1.000000 \ baselineskip
    

The fourth mode: a routing mode according to a established routing strategy

This method adopts the model "Diff-serv" illustrated in Figure 1 for Perform data transmission over a network. In this model, the path of the carrier network control layer comprises the signaling path between network resource managers carrier and service path between CN connection nodes, the service route comprising a route inter-domains and a route intra-domain The routing method of strategies of this routing mode can be applied, in both service and signaling routes. In this case, the node of CN connection indicated above can be ER, BR or other routers such as forwarding routers.

With reference to Figure 22, in a form of realization of the present routing mode, you need establish an itinerary from CA1 to the network resource manager carrier 4, as illustrated in Figure 22, there are five signaling itineraries from CA1 to the network resource manager carrier 4:

Itinerary 1: CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager bearer 2 → network resource manager bearer 4;

Itinerary 2: CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager bearer 3 → network resource manager bearer 4;

Itinerary 3: CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager bearer 5 → network resource manager bearer 4;

Itinerary 4: CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager carrier 2 \ rightarrow carrier network resource manager 5 carrier network resource manager 4;

Itinerary 5: CA1 \ rightarrow manager carrier network resources 1 \ rightarrow network resource manager carrier 3 \ rightarrow carrier network resource manager 5 r carrier network resource manager 4.

       \ vskip1.000000 \ baselineskip
    

In the present example, each resource manager carrier network stores routing information from strategies and conducts a strategy routing between five signaling itineraries according to the information in routing of stored strategy. The specific procedure It is as follows:

In step 41, first and foremost, each manager of Carrier network resources conducts routing in accordance with the status of bandwidth resources. In this example of present routing mode, signaling itineraries 1, 2, 3 and 4 have sufficient bandwidth resources, while signaling itinerary 5 has few resources of width of band. Therefore, signaling itineraries are selected 1, 2, 3 and 4 as candidate routes.

In step 42, each bearer network resource manager performs the routing according to the priority of the service request. In this example of the present routing mode, the service has high priority. Since the signaling itineraries indicated above 1, 2 and 3 satisfy the high priority requirement, while signaling itineraries 4 and 5 do not satisfy said requirement, signaling itineraries 1, 2 and 3 are selected as candidate routes from signaling itineraries mentioned above 1, 2, 3 and 4 selected in the
stage A.

In step 43, the routing is done in according to the current service flow of each route in the network. In this example of the present routing mode, the itineraries of Signaling 2 and 5 have a large current service flow, while signaling itineraries 1, 3 and 4 have a relatively small service flow. Therefore, the signaling itineraries 1 and 3 are selected as routes Candidates that are consistent with the state of service flow current from candidate signaling itineraries 1, 2 and 3 in stage B.

In step 44, the routing is done in according to the IP address of the called user. In this example in this routing mode, the routing strategy prescribe this service for the IP address of this user called to be transmitted through route 3. Therefore, Route 3 is selected from candidate routes 1 and 3 in the stage C.

In this way, the signaling itinerary is determined as: CA1 \ carrier network resource manager
1? Carrier network resource manager 5? Carrier network resource manager 4.

The above description is just an example. of signaling route realization using the carrier network resources and other kinds of strategies can be adopt also to conduct routing in other forms of realization of the current routing mode, such as the number of jumps of an itinerary or IP address of the user doing the call. In addition, as described in the embodiment above, routing with a delete mode by selection can be made by adopting multiple strategies in one determine sequence or routing can be done by adopting each strategy respectively and then you select a relatively optimal route from all selected routes. There are multiple routing strategies in this form of realization of the present routing mode, but can also be only a routing strategy in other ways of realization of the present routing mode.

In the present routing mode, while service route routing is performed, each manager of carrier network resources can also perform a routing intra-domain or inter-domain using routing strategies. Taking the manager of carrier network resources 1 that performs routing intra-domain as an example, referring to the Figure 24, the procedure for carrying out this routing strategic intra-domain, in the present form of realization, is as follows.

       \ newpage
    

It is determined in advance that the router inbound and outbound service router, in the manager of carrier network resources 1, are ER1 and BR1, respectively and are stores a matrix table of route information in the manager Carrier network resources 1 in advance. Checking this table matrix, it is determined that there are two LSP routes with ER1 as inbound router and BR1 as outbound router, which are LSP1 + LSP2 and LSP3 + LSP4.

       \ vskip1.000000 \ baselineskip
    

TABLE 7

9

       \ vskip1.000000 \ baselineskip
    

In table 7, the row and column elements represent, respectively, an outbound router and an inbound router within the domain of the bearer network resource manager 1. The elements of the inbound router table and the elements of The output router table comprises, respectively, all ER or BR routers in this management domain, indicating the crossing points of rows and columns in the aggregation of routes from one ER / BR to another ER / BR. Route aggregation, in this table, can have the operational status
next:

(1) Null. The "__" or a space in the table 7 means that there is no route available between the inbound router and outbound router.

(2) There is only one route available. By example, {(LSP1)} in table 7 means that there is only one optimal route between the input router and the router exit; {(LSP2, LSP4)} in Table 7 means that this route transmits a plurality of LSP routes intra-domain

(3) There are multiple routes. For example, {(LSP5), (LSP3, LSP4)} in Table 7, which are separated by parenthesis, means that there are multiple optimal routes between the inbound router and outbound router.

       \ vskip1.000000 \ baselineskip
    

Since the following strategy is established previously in the carrier network resource manager 1: selecting "LSP1 + LSP2" for the service flow with 10.10.1.0/24 as the destination IP address of the information of path in ER1 of the carrier network resource manager 1, the manager of Carrier network resources 1 will select "LSP1 + LSP2" as the intra-domain route according to this strategy, thereby determining the output router of the manager of carrier network resources 1 such as BR1. The network resource manager Carrier 1 determines an itinerary of "ER1 \ LSP1 ? LSP2? BR1 "accordingly. In the present example, the carrier network resource manager 1 performs routing according to the destination address while that in other examples of this routing mode, the manager of carrier network resources 1 can also perform the strategic routing according to priority, flow of current service, status of bandwidth resources and others factors and the routing method is the same as in the previous.

In the present example, the mode of intra-domain strategic routing of others Bearer network resource managers are the same as the bearer network resource manager 1 while strategies of the bearer network resource managers can be the same or different, which does not affect the performance of this mode of routing

In the present routing mode, each carrier network resource manager can perform a routing  inter-domains for the service path using a strategic routing and routing method specific inter-domains is similar to the method of intra-domain routing.

In the routing procedure strategy described above, if none of the itineraries can satisfy the strategic routing requirement, it will report a connection rejection response to the manager of carrier network resources upstream, where information from routing failure is included in this rejection response of connection. This bearer network resource manager reports the connection rejection response message to resource manager of previous jump carrier network or CA, so that this connection resource request.

In other examples of the present mode of routing, other types of strategies can also be adopted  for routing, for example: the strategy of routing can be a rule restriction on the LSP intra-domain, where this rule restriction includes: what service currents are admitted for transmitted through this LSP and which ones are not, etc.

In the routing mode example present, the strategy information adopted for the routing is stored in each network resource manager carrier, while in other examples of the present mode of routing the strategy information adopted for the routing can also be stored in a database of dedicated strategies, which can be consulted by all managers of carrier network resources.

Adopting the method of this mode of routing, network service providers can select specified routes through routing strategic to perform the corresponding services of the user, as for charging the user according to these service requirements of this user. In addition, the state Prepaid user for the service can be considered as a routing strategy and taken into consideration of the routing When network plans are made, providers of service must correct the network plans in terms of ensuring that sufficient resources can be provided for users

Therefore, the present method can perform routing based on strategies in terms of service request to be able to select a route that meets the bandwidth requirement and thus, can be guaranteed a desirable Quality of Service after the call is accepted of the user. In addition, the service provider can set loading criteria according to the restriction condition of preset resources in order to perform a classified load and get the best economic performance. This method is easy to Implement, maintain and manage.

It should be noted that the description above is a demonstration, and not a limitation, for the present invention.

Claims (17)

1. Method to select a route from real-time service data transmission based on tag switching, where a control layer is established independent carrier network, which comprises more than one manager of carrier network resources (1001, 1002, 1003, 1004, 1005) between a service control layer and a carrier network, corresponding a bearer network resource manager to a single domain and when a carrier network resource manager at source receives a request of connection resource (1201, 1401, 1500) for a service in real time from the service control layer, the method that understands: from a source carrier network resource manager, which determines (1202, 1204, 1206, 1402, 1404, 1406, 1408, 1411,1501) an inter-domain tag switching path, LSP, between each resource manager of jump carrier network and a next hop carrier network resource manager, which sends (1203, 1205, 1403, 1405, 1502) a connection resource request to the next hop carrier network resource manager, until the manager of bearer network resources at destination receive the connection resource request, said method being characterized by: from the destination network resource manager at destination, sending (1207, 1208, 1210, 1407, 1409, 1410, 1506) the inter-domain LSP and an intra-domain LSP of the carrier network resource manager in a resource response of connection to the previous jump bearer network resource manager, until a connection resource response is sent to the source bearer network resource manager, the source bearer network resource manager receiving the connection resource response, obtaining a global LSP route aggregation for the connection resource request,
which is from the carrier network resource manager at source to the carrier network resource manager at destination.

         \ vskip1.000000 \ baselineskip
      

2. The method according to claim 1, wherein each carrier network resource manager has an Internet protocol address, IP, the user making the call and the called user, of the real-time service, identifying
By the IP addresses and the carrier network resource manager selects the LSP based on the IP addresses. 3. Method according to claim 1, which It also includes: transmission of the aggregation of global LSP routes to the entry (1006) of the real-time service flow in the network carrier 4. Method according to claim 1, which It also includes: after receiving the appeal request from connection, for each carrier network resource manager, determine (1202, 1204, 1206) the manager's intra-domain LSP of carrier network resources.

         \ vskip1.000000 \ baselineskip
      

5. Method according to claim 1, which It also includes: through the carrier network resource manager at destination, determine (1406) intra-domain LSP after receiving the connection resource request and through each network resource manager carrier, except the carrier network resource manager in destination, determine (1408, 1410) the LSP intra-domain after receiving the response from connection resource.

         \ vskip1.000000 \ baselineskip
      

6. Method according to any of the claims 1 to 5 further comprising the resource manager of carrier network that selects the LSP according to the strategy of routing. 7. Method according to any of the claims 1 to 5, wherein the mode of selecting the LSP intra-domain comprises: precalculate a set of LSP routes between all the BR and ER routers in the local domain, establishing a intra-domain routing table and consulting said table to obtain the intra-domain LSP of according to the input router and the output router of the local domain or select the LSP intra-domain, stage by stage type, until output router of the LSP currently selected in a BR or ER in the local domain and get the LSP intra-domain comprising at least one LSP or select intra-domain LSP of each jump carrier network resource manager using a intra-matrix matrix route algorithm or select the LSP intra-domain, according to a condition of preconfigured resource constraint or a strategy of routing or select intra-domain LSP of each jump carrier network resource manager, according to an aggregation of routes that includes all the identifiers of incoming IP addresses and IP address identifiers of output, within the management domain of the network resource manager carrier

         \ vskip1.000000 \ baselineskip
      

8. Method according to any of the claims 1 to 5 wherein the connection resource request includes the operational status of the current network and the Quality of Service, QoS. 9. Method according to claim 7, in where the selection of the intra-domain LSP of each jump carrier network resource manager, using an algorithm Intra-domain route matrix includes: calculate at least one set of LSP routes between all BR and ER routers in the local domain; storing at least one set of LSP routes in a matrix table, where, in the matrix table, a row element is an input CN connection node identifier, a column element is an output CN connection node identifier , a pair of row element and column element corresponds to one of at least one set of LSP routes, wherein one of at least one set of LSP routes comprises all LSP routes from an input connection node CN to a output CN connection node, the input CN being identified by the corresponding row element and an output CN connection node identified by the corresponding column element or a row element is an identifier of the output CN node, a column element is an input CN identifier, a pair of a row element and a column element corresponding to one of at least one set of LSP routes, where one of at least one set of LSP routes comprises all LSP routes from an input CN connection node to an output CN connection node, an output CN being identified by the corresponding row element and the input CN is identified by the corresponding element
of column; consult the matrix table, according to the current local domain entry router to get a set of LSP routes in the local domain and select an LSP as the LSP route intra-domain from the set obtained from routes LSP in the local domain, according to the strategy of routing, the operational status of the existing network and some QoS Quality of Service requirements.

         \ vskip1.000000 \ baselineskip
      

10. Method according to claim 7, where the intra-domain LSP route selection of each jump carrier network resource manager, by means of a intra-domain route matrix algorithm understands: calculate at least one set of LSP routes between all BR and ER routers in the local domain; assign segments of IP addresses for BR and ER routers, respectively; store at least one set of LSP routes in a matrix table, said column being a column element the IP address segment of the incoming CN connection node, being a column element the segment of IP addresses of the node CN output connection, corresponding a pair of an element of row and a column element with one of at least one set of LSP routes, where one at least one set of LSP routes comprises all LSP routes from a CN connection node of input to an output CN connection node, the input CN node by the corresponding row element and the node Output CN identified by the corresponding element of column or, a row element is the IP address segment of the CN output node, a column element is the segment of IP addresses of the incoming CN node, a pair of an element of row and a column element correspond to one of at least one LSP route set, where one of at least one set of routes LSP comprises all LSP routes from an incoming CN node to a output CN node, the output CN node being identified by the corresponding row element and the input CN node identifying by the corresponding column element; consult the matrix table according to the IP address segment of the local domain entry CN node to get a set of LSP routes in the local domain and select an LSP as the LSP intra-domain from the set obtained from LSP routes in the local domain, according to the strategy of routing, the operational status of the existing network and some QoS Quality of Service requirements.

         \ vskip1.000000 \ baselineskip
      

11. A carrier network resource manager for select a service data transmission path in time real on the basis of tag switching, where one layer of independent carrier network control, comprising more than one carrier network resource manager (1001, 1002, 1003, 1004, 1005) is established between a service control layer and a network carrier, a carrier network resource manager corresponding to a single domain, the network resource manager circuits being carrier adapted for: receive a connection resource request for a real-time service from the service control layer, determine (1202, 1204, 1206, 1402, 1404, 1406, 1408, 1411, 1501, 1502) an inter-domain LSP between the bearer network resource manager and a next hop bearer network resource manager and the bearer network resource manager characterized by circuits adapted to: send (1207, 1208, 1210, 1407, 1409, 1410, 1506) the inter-domain LSP and an LSP intra-domain network resource manager carrier to the previous jump carrier network resource manager, that is transported in a connection resource response.

         \ vskip1.000000 \ baselineskip
      

12. Bearer network resource manager of according to claim 11, being further adapted for use Internet protocol, IP address and being the part that called and the called part of the real-time service identified by the IP addresses and select the LSP based on the IP addresses. 13. Bearer network resource manager according to claim 11, being further adapted for transmit the aggregation of global LSP routes to the flow inlet of real-time service in the carrier network. 14. Bearer network resource manager according to any of claims 11 to 13, being also adapted to select the LSP according to the strategy of routing. 15. Bearer network resource manager according to any of claims 11 to 13, being also adapted to use the following mode to select the Intra-domain LSP: precalculate a set of LSP routes between all the BR and ER routers in the local domain, establishing a intra-domain routing table and consulting the intra-domain routing table for obtain intra-domain LSP according to the inbound router and local domain outbound router or select the LSP intra-domain, jump by jump, until the Output router of the currently selected LSP is either a BR or an ER in the local domain and get the LSP intra-domain comprising at least one LSP or select intra-domain LSP of each jump carrier network resource manager using a intra-domain route matrix algorithm or select intra-domain LSP according to a resource restriction condition preconfigured or routing strategy or select intra-domain LSP of each jump carrier network resource manager, according to an aggregation of routes that includes all the identifiers of incoming IP addresses and IP address identifiers of output, within the management domain of the network resource manager carrier

         \ vskip1.000000 \ baselineskip
      

16. Bearer network resource manager of according to claim 11, wherein, when the manager of carrier network resources is not a network resource manager carrier in origin, the manager's intra-domain LSP of carrier network resources is the connection resource response that is sent to the previous carrier of network resources carrier of jump that is determined by the carrier network resource manager after receiving the connection resource request. 17. Bearer network resource manager of according to claim 11, wherein, when the manager of carrier network resources is not a network resource manager carrier at source or a carrier network resource manager in target, the intra-domain LSP of the resource manager of carrier network, in the connection resource response, which send to the previous jump carrier network resource manager it determined by the carrier network resource manager after receive the connection resource response and when the carrier network resource manager is a carrier network resource manager at destination, the LSP intra-domain network resource manager bearer, in the connection resource response, which is sent to the Previous jump carrier network resource manager is determined by the carrier network resource manager after receiving the connection resource request.