CN102378393A

CN102378393A - Relay node non-access stratum processing method and equipment

Info

Publication number: CN102378393A
Application number: CN2010102512307A
Authority: CN
Inventors: 杨义
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2010-08-11
Filing date: 2010-08-11
Publication date: 2012-03-14
Anticipated expiration: 2030-08-11
Also published as: CN102378393B

Abstract

The invention discloses a relay node non-access stratum processing method and equipment. The method comprises the steps that after access equipment is determined to be a relay node by a mobility management entity, when the access cell of the mobility management entity and the relay node on an evolved node B supports the relay node, the evolved node B is informed about that a network has been already prepared; after the evolved node B is determined to be selected as a serving gateway/packet data network gateway for the relay node, an indication that the network has been already prepared is transmitted to the relay node; when the relay node is informed about that the network has been already prepared, the relay node keeps the built connection with a packet data network; and when the relay node is not informed about that the network has been already prepared, the relay node conducts a detaching process to release the existing connection with the packet data network and conducts an attaching process to rebuild new connection with the packet data network. The relay node non-access stratum processing method and the equipment have the advantages that the starting process of the relay node can be simplified, the starting time of the relay node is shortened and the unnecessary signaling process and bearer management are reduced.

Description

A kind of Non-Access Stratum procedure processing method and equipment of via node

Technical field

The present invention relates to mobile communication technology, particularly a kind of Non-Access Stratum procedure processing method and equipment of via node.

Background technology

GSM in future; For example in back three generations (B3G:Beyond Third Generation) or LTE-A (Long Term Evolution-Advanced, long-term evolution upgrading), system will provide higher peak data rate and cell throughout; Also need bigger bandwidth simultaneously; At present the unassigned bandwidth below the 2GHz seldom, the part or all of bandwidth that the B3G system needs can only be on higher frequency range, for example 3GHz is above seeks.Frequency range is high more, and it is fast more that radio wave propagation is decayed, and transmission range is short more, under the therefore same overlay area, guarantee continuous covering, needs more base station, because the base station has higher cost usually, this can increase the cost of arranging net undoubtedly.In order to solve arrange net cost and covering problem, each manufacturer and standardization body begin one's study relaying are incorporated in the cellular system, increase to cover.

Fig. 1 is for comprising RN (Relay Node; Via node) E-UTRAN (Evolved UniversalTerrestrial Radio Access Network, the universal land radio access web of evolution) network architecture sketch map, as shown in the figure; After the LTE-A system introduces RN; RN is linked into core net through the donor cell (alms giver sub-district) under the DeNB (alms giver's evolution base station) and core net does not have direct wireline interface, and each RN can control one or more sub-districts.Under this framework, the interface between UE (User Equipment, subscriber equipment) and the RN is called the Uu mouth, and the interface between RN and the DeNB is called the Un mouth.

RN has dual identity in the framework:

At first RN has the identity of UE, and RN is similar to the start attaching process of UE when starting.RN has SGW/PGW (Serving Gateway/PDN Gateway, gateway/packet data gateway) and the Control Node MME (Mobility Management Entity, Mobility Management Entity) of oneself.

Secondly, for the UE that inserts RN, RN has the identity of eNB, and this moment, the downlink data of UE need send to the serving BS of UE from the SGW/PGW of UE, i.e. RN, and RN issues UE on the Uu mouth then.

The RN start-up course can be described as: set up RRC (Radio ResourceControl, Radio Resource control) between RN and the DeNB and connect; RN sends attach request to MME; MME carries out authentication from the subscription data that HSS (HomeSubscriber Server, home subscriber server) locates to obtain RN to RN; If authentication is passed through, MME for RN sets up default bearing, and sends the initial UE context to DeNB and sets up request message in DeNB (S-GW/P-GW funtion part), in DeNB, sets up the context of RN; DeNB sends RRC to RN and connects reconfiguration message subsequently, carries MME and issues adhering to of RN and accept message; RN returns RRC and connects to reshuffle to accomplish and confirm.Like this, RN has set up basic IP connection.

O&M (Operation and Maintenance, operation and maintenance system) downloads to RN with node configuration information then, and RN is configured.After RN sets up necessary S1 interface and X2 interface again, just can be as the base station operate as normal.

RN only and DeNB set up an X2 interface and a S1 interface.It is a sub-district below the DeNB that other base stations and core net are looked RN; DeNB only need upgrade the X2/S1 that has set up and connect: need upgrade to other base stations and add a new sub-district; If the TAC of RN sub-district is (Tracking Area Code; Tracking Area Code) be new, then DeNB is to new TAC of MME registration.

U adheres in (Attach) process, and network is that UE selects PGW, and between UE and PGW, sets up default bearing.PGW can initiate to set up the dedicated bearer process after setting up default bearing.Dedicated bearer is set up process and can be followed attaching process to accomplish together, also can carry out separately subsequently.UE also can initiate dedicated bearer to network and set up request in needs, the request network is that UE sets up dedicated bearer.

A PDN (Packet Data Network, Packet Data Network) connects and comprises a default bearing and several dedicated bearers.

After the UE access network, MME is that UE selects SGW and PGW.Selecting the standard of SGW mainly is according to user position information, also will consider the loading condition between the different SGW.Overlapping covered at SGW, to reduce the frequency of changing SGW when selecting SGW as far as possible.The user contracting data that main reference obtained from HSS when MME selected PGW, the user also might report APN (Access Point Name, APN) in request PDN connection, and MME just can select PGW in view of the above.

Interface between the eNB is called X2 interface, and interactive signaling is used X2-AP message each other; Interface between MME and the eNB is called S1-MME (also being S1-C) interface, and application layer interactive signaling each other is a S1-AP message.Interface between MME and the SGW is the S11 interface, and the chain of command interactive signaling is used the GTPv2-C agreement each other, also uses the GTPv2-C agreement between SGW and the PGW.SGW and PGW can be integrated in the node.

In the E-UTRAN network, not all eNB supports RN, and promptly not all base station can be configured to DeNB.In a MME Pool (MME pond), MME that might not be all supports RN.

The deficiency of prior art is: the support situation that RN can not the aware networks side in access procedure, just can accurately not carry out follow-up start-up course yet.

Summary of the invention

The problem that the present invention solved has been to provide a kind of Non-Access Stratum procedure processing method and equipment of via node.

A kind of NAS procedure processing method of via node is provided in the embodiment of the invention, has comprised the steps:

Whether RN confirms to notify in the message RN network ready-made preparation after receiving message;

When the ready-made preparation of notice RN network, RN keeps the PDN that has set up to connect;

When not notifying the ready-made preparation of RN network, RN carries out the Detach process, discharges existing PDN and connects, and carry out the Attach process and rebulid new PDN and connect.

MME is after the initial UE message that receives the DeNB transmission, and MME is from the subscription data of HSS acquisition RN, and said initial UE message is set up RRC carrying back transmission between RN start and eNB;

MME when RN is supported in self and the RN access sub-district on DeNB, selects the SGW/PGW of DeNB as RN after definite access device is RN;

MME sends to DeNB and creates conversation request;

MME is after RN sets up default bearing and returns establishment conversational response message at DeNB; On the S1 interface, send S1-AP message to DeNB; And in this message, carried MME and issued adhering to of RN and accept message, accept the ready-made preparation of message informing RN network through adhering to.

DeNB determines whether to be chosen as the SGW/PGW of RN;

DeNB sends the ready indication of network to RN after confirming to be chosen as the SGW/PGW of RN.

A kind of via node is provided in the embodiment of the invention, has comprised:

Whether determination module is used for after RN receives message, confirm to notify in the message RN network ready-made preparation;

Processing module is used for when the ready-made preparation of notice RN network, and RN keeps the PDN that has set up to connect; When not notifying the ready-made preparation of RN network, RN carries out the Detach process, discharges existing PDN and connects, and carry out the Attach process and rebulid new PDN and connect.

A kind of mobile management entity device is provided in the embodiment of the invention, has comprised:

Receiver module is used for after the initial UE message that receives the DeNB transmission, and from the subscription data of HSS acquisition RN, said initial UE message is set up RRC carrying back transmission between RN start and DeNB;

Processing module is used for after definite access device is RN, when RN is supported in self and the RN access sub-district on DeNB, selects the SGW/PGW of DeNB as RN;

Sending module is used for sending the establishment conversation request to DeNB;

Notification module; Being used at DeNB is after RN sets up default bearing and returns establishment conversational response message; On the S1 interface, send S1-AP message to DcNB, and in this message, carried MME and issued adhering to of RN and accept message, accept the ready-made preparation of message informing RN network through adhering to.

A kind of evolution base station is provided in the embodiment of the invention, has comprised:

Determination module is used for confirming whether eNB is chosen as the SGW/PGW of RN;

Sending module is used for after confirming to be chosen as the SGW/PGW of RN, sends the ready indication of network to RN.

Beneficial effect of the present invention is following:

In the technical scheme that the embodiment of the invention provides, MME when RN is supported in self and the RN access sub-district on DeNB, selects the SGW/PGW of DeNB as RN after definite access device is RN; And the ready-made preparation of notice DeNB network.DeNB sends the ready indication of network to RN after confirming to be chosen as the SGW/PGW of RN.When the ready-made preparation of notice RN network, RN keeps the PDN that has set up to connect; When not notifying the ready-made preparation of RN network, RN carries out the Detach process, discharges existing PDN and connects, and carry out the Attach process and rebulid new PDN and connect.

By the way, can let RN whether know core net, thereby RN can select corresponding N AS process to carry out follow-up start-up course according to the indication of receiving for RN has selected appropriate nodes.Thereby, can simplify the startup flow process of RN, shorten the start-up time of RN, reduce signaling process and the bearer management that there is no need.

Description of drawings

Fig. 1 is for comprising the E-UTRAN network architecture sketch map of RN in the background technology;

Fig. 2 is the NAS procedure processing method implementing procedure sketch map of the via node of RN side in the embodiment of the invention;

Fig. 3 is the NAS procedure processing method implementing procedure sketch map of the via node of MME side in the embodiment of the invention;

Fig. 4 is the NAS procedure processing method implementing procedure sketch map of the via node of DeNB side in the embodiment of the invention;

Fig. 5 is a RN start-up course implementing procedure sketch map in the embodiment of the invention 1;

Fig. 6 sets up process implementing procedure sketch map for the dedicated bearer that DeNB in the embodiment of the invention initiates;

Fig. 7 sets up the process sketch map together for default bearing in the embodiment of the invention and dedicated bearer;

Fig. 8 is a via node structural representation in the embodiment of the invention;

Fig. 9 is a mobile management entity device structural representation in the embodiment of the invention;

Figure 10 is an evolution base station structural representation in the embodiment of the invention.

Embodiment

The inventor notices in the invention process:

In the E-UTRAN network, not all eNB supports RN, and promptly not all base station can be configured to DeNB.In a MME Pool (MME pond), MME that also might not be all supports RN.

Because RN is disposed by operator, operator is deployed in RN probably and receives the good position of DeNB signal when the network planning so, like this, when the sub-district is selected in the RN start, selects the probability of DeNB just bigger.DeNB might choose the MME that does not support RN when selecting MME for RN (still be the identity of UE this moment), also might select to support the MME of RN.If selected the former, RN set up and OAM between carrying and download finish behind the OAM configuration data, need reselect DeNB and/or support the MME of RN.But if the MME that DeNB selects supports RN, MME can select the SGW/PGW of DeNB as RN so, and sets up corresponding core net carrying.If this situation; RN just there is no need to discharge the carrying of having set up after accepting message in adhering to of receiving that MME sends, but further sets up the S1 interface and X2 interface gets final product; Like this; Just simplified the startup flow process of RN greatly, shortened the start-up time of RN, and reduced signaling process unnecessary and bearer management.

Given this, the scheme that a kind of RN selects NAS (NonAccess Stratum, Non-Access Stratum) process has been proposed in the embodiment of the invention.Through letting RN know whether core net has selected appropriate nodes for RN; Thereby RN can select corresponding N AS process carry out follow-up start-up course according to the indication of receiving, thereby has solved the problem that can not accurately carry out follow-up start-up course that causes of the support situation of aware networks side not in access procedure because of RN.Describe below in conjunction with the accompanying drawing specific embodiments of the invention.

The main thought of the technical scheme that the embodiment of the invention provides is: via node is selected the NAS process according to the network side indication of receiving.If RN is known network side for RN gets ready, then can keep the PDN that has set up to connect; Otherwise, carry out Detach (attachment removal) process, discharge existing PDN and connect, and then carry out the Attach process and rebulid new PDN and connect.

RN knows that the indication of " network side is ready " can be from MME, also can be from DeNB;

Network side is ready to be meant that the base station of the current access of RN is DeNB, and the serving MME of RN is to support RN, and MME has selected the SGW/PGW of DeNB as RN.

Concrete three's main execution content can be following:

The RN side:

After knowing that network has been selected to support the network node of RN, keep the PDN that has set up to connect;

If desired, default bearing or a small amount of dedicated bearer have been set up, initiation dedicated bearer foundation request such as current; Or wait for the dedicated bearer foundation request that network side is initiated;

The follow-up S1/X2 interface of setting up;

After knowing that network is not selected to support the network node of RN, RN carries out the Detach process, discharges existing PDN and connects, and then carry out the Attach process and rebulid new PDN and connect.

The MME side:

Know that RN passes through after the DeNB access network, select the SGW/PGW of DeNB as RN.

Through NAS message informing RN " network is ready ".

The entity that notice DeNB inserts is RN.

The DeNB side:

Know after the SGW/PGW that oneself is chosen as RN, send indication " network is ready " to RN.

Know that inserting entity is after the RN, if desired, initiates dedicated bearer to RN and sets up process;

Implement explanation below, in declarative procedure, with describing from the enforcement of RN, MME, DeNB at first respectively; Explain how to cooperate enforcement between them with instance then, but this and do not mean that the three must cooperate enforcement, in fact; When dividing, RN, MME, DeNB open when implementing; It also solves the problem of RN side, MME side, DeNB side separately, when just triplicity is used, can obtain better technique effect.

Fig. 2 is the NAS procedure processing method implementing procedure sketch map of the via node of RN side, and is as shown in the figure, can comprise the steps: in the RN side

Whether step 201, RN confirm to notify in the message RN network ready-made preparation after receiving message;

Step 202, when notice RN network ready-made preparations, RN keeps the PDN connection of having set up; When not notifying the ready-made preparation of RN network, RN carries out the Detach process, discharges existing PDN and connects, and carry out the Attach process and rebulid new PDN and connect.

In the enforcement, the message that RN receives can be that MME issues adhering to of RN and accepts message;

RN confirms whether MME accepts the ready-made preparation of message informing RN network through adhering to.

In the enforcement, the message that RN receives can be that the RRC that DeNB sends connects reallocation message, and RN confirms whether DeNB notifies the RN network ready in RRC connection reconfiguration message.

In the enforcement, can further include:

Initiate dedicated bearer and set up request;

Or, wait for the dedicated bearer foundation request that network side is initiated.

In the enforcement, RN sets up before or after the dedicated bearer, can further include:

RN is from OAM download configuration data.

Fig. 3 is the NAS procedure processing method implementing procedure sketch map of the via node of MME side, and is as shown in the figure, can comprise the steps: in the MME side

Step 301, MME are after the initial UE message that receives the DeNB transmission, and MME is from the subscription data of HSS acquisition RN, and said initial UE message is set up RRC carrying back transmission between RN start and DeNB;

Step 302, MME when RN is supported in self and the RN access sub-district on DeNB, select the SGW/PGW of DeNB as RN after definite access device is RN;

Step 303, MME send to DeNB and create conversation request;

Step 304, MME are after RN sets up default bearing and returns establishment conversational response message at DeNB; On the S1 interface, send S1-AP message to DeNB; And in this message, carried MME and issued adhering to of RN and accept message, accept the ready-made preparation of message informing RN network through adhering to.

In the enforcement, S1-AP message can be that initial context is set up request message.

In the enforcement, MME can further include when DeNB sends S1-AP message on the S1 interface:

It is RN that MME sets up the equipment that notice DeNB inserts in the request message at initial context.

In the enforcement, when MME is RN at definite access device, can be from the subscription data that HSS obtains, to learn, or, learn from other MME.

In the enforcement, accept the ready-made preparation of message informing RN network, can comprise one of following mode or its combination through adhering to:

(EPS adheres to the object information unit to EPS attach result IE in Attach Accept (adhering to acceptance) message; EPS:Evolved Packet System, evolved packet system; IE:Information Element, information unit) increase an option in order to the ready-made preparation of indication network;

EPS network feature support IE (EPS network characterization support information unit) increases an option in order to the ready-made preparation of indication network in AttachAccept message;

The GUTI that distributes for RN in the AttachAccept message (Globally Unique TemporaryIdentity, the whole world unique (user) temporary mark) is set to particular value in order to the ready-made preparation of indication network;

Carried in the Attach Accept message in Activate Default EPS BearerContext Request (the activating the default EPS bearing context request) message that MME issues RN and added indication in order to the ready-made preparation of indication network.

In the enforcement, when MME sends the establishment conversation request to DeNB, can further include:

MME indication DeNB in creating conversation request creates default bearing for RN.

In the enforcement, MME indicates DeNB through MSISDN (Mobile station internationalISDN number, travelling carriage international number) or increase IE in creating conversation request be to be that RN creates default bearing.

Fig. 4 is the NAS procedure processing method implementing procedure sketch map of the via node of DeNB side, and is as shown in the figure, can comprise the steps: in the DeNB side

Step 401, DeNB determine whether to be chosen as the SGW/PGW of RN;

Step 402, DeNB send the ready indication of network to RN after confirming to be chosen as the SGW/PGW of RN.

In the enforcement, can further include:

After confirming that inserting entity is RN, initiate dedicated bearer to RN and set up process.

In the enforcement, DeNB confirms that inserting entity is RN, can comprise:

DeNB receives the S1-AP message that MME sends on the S1 interface, it is RN that MME sets up the equipment that notice DeNB inserts in the request message at initial context.

In the enforcement, initiate dedicated bearer to RN and set up process, can comprise one of following mode:

DeNB initiates dedicated bearer to RN and sets up request process after RN downloads the OAM configuration data that finishes;

DeNB initiates dedicated bearer to RN and sets up request process after receiving the RRC connection reprovision completion message that RN returns;

DeNB initiates dedicated bearer to RN and sets up request process after receiving the indication that the download of sending to DeNB after RN downloads the OAM configuration data that finishes finishes.

In the enforcement, can further include:

DeNB receives the establishment conversation request that MME sends, and MME indication DeNB in creating conversation request creates default bearing for RN.

In the enforcement, MME can indicate DeNB through MSISDN or increase IE in creating conversation request be to be that RN creates default bearing.

In the enforcement, when RN initiation dedicated bearer is set up process, can be the dedicated bearer of also setting up requirement when setting up default bearing for RN; Or, after setting up the default bearing success, set up dedicated bearer more separately.

In the enforcement; The indication that the download of sending to DeNB behind RN download the finishing OAM configuration data finishes can be that RN passes through NAS message, after arriving MME; MME is through GTPv2-C (GPRSTunnelling Protocol for Control plane, GPRS Tunnel Protocol; GPRS:General PacketRadio Service, GPRS) message informing DeNB; Or RN is through RRC (RadioResourceControl, Radio Resource control) message informing DeNB's.

In the enforcement, send the ready indication of network, can comprise to RN:

DeNB is that RN creates the Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer, and DeNB notice RN network in RRC connection reconfiguration message is ready.

In the enforcement, after RN sends the ready indication of network, can further include one of following steps or its combination:

For part DRB (Data Radio Bearer, Data Radio Bearer) opens integrity protection, be used to transmit S1-AP and/or X2-AP message;

The part IE that RRC connects in the reconfiguration message is set to the RN specific value;

In RRC connection reconfiguration message, increase the SGW/PGW that IE indication DeNB is selected as RN.

Describe with instance below.

Embodiment 1

In the present embodiment, notify, after RN downloads OAM, initiate to set up dedicated bearer with NAS message.Fig. 5 is RN start-up course implementing procedure sketch map among the embodiment 1, and is as shown in the figure, can may further comprise the steps:

Step 501, RN start, and set up the RRC carrying between the DeNB.

Step 502, DeNB are that RN selects a MME, send initial UE message (Initial UEMessage) to it.

Carry out safety certification between step 503-step 505, network and the RN.If authentication is passed through, MME obtains the information such as subscription data of RN from HSS.

If the MME that step 506-step 507 is selected supports RN, MME judges the access entity type so, and the cell type that inserts.If know that inserting entity is RN, and Current Serving BTS is after the DeNB, selects the SGW/PGW of DeNB as RN; Then, MME sends to DeNB and creates conversation request, in DeNB, sets up default bearing for RN; DeNB returns and creates conversational response message.

In the enforcement, MME can learn the RN of the entity of access from the subscription data that HSS obtains, or knows from other MME.

In the enforcement, MME judges that the cell type that inserts is to have considered that a DeNB possibly not all sub-district be the situation of Donor cell down.Such as, to insert in the non-Donor cell of RN under DeNB, judge that cell type is reliable this moment.

Step 508, MME send initial context to DeNB and set up request message on the S1 interface, this has carried MME and has issued and accept message (Attach Accept) adhering to of RN.

MME notifies RN in Attach Accept message: the ready-made preparation of network, and the mode of notice can be:

A) EPS attach result IE increases an option in Attach Accept message, for example increases " RNattach "; Specifically can be following:

Table 1:EPS attach result IE content (thickened portion is for newly adding content)

EPS attach result value(octet 1) Bits 3 2 1 0 0 1 EPS only 0 1 0 combined EP S/IMS I attach 1 0 0 RN attach All other values are reserved. Bit 4of octet l is spare and shall be coded as zero.

B) EPS network feature support IE increases an option in AttachAccept message, for example increases " RN supported ";

C) GUTI that distributes for RN in the MME Attach Accept message is set to particular value;

D) carry Activate Default EPS BearerContext Request (the activating the default EPS bearing request) message that MME issues RN in the Attach Accept message, MME can add indication in this message.Such as, the value that the APN IE in this message (APN information unit, APN:Access Point Name, APN) is set to indicate DeNB.

In the enforcement, if base station selected MME does not support RN, or the base station that RN inserts is not DeNB, and MME can not give RN the indication of " network is ready " so.

Step 509, DeNB are that RN creates the Access Layer context, and send RRC connection reallocation message to RN, set up radio bearer.

Step 510-step 511, RN return acknowledge message to the base station, and response message is returned to MME in the base station.

Step 512, RN are from OAM download configuration data.

If RN has received the indication of " network is ready " from NAS message, RN can keep the PDN that has set up to connect after download finishes the OAM configuration data so.If desired, can initiate dedicated bearer to network side and set up request process.

If RN does not receive the indication of " network is ready ", RN adheres to network side attachment removal (Detach) afterwards again so.

After RN sets up necessary S1 interface and X2 interface, just can preparation.

Embodiment 2

In the present embodiment, notify, before RN downloads OAM, set up dedicated bearer with NAS message.

The processing of step 512 among the embodiment 1 and RN is changed order:

If RN has received the indication of " network is ready " from NAS message, RN can keep the PDN that has set up to connect so.If desired, can set up dedicated bearer to the network side request.

If RN does not receive the indication of " network is ready ", RN selects the eNB that can be used as DeNB to insert after the network side attachment removal so, adheres to again.

RN is from OAM download configuration data.Set up necessary S1 interface and X2 interface then, just can preparation.

The enforcement of other steps can reference implementation example 1.

Embodiment 3

In the present embodiment, notify, initiate to set up the process of dedicated bearer by DeNB with NAS message.

The enforcement of front can reference implementation step 501～505 of example 1.That is, the RN start, and set up the RRC carrying between the DeNB.DeNB is that RN selects a MME, sends initial UE message to it.Carry out safety certification between network and the RN.If authentication is passed through, MME obtains the information such as subscription data of RN from HSS.

If the MME that selects supports RN, MME judges the access entity type so, and the cell type that inserts.If know that inserting entity is RN, and Current Serving BTS is after the DeNB, selects the SGW/PGW of DeNB as RN; Then, MME sends to DeNB and creates conversation request, in DeNB, sets up default bearing for RN.MME indication DeNB in creating conversation request creates default bearing for RN.

MME can learn the RN of the entity of access from the subscription data that HSS obtains, or knows from other MME.

The mode of MME notice DeNB can be with special MSISDN, or increasing IE indicates RN inserting.

MME sends initial context to DeNB and sets up request message on the S1 interface, this has carried MME and has issued adhering to of RN and accept message.DeNB is that RN creates the Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer.RN returns acknowledge message to the base station, and response message is returned to MME in the base station.RN is from OAM download configuration data.The processing of this part can be referring to embodiment 1 step 508～512.

If RN has received the indication of " network is ready " from NAS message, RN keeps the PDN that has set up to connect after download finishes the OAM configuration data so.

If RN does not receive the indication of " network is ready ", RN adheres to after the network side attachment removal again so.

If DeNB has received the indication of " network is ready " from create conversation request message, so:

DeNB can initiate dedicated bearer to RN and set up request process after RN downloads the OAM configuration data that finishes, and Fig. 6 sets up process implementing procedure sketch map for the dedicated bearer that DeNB initiates, and setting up request process to RN initiation dedicated bearer can be referring to Fig. 6.

Perhaps, DeNB initiates dedicated bearer to RN and sets up request process after receiving the RRC connection reprovision completion message that RN returns.

Perhaps, after RN downloads the OAM configuration data that finishes, the indication of finishing for download of DeNB, DeNB can initiate dedicated bearer to RN and set up request process then.

Wherein, RN downloads the indication that finishes to DeNB can pass through NAS message, arrives after the MME, and MME is through GTPv2-C message informing DeNB (message among MME and the DeNB between the SGW/PGW function is used the GPTv2-C agreement); Or directly notify DeNB through RRC message.

Embodiment 4

In the present embodiment, notify with NAS message or RRC message, DeNB builds default bearing and dedicated bearer simultaneously.

The enforcement of front can reference implementation step 5011～505 of example 1.That is, the RN start, and set up the RRC carrying between the DeNB.DeNB is that RN selects a MME, sends initial UE message to it.Carry out safety certification between network and the RN.If authentication is passed through, MME obtains the information such as subscription data of RN from HSS.

If the MME that selects supports RN, MME judges the access entity type so, and the cell type that inserts.If know RN at access network, and Current Serving BTS is after the DeNB, selects the SGW/PGW of DeNB as RN; Then, MME sends to DeNB and creates conversation request, in DeNB, sets up default bearing for RN.MME indication DeNB in creating conversation request message is for RN creates default bearing, can be referring to the corresponding description of embodiment 3 during enforcement.

If DeNB has received the indication of " network is ready " from create conversation request message, DeNB also sets up the dedicated bearer of requirement for RN when setting up default bearing for RN so.Fig. 7 sets up the process sketch map together for default bearing and dedicated bearer, when setting up default bearing for RN also for RN sets up the enforcement of the dedicated bearer of requirement can be referring to Fig. 7.DeNB sends the request of carrying of creating when MME sends the establishment conversational response.

MME sends the carrying that initial context sets up request message and be used to create dedicated bearer to DeNB and sets up request message on the S1 interface.Wherein initial context is set up and has been carried MME in the request message and issue adhering to of RN and accept message.

Optional, MME also can notify RN in Attach Accept message: " the ready-made preparation of network ", the mode of notice can be referring to the enforcement of step 508 among the embodiment 1.

Optional, that MME also can set up that notice DeNB inserts in the request message at initial context is RN.The mode of notice can be: newly-increased IE indication RN is inserting, such as newly-increased be designated as " RNIndicator ";

DeNB is that RN creates the Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer.Optional, connecting in the reconfiguration message at RRC, DeNB can notify RN " network is ready ".Such as:

A) for part DRB opens integrity protection, be used to transmit S1-AP and/or X2-AP message;

B) RRC connects that some IE is set to the RN specific value in the reconfiguration message, or increases the SGW/PGW that IE indication DeNB is selected as RN.

RN returns acknowledge message to the base station then, and response message is returned to MME in the base station.RN is from OAM download configuration data.The processing of this part can be referring to embodiment 1 step 510～512.

RN has received the indication of " network is ready " from NAS and/or RRC message after, after download finishes the OAM configuration data, keep the PDN that has set up to connect so, set up necessary S1 interface and X2 interface again, just can preparation.

The difference of embodiment 4 and embodiment 1,2,3 is: DeNB knows that RN after inserting, also sets up the dedicated bearer of requirement when setting up default bearing for RN among the embodiment 4; Preceding 3 embodiment set up earlier after the default bearing success, set up dedicated bearer more separately.

Embodiment 5

In the present embodiment, notify, set up dedicated bearer, only at S1 interface notice DeNB by the RN request with RRC message.

The enforcement of front can reference implementation step 501～507 of example 1.That is, the RN start, and set up the RRC carrying between the DeNB.DeNB is that RN selects a MME, sends initial UE message to it.Carry out safety certification between network and the RN.If authentication is passed through, MME obtains the information such as subscription data of RN from HSS.If the MME that selects supports RN, MME judges the access entity type so, and the cell type that inserts.If know that inserting entity is RN, and Current Serving BTS is after the DeNB, selects the SGW/PGW of DeNB as RN; Then, MME sends to DeNB and creates conversation request, in DeNB, sets up default bearing for RN; DeNB returns and creates conversational response message.

MME sends initial context to DeNB and sets up request message on the S1 interface, that MME notifies the DeNB access in this message is RN.

In the enforcement, the mode of notice can be referring to the appropriate section among the embodiment 4.

Optional, MME also can notify RN simultaneously in Attach Accept message: the ready-made preparation of network, the mode of notice can be referring to the enforcement of step 508 among the embodiment 1.

DeNB is that RN creates the Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer.Connect in the reconfiguration message DeNB notice RN " network is ready " at RRC.The mode of notice can be referring to the appropriate section among the embodiment 4.

RN returns acknowledge message to the base station, and response message is returned to MME in the base station.

RN is from OAM download configuration data.

If RN has received the indication of " network is ready " from RRC message, RN can keep the PDN that has set up to connect after download finishes the OAM configuration data so.If desired, can initiate dedicated bearer to network side and set up request process.If RN does not receive the indication of " network is ready ", RN adheres to after the network side attachment removal again so.

RN sets up necessary S1 interface and X2 interface, just can preparation.

In the enforcement, be similar to embodiment 2, RN can put upside down order from the processing of OAM download configuration data and RN, that is:

If RN has received the indication of " network is ready " from RRC message, RN can keep the PDN that has set up to connect so.If desired, can set up dedicated bearer to the network side request.

Embodiment 6

In the present embodiment, notify with RRC message, initiate to set up the process of dedicated bearer by DeNB, it is RN that MME inserts entity at S11 interface notice DeNB.

MME sends initial context to DeNB and sets up request message on the S1 interface, this has carried MME and has issued adhering to of RN and accept message.

Optional, that MME also can set up that notice DeNB inserts in the request message at initial context is RN.The mode of notice can be referring to the appropriate section among the embodiment 5.

DeNB is that RN creates the Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer.Connect in the reconfiguration message DeNB notice RN " network is ready " at RRC.

The mode of notice can be referring to the appropriate section among the embodiment 4.

If RN has received the indication of " network is ready " from RRC message, RN keeps the PDN that has set up to connect after download finishes the OAM configuration data so.

Based on same inventive concept; A kind of via node, MME equipment, evolution base station also are provided in the embodiment of the invention; Because the principle that these equipment are dealt with problems is similar with the Non-Access Stratum procedure processing method of via node; Therefore the enforcement of these equipment can repeat part and repeat no more referring to the enforcement of method.

Fig. 8 is the via node structural representation, and is as shown in the figure, can comprise among the RN:

Whether determination module 801 is used for after RN receives message, confirm to notify in the message RN network ready-made preparation;

Processing module 802 is used for when the ready-made preparation of notice RN network, and RN keeps the PDN that has set up to connect; When not notifying the ready-made preparation of RN network, RN carries out the Detach process, discharges existing PDN and connects, and carry out the Attach process and rebulid new PDN and connect.

In the enforcement, it can be that MME issues adhering to of RN and accepts message that determination module can also be further used in the message that RN receives; Confirm whether MME accepts the ready-made preparation of message informing RN network through adhering to.

In the enforcement, it is that the RRC that DeNB sends connects reallocation message that determination module can also be further used in the message that RN receives, and confirms whether DeNB notifies the RN network ready in RRC connection reconfiguration message.

In the enforcement, can further include in the via node:

Module 803 is set up in carrying, is used to initiate dedicated bearer and sets up request; Or, wait for the dedicated bearer foundation request that network side is initiated.

In the enforcement, can further include in the via node:

Configuration module 804 is used for setting up before or after the dedicated bearer at RN, from OAM download configuration data.

Fig. 9 is the mobile management entity device structural representation, and is as shown in the figure, can comprise among the MME:

Receiver module 901 is used for after the initial UE message that receives the DeNB transmission, and from the subscription data of HSS acquisition RN, said initial UE message is set up RRC carrying back transmission between RN start and DeNB;

Processing module 902 is used for after definite access device is RN, when RN is supported in self and the RN access sub-district on DeNB, selects the SGW/PGW of DeNB as RN;

Sending module 903 is used for sending the establishment conversation request to DeNB;

Notification module 904; Being used at DeNB is after RN sets up default bearing and returns establishment conversational response message; On the S1 interface, send S1-AP message to DeNB, and in this message, carried MME and issued adhering to of RN and accept message, accept the ready-made preparation of message informing RN network through adhering to.

In the enforcement, notification module can also be further used for adopting initial context to set up request message and notify.

In the enforcement, notification module can also be further used for when DeNB sends S1-AP message on the S1 interface, and setting up the equipment that notice DeNB inserts in the request message at initial context is RN.

In the enforcement, processing module can also be further used for from the subscription data that HSS obtains, learning that access device is RN, or, be to learn that from other MME access device is RN.

In the enforcement, notification module can also be further used for accepting the ready-made preparation of message informing RN network through adhering to, and adopts one of following mode or its combination:

EPS attach result IE increases an option in order to the ready-made preparation of indication network in Attach Accept message;

EPS network feature support IE increases an option in order to the ready-made preparation of indication network in AttachAccept message;

The GUTI that distributes for RN in the Attach Accept message is set to particular value in order to the ready-made preparation of indication network;

Carried in the Attach Accept message in Activate Default EPS BearerContext Request (the activating the default EPS bearing request) message that MME issues RN and added indication in order to the ready-made preparation of indication network.

In the enforcement, sending module can also be further used for when sending the establishment conversation request to DeNB, and indication DeNB is to be that RN creates default bearing in creating conversation request.

In the enforcement, it is to be that RN creates default bearing that sending module can also be further used in creating conversation request, indicating DeNB through MSISDN or increase IE.

Figure 10 is the evolution base station structural representation, and is as shown in the figure, can comprise among the eNB:

Determination module 1001 is used for confirming whether eNB is chosen as the SGW/PGW of RN;

Sending module 1002 is used for after confirming to be chosen as the SGW/PGW of RN, sends the ready indication of network to RN.

In the enforcement, can further include among the eNB:

Module 1003 is set up in carrying, is used for after confirming that inserting entity is RN, initiating dedicated bearer to RN and setting up process.

In the enforcement, carrying is set up module and is further used for when confirming that inserting entity is RN, is to confirm through the S1-AP message that the MME that receives sends on the S1 interface, and the equipment that MME sets up notice eNB access in the request message at initial context is RN.

In the enforcement, carrying is set up module and can also be further used for adopting one of following mode when RN initiation dedicated bearer is set up process:

ENB initiates dedicated bearer to RN and sets up request process after RN downloads the OAM configuration data that finishes;

ENB initiates dedicated bearer to RN and sets up request process after receiving the RRC connection reprovision completion message that RN returns;

ENB initiates dedicated bearer to RN and sets up request process after receiving the indication that the download of sending to eNB after RN downloads the OAM configuration data that finishes finishes.

In the enforcement, can further include among the eNB:

Receiver module 1004 is used to receive the establishment conversation request that MME sends, and MME indication eNB in creating conversation request creates default bearing for RN.

In the enforcement, receiver module can also be further used for receiving MME through MSISDN or increase IE to indicate eNB be the establishment conversation request of creating default bearing for RN.

In the enforcement, carrying is set up module and can also be further used for also setting up the dedicated bearer of requirement when setting up default bearing for RN when RN initiation dedicated bearer is set up process; Or, after setting up the default bearing success, set up dedicated bearer more separately.

In the enforcement, carry and to set up module and can also be further used for receiving that to download the indication that finishes be that RN passes through NAS message, after arriving MME, MME is through GTPv2-C message informing eNB's; Or RN is through RRC message informing eNB's.

In the enforcement; Sending module can also be further used for when the indication of having got ready to RN transmission network, being that RN creates the Access Layer context, and sending RRC connection reallocation message to RN; Set up radio bearer, connect at RRC and notify the RN network ready in the reconfiguration message.

In the enforcement, can further include among the eNB: with one of lower module or its combination:

Opening module is used to part DRB and opens integrity protection, is used to transmit S1-AP and/or X2-AP message;

Module is set, is used for the part IE that RRC connects reconfiguration message and is set to the RN specific value;

Indicating module, being used for connecting reconfiguration message at RRC increases the SGW/PGW that IE indication eNB is selected as RN.

For the convenience of describing, the each several part of the above device is divided into various modules with function or the unit is described respectively.Certainly, when embodiment of the present invention, can in same or a plurality of softwares or hardware, realize the function of each module or unit.

From the above, in the technical scheme that the embodiment of the invention provides, via node is selected the NAS process according to the network side indication of receiving.If RN is known network side for RN gets ready, then can keep the PDN that has set up to connect; Otherwise, discharge existing PDN connection and rebulid new PDN connection.

Further, also provide RN according to the different NAS process of network indication selection; The mode of MME notice RN " whether network is ready "; MME notifies DeNB the mode of " whether insert entity is RN " on the S1 interface; MME notifies DeNB the mode of " whether insert entity is RN " on the S11 interface; The mode of DeNB notice RN " whether network is ready "; The execution mode of the settling time of dedicated bearer etc.

The technical scheme that the embodiment of the invention provides can let RN whether know core net for RN has selected appropriate nodes, thereby RN can select corresponding N AS process to carry out follow-up start-up course according to the indication of receiving.Thereby, can simplify the startup flow process of RN, shorten the start-up time of RN, reduce signaling process and the bearer management that there is no need.

Those skilled in the art should understand that embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of the embodiment of complete hardware embodiment, complete software implementation example or combination software and hardware aspect.And the present invention can be employed in the form that one or more computer-usable storage medium (including but not limited to magnetic disc store, CD-ROM, optical memory etc.) that wherein include computer usable program code go up the computer program of implementing.

The present invention is that reference is described according to the flow chart and/or the block diagram of method, equipment (system) and the computer program of the embodiment of the invention.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or the block diagram and/or square frame and flow chart and/or the block diagram and/or the combination of square frame.Can provide these computer program instructions to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, make the instruction of carrying out through the processor of computer or other programmable data processing device produce to be used for the device of the function that is implemented in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame appointments.

These computer program instructions also can be stored in ability vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work; Make the instruction that is stored in this computer-readable memory produce the manufacture that comprises command device, this command device is implemented in the function of appointment in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame.

These computer program instructions also can be loaded on computer or other programmable data processing device; Make on computer or other programmable devices and to carry out the sequence of operations step producing computer implemented processing, thereby the instruction of on computer or other programmable devices, carrying out is provided for being implemented in the step of the function of appointment in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame.

Although described the preferred embodiments of the present invention, in a single day those skilled in the art get the basic inventive concept could of cicada, then can make other change and modification to these embodiment.So accompanying claims is intended to be interpreted as all changes and the modification that comprises preferred embodiment and fall into the scope of the invention.

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, belong within the scope of claim of the present invention and equivalent technologies thereof if of the present invention these are revised with modification, then the present invention also is intended to comprise these changes and modification interior.

Claims

1. the Non-Access Stratum NAS procedure processing method of a via node RN is characterized in that, comprises the steps:

When the ready-made preparation of notice RN network, the grouped data network PDN that RN keeps having set up connects;

When not notifying the ready-made preparation of RN network, RN carries out attachment removal Detach process, discharges existing PDN and connects, and adhere to the Attach process and rebulid new PDN and connect.

2. the method for claim 1 is characterized in that, the message that RN receives is that Mobility Management Entity MME issues adhering to of RN and accepts message;

3. the method for claim 1 is characterized in that, the message that RN receives is that the radio resource control RRC that alms giver's evolution base station DeNB sends connects reallocation message, and RN confirms whether DeNB notifies the RN network ready in RRC connection reconfiguration message.

4. the method for claim 1 is characterized in that, further comprises:

Initiate dedicated bearer and set up request;

5. method as claimed in claim 4 is characterized in that, RN sets up before or after the dedicated bearer, further comprises:

RN is from operation and maintenance system OAM download configuration data.

6. the NAS procedure processing method of a via node is characterized in that, comprises the steps:

MME is after the initial user equipment UE message that receives the DeNB transmission, and MME is from the subscription data of home subscriber server HSS acquisition RN, and said initial UE message is set up RRC carrying back transmission between RN start and DeNB;

MME when RN is supported in self and the RN access sub-district on DeNB, selects the gateway/PDN Gateway SGW/PGW of DeNB as RN after definite access device is RN;

MME sends to DeNB and creates conversation request;

7. method as claimed in claim 6 is characterized in that, said S1-AP message is that initial context is set up request message.

8. method as claimed in claim 7 is characterized in that, MME further comprises when DeNB sends S1-AP message on the S1 interface:

9. method as claimed in claim 6 is characterized in that, when MME is RN at definite access device, is from the subscription data that HSS obtains, to learn, or, learn from other MME.

10. method as claimed in claim 6 is characterized in that, accepts the ready-made preparation of Attach Accept message informing RN network through adhering to, and comprises one of following mode or its combination:

Evolved packet system adheres to object information unit EPS attach resultIE in Attach Accept message increases an option in order to the ready-made preparation of indication network;

Evolved packet system network characterization supporter EPS networkfeature support IE increases an option in order to the ready-made preparation of indication network in Attach Accept message;

Global unique (user) temporary mark GUTI that distributes for RN in the AttachAccept message is set to particular value in order to the ready-made preparation of indication network;

Having carried activation acquiescence evolved packet system that MME issues RN in the AttachAccept message carries in the request Activate Default EPS Bearer Context Request message and adds indication in order to the ready-made preparation of indication network.

11. method as claimed in claim 6 is characterized in that, when MME sends the establishment conversation request to DeNB, further comprises:

12. method as claimed in claim 11 is characterized in that, MME indicates DeNB through travelling carriage international number MSISDN or increase information unit IE in creating conversation request be to be that RN creates default bearing.

13. the NAS procedure processing method of a via node is characterized in that, comprises the steps:

DeNB determines whether to be chosen as the SGW/PGW of RN;

14. method as claimed in claim 13 is characterized in that, further comprises:

15. method as claimed in claim 14 is characterized in that, DeNB confirms that inserting entity is RN, comprising:

16. method as claimed in claim 15 is characterized in that, initiates dedicated bearer to RN and sets up process, comprises one of following mode:

17. method as claimed in claim 14 is characterized in that, further comprises:

18. method as claimed in claim 17 is characterized in that, MME indicates DeNB through MSISDN or increase IE in creating conversation request be to be that RN creates default bearing.

19. method as claimed in claim 17 is characterized in that, when RN initiation dedicated bearer is set up process, also sets up the dedicated bearer of requirement when setting up default bearing for RN; Or, after setting up the default bearing success, set up dedicated bearer more separately.

20. method as claimed in claim 16; It is characterized in that the indication that the download of sending to DeNB behind RN download the finishing OAM configuration data finishes is that RN passes through NAS message; After arriving MME, MME is through general packet wireless service tunnel protocol GTPv2-C message informing DeNB's; Or RN is through RRC message informing DeNB's.

21. method as claimed in claim 13 is characterized in that, sends the ready indication of network to RN, comprising:

22. method as claimed in claim 13 is characterized in that, after RN sends the ready indication of network, one of further may further comprise the steps or its combination:

For partial data radio bearer DRB opens integrity protection, be used to transmit S1-AP and/or X2-AP message;

23. a via node is characterized in that, comprising:

24. via node as claimed in claim 23 is characterized in that, it is that MME issues adhering to of RN and accepts message that determination module is further used in the message that RN receives; Confirm whether MME accepts the ready-made preparation of message informing RN network through adhering to.

25. via node as claimed in claim 23 is characterized in that, it is that the RRC that DeNB sends connects reallocation message that determination module is further used in the message that RN receives, and confirms whether DeNB notifies the RN network ready in RRC connection reconfiguration message.

26. via node as claimed in claim 23 is characterized in that, further comprises:

Module is set up in carrying, is used to initiate dedicated bearer and sets up request; Or, wait for the dedicated bearer foundation request that network side is initiated.

27. via node as claimed in claim 26 is characterized in that, further comprises:

Configuration module is used for setting up before or after the dedicated bearer at RN, from OAM download configuration data.

28. a mobile management entity device is characterized in that, comprising:

Notification module; Being used at DeNB is after RN sets up default bearing and returns establishment conversational response message; On the S1 interface, send S1-AP message to DeNB, and in this message, carried MME and issued adhering to of RN and accept message, accept the ready-made preparation of message informing RN network through adhering to.

29. equipment as claimed in claim 28 is characterized in that, notification module is further used for adopting initial context to set up request message and notifies.

30. equipment as claimed in claim 29 is characterized in that, notification module is further used for when DeNB sends S1-AP message on the S1 interface, and setting up the equipment that notice DeNB inserts in the request message at initial context is RN.

31. equipment as claimed in claim 28 is characterized in that, processing module is further used for from the subscription data that HSS obtains, learning that access device is RN, or, be to learn that from other MME access device is RN.

32. equipment as claimed in claim 28 is characterized in that, notification module is further used for accepting the ready-made preparation of message informing RN network through adhering to, and adopts one of following mode or its combination:

EPS network feature support IE increases an option in order to the ready-made preparation of indication network in Attach Accept message;

Having carried MME in the Attach Accept message issues in the Activate Default EPS BearerContext Request message of RN and adds indication in order to the ready-made preparation of indication network.

33. equipment as claimed in claim 28 is characterized in that, sending module is further used for when sending the establishment conversation request to DeNB, and indication DeNB is to be that RN creates default bearing in creating conversation request.

34. equipment as claimed in claim 33 is characterized in that, it is to be that RN creates default bearing that sending module is further used in creating conversation request, indicating DeNB through MSISDN or increase IE.

35. an evolution base station is characterized in that, comprising:

36. base station as claimed in claim 35 is characterized in that, further comprises:

Module is set up in carrying, is used for after confirming that inserting entity is RN, initiating dedicated bearer to RN and setting up process.

37. base station as claimed in claim 36; It is characterized in that; Carrying is set up module and is further used for when confirming that inserting entity is RN; Be to confirm through the S1-AP message that the MME that receives sends on the S1 interface, it is RN that MME sets up the equipment that notice eNB inserts in the request message at initial context.

38. base station as claimed in claim 37 is characterized in that, carrying is set up module and is further used for adopting one of following mode when RN initiation dedicated bearer is set up process:

39. base station as claimed in claim 36 is characterized in that, further comprises:

Receiver module is used to receive the establishment conversation request that MME sends, and MME indication eNB in creating conversation request creates default bearing for RN.

40. base station as claimed in claim 39 is characterized in that, receiver module is further used for receiving MME through MSISDN or increase IE to indicate eNB be the establishment conversation request of creating default bearing for RN.

41. base station as claimed in claim 39 is characterized in that, carrying is set up module and is further used for also setting up the dedicated bearer of requirement when setting up default bearing for RN when RN initiation dedicated bearer is set up process; Or, after setting up the default bearing success, set up dedicated bearer more separately.

42. base station as claimed in claim 38 is characterized in that, carries to set up module and be further used for receiving that to download the indication that finishes be that RN passes through NAS message, after arriving MME, MME is through GTPv2-C message informing eNB's; Or RN is through RRC message informing eNB's.

43. base station as claimed in claim 35; It is characterized in that; Sending module is further used for when the indication of having got ready to RN transmission network, being that RN creates the Access Layer context, and sending RRC connection reallocation message to RN; Set up radio bearer, connect at RRC and notify the RN network ready in the reconfiguration message.

44. base station as claimed in claim 35 is characterized in that, further comprises with one of lower module or its combination: