CN100346620C - A transmitter-oriented resource reservation implementing method having backtracking ability - Google Patents
A transmitter-oriented resource reservation implementing method having backtracking ability Download PDFInfo
- Publication number
- CN100346620C CN100346620C CNB2004100989354A CN200410098935A CN100346620C CN 100346620 C CN100346620 C CN 100346620C CN B2004100989354 A CNB2004100989354 A CN B2004100989354A CN 200410098935 A CN200410098935 A CN 200410098935A CN 100346620 C CN100346620 C CN 100346620C
- Authority
- CN
- China
- Prior art keywords
- node
- resv
- reservation
- message
- session
- 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.)
- Active
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention belongs to the technical field of grouping networks, which relates to an implement method for reserving resources for difference services in the grouping networks so as to ensure the quality of services of various services transferred on the networks. The method steps comprise that a sending end sends out a reserved request message to a receiving end, and the message comprises requirements of the quality of service of the service and other useful information; the reserved request message passes through each node of the grouping network on the way according to routes selected by a routing algorithm or according to routes defined by explicit route objects, and the intermediate nodes can try to reserve resources according to the defined quality of service in the message; if the reservation is successful, the request message is forwarded downstream; if the reservation is failed, nodes can judge whether the upstream nodes continuously try other paths or return error information according to the value of an AFT domain in the message. When the reserved request message is transferred to a conversation receiver, the receiver can return a confirmed message reserved successfully to a sender.
Description
Technical field
The invention belongs to the packet network technologies field, is a kind of implementation method of carrying out resource reservation on packet network for different business.Particularly a kind of resource reservation implementation method towards transmit leg with the ability of recalling.
Background technology
The packet switching network that with Internet is representative is taked the transmission means of (Best Effort) of doing one's best to loaded service on it, thereby can't guarantee service quality.For multimedia services such as audio frequency, videos, they are very responsive to time-delay, thereby must give the enough Internet resources of this class traffic assignments, could guarantee their high-quality real-time Transmission.For this reason, the IETF of Internet working group (Internet Engineering Task Force) has formulated RSVP RSVP (ResourceReservation Protocol).Document [1] R.Braden, L.Zhang, " Resource ReservationProtocol (RSVP) ", IETF RFC2205.RSVP is a reservation protocol towards receiving terminal, specifies the Internet resources that need to reserve also to pay for it by receiving terminal.Its initial design idea is at application scenarioss such as video request programs, and its mode towards receiving terminal has adapted to the real needs of this class business well.But along with the diversity development of bearer service on the packet network, RSVP has exposed its some shortcoming and defect: 1. a lot of business that present Internet goes up transmission are not easy to use the resource reservation towards receiving terminal, such as voice service.In voice service, be that conversation is paid normally by sending a side, therefore reasonably way is to allow the initiator who calls out determine which type of service quality it needs, and needs intermediate node to reserve how many resources, promptly should use the resource reservation mode towards transmit leg.In RSVP along by receiving terminal hop-by-hop reserved resource on the reverse path of transmitting terminal, if intermediate node is reserved failure, it can be sent out error messages corresponding and give receiving terminal, and transmitting terminal then must be set up the situation of failure through just learning the path after waiting for for a long time.In such as business such as voice, always wish that transmitting terminal (calling party) can set up failure information in the perception path in the shortest time, so that abnormal conditions in time can be conveyed to the user, be convenient to the user and further take measures.3. in current various method for obligating resource, whole reservation procedure has just been failed when some intermediate nodes are reserved failure, and reservation procedure is not sought the ability in other path automatically.
For can be better and the existing equipment compatibility, it is identical to describe the Format Object of stipulating in the object of service quality and the RSVP in this method for obligating resource, this comprises stream description object (FLOWSPEC) and filter description object (FILTER_SPEC), wherein the FLOWSPEC object definition service quality that requires of data flow, the FILTER_SPEC object has played the effect of filter.Document [1] R.Braden is seen in the definition of related object, L.Zhang, " Resource ReservationProtocol (RSVP) ", IETF RFC2205, document [2] J.Wroclawski, " The Use ofRSVP with IETF Integrated Services ", IETF RFC2210.Adopt the Format Object identical, make this method for obligating resource may operate on the router of any existing support RSVP with RSVP.In addition, for route display object of using in this method (EXPLICITROUTE) and path record object (RECORD ROUTE), their definition and form can be referring to document [3] D.Awduche, L.Berger, " RSVP-TE:Extensions to RSVP for LSPTunnels ", IETF RFC3209.
Summary of the invention
The object of the present invention is to provide a kind of on packet network the method for obligating resource towards transmit leg, the resource reservation process has the ability of recalling.
The invention belongs to the packet network technologies field, is to carry out a kind of implementation method towards the transmit leg resource reservation for different business on packet network.It is by introducing novel mechanism such as service quality description object (comprising stream description object FLOWSPEC and filter object FILTER_SPEC), fault-tolerant territory (AFT), path record object, guaranteed the service quality of the miscellaneous service that transmits on the packet network, guarantee simultaneously not have in network under the situation that enough resources can use, transmission can obtain corresponding notification message as soon as possible.
The present invention is based upon on the packet network basis, and operation platform is the router in the network, and these routers should have the function of priority scheduling, for example the RSVP router.Routing forwarding equipment can be created corresponding formation for this data flow according to the quality of service requirement of wherein describing after receiving reservation request, coordinate the data transmission of each formation then according to the priority of scheduling strategy of formulating in the equipment and data flow, thereby guarantee the quality of service requirement of different business.
The invention provides a kind of resource reservation implementation method towards transmit leg with the ability of recalling, this method may further comprise the steps:
The sending direction recipient sends a reservation requests Resv_Req, this reservation requests Resv_Req transmits downstream according to the route of routing algorithm selection or according to the route of explicit route object EXPLICITROUTE regulation, each node attempts reserving enough resources according to the service quality of stipulating among the reservation requests Resv_Req on the way, if reserve successfully, then reservation requests Resv_Req is continued to transmit downstream, simultaneously this node is recorded among the record object RECORD ROUTE of path; If reserve failure, then node is recalled inspection, whether the value of judging fault-tolerant territory AFT is 0, if the value of fault-tolerant territory AFT is not 0, then judge and upstream recall, this node subtracts 1 with the value of fault-tolerant territory AFT, and upwards a hop node sends a reservation retry message Resv_Retry, upstream node can be reselected next jumping after receiving and reserving retry message Resv_Retry, if corresponding next jumping is arranged then passes the reservation retry message Resv_Retry that comes and construct reservation requests Resv_Req according to the downstream, and send out to next redirect, if there is not next jumping, then recall inspection once more; After reservation requests Resv_Req arrives the session recipient, article one, the packet-switched path of reserved resource has just been set up, its each intermediate node information of going through is included among the record object RECORD ROUTE of path, the recipient should reserve successful acknowledge message Resv_Conf to one of transmit leg loopback, and this is reserved and comprises corresponding path description object RECORD ROUTE among the successful acknowledge message Resv_Conf; Check that the value of finding fault-tolerant territory AFT is 0 if recall, then reserve failure, failure node can send reservation error message Resv_Err to the session initiator, has comprised corresponding error description object ERRORSPEC among this reservation error message Resv_Err.
Described transmit leg has the power to make decision of reserved resource, it constructs corresponding QoS parameter description object as required, how many resources this object has determined to need to reserve, the sending direction recipient sends reservation requests Resv_Req, remove among this reservation requests Resv_Req and comprise QoS parameter description object (comprising stream description object FLOWSPEC and filter description object FILTER_SPEC), session object SESSION in order to descriptive session information, outside the path record object RECORD ROUTE in order to record path information, can also optionally comprise explicit route object EXPLICIT ROUTE, in addition, comprised a fault-tolerant territory AFT in the head of message, the value of fault-tolerant territory AFT shows the number of times that can recall in the reservation procedure, if reservation requests Resv_Req comprises explicit route object, the value of then fault-tolerant territory AFT must be set to 0.
The method for obligating resource of the present invention and traditional RSVP (IETF RFC2205) defined relatively, we obviously as can be seen the present invention have the following advantages:
1. the present invention is a kind of method for obligating resource towards transmitting terminal, is more suitable in the business by transmitting terminal control, and as voice service, which type of service quality transmitting terminal need can determine and pay for it.
2. transmitting terminal can obtain error notification in time when intermediate node is reserved failure, thereby can notify the user to take corresponding measure as soon as possible.
3. when middle certain node occurs reserving failure, can recall, thereby attempt reserved resource on other path, and needn't allow transmitting terminal initiate reservation request once more, the number of times that allows to recall is specified by transmitting terminal.
Reservation confirmation message not necessarily along reservation requests through the back transfer in path, can select another different path, improved flexibility.
5. support explicit route.
6. the transmitting terminal of session and receiving terminal can be known the node listing that the resource reservation path is experienced by path description object and path record object respectively.
Description of drawings
Fig. 1 is the process chart that the first resource reserved path is set up.
Embodiment
This resource reservation implementation method provided by the invention towards transmit leg with the ability of recalling, the sending direction recipient sends a reservation requests, comprised professional quality of service requirement in this reservation requests, reservation requests is transmitted downstream according to the route of routing algorithm selection or according to the route of explicit route object regulation, each node attempts reserving enough resources according to the service quality of stipulating in the reservation requests on the way, if reserve successfully, just reservation requests is continued to transmit downstream, simultaneously this node is recorded in record (RECORDROUTE) object of path, if reserve failure, node can continue to allow upstream node attempt other path according to the value decision of the fault-tolerant territory AFT in the reservation requests (Allowed Failed Times) or return reservation error information to transmit leg, allow upstream node continue to attempt other path if judge, then this node hop node that will make progress sends one and reserves retry message, a last hop node can be reselected next jumping according to routing table information, after reservation requests arrives the recipient, article one, the packet-switched path of reserved resource has just been set up, its each intermediate node information of going through is included in the record object of path, the recipient should also should comprise corresponding path description object to reservation confirmation message of transmit leg loopback in this message.
This resource reservation implementation method provided by the invention towards transmit leg with the ability of recalling, transmit leg has the power to make decision of reserved resource, it constructs corresponding QoS parameter description object as required, how many resources this object has determined to need to reserve, the sending direction recipient sends reservation requests, remove in this message and comprise QoS parameter description object (comprising stream description object FLOWSPEC and filter description object FILTER_SPEC), session object in order to descriptive session information, outside the path record object in order to record path information, can also optionally comprise explicit route object, in addition, comprised a fault-tolerant territory in the head of message, the value in fault-tolerant territory shows the number of times that can recall in the reservation procedure, if reservation request message contains explicit route object, then the value in fault-tolerant territory must be set to 0; Reservation requests is transmitted downstream according to the route of routing algorithm selection or according to the route of explicit route object regulation, each node attempts reserving enough resources according to the service quality of stipulating in the reservation requests on the way, if reserve successfully, just request message is continued to transmit downstream, simultaneously this node is recorded in the record object of path, if reserve failure, node is recalled inspection, whether the value of judging fault-tolerant territory AFT is 0, if the value of fault-tolerant territory AFT is not 0, then decision is upstream recalled, this node can subtract 1 to the value of fault-tolerant territory AFT, and upwards a hop node sends a reservation retry message Resv_Retry, upstream node can be reselected next jumping after receiving and reserving retry message Resv_Retry, and next is jumped then passes the reservation retry message Resv_Retry structure reservation requests Resv_Req that comes according to the downstream accordingly if having, and sends out to next redirect, if there is not next jumping, then recall inspection once more; After reservation requests Resv_Req arrives the session recipient, article one, the packet-switched path of reserved resource has just been set up, its each intermediate node information of going through is included among the record object RECORD ROUTE of path, the recipient should successfully confirm Resv_Conf message to reservation of transmit leg loopback, also should comprise corresponding path description object ROUTE DESCRIPTOR in this message, check that the value of finding fault-tolerant territory AFT is 0 if recall, then reserve failure, failure node can send reservation error message Resv_Err to the session initiator, has comprised corresponding error description object ERRORSPEC in this message.
The present invention is a kind of method for obligating resource towards transmit leg that has the ability of recalling on packet network, and its implementation is as follows:
In the process that first resource is reserved, may comprise four kinds of dissimilar message: reservation requests Resv_Req, reservation confirmation message Resv_Conf, reservation error message Resv_Err reserves retry message ResV_Retry.
The form of four kinds of message all constitutes by connecing a series of objects behind a public COMMON HEADER.The form of common headers COMMON HEADER is as follows.
0 3 8 16 31
++++++++++++++++++++++++++++++++++++++++++++++++
+Vers+AFT+ Msg?Type + Check?Sum +
++++++++++++++++++++++++++++++++++++++++++++++++
+Send?TTL?+ (Reserved)+ Length +
++++++++++++++++++++++++++++++++++++++++++++++++
+ Msg?ID +
++++++++++++++++++++++++++++++++++++++++++++++++
Vers: version number, 4, current version is 1.
AFT: fault-tolerant territory, 4, the number of times that the request of indicating can be recalled.
Msg_Type: type of message, 1 byte, Resv_Req is 1, and Resv_Conf is 2, and Resv_Err is 3, and Resv_Retry is 4.
Check Sum: verification and, 2 bytes are carried out completeness check to message, complete 0 expression need not verification.
Send TTL: life cycle, 1 byte.
Length: length field, 2 bytes, the total length of message.
Msg ID: message flag symbol, 2 bytes.
In addition, comprise following 8 objects among the present invention: stream description object FLOWSPEC, filter description object FILTER_SPEC, session object SESSION, route display object EXPLICITROUTE, path record object RECORD ROUTE, path description object ROUTEDESCRIPTOR, error description object ERRORSPEC confirms object CONFIRM.Each object all is made up of identical header field and particular content.Form is as follows:
0 8 16 24 31
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Length + Class + Type +
+++++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Object?content +
+ +
+++++++++++++++++++++++++++++++++++++++++++++++++
Length: length field, 2 bytes, object length.
Class: classification, 1 byte, session object SESSION is 1, confirm that object CONFIRM is 2, explicit route object EXPLICIT ROUTE is 3, and path record object RECORDROUTE is 4, path description object ROUTE DESCRIPTOR is 5, error description object ERRORSPEC is 6, and stream description object FLOWSPEC is 7, and filter object FILTER_SPEC is 8.
Type: type, 1 byte, the particular type of same classification the inside.
Object content: content, one or more words indicate the particular content of object.
When the initiator of session wanted to set up a resource reservation path, it at first sent a reservation requests Resv_Req to the recipient of session.Reservation requests Resv_Req form is as follows,＜Resv_Req message 〉: :=＜COMMON HEADER〉＜SESSION〉[＜EXPLICIT
ROUTE>]
<FLOWSPEC><FILTER_SPEC><RECORD
ROUTE>
Wherein, the form of public COMMON HEADER as previously shown, the form of stream description object FLOWSPEC is referring to RFC2210, the form of option explicit route object EXPLICITROUTE and path record object RECORD ROUTE is referring to RFC3209, the form of filter object FILTER_SPEC is referring to RFC2205, the form of session object SESSION is as follows
Session object SESSION, the value in classification Class territory is 1.It is divided into two types of IPv4 session and IPv6 sessions, and the value in IPv4 conversation type Type territory is 1, and the value in IPv6 conversation type Type territory is 2, and the content field form is as follows,
IPv4 SESSION object Class=1, Type=1
0 8 16 24 31
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Source?IP?Address +
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Source?Port + Dest?IP?Address +
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Dest?IP?Address?+ Dest?Port +
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Protocol?ID?+?Flags?+ (Reserved) +
+++++++++++++++++++++++++++++++++++++++++++++++++
IPv6 SESSION object Class=1, Type=2
0 8 16 24 31
++++++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Source?IP?Address +
+ +
+ +
++++++++++++++++++++++++++++++++++++++++++++++++++
+ Source?Port + Dest?IP?Address +
++++++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Dest?IP?Address +
+ +
++++++++++++++++++++++++++++++++++++++++++++++++++
+ Dest?IP?Address + Dest?Port +
++++++++++++++++++++++++++++++++++++++++++++++++++
+ Protocol?ID?+ Flags + (Reserved) +
+++++++++++++++++++++++++++++++++++++++++++++++++++
Source IPAddress: session source address, 32 of IPv4 addresses, 128 of IPv6 addresses.
Source Port: session source port, 32.
Dest IP Address: session destination address, 32 of IPv4 addresses, 128 of IPv6 addresses.
Dest Port: session destination interface, 32.
Protocol ID: agreement ID, 1 byte is indicated used IP agreement.
Flags: mark, 1 byte.
If comprised explicit route object EXPLICITROUTE among the reservation requests Resv_Req, the value of fault-tolerant territory AFT must be set to 0 among public COMMON HEADER, and expression message can only be reserved along the path of explicit route regulation, does not allow to recall.
Reservation requests Resv_Req perhaps transmits along the path that routing algorithm is selected downstream along the path (if explicit route object EXPLICIT ROUTE is arranged) of explicit route regulation.After intermediate node receives reservation requests Resv_Req, can check the QoS parameter that comprises in the message, judge whether that according to the current available resource situation of this node enough resources support this session then, if have, node just reserves enough resources to guarantee the service quality of session for this session, then the address information recording of this node is write down among the object RECORDROUTE in the path.Last this node is sought next jumping according to the situation of Route Selection again, if having found next jumping just sends out reservation requests Resv_Req to next redirect, if do not find next jumping, just removing before was that the nodal information among the object RECORDROUTE is write down in this session reserved resource and path, attempted then recalling; If intermediate node does not have enough resources in order to support this session, node also will be attempted recalling.
Concrete steps are recalled in trial, node checks at first whether the value of the fault-tolerant territory AFT among public the COMMON HEADER is 0, if be 0, explanation has not allowed to have been recalled for this request again, and so current failure node will send a reservation error message Resv_Err to the originating end of session.The form of reservation error message Resv_Err is as follows,
<Resv_Err message> ::＝ <COMMONHEADER><SESSION><ERRORSPEC>
Wherein, the form of public COMMON HEADER and session object SESSION as previously mentioned, the form of error description object ERRORSPEC is as follows,
Error description object ERRORSPEC, the value in classification Class territory is 6.It is divided into two types of IPv4 session and IPv6 sessions, and the value in IPv4 conversation type Type territory is 1, and the value in IPv6 conversation type Type territory is 2, and the content field form is as follows,
IPv4 ERRORSPEC object Class=6, Type=1
0 8 16 24 31
+++++++++++++++++++++++++++++++++++++++++++++++
+ Error?node?IP?Address +
+++++++++++++++++++++++++++++++++++++++++++++++
+ Flags + Error?Code?+ Error?Value +
+++++++++++++++++++++++++++++++++++++++++++++++
IPv6ERRORSPEC object Class=6, Type=2
0 8 16 24 31
+++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Error?node?IP?Address +
+ +
+ +
+++++++++++++++++++++++++++++++++++++++++++++++
+ Flags?+ Error?Code?+Error?Value +
+++++++++++++++++++++++++++++++++++++++++++++++
Error node IP Address: reserve the failure node address, 32 of IPv4 addresses, 128 of IPv6 addresses.
Flags: mark, 1 byte.
Error Code: error code, 8.
Error Value: improper value, 16.Error code and improper value are in order to describe wrong specifying information.
Reservation error message Resv_Err is along the back transfer of path record object RECORD ROUTE record path, and the node of going through all can be removed and be this session reserved resource.After the originating end of session was received the reservation error message Resv_Err that intermediate node sends, this resource reservation path was set up and is just ended in failure.
If the said value of recalling the fault-tolerant territory AFT of inspection discovery in front is not 0, illustrate that this request also allows to recall, failure node just subtracts 1 to the value of fault-tolerant territory AFT so, upwards a hop node sends and reserves retry message Resv_Retry then, and the address information of a last hop node can write down the object RECORD ROUTE from the path and obtain.The form of reserving retry message Resv_Retry is as follows,
<Resv_Retry message> :: ＝<COMMONHEADER><SESSION><FLOWSPEC> <FILTER_SPEC><RECORDROUTE>
Wherein, the form of public COMMON HEADER and session object SESSION as previously mentioned, the form of stream description object FLOWSPEC is referring to RFC2210, and the form of filter description object FILTER_SPEC is referring to RFC2205, and the form of path record object RECORD ROUTE is referring to RFC3209.
After a last hop node is received reservation retry Resv_Retry message, it can recomputate according to routing table information, select next jumping of another neighbor node as the resource reservation path, if such neighbor node is arranged, present node will re-construct reservation request Resv_Req message according to the content of reserving retry message Resv_Retry so.Reserve and comprised relevant service quality description (comprising stream description object FLOWSPEC and filter description object FILTER_SPEC) and conversation description object SESSION and path record object RECORD ROUTE among the retry message Resv_Retry, these objects are the reservation requests Resv_Req content that need comprise just, so node is easy to re-construct reservation requests Resv_Req according to these information.Behind the good reservation requests Resv_Req of joint structure, just this message is transmitted to selected again next-hop node; If select the operation failure of next jumping, node will be removed previous this session reserved resource that is so, and removes the address information of this node among the record object RECORD ROUTE of path, and continuation is attempted recalling then.
After the relaying of a series of intermediate nodes of reservation requests Resv_Req process was transmitted the recipient of the final arrival of operation session, the resource reservation path with service quality assurance had just been set up.At this moment, the recipient need construct corresponding affirmation object CONFIRM and path description object ROUTE DESCRIPTOR, and replys a reservation confirmation message Resv_Conf to transmitting terminal.The form of reservation confirmation message is as follows,
<Resv_Conf message> ::＝ <COMMONHEADER><SESSION><CONFIRM><ROUTEDESCRIPTOR>
Wherein, the form of public COMMON HEADER and session object SESSION confirms that the form of object CONFIRM and path description object ROUTE DESCRIPTOR is as follows as previously mentioned,
Confirm object CONFIRM, the value in classification Class territory is 2.It is divided into two types of IPv4 session and IPv6 sessions, and the value in IPv4 conversation type Type territory is 1, and the value in IPv6 conversation type Type territory is 2, and the content field form is as follows,
IPv4CONFIRM object Class=2, Type=1
0 8 16 24 31
++++++++++++++++++++++++++++++++++++++++++++++++
+ Source?IP?Address +
++++++++++++++++++++++++++++++++++++++++++++++++
+ Request?Msg?ID +
++++++++++++++++++++++++++++++++++++++++++++++++
IPv6 CONFIRM object Class=2, Type=2
0 8 16 24 31
+++++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Source?IP?Address +
+ +
+ +
+++++++++++++++++++++++++++++++++++++++++++++++++
+ Request?Msg?ID +
+++++++++++++++++++++++++++++++++++++++++++++++++
Source IPAddress: session source address, 32 of IPv4 addresses, 128 of IPv6 addresses.
Request Msg ID: the identifier of request message, 32, which resource reservation request what expression was confirmed is.
Path description object ROUTE DESCRIPTOR, the value in classification Class territory is 5.The content territory form and the explicit route object of object are identical, referring to RFC3209.The effect of path description object ROUTE DESCRIPTOR is that the originating end to session provides the resource reservation path to go through the Verbose Listing of node.
When reservation confirmation message Resv_Conf arrived the originating end of session, first resource reservation request process finished.The session source node just can utilize the routing information that writes down among the path description object ROUTEDESCRIPTOR to transmit session service.
As shown in Figure 1, the treatment step of each incident is as follows among Fig. 1:
Step S1.1: the session source node sends reservation requests Resv_Req message request to downstream node and sets up the resource reservation path, has comprised the desired QoS parameter of this session in this message;
Step S1.2: downstream node receives reservation requests Resv_Req;
Step S1.3: node judges whether oneself is the destination node of session, if, enter S1.22, if not, S1.4 entered;
Step S1.4: whether node is judged oneself has enough resource reservation to give this session, if having, to enter S1.5, if do not have, to enter S1.12;
Step S1.5: node is reserved enough resources with reference to the quality of service requirement among the reservation requests Resv_Req for this session;
Step S1.6: node is recorded in the information of this node among the record object RECORD ROUTE of path;
Step S1.7: node is according to routing table information or route display object EXPLICIT ROUTE chooses next-hop node;
Step S1.8:,, enter S1.10 if do not have if there is corresponding next-hop node to enter S1.9;
Step S1.9: node is sent out reservation requests Resv_Req to next redirect;
Step S1.10: node is removed and is this session reserved resource;
Step S1.11: node is removed the information of this node among the record object RECORD ROUTE of path;
Step S1.12: node judges whether the value of fault-tolerant territory AFT in the message is 0, if, enter S1.13, if not, S1.15 entered;
Step S1.13: node sends reservation error message Resv_Err to source node, and this message writes down the back transfer of record path among the object RECORD ROUTE along the path, and the node of going through all can be removed and be this session reserved resource;
Step S1.14: source node is received reservation error message Resv_Err, and failure is set up in the resource reservation path;
Step S1.15: the value of fault-tolerant territory AFT subtracts 1 in the message header;
Step S1.16: node sends reserves retry message Resv_Retry to a last hop node;
Step S1.17: a last hop node is received and is reserved retry message Resv_Retry;
Step S1.18: a last hop node attempts selecting other node to jump as next;
Step S1.19: if corresponding next-hop node is arranged, enter S1.20,, enter S1.10 if do not have;
Step S1.20: node re-constructs reservation requests Resv_Request according to reserving retry message Resv_Retry;
Step S1.21: node is sent out reservation requests Resv_Req to next redirect;
Step S1.22: reservation requests Resv_Req arrives the session destination node, and the destination node structure is confirmed object CONFIRM object and path description object ROUTE DESCRIPTOR;
Step S1.23: destination node sends reservation confirmation message Resv_Conf to the session source node;
Step S1.24: source node is received reservation confirmation message Resv_Conf, and the resource reservation path is set up successfully.
Claims (4)
1, a kind of resource reservation implementation method towards transmit leg with the ability of recalling is characterized in that this method may further comprise the steps:
The sending direction recipient sends a reservation requests Resv_Req, this reservation requests Resv_Req transmits downstream according to the route of routing algorithm selection or according to the route of explicit route object EXPLICITROUTE regulation, each node attempts reserving enough resources according to the service quality of stipulating among the reservation requests Resv_Req on the way, if reserve successfully, then reservation requests Resv_Req is continued to transmit downstream, simultaneously this node is recorded among the record object RECORD ROUTE of path; If reserve failure, then node is recalled inspection, whether the value of judging fault-tolerant territory AFT is 0, if the value of fault-tolerant territory AFT is not 0, then judge and upstream recall, this node subtracts 1 with the value of fault-tolerant territory AFT, and upwards a hop node sends a reservation retry message Resv_Retry, upstream node can be reselected next jumping after receiving and reserving retry message Resv_Retry, if corresponding next jumping is arranged then passes the reservation retry message Resv_Retry that comes and construct reservation requests Resv_Req according to the downstream, and send out to next redirect, if there is not next jumping, then recall inspection once more; After reservation requests Resv_Req arrives the session recipient, article one, the packet-switched path of reserved resource has just been set up, its each intermediate node information of going through is included among the record object RECORD ROUTE of path, the recipient should reserve successful acknowledge message Resv_Conf to one of transmit leg loopback, and this is reserved and comprises corresponding path description object RECORD ROUTE among the successful acknowledge message Resv_Conf; Check that the value of finding fault-tolerant territory AFT is 0 if recall, then reserve failure, failure node can send reservation error message Resv_Err to the session initiator, has comprised corresponding error description object ERRORSPEC among this reservation error message Resv_Err.
2, resource reservation implementation method with the ability of recalling according to claim 1 towards transmit leg, it is characterized in that, described transmit leg has the power to make decision of reserved resource, it constructs corresponding QoS parameter description object as required, how many resources this object has determined to need to reserve, the sending direction recipient sends reservation requests Resv_Req, remove among this reservation requests Resv_Req and comprise the QoS parameter description object, session object SESSION in order to descriptive session information, outside the path record object RECORD ROUTE in order to record path information, can also optionally comprise explicit route object EXPLICIT ROUTE, in addition, comprised a fault-tolerant territory AFT in the head of message, the value of fault-tolerant territory AFT shows the number of times that can recall in the reservation procedure, if reservation requests Resv_Req comprises explicit route object, the value of then fault-tolerant territory AFT must be set to 0.
3, the resource reservation implementation method towards transmit leg with the ability of recalling according to claim 2 is characterized in that, described QoS parameter description object comprises stream description object FLOWSPEC and filter description object FILTER_SPEC.
4, the resource reservation implementation method with the ability of recalling according to claim 1 towards transmit leg, its concrete steps are as follows:
Step S1.1: the session source node sends reservation requests Resv_Req request to downstream node and sets up the resource reservation path, has comprised the desired QoS parameter of this session among this reservation requests Resv_Req;
Step S1.2: downstream node receives reservation requests Resv_Req;
Step S1.3: node judges whether oneself is the destination node of session, if, enter S1.22, if not, S1.4 entered;
Step S1.4: whether node is judged oneself has enough resource reservation to give this session, if having, to enter S1.5, if do not have, to enter S1.12;
Step S1.5: node is reserved enough resources with reference to the quality of service requirement among the reservation requests Resv_Req for this session;
Step S1.6: node is recorded in the information of this node among the record object RECORDROUTE of path;
Step S1.7: node is according to routing table information or route display object EXPLICIT ROUTE chooses next-hop node;
Step S1.8:,, enter S1.10 if do not have if there is corresponding next-hop node to enter S1.9;
Step S1.9: node is sent out reservation requests Resv_Req to next redirect;
Step S1.10: node is removed and is this session reserved resource;
Step S1.11: node is removed the information of this node among the record object RECORD ROUTE of path;
Step S1.12: node judges whether the value of fault-tolerant territory AFT in the message is 0, if, enter S1.13, if not, S1.15 entered;
Step S1.13: node sends reservation error message Resv_Err to source node, and this message writes down the back transfer of record path among the object RECORD ROUTE along the path, and the node of going through all can be removed and be this session reserved resource;
Step S1.14: source node is received reservation error message Resv_Err, and failure is set up in the resource reservation path;
Step S1.15: the value of fault-tolerant territory AFT subtracts 1 in the message header;
Step S1.16: node sends reserves retry message Resv_Retry to a last hop node;
Step S1.17: a last hop node is received and is reserved retry message Resv_Retry;
Step S1.18: a last hop node attempts selecting other node to jump as next;
Step S1.19: if corresponding next-hop node is arranged, enter S1.20,, enter S1.10 if do not have;
Step S1.20: node re-constructs reservation requests Resv_Request according to reserving retry message Resv_Retry;
Step S1.21: node is sent out reservation requests Resv_Req to next redirect;
Step S1.22: reservation requests Resv_Req arrives the session destination node, and the destination node structure is confirmed object CONFIRM and path description object ROUTE DESCRIPTOR;
Step S1.23: destination node sends reservation confirmation message Resv_Conf to the session source node; Step S1.24: source node is received reservation confirmation message Resv_Conf, and the resource reservation path is set up successfully.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100989354A CN100346620C (en) | 2004-12-16 | 2004-12-16 | A transmitter-oriented resource reservation implementing method having backtracking ability |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100989354A CN100346620C (en) | 2004-12-16 | 2004-12-16 | A transmitter-oriented resource reservation implementing method having backtracking ability |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1633106A CN1633106A (en) | 2005-06-29 |
| CN100346620C true CN100346620C (en) | 2007-10-31 |
Family
ID=34847982
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100989354A Active CN100346620C (en) | 2004-12-16 | 2004-12-16 | A transmitter-oriented resource reservation implementing method having backtracking ability |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100346620C (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110753A (en) * | 2006-07-20 | 2008-01-23 | 华为技术有限公司 | End-to-end quality assurance method and system based on congestion alarm |
| CN101132297B (en) * | 2006-08-21 | 2011-04-13 | 华为技术有限公司 | Method and system for implementing multicast business, resource and admission control cell |
| CN101155046B (en) * | 2006-09-25 | 2011-06-22 | 华为技术有限公司 | Network control system and method for implementing multicast control |
| CN101155098B (en) * | 2006-09-28 | 2011-01-05 | 华为技术有限公司 | Wireless Mesh and its resource management method |
| CN101499954B (en) * | 2008-01-30 | 2012-06-06 | 华为技术有限公司 | Method for resource reservation and node equipment |
| CN102647333B (en) * | 2011-02-21 | 2016-03-30 | 中国移动通信集团公司 | Communication means under distributed base station system between baseband processing equipment and device |
| CN103593730B (en) * | 2013-10-30 | 2016-08-17 | 中国运载火箭技术研究院 | A kind of design parameter management system recalled |
| CN115250294B (en) * | 2021-04-25 | 2024-03-22 | 贵州白山云科技股份有限公司 | Cloud distribution-based data request processing method and system, medium and equipment thereof |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6385207B1 (en) * | 1997-12-23 | 2002-05-07 | Mediaone Group, Inc. | RSVP support for upstream traffic |
| JP2002374292A (en) * | 2001-06-18 | 2002-12-26 | Nec Corp | Communication path selection system |
| WO2003041431A1 (en) * | 2001-11-02 | 2003-05-15 | Interdigital Technology Corporation | Bi-directional and reverse directional resource reservation setup protocol |
-
2004
- 2004-12-16 CN CNB2004100989354A patent/CN100346620C/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6385207B1 (en) * | 1997-12-23 | 2002-05-07 | Mediaone Group, Inc. | RSVP support for upstream traffic |
| JP2002374292A (en) * | 2001-06-18 | 2002-12-26 | Nec Corp | Communication path selection system |
| WO2003041431A1 (en) * | 2001-11-02 | 2003-05-15 | Interdigital Technology Corporation | Bi-directional and reverse directional resource reservation setup protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1633106A (en) | 2005-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1188985C (en) | Jam control system of voice network through internet protocol | |
| CN1158830C (en) | Service parameter interworking method | |
| CN1153427C (en) | Method and device for data trunking processing and information discarding and program recording medium | |
| CN1925419A (en) | Resource acceptance control handling method | |
| CN1242593C (en) | Source address selection system, router device and communication joint and source address selection method | |
| CN1675909A (en) | Packet flow processing in a communication system | |
| CN1832447A (en) | Method for implementing user requiring mode resource preretention in net network | |
| CN1933478A (en) | Media stream packet assembling time length consultation method | |
| CN1764154A (en) | Route control method of label switch path | |
| CN1941753A (en) | IP interconnected gateway in next-generation Internet and method for interconnecting IP domain | |
| CN1852384A (en) | Method for realizing policy and charging rule decision | |
| CN101052154A (en) | IP multimedia sub system and its coding and decoding switching control method | |
| CN100346620C (en) | A transmitter-oriented resource reservation implementing method having backtracking ability | |
| CN1913503A (en) | Control method and system of session route path | |
| CN101047586A (en) | Service QoS ensuring method and device for radio mesh network | |
| CN1893304A (en) | Method for realizing provide of service quality assurance in wireless communication system | |
| CN1649344A (en) | Method for realizing interactive multimedia data transmission on internet | |
| CN101051993A (en) | Method for substituting conversation mark conversation replacing method using said conversation mark substitution | |
| CN1901742A (en) | Channel switching method | |
| CN101080097A (en) | A method, system and device for realizing multimedia call service | |
| CN1878388A (en) | Method for confirming data transmission service quality in communication network | |
| CN1838616A (en) | Media stream shunting system and method | |
| CN101060703A (en) | User equipment switching policy and charging control method | |
| CN101068199A (en) | Method, system, business and terminal for realizing convergence business | |
| CN1812453A (en) | Method for realizing message-leaving lamp and communication system |
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 | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Assignee: Beijing Zhongke Jingshang Technology Co., Ltd. Assignor: Institute of Computing Technology, Chinese Academy of Sciences Contract record no.: 2011110000143 Denomination of invention: A transmitter-oriented resource reservation implementing method having backtracking ability Granted publication date: 20071031 License type: Exclusive License Open date: 20050629 Record date: 20110823 |
|
| EC01 | Cancellation of recordation of patent licensing contract | ||
| EC01 | Cancellation of recordation of patent licensing contract |
Assignee: Beijing Zhongke Polytron Technologies Inc Assignor: Institute of Computing Technology, Chinese Academy of Sciences Contract record no.: 2011110000143 Date of cancellation: 20181212 |