CN102025688A - Network resource management method and system - Google Patents
Network resource management method and system Download PDFInfo
- Publication number
- CN102025688A CN102025688A CN2009101699756A CN200910169975A CN102025688A CN 102025688 A CN102025688 A CN 102025688A CN 2009101699756 A CN2009101699756 A CN 2009101699756A CN 200910169975 A CN200910169975 A CN 200910169975A CN 102025688 A CN102025688 A CN 102025688A
- Authority
- CN
- China
- Prior art keywords
- rsvp
- message
- path
- client
- bng
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 15
- 238000013507 mapping Methods 0.000 claims abstract description 47
- 238000000034 method Methods 0.000 claims abstract description 17
- 230000003993 interaction Effects 0.000 claims description 18
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a network resource management method which comprises the following steps: generating a strategy parameter and transmitting the strategy parameter to the strategy executing functive of a first hop router of a bearing surface based on the information of the requested service, subscription information of a user, and the information of the bearing surface accessed by the user currently which are all carried by a received strategy request; mapping the received strategy parameter to an RSVP (resource reservation protocol) object at the protocol end of RSVP of the first hop router by the strategy executing functive; and transmitting the RSVP object to each RSVS client by the RSVP protocol end through an RSVP path message, and reserving bandwidth for the requested service by each RSVP client based on the RSVP object. The invention also discloses a network resource management system, which comprises a strategy server, the strategy executing functive, the RSVP protocol end and the RSVP clients. By the method and the system, the quality of service requiring high speed transmission can be ensured.
Description
Technical Field
The present invention relates to the field of wireless communications, and in particular, to a network resource management method and system.
Background
The characteristics of simplicity, rapidness, sharing and the like of the IP network bring prosperity of the broadband network, but a large amount of services also cause network resource shortage, the transmission speed of the services cannot be ensured, and further the quality of services needing high-speed transmission, such as video services, instant services and the like, cannot be ensured, and user experience is influenced.
The current common network resource management method is as follows: the priority is allocated to various services, bandwidth resources are allocated to the services according to the priority of each service, but with the continuous development of video services, instant services and other services, the types and the number of high-priority services are suddenly increased, and a large number of high-priority services, especially a large number of video services occupying large bandwidth, still make network resources nervous, and even possibly cause network overload.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for managing network resources, which can ensure the quality of services requiring high-speed transmission.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
when a policy server receives a policy request sent by an application service server, the method comprises the following steps:
generating a policy parameter according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user, which are carried by the received policy request, and issuing the policy parameter to a policy execution functional body of a first-hop router of the bearing surface;
the strategy executing functional body maps the received strategy parameters to RSVP objects of a resource reservation protocol RSVP protocol end of the first-hop router; and the RSVP protocol end transmits the RSVP object to RSVP clients of other routers except the first-hop router of the bearing surface through RSVP path information, and each RSVP client reserves bandwidth for the requested service according to the RSVP object.
Further, the policy parameters include: IP quintuple of the requested service, QoS requirement parameter, and IP address and receiving port number of the user gateway BNG;
the RSVP object includes: a session field, a sender template field and a sender specification sender _ TSPEC field;
the RSVP object that maps the received policy parameters to the RSVP protocol end is:
mapping the IP address and the receiving port number of the BNG included by the strategy parameter to a receiving address field and a receiving port field of the session field respectively, and mapping the protocol number in the IP quintuple included by the strategy parameter to a protocol ID field included by the session field;
respectively mapping a source IP address and a source port number in an IP five-tuple included in the strategy parameters to a sender address field and a sender port field included in the sender template field;
and mapping the QoS requirement parameter included by the strategy parameter to the sender _ TSPEC field.
Further, the RSVP protocol end transmits the RSVP object to RSVP clients of the other routers except the first-hop router through the RSVP path message:
the RSVP protocol end generates RSVP path message of carried RSVP object, and transmits to RSVP client of user gateway BNG of bearing surface through RSVP client of each router of bearing surface;
the steps of reserving the bandwidth for the requested service by each RSVP client according to the RSVP object comprise:
a1, the RSVP clients of the other routers except BNG create path state according to RSVP object carried by RSVP path message sent by the previous-hop router, and forward the RSVP path message sent by the previous-hop router to the next-hop router, until the RSVP path message reaches the RSVP client of BNG, execute step b 1;
b1, the RSVP client of BNG creates path state according to RSVP object carried by RSVP path message, calculates bandwidth needed to be reserved for the requested service, reserves calculated bandwidth for the requested service, and sends RSVP path message back to RSVP protocol end through RSVP client of the rest routers of bearing surface;
c1, the RSVP clients of the other routers except BNG calculate the bandwidth needed to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message sent by the next-hop router, reserve the calculated bandwidth for the requested service, and forward the returned RSVP path message sent by the next-hop router to the previous-hop router; and until the RSVP protocol end receives the returned RSVP path message, replying a reservation completion message to the policy server through the policy execution function body.
Further, when the transmission of the requested service is completed or the requested service is terminated, the method further includes: and releasing the reserved resources.
Further, the releasing the reserved resources comprises:
a2, when the policy server receives the resource release request from the application service server, the policy server sends the bandwidth release notice to the policy execution functional body;
b2, the strategy executing functional body maps the IP quintuple corresponding to the requested service carried by the received bandwidth releasing notice, the IP address and the receiving port number of the BNG to the RSVP path deleting RSVP path tear object of the RSVP protocol end; the RSVP protocol end generates RSVP path tear object RSVP path tear message carrying RSVP path tear object and transmits the RSVP path tear message to the RSVP client end of the bearing surface BNG;
c2, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the previous-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forward the RSVP path tear message to the next-hop router until the RSVP path tear message reaches the BNG, execute step d 2;
d2, the RSVP client of BNG deletes the path state corresponding to the RSVP path tear object carried by the received RSVP path tear message, and releases the resource corresponding to the RSVP path tear object carried by the received RSVP path tear message; and replying a release completion message to the policy server through the RSVP client, the RSVP protocol end and the policy execution function of the rest routers of the bearing surface.
Further, the releasing the reserved resources comprises:
a3, BNG RSVP client end deletes the path state corresponding to the requested service, and after releasing the resource occupied by the requested service, generates RSVP path tear message and transmits to RSVP protocol end through the RSVP client end of each router except BNG on the bearing surface;
b3, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the next-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router until the RSVP path tear message reaches the RSVP protocol end, execute step c 3;
c3, after the RSVP path tear message reaches the RSVP protocol end, the RSVP protocol end replies the release completing message to the strategy server through the strategy executing function body.
The invention also provides a network resource management system, which comprises: the system comprises a policy server, a policy execution functional body, an RSVP protocol end and RSVP clients, wherein the policy server is introduced into a control surface and is respectively connected with a bearing surface and an application service server, the policy execution functional body and the RSVP protocol end are arranged on a first-hop router of the bearing surface, and the RSVP clients are arranged on the other routers except the first-hop router of the bearing surface; wherein,
the policy server is used for generating policy parameters and issuing the policy parameters to the policy execution functional body according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user, which are carried by the received policy request when receiving the policy request sent by the application service server;
the strategy executing function body is used for mapping the received strategy parameters to the RSVP object of the RSVP protocol end;
the RSVP protocol end is used for transmitting the RSVP object to each router of the bearing surface through the RSVP path message;
and the RSVP client is used for reserving the bandwidth for the requested service according to the RSVP object.
Further, the RSVP object includes: a session field, a sender template field, and a sender _ TSPEC field;
the policy enforcement function includes: the system comprises an interaction module, a session mapping module, a template mapping module and a specification mapping module; wherein,
the interaction module is used for receiving the strategy parameters sent by the strategy server;
a session mapping module, configured to map an IP address and a receiving port number of a BNG included in a received policy parameter to a receiver address field and a receiver port field included in the session field, respectively, and map a protocol number in an IP five-tuple included in the received policy parameter to a protocol ID field included in the session field;
a template mapping module, configured to map a source IP address and a source port number in an IP five-tuple included in the received policy parameter to a sender address field and a sender port field included in the sender template field, respectively;
and the specification mapping module is used for mapping the QoS requirement parameters included in the received strategy parameters to the sender _ TSPEC fields.
Furthermore, the RSVP protocol end comprises a message generation module and a message receiving and sending module; wherein,
the message generating module is used for generating RSVP path messages of the carried RSVP objects;
the message receiving and sending module is used for transmitting the RSVP path message to the RSVP client of the bearing surface BNG through the RSVP client of each router of the bearing surface; when receiving the returned RSVP path message, replying a reservation completion message to the policy server through the interaction module;
the RSVP client is a router client when arranged on the rest routers of the bearing surface except the BNG; the RSVP client is a BNG client when being arranged on the BNG; wherein,
the router client is used for establishing a path state according to the received RSVP object carried by the previous RSVP path message and forwarding the RSVP path message sent by the previous hop router to the next hop router; calculating the bandwidth required to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message sent by the next hop router, reserving the calculated bandwidth for the requested service, and forwarding the returned RSVP path message sent by the next hop router to the previous hop router;
the BNG client is used for establishing a path state according to the RSVP object carried by the RSVP path message sent by the previous hop router, calculating the bandwidth required to be reserved for the requested service, reserving the calculated bandwidth for the requested service, and sending the RSVP path message back to the message receiving and sending module of the RSVP protocol end through each router client.
Further, the policy server is further configured to send a bandwidth release notification to the policy executing function when receiving a resource release request sent by the application service server;
the interaction module is further used for receiving a bandwidth release notification sent by the policy server;
the session mapping module, the template mapping module and the specification mapping module are further configured to map an IP quintuple corresponding to the requested service carried by the received bandwidth release notification, and the IP address and the receiving port number of the BNG to an RSVP path delete RSVP path tear object at the RSVP protocol end;
the message generating module is also used for generating RSVP path tear object RSVP path tear message carrying RSVP path tear object;
the message receiving and sending module is further configured to transmit the RSVP path tear message to an RSVP client of the bearer BNG;
the router client is used for receiving the RSVP path tear message sent by the previous hop router, deleting the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, releasing the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forwarding the RSVP path tear message to the next hop router;
the BNG client is configured to receive the RSVP path tear message, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, and reply the release completion message to the policy server through the RSVP clients, the message transceiver module, and the interaction module of the other routers on the bearing surface after releasing the RSVP path tear object carried by the RSVP path tear message.
Further, the BNG client is further configured to delete the path state corresponding to the requested service, and after releasing the resources occupied by the requested service, generate an RSVP path tear message and transmit the RSVP path tear message to the message transceiver module through the RSVP clients of the routers on the bearer side except the BNG;
the router client is further configured to receive an RSVP path tear message sent by a next-hop router, delete a path state corresponding to an RSVP path tear object carried in the RSVP path tear message, release resources corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router;
the message receiving and sending module is also used for replying a release completion message to the policy server through the interaction module.
The method and the system for managing the network resources provided by the invention have the advantages that the strategy server maps the strategy parameters to the RSVP protocol end through the strategy execution function body of the first-hop router, the RSVP protocol end and the RSVP client end reserve resources for the requested service according to the strategy parameters, the resource management is realized, the resources can be specifically reserved for the service currently requested by the user, the quality of the service needing high-speed transmission can be ensured, and the problem that the service transmission speed is influenced by network resource shortage so as to influence the user experience is solved. The invention also has the following advantages and characteristics:
when the service is completed or terminated, the network resources occupied by the service are released so as to be used by other services, thereby solving the problem of network resource shortage.
Drawings
FIG. 1 is a flowchart illustrating a method for managing network resources according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a network resource management system according to an embodiment of the present invention.
Detailed Description
The implementation flow of the network resource management method of the embodiment of the invention is shown in fig. 1, and comprises the following steps:
step 101: when the strategy server receives a strategy request sent by an application service server, generating strategy parameters according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user carried by the received strategy request, and issuing the strategy parameters to a strategy execution functional body of a first-hop router (first-hop router) of the bearing surface;
wherein the policy parameters include: the IP quintuple of the requested service, the QoS requirement parameter, and the IP address and the receiving port number of the user gateway (BNG) are respectively contained in the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user; the information of the requested service and the user subscription information are both stored in the application service server, and the bearing surface information currently accessed by the user is the bearing surface information which is provided for the user access of the application service server when the user logs in the network last time.
Step 102: the strategy executing function body maps the received strategy parameters to RSVP objects at the resource reservation protocol (RSVP) protocol end of the first-hop router.
Wherein the RSVP object comprises: a session (session) field, a sender template (sender _ TSPEC) field, and a sender specification (sender _ TSPEC) field;
the mapping of the policy parameters to the RSVP objects specifically includes:
mapping the IP address and the receiving port number of the BNG included by the policy parameter to a receiving port address field and a receiving port field respectively, and mapping the protocol number in the IP five-tuple included by the policy parameter to a protocol ID (protocol ID) field included by the session field;
mapping a source IP address and a source port number in an IP five-tuple included in the policy parameters to a sender address field and a sender port field included in the sender template field respectively;
and mapping the QoS requirement parameter included by the strategy parameter to the sender _ TSPEC field.
Step 103: and the RSVP protocol end transmits the RSVP object to RSVP clients of other routers except the first-hop router of the bearing surface through RSVP path (RSVP path) information, and each RSVP client reserves bandwidth for the requested service according to the RSVP object.
The RSVP protocol end transmits the RSVP object to RSVP clients of the other routers except the first-hop router through RSVP path message:
the RSVP protocol end generates RSVP path information carrying RSVP objects and transmits the RSVP path information to the RSVP client of the bearing surface BNG through the RSVP clients of all routers of the bearing surface; wherein, BNG is the last jump of the bearing surface and is used for connecting the bearing surface and the user side;
the steps of reserving the bandwidth for the requested service by each RSVP client according to the RSVP object comprise:
step a1, the RSVP clients of the other routers except the BNG establish path state according to the RSVP object carried by the RSVP path message forwarded by the previous-hop router, and forward the RSVP path message forwarded by the previous-hop router to the next-hop router, until the RSVP path message reaches the RSVP client of the BNG, step b1 is executed;
wherein the path state comprises the RSVP object and the address of the last hop router, the RSVP object is used for the next hop router to send signaling or data to;
b1, the RSVP client of BNG creates path state according to the RSVP object carried by the received RSVP path message, calculates the bandwidth needed to be reserved for the requested service, reserves the calculated bandwidth for the requested service, and sends back the RSVP path message to the RSVP protocol end through the RSVP clients of the rest routers of the bearing surface;
step c1, the RSVP clients of the other routers except BNG calculate the bandwidth needed to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message forwarded by the next-hop router, reserve the calculated bandwidth for the requested service, and forward the returned RSVP path message forwarded by the next-hop router to the previous-hop router; and until the RSVP protocol end receives the returned RSVP path message, namely, the returned RSVP path message reaches the first-hop router, the RSVP protocol end replies a reservation completion message to the policy server through the policy execution functional body, and the resource reservation flow is ended.
After step 103, when the service is completed or terminated, the embodiment of the present invention further includes: and releasing the reserved resources.
Wherein, when the service is completed or the application service server terminates the service, the releasing the reserved resource comprises:
step a2, when the policy server receives the resource release request from the application service server, the policy server sends the bandwidth release notice to the policy execution functional body;
step b2, the policy execution function body maps the IP quintuple corresponding to the requested service carried by the received bandwidth release notice, the IP address and the receiving port number of the BNG to an RSVP path delete (RSVP path tear) object of the RSVP protocol end; the RSVP protocol end generates RSVP path tear message carrying RSVP path tear object and transmits to RSVP client end of bearing surface BNG;
step c2, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the previous-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forward the RSVP path tear message to the next-hop router until the RSVP path tear message reaches the BNG, execute step d 2;
d2, the RSVP client of BNG deletes the path state corresponding to the RSVP path tear object carried by the received RSVP path tear message, and releases the resource corresponding to the RSVP path tear object carried by the received RSVP path tear message; and replying a release completion message to the policy server through the RSVP client, the RSVP protocol end and the policy execution function of the rest routers of the bearing surface, and ending the resource release process.
When the bearer plane terminates the service, the releasing the reserved resources includes:
step a3, after the RSVP client of BNG deletes the path state corresponding to the requested service and releases the resources occupied by the requested service, RSVP path tear message is generated and transmitted to RSVP protocol end through the RSVP client of each router except BNG on the bearing surface;
step b3, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the next-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router until the RSVP path tear message reaches the RSVP protocol end, that is, until the RSVP path tear message reaches the first-hop router, execute step c 3;
and c3, the RSVP protocol end replies a release completion message to the policy server through the policy execution function body, and the resource release process is ended.
The structure of the network resource management system according to the embodiment of the present invention is shown in fig. 2, and includes: the system comprises a policy server, a policy execution functional body, an RSVP protocol end and RSVP clients, wherein the policy server is introduced from a control surface and is respectively connected with a bearing surface and an application service server; wherein,
the policy server is used for generating policy parameters and issuing the policy parameters to the policy execution functional body according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user, which are carried by the received policy request when receiving the policy request sent by the application service server;
the strategy executing function body is used for mapping the received strategy parameters to the RSVP object of the RSVP protocol end;
and the RSVP protocol end is used for transmitting the RSVP object to each router of the bearing surface through the RSVP path message.
And the RSVP client is used for reserving the bandwidth for the requested service according to the RSVP object.
Wherein the RSVP object comprises: a session field, a sender template field, and a sender _ TSPEC field;
the policy enforcement function includes: the system comprises an interaction module, a session mapping module, a template mapping module and a specification mapping module; wherein,
the interaction module is used for receiving the strategy parameters sent by the strategy server;
a session mapping module, configured to map an IP address and a receiving port number of a BNG included in a received policy parameter to a receiver address field and a receiver port field included in the session field, respectively, and map a protocol number in an IP five-tuple included in the received policy parameter to a protocol ID field included in the session field;
a template mapping module, configured to map a source IP address and a source port number in an IP five-tuple included in the received policy parameter to a sender address field and a sender port field included in the sender template field, respectively;
and the specification mapping module is used for mapping the QoS requirement parameters included in the received strategy parameters to the sender _ TSPEC fields.
Furthermore, the RSVP protocol end comprises a message generation module and a message receiving and sending module; wherein,
the message generating module is used for generating RSVP path messages of the carried RSVP objects;
the message receiving and sending module is used for transmitting the RSVP path message to the RSVP client of the bearing surface BNG through the RSVP client of each router of the bearing surface; when receiving the returned RSVP path message, replying a reservation completion message to the policy server through the interaction module;
the RSVP client is a router client when arranged on the rest routers of the bearing surface except the BNG; the RSVP client is a BNG client when being arranged on the BNG; wherein,
the router client is arranged on the other routers of the bearing surface except the BNG and used for establishing a path state according to the received RSVP object carried by the RSVP path message sent from the previous hop router and forwarding the RSVP path message sent from the previous hop router to the next hop router; calculating the bandwidth required to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message sent by the next hop router, reserving the calculated bandwidth for the requested service, and forwarding the returned RSVP path message sent by the next hop router to the previous hop router;
and the BNG client is arranged on the BNG and used for establishing a path state according to the RSVP object carried by the RSVP path message sent by the previous-hop router, calculating the bandwidth required to be reserved for the requested service, reserving the calculated bandwidth for the requested service, and sending the path message back to the RSVP transceiver module of the RSVP protocol end through each router client.
Further, the policy server is further configured to send a bandwidth release notification to the policy executing function when receiving a resource release request sent by the application service server;
the interaction module is further used for receiving a bandwidth release notification sent by the policy server;
the session mapping module, the template mapping module and the specification mapping module are further configured to map an IP quintuple corresponding to the requested service carried by the received bandwidth release notification, and the IP address and the receiving port number of the BNG to an RSVP path delete RSVP path tear object at the RSVP protocol end;
the message generating module is also used for generating RSVP path tear object RSVP path tear message carrying RSVP path tear object;
the message receiving and sending module is further configured to transmit the RSVP path tear message to an RSVP client of the bearer BNG;
the router client is used for receiving the RSVP path tear message sent by the previous hop router, deleting the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, releasing the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forwarding the RSVP path tear message to the next hop router;
the BNG client is configured to receive the RSVP path tear message, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, and reply a release completion message to the policy server through the RSVP clients, the message transceiver module, and the interaction module of the other routers on the bearing surface after releasing the RSVP path tear object carried by the RSVP path tear message, thereby ending the resource release process.
Further, the BNG client is further configured to delete the path state corresponding to the requested service, and after releasing the resources occupied by the requested service, generate an RSVP path tear message and transmit the RSVP path tear message to the message transceiver module through the RSVP clients of the routers on the bearer side except the BNG;
the router client is further configured to receive an RSVP path tear message sent by a next-hop router, delete a path state corresponding to an RSVP path tear object carried in the RSVP path tear message, release resources corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router;
the message receiving and sending module is further configured to reply a release completion message to the policy server through the interaction module, and end the resource release process.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (11)
1. A network resource management method is characterized in that when a policy server receives a policy request sent by an application service server, the method comprises the following steps:
generating a policy parameter according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user, which are carried by the received policy request, and issuing the policy parameter to a policy execution functional body of a first-hop router of the bearing surface;
the strategy executing functional body maps the received strategy parameters to RSVP objects of a resource reservation protocol RSVP protocol end of the first-hop router; and the RSVP protocol end transmits the RSVP object to RSVP clients of other routers except the first-hop router of the bearing surface through RSVP path information, and each RSVP client reserves bandwidth for the requested service according to the RSVP object.
2. The method according to claim 1, wherein the policy parameters comprise: IP quintuple of the requested service, QoS requirement parameter, and IP address and receiving port number of the user gateway BNG;
the RSVP object includes: a session field, a sender template field and a sender specification sender _ TSPEC field;
the RSVP object that maps the received policy parameters to the RSVP protocol end is:
mapping the IP address and the receiving port number of the BNG included by the strategy parameter to a receiving address field and a receiving port field of the session field respectively, and mapping the protocol number in the IP quintuple included by the strategy parameter to a protocol ID field included by the session field;
respectively mapping a source IP address and a source port number in an IP five-tuple included in the strategy parameters to a sender address field and a sender port field included in the sender template field;
and mapping the QoS requirement parameter included by the strategy parameter to the sender _ TSPEC field.
3. The method for managing network resources according to claim 1 or 2, wherein the RSVP protocol end transmits the RSVP object to RSVP clients of all routers except the first-hop router of the bearer side through RSVP path message:
the RSVP protocol end generates RSVP path message of carried RSVP object, and transmits to RSVP client of user gateway BNG of bearing surface through RSVP client of each router of bearing surface;
the steps of reserving the bandwidth for the requested service by each RSVP client according to the RSVP object comprise:
a1, the RSVP clients of the other routers except BNG create path state according to RSVP object carried by RSVP path message sent by the previous-hop router, and forward the RSVP path message sent by the previous-hop router to the next-hop router, until the RSVP path message reaches the RSVP client of BNG, execute step b 1;
b1, the RSVP client of BNG creates path state according to RSVP object carried by RSVP path message, calculates bandwidth needed to be reserved for the requested service, reserves calculated bandwidth for the requested service, and sends RSVP path message back to RSVP protocol end through RSVP client of the rest routers of bearing surface;
c1, the RSVP clients of the other routers except BNG calculate the bandwidth needed to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message sent by the next-hop router, reserve the calculated bandwidth for the requested service, and forward the returned RSVP path message sent by the next-hop router to the previous-hop router; and until the RSVP protocol end receives the returned RSVP path message, replying a reservation completion message to the policy server through the policy execution function body.
4. The method of claim 3, wherein when the requested service is completed or terminated, the method further comprises: and releasing the reserved resources.
5. The method according to claim 4, wherein said releasing reserved resources comprises:
a2, when the policy server receives the resource release request from the application service server, the policy server sends the bandwidth release notice to the policy execution functional body;
b2, the strategy executing functional body maps the IP quintuple corresponding to the requested service carried by the received bandwidth releasing notice, the IP address and the receiving port number of the BNG to the RSVP path deleting RSVP path tear object of the RSVP protocol end; the RSVP protocol end generates RSVP path tear object RSVP path tear message carrying RSVP path tear object and transmits the RSVP path tear message to the RSVP client end of the bearing surface BNG;
c2, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the previous-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forward the RSVP path tear message to the next-hop router until the RSVP path tear message reaches the BNG, execute step d 2;
d2, the RSVP client of BNG deletes the path state corresponding to the RSVP path tear object carried by the received RSVP path tear message, and releases the resource corresponding to the RSVP path tear object carried by the received RSVP path tear message; and replying a release completion message to the policy server through the RSVP client, the RSVP protocol end and the policy execution function of the rest routers of the bearing surface.
6. The method according to claim 4, wherein said releasing reserved resources comprises:
a3, BNG RSVP client end deletes the path state corresponding to the requested service, and after releasing the resource occupied by the requested service, generates RSVP path tear message and transmits to RSVP protocol end through the RSVP client end of each router except BNG on the bearing surface;
b3, the RSVP clients of the other routers except the BNG receive the RSVP path tear message sent by the next-hop router, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, release the resource corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router until the RSVP path tear message reaches the RSVP protocol end, execute step c 3;
c3, after the RSVP path tear message reaches the RSVP protocol end, the RSVP protocol end replies the release completing message to the strategy server through the strategy executing function body.
7. A network resource management system, the system comprising: the system comprises a policy server, a policy execution functional body, an RSVP protocol end and RSVP clients, wherein the policy server is introduced into a control surface and is respectively connected with a bearing surface and an application service server, the policy execution functional body and the RSVP protocol end are arranged on a first-hop router of the bearing surface, and the RSVP clients are arranged on the other routers except the first-hop router of the bearing surface; wherein,
the policy server is used for generating policy parameters and issuing the policy parameters to the policy execution functional body according to the information of the requested service, the user subscription information and the bearing surface information currently accessed by the user, which are carried by the received policy request when receiving the policy request sent by the application service server;
the strategy executing function body is used for mapping the received strategy parameters to the RSVP object of the RSVP protocol end;
the RSVP protocol end is used for transmitting the RSVP object to each router of the bearing surface through the RSVP path message;
and the RSVP client is used for reserving the bandwidth for the requested service according to the RSVP object.
8. The network resource management system of claim 7 wherein the RSVP object comprises: a session field, a sender template field, and a sender _ TSPEC field;
the policy enforcement function includes: the system comprises an interaction module, a session mapping module, a template mapping module and a specification mapping module; wherein,
the interaction module is used for receiving the strategy parameters sent by the strategy server;
a session mapping module, configured to map an IP address and a receiving port number of a BNG included in a received policy parameter to a receiver address field and a receiver port field included in the session field, respectively, and map a protocol number in an IP five-tuple included in the received policy parameter to a protocol ID field included in the session field;
a template mapping module, configured to map a source IP address and a source port number in an IP five-tuple included in the received policy parameter to a sender address field and a sender port field included in the sender template field, respectively;
and the specification mapping module is used for mapping the QoS requirement parameters included in the received strategy parameters to the sender _ TSPEC fields.
9. The network resource management system of claim 7 or 8, wherein the RSVP protocol end comprises a message generation module, a message transceiver module; wherein,
the message generating module is used for generating RSVP path messages of the carried RSVP objects;
the message receiving and sending module is used for transmitting the RSVP path message to the RSVP client of the bearing surface BNG through the RSVP client of each router of the bearing surface; when receiving the returned RSVP path message, replying a reservation completion message to the policy server through the interaction module;
the RSVP client is a router client when arranged on the rest routers of the bearing surface except the BNG; the RSVP client is a BNG client when being arranged on the BNG; wherein,
the router client is used for establishing a path state according to the received RSVP object carried by the previous RSVP path message and forwarding the RSVP path message sent by the previous hop router to the next hop router; calculating the bandwidth required to be reserved for the requested service according to the RSVP object carried by the returned RSVP path message sent by the next hop router, reserving the calculated bandwidth for the requested service, and forwarding the returned RSVP path message sent by the next hop router to the previous hop router;
the BNG client is used for establishing a path state according to the RSVP object carried by the RSVP path message sent by the previous hop router, calculating the bandwidth required to be reserved for the requested service, reserving the calculated bandwidth for the requested service, and sending the RSVP path message back to the message receiving and sending module of the RSVP protocol end through each router client.
10. The system according to claim 9, wherein the policy server is further configured to send a bandwidth release notification to the policy execution function when receiving a resource release request from the application service server;
the interaction module is further used for receiving a bandwidth release notification sent by the policy server;
the session mapping module, the template mapping module and the specification mapping module are further configured to map an IP quintuple corresponding to the requested service carried by the received bandwidth release notification, and the IP address and the receiving port number of the BNG to an RSVP path delete RSVP path tear object at the RSVP protocol end;
the message generating module is also used for generating RSVP path tear object RSVP path tear message carrying RSVP path tear object;
the message receiving and sending module is further configured to transmit the RSVP path tear message to an RSVP client of the bearer BNG;
the router client is used for receiving the RSVP path tear message sent by the previous hop router, deleting the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, releasing the resource corresponding to the RSVP path tear object carried by the RSVP path tear message, and forwarding the RSVP path tear message to the next hop router;
the BNG client is configured to receive the RSVP path tear message, delete the path state corresponding to the RSVP path tear object carried by the RSVP path tear message, and reply the release completion message to the policy server through the RSVP clients, the message transceiver module, and the interaction module of the other routers on the bearing surface after releasing the RSVP path tear object carried by the RSVP path tear message.
11. The system according to claim 9, wherein said BNG client is further configured to delete a path state corresponding to the requested service, and after releasing resources occupied by the requested service, generate an RSVP path tear message and transmit the RSVP path tear message to said messaging module through the RSVP clients of the routers on the bearer side except the BNG;
the router client is further configured to receive an RSVP path tear message sent by a next-hop router, delete a path state corresponding to an RSVP path tear object carried in the RSVP path tear message, release resources corresponding to the RSVP path tear object, and forward the RSVP path tear message to the previous-hop router;
the message receiving and sending module is also used for replying a release completion message to the policy server through the interaction module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910169975.6A CN102025688B (en) | 2009-09-11 | 2009-09-11 | Network resource management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910169975.6A CN102025688B (en) | 2009-09-11 | 2009-09-11 | Network resource management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102025688A true CN102025688A (en) | 2011-04-20 |
| CN102025688B CN102025688B (en) | 2014-09-10 |
Family
ID=43866551
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910169975.6A Expired - Fee Related CN102025688B (en) | 2009-09-11 | 2009-09-11 | Network resource management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102025688B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1675909A (en) * | 2002-06-10 | 2005-09-28 | 高通股份有限公司 | Packet flow processing in a communication system |
| CN1731757A (en) * | 2004-08-05 | 2006-02-08 | 华为技术有限公司 | Method and system for providing QoS assurance in edge router |
| US7272145B2 (en) * | 2002-07-31 | 2007-09-18 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network through proxy signaling |
| CN101047586A (en) * | 2006-06-29 | 2007-10-03 | 华为技术有限公司 | Service QoS ensuring method and device for radio mesh network |
| CN101330445A (en) * | 2007-06-21 | 2008-12-24 | 华为技术有限公司 | Method for implementing load-bearing path as well as apparatus and system thereof |
-
2009
- 2009-09-11 CN CN200910169975.6A patent/CN102025688B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1675909A (en) * | 2002-06-10 | 2005-09-28 | 高通股份有限公司 | Packet flow processing in a communication system |
| US7272145B2 (en) * | 2002-07-31 | 2007-09-18 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network through proxy signaling |
| CN1731757A (en) * | 2004-08-05 | 2006-02-08 | 华为技术有限公司 | Method and system for providing QoS assurance in edge router |
| CN101047586A (en) * | 2006-06-29 | 2007-10-03 | 华为技术有限公司 | Service QoS ensuring method and device for radio mesh network |
| CN101330445A (en) * | 2007-06-21 | 2008-12-24 | 华为技术有限公司 | Method for implementing load-bearing path as well as apparatus and system thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102025688B (en) | 2014-09-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1935161B1 (en) | System for dynamic bandwidth adjustment and trading among peers | |
| KR100822707B1 (en) | Apparatus and method for managing quality of service in integrated network of heterogeneous mobile networks | |
| US7272651B1 (en) | RSVP transmitter proxy | |
| EP1338126B1 (en) | Method and system for resource reservations in a multicasting network | |
| US6765927B1 (en) | RSVP proxy service for communication network | |
| US20070189293A1 (en) | QoS guarantee system in multidomain network and QoS server applied to the same | |
| EP3664389B1 (en) | Resource reservation method and related apparatus | |
| US20090201932A1 (en) | Method and system for implementing mpls network diffserv traffic engineering | |
| WO2004064325A1 (en) | The system and method for realizing the resource distribution in the communication network | |
| US9755905B2 (en) | Method, node device and system for establishing label switched path | |
| CN102365850A (en) | Method and arrangement for providing relevant service levels | |
| Demetrios | A Glance at Quality of Ėervices in Mobile Ad-Hoc Networks | |
| CN100387023C (en) | Method of flow state establishment | |
| US20080137654A1 (en) | Method of managing signaling message in path-based signaled paths to mpls-enabled core network | |
| CN113810442B (en) | Resource reservation method, device, terminal and node equipment | |
| JP2009071824A (en) | Method and apparatus for configuring bandwidth in class-based network | |
| CN102025688B (en) | Network resource management method and system | |
| WO2013037319A1 (en) | Bandwidth resource management method, device and system for label switched path | |
| CN100502370C (en) | Optimizing system and method for medium transmission on different transmission channels | |
| CN108476219B (en) | Method and apparatus for data exchange | |
| CN101119513A (en) | System and method for developing multicast broadcasting service of wireless network | |
| WO2013013577A1 (en) | Method, device and system for managing bandwidth resource of label switched path | |
| US8681613B2 (en) | Method for establishing and terminating service flow via relay nodes using tunnel mechanism | |
| KR100766033B1 (en) | Method of Guarantee for End-To-End Quality of Service using SIP and RSVP-TE | |
| EP3035618B1 (en) | Integrated bandwidth and storage reservation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201218 Address after: 256651 Bincheng District, Binzhou, Shandong, Beizhen, Phoenix Road three, road ten Patentee after: BINZHOU DAYOU NEW ENERGY DEVELOPMENT Co.,Ltd. Address before: 518057 Ministry of justice, Zhongxing building, South Science and technology road, Nanshan District hi tech Industrial Park, Shenzhen, Guangdong Patentee before: ZTE Corp. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140910 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |