Method for implementing resource applications of multiple service flows

Abstract

The invention discloses a method for implementing resource applications of multiple service flows, including: receiving by a connection manager (CM) a connection resource request message including resource applications of at least two service flows; allocating paths and reserving resources for the service flows by the CM; sending by the CM the paths allocated for the service flows and resources reserved for the service flows to an edge router of a bearer network accessed by the service flows. With the method, resource applications of multiple service flows may be accomplished in one service connection, thereby providing support for rich QoS services of the application layer, reducing the time of signaling exchange between devices, saving the network traffic and the time of resource applications

Description

FIELD OF THE INVENTION

The invention relates to the field of network communications, and in particular, to a method for implementing resource applications of multiple service flows.

BACKGROUND OF THE INVENTION

With the development of the Internet techniques and the increase of user requirements, a variety of multimedia services emerge. The multimedia services appearing in the network may occupy a lot of bandwidth resources. Consequently, the appearance of the services such as a File Transfer Protocol (FTP) service of high burst level or a Hyper Text Transfer Protocol (HTTP) service containing an image file in the network may have a significant effect on the real time services sensitive to transmission delay, delay jittering and the like, which may results in unreliable transmission of critical services in the network. In view of this, various Quality of Service (QoS) techniques are presented. The Internet Engineering Task Force (IETF) has developed many service models and mechanisms to meet the QoS requirements.

At present, in most applications, an integrated service (Int-Serv) model is utilized at the access part and edges of the network, and a differentiated service (Diff-Serv) model is utilized at the core of the network. In the differentiated service (Diff-Serv) model, the effect of QoS guarantee is unpredictable because only priority level guarantee is set as a QoS guarantee. Therefore, an independent bearer control layer is introduced into the Diff-Serv of backbone networks, and a set of special Diff-Serv QoS signaling mechanism is established. In other words, a resource management layer is established for the Diff-Serv, to manage the topology resources of the networks. The Diff-Serve for resource management is referred to as the Diff-Serv model with an independent bearer control layer.

In the Diff-Serv model with an independent bearer control layer, management rules and network topology are configured in a connection manager (CM) (including a bandwidth broker or a QoS server or a QoS resource manager), in order to allocate resources for service bandwidth applications of users. As shown in FIG. 1, the service bandwidth application requests from users and the results of the service bandwidth application requests, as well as the path information allocated by the CM for service applications, etc., are transmitted by signaling between the bearer network control servers of management domains. Usually, a route table is simulated for each Core Network-device (CN) on the CM, in order to implement the intra-domain route selection of every CM in the bearer control layer, as well as the service routing. The resource requests of each specific service type (i.e., the specific traffic flow) are bound with a series of Label Switch Path (LSP). In other words, the resources of the corresponding LSPs are utilized. The resources of the corresponding LSPs as well as other resources are released when a call is ended.

The particular process is as follows: the bearer control layer determines the path of a service flow of a user when the bearer control layer processes a service bandwidth application of the user. The connection manager then notifies an edge router to forward the service flow along the specified path. The bearer network usually establishes an LSP along the path of the service flow specified by bearer control layer in a resource reservation manner by using the Multiple Protocol Label Switch (MPLS) technique, and establishes an end-to-end LSP by using the route showing mechanism of Resource Reservation Protocol-Traffic Engineering (RSVP-TE) or Constraint-based Label Distribution Protocol (CR-LDP).

In the related art, another solution for resource management employs a QoS server as the QoS management unit in a network. In implementation, a policy server, a directory server and a network management monitoring server matched with the QoS server are also included in the solution. The policy server is adapted to set parameters of related routers and configure the related routers according to the policy configuration information such as the information about the QoS server and management interfaces. The directory server is a unified and concentrated database for storing network device configuration information, user information and QoS information. The network management monitoring server is responsible for collecting information such as block state of routers and links of the bearer network, etc.. The information may be used as a reference for the QoS server in selecting route for service applications.

The QoS server is responsible for allocating a bearer route satisfying the QoS requirements based on the network topology and resource condition for QoS requests of services. Therefore, it is necessary to preset the topology and bandwidth condition in the QoS server and pre-configure rules for route selection. When a service server sends a bandwidth request to the QoS server, the QoS server records the bandwidth request of the call, allocates a bearer route according to the QoS requirements, the current topology and resource condition of the bearer network for the bandwidth request, and returns the result of allocation to the service server.

In addition, the QoS server may send an LSP policy modification command to the policy server according to the bandwidth occupation condition of the service. The policy server then configures an edge router according to the LSP policy modification command from the QoS server. The edge router therefore reestablishes or adjusts the LSP, using the route showing technique of MPLS LSP, according to the path specified by the QoS server.

In independently operated networks, the above described solutions implement QoS resource management for various traffic flows. Thus, when a user performs a service in a network, the user may apply for QoS resources for the service. At present, in the implementations of the above described solutions, when requesting QoS resources, one service connection is needed to be established for each service flow so as to request the QoS resources. If a communication process contains multiple service flows applying for QoS resources, it is necessary to establish multiple service connections for exchanging signaling based on the service connections, so as to implement QoS resource applications of the multiple service flows.

As can be seen, in the above described solutions for resource applications of various service flows, the amount of the signaling exchanged is large. Accordingly, it will take a relatively long time for resource applications in one communication process.

SUMMARY OF THE INVENTION

The invention provides a method for implementing resource applications of multiple service flows, to accomplish the resource applications of multiple service flows in one service connection, so as to reduce the number of signaling to be exchanged during the resource applications of the multiple service flows, and to reduce the time of the resource applications.

The invention provides the following technical solutions:

The invention provides a method for implementing resource applications of multiple service flows. The method includes:

receiving, by a connection manager (CM), a connection resource request message including resource applications of at least two service flows;

allocating paths and reserving resources for the service flows by the CM;

sending, by the CM, the paths allocated for the service flows and resources reserved for the service flows to an edge router of a bearer network accessed by the service flows.

Optionally,

the connection resource request message of the at least two service flows are sent to the CM by a core network device of the bearer network via a call agent.

Optionally, the method includes:

determining, by the CM, an edge router or a border router of a CM domain through which the service flows pass according to address information saved in the CM;

allocating paths and reserving resources for the service flows in the CM domain based on the edge router or the border router.

The paths may be Label Switch Paths.

The paths allocated for the service flows and resources reserved for the service flows may be saved in the CM.

The method may also include:

determining an inter-domain route and a next hop CM for each of the service flows, and sending the connection resource request message of the service flows to the next hop CM.

Optionally, different inter-domain paths and different next-hop CMs may be determined for the service flows, the connection resource request messages of the service flows are sent to the different next-hop CMs via the different inter-domain paths; or

a same inter-domain path and a same next-hop CM may be determined for the service flows, the connection resource request message containing information of the service flows is sent to the same next-hop CM via the same inter-domain path.

The method may also include:

returning connection resource acknowledgement responses to CMs through which the service flows pass, until the connection resource acknowledgement responses reach a source CM, after the connection resource request message of the service flows contained in a service connection reaches a destination CM and the destination CM accomplishes path allocation and resource reservation.

The method may also include:

initiating, by a source CM, a flow mapping command, and delivering the paths allocated for the service flows and resources reserved for the service flows to the edge router of the bearer network accessed by the service flows, when the source CM receives the connection resource acknowledgement responses of the service flows.

The service flows correspond to a same destination CM, or different destination CMs.

An embodiment of the invention provides a system for implementing resource applications of multiple service flows, including: means for receiving a connection resource request message comprising resource applications of at least two service flows; means for allocating paths and reserving resources for the service flows; and means for sending the paths allocated for the service flows and resources reserved for the service flows to an edge router of a bearer network accessed by the service flows.

As can be seen, in the above technical solutions, resource applications of multiple service flows may be accomplished in one service connection, thereby providing support for rich QoS services of the application layer, reducing the time of signaling exchange between devices, saving the network traffic and the time of resource applications. With the method according to the invention, in the case that one communication process contains multiple service flows applying for QoS resources, the time for establishing signaling connection may be reduced significantly, and the amount of signaling exchanged during resource application may be decreased.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing the network module of an independent bearer control layer;

FIG. 2 is a schematic diagram showing the mapping relationship between types of services and the LSPs bearing the services;

FIG. 3 shows a flow A of a method according to the invention;

FIG. 4 is a flow chart showing resource applications in one service connection as shown in FIG. 3;

FIG. 5 shows a flow B of a method according to the invention;

FIG. 6 is a flow chart showing resource applications in one service connection as shown in FIG. 5.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In a full service bearing Internet Protocol (IP) telecommunication network, services with various QoS requirements are usually borne over various Label Switch Paths (LSPs). The connection manager is required to save information about the mapping relationship between the services and the LSPs bearing the services. As shown in FIG. 2, the audio service, the video service, the internet services, and the like, correspond to different LSPs respectively. In other words, different types of services are transferred in the network via different LSPs, so as to provide different levels of QoS guarantee for the different types of services.

Thus, in the full service bearing IP telecommunication network, there may be the case that one communication process needs to implement QoS resource applications for multiple service flows. The invention is to reduce the number of exchanged signaling in the network in this case, therefore decrease the time cost on the resource applications.

In the invention, resource applications for different service flows are performed simultaneously on connection servers (CMs) during one service connection. Therefore, in the network, resources for different service flows are provided with different levels of QoS guarantee.

In other words, one or more resource requests, having the same source address and destination address, as well as different bandwidth requirements, may be accomplished in one resource application according to the invention. A message indicating success of the resource application is returned only when each of the path resource applications for the service flows is successful per hop. During the resource application, when initiating a resource request to a next hop CM, a resource request message may be sent to the same CM or multiple CMs to request the resources of the service flows.

In the invention, the number of the service flows requesting resources at the same time may be set based on the hardware performance of devices, i.e., the connection managers.

FIG. 3 and FIG. 4 show an implementation of a method according to the invention. In FIG. 4, different service flows are required to pass through the same CMs. In other words, FIG. 4 shows a process of resource application allowing intra-domain divergence and inter-domain convergence. This solution facilitates the network planning and management, and is applicable to medium-to-large scale of networks.

The procedure as shown in FIG. 3 and FIG. 4 is as follows:

31: a call agent (CA) sends a connection resource request message to a CM, the connection resource request message contains resource applications for multiple service flows.

In an example, the connection resource request message may include a resource application for an audio service and a resource application for a video service. The service flows of the audio service and the video service correspond to different resource application amounts of bandwidth. The bandwidth applied for the audio service is 64 kbps, and the bandwidth applied for the video service is 483 kbps.

32: when receiving the connection resource request message, the CM saves connection information of the service flows, and determines the information of edge routers (ERs) or border routers (BRs) of the service flows.

If the CM is a source CM, the CM determines the home ERs of the source IP addresses of the service flows according to the source IP address information stored in quintuples.

If the CM is a non-source CM, the CM determines the address sequence of an ingress BR of local CM domain. For example, in a hop-by-hop routing algorithm, the ingress BR of the local CM domain is determined after the last hop CM selects an inter-domain LSP. In other words, the egress router of the inter-domain LSP is the ingress BR of the local CM domain.

33, the CM selects routes, i.e., allocates paths and reserves resources, for the service flows using a service routing algorithm in the local CM domain.

As in the above example, in 33, the CM firstly applies for intra-domain LSP resource for the first type of service, i.e., the audio service, allocates bandwidth after an idle LSP capable of bearing the audio service is found, and records the information. Then, the CM applies for intra-domain LSP resource for the second type of service, i.e., the video service, finds an idle LSP for the video service, allocates bandwidth and records the information.

Then, the CM allocates routes and resources hop by hop in the topology of the CM in like manner. It should be noted that, when selecting routes and allocating resources for different service flows in the domain, the same sequence of Core Network-devices (CNs) may be used, because the starting points of the service connections are the same ER. If there is no LSP suitable for a service flow between the CNs, a different sequence of CNs in the domain may be used. In other words, the LSPs passing through different devices may be selected for different service flows in a CM domain.

34: after the intra-domain resource application is completed, the CM selects inter-domain routes using the signaling routing algorithm.

For instance, the CM initiates a QoS resource request to the next hop CM using the hop-by-hop algorithm, the QoS resource request includes the address of the next hop CM and the egress BR corresponding to an LSP set going out of the domain, in addition to the QoS parameters and service type, etc.

As in the above example, the LSP set includes an LSP#1 of audio type and an LSP#2 of video type. The LSP#1 and the LSP#2 may have a same egress BR, or may have different egress BRs. However, the two LSPs have a same next hop CM.

All the CMs through which the service flows pass, except the destination CM, are required to execute the procedure from 32 to 34, until the connection resource request message reaches the destination CM.

35, after receiving the connection resource request message, the destination CM completes the allocation of service routes and LSP resources, and returns a resource acknowledgement response to its last hop CM.

Each of the CMs, except the source CM, sends the LSP resources returned by the next hop CM and the LSP resources of the each of the CMs to the last hop CM using the resource acknowledgement response, until the resource acknowledgement response reaches the source CM.

36: After receiving the resource acknowledgement response, the source CM initiates a 10 flow mapping command, and delivers to the ER the information of the allocated paths and reserved resources including session ID (identification), information of multiple service flows, QoS parameters, traffic descriptor and label stack of whole path, etc.

FIG. 5 and FIG. 6 show another implementation of a method according to the invention. In the implementation as shown in FIG. 5 and FIG. 6, the service flows are not required to pass through the same CMs, however, the service flows are required to have the same source CM and the same destination CM. As shown in FIG. 5 and FIG. 6, when a CA sends a connection resource request message to a CM, the subsequent processing procedure is as follows:

51: The CA sends connection resource request messages to a CM, the connection resource request messages contain resource applications for multiple service flows.

Similarly, the connection resource request messages may include a resource application for an audio service and a resource application for a video service.

52: when receiving the connection resource request messages, the CM saves connection information of the service flows, and determines information of edge routers (ERs) or border routers (BRs) of the service flows.

If the CM is a source CM, the CM determines the home ERs of the source IP addresses of the service flows according to the source IP address information stored in quintuples.

If the CM is a non-source CM, the CM determines the address of an ingress BR of local CM domain. For example, in the hop-by-hop routing algorithm, the ingress BR of the local CM domain is determined after the last hop CM selects an inter-domain LSP. In other words, the egress router of the inter-domain LSP is the ingress BR of the local CM domain.

53: the CM selects routes, i.e., allocates paths and reserves resources, for the service flows using the service routing algorithm in the local CM domain.

As in the above example, the CM firstly applies for intra-domain LSP resource for the first type of service, i.e., the audio service, allocates bandwidth after an idle LSP capable of bearing the audio service is found, and records the information. Then, the CM applies for intra-domain LSP resource for the second type of service, i.e., the video service, finds an idle LSP for the video service, allocates bandwidth and records the information.

Then, the CM allocates routes and resources hop by hop in the topology of the CM in like manner. It should be noted that, when selecting routes and allocating resources for different service flows in the domain, the same sequence of Core Network-devices (CNs) may be used, because the starting points of the service connections are the same ER. If there is no LSP suitable for a service flow between the CNs, a different sequence of CNs in the domain may be used.

The procedure from 51 to 53 is similar to that from 31 to 33 as shown in FIG. 3, the difference lies in the subsequent procedure: the connection resource request messages corresponding to different service flows may reach the destination CM, passing through different CMs.

54: after the intra-domain resource application is completed, the CM selects inter-domain routes for the service flows using the signaling routing algorithm.

For instance, the CM initiates a QoS resource request to the next hop CM using the hop-by-hop algorithm, the QoS resource request includes the address of the next hop CM and egress BRs corresponding to LSP sets going out of the domain, in addition to the QoS parameters and service type, etc.. The egress BRs corresponding to different service flows may be a same BR, or may be different BRs. When the egresses BRs are different, the opposite BRs may correspond to a same CM, or may correspond to different CMs. FIG. 6 shows an example of different CMs.

55: the CM computes service routes and path resources for the service flows.

All the CMs, except the destination CM, are required to execute repeatedly the procedure from 52 to 54, until the connection resource request messages of all the service flows reach the destination CM.

56: the destination CM completes the allocation of service routes and LSP resources, and then returns resource acknowledgement responses to its last hop CM.

Each of the CMs, except the source CM, sends the LSP resources returned by the next hop CM and the LSP resources of the each of the CMs to the last hop CM using the resource acknowledgement responses, until the resource acknowledgement responses reach the source CM.

57: After receiving the resource acknowledgement responses corresponding to the service flows, i.e., the resource acknowledgement responses corresponding to all the service flows in the connection, the source CM initiates a flow mapping command, and delivers to the ER the information of the allocated paths and reserved resources including session ID (identification), information of multiple service flows, QoS parameters, traffic descriptor and label stack of whole path, etc.

In the invention, if one service connection is a point-to-point communication, multiple service flows are required to reach the same destination CM. If one service connection is a point-to-multi-points communication, the multiple service flows are allowed to have different destination CMs. Different service flows have a same source CM, and are allowed to have different intermediate CMs. This is a connection resource application process allowing both intra-domain divergence and inter-domain divergence. This connection resource application process has a higher requirement for network planning and management, and utilizes a relatively complex technique for the source CM and the destination CM, as well as a relatively simple technique for the intermediate CMs. This connection resource application process is applicable to small-to-medium scale of networks.

Though some embodiments of the present invention are described above, the present invention shall not be limited thereto. It shall be recognized by a person of ordinary skill in the art that various modifications and variations readily made thereto in light of the disclosure of the invention shall be covered within the protection scope of the present invention as defined by the accompanying claims.

Claims

1. A method for implementing resource applications of multiple service flows, comprising: receiving, by a connection manager, a connection resource request message comprising resource applications of at least two service flows; allocating paths and reserving resources for the service flows by the connection manager; sending, by the connection manager, the paths allocated for the service flows and resources reserved for the service flows to an edge router of a bearer network accessed by the service flows.

2. The method for implementing resource applications of multiple service flows according to claim 1, wherein the connection resource request message of the at least two service flows are sent to the connection manager by a core network device of the bearer network via a call agent.

3. The method for implementing resource applications of multiple service flows according to claim 1, wherein the allocating paths and reserving resources for the service flows further comprises: determining an edge router or a border router of a connection manager domain through which the service flows pass according to address information saved in the connection manager; allocating paths and reserving resources for the service flows in the connection manager domain based on the edge router or the border router.

4. The method for implementing resource applications of multiple service flows according to claim 3, wherein the said paths are Label Switch Paths.

5. The method for implementing resource applications of multiple service flows according to claim 4, wherein the paths allocated for the service flows and resources reserved for the service flows are saved in the connection manager.

6. The method for implementing resource applications of multiple service flows according to claim 3, further comprising: determining an inter-domain route and a next hop connection manager for each of the service flows, and sending the connection resource request message of the service flows to the next hop connection manager.

7. The method for implementing resource applications of multiple service flows according to claim 6, wherein different inter-domain paths and different next-hop connection managers are determined for the service flows, the connection resource request messages of the service flows are sent to the different next-hop connection managers via the different inter-domain paths; or a same inter-domain path and a same next-hop connection manager are determined for the service flows, the connection resource request message containing information of the service flows is sent to the same next-hop connection manager via the same inter-domain path.

8. The method for implementing resource applications of multiple service flows according to claim 7, further comprising: returning connection resource acknowledgement responses to connection managers through which the service flows pass, until the connection resource acknowledgement responses reach a source connection manager, after the connection resource request message of the service flows contained in a service connection reaches a destination connection manager and the destination connection manager performs path allocation and resource reservation.

9. The method for implementing resource applications of multiple service flows according to claim 8, further comprising: initiating, by a source connection manager, a flow mapping command, and delivering the paths allocated for the service flows and resources reserved for the service flows to the edge router of the bearer network accessed by the service flows, when the source connection manager receives the connection resource acknowledgement responses of the service flows.

10. The method for implementing resource applications of multiple service flows according to claim 8, wherein the service flows correspond to a same destination connection manager, or different destination connection managers.

11. The method for implementing resource applications of multiple service flows according to claim 2, wherein the allocating paths and reserving resources for the service flows further comprises: determining, by the connection manager, an edge router or a border router of a connection manager domain through which the service flows pass according to address information saved in the connection manager; allocating paths and reserving resources for the service flows in the connection manager domain based on the edge router or the border router.

12. The method for implementing resource applications of multiple service flows according to claim 11, wherein the said paths are Label Switch Paths.

13. A system for implementing resource applications of multiple service flows, comprising: means for receiving a connection resource request message comprising resource applications of at least two service flows; means for allocating paths and reserving resources for the service flows; and means for sending the paths allocated for the service flows and resources reserved for the service flows to an edge router of a bearer network accessed by the service flows.

14. The system for implementing resource applications of multiple service flows according to claim 13, wherein the means for allocating paths and reserving resources for the service flows further comprises: means for determining an edge router or a border router of a connection manager domain through which the service flows pass according to address information saved in a connection manager; means for allocating paths and reserving resources for the service flows in the connection manager domain based on the edge router or the border router.

15. The system for implementing resource applications of multiple service flows according to claim 14, further comprising: means for saving the paths allocated for the service flows and resources reserved for the service flows.

16. The system for implementing resource applications of multiple service flows according to claim 14, further comprising: means for determining an inter-domain route and a next hop connection manager for each of the service flows, and means for sending the connection resource request message of the service flows to the next hop connection manager.

17. The system for implementing resource applications of multiple service flows according to claim 16, wherein different inter-domain paths and different next-hop connection managers are determined for the service flows, the connection resource request messages of the service flows are sent to the different next-hop connection managers via the different inter-domain paths; or a same inter-domain path and a same next-hop connection manager are determined for the service flows, the connection resource request message containing information of the service flows is sent to the same next-hop connection manager via the same inter-domain path.

18. The system for implementing resource applications of multiple service flows according to claim 17, further comprising: ,means for returning connection resource acknowledgement responses to connection managers through which the service flows pass.

19. The system for implementing resource applications of multiple service flows according to claim 18, further comprising: means for initiating a flow mapping command and for delivering the paths allocated for the service flows and resources reserved for the service flows to the edge router of the bearer network accessed by the service flows when a source connection manager receives the connection resource acknowledgement responses of the service flows.