CN100450049C - A method for implementing resource distribution - Google Patents
A method for implementing resource distribution Download PDFInfo
- Publication number
- CN100450049C CN100450049C CNB2003101003865A CN200310100386A CN100450049C CN 100450049 C CN100450049 C CN 100450049C CN B2003101003865 A CNB2003101003865 A CN B2003101003865A CN 200310100386 A CN200310100386 A CN 200310100386A CN 100450049 C CN100450049 C CN 100450049C
- Authority
- CN
- China
- Prior art keywords
- request
- load network
- resource
- network resource
- resource manager
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 189
- 230000004044 response Effects 0.000 claims description 241
- 230000008569 process Effects 0.000 claims description 107
- 230000008859 change Effects 0.000 claims description 82
- 238000012508 change request Methods 0.000 claims description 53
- 230000005540 biological transmission Effects 0.000 claims description 48
- 230000009191 jumping Effects 0.000 claims description 24
- 238000013468 resource allocation Methods 0.000 claims description 20
- 230000000977 initiatory effect Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000013439 planning Methods 0.000 abstract description 5
- 238000010276 construction Methods 0.000 abstract 1
- 238000007726 management method Methods 0.000 description 20
- 238000005516 engineering process Methods 0.000 description 8
- FGUUSXIOTUKUDN-IBGZPJMESA-N C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 Chemical compound C1(=CC=CC=C1)N1C2=C(NC([C@H](C1)NC=1OC(=NN=1)C1=CC=CC=C1)=O)C=CC=C2 FGUUSXIOTUKUDN-IBGZPJMESA-N 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012163 sequencing technique Methods 0.000 description 2
- 241000270666 Testudines Species 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000007727 signaling mechanism Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention discloses a method for implementing resource distribution, which comprises the steps: a, calling user equipment (UE) sends a call request to a calling call agent (CA); b. a calling CA sends a call request to a called CA; c. the calling CA or the called CA sends a resource connecting request to a resource manager of a source load net; the resource manager of the source load net establishes a route path according to the received resource connecting request, preserves bandwidth for the route path, and issues selected information of the route path to an entrance router so as to finish resource distribution. The present invention provides a standard resource distribution calling flow for resource distribution under different conditions, and unifies the methods of resource distribution under various conditions, so that operators can select proper equipment and implementing methods by using the present invention as a standard when planning networks and businesses. The present invention enhances the standardization degree of a differentiated service model which has an independent load control layer, and reduces the cost of network construction and maintenance.
Description
Technical field
(Diff-serv, DifferentiatedService) technology especially relate to a kind of method that realizes resource allocation to the present invention relates to the differentiated service of independent bearing layer.
Background technology
Along with the continuous increase of the Internet (Internet) scale, various service quality (QoS, Quality ofService) technology is arisen at the historic moment.Therefore, the Internet engineering duty group (IETF, Internet EngineeringTask Force) has been advised a lot of service models and mechanism, to satisfy the demand of QoS.What industry was relatively approved at present is to use integrated service model (Int-Serv, Integrated Service) at the access and the edge of network, uses differentiated service (Diff-serv, Differentiated Service) at server.Differentiated service is only set priority level and is ensured the QoS measure, though this QoS measure has the high characteristics of line efficiency, concrete effect is difficult to prediction.Therefore, in order further to improve the QoS technology, industry begins to introduce an independently bearer control layer for the backbone network differentiated service, sets up the qos signaling mechanism of the special differentiated service of a cover.This differentiated service is called as the differentiated service that independent bearing control layer is arranged.
Fig. 1 has the independently differentiated service figure of bearer control layer.As shown in Figure 1, in this model, bearer control layer 102 places between bearer network 103 and the service control layer 101.Call Agent (CA in service control layer 101, Call Agent) is service server, such as soft switch, video request program (VOD) Control Server, route gatekeeper (GK, Gate Keeper) etc., CA receives the call request of subscriber equipment, and proxy user equipment is finished the request and the exchange of calling; In bearer control layer 102, load network resource manager has disposed rule and network topology, service bandwidth application Resources allocation for the client, three load network resource manager have only been drawn among this figure, be load network resource manager 1 (104), load network resource manager 2 (105) and load network resource manager 3 (106), but the number of load network resource manager is not certain, and each load network resource manager is transmitted client's service bandwidth application request and result by signaling each other and is professional routed path information of applying for distribution etc.; In bearer network 103, each specific bearer network zone of load network resource manager management, this specific bearer network zone is called as the management domain of pairing load network resource manager, it among this figure the management domain 107 of load network resource manager 1, the management domain 108 of load network resource manager 2 and the management domain 109 of load network resource manager 3, comprise edge router (ER in the management domain 107, Edge Router) 110, core router 111 and border router (BR, Border Router) 112, wherein, ER can be linked into bearer network with the call business stream of subscriber equipment or draw bearer network, also comprises core router and border router in management domain 108 and the management domain 109.
At present, the differentiated service of existing not rare independently bearer control layer, as the bandwidth broker device model of serving key experimental network (Qbone, Quality-of-Service backbone).Fig. 2 is the bandwidth broker device illustraton of model of Qbone, as shown in Figure 2, bandwidth broker device 1 (201), what bandwidth broker device 2 (202) and bandwidth broker device 3 (203) were realized is exactly the function of load network resource manager, in this model, the bandwidth broker device is responsible for handling from subscriber's main station, service server or network maintenance staff's bandwidth application request, and according to the resource reservation situation of current network and configured strategy and the business service grade agreement (SLA that signs with the user, Service Level Agreement), determine whether to ratify user's bandwidth application.Writing down a large amount of static or dynamic information such as the configuration information of topology information, router of all kinds of SLA configuration informations, physical network and policy information, user authentication information, current resource obligate information, network seizure condition information in this Bandwidth Broker.Simultaneously, Bandwidth Broker also needs to write down routing iinformation, to establish user service flow path and cross-domain downstream bandwidth manager position.In this bandwidth broker device model, because the resource and the configuration information of the all-router in the direct management area of Bandwidth Broker are managed too complicated problems so exist topological sum; Simultaneously, because Bandwidth Broker needs the dynamic routing information in Minute book zone,, thereby cause the instability of network reservation so routing table update is frequent; And Bandwidth Broker also is difficult to consistent with the forwarding route of Business Stream reality according to the determined professional route of the dynamic routing information of one's respective area.Because the Bandwidth Broker model also exists above-mentioned these problems, so this pattern is not also put it into commercial operation.
In addition, the Rich QoS scheme that also has a kind of NEC Corporation to propose.Fig. 3 is the illustraton of model of Rich QoS scheme, as shown in Figure 3, QoS server 301 is as critical component, also comprise the strategic server 302 and LIST SERVER 303 and the network management monitoring server 304 that match with the QoS server, strategic server 302 is provided with the parameter and the configuration of relevant router according to policy configurations information such as QoS server 301 and management interfaces; LIST SERVER 303 is a unification and concentrated database, preserves configuring information of network appliance, user profile and QoS information; And the information such as congestion state that network management monitoring server 304 is responsible for collecting each router of bearer network and link, reference when being business application routing for the QoS server.The QoS server then is responsible for distributing the bearer path that meets the demands for the QoS service request according to the topological sum resource situation of bearer network.In actual applications, need on the QoS server, pre-set the topological sum bandwidth conditions of bearer network, configure the routing rule.When service server after the QoS server sends bandwidth request, the QoS server is noted down the resource request of this calling, and according to its qos requirement, and the current resource situation of current topological sum of bearer network is that service request is distributed the bearer path meet the demands, and distribution result is fed back service server.The QoS server also can be according to the bandwidth occupancy situation of business, send corresponding label switched path (LSP to strategic server, Label SwitchedPath) strategy modification order, strategic server are disposed the respective edges router according to the order of QoS server.In this scheme, the explicit route technology that edge router will use (MPLS) LSP to set up, and, rebulid or adjust LSP according to the path of QoS server appointment.
In above-mentioned Rich QoS scheme, the QoS server is managed remains complicated, a many bearer network of router quantity; Simultaneously, what QoS server and strategic server notice edge router used is that explicit route MPLS LSP sets up technology, sets up this pattern of LSP end to end, and autgmentability is very poor, network size is limited, can not adapt to the teleservice demand of a national public network.
Current problem is: in above-mentioned scheme, owing to be subjected to the restriction of each scheme shortcoming and the influence that each scheme is used the equipment and the network planning, so carrying out the method flow of resource allocation in such scheme has nothing in common with each other, neither one optimizes, unified standard, make the differentiated service standardization of bearer control layer independently not high, thereby increased the cost of networking and maintenance.
Summary of the invention
In view of this, main purpose of the present invention provides the method for carrying out resource allocation in the differentiated service that the independent bearing layer is arranged, the resource allocation call flow of standard is provided for the resource allocation under the different situations, thereby under the unified various situations resource allocation methods, make operator when the network planning and plan of operation, can be as Standard Selection suitable device and implementation method, improving has the independently standardization level of the differentiated service of bearer control layer, reduces the cost of networking and maintenance.
To achieve these goals, technical scheme of the present invention specifically is achieved in that
A kind of method that realizes resource allocation is characterized in that, this method may further comprise the steps:
A: calling subscriber equipment UE acts on behalf of CA to calling and sends call request;
B: caller CA sends call request to called CA;
C: caller CA or called CA send the connection resource request to the source load network resource manager, and described connection resource request is the request of forward connection resource, and the source load network resource manager is set up the forward routed path after receiving the request of described forward connection resource; Or described connection resource request is reverse connection resource request, and the source load network resource manager is set up reverse routed path after receiving described reverse connection resource request; Or described connection resource request is two-way connection resource request, and the source load network resource manager is set up two-way routed path after receiving described two-way connection resource request;
The source load network resource manager is the routed path bandwidth reserved of foundation, and issues the routed path information of choosing to ingress router, finishes resource allocation.
Comprise in the described call request: calling UE comprises the terminal iidentification of address information or the terminal iidentification and the called UE of calling UE to identification information, the call information of demand information, calling UE and the called UE of bandwidth resources in the identification information wherein,
Described address information can be IP address or domain name, and described terminal iidentification can be the number, H323 termination number, fax number of Session Initiation Protocol phone, E.164 number or e-mail address;
In step b, further comprise: called CA according to call request in the terminal iidentification of called UE determine the address information of called UE.
If the identification information of calling UE is a terminal iidentification in the call request, then further comprise in step a: caller CA determines the address information of calling UE according to this terminal iidentification.
Described step c specifically may further comprise the steps:
C1: called CA sends forward connection resource request and reverse connection resource request or two-way resource request to the source of reverse resource request load network resource manager;
C2: the source load network resource manager of the described reverse resource request of step c1 is carried out forward resource request process and reverse resource request process or two-way resource request process, set up forward routed path and reverse routed path or two-way routed path, and be this forward routed path and reverse routed path or two-way routed path bandwidth reserved;
C3: called CA sends call request to called UE;
C4: called UE is returned Temporary Response to request to called CA, if in this Temporary Response resource request is had change, and execution in step c5 then, otherwise the source load network resource manager issues the routed path information of choosing to ingress router, finishes resource allocation;
C5: called CA sends forward resource change request and reverse resource change request or two-way resource change request to the source of reverse resource request load network resource manager;
The described source of c6: step c5 load network resource manager is carried out forward resource change procedure and reverse resource change procedure or two-way resource change procedure, finishes resource allocation.
The described forward resource request of step c2 process specifically may further comprise the steps:
C21: the source load network resource manager of described reverse resource request is jumped load network resource manager to next and is sent the request of forward proxy resources;
C22: current load network resource manager is received the request of forward proxy resources, if the source load network resource manager that this current load network resource manager is the forward resource request, then this source load network resource manager is selected the forward routed path, and on this forward routed path bandwidth reserved, upwards one jump load network resource manager transmission forward resource request subsequently, carry out c23; Otherwise this current load network resource manager is jumped load network resource manager to next and is sent the request of forward proxy resources, returns step c22;
C23: after current load network resource manager is received the forward resource request, select the forward routed path, and on this forward routed path bandwidth reserved, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is jumped load network resource manager to next and is returned forward resource response, execution in step c24; Otherwise this current load network resource manager upwards one is jumped load network resource manager transmission forward resource request, returns step c23;
C24: current load network resource manager is received the forward resource response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource response, and upwards one jump the response of load network resource manager transmission forward proxy resources, execution in step c25; Otherwise, jump load network resource manager to next and return the forward resource response, return step c24;
C25: current load network resource manager is received the response of forward proxy resources, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is returned the response of forward connection resource to called CA; Otherwise, upwards one jump the response of load network resource manager transmission forward proxy resources, return step c25.
Comprise the demand information of called UE in described Temporary Response, forward resource change request, reverse resource change request and the two-way resource change request to bandwidth resources.
Forward resource change procedure described in the step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is jumped load network resource manager to next and is sent forward agency change request, and forward agency change request comprises that called UE in the forward resource change request is to the demand information of bandwidth resources;
C62: current load network resource manager is received forward agency change request, if the source load network resource manager that this current load network resource manager is the forward resource request, then this source load network resource manager is according to the bandwidth of called UE to the demand information change reservation of bandwidth resources, upwards one jump load network resource manager transmission forward resource change request, execution in step c63 subsequently; Otherwise this current load network resource manager is jumped load network resource manager to next and is sent forward agency change request, returns step c62;
C63: after current load network resource manager is received forward resource change request, according to the bandwidth of called UE to the demand information change reservation of bandwidth resources, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is jumped load network resource manager to next and is returned forward resource change response, execution in step c64; Otherwise this current load network resource manager upwards one is jumped load network resource manager transmission forward resource change request, returns step c63;
C64: current load network resource manager is received forward resource change response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource change response, issue the routed path information of forward to ingress router, and upwards one jump load network resource manager transmission forward agency change response, execution in step c65; Otherwise, jump load network resource manager to next and return forward resource change response, return step c64;
C65: current load network resource manager is received forward agency change response, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is returned forward connection resource change response to called CA; Otherwise, upwards one jump load network resource manager transmission forward agency change response, return step c65.
Reverse resource change procedure described in the step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is changed the bandwidth of reserving on the reverse routed path according to called UE to the demand information of bandwidth resources, and sends reverse resource change request to next jumping load network resource manager;
C62: current load network resource manager is received reverse resource change request, the demand information of bandwidth resources is changed the bandwidth of reserving on the reverse routed path according to called UE, if the purpose load network resource manager that this current load network resource manager is reverse resource request, then upwards a jumping load network resource manager is returned reverse resource change response, execution in step c63; Otherwise jump load network resource manager to next and send reverse resource change request, return step c62;
C63: current load network resource manager is received reverse resource change response, if the source load network resource manager that this current load network resource manager is reverse resource request, then set up whole reverse routed path according to the routed path information in this reverse resource change response, issue routed path information to ingress router, and return reverse resource change response to called CA; Otherwise upwards a jumping load network resource manager is returned reverse resource change response, returns step c63.
Two-way resource change procedure among the described step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is changed the bandwidth of reserving on the two-way routed path according to called UE to the demand information of bandwidth resources, and sends two-way resource change request to next jumping load network resource manager;
C62: current load network resource manager is received two-way resource change request, the demand information of bandwidth resources is changed the bandwidth of reserving on the two-way routed path according to called UE, if the purpose load network resource manager that this current load network resource manager is two-way resource request, then upwards a jumping load network resource manager is returned two-way resource change response, execution in step c63; Otherwise jump load network resource manager to next and send two-way resource change request, return step c62;
C63: current load network resource manager is received two-way resource change response, if the source load network resource manager that this current load network resource manager is described reverse resource request, then set up whole two-way routed path according to the routed path information in this two-way resource change response, issue routed path information to ingress router, and return two-way resource change response to called CA; Otherwise upwards a jumping load network resource manager is returned two-way resource change response, returns step c63.
After described step c, further comprising the steps of:
D: called CA to caller CA return to the request Temporary Response;
E: caller CA to calling UE return to the request Temporary Response;
F: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
G: called CA is to the affirmation of called UE transmission to the Temporary Response of request;
H: called UE is to the once more Temporary Response of called CA transmission to request;
I: called CA to caller CA return to the request Temporary Response once more;
J: caller CA to calling UE return to the request Temporary Response once more.
Step c specifically may further comprise the steps:
C1: called CA sends call request to called UE;
C2: called UE is to the Temporary Response of called CA transmission to request;
C3: after called CA receives Temporary Response to request, return Temporary Response to caller CA, and send reverse connection resource request, finish reverse resource request process to the source of reverse resource request load network resource manager to request; Caller CA returns Temporary Response to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process, end step c;
Perhaps, called CA receive to the request Temporary Response after, called CA to caller CA return to the request Temporary Response; Caller CA returns Temporary Response to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA receives that called CA directly sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process to behind the Temporary Response of asking, caller CA to calling UE return to the request Temporary Response, end step c.
After step c, further may further comprise the steps:
D: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
E: called CA is to the affirmation of called UE transmission to the Temporary Response of request;
F: called UE is to the once more Temporary Response of called CA transmission to request;
G: called CA to caller CA return to the request Temporary Response once more;
H: caller CA to calling UE return to the request Temporary Response once more.
Step c specifically may further comprise the steps:
C1: called CA returns Temporary Response to request to caller CA, and sends reverse connection resource request to the source of reverse resource request load network resource manager, finishes reverse resource request process; Caller CA returns Temporary Response to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process, end step c;
Perhaps, called CA to caller CA return to the request Temporary Response; Caller CA returns Temporary Response to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA returns Temporary Response to request to caller CA, and sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process, caller CA to calling UE return to the request Temporary Response, end step c.
After step c, further may further comprise the steps:
D: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
E: called CA sends call request to called UE;
F: called UE is to the once more Temporary Response of called CA transmission to request;
G: called CA to caller CA return to the request Temporary Response once more;
H: caller CA to calling UE return to the request Temporary Response once more.
Call request among the step b is the endpoint location call request, and step c specifically may further comprise the steps:
C1: called CA sends call request to called UE;
C2: called UE is to the affirmation of called CA transmission to request;
C3: called CA returns affirmation to the endpoint location call request to caller CA, and sends reverse connection resource request to the source of reverse resource request load network resource manager, finishes reverse resource request process; Caller CA returns affirmation to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process; End step c;
Perhaps, called CA returns affirmation to the endpoint location call request to caller CA; Caller CA returns affirmation to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA returns affirmation to the endpoint location call request to caller CA, and sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process, caller CA to calling UE return to the request affirmation, end step c.
Described forward resource request process specifically may further comprise the steps:
A1: after the source load network resource manager of forward resource request is received the request of forward connection resource, select the forward routed path, and on this forward routed path bandwidth reserved, jump load network resource manager to next subsequently and send the forward resource request;
A2: after current load network resource manager is received the forward resource request, select the forward routed path, and on this forward routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is the forward resource request, then upwards a jumping load network resource manager is returned forward resource response, execution in step A3; Otherwise, jump load network resource manager to next and send the forward resource request, return steps A 2;
A3: current load network resource manager is received the forward resource response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource response, issue the forward routed path to ingress router, finish the forward resource request, and return the response of forward connection resource to caller CA; Otherwise upwards a jumping load network resource manager is returned the forward resource response, returns steps A 3.
Described reverse resource request process specifically may further comprise the steps:
B1: the source load network resource manager of reverse resource request is selected reverse routed path after receiving reverse connection resource request, and on this reverse routed path bandwidth reserved, jump load network resource manager to next subsequently and send reverse resource request;
B2: after current load network resource manager is received reverse resource request, select reverse routed path, and on this reverse routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is reverse resource request, then upwards a jumping load network resource manager is returned reverse resource response, execution in step B3; Otherwise, jump load network resource manager to next and send reverse resource request, return step B2;
B3: current load network resource manager is received reverse resource response, if the source load network resource manager that this current load network resource manager is reverse resource request, then set up whole reverse routed path according to the routed path information in the reverse resource response, issue reverse routed path to ingress router, finish reverse resource request, and return reverse connection resource response to called CA; Otherwise upwards a jumping load network resource manager is returned reverse resource response, returns step B3.
Described two-way resource request process specifically may further comprise the steps:
C1: the load network resource manager that receives two-way connection resource request is selected two-way routed path, and on this two-way routed path bandwidth reserved, jump load network resource manager to next subsequently and send two-way resource request;
C2: after current load network resource manager is received two-way resource request, select two-way routed path, and on this two-way routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is two-way resource request, then upwards a jumping load network resource manager is returned two-way resource response, execution in step C3; Otherwise, jump load network resource manager to next and send two-way resource request, return step C2;
C3: current load network resource manager is received two-way resource response, if this current load network resource manager is the load network resource manager that receives two-way connection resource request, then set up whole two-way routed path according to the routed path information in the two-way resource response, issue two-way routed path to ingress router, finish two-way resource request, and return two-way connection resource response to called CA; Otherwise upwards a jumping load network resource manager is returned two-way resource response, returns step C3.
If called UE is made affirmation to request, then after sending the last Temporary Response of asking, described called UE further may further comprise the steps:
K: called CA to caller CA return to the request affirmation;
L: caller CA returns the above-mentioned affirmation to request to calling UE;
M: calling UE is returned response to above-mentioned affirmation to caller CA;
N: caller CA sends to called CA with the response of above-mentioned affirmation;
O: called CA sends to called UE with the response of above-mentioned affirmation.
If what use between UE and UA and the UA is the H323 agreement, then after step c, finish processing to this calling by the H323 agreement.
Owing to the present invention is directed to the agreement difference of using between bearer control layer inner and it and the CA, different resource allocation process flow processs is provided, the resource allocation call flow of standard is provided for the resource allocation under the different situations, thereby under the unified various situations resource allocation methods, make operator when the network planning and plan of operation, can be as Standard Selection suitable device and implementation method, improving has the independently standardization level of the differentiated service of bearer control layer, reduces the cost of networking and maintenance.
Description of drawings
Fig. 1 is the differentiated service figure that independent bearing control layer is arranged;
Fig. 2 is the bandwidth broker device illustraton of model of Qbone;
Fig. 3 is the illustraton of model of Rich QoS scheme;
Fig. 4 for when use between UE and CA and the CA be Session Initiation Protocol the time first kind of implementing procedure figure;
Fig. 5 for when use between UE and CA and the CA be Session Initiation Protocol the time second kind of implementing procedure figure;
Fig. 6 for when use between UE and CA and the CA be Session Initiation Protocol the time the third implementing procedure figure;
Fig. 7 for when use between UE and CA and the CA be Session Initiation Protocol the time the 4th kind of implementing procedure figure;
Fig. 8 for when use between UE and CA and the CA be the H323 agreement time a kind of implementing procedure figure.
Embodiment
The present invention is further described in more detail below in conjunction with the drawings and specific embodiments.
Subscriber equipment (UE) is different with the agreement that Call Agent (CA) uses, support to agreement is different with disposition, handling process between them is just different, in the differentiated service of bearer control layer is independently arranged, in most cases use Session initiation Protocol (SIP, Session Initial Protocol) with based on multimedia communication system (the Packet Based Multimedia CommunciationSystem) agreement of packet switching, be that the H323 agreement is carried out communication, following embodiment illustrates the handling process when using Session Initiation Protocol and the communication of H323 agreement respectively.
Fig. 1 is the differentiated service that independent bearing control layer is arranged, network configuration of the present invention is based on this model, as shown in Figure 1, subscriber equipment 1 is a calling UE, subscriber equipment 2 is a called UE, CA1 is caller CA, CA2 is called CA, ER1 (110) is for being linked into the forward Business Stream of this calling the ER of network, and ER1 is in the management domain 107 of load network resource manager 1, therefore, load network resource manager 1 (104) is the source load network resource manager of forward request or is the purpose load network resource manager of reverse request; ER2 (113) is the ER that the reverse Business Stream of this calling can be introduced present networks, and ER2 is in the management domain 109 of load network resource manager 3, therefore, load network resource manager 3 (106) is the purpose load network resource manager of forward request or the source load network resource manager of reverse request, load network resource manager 2 (105) is for except that source load network resource manager and purpose load network resource manager, this request the load network resource manager of process, be called load network resource manager midway herein, management domain 107 is the management domain of load network resource manager 1 (104), management domain 108 is the management domain of load network resource manager 2 (105) midway, and management domain 109 is the management domain of load network resource manager 3 (106).In some cases, may there be load network resource manager midway, also have a plurality of load network resource manager midway, in the present embodiment, have only a load network resource manager midway.
When use between UE and CA and the CA be Session Initiation Protocol the time, the implementing procedure that carries out resource allocation in the differentiated service that the independent bearing layer is arranged has several, Fig. 4 is first kind of implementing procedure figure wherein, as shown in Figure 1 and Figure 4, this flow process may further comprise the steps:
Step 401: calling subscriber equipment UE1 sends call request to CA1, this call request is meant sensu lato call request, be INVITE herein, comprise among this INVITE: the identification information of UE1 and UE2, call information and UE1 are to the demand information of bandwidth resources, comprise the address information of UE1 or the terminal iidentification of terminal iidentification and UE2 in the identification information wherein, this address information can be IP address or domain name, and this terminal iidentification can be the number, H323 termination number, fax number of SIP phone, E.164 number or Email (Email) address;
Step 402:CA1 receives the INVITE that UE1 sends, if the identification information of UE1 is a terminal iidentification, then CA1 determines the address information of UE1 according to this terminal iidentification, and to CA2 transmission INVITE, comprise among this INVITE: the identification information of UE1 and UE2, call information and UE1 comprise the address information of UE1 and the terminal iidentification of UE2 to the demand information of bandwidth resources in the identification information wherein;
Step 403:CA2 receives the INVITE that CA1 sends, determine the address information of UE2 according to the terminal iidentification of UE2, and to load network resource manager 3 transmission forward connection resource requests, this forward connection resource request comprises caller and called address information and Qos parameter, comprises the demand information of UE1 to bandwidth resources in this Qos parameter;
Step 404: load network resource manager 3 is received the request of forward connection resource, because load network resource manager 3 is not the source load network resource manager of forward resource request, so, load network resource manager 3 upwards one is jumped load network resource manager, be that load network resource manager 2 sends the request of forward proxy resources, this forward proxy resources request comprises caller and called address information and Qos parameter;
Step 405: load network resource manager 2 upwards one is jumped load network resource manager, and promptly load network resource manager 1 sends the request of forward proxy resources, and this forward proxy resources request comprises caller and called address information and Qos parameter;
Step 406: because load network resource manager 1 is the source load network resource manager of forward resource request, so, load network resource manager 1 begins to select forward LSP, and on this forward LSP bandwidth resource, jump load network resource manager to next subsequently, be that load network resource manager 2 sends the forward resource request, this forward resource request comprises caller and called address information and Qos parameter;
Step 407: load network resource manager 2 is selected forward LSP, and on this forward LSP bandwidth resource, jump load network resource manager to next subsequently, be that load network resource manager 3 sends the forward resource request, this forward resource request comprises caller and called address information and Qos parameter;
Step 408: load network resource manager 3 is selected forward LSP, and on this forward LSP bandwidth resource, because load network resource manager 3 is the purpose load network resource manager of forward resource request, so, upwards one jump load network resource manager, be that load network resource manager 2 sends the forward resource response, comprise the forward LSP that load network resource manager 3 is selected in this forward resource response;
Step 409: load network resource manager 2 sends the forward resource response to load network resource manager 1, comprises the forward LSP that load network resource manager 2 and load network resource manager 3 are selected in this forward resource response;
Step 410: load network resource manager 1 is set up whole forward LSP, confirm the bandwidth resources of reservation, finish the distribution of forward resource, and send the response of forward proxy resources to load network resource manager 2, this forward proxy resources response expression forward resource request completes successfully;
Step 411: load network resource manager 2 sends the response of forward proxy resources to load network resource manager 3, and this forward proxy resources response expression forward resource request completes successfully;
Step 412: load network resource manager 3 sends the response of forward connection resource to CA2, and this forward connection resource response expression forward resource request completes successfully;
Step 413:CA2 sends reverse connection resource request to load network resource manager 3, and this reverse connection resource request comprises caller and called address information and Qos parameter, comprises the demand information of UE1 to bandwidth resources in this Qos parameter;
Step 414: because load network resource manager 3 is the source load network resource manager of reverse request, so, load network resource manager 3 begins to select reverse LSP, bandwidth resource on this reverse LSP, and to the reverse resource request of load network resource manager 2 transmissions, this reverse resource request comprises caller and called address information and Qos parameter;
Step 415: load network resource manager 2 is selected reverse LSP, bandwidth resource on this reverse LSP, and to the reverse resource request of load network resource manager 1 transmission, this reverse resource request comprises caller and called address information and Qos parameter;
Step 416: load network resource manager 1 is selected reverse LSP, bandwidth resource on this reverse LSP, because load network resource manager 1 is the purpose load network resource manager of reverse request, so, load network resource manager 1 sends reverse resource response to load network resource manager 2, comprises the reverse LSP that load network resource manager 1 is selected in this reverse resource response;
Step 417: load network resource manager 2 sends reverse resource response to load network resource manager 3, comprises the reverse LSP of load network resource manager 1 selection and the reverse LSP that load network resource manager 2 is selected in this reverse resource response;
Step 418: load network resource manager 3 is set up whole reverse LSP, confirms the bandwidth resources of reservation, finishes the distribution of reverse resource, and sends reverse connection resource response to CA2, and the reverse resource request of this reverse connection resource response expression completes successfully;
Step 419:CA2 sends INVITE to UE2;
Step 420:UE2 returns asking the Temporary Response of INVITE to CA2, be 183 responses herein, this 183 response expression UE2 acknowledges receipt of INVITE, comprising the demand information of UE2 to bandwidth resources, if this demand information is different or different with the last existing called port information of called CA to the demand information of bandwidth resources with UE1, then execution in step 421, otherwise execution in step 437;
Step 421:CA2 sends reverse resource change request to load network resource manager 3, comprises the demand information of UE2 to bandwidth resources in this change request;
Step 422: load network resource manager 3 is changed reverse LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and sends reverse resource change request to load network resource manager 2;
Step 423: load network resource manager 2 is changed reverse LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and sends reverse resource change request to load network resource manager 1;
Step 424: load network resource manager 1 is changed reverse LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and return reverse resource to load network resource manager 2 and change response, the bandwidth resources on the reverse LSP of this reverse resource change response expression are successfully changed;
Step 425: load network resource manager 2 is returned reverse resource change response to load network resource manager 3;
Step 426: load network resource manager 3 is returned reverse resource change response to CA2;
Step 427:CA2 sends forward resource change request to load network resource manager 3, comprises the demand information of UE2 to bandwidth resources in this change request;
Step 428: because load network resource manager 3 is not the source load network resource manager of forward request, so load network resource manager 3 sends forward agency change request to load network resource manager 2;
Step 429: load network resource manager 2 sends forward agency change request to load network resource manager 1;
Step 430: because load network resource manager 1 is the source load network resource manager of forward request, so, load network resource manager 1 is changed forward LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and asks to load network resource manager 2 transmission forward resources changes;
Step 431: load network resource manager 2 is changed forward LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and asks to load network resource manager 3 transmission forward resources changes;
Step 432: load network resource manager 3 is changed forward LSP according to UE2 to the demand information of bandwidth resources and is gone up the bandwidth resources of reserving, and return the forward resource to load network resource manager 2 and change response, the bandwidth resources on this forward resource change response expression forward LSP are successfully changed;
Step 433: load network resource manager 2 is returned forward resource change response to load network resource manager 1;
Step 434: load network resource manager 1 is returned forward agency change response to load network resource manager 2, and the bandwidth resources on this forward agency change response expression forward LSP are successfully changed;
Step 435: load network resource manager 2 is returned forward agency change response to load network resource manager 3;
Step 436: load network resource manager 3 is returned forward resource change response to CA2;
Step 437:CA2 returns 183 above-mentioned responses to CA1;
Step 438:CA1 returns 183 above-mentioned responses to UE1;
Step 439:CA1 sends the affirmation that responds 183, i.e. PRACK to CA2;
Step 440:CA2 sends above-mentioned PRACK to UE2;
Step 441:UE2 is the ring response to the Temporary Response once more of CA2 transmission to request herein, i.e. 180 responses;
Step 442:CA2 sends to CA1 with 180 above-mentioned responses;
Step 443:CA1 sends to UE1 with 180 above-mentioned responses, and this moment, UE1 can hear ring-back tone;
Step 444: confirm reaction when UE2 makes, during such as the UE2 off-hook, UE2 is 200 responses to the affirmation of CA2 transmission to request herein;
Step 445:CA2 returns 200 above-mentioned responses to CA1;
Step 446:CA1 returns 200 above-mentioned responses to UE1;
Step 447:UE1 responds to the affirmation that CA1 returns 200 responses, is ACK herein;
Step 448:CA1 sends to CA2 with above-mentioned ACK;
Step 449:CA2 sends to UE2 with above-mentioned ACK, process ends.
In above-mentioned flow process, step 403 is a forward resource request process to step 412, and step 413 is reverse resource request process to step 418; This forward resource request process and reverse resource request process do not have fixing sequencing, also can first reverse resource request, and back forward resource request, perhaps forward resource request and reverse resource request are carried out simultaneously.
Step 421 is reverse resource change procedure to step 426, step 427 is to step 436 forward resource change procedure, this forward resource change procedure and reverse resource change procedure do not have fixing sequencing, also can carry out the change of forward resource earlier, after carry out the change of reverse resource, perhaps change of forward resource and reverse resource are changed and are carried out simultaneously.
Above-mentioned forward resource request process and reverse resource request process can be replaced by two-way resource request process, above-mentioned reverse resource change procedure and forward resource change procedure also can be replaced by two-way resource change procedure, in this implementing procedure, the source load network resource manager of two-way resource request and two-way resource change request is a load network resource manager 3, and the purpose load network resource manager is a load network resource manager 1.
Two-way resource request process specifically may further comprise the steps:
A, CA2 send two-way resource connection request to load network resource manager 3;
B, load network resource manager 3 are selected two-way routed path after receiving two-way connection resource request, and according to demand information bandwidth reserved on this two-way routed path of bandwidth resources, send two-way resource request to load network resource manager 2 subsequently;
After c, load network resource manager 2 are received two-way resource request, select two-way routed path, and, send two-way resource request to load network resource manager 1 according to demand information bandwidth reserved on this two-way routed path of bandwidth resources;
After d, load network resource manager 1 are received two-way resource request, select two-way routed path, and, return two-way resource response to load network resource manager 2 according to demand information bandwidth reserved on this two-way routed path of bandwidth resources;
E, load network resource manager 2 are received two-way resource response, return two-way resource response to load network resource manager 3;
F, load network resource manager 3 are set up whole two-way routed path according to the routed path information in the two-way resource response of receiving, issue two-way routed path to ingress router, and return two-way resource connection response to CA2, finish two-way resource request.
Above-mentioned two-way resource change procedure specifically may further comprise the steps:
A, CA2 send two-way resource change request to load network resource manager 3;
B, load network resource manager 3 are changed the bandwidth of reserving on the two-way routed path according to called UE to the demand information of bandwidth resources, and send two-way resource change request to load network resource manager 2;
C, load network resource manager 2 are received two-way resource change request, according to called UE the demand information of bandwidth resources are changed the bandwidth of reserving on the two-way routed path, send two-way resource change request to load network resource manager 1;
D, load network resource manager 1 are changed the bandwidth of reserving on the two-way routed path according to called UE to the demand information of bandwidth resources, return two-way resource change response to load network resource manager 2;
E: load network resource manager 2 is received two-way resource change response, returns two-way resource change response to load network resource manager 3;
F, load network resource manager 3 are set up whole two-way routed path according to the routed path information in the two-way resource change response of receiving, issue routed path information to ingress router, and return two-way resource change response to CA2.
Fig. 5 for when use between UE and CA and the CA be Session Initiation Protocol the time second kind of implementing procedure figure, as Fig. 1 and shown in Figure 5, this flow process may further comprise the steps:
Step 501 is identical with step 401 and step 402 with step 502, is call request procedure;
Step 503:CA2 sends INVITE to UE2;
Step 504 is identical with step 420, and UE2 returns asking the Temporary Response of INVITE to CA2;
Step 505:CA2 returns 183 responses to CA1, comprises the IP address of UE2 in this 183 response;
Step 506:CA1 returns 183 responses to UE1;
Step 507:CA2 sends reverse connection resource request to load network resource manager 3, and this reverse connection resource request comprises caller and called address information and Qos parameter, comprises UE1 and the UE2 demand information to bandwidth resources in this Qos parameter;
Step 508: because load network resource manager 3 is the source load network resource manager of reverse request, so, load network resource manager 3 begins to select reverse LSP, according to the demand information bandwidth resource on this reverse LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, and to the reverse resource request of load network resource manager 2 transmissions, this reverse resource request comprises caller and called address information and Qos parameter;
Step 509: load network resource manager 2 is selected reverse LSP, according to the demand information bandwidth resource on this reverse LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, and to the reverse resource request of load network resource manager 1 transmission, this reverse resource request comprises caller and called address information and Qos parameter;
Step 510: load network resource manager 1 is selected reverse LSP, according to the demand information bandwidth resource on this reverse LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, because load network resource manager 1 is the purpose load network resource manager of reverse request, so, load network resource manager 1 sends reverse resource response to load network resource manager 2, comprises the reverse LSP that load network resource manager 1 is selected in this reverse resource response;
Step 511: load network resource manager 2 sends reverse resource response to load network resource manager 3, comprises the reverse LSP of load network resource manager 1 selection and the reverse LSP that load network resource manager 2 is selected in this reverse resource response;
Step 512: load network resource manager 3 is set up whole reverse LSP, confirms the bandwidth resources of reservation, finishes the distribution of reverse resource, and sends reverse connection resource response to CA2, and the reverse resource request of this reverse connection resource response expression completes successfully;
Step 513:CA1 sends the request of forward connection resource to load network resource manager 1, and this forward connection resource request comprises caller and called address information and Qos parameter, comprises UE1 and the UE2 demand information to bandwidth resources in this Qos parameter;
Step 514: because load network resource manager 1 is the source load network resource manager of forward request, so, load network resource manager 1 begins to select forward LSP, according to the demand information bandwidth resource on this forward LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, and to the reverse resource request of load network resource manager 2 transmissions, this forward resource request comprises caller and called address information and Qos parameter;
Step 515: load network resource manager 2 is selected forward LSP, according to the demand information bandwidth resource on this forward LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, and to load network resource manager 3 transmission forward resource request, this forward resource request comprises caller and called address information and Qos parameter;
Step 516: load network resource manager 3 is selected forward LSP, according to the demand information bandwidth resource on this forward LSP of UE1 and UE2 in the Qos parameter to bandwidth resources, because load network resource manager 3 is the purpose load network resource manager of forward request, so, load network resource manager 3 sends reverse resource response to load network resource manager 2, comprises the forward LSP that load network resource manager 3 is selected in this reverse resource response;
Step 517: load network resource manager 2 sends the forward resource response to load network resource manager 1, comprises the forward LSP of load network resource manager 3 selections and the forward LSP that load network resource manager 2 is selected in this forward resource response;
Step 518: load network resource manager 1 is set up whole reverse LSP, confirms the bandwidth resources of reservation, finishes the distribution of forward resource, and sends the response of forward connection resource to CA1, and this forward connection resource response expression forward resource request completes successfully;
Step 519 is identical to step 449 with step 439 to step 529, is the subsequent process of finishing calling.
In flow process shown in Figure 5, in above-mentioned flow process, step 507 is reverse resource request process to step 512, and step 513 is a forward resource request process to step 518, and reverse resource request process wherein can be carried out after CA2 receives 183 responses immediately; Forward resource request process can be carried out after CA1 receives 183 responses immediately.
Forward resource request process in the flow process shown in Figure 5 and reverse resource request process can be replaced by two-way resource request process, the source load network resource manager of two-way resource request can be load network resource manager 3 or load network resource manager 1, in this implementing procedure, the source load network resource manager of two-way resource request is a load network resource manager 3, and the purpose load network resource manager is a load network resource manager 1.Step a in the detailed process of two-way resource request and the first kind of implementing procedure is identical to step f.
Fig. 6 for when use between UE and CA and the CA be Session Initiation Protocol the time the third implementing procedure figure, as Fig. 1 and shown in Figure 6, this flow process may further comprise the steps:
Step 601 is identical with step 401 and step 402 with step 602, is call request procedure;
Step 603:CA2 sends INVITE to UE2;
Step 604:UE2 sends 180 responses to CA2, comprises the demand information of UE2 to bandwidth resources in this response;
Step 605 is identical with step 507 to 512 to step 610, is reverse resource request process;
Step 611:CA2 returns 180 responses to CA1;
Step 612:CA1 returns 180 responses to UE1, comprises the IP address of UE2 in this 180 response;
Step 613 is identical to step 518 with step 513 to step 618, is forward resource request process;
Step 619 is identical to step 449 with step 444 to step 624, for finishing the subsequent process of calling.
In the flow process shown in Figure 6, forward resource request process also can be carried out after CA1 receives 180 responses immediately.
Forward resource request process in the flow process shown in Figure 6 and reverse resource request process can be replaced by two-way resource request process, the source load network resource manager of two-way resource request can be load network resource manager 3 or load network resource manager 1, in this implementing procedure, the source load network resource manager of two-way resource request is a load network resource manager 3, and the purpose load network resource manager is a load network resource manager 1.Step a in the detailed process of two-way resource request and the first kind of implementing procedure is identical to step f.
Fig. 7 for when use between UE and CA and the CA be Session Initiation Protocol the time the 4th kind of implementing procedure figure, as Fig. 1 and shown in Figure 7, this flow process may further comprise the steps:
Step 701 is identical to step 402 with step 401 to step 702, is call request procedure;
Step 703 is identical with step 420, and UE2 returns asking the Temporary Response of INVITE to CA2;
Step 704:CA2 returns 183 responses to CA1, comprises the IP address of UE2 in this 183 response;
Step 705 is identical to step 512 with step 507 to step 710, is reverse resource request process;
Step 711 is identical to step 518 with step 513 to step 716, is forward resource request process;
Step 717 is identical with step 439, and CA1 sends the affirmation that responds 183 to CA2;
Step 718:CA2 sends INVITE to UE2;
Step 719 is identical to step 449 with step 441 to step 727, is the subsequent process of finishing calling.
In the flow process shown in Figure 7, reverse resource request process also can be carried out after CA2 receives INVITE immediately, and forward resource request process also can be carried out after CA1 receives 183 responses immediately.
Forward resource request process in the flow process shown in Figure 7 and reverse resource request process can be replaced by two-way resource request process, the source load network resource manager of two-way resource request can be load network resource manager 3 or load network resource manager 1, in this implementing procedure, the source load network resource manager of two-way resource request is a load network resource manager 3, and the purpose load network resource manager is a load network resource manager 1.Step a in the detailed process of two-way resource request and the first kind of implementing procedure is identical to step f.
Fig. 8 for when use between UE and CA and the CA be the H323 agreement time a kind of implementing procedure figure, as Fig. 1 and shown in Figure 8, this flow process may further comprise the steps:
Step 801: calling subscriber equipment UE1 sends call request to CA1, this call request is meant sensu lato call request, it is call admission request (ARQ) herein, comprise among this ARQ: the identification information of UE1 and UE2, call information and UE1 are to the demand information of bandwidth resources, comprise the address information of UE1 or the terminal iidentification of terminal iidentification and UE2 in the identification information wherein, this address information can be IP address or domain name, and this terminal iidentification can be the number or Email (Email) address of SIP phone;
Step 802:CA1 receives the ARQ that UE1 sends, if the identification information of UE1 is a terminal iidentification, then CA1 determines the address information of UE1 according to this terminal iidentification, and send the endpoint location call request (LRQ) of CA1 to CA2, comprise among this LRQ: the identification information of UE1 and UE2, call information and UE1 comprise the address information of UE1 and the terminal iidentification of UE2 to the demand information of bandwidth resources in the identification information wherein;
Step 803:CA2 sends ARQ to UE2;
Step 804:UE2 returns affirmation to ARQ to CA2, is that call acceptance confirms (ACF) herein, and this ACF represents that UE2 acknowledges receipt of ARQ, comprising the demand information of UE2 to bandwidth resources;
Step 805:CA2 returns affirmation to LRQ to CA1, for endpoint location confirms (LCF), comprises the IP address of UE2 to the demand information and the UE2 of bandwidth resources among this LCF herein;
Step 806:CA1 returns ACF to UE1;
Step 807 is identical to step 512 with step 507 to step 812, is reverse resource request process;
Step 813 is identical to step 518 with step 513 to step 818, is forward resource request process;
Step 819:H.323 agreement is finished the processing of this calling.
After this step, H.323 the agreement Q.931 processing of agreement and H245 protocol specification in addition, above-mentioned forward and reverse resource request process also can be finished in any one stage after these two protocol processes, purpose is before media delivery subsequently, set up routed path to transmit Business Stream at bearing bed, the concrete processing procedure of this step is a known technology, and no longer huge legendary turtle is stated herein.
In the flow process shown in Figure 8, reverse resource request process also can be carried out when CA2 receives ACF immediately, and forward resource request process also can be carried out when CA1 receives LCF immediately, in this flow process, what use between UE and UA and the UA is the H323 agreement, and this moment, CA was equivalent to the GK among the H323.
Forward resource request process in the flow process shown in Figure 8 and reverse resource request process can be replaced by two-way resource request process, the source load network resource manager of two-way resource request can be load network resource manager 3 or load network resource manager 1, in this implementing procedure, the source load network resource manager of two-way resource request is a load network resource manager 3, and the purpose load network resource manager is a load network resource manager 1.The detailed process of two-way resource request with when use between UE and CA and the CA be Session Initiation Protocol the time first kind of flow process in step a to step f identical.
In above-mentioned flow chart, because CM need support multiple business such as speech, video conferencing, VOD simultaneously, so CA can be equipment such as SoftSwitch, VOD Control Server, GK.Some UE with intelligent function also can be directly as CA, but this moment user identity checking, fail safe can't guarantee that professional charging is also difficult to be realized, so do not recommend to use the method.
In above-mentioned flow process, if calling UE is supported Session Initiation Protocol, called UE is supported H.323 agreement, and is perhaps just opposite, and CA supports the both.Just need Session Initiation Protocol and protocol interconnection H.323 be changed both message according to network and equipment situation in this case, that is to say, INVITE can be converted to ARQ or LRQ; 183 responses or 180 responses can be converted to ACF or LCF.But the effect of these message can not change, and promptly INVITE, ARQ and LRQ are call request; 183 responses, 180 responses, ACF and LCF are to request responding.
Owing to the present invention is directed to the agreement difference of using between bearer control layer inner and it and the CA, different resource request handling processes is provided, the resource request call flow of standard is provided for the resource request under the different situations, thereby under the unified various situations the resource request method, make operator when the network planning and plan of operation, can be as Standard Selection suitable device and implementation method, improving has the independently standardization level of the differentiated service of bearer control layer, reduces the cost of networking and maintenance.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with the people of this technology in the disclosed technical scope of the present invention; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.
Claims (21)
1, a kind of method that realizes resource allocation is characterized in that, this method may further comprise the steps:
A: calling subscriber equipment UE acts on behalf of CA to calling and sends call request;
B: caller CA sends call request to called CA;
C: caller CA or called CA send the connection resource request to the source load network resource manager, and described connection resource request is the request of forward connection resource, and the source load network resource manager is set up the forward routed path after receiving the request of described forward connection resource; Or described connection resource request is reverse connection resource request, and the source load network resource manager is set up reverse routed path after receiving described reverse connection resource request; Or described connection resource request is two-way connection resource request, and the source load network resource manager is set up two-way routed path after receiving described two-way connection resource request;
The source load network resource manager is the routed path bandwidth reserved of foundation, and issues the routed path information of choosing to ingress router, finishes resource allocation.
2, the method for claim 1, it is characterized in that, comprise in the described call request: calling UE comprises the terminal iidentification of address information or the terminal iidentification and the called UE of calling UE to identification information, the call information of demand information, calling UE and the called UE of bandwidth resources in the identification information wherein.
3, method as claimed in claim 2, it is characterized in that, described address information can be IP address or domain name, and described terminal iidentification can be the number, H323 termination number, fax number of Session Initiation Protocol phone, E.164 number or e-mail address.
4, method as claimed in claim 2 is characterized in that, further comprises in step b: called CA according to call request in the terminal iidentification of called UE determine the address information of called UE;
If the identification information of calling UE is a terminal iidentification in the call request, then further comprise in step a: caller CA determines the address information of calling UE according to this terminal iidentification.
5, the method for claim 1 is characterized in that, described step c comprises that specifically the following step poly-
C1: called CA sends forward connection resource request and reverse connection resource request or two-way resource request to the source of reverse resource request load network resource manager;
C2: the source load network resource manager of the described reverse resource request of step c1 is carried out forward resource request process and reverse resource request process or two-way resource request process, set up forward routed path and reverse routed path or two-way routed path, and be this forward routed path and reverse routed path or two-way routed path bandwidth reserved;
C3: called CA sends call request to called UE;
C4: called UE is returned Temporary Response to request to called CA, if in this Temporary Response resource request is had change, and execution in step c5 then, otherwise the source load network resource manager issues the routed path information of choosing to ingress router, finishes resource allocation;
C5: called CA sends forward resource change request and reverse resource change request or two-way resource change request to the source of reverse resource request load network resource manager;
The described source of c6: step c5 load network resource manager is carried out forward resource change procedure and reverse resource change procedure or two-way resource change procedure, finishes resource allocation.
6, method as claimed in claim 5 is characterized in that, the described forward resource request of step c2 process specifically may further comprise the steps:
C21: the source load network resource manager of described reverse resource request is jumped load network resource manager to next and is sent the request of forward proxy resources;
C22: current load network resource manager is received the request of forward proxy resources, if the source load network resource manager that this current load network resource manager is the forward resource request, then this source load network resource manager is selected the forward routed path, and on this forward routed path bandwidth reserved, upwards one jump load network resource manager transmission forward resource request subsequently, carry out c23; Otherwise this current load network resource manager is jumped load network resource manager to next and is sent the request of forward proxy resources, returns step c22;
C23: after current load network resource manager is received the forward resource request, select the forward routed path, and on this forward routed path bandwidth reserved, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is jumped load network resource manager to next and is returned forward resource response, execution in step c24; Otherwise this current load network resource manager upwards one is jumped load network resource manager transmission forward resource request, returns step c23;
C24: current load network resource manager is received the forward resource response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource response, and upwards one jump the response of load network resource manager transmission forward proxy resources, execution in step c25; Otherwise, jump load network resource manager to next and return the forward resource response, return step c24;
C25: current load network resource manager is received the response of forward proxy resources, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is returned the response of forward connection resource to called CA; Otherwise, upwards one jump the response of load network resource manager transmission forward proxy resources, return step c25.
7, method as claimed in claim 5 is characterized in that, comprises the demand information of called UE to bandwidth resources in described Temporary Response, forward resource change request, reverse resource change request and the two-way resource change request.
8, method as claimed in claim 7 is characterized in that, the forward resource change procedure described in the step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is jumped load network resource manager to next and is sent forward agency change request, and forward agency change request comprises that called UE in the forward resource change request is to the demand information of bandwidth resources;
C62: current load network resource manager is received forward agency change request, if the source load network resource manager that this current load network resource manager is the forward resource request, then this source load network resource manager is according to the bandwidth of called UE to the demand information change reservation of bandwidth resources, upwards one jump load network resource manager transmission forward resource change request, execution in step c63 subsequently; Otherwise this current load network resource manager is jumped load network resource manager to next and is sent forward agency change request, returns step c62;
C63: after current load network resource manager is received forward resource change request, according to the bandwidth of called UE to the demand information change reservation of bandwidth resources, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is jumped load network resource manager to next and is returned forward resource change response, execution in step c64; Otherwise this current load network resource manager upwards one is jumped load network resource manager transmission forward resource change request, returns step c63;
C64: current load network resource manager is received forward resource change response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource change response, issue the routed path information of forward to ingress router, and upwards one jump load network resource manager transmission forward agency change response, execution in step c65; Otherwise, jump load network resource manager to next and return forward resource change response, return step c64;
C65: current load network resource manager is received forward agency change response, if the source load network resource manager that this current load network resource manager is reverse resource request, then this source load network resource manager is returned forward connection resource change response to called CA; Otherwise, upwards one jump load network resource manager transmission forward agency change response, return step c65.
9, method as claimed in claim 7 is characterized in that, the reverse resource change procedure described in the step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is changed the bandwidth of reserving on the reverse routed path according to called UE to the demand information of bandwidth resources, and sends reverse resource change request to next jumping load network resource manager;
C62: current load network resource manager is received reverse resource change request, the demand information of bandwidth resources is changed the bandwidth of reserving on the reverse routed path according to called UE, if the purpose load network resource manager that this current load network resource manager is reverse resource request, then upwards a jumping load network resource manager is returned reverse resource change response, execution in step c63; Otherwise jump load network resource manager to next and send reverse resource change request, return step c62;
C63: current load network resource manager is received reverse resource change response, if the source load network resource manager that this current load network resource manager is reverse resource request, then set up whole reverse routed path according to the routed path information in this reverse resource change response, issue routed path information to ingress router, and return reverse resource change response to called CA; Otherwise upwards a jumping load network resource manager is returned reverse resource change response, returns step c63.
10, method as claimed in claim 7 is characterized in that, the two-way resource change procedure among the described step c6 specifically may further comprise the steps:
C61: the source load network resource manager of described reverse resource request is changed the bandwidth of reserving on the two-way routed path according to called UE to the demand information of bandwidth resources, and sends two-way resource change request to next jumping load network resource manager;
C62: current load network resource manager is received two-way resource change request, the demand information of bandwidth resources is changed the bandwidth of reserving on the two-way routed path according to called UE, if the purpose load network resource manager that this current load network resource manager is two-way resource request, then upwards a jumping load network resource manager is returned two-way resource change response, execution in step c63; Otherwise jump load network resource manager to next and send two-way resource change request, return step c62;
C63: current load network resource manager is received two-way resource change response, if the source load network resource manager that this current load network resource manager is described reverse resource request, then set up whole two-way routed path according to the routed path information in this two-way resource change response, issue routed path information to ingress router, and return two-way resource change response to called CA; Otherwise upwards a jumping load network resource manager is returned two-way resource change response, returns step c63.
11, method as claimed in claim 5 is characterized in that, and is after described step c, further comprising the steps of:
D: called CA to caller CA return to the request Temporary Response;
E: caller CA to calling UE return to the request Temporary Response;
F: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
G: called CA is to the affirmation of called UE transmission to the Temporary Response of request;
H: called UE is to the once more Temporary Response of called CA transmission to request;
I: called CA to caller CA return to the request Temporary Response once more;
J: caller CA to calling UE return to the request Temporary Response once more.
12, the method for claim 1 is characterized in that, step c specifically may further comprise the steps:
C1: called CA sends call request to called UE;
C2: called UE is to the Temporary Response of called CA transmission to request;
C3: after called CA receives Temporary Response to request, return Temporary Response to caller CA, and send reverse connection resource request, finish reverse resource request process to the source of reverse resource request load network resource manager to request; Caller CA returns Temporary Response to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process, end step c;
Perhaps, called CA receive to the request Temporary Response after, called CA to caller CA return to the request Temporary Response; Caller CA returns Temporary Response to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA receives that called CA directly sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process to behind the Temporary Response of asking, caller CA to calling UE return to the request Temporary Response, end step c.
13, method as claimed in claim 12 is characterized in that, further may further comprise the steps after step c:
D: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
E: called CA is to the affirmation of called UE transmission to the Temporary Response of request;
F: called UE is to the once more Temporary Response of called CA transmission to request;
G: called CA to caller CA return to the request Temporary Response once more;
H: caller CA to calling UE return to the request Temporary Response once more.
14, the method for claim 1 is characterized in that, step c specifically may further comprise the steps:
C1: called CA returns Temporary Response to request to caller CA, and sends reverse connection resource request to the source of reverse resource request load network resource manager, finishes reverse resource request process; Caller CA returns Temporary Response to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process, end step c;
Perhaps, called CA to caller CA return to the request Temporary Response; Caller CA returns Temporary Response to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA returns Temporary Response to request to caller CA, and sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process, caller CA to calling UE return to the request Temporary Response, end step c.
15, method as claimed in claim 14 is characterized in that, further may further comprise the steps after step c:
D: caller CA is to the affirmation of called CA transmission to the Temporary Response of request;
E: called CA sends call request to called UE;
F: called UE is to the once more Temporary Response of called CA transmission to request;
G: called CA to caller CA return to the request Temporary Response once more;
H: caller CA to calling UE return to the request Temporary Response once more.
16, the method for claim 1 is characterized in that, the call request among the step b is the endpoint location call request, and step c specifically may further comprise the steps:
C1: called CA sends call request to called UE;
C2: called UE is to the affirmation of called CA transmission to request;
C3: called CA returns affirmation to the endpoint location call request to caller CA, and sends reverse connection resource request to the source of reverse resource request load network resource manager, finishes reverse resource request process; Caller CA returns affirmation to request to calling UE, and sends the request of forward connection resource to the source of forward resource request load network resource manager, finishes forward resource request process; End step c;
Perhaps, called CA returns affirmation to the endpoint location call request to caller CA; Caller CA returns affirmation to request to calling UE, and sends two-way connection resource request to the source of forward resource request load network resource manager, finishes two-way resource request process, end step c;
Perhaps, called CA returns affirmation to the endpoint location call request to caller CA, and sends two-way connection resource request to the source of reverse resource request load network resource manager, finishes two-way resource request process, caller CA to calling UE return to the request affirmation, end step c.
As claim 12,14 or 16 described methods, it is characterized in that 17, described forward resource request process specifically may further comprise the steps:
A1: after the source load network resource manager of forward resource request is received the request of forward connection resource, select the forward routed path, and on this forward routed path bandwidth reserved, jump load network resource manager to next subsequently and send the forward resource request;
A2: after current load network resource manager is received the forward resource request, select the forward routed path, and on this forward routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is the forward resource request, then upwards a jumping load network resource manager is returned forward resource response, execution in step A3; Otherwise, jump load network resource manager to next and send the forward resource request, return steps A 2;
A3: current load network resource manager is received the forward resource response, if the source load network resource manager that this current load network resource manager is the forward resource request, then set up whole forward routed path according to the routed path information in the forward resource response, issue the forward routed path to ingress router, finish the forward resource request, and return the response of forward connection resource to caller CA; Otherwise upwards a jumping load network resource manager is returned the forward resource response, returns steps A 3.
As claim 5,12,14 or 16 described methods, it is characterized in that 18, described reverse resource request process specifically may further comprise the steps:
B1: the source load network resource manager of reverse resource request is selected reverse routed path after receiving reverse connection resource request, and on this reverse routed path bandwidth reserved, jump load network resource manager to next subsequently and send reverse resource request;
B2: after current load network resource manager is received reverse resource request, select reverse routed path, and on this reverse routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is reverse resource request, then upwards a jumping load network resource manager is returned reverse resource response, execution in step B3; Otherwise, jump load network resource manager to next and send reverse resource request, return step B2;
B3: current load network resource manager is received reverse resource response, if the source load network resource manager that this current load network resource manager is reverse resource request, then set up whole reverse routed path according to the routed path information in the reverse resource response, issue reverse routed path to ingress router, finish reverse resource request, and return reverse connection resource response to called CA; Otherwise upwards a jumping load network resource manager is returned reverse resource response, returns step B3.
As claim 5,12,14 or 16 described methods, it is characterized in that 19, described two-way resource request process specifically may further comprise the steps:
C1: the load network resource manager that receives two-way connection resource request is selected two-way routed path, and on this two-way routed path bandwidth reserved, jump load network resource manager to next subsequently and send two-way resource request;
C2: after current load network resource manager is received two-way resource request, select two-way routed path, and on this two-way routed path bandwidth reserved, if the purpose load network resource manager that this current load network resource manager is two-way resource request, then upwards a jumping load network resource manager is returned two-way resource response, execution in step C3; Otherwise, jump load network resource manager to next and send two-way resource request, return step C2;
C3: current load network resource manager is received two-way resource response, if this current load network resource manager is the load network resource manager that receives two-way connection resource request, then set up whole two-way routed path according to the routed path information in the two-way resource response, issue two-way routed path to ingress router, finish two-way resource request, and return two-way connection resource response to called CA; Otherwise upwards a jumping load network resource manager is returned two-way resource response, returns step C3.
20, as claim 11,12,13 or 15 described methods, it is characterized in that,, then after described called UE is sent the last Temporary Response of asking, further may further comprise the steps if called UE is made affirmation to request:
K: called CA to caller CA return to the request affirmation;
L: caller CA returns the above-mentioned affirmation to request to calling UE;
M: calling UE is returned response to above-mentioned affirmation to caller CA;
N: caller CA sends to called CA with the response of above-mentioned affirmation;
O: called CA sends to called UE with the response of above-mentioned affirmation.
21, method as claimed in claim 16 is characterized in that, if what use between UE and UA and the UA is the H323 agreement, then after step c, finishes processing to this calling by the H323 agreement.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101003865A CN100450049C (en) | 2003-10-14 | 2003-10-14 | A method for implementing resource distribution |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2003101003865A CN100450049C (en) | 2003-10-14 | 2003-10-14 | A method for implementing resource distribution |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1607779A CN1607779A (en) | 2005-04-20 |
| CN100450049C true CN100450049C (en) | 2009-01-07 |
Family
ID=34755940
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2003101003865A Expired - Fee Related CN100450049C (en) | 2003-10-14 | 2003-10-14 | A method for implementing resource distribution |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100450049C (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101330396B (en) * | 2007-06-18 | 2012-10-03 | 华为技术有限公司 | Method for establishing multicast route and entity equipment |
| CN101309224B (en) * | 2008-06-30 | 2011-07-20 | 中兴通讯股份有限公司 | Resource admission control system and method for network of multiple protocol label switching structure |
| US20170024680A1 (en) * | 2015-07-21 | 2017-01-26 | Oracle International Corporation | Multi-dimensional approach to agent assignment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1269091A (en) * | 1997-07-01 | 2000-10-04 | 奥普斯威芙网络股份有限公司 | Methods for resource control in a non-unitary service system |
| CN1391749A (en) * | 1999-11-18 | 2003-01-15 | 艾利森电话股份有限公司 | Selection of packet switch router routing method and bearer type within system intranet |
| US20030076816A1 (en) * | 2001-04-26 | 2003-04-24 | At Comm Corporation | Automatic route selection |
| US6614765B1 (en) * | 1997-10-07 | 2003-09-02 | At&T Corp. | Methods and systems for dynamically managing the routing of information over an integrated global communication network |
-
2003
- 2003-10-14 CN CNB2003101003865A patent/CN100450049C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1269091A (en) * | 1997-07-01 | 2000-10-04 | 奥普斯威芙网络股份有限公司 | Methods for resource control in a non-unitary service system |
| US6614765B1 (en) * | 1997-10-07 | 2003-09-02 | At&T Corp. | Methods and systems for dynamically managing the routing of information over an integrated global communication network |
| CN1391749A (en) * | 1999-11-18 | 2003-01-15 | 艾利森电话股份有限公司 | Selection of packet switch router routing method and bearer type within system intranet |
| US20030076816A1 (en) * | 2001-04-26 | 2003-04-24 | At Comm Corporation | Automatic route selection |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1607779A (en) | 2005-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6944166B1 (en) | Method for controlling service levels over packet based networks | |
| CN101151858B (en) | System and method for providing bandwidth reservations in a resource reservation setup protocol, RSVP, environment | |
| US7656866B2 (en) | Controlling media server resources in a VoIP network | |
| US7606885B2 (en) | Method for, and a topology aware resource manager in an IP-telephony system | |
| US6760312B1 (en) | Quality of service on demand | |
| CN100505639C (en) | Method of implementing resource application for multi-service streams | |
| US7899865B2 (en) | Managing media server resources in a VoIP network | |
| US9350784B2 (en) | Method and communication system for selecting a transmission mode for transmitting payload data | |
| US20070239899A1 (en) | Middleware server for interfacing communications, multimedia, and management systems | |
| CN101116296A (en) | Voip network infrastructure components and method | |
| US20060165224A1 (en) | Apparatus and method for managing network resources | |
| JP4823306B2 (en) | Management of media server resources in VoIP networks | |
| US20100064182A1 (en) | Communication system | |
| CN100426805C (en) | Edge or packet gateway control system in next generation network and its method | |
| CN100488179C (en) | Method for insuring telecommunication service quality in soft-exchanging network | |
| CN100450049C (en) | A method for implementing resource distribution | |
| WO2014180289A1 (en) | Session initiation protocol based session method, terminal, and server | |
| CN1756186B (en) | Resource management realizing method | |
| CN106550159B (en) | VoIP communication system | |
| AU776055B2 (en) | Method for providing IP telephony with QoS using end-to-end RSVP signaling | |
| CN100442703C (en) | Method for transmitting service flow in supporting network | |
| CN100355249C (en) | A method for accomplishing resource request for bothway service in bearing network | |
| CN100391154C (en) | Selecting method of path in resource supervisor | |
| CN100370736C (en) | Method for managing resources based on planes | |
| US7653048B2 (en) | Method and apparatus for providing optimal VoIP call routing in VRF environment |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090107 |