CN100450030C - A mapping method for implementing call service levels to connections that bear calls - Google Patents
A mapping method for implementing call service levels to connections that bear callsDownload PDFInfo
- Publication number
- CN100450030C CN100450030CCNB2006100758132ACN200610075813ACN100450030CCN 100450030 CCN100450030 CCN 100450030CCN B2006100758132 ACNB2006100758132 ACN B2006100758132ACN 200610075813 ACN200610075813 ACN 200610075813ACN 100450030 CCN100450030 CCN 100450030C
- Authority
- CN
- China
- Prior art keywords
- call
- connection
- ncc
- calling
- cos
- 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
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Translated fromChinese
Description
Technical field
The present invention relates to networking technology area, particularly a kind of mapping method of realizing the connection of calling service grade to carrying calling.
Background technology
Along with developing rapidly of data service and private line service; demand to the network bandwidth improves constantly; dynamic assignment to the network bandwidth requires also more and more urgent; need network that the ability of dynamically opening can be provided; support the structure of mesh network, have flexibly extended capability simultaneously and protect restore funcitons fast.And the service dispatching of conventional optical network adopts the mode of webmaster static configuration; do not support the mode dynamically opened; and adopt linearity or annular networking mostly; protection recovers to adopt static restoration methods such as multiplex section protection, SNCP (Sub-Network Connection Protection SNCP), path protection (PP) ring, can not satisfy the needs of above-mentioned business.
For satisfying the needs of practical business, (the InternationalTelecommunication Unite-T sector of itu standard portion, ITU-T), the Internet task group (InternetEngineering Task Force, IETF) and (the Optical InternetworkingForum of optical internet forum, OIF) common development ASON (Automatically switched opticalnetwork, ASON) technology can address the above problem well.It uses general multiple protocols label exchange (Generalized Multi-Protocol Label Switching at control plane, GMPLS), two kinds of new connection types are provided: the permanent connection (Switched connections:, SC) with soft permanent the connection (Soft permanent connections, SPC).
ITU-T normative document that framework and demand to ASON define G.8080 in, proposed to call out and is connected the notion of separation.In the definition of this normative document, calling is a kind of service that network offers the user, directly presents to the user, supports the contact between the service entities end points, and (Call Name) identifies by call name; The grade of service (the Class of Service that calls out, COS) quality of expression call business, specifically defined by operator: for example, the diamond level is called out COS and is represented that the reliability of call business is 99.999%, and the gold level is called out a COS and represented that the reliability of call business is 99.99% etc.Connection is a kind of transmission entity, it by a pair of that be associated, can be between its corresponding input and output, transmit the unidirectional of information in opposite directions, simultaneously and connect to form, (Tunnel ID) identifies by connection identifier, is the specific implementation of the end-to-end contact of network service entity.Connect COS and represent the protection type that connects, the connection of supporting usually protection type comprises: privacy protection, as 1+1 or 1:1 mode; Share protect is as 1:N or M:N mode; Unprotect, as have only work to connect, business will be interrupted when work connects fault; Generally also support various recoveries in addition, for example dynamic heavy-route etc.Zero, one or more connections can be arranged under the calling; Calling can be used and connect identical signaling, also can use independently call signaling; That the operation that calling is carried out comprises is newly-built, deletion, recovery and modification etc.Local call COS and the corresponding relation that is connected COS, for example, the diamond level is called out the corresponding 1+1 of COS and is connected, and is called and calls out COS to the mapping that connects COS.
Though provided call setup in G.8080, called out the flow process that discharges at ITU-T, do not provided and to call out the end-to-end connection realization flow that COS is mapped as this calling of carrying.Only the someone provides the scheme that call bandwidth is revised at present, for example has the people to provide a kind of support scheme of calling among the OIF.This scheme adopts the framework of ITU-T definition, calls out with being connected with identical signaling and realizes, increases the call identification object and carry call information in the signaling message that connects.
There is following problem in this scheme: still not support call COS is to the mapping of the end-to-end connection of this calling of carrying; Call out with being connected and adopt same signaling to realize, be difficult for realizing calling out and being connected function independent of each other, be difficult to realize different internodal call requests; The modification of not support call COS.
Summary of the invention
In view of this, the objective of the invention is to, propose a kind of mapping method of COS of realizing calling out, can realize the mapping of call service to the connection of bearing call to the connection of bearing call.This method comprises the steps:
A, caller controller send to Calling Side calling network controller NCC and comprise the call request of calling out COS, Calling Side NCC obtains the corresponding call consultation parameter according to the calling COS in the receiving call request, and gained call negotiation parameter is sent to callee side NCC;
B, callee side NCC hold consultation to the call negotiation parameter from Calling Side NCC, and the call negotiation parameter that will obtain after will consulting returns to Calling Side NCC;
C, Calling Side NCC trigger corresponding attended operation according to the call negotiation parameter that callee side NCC returns;
D, Calling Side NCC return the calling acknowledge message to the caller controller.
Steps A is described receives that call request can further include afterwards:
Calling Side NCC obtains calling subscriber's subscription data to data server, judges whether to allow this call request according to the subscription data that is obtained, if do not allow then return refuse information and withdraw from this flow process to the caller controller; If allow, then continue to carry out subsequent step.
If the call negotiation parameter that obtains after the described negotiation of step B is returned miscue and process ends for empty to Calling Side NCC.
Steps A is described to be obtained the corresponding call consultation parameter according to the calling COS in the call request of being received and is:
According to the calling COS in the receiving call request, search this locality calling COS that sets in advance and the mapping relations table that is connected COS, obtain corresponding attended operation and be connected parameter information, and according to the gained attended operation be connected parameter information and determine the call negotiation parameter.
Further comprise call policy information in the described call request, then describedly obtain corresponding attended operation and be connected parameter information and be: according to the call policy information in the call request, search local policy data, and use the local policy data of being searched, screening is searched attended operation that this locality the calling COS that sets in advance and the mapping relations table that is connected COS obtain and is connected parameter information, through the attended operation of screening be connected parameter information as the attended operation of correspondence be connected parameter information.
Described according to the gained attended operation be connected parameter information and determine that the call negotiation parameter is: according to the gained attended operation be connected parameter information and determine that corresponding being operating as increases a connection in calling, then the call negotiation parameter of Que Dinging comprises that calling out being connected that COS and calling COS can shine upon protects type;
The described callee side NCC of step B to hold consultation from the call negotiation parameter of Calling Side NCC for: search local mapping relations table according to the calling COS in the call negotiation parameter and obtain corresponding connection protection type, get common factor with the protection type that is connected in the call negotiation parameter, judge whether occur simultaneously is zero, if it is non-vanishing, occuring simultaneously is the connection protection type of this calling of carrying after the negotiation, and the connection that will carry this calling protects type as the call negotiation parameter; If occur simultaneously is that call negotiation parameter zero then after the negotiation is sky.
Described definite call negotiation parameter further comprises the connection bandwidth,
Then the described judgement of step B is occured simultaneously and is further comprised after non-vanishing: judge whether the connection bandwidth in the call negotiation parameter can be accepted, if then the connection bandwidth of being accepted is added the call negotiation parameter after consulting and continue the execution subsequent step; Otherwise the call negotiation parameter after consulting is empty, returns miscue and withdraws from this flow process to Calling Side NCC.
Described definite call negotiation parameter further comprises the subnet point SNP that Calling Side connects, then the described judgement of step B is occured simultaneously and further comprised after non-vanishing: callee side NCC judges whether the subnet point SNP of Calling Side NCC connection can be used as the source SNP of new connection, if, the SNP that callee side is about to use adds the call negotiation parameter after consulting and continues to carry out subsequent step, otherwise the call negotiation parameter after consulting is empty, returns miscue and withdraws from this flow process to Calling Side NCC.
Described according to the gained attended operation be connected parameter information and determine that the call negotiation parameter is: according to the gained attended operation be connected parameter information and determine that the corresponding deleting bearing that is operating as set up a connection in the calling, then the call negotiation parameter of Que Dinging comprises the connection identifier Tunnel ID of a connection of carrying described calling;
The described callee side NCC of step B to hold consultation from the call negotiation parameter of Calling Side NCC into: check the Tunnel ID in the call negotiation parameter, judge whether this locality allows to delete this connection, as if allowing then to keep the call negotiation parameter constant; Otherwise the call negotiation parameter that obtains after consulting is for empty.
According to the gained attended operation be connected parameter information and determine that the call negotiation parameter is: according to the gained attended operation be connected parameter information and determine that corresponding being operating as revise the protection attribute that a connection of calling has been set up in carrying, then the call negotiation parameter of Que Dinging comprises the connection identifier Tunnel ID of a connection of carrying described calling and the parameter of this connection needs modification;
The described callee side NCC of step B to hold consultation from the call negotiation parameter of Calling Side NCC into: check the Tunnel ID in the call negotiation parameter, judge whether this locality allows the requirement of revising this connection and satisfying new connection parameter, if then keep the call negotiation parameter constant; Otherwise the call negotiation parameter that obtains after consulting is for empty.
The call negotiation parameter that step B is described to be obtained after will consulting returns to Calling Side NCC and is:
B1, callee side NCC send and call out Indication message to called controller;
B2, called controller to receive that calling out Indication message authenticates, if authentication is passed through, then returns the calling acknowledge message by callee side NCC to Calling Side NCC; Otherwise return refuse information and withdraw from this flow process to Calling Side NCC by callee side NCC.
Described calling COS carries by the resource reservation protocol flow engineering RSVP-TE signaling of expansion or based on the notification message in the routing tag distributorship agreement CR-LDP signaling of restriction.
The SNP ID object that SNP in the described call negotiation parameter carries for the notification message in expansion RSVP-TE signaling or the CR-LDP signaling.
The connection protection type object that connection protection type in the described call negotiation parameter is carried for the notification message in expansion RSVP-TE signaling or the CR-LDP signaling.
As can be seen from the above technical solutions, by to GMPLS (GeneralMultiple Protocol Label Switching, GMPLS) call signaling is expanded, the call controller at sourcesink two ends to attended operation that can the bearing call service be connected parameter and hold consultation, final obtain the attended operation adopted and be connected parameter, finish the operation such as establishment, deletion, modification of corresponding connection, realize calling out the mapping of COS to the connection of bearing call, and realized call signaling and be connected separating of signaling, supported calling out the modification of COS.
Description of drawings
Fig. 1 handles schematic diagram for network control aspect of the present invention realizes calling out COS to connecting the COS mapping;
Fig. 2 is the form of COS object in the expansion call signaling of the present invention's definition;
Fig. 3 is the form of SNP object in the expansion call signaling of the present invention's definition;
Fig. 4 realizes calling out COS to the process chart that connects the COS mapping for the present invention;
Fig. 5 is the network annexation schematic diagram of the embodiment of the invention;
Fig. 6 realizes setting up the process chart that 1+1 connects for the embodiment of the invention one;
Fig. 7 is that the embodiment of the invention two realizes calling out the process chart that COS revises.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is further elaborated below in conjunction with accompanying drawing.
Fig. 1 handles schematic diagram for network control aspect of the present invention realizes calling out COS to the connection mapping of this calling of carrying, comprise caller controller (Calling Party Controller) 101, called controller (CalledParty Controller) 104, calling network controller (Network Call Controller, NCC) 102 and 103, and a plurality of connection controller (Connection Controller) 105～107.In the practical application, may relate to one or more connection controller.
For realizing calling out COS to the mapping that connects, need be to GMPLS (GeneralMultiple Protocol Label Switching, GMPLS) call signaling is expanded, can to wherein resource reservation protocol flow engineering (Resource Reservation Protocol-TrafficExtension, RSVP-TE) signaling is done following expansion:
Expand 1, in RSVP-TE, increase and call out the COS object, in calling out (Notify) signaling, carry this COS object.Concrete form is shown in Figure 2, and this object comprises length, class field (Class-Num) and type (C-Type), and the byte length that the expression various piece takies in its bracket is respectively 2 bytes, 1 byte and 1 byte.The length of COS value is defined as 4 bytes, and pairing concrete implication is defined by operator, for example:
The COS value is that 1 expression service reliability is 99.999%, and promptly the diamond level is called out COS;
The COS value is that 2 expression service reliabilitys are 99.99%, and promptly the gold level is called out COS;
The COS value is that 3 expression service reliabilitys are 99.9%, and promptly the silver level is called out COS;
The COS value is that 4 expression service reliabilitys are 90%, and promptly the copper level is called out COS;
The COS value is 5 for user-defined other types;
......
Below only be an example of COS object, in the practical application, the value of COS can define as required, and the length of COS object also can be not limited to foregoing description.
By expanding 1, call signaling can carry the particular content of calling out COS.For example according to the definition of front COS value; the value of COS object is 1 in the setup requests thatcaller controller 101 sends; then this call request is the service of setting up a diamond level; if this calling has existed and COS is the gold level; expression need upgrade to the diamond level by the gold level with COS; correspondingly, the operation that need carry out is the connection protection type that the connection protection type of gold level calling COS correspondence is upgraded to diamond level calling COS correspondence.
Increase subnet point (SNP) object among expansion 2, the RSVP-TE, in call signaling Notify message, carry can bearing call connection SNP ID, concrete form is as shown in Figure 3, and is similar with expansion 1, also comprise length, class field and type, that just carry here is SNP ID.Wherein, SNP represents reality or potential tie point (CP) or connection end points (CTP), perhaps represents reality or potential Termintion connection point (TCP) or Trail termination point (TTP).SNP is determined by node identification+interface identifier+SNP ID, because node identification, interface identifier existing relevant object in RSVP-TE is represented, therefore only increases a SNP object here.Difference relation between a SNP and other SNP then forms link connection (LC) and is connected (SNC) with subnet.SNP can also and other SNP combine, form sub-network point pool (SNPP), between the SNPP on the different sub-network, be connected to form a SNPP link.At last, be connected with the whole network of SNC series connection formation leap by a series of LC, the final realization connects end to end.Can say so, connecting end to end is exactly the combination of one group of SNP according to certain relation.
The expansion 3, in call signaling Notify message; carry and call out connection protection type (protection) object that COS can shine upon; calling out COS for one can corresponding more than one protection type object, the concrete definition of protection type object can referring in the ietf standard document (draft-ietf-ccamp-gmpls-recovery-e2e-signaling-03.txt) about connecting the content of protection type object (Protection Object).
The protection type has provided and has connected the protection reset mode that is adopted.
Notify message format after the expansion is as follows:
<Notify?message>::＝<Common?Header>[<INTEGRITY>]
[[<MESSAGE_ID_ACK>|<MESSAGE_ID_NACK>]...]
[<MESSAGE_ID>]
<ERROR_SPEC>
<notify?session?list>
<notify?session?list>::＝[<notify?session?list>]<notify?session>
<notify?session>::＝<SESSION>[<ADMIN_STATUS>]
[<POLICY_DATA>...]
[ <COS> ] (1)
[ <SNP?ID> ] (2)
[ <Protection>] (3)
[<LINK_CAPABILITY>]
[<SESSION_ATTRIBUTE>]
[<sender?descriptor>|<flow?descriptor>]
Wherein, the part that is above-mentioned expansion that marks of symbol (1), (2), (3).
Above-mentioned expansion can also realize that in based on the routing tag distributorship agreement (CR-LDP) of restriction the mode of implementation and RSVP-TE does not have essential distinction, so repeat no more.
Except call signaling is done the expansion; in each NCC, all to set in advance and call out COS and the mapping relations table that is connected COS; be designated hereinafter simply as the mapping relations table,, can obtain one or more possible connection protection types according to known calling COS by searching this table.For example; if in the described mapping relations table, call out COS and call out corresponding 1+1 connection with the diamond level that corresponds to that connects COS, then the calling COS that comprises in the call signaling that NCC receives calls out for the diamond level; by searching this mapping relations table, just can obtain corresponding connection protection type is the 1+1 mode.In addition; can also carry call policy information in the call signaling; and the subscriber policy database is set in NCC; obtain corresponding policy data according to the call policy information inquiry subscriber policy database in the call signaling; according to policy data the above-mentioned protection type that is connected that obtains is further screened with service at different users, obtain meeting the connection protection type of policy data.Described policy data is the information relevant with service is provided to the user, and for example, user A is VIP user, and the call service of all types can be provided, and enjoys 10% term discount; User B is the defaulting subscriber, and the call service of part type can only be provided, and binding hours or the like.If described calling then according to the policy data of user B, can not provide the connection of 1+1 protection type for user B initiates.
Fig. 4 is the flow chart that key-course network configuration realization calling COS as shown in Figure 1 shines upon to the connection of this calling of carrying, comprises the steps:
Step 401: network management system or client device have callee's call controller address, current call identification, calling COS object and call policy information by the NCC102 ofcaller controller 101 request of making a call to Calling Side in this request;
Step 402:NCC102 carries out call authorization to the call signaling of being received, if the authentication not by refuse this call request; Otherwise according to the calling COS that carries in the call signaling and local mapping relations table of call policy information searching and corresponding subscriber policy data, obtain attended operation that this calling COS can shine upon and be connected parameter, and according to the gained attended operation be connected parameter and determine the call negotiation parameter, determined call negotiation parameter is joined in the call request, and call request is sent to the NCC103 of callee side; Described call authorization promptly judges whether to allow this user to carry out the calling of being submitted in the call signaling according to calling subscriber's CAMEL-Subscription-Information, CAMEL-Subscription-Information is kept in the data server, when NCC102 receives call request, then obtain this CAMEL-Subscription-Information to data server; For example: if the call request that the calling subscriber submits to is for upgrading to the diamond level with current calling COS by the gold level, the not signatory diamond level of golden level if the calling subscriber has only contracted, NCC does not pass through for authentication according to obtaining calling subscriber's CAMEL-Subscription-Information judged result.
Step 403:NCC103 holds consultation to the call negotiation parameter in the call request, and negotiation method is:
1) connects for increasing if call out map operation, the call negotiation parameter comprises calls out COS, the subnet point SNP that Calling Side connects, bandwidth with call out that COS can shine upon be connected the protection type, NCC103 searches local mapping relations table according to the calling COS in the call negotiation parameter and obtains corresponding connection protection type, get common factor with the protection type that is connected in the call negotiation parameter, judge whether occur simultaneously is zero, if it is non-vanishing, occuring simultaneously is the connection protection type of this calling of carrying after the negotiation, and the connection protection type and the callee side that will carry this calling are about to the SNP of use as the call negotiation parameter; If occur simultaneously is that call negotiation parameter zero then after the negotiation is sky, non-vanishing NCC103 judges whether the subnet point SNP that Calling Side NCC connects can be used as the source SNP of new connection, whether new bandwidth requirement allows if occur simultaneously, if then continue to carry out subsequent step, otherwise the call negotiation parameter after consulting is empty, returns miscue and withdraws from this flow process to Calling Side NCC.
2) comprise the connection identifier Tunnel ID that will delete connection if call out map operation for deleting the call negotiation parameter that connects then determine, NCC103 checks the Tunnel ID in the call negotiation parameter, judge whether this locality allows to delete this connection, if allow then to keep the call negotiation parameter constant; Otherwise the call negotiation parameter that obtains after consulting is for empty.
3) if call out map operation for revising certain connection, then the call negotiation parameter of Que Dinging comprises the connection identifier Tunnel ID of a connection of carrying described calling and the parameter that this connection needs are revised, NCC103 checks the Tunnel ID and the new parameter that is connected in the call negotiation parameter, judge whether this locality allows the requirement of revising this connection and satisfying new connection parameter, if then keep the call negotiation parameter constant; Otherwise the call negotiation parameter that obtains after consulting is for empty.
If the calling parameter that obtains after consulting not for empty, send the calling Indication message to calledcontroller 104, otherwise refuses this calling, return miscue and process ends to NCC102; Described calling Indication message carries the relevant information of this calling, can include but not limited to the call service type, promoter's information etc.
Step 404: the calling indication that 104 pairs of called controllers are received authenticates, and described authentication if authentication is passed through, is then returned the affirmation message of call accepted for judging whether to accept this call request tocallee side NCC 103; If authentication is not passed through, then return refuse information and withdraw from this flow process to NCC103.
Call negotiation parameter after step 405:NCC103 will consult is sent to CallingSide NCC 102, NCC102 is according to receiving call negotiation parameter, finally determine corresponding attended operation and be connected parameter, difference according to the call negotiation parameter, corresponding attended operation may be to set up new the connection, deletion is existing to be connected, and revises to connect bandwidth or revise to connect the protection type;
Step 406:NCC102 triggers and connects the 405 determined attended operations ofcontroller 105 to 107 execution in step.
Step 407: afterconnection controller 105 to 107 is finished associative operation, the NCC102 of notice Calling Side, NCC102 returns acknowledge message to the caller controller, and the terminated call request processing flow.
Fig. 5 calls out COS to the network connection diagram that connects the COS mapping for realizing.Wherein, A is the caller node, and Z is called node, and B and D are respectively the Ingress node and the Egress node of network, and C, E, F and G are the network intermediate node.Connect situation according to network shown in Figure 5, below according to the concrete condition of the attended operation corresponding with calling out COS, lift two specific embodiments again and describe in detail and call out the idiographic flow of COS to the mapping of the connection of this calling of carrying.
Embodiment one: caller node A is to the called node Z request of making a call, and the attended operation of this calling COS correspondence is a newly-built connection.In the present embodiment flow process, the function of each node on the control aspect of Fig. 5 is: node A is the caller controller, node Z is called controller, Node B has Calling Side network controller and the function that is connected controller concurrently, node D then has callee side network controller and the function that is connected controller concurrently, node C, node E are intermediate node, have neither part nor lot in call treatment, only participate in the connection processing process as connecting controller.
The idiographic flow of present embodiment comprises the steps: as shown in Figure 6
Step 601: node A sends Notify message as call request to Node B, except the calling parameter of the standard of carrying, also carries newly-increased COS object in the Notify message, supposes that the COS object numerical value that carries is 1;
Calling COS and mapping relations table that connects COS and relevant subscriber policy data that step 602:B node sets in advance according to this locality, obtain attended operation that this calling COS can shine upon and be connected parameter, suppose that the attended operation that can shine upon is newly-built connection, the new protection type that connects is 1+1 or 1:1, and corresponding call negotiation parameter is new source SNP, bandwidth, the protection type that connects;
Step 603:B node sends Notify message to node D, wherein has and calls out COS object and the determined call negotiation parameter ofstep 602, and concrete data format is:
<notify?session>::＝<SESSION>[<ADMIN_STATUS>]
[<POLICY_DATA>...]
[ <COS：1> ] (4)
[ <Protection：1+1> ] (5)
[ <Protection：1:1>?] (6)
[ SNP?ID ] (7)
[<LINK_CAPABILITY>]
[<SESSION_ATTRIBUTE>]
[<sender?descriptor>|<flow?descriptor>] (8)
Wherein object (4) is for calling out the COS object, and object (5) is being connected of can shining upon to protect type with object (6), and object (7) is source end SNP ID, promptly newly is connected the employed SNPID of Node B, the bandwidth of object (8) for connecting;
Step 604: after node D receives Notify message, call negotiation parameter in the Notify message is held consultation, detailed process is: according to the calling COS in the Notify message, search local call COS and mapping relations table that is connected COS and corresponding subscriber policy data, find this locality corresponding connection to protect type, be assumed to be 1+1; Node D gets common factor with the connection protection type that this locality can be corresponding with the protection type that is connected in the Notify message of receiving, because node D can only be mapped as 1+1 to this calling, can not get 1:1, therefore getting occurs simultaneously is 1+1, be about to the connection protection type of 1+1, protect the pairing object of type (6) from Notify message, to delete 1:1 as this calling of carrying; Judge the SNP ID in the Notify message and connect bandwidth whether can accept, hypothesis can be accepted herein, in Notify message, increase node D operable SNP ID object and connect bandwidth.
Step 605: node D sends Notify message as calling out indication to node Z;
Step 606: node Z authenticates the call negotiation parameter in the Notify message of being received, establishes authentication here and passes through, and sends Notify message as acknowledge message by the back to node D.
Step 607: after node D receives acknowledge message; send Notify message to Node B; wherein have the connection protection type and the spendable SNP ID of node D that get behind the common factor; in this example; described connection protection type is 1+1; the spendable SNP ID of node D is the SNP201 among the Port101, and the SNP ID that uses on the Node B is the SNP200 among the Port100, and wherein Port101 and Port100 are port-mark.
Step 608: Node B connects according to the call negotiation parameter in this Notify message after receiving Notify message from node D, is specially: the protection type after obtaining to consult is 1+1, as the connection COS of this calling of carrying; According to SNP and self the spendable SNP that node D returns, obtain the corresponding connection of this calling, and the connection controller of triggering interdependent node is set up the connection of satisfying bandwidth requirement.In this example, be connected to the connection that the SNP200 among the Port100 goes up the 1+1 protection type of the SNP201 among the Port101 to node D on the Node B, the specifying information of 2 connections that comprise is:
Through the connection of node C, be the work connection from Node B to node D;
Through the connection of node E, be the protection connection from Node B to node D; More than two be connected among Fig. 5 black line and represent with overstriking.
Step 609: after connecting foundation, connect controller and return acknowledge message to the caller controller, notice caller controller connects to be finished, and process ends.
In the above-mentioned negotiations process to the call negotiation parameter, to the steps necessary that judges between right and wrong of SNP ID, bandwidth, also can save in the consultation parameter to SNP ID, bandwidth carry and negotiations process in to the judgement of SNPID, bandwidth.
Embodiment two: the modification of calling out COS between caller node A and the called node Z.
The idiographic flow of present embodiment comprises the steps: as shown in Figure 7
Step 701: node A sends Notify message as call request to Node B, except the calling parameter of the standard of carrying, also carries newly-increased COS object in the Notify message;
Step 702: Node B finds that new calling parameter is different with the local calling parameter of preserving, think the call modification operation, according to local mapping relations table and subscriber policy data, calling COS value in the call request is mapped to concrete attended operation and is connected parameter, and according to described attended operation be connected parameter, generate the call negotiation parameter:
If increase new connection in calling out, then select the new source SNP that connects, bandwidth, protection type etc. as the call negotiation parameter by the call controller of Node B;
If in calling out deletion certain connect, then select a connection corresponding with this calling by the call controller of Node B, with the Tunnel ID of this connection as the call negotiation parameter;
If desired the protection attribute of the connection of carrying this calling is made amendment, then select a connection of this calling of carrying, with the Tunnel ID of selected connection, this connects the parameter that needs to revise as the call negotiation parameter by call controller;
Step 703: Node B sends Notify message to node D, comprises the determined call negotiation parameter ofstep 702 in the described Notify message;
Step 704: node D holds consultation to the call negotiation parameter of being received, according to the difference of call negotiation parameter in the Notify message of being received, detailed process is as follows:
If increase new connection in calling out, then be connected the protection type according to what the calling COS in the Notify message searched that local mapping relations table and local policy data obtain shining upon, get common factor with the protection type that is connected in the Notify message, obtain the connection protection type of this calling of carrying; And will carry the connection protection type of this calling and the new place SNP that is connected as the call negotiation parameter;
If the Tunnel ID that carries in the Notify message is checked in certain connection of deletion in calling out, judge whether this locality allows to delete this connection, if allow to keep the call negotiation parameter constant and continue execution instep 705, otherwise return miscue and withdraw from this flow process;
If desired to making amendment with the protection attribute of corresponding certain connection of this calling, check the Tunnel ID that carries in the Notify message, judge whether this locality allows the requirement of revising this connection and satisfying new connection parameter, if keep the call negotiation parameter constant and continue execution instep 705, otherwise return miscue and withdraw from this flow process;
Step 705: node D sends Notify message as calling out indication to node Z;
Step 706: node Z authenticates the Notify message of being received, sends Notify message as acknowledge message by the back to node D.
Step 707: after node D receives acknowledge message, send Notify message, wherein have the determined call negotiation parameter ofstep 704 to Node B;
Step 708: after Node B is received Notify message from node D, carry out following processing according to wherein calling parameter:
If increase new connection in calling out, then trigger the establishment that the connection controller is finished new connection by call controller, the establishment of connection can adopt GMPLS RSVP-TE (referring to the ietf standard RFC3473) signaling of standard to finish.
If certain connection of deletion in calling out then triggers the deletion that the connection controller is finished connection by call controller, the deletion of connection can adopt GMPLS RSVP-TE (referring to the ietf standard RFC3473) signaling of standard to finish.
If the call modification bandwidth then triggers the bandwidth modification that the connection controller is finished connection by call controller, the signaling that connects the bandwidth modification adopts newly-built signaling process, and detailed process can be with reference to RFC3473;
If desired certain is connected the protection attribute and makes amendment, then carry out following processing:
If only revise the protection attribute that connects, can not cause the additions and deletions of connection, trigger the connection controller by call controller according to the result who negotiates and finish the modification that connects the protection attribute;
If revise the protection attribute that connects; the increase that need connect; for example need certain connection is revised as 1+1 by heavy-route; select corresponding connection by call controller according to the result after consulting; trigger and connect the establishment that controller is finished a new connection; these two are connected with 3 identical tuples; different Tunnel ID; connecting controller finishes at two ends and newly-increasedly connects and originally be connected two sending out and the choosing receipts; call controller triggers and connects the renewal that controller is finished original connection attribute after new connection establishment is finished, simultaneously the incidence relation of these two connections of preservation in the call controller of first and last node.
If revise the protection attribute that connects; the deletion that need connect; for example need certain connection is revised as heavy-route by 1+1; select corresponding connection by call controller according to the result after consulting; trigger the connection controller and finish the deletion of a connection, deleting successfully, the back call controller triggers the renewal that the connection controller is finished connection attribute again.
Step 709: after the connection controller is finished the function of join dependency, return acknowledge message and process ends to call controller.
The above only is preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of being done within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (14)
Translated fromChinesePriority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100758132ACN100450030C (en) | 2006-04-18 | 2006-04-18 | A mapping method for implementing call service levels to connections that bear calls |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100758132ACN100450030C (en) | 2006-04-18 | 2006-04-18 | A mapping method for implementing call service levels to connections that bear calls |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101047551A CN101047551A (en) | 2007-10-03 |
| CN100450030Ctrue CN100450030C (en) | 2009-01-07 |
Family
ID=38771800
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100758132AExpired - Fee RelatedCN100450030C (en) | 2006-04-18 | 2006-04-18 | A mapping method for implementing call service levels to connections that bear calls |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100450030C (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102448017A (en)* | 2010-10-13 | 2012-05-09 | 中兴通讯股份有限公司 | Call confirmation method, system and mobile station |
| CN102638733B (en)* | 2011-02-15 | 2017-03-15 | 中兴通讯股份有限公司 | The method and system of configuration protection group |
| CN102647401B (en)* | 2011-02-22 | 2017-05-31 | 中兴通讯股份有限公司 | A kind of method and system of user node session control |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1427589A (en)* | 2001-12-21 | 2003-07-02 | 阿尔卡塔尔加拿大公司 | Method and system for coordinating service quantity between asynchronous transfer mode (ATM) network and adjacent network |
| CN1514617A (en)* | 2002-12-13 | 2004-07-21 | 三星电子株式会社 | VoIP call control device and method in private small exchange |
| CN1520113A (en)* | 2002-10-29 | 2004-08-11 | ̩�ձ�˹�ɷݹ�˾ | Method and apparatus for scheduling available link bandwidth between packet switched data streams |
| US20050180397A1 (en)* | 2004-02-03 | 2005-08-18 | Eung-Moon Yeom | Call processing system and method in a voice and data integrated switching system |
| CN1708957A (en)* | 2002-10-29 | 2005-12-14 | 思科技术公司 | Multi-layer virtual local area network (VLAN) domain mapping mechanism |
- 2006
- 2006-04-18CNCNB2006100758132Apatent/CN100450030C/ennot_activeExpired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1427589A (en)* | 2001-12-21 | 2003-07-02 | 阿尔卡塔尔加拿大公司 | Method and system for coordinating service quantity between asynchronous transfer mode (ATM) network and adjacent network |
| CN1520113A (en)* | 2002-10-29 | 2004-08-11 | ̩�ձ�˹�ɷݹ�˾ | Method and apparatus for scheduling available link bandwidth between packet switched data streams |
| CN1708957A (en)* | 2002-10-29 | 2005-12-14 | 思科技术公司 | Multi-layer virtual local area network (VLAN) domain mapping mechanism |
| CN1514617A (en)* | 2002-12-13 | 2004-07-21 | 三星电子株式会社 | VoIP call control device and method in private small exchange |
| US20050180397A1 (en)* | 2004-02-03 | 2005-08-18 | Eung-Moon Yeom | Call processing system and method in a voice and data integrated switching system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101047551A (en) | 2007-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7293080B1 (en) | Automatically discovering management information about services in a communication network | |
| US8300625B2 (en) | Call control using a layered call model | |
| EP2012470A1 (en) | A method, apparatus, and system implementing the vpn configuration service | |
| KR20070047293A (en) | Method and apparatus for providing a correlation means in a hybrid telecommunications network | |
| CN1331363C (en) | Rerouting method based on network entrance node | |
| CN100407712C (en) | Gateway system and integrated management method | |
| US8050277B2 (en) | Control method for the cross-domain call and the connection of ASON | |
| US8005964B2 (en) | Communication between call controllers by amending call processing messages | |
| EP2296319B1 (en) | Apparatus and methods for establishing virtual private networks in a broadband network | |
| JP3834035B2 (en) | Processing multimedia calls in packet-based networks | |
| CN100450030C (en) | A mapping method for implementing call service levels to connections that bear calls | |
| US6845250B1 (en) | Method and system for transmitting messages in a communications network | |
| EP1703745B1 (en) | Route serving device, method and system applying the device | |
| Cisco | Configuring the Gateway | |
| CN100550803C (en) | Device and method for managing multi-protocol public route | |
| KR100288755B1 (en) | Private network network interface routing method for considering connections currently being in progress of setup phase | |
| CN100414907C (en) | Resource Management Method Based on Signaling Mechanism in IP Telecom Network System | |
| EP2395773B1 (en) | Method and apparatus of sub-network connection protection (sncp) service migration | |
| KR100511747B1 (en) | Operation Method for Signaling Network Resources in Signaling Gateway System | |
| CN100426813C (en) | Method for transmitting signaling messages in signaling system 7 type network | |
| CN100542174C (en) | Method for communication between softswitch equipment and integrated intelligent home location register | |
| KR100554226B1 (en) | TDM virtual line control method considering scalability in MPLS network |
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 Termination date:20160418 |