CN101141668A

CN101141668A - Release method and system for service bearer

Info

Publication number: CN101141668A
Application number: CNA2006101128563A
Authority: CN
Inventors: 贺文涛; 王震
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2006-09-05
Filing date: 2006-09-05
Publication date: 2008-03-12
Anticipated expiration: 2026-09-05
Also published as: CN101141668B

Abstract

The present invention discloses a service bearing releasing method. The method is that when a radio network controller (RNC) sends a user released indicating message which comprises a releasing reason to a base station (NodeB), the RNC concentratedly releases all the service bearing which is correspond to the current releasing reason in the current side; when the NodeB receives the user released indicating message which comprises a releasing reason which is sent by the RNC, the NodeB concentratedly releases all the service bearing which is corresponding to the current releasing reason in the current side. The present invention has the advantages that the alternation of the access link controlling application protocol entity (ALCAP) on the IuB interface is greatly reduced, the transmission load on the IuB interface is reduced, and the efficiency and the stability of the system are improved. The present invention also discloses a service bearing releasing system of the interface of the IuB.

Description

A kind of method for releasing of service bearer and system

Technical field

The present invention relates to the data transmission technology of the communications field, relate in particular to method for releasing and system that a kind of wireless access network base-station interface (IuB) is gone up service bearer.

Background technology

(NodeB Application Part NBAP) is positioned at the chain of command of the wireless network layer of IuB interface to base station application part, and radio network controller (RNC) is realized management to Radio Resource in the base station by NBAP.Finish control alternately by the NBAP signaling between RNC and base station (NodeB) on the IuB interface to NodeB side Internet resources.The NBAP process is exactly the process of Signalling exchange between RNC and the NodeB on the IuB interface of NBAP agreement regulation, and effect is completeness and the reliability that guarantees Signalling exchange.

The reseting procedure of NBAP, obstruction process and sub-district delete procedure all will carry out the release of service bearer is handled on the IuB interface, and service bearer is meant the corresponding relation of ATM(Asynchronous Transfer Mode) link bearer and user's transmission channel and the corresponding relation of the carrying on asynchronous transfer mode link bearer and the wireless access network base-station interface.The reseting procedure of NBAP usually occurs under the unusual situation of system's generation in service, PVC (Permanent Virtual Circuit such as bearer service on the IuB interface, PVC) break down, RNC initiates reseting procedure to NodeB, discharge the resource of all CUs of base station, comprise discharging bottom ATM Adaptation Layer type 2 (AAL2) link; The sub-district delete procedure of NBAP is initiated by the sub-district deletion message of RNC, is used for deleting the remaining public and private network resource in sub-district; The obstruction process of NBAP usually occurs in RNC and need reshuffle the public resource of NodeB control, such as cell re-configuration put, (Common Traffic Channel, sets up or reshuffles etc. before the process at deletion CTCH) CTCH Common Traffic Channel.

The transport network layer of IuB interface is divided into transmission network layer user surface and transport network layer chain of command, (Access Link Control Application Protocol ALCAP) controls the foundation and the release of the service bearer of user's face to Access Link Control Application Protocol in the chain of command.The ALCAP entity of RNC side and the ALCAP entity of NodeB side can be initiated the release flow process of service bearer.

As shown in Figure 1, initiate the release flow process of AAL2 link respectively for the ALCAP entity of RNC side and NodeB side.When the ALCAP of RNC side entity is initiated the release flow process of AAL2 link, RNC side ALCAP sends release information (Release Message, REL) instruction, to discharge information parameter and inform NodeB, these parameters are: type of message (MstType), cause parameter (CAU) and purpose protocol entity identity (DSAID).The NodeB lateral root discharges corresponding information according to the parameter of these ALCAP, returns to discharge to RNC then and finishes (Release complete, RLC) instruction.When the ALCAP of NodeB side entity was initiated the release flow process of AAL2 link, NodeB side ALCAP also sent the REL instruction, will discharge information parameter MstType, CAU and DSAID and inform RNC, and the RNC side discharges corresponding information, returned the RLC instruction to NodeB then.

With the AAL2 link is example, illustrates in the prior art, and the foundation of the service bearer of IuB interface and release are to finish by ALCAP and two common Signalling exchanges of inter-entity of NBAP on RNC and the NodeB.

The AAL2 link establishing method is as follows:

AAL2 link bearer (PATH_ID+C_ID) on the IuB interface is responsible for distributing and safeguarding by the RNC side, and base station side is safeguarded carrying (BindingID) and the one group of inside of base station carrying (FP_ID) on the IuB interface.Radio Link (RL) is set up process need and set up a service bearer on the IuB interface, promptly needs to set up by BindingID the corresponding relation of AAL2 link bearer and inside of base station carrying.

Base station side NBAP sets up in the process to the user distributes a BindingID and a FP_ID at RL, and sets up the corresponding relation of BindingID and user's transmission channel bearing (TrCH_ID) and BindingID and FP_ID.RNC is informed with the corresponding relation of BindingID and TrCH_ID in the base station, and the corresponding relation of BindingID and FP_ID is informed base station side ALCAP protocol entity (TNL), and the TNL entity will be reserved this group corresponding relation, as the transmission bearer of inside of base station.

The BindingID that RNC obtains in the link establishment response distributes a PATH_ID+C_ID as the transmission bearer on the IuB mouth, by the TNL entity of ALCAP signaling base station side, the TNL entity can connect the path that forms a business datum with carrying on the IuB interface and inside of base station carrying according to BindingID like this.

AAL2 link method for releasing is as follows:

After finishing the resetting of NBAP, sub-district deletion and obstruction process, the Signalling exchange of the ALCAP entity of holding by RNC end and NodeB is finished the release flow process of AAL2 link.

The release flow process of AAL2 link when as shown in Figure 2, initiating reseting procedure for the RNC side.When RNC carries out reset operation to the user, the PATH_ID+C_ID that RNC need find corresponding BindingID and distribute for it according to TrCH_ID.The ALCAP of RNC side is by sending reset message signaling (RES) to NodeB, inform the carrying that the TNL entity of NodeB need discharge, it is the corresponding relation of BindingID and AAL2 link bearer, find corresponding with it inside of base station carrying FP ID and discharge this corresponding relation according to BindingID after NodeB receives, then NodeB sends out to reset to RNC and confirms signaling (RSC), RNC receives and confirms that the order back discharges the corresponding relation of BindingID and AAL2 link bearer, thereby finishes the release of service bearer.A user's carrying discharged flow process when promptly the RSC Signalling exchange that sends of RES signaling of sending by RNC side ALCAP and NodeB side ALCAP had been finished reseting procedure.

The release flow process of AAL2 link when as shown in Figure 3, initiating the sub-district delete procedure for the RNC side.After RNC finishes the sub-district deletion, the ALCAP of RNC side is by sending reset message signaling (RES) to NodeB, inform the carrying of user in the sub-district that the TNL entity of NodeB need discharge, it is the corresponding relation of BindingID and AAL2 link bearer, find corresponding with it inside of base station carrying FP_ID and discharge this corresponding relation according to BindingID after NodeB receives, then NodeB sends out to reset to RNC and confirms signaling (RSC), RNC receives and confirms that the order back discharges the corresponding relation of BindingID and AAL2 link bearer, thereby finishes the release of service bearer.A user's carrying discharged flow process when promptly the RSC Signalling exchange that sends of RES signaling of sending by RNC side ALCAP and NodeB side ALCAP had been finished reseting procedure.

The release flow process of AAL2 link when as shown in Figure 4, initiating the obstruction process for the NodeB side.

The NBAP of NodeB side blocks request to the initiation of RNC, receives that again RNC returns obstruction response back to NodeB and sends the RES signaling by NodeB side ALCAP entity to the RNC side, and RNC discharges the corresponding relation of BindingID and AAL2 link bearer immediately.RNC side ALCAP entity sends the RSC signaling to the NodeB side then, and NodeB discharges the corresponding relation of BindingID and inside of base station carrying immediately.Like this, the carrying of having finished a user when blocking process of the RSC Signalling exchange that sends of RES signaling of sending by NodeB side ALCAP and RNC side ALCAP discharges flow process.

In the prior art, when needs carry out the user when discharging,, need ALCAP Signalling exchange on the IuB interface to finish the release of service bearer as reseting procedure, sub-district delete procedure or obstruction process etc.And the resource that discharges a user just needs a Signalling exchange, and RNC or NodeB can provide service for a plurality of users simultaneously, so just causes when release multi-user's service bearer the Signalling exchange on the IuB interface too much.To discharge the AAL2 link in the delete procedure of sub-district is example: the sub-district delete procedure is unit with the sub-district, after RNC initiates the resource of all CUs in the delete procedure release sub-district, sub-district, needing to discharge one group is the AAL2 link that the user distributes in the sub-district, but the ALCAP agreement does not have the signaling process of one group of AAL2 link bearer of release of standard, can only be by the method for wall scroll release, cause signaling too much, complexity is higher and system effectiveness is lower.

Summary of the invention

The method for releasing and the system that the purpose of this invention is to provide a kind of service bearer, with solve exist in the prior art since the signaling that the wall scroll releasing bearing causes too much, problem that efficient is lower.

The invention provides a kind of method for releasing of service bearer, this method comprises:

When radio network controller (RNC) when base station node B sends the user comprise release cause and discharges Indication message, RNC concentrates and discharges all service bearers corresponding with this release cause in this side;

When NodeB received that the user who comprises release cause of RNC transmission discharges Indication message, NodeB concentrated and discharges all service bearers corresponding with this release cause in this side.

It is reset request message that the described user who comprises release cause discharges Indication message, or is the sub-district deletion request message, or for blocking response message.

Described RNC side comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP;

When RNC when NodeB sends the user and discharges Indication message, described RNC concentrates the step that discharges all corresponding with this release cause in this side service bearers to comprise:

A1, RM entity issue the user to the NBAP entity and discharge Indication message, the NBAP entity discharges Indication message according to the user and concentrate to discharge and this release cause user information corresponding resource, and discharges Indication message according to the user and issue the deleting load-bearing Indication message to the ALCAP entity;

After A2, ALCAP entity are received the deleting load-bearing Indication message that the NBAP entity issues, concentrate according to this deleting load-bearing Indication message to discharge and this release cause corresponding service carrying.

Described NodeB side comprises NBAP entity and NodeB side ALCAP protocol entity TNL;

When NodeB received that the user of RNC transmission discharges Indication message, described NodeB concentrated the step that discharges all corresponding with this release cause in this side service bearers to comprise:

After B1, TNL entity receive that the user of RNC transmission discharges Indication message, transmit this user to the NBAP entity and discharge Indication message, after the NBAP entity receives that this user discharges Indication message, discharge Indication message according to the user and concentrate to discharge and this release cause user information corresponding resource, and discharge Indication message according to the user and issue the deleting load-bearing Indication message to the TNL entity;

After B2, TNL entity are received the deleting load-bearing Indication message that NBAP issues, concentrate according to this deleting load-bearing Indication message to discharge and this release cause corresponding service carrying.

When described user discharges Indication message and is reset request message, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; The deleting load-bearing Indication message is dedicated bearer deletion Indication message or base station deleting load-bearing Indication message among described steps A 2 and the B2.

When described user discharged Indication message and is the sub-district deletion request message, the user profile resource was the pairing information resources of all users in the sub-district among described steps A 1 and the B1; The deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message among described steps A 2 and the B2.

When described user discharged Indication message for the obstruction response message, the user profile resource was the pairing information resources of all users in the sub-district among described steps A 1 and the B1; The deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message among described steps A 2 and the B2.

Described reset request message will be carried out type and be judged, when the reset request type of message when resetting the user, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; The deleting load-bearing Indication message is a dedicated bearer deletion Indication message among described steps A 2 and the B2;

When the reset request type of message when resetting the base station, the user profile resource is the pairing information resources of all users in the base station among described steps A 1 and the B1; The deleting load-bearing Indication message is a base station deleting load-bearing Indication message among described steps A 2 and the B2.

Described service bearer comprises the corresponding relation of asynchronous transfer mode link bearer and user's transmission channel and the corresponding relation of the carrying on asynchronous transfer mode link bearer and the wireless access network base-station interface.

The present invention also provides a kind of service bearer delivery system, it is characterized in that, this system comprises RNC and one or more NodeB,

RNC is used for concentrating to discharge all service bearers corresponding with this release cause in this side when the user who comprises release cause to the NodeB transmission discharges Indication message;

NodeB is used for when the user who comprises release cause who receives the RNC transmission discharges Indication message, concentrates to discharge all service bearers corresponding with this release cause in this side.

Described RNC comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP;

The RM entity is used for issuing the user to the NBAP entity and discharges Indication message;

The NBAP entity is used to obtain the user that RM issues and discharges Indication message, discharges Indication message according to the user and concentrates and discharge and this release cause user information corresponding resource, and discharge Indication message according to the user and issue the deleting load-bearing Indication message to the ALCAP entity;

The ALCAP entity is used to the deleting load-bearing Indication message of receiving that the NBAP entity issues, concentrates according to the deleting load-bearing Indication message of receiving to discharge and this release cause corresponding service carrying.

Described NodeB comprises NBAP entity and ALCAP protocol entity TNL;

The TNL entity is used to receive the user that RNC sends and discharges Indication message, this user is discharged Indication message be transmitted to the NBAP entity, and receive the deleting load-bearing Indication message that NBAP issues, concentrate according to this deleting load-bearing Indication message to discharge and this release cause corresponding service carrying;

The NBAP entity is used to receive that the user that RNC that the TNL entity is transmitted sends discharges Indication message, discharge Indication message according to the user and concentrate to discharge and this release cause user information corresponding resource, and discharge Indication message according to the user and issue the deleting load-bearing Indication message to the TNL entity.

When described user discharges Indication message and is reset request message, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; Described deleting load-bearing Indication message is dedicated bearer deletion Indication message or base station deleting load-bearing Indication message.

When described user discharged Indication message and is the sub-district deletion request message, described user profile resource was the pairing information resources of all users in the sub-district; Described deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message.

When described user discharged Indication message for the obstruction response message, described user profile resource was the pairing information resources of all users in the sub-district; Described deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message.

When described user discharged Indication message and is reset request message, described NBAP entity also comprised type judging module;

When type judging module is judged the reset request type of message when resetting the user, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message; Described deleting load-bearing Indication message is a dedicated bearer deletion Indication message;

Judge the reset request type of message when resetting the base station when type judging module, described user profile resource is the pairing information resources of all users in the base station; Described deleting load-bearing Indication message is a base station deleting load-bearing Indication message.

The present invention also provides a kind of radio network control apparatus, and this device is used for concentrating to discharge all service bearers corresponding with this release cause in this side when the user who comprises release cause to the base station transmission discharges Indication message.

This device comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP;

The present invention also provides a kind of base station, and this base station is used for when the user who comprises release cause who receives the radio network controller transmission discharges Indication message, concentrates to discharge all service bearers corresponding with this release cause in this side.

This base station comprises NBAP entity and ALCAP protocol entity TNL;

The present invention by RNC when NodeB sends the user comprise release cause and discharges Indication message, RNC concentrate to discharge all corresponding with this release cause in this side service bearers and when NodeB receives that the user who comprises release cause of RNC transmission discharges Indication message, NodeB concentrates and discharges all service bearing method corresponding with this release cause in this side, significantly reduced the mutual of ALCAP signaling on the IuB interface, reduce the transmission load on the IuB interface, improved the efficient and the stability of system.

Description of drawings

Fig. 1 initiates AAL2 respectively for RNC side in the prior art and NodeB side and discharges schematic flow sheet;

Fig. 2 is the release schematic flow sheet of AAL2 link when the RNC side is initiated reseting procedure in the prior art;

Fig. 3 is the release schematic flow sheet of AAL2 link when the RNC side is initiated the sub-district delete procedure in the prior art;

Fig. 4 is the release schematic flow sheet of AAL2 link when the NodeB side is initiated the obstruction process in the prior art;

Fig. 5 among the embodiment among the present invention during reseting procedure RNC and NodeB discharge the signaling process schematic diagram of AAL2 link bearer alternately by internal entity separately;

Fig. 6 among the embodiment among the present invention during the delete procedure of sub-district RNC and NodeB discharge the signaling process schematic diagram of AAL2 link bearer alternately by internal entity separately;

Fig. 7 RNC and NodeB when blocking process among the embodiment among the present invention discharge the signaling process schematic diagram of AAL2 link bearer alternately by internal entity separately;

Fig. 8 is a RNC side ALCAP entity structure schematic diagram in the embodiment of the invention;

Fig. 9 in the embodiment of the invention during reseting procedure RNC side internal entity discharge the signaling process schematic diagram of AAL2 link bearer alternately;

Figure 10 in the embodiment of the invention during reseting procedure RNC side internal entity discharge AAL2 link bearer step schematic diagram alternately;

Figure 11 in the embodiment of the invention during delete procedure of sub-district RNC side internal entity discharge AAL2 link bearer step schematic diagram alternately;

Figure 12 is that RNC side internal entity discharges AAL2 link bearer step schematic diagram alternately when blocking process in the embodiment of the invention;

Figure 13 in the embodiment of the invention during reseting procedure NodeB side internal entity discharge the signaling process schematic diagram of AAL2 link bearer alternately;

Figure 14 in the embodiment of the invention during reseting procedure NodeB side internal entity discharge AAL2 link bearer step schematic diagram alternately;

Figure 15 in the embodiment of the invention during delete procedure of sub-district NodeB side internal entity discharge the signaling process schematic diagram of AAL2 link bearer alternately;

Figure 16 in the embodiment of the invention during delete procedure of sub-district NodeB side internal entity discharge AAL2 link bearer step schematic diagram alternately;

Figure 17 is the signaling process schematic diagram that NodeB side internal entity discharges the AAL2 link bearer alternately when blocking process in the embodiment of the invention;

Figure 18 is that NodeB side internal entity discharges AAL2 link bearer step schematic diagram alternately when blocking process in the embodiment of the invention.

Embodiment

To discharge the signaling that service bearer causes on the IuB interface mutually in RNC side and NodeB top-cross too much in order to solve, and the problem that system effectiveness is lower the present invention proposes in RNC side and NodeB side in the method for the own releasing bearing in two ends separately.

In the present invention, RNC and NodeB side respectively have a sets of plan, realize realizing the two ends purpose of releasing bearing resource separately by reaching alternately between internal entity separately.Therefore, the present invention has defined the message format of NBAP entity and ALCAP entity interaction, is used to specify the release of carrying.In RNC side and NodeB side NBAP entity and ALCAP entity are arranged all, and the function of finishing in both sides is similarly, difference is the scope difference of both sides control resource.Therefore, the message format of definition can apply to RNC side and NodeB side.The message format of definition is respectively:

1, dedicated bearer deletion Indication message (O_APBTNL_DEL_BEARER_IND), be used to notify the ALCAP entity to discharge the transmission bearer of one group of appointment, definition structure is stored the quantity of releasing bearing in a piece of news in the message header, promptly needs the quantity of the BindingID that deletes; Also definition structure is deposited a carrying on the IuB interface.Because each dispose procedure is unit with user, so in order to handle conveniently, the carrying quantity of NBAP statistics is unit with the frequency, promptly once discharging on a certain frequency is the carrying that one group of user distributes, if initiate type and be to reset during user's reseting procedure, because the user who relates on a plurality of frequencies, then sends out multiple messages with the frequency grouping to TNL.

2, base station deleting load-bearing message (O_APBTNL_DEL_NB_BEARER_IND), when the IuB interface is initiated whole base station user's reseting procedure, the NBAP entity sends O_APBTNL_DEL_NB_BEARER_IND message to the ALCAP entity, discharges all special-purpose AAL2 links of NodeB.The bearer types that defines release by definition structure u8ComDediFlag in message header is public or special-purpose.

3, sub-district deleting load-bearing message (O_APBTNL_DEL_CELL_DEDI_BEARER_IND), when initiating the sub-district deletion on the IuB mouth or blocking process, the NBAP entity sends O_APBTNL_DEL_CELL_DEDI_BEARER_IND message to the ALCAP entity, discharges the dedicated bearer in the sub-district.Because each frequency in the sub-district all has an initial link address (StartFP_ID), so only the StartFP_ID of all frequencies in the sub-district need be informed the TNL entity in the message, the TNL entity just can discharge all dedicated bearers in the sub-district.The number of can definition structure u8NofStartFP_ID in message header storing initial FP_ID, definition structure u16StartFP_ID stores the FP_ID information that needs the TNL deletion.

Below in conjunction with Figure of description method of the present invention is described in further detail.

The AAL2 link bearer is embodiment on the IuB interface to discharge, and illustrate among the present invention at reseting procedure, sub-district delete procedure and when blocking process, and RNC and NodeB are by the process of AAL2 link bearer on the mutual release IuB interface between internal entity separately.

As shown in Figure 5, when reseting procedure, the resource dispose procedure of RNC side is:

The RNC side is at first initiated the NBAP reset request to the NodeB side, the resource allocation entity of RNC side (Resource manager, RM) issue user's reset message to RNC side NBAP entity, with the user profile resource of release NBAP preservation and the corresponding relation of user's transmission channel and AAL2 link bearer; The NBAP entity issues dedicated bearer deletion Indication message or base station deleting load-bearing message in order to the AAL2 link bearer that discharges ALCAP and preserve and the corresponding relation of BindingID to ALCAP then.

When reseting procedure, the resource dispose procedure of NodeB side is:

Receive the reset request of RNC initiation when the NodeB side after, carry out the NBAP reseting procedure and discharge the user profile resource, the NBAP reseting procedure is exactly RNC discharges the user profile resource by NBAP reset message notice NodeB a process; Issue dedicated bearer deletion Indication message or base station deleting load-bearing message to the ALCAP of NodeB side protocol entity TNL then, the TNL entity discharges the corresponding relation of BindingID and inside of base station carrying immediately.After dispose procedure finished, NodeB returned the response that resets to RNC.

As shown in Figure 6, when the delete procedure of sub-district, the resource dispose procedure of RNC side is:

The RNC side is at first initiated NBAP sub-district removal request to the NodeB side, and the RM entity of RNC side issues sub-district deletion message to the NBAP entity, in order to all user profile resources in the sub-district that discharges the NBAP preservation; The NBAP entity issues sub-district deleting load-bearing Indication message in order to discharge the corresponding relation of AAL2 link bearer and BindingID to the ALCAP entity then.

When the delete procedure of sub-district, the resource dispose procedure of NodeB side is:

Receive the sub-district removal request of RNC initiation when the NodeB side after, just carry out NBAP sub-district delete procedure and discharge user resources, NBAP sub-district delete procedure is exactly the process of RNC by public in the NBAP sub-district deletion message informing NodeB release sub-district and private resource; Issue the deleting load-bearing Indication message of respective cell then to the TNL entity, the TNL entity discharges the corresponding relation of BindingID and inside of base station carrying immediately.After dispose procedure finished, NodeB returned sub-district deletion response to RNC.

As shown in Figure 7,, be used for the use of restricted cell logical resource, so initiate to block request by NodeB in the NBAP aspect because the obstruction process mainly is at the wireless network layer chain of command.

When blocking process, the resource dispose procedure of RNC side is:

Initiate the request of NBAP obstruction by NodeB to RNC, the RNC side receives that this blocks the request back and returns the obstruction response to NodeB.RNC side RM entity issues obstruction message to the NBAP entity, in order to the user profile resource of release NBAP preservation and the corresponding relation of user's transmission channel and carrying; The NBAP entity issues sub-district deleting load-bearing Indication message in order to discharge the corresponding relation of AAL2 link bearer and BindingID to the ALCAP entity then.

When blocking process, the resource dispose procedure of NodeB side is:

After the NodeB side is received the obstruction response that RNC returns, just to carry out NBAP obstruction process and discharge the private subscribers resource sub-district in, NBAP obstruction process is exactly RNC blocks all private subscribers resources of response notice NodeB release sub-district by NBAP a process; Issue the deleting load-bearing Indication message of respective cell then to the TNL entity, the TNL entity discharges the corresponding relation of BindingID and inside of base station carrying immediately.

Below still the AAL2 link bearer is embodiment on the IuB interface to discharge, and illustrates that respectively RNC side and NodeB side are by discharging the process of AAL2 link bearer on the IuB interface separately alternately between internal entity.

The RNC side has been safeguarded NBAP information and ALCAP information.Wherein NBAP information has comprised the user totem information (CRNC_CC_ID) of user profile, transmitting channel information (DCH_ID), and the inside of base station bearing identification information of transmission channel correspondence.CRNC_CC_ID and NBCC_ID have represented a user ID, and different is CRNC_CC_ID is at the RNC side management, and NBCC_ID is at the NodeB side management.DCH_ID is the transmission channel sign that a user uses, and belongs to a user's child resource, and each transmission channel need distribute a transmission bearer, is its transmission service.ALCAP information comprises routing iinformation and beared information.Routing iinformation has comprised adjacent node information, outlet is by information and go into route information; Beared information comprises virtual link number (PATH_ID) and hyphen (C_ID).RNC is mutual by ALCAP entity and NodeB, thereby sets up, discharges and safeguard the IuB interface link.The storage organization of these information in RNC is as shown in table 1:

Resource name	Attribute	Explanation
Resource name	Attribute	Explanation	CRNC_CC_ID	NBCC_ID	User ID in the respective base station
AP_RL[0-1]				NBCC_ID	User ID in the respective base station
AP_RL[0-1]					u8DCH_ID[0-4]		The transmission channel of every link
		PATH_ID+C_ID			u8DCH_ID[0-4]		The transmission channel of every link	The AAL2 link bearer of transmission channel correspondence
		PATH_ID+C_ID				u32BindingID	The inside of base station carrying of transmission channel correspondence	The AAL2 link bearer of transmission channel correspondence
ALCAP	PATH_ID	On the IuB interface AAL2 link bearer be by				u32BindingID

C_ID[8-255]	The RM entity distributes
C_ID[8-255]	The RM entity distributes	Altsap	PATH_ID quantity
Dlsap/Sntsap	C_ID quantity	Altsap	PATH_ID quantity
Dlsap/Sntsap	C_ID quantity	AdjNode	Adjacent node

Table 1

As shown in Figure 8, be RNC side ALCAP entity structure schematic diagram, wherein: the nodal function entity (Nodal Function, NF): realize that route and internal resource distribute and the recovery function; Protocol entity (Protocal Entity, PE): be used for the maintenance link state; ALCAP user subject (AA): be used for setting up and discharging internal path, the maintain internal link circuit resource is carried out foundation or is discharged the operation that drives link.

The RNC lateral root is initiated corresponding NBAP process according to service needed, and the NBAP entity just discharges corresponding resource.Be example with reseting procedure, sub-district delete procedure and obstruction process respectively below, illustrate that the RNC side discharges the process of AAL2 link bearer on the IuB interface.

As Fig. 9 and shown in Figure 10, RNC side resource release steps is when reseting procedure:

Step 1001:RNC at first initiates reset request to NodeB.

The RM entity of step 1002:RNC side issues user's reset message to the NBAP entity, discharges the user profile of NBAP preservation and the corresponding relation of user's transmission channel and AAL2 link bearer.This step specific implementation is:

After the NBAP entity is received reset message, at first judge reset types determine to reset user's scope.Owing to when RM issues user's reset message, comprised reset types information in this message, reset types is divided into the reset user and the base station that resets.When reset types when resetting the user, when promptly resetting, add up this group user profile resource and be the BindingID resource of this group user distribution according to the frequency at user place according to reset sign NBCC_ID or CRNC_CC_ID.Since the NBAP entity management user totem information and transmitting channel information, the method of statistics is exactly according to the user ID circulation carrying of each CU that need reset to be found and is saved in the array, all is saved in the array up to the carrying with all users that need reset.Discharge the corresponding relation of user profile resource and the user's transmission channel and the AAL2 link bearer of this preservation immediately.When reset types when resetting the base station, need the carrying of all users in the accounting base-station to find and be saved in the array equally, discharge the corresponding relation of all user profile resources and user's transmission channel and AAL2 link bearer in the base station of this preservation again.

Step 1003:NBAP entity is sent out the deleting load-bearing Indication message to the ALCAP entity, AAL2 link bearer that ALCAP release oneself is preserved and the corresponding relation of BindingID, and the link entity PE of release respective links.The processing of ALCAP is finished by AA, NF and three sub-protocol entities of PE, and these three entities are finished link alternately by inside story and discharged.

At first, determine the deleting load-bearing Indication message according to the reset types of NBAP.If reset types is when resetting the user, then the AA of NBAP in ALCAP sends dedicated bearer and deletes Indication message; If reset types is the base station that resets, then the AA of NBAP in ALCAP sends base station deleting load-bearing message.In the present embodiment, the reset types of employing is the user that resets.Because AA can carry out the operation that discharges link, therefore, AA just sends AAL2 link release application (AaLiAltRelReq) to NF after receiving dedicated bearer deletion Indication message.After NF receives the release application that AA sends, just send the AAL2 link and discharge application (alNptRelReq) to PE.After PE receives the release application that NF sends, just discharge the corresponding relation of AAL2 link bearer and BindingID, send the AAL2 link to NF then and discharge affirmation (alNptRlcCfm).NF receives that link that PE sends discharges and just discharges PE after confirming, sends the AAL2 link to AA immediately and discharges and confirm (AlUiAltRlcCfm), just finished the RNC side carrying dispose procedure of a reseting procedure this moment.

As shown in figure 11, RNC side resource release steps is when the delete procedure of sub-district:

Step 1101:RNC at first initiates the sub-district removal request to NodeB.

The RM entity of step 1102:RNC side issues sub-district deletion message to the NBAP entity, and NBAP carries out the sub-district delete procedure, and user profile resource and being kept in the array in the statistics sub-district discharges the user profile resource in the sub-district of preserving then.

Step 1103:NBAP entity sends sub-district deleting load-bearing message to the ALCAP entity, AAL2 link bearer that ALCAP release oneself is preserved and the corresponding relation of BindingID, and the link entity PE of release respective links.Processing procedure and the reseting procedure of ALCAP are similar, are also finished by AA, NF and three sub-protocol entities of PE, and these three entities are finished link alternately by inside story and discharged.

At first, the AA of NBAP in ALCAP sends sub-district deleting load-bearing message.AA just sends AAL2 link release application (AaLiAltRelReq) to NF after receiving sub-district deleting load-bearing message.After NF receives the release application that AA sends, just send the AAL2 link and discharge application (alNptRelReq) to PE.After PE receives the release application that NF sends, just discharge the corresponding relation of AAL2 link bearer and BindingID, send the AAL2 link to NF then and discharge affirmation (alNptRlcCfm).NF receives that link that PE sends discharges and just discharges PE after confirming, sends the AAL2 link to AA immediately and discharges and confirm (AlUiAltRlcCfm), just finished the RNC side carrying dispose procedure of a sub-district delete procedure this moment.

As shown in figure 12, RNC side resource release steps is when blocking process:

Step 1201:NodeB at first initiates to block request to RNC.

Step 1202:RNC returns to NodeB and blocks response.The RM entity of RNC side issues to the NBAP entity and blocks response, and NBAP carries out the obstruction process, and user resources and being kept in the array in the statistics sub-district discharge the user in the user profile and sub-district in the sub-district of preserving then.

Step 1203:NBAP entity sends sub-district deleting load-bearing message to the ALCAP entity, the corresponding relation of AAL2 link bearer that ALCAP release oneself is preserved and inside of base station carrying BindingID, and the link entity PE of release respective links.Processing procedure and the reseting procedure of ALCAP are similar, are also finished by AA, NF and three sub-protocol entities of PE, and these three entities are finished link alternately by inside story and discharged.

At first, the AA of NBAP in ALCAP sends sub-district deleting load-bearing message.AA just sends AAL2 link release application (AaLiAltRelReq) to NF after receiving sub-district deleting load-bearing message.After NF receives the release application that AA sends, just send the AAL2 link and discharge application (alNptRelReq) to PE.After PE receives the release application that NF sends, just discharge the corresponding relation of AAL2 link bearer and BindingID, send the AAL2 link to NF then and discharge affirmation (alNptRlcCfm).NF receives that link that PE sends discharges and just discharges PE after confirming, sends the AAL2 link to AA immediately and discharges and confirm (AlUiAltRlcCfm), just finished the RNC side carrying dispose procedure of a secondary stricture process this moment.

The NBAP entity maintaining of NodeB side the relation between user's transmission channel ID and the BindingID, can discharge this group corresponding relation by inter-process, and notify ALCAP to discharge the corresponding relation of BindingID and FP_ID by the mode of inter-entity message.

In the NodeB side NBAP entity to the management such as the table 2 of user and bearing resource:

Resource name	Attribute		Explanation
Resource name	Attribute		Explanation	AP_UARFCN	Air-link resources item AP_RL[0-23]		Frequency is the wireless link information of management down
FP_ID[0-59] the inside of base station carrying					Air-link resources item AP_RL[0-23]
FP_ID[0-59] the inside of base station carrying			NBCC[0-71]		NBCC_ID
AP_NBCC_RL_Index[0-1]		Be initialized as invalid value			NBCC_ID
AP_NBCC_RL_Index[0-1]		Be initialized as invalid value			u8UARFCN_Index	RL place frequency index
u8LocalRL_Index	The RL local index				u8UARFCN_Index	RL place frequency index
u8LocalRL_Index	The RL local index	BindingID			u32BindingID		, a carrying on the IuB interface
u16FP_ID_Index			Corresponding inner link carrying		u32BindingID		, a carrying on the IuB interface
u16FP_ID_Index			Corresponding inner link carrying	AP_RL	u8DCH_ID[0-4]		The transmission channel of RNC configure user
	u32BindingID	The carrying that the base station is distributed for each transmission channel			u8DCH_ID[0-4]		The transmission channel of RNC configure user
	u32BindingID				u16FP_ID

Table 2

Current user profile is by RL information management under NBCC information and the frequency.Can find out the RL resource by the RL local index under the NBCC, have user's transmitting channel information under every RL, and NBAP to be these transmission channels of user distribute corresponding bearer resource, have the index that distributes bearing resource under the dedicated channel (DCH).When the NodeB side needed oneself to discharge AAL2 link dedicated bearer, NBAP added up the carrying that need discharge according to the resource of managing in the resource table, and sent deleting load-bearing message according to reset types and statistical content to the TNL entity.

The NodeB lateral root is initiated corresponding NBAP process according to service needed, and the NBAP entity just discharges corresponding resource.Be example with reseting procedure, sub-district delete procedure and obstruction process respectively below, illustrate that the NodeB side discharges the process of AAL2 link bearer on the IuB interface.

As Figure 13 and shown in Figure 14, NodeB side resource release steps is when reseting procedure:

Step 1401:RNC side direction NodeB side is initiated reset request.Because it is to be responsible for receiving and be transmitted to other entities of NodeB inside by the TNL entity of NodeB that RNC issues the message of NodeB and message that NodeB issues RNC, so the reset request of this moment is transmitted to the NBAP of NodeB side by TNL.

Step 1402: carry out the NBAP reseting procedure.Because the NBAP reseting procedure is to discharge the user profile resource, the user's that therefore will determine earlier to reset scope is judged the reset types of NBAP.When TNL is transmitted in the reset request of NBAP by the initiation of RNC side, comprised reset types information in this request.NBAP reads this reset types and carries out corresponding reseting procedure.As shown in table 2, the NBAP entity management beared information that uses of user ID and each user, so when carrying out reseting procedure, will add up the BindingID carrying that distributes into the user.

If when NBAP resetted the user, reseting procedure was: after NBAP judges the user procedures that resets by the information in the reset request, according to of the BindindID carrying of frequency statistics in user place for this group user distribution.Statistical method is: as shown in table 2, current user profile is by RL information management under NBCC information and the frequency, has user's transmitting channel information in NBCC under every RL, has the carrying index of channel allocation under the DCH.Therefore, each user profile that need reset can be found and is saved in the array,, discharge the user profile resource of this preservation then up to all user profile that need reset all are saved in this array according to user ID.

If when NBAP resetted the base station, reseting procedure was: interior all users' of accounting base-station information also is saved in the array, up to all user profile all is saved in this array, discharges the user profile resource of this preservation then.

Step 1403:NBAP issues deleting load-bearing message according to reset types and statistical content to TNL, and TNL discharges the corresponding relation of BindingID and inside of base station carrying then.

If reset types is when resetting the user, NBAP issues dedicated bearer deletion Indication message to TNL, and notice TNL discharges the transmission bearer of appointment.When reset types when resetting the user, the user who relates to may then send out multiple messages with the frequency grouping to TNL on a plurality of frequencies.Owing in statistical content, preserved the user profile that needs release, so TNL can discharge the BindingID of appointment and the corresponding relation of inside of base station carrying according to this statistical content.

If reset types is when resetting the base station, NBAP issues base station deleting load-bearing Indication message to TNL, and notice TNL discharges all AAL2 links.In statistical content, preserved all user profile in the base station, so TNL can discharge the corresponding relation of all BindingID and inside of base station carrying according to inferior statistical content.

Step 1404: behind the mutual releasing bearing of NodeB side internal entity, NodeB returns the response that resets to RNC when having finished reseting procedure.

As Figure 15 and shown in Figure 16, NodeB side resource release steps is when the delete procedure of sub-district:

Step 1601:RNC initiates the sub-district removal request to NodeB, and this request is forwarded to NodeB side NBAP place by TNL.

Step 1602: carry out NBAP sub-district delete procedure.The sub-district delete procedure is the process of public and dedicated bearer in the release sub-district of being initiated by RNC, the carrying of CU and being saved in the array in the NBAP statistics sub-district, and NBAP discharges common carrier in the sub-district, dedicated bearer and user profile then.Common carrier is the common carrying of using of user in the sub-district, and dedicated bearer is the carrying that the certain user takies separately in the sub-district, and common carrier and dedicated bearer are all on the logic aspect.

Step 1603:NBAP issues sub-district deleting load-bearing Indication message to TNL, and TNL discharges the corresponding relation of BindingID and inside of base station carrying immediately.

Step 1604: behind the mutual releasing bearing of NodeB side internal entity, NodeB returns sub-district deletion response to RNC when having finished the sub-district delete procedure.

As Figure 17 and shown in Figure 180, NodeB side resource release steps is when blocking process:

Step 1801:NodeB initiates to block request to RNC.This obstruction request is to be initiated by the Operation and Maintenance entity (AOM) of base station among the NodeB, is forwarded to TNL by NodeB side NBAP and TNL.

Step 1802:RNC returns to NodeB and blocks response, and this obstruction response is forwarded among the NBAP by TNL.

Step 1803: carry out NBAP and block process.The carrying of CU and being saved in the array in the NBAP statistics sub-district, NBAP discharges private subscribers resource in the sub-district of this preservation then.

Step 1804:NBAP issues sub-district deleting load-bearing Indication message to TNL, and TNL discharges the corresponding relation of BindingID and inside of base station carrying immediately.

Can reduce ALCAP Signalling exchange on the IuB interface by service bearer method for releasing on the IuB interface of the present invention, reduce the transmission load on the IuB interface, improve the stability of a system.

The present invention also provides the delivery system of service bearer on a kind of IuB interface, and this system comprises RNC side and one or more NodeB side, and RNC side and NodeB side are the request that discharges by the user and response signaling intercommunication.

In the present invention, request that the user discharges and response comprise reset request and the response that resets, and sub-district removal request and sub-district deletion response are blocked request and blocked response.

Though a RNC can control a plurality of NodeB, in practical operation, the intercommunication operation of RNC and each NodeB can be thought independent and non-interfering.According to the real work situation of NodeB, RNC manages NodeB by request and the response signaling that different users discharges.

If need reset or during the delete procedure of sub-district, initiate demand signalling by RNC side direction NodeB side, mutual by the RNC internal entity, oneself discharges service bearer, after NodeB receives the demand signalling of RNC initiation, mutual by the NodeB internal entity, oneself discharges service bearer, and returns response signaling to RNC; If in the time of need blocking process, initiate demand signalling by NodeB side direction RNC side, after RNC side direction NodeB side is returned response signaling, mutual by the RNC internal entity, oneself discharges service bearer, after NodeB received the response signaling that RNC returns, mutual by the NodeB internal entity, oneself discharged service bearer.

Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.

Claims

1. the method for releasing of a service bearer is characterized in that, this method comprises:

2. method according to claim 1 is characterized in that it is reset request message that the described user who comprises release cause discharges Indication message, or is the sub-district deletion request message, or for blocking response message.

3. method according to claim 1 is characterized in that described RNC side comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP;

4. method according to claim 1 is characterized in that described NodeB side comprises NBAP entity and NodeB side ALCAP protocol entity TNL;

5. as method as described in the claim 2, it is characterized in that, when described user discharges Indication message and is reset request message, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; The deleting load-bearing Indication message is dedicated bearer deletion Indication message or base station deleting load-bearing Indication message among described steps A 2 and the B2.

6. as method as described in the claim 2, it is characterized in that when described user discharged Indication message and is the sub-district deletion request message, the user profile resource was the pairing information resources of all users in the sub-district among described steps A 1 and the B1; The deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message among described steps A 2 and the B2.

7. as method as described in claim 3 or 4, it is characterized in that when described user discharges Indication message when blocking response message, the user profile resource is the pairing information resources of all users in the sub-district among described steps A 1 and the B1; The deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message among described steps A 2 and the B2.

8. as method as described in the claim 5, it is characterized in that, described reset request message will be carried out type and be judged, when the reset request type of message when resetting the user, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; The deleting load-bearing Indication message is a dedicated bearer deletion Indication message among described steps A 2 and the B2;

9. method according to claim 1 is characterized in that described service bearer comprises the corresponding relation of asynchronous transfer mode link bearer and user's transmission channel and the corresponding relation of the carrying on asynchronous transfer mode link bearer and the wireless access network base-station interface.

10. a service bearer delivery system is characterized in that, this system comprises RNC and one or more NodeB,

11., it is characterized in that it is reset request message that the described user who comprises release cause discharges Indication message, or be the sub-district deletion request message, or for blocking response message as system as described in the claim 10.

12., it is characterized in that described RNC comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP as system as described in the claim 10;

13., it is characterized in that described NodeB comprises NBAP entity and ALCAP protocol entity TNL as system as described in the claim 10;

14. as system as described in claim 12 or 13, it is characterized in that, when described user discharges Indication message and is reset request message, comprised the user totem information that needs the user profile of deletion in this reset request message, the user profile resource is the pairing information resources of user totem information that comprise in the reset request message among described steps A 1 and the B1; Described deleting load-bearing Indication message is dedicated bearer deletion Indication message or base station deleting load-bearing Indication message.

15., it is characterized in that when described user discharged Indication message and is the sub-district deletion request message, described user profile resource was the pairing information resources of all users in the sub-district as system as described in claim 12 or 13; Described deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message.

16., it is characterized in that when described user discharges Indication message when blocking response message, described user profile resource is the pairing information resources of all users in the sub-district as system as described in claim 12 or 13; Described deleting load-bearing Indication message is a sub-district deleting load-bearing Indication message.

17., it is characterized in that when described user discharged Indication message and is reset request message, described NBAP entity also comprised type judging module as system as described in claim 12 or 13;

18., it is characterized in that described service bearer comprises the corresponding relation of asynchronous transfer mode link bearer and user's transmission channel and the corresponding relation of the carrying on asynchronous transfer mode link bearer and the wireless access network base-station interface as system as described in the claim 10.

19. a radio network control apparatus is characterized in that, this device is used for concentrating to discharge all service bearers corresponding with this release cause in this side when the user who comprises release cause to the base station transmission discharges Indication message.

20., it is characterized in that this device comprises resource allocation entity RM, base station application part entity NBAP and Access Link Control Application Protocol entity A LCAP as device as described in the claim 19;

21. a base station is characterized in that, this base station is used for when the user who comprises release cause who receives the radio network controller transmission discharges Indication message, concentrates to discharge all service bearers corresponding with this release cause in this side.

22., it is characterized in that this device comprises NBAP entity and ALCAP protocol entity TNL as base station as described in the claim 21;