CN102378393B

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

Info

Publication number: CN102378393B
Application number: CN201010251230.7A
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: 2014-04-16
Anticipated expiration: 2030-08-11
Also published as: CN102378393A

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 processing method of via node and equipment

Technical field

The present invention relates to mobile communication technology, particularly a kind of non-access stratum processing method of via node and equipment.

Background technology

In following mobile communication system, for example, after in 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 larger bandwidth simultaneously, unassigned bandwidth below 2GHz is little at present, and the part or all of bandwidth that B3G system needs can only be in higher frequency range, and for example 3GHz finds above.Frequency range is higher, and it is faster that radio wave propagation is decayed, and transmission range is shorter, therefore, under same overlay area, guarantee continuous covering, needs more base station, and because base station has higher cost conventionally, 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 cellular system, increase and 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 schematic diagram, as shown in the figure, LTE-A system is introduced after RN, RN is linked into core net by the donor cell (alms giver community) under DeNB (alms giver's evolution base station), there is no direct wireline interface with core net, each RN can control one or more communities.Under this framework, the interface between UE (User Equipment, subscriber equipment) and RN is called Uu mouth, and interface between RN and DeNB is called Un mouth.

In framework, RN has dual identity:

First RN has the identity of UE, and RN is similar to the start attaching process of UE while starting.RN has the SGW/PGW (Serving Gateway/PDN Gateway, gateway/packet data gateway) of oneself and controls node M ME (Mobility Management Entity, Mobility Management Entity).

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

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

Then O & M (Operation and Maintenance, operation and maintenance system) downloads to RN by node configuration information, and RN is configured.RN sets up after necessary S1 interface and X2 interface again, just can be as base station normal work.

RN only and DeNB set up an X2 interface and a S1 interface.Other base stations and core net are Yi Ge community below DeNB depending on RN, DeNB only need upgrade the X2/S1 having set up and connect: need to upgrade and add Yi Gexin community to other base stations, if the TAC of RN community is (Tracking Area Code, Tracking Area Code) be new, DeNB is to a new TAC of MME registration.

UE adheres in (Attach) process, and network is that UE selects PGW, and sets up default bearing between UE and PGW.PGW, after setting up default bearing, can initiate to set up dedicated bearer process.Dedicated bearer process of establishing can follow attaching process to complete together, also can carry out separately subsequently.UE also can initiate dedicated bearer to network and set up request in needs, and 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 UE access network, MME is that UE selects SGW and PGW.Selecting the standard of SGW is mainly the positional information according to user, also will consider the loading condition between different SGW.Overlapping covered at SGW, while selecting SGW, to reduce the frequency of changing SGW as far as possible.The main user contracting data with reference to obtaining from HSS when MME selects PGW, user also likely reports APN (Access Point Name, APN) when request PDN connects, and MME just can select PGW accordingly.

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

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

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

summary of the invention

Problem solved by the invention has been to provide a kind of non-access stratum processing method and equipment of via node.

The NAS procedure processing method that a kind of via node is provided in the embodiment of the present invention, comprises the steps:

RN is receiving after message, determines in message, whether to notify the ready-made preparation of RN network;

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

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

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

Determination module, for receiving after message at RN, determines in message, whether to notify the ready-made preparation of RN network;

Processing module, for when notifying the ready-made preparation of RN network, RN keeps the PDN having set up to connect; When not notifying the ready-made preparation of RN network, RN carries out Detach process, discharges existing PDN and connects, and carry out Attach process and re-establish new PDN and connect.

Beneficial effect of the present invention is as follows:

In the technical scheme providing in the embodiment of the present invention, MME, after definite access device is RN, when RN is supported in self and the RN access community on DeNB, selects the SGW/PGW of DeNB as RN; And notify the ready-made preparation of DeNB network.DeNB is chosen as after the SGW/PGW of RN determining, to RN, sends ready indication of network.When the ready-made preparation of notice RN network, RN keeps the PDN having set up to connect; When not notifying the ready-made preparation of RN network, RN carries out Detach process, discharges existing PDN and connects, and carry out Attach process and re-establish new PDN and connect.

By the way, can allow RN know that whether core net is for RN has selected suitable node, thereby RN can select corresponding NAS 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.

Fig. 1 is the E-UTRAN network architecture schematic diagram that comprises RN in background technology;

Fig. 2 is the NAS procedure processing method implementing procedure schematic diagram of the via node of RN side in the embodiment of the present invention;

Fig. 3 is the NAS procedure processing method implementing procedure schematic diagram of the via node of MME side in the embodiment of the present invention;

Fig. 4 is the NAS procedure processing method implementing procedure schematic diagram of the via node of DeNB side in the embodiment of the present invention;

Fig. 5 is RN start-up course implementing procedure schematic diagram in the embodiment of the present invention 1;

Fig. 6 is the dedicated bearer process of establishing implementing procedure schematic diagram that in the embodiment of the present invention, DeNB initiates;

Fig. 7 is default bearing process of establishing schematic diagram together with dedicated bearer in the embodiment of the present invention;

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

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

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

Inventor notices in invention process:

In E-UTRAN network, not all eNB supports RN, and 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, when the network planning, is probably deployed in RN and receives the good position of DeNB signal so, like this, when community is selected in RN start, selects the probability of DeNB just larger.DeNB, being, when RN (now or UE identity) selects MME, likely to choose the MME that does not support RN, has also likely selected to support the MME of RN.If selected the former, RN is setting up the carrying between OAM and is downloading after complete OAM configuration data, need to reselect the MME of DeNB and/or support RN.But if the MME that DeNB selects supports RN, MME can select the SGW/PGW of DeNB as RN so, and set up corresponding core net carrying.If this is the case, RN accepts after message receiving adhering to that MME sends, just there is no need to discharge the carrying of having set up, but further set up S1 interface and X2 interface, like this, the startup flow process of just greatly having simplified RN, has shortened the start-up time of RN, and has reduced signaling process unnecessary and bearer management.

Given this, a kind of scheme of RN selection NAS (NonAccess Stratum, Non-Access Stratum) process has been proposed in the embodiment of the present invention.By allowing RN know that whether core net is for RN has selected suitable node, thereby RN can select corresponding NAS process to carry out follow-up start-up course according to the indication of receiving, thereby solved the problem that can not accurately carry out follow-up start-up course that the support situation of aware networks side does not cause in access procedure because of RN.Below in conjunction with accompanying drawing, the specific embodiment of the present invention is described.

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

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

accompanying drawing explanation

The base station of the current access of the ready RN of referring to of network side 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 as follows:

RN side:

Know that network selected to support after the network node of RN, keep the PDN having set up to connect;

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

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

Know that network do not select to support that, after the network node of RN, RN carries out Detach process, discharge existing PDN and connect, and then carry out Attach process and re-establish new PDN and connect.

MME side:

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

By NAS message informing RN " network is ready ".

embodiment

The entity of notice DeNB access is RN.

DeNB side:

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

Know that access entity is after RN, if needed, to RN, initiate dedicated bearer process of establishing;

Carry out implementation below, in declarative procedure, to from the enforcement of RN, MME, DeNB, describe first respectively, then with example, illustrate between them, how to coordinate enforcement, but this and do not mean that three must coordinate enforcement, in fact, when RN, MME, DeNB divide out enforcement, 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 schematic diagram of the via node of RN side, as shown in the figure, in RN side, can comprise the steps:

Step 201, RN are receiving after message, determine in message, whether to notify the ready-made preparation of RN network;

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 Detach process, discharges existing PDN and connects, and carry out Attach process and re-establish new PDN and connect.

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

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

In enforcement, the message that RN receives can be that the RRC that DeNB sends connects reallocation message, and RN determines whether DeNB connects in reconfiguration message and notify RN network ready at RRC.

In 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 enforcement, RN sets up before or after dedicated bearer, can further include:

RN is from OAM download configuration data.

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

Step 301, MME are receiving after the initial UE message of DeNB transmission, and MME obtains the subscription data of RN from HSS, the transmission after setting up RRC carrying between RN start and DeNB of described initial UE message;

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

Step 303, MME send to DeNB the session request that creates;

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

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

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

It is RN that MME sets up at initial context the equipment of notifying DeNB to access in request message.

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

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

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

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

The GUTI distributing for RN in Attach Accept message (Globally Unique Temporary Identity, the whole world unique (user) temporary mark) is set to particular value in order to ready-made preparation of indication network;

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

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

It is to be that RN creates default bearing that MME indicates DeNB in establishment session request.

In enforcement, it is to be that RN creates default bearing that MME indicates DeNB by MSISDN (Mobile station international ISDN number, travelling carriage international number) or increase IE in establishment session request.

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

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

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

In enforcement, can further include:

After determining that access entity is RN, to RN, initiate dedicated bearer process of establishing.

In enforcement, DeNB determines that access entity is RN, can comprise:

DeNB receives the S1-AP message that MME sends on S1 interface, and it is RN that MME sets up at initial context the equipment of notifying DeNB to access in request message.

In enforcement, to RN, initiate dedicated bearer process of establishing, can comprise one of following mode:

DeNB downloads after complete OAM configuration data at RN, initiates dedicated bearer set up request process to RN;

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

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

In enforcement, can further include:

DeNB receives the establishment session request that MME sends, and it is to be that RN creates default bearing that MME indicates DeNB in establishment session request.

In enforcement, it is to be that RN creates default bearing that MME can indicate DeNB by MSISDN or increase IE in establishment session request.

In enforcement, while initiating dedicated bearer process of establishing to RN, can be the dedicated bearer of also setting up requirement when setting up default bearing for RN; Or, after setting up default bearing success, then set up separately dedicated bearer.

In enforcement, RN downloads the complete indication of download sending to DeNB after complete OAM configuration data, can be that RN passes through NAS message, arrives after MME, MME is by GTPv2-C (GPRS Tunnelling Protocol for Control plane, GPRS Tunnel Protocol; GPRS:General Packet Radio Service, GPRS) message informing DeNB; Or RN is by RRC (Radio Resource Control, Radio Resource control) message informing DeNB's.

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

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

In enforcement, to RN, send after 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, for transmitting S1-AP and/or X2-AP message;

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

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

With example, describe below.

Embodiment 1

In the present embodiment, by NAS message, notify, after RN downloads OAM, initiate to set up dedicated bearer.Fig. 5 is RN start-up course implementing procedure schematic diagram in embodiment 1, as shown in the figure, can comprise the following steps:

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

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

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

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

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

In enforcement, the cell type of MME judgement access is to have considered under a DeNB not all community to be all the situation of Donor cell.Such as, in the non-Donor cell of RN under DeNB, access, now judge that cell type is reliable.

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

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

A) in Attach Accept message, EPS attach result IE increases an option, for example, increase " RN attach "; Specifically can be as follows:

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) in AttachAccept message, EPS network feature support IE increases an option, for example, increase " RN supported ";

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

D) in Attach Accept message, carry Activate Default EPS BearerContext Request (the activating default EPS bearing request) message that MME issues RN, 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 enforcement, if base station selected MME does not support RN, or the base station of RN access is not DeNB, and MME can not give the RN indication of " network is ready " so.

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

Step 510-step 511, RN return to acknowledge message to base station, and response message is returned to MME in 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 is downloading after complete OAM configuration data so, can keep the PDN having set up to connect.If need, can initiate dedicated bearer to network side and set up request process.

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

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

Embodiment 2

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

The processing of step 512 and RN in embodiment 1 is changed to order once:

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

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

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

The enforcement of other steps can reference example 1.

Embodiment 3

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

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

If the MME selecting supports RN, MME judgement access entity type, and the cell type of access so.If know that access entity is RN, and Current Serving BTS is after DeNB, selects the SGW/PGW of DeNB as RN; Then, MME sends and creates session request to DeNB, in DeNB for RN sets up default bearing.It is to be that RN creates default bearing that MME indicates DeNB in establishment session request.

The subscription data that MME can obtain from HSS, learn the RN of the entity of access, or know from other MME.

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

MME sends initial context to DeNB and sets up request message on S1 interface, and this has carried MME and has issued adhering to of RN and accept message.DeNB is that RN creates Access Layer context, and sends RRC connection reallocation message to RN, sets up radio bearer.RN returns to acknowledge message to base station, and response message is returned to MME in 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 is downloading after complete OAM configuration data so, keeps the PDN having set up to connect.

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

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

DeNB downloads after complete OAM configuration data at RN, can initiate dedicated bearer to RN and set up request process, and Fig. 6 is the dedicated bearer process of establishing implementing procedure schematic diagram that DeNB initiates, and to RN initiation dedicated bearer, setting up request process can be referring to Fig. 6.

Or DeNB is receiving that RRC that RN returns connects after reprovision completes message, initiates dedicated bearer to RN and sets up request process.

Or RN downloads after complete OAM configuration data, give DeNB mono-and download complete indication, then DeNB can initiate dedicated bearer to RN and set up request process.

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

Embodiment 4

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

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

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

If the indication that DeNB has received " network is ready " from create conversation request message, DeNB also sets up the dedicated bearer of requirement when setting up default bearing for RN for RN so.Fig. 7 is default bearing process of establishing schematic diagram together with 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 carrying request that creates when MME sends establishment conversational response.

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

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

Optionally, also can to set up what in request message, notify DeNB access at initial context be RN to MME.The mode of notice can be: newly-increased IE indication RN is in access, such as newly-increased be designated as " RNIndicator ";

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

A) for part DRB opens integrity protection, for transmitting S1-AP and/or X2-AP message;

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

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

RN received after the indication of " network is ready " from NAS and/or RRC message, downloading after complete OAM configuration data so, keeps the PDN having set up to connect, then sets up necessary S1 interface and X2 interface, just can preparation.

The difference of embodiment 4 and embodiment 1,2,3 is: in embodiment 4, DeNB knows that RN, after access, also sets up the dedicated bearer of requirement when setting up default bearing for RN; Front 3 embodiment be first set up default bearing success after, then set up separately dedicated bearer.

Embodiment 5

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

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

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

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

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

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

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

RN is from OAM download configuration data.

If RN has received the indication of " network is ready " from RRC message, RN is downloading after complete OAM configuration data so, can keep the PDN having set up to connect.If need, can initiate dedicated bearer to network side and set up request process.If RN does not receive the indication of " network is ready ", RN re-starts and adheres to after network side attachment removal so.

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

In 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 having set up to connect so.If need, can set up dedicated bearer to network side request.

Embodiment 6

In the present embodiment, by RRC message, notify, initiated to set up the process of dedicated bearer by DeNB, MME is RN at S11 interface notice DeNB access entity.

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

Optionally, also can to set up what in request message, notify DeNB access at initial context be RN to MME.The mode of notice can be referring to the appropriate section in embodiment 5.

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

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

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

Based on same inventive concept, a kind of via node, MME equipment, evolution base station are also provided in the embodiment of the present invention, because the principle that these equipment are dealt with problems is similar to the non-access stratum processing method of via node, therefore the enforcement of these equipment can be referring to the enforcement of method, repeats part and repeat no more.

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

Determination module 801, for receiving after message at RN, determines in message, whether to notify the ready-made preparation of RN network;

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

In enforcement, the message that determination module can also be further used for receiving at RN can be that MME issues adhering to of RN and accepts message; Determine whether MME accepts the ready-made preparation of message informing RN network by adhering to.

In enforcement, the message that determination module can also be further used for receiving at RN is that the RRC that DeNB sends connects reallocation message, determines whether DeNB connects in reconfiguration message and notify RN network ready at RRC.

In enforcement, in via node, can further include:

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

In enforcement, in via node, can further include:

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

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

Receiver module 901, for receiving after the initial UE message of DeNB transmission, obtains the subscription data of RN from HSS, the transmission after setting up RRC carrying between RN start and DeNB of described initial UE message;

Processing module 902, after being RN at definite access device, when RN is supported in self and the RN access community on DeNB, selects the SGW/PGW of DeNB as RN;

Sending module 903, for sending the session request that creates to DeNB;

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

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

In enforcement, notification module can also be further used for when sending S1-AP message to DeNB on S1 interface, and at initial context, setting up the equipment of notifying DeNB to access in request message is RN.

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

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

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

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

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

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

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

In enforcement, it is to be that RN creates default bearing that sending module can also be further used for by MSISDN or increase IE, indicating DeNB in establishment session request.

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

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

Sending module 1002, for being chosen as after the SGW/PGW of RN determining, sends ready indication of network to RN.

In enforcement, in eNB, can further include:

Module 1003 is set up in carrying, for after determining that access entity is RN, to RN, initiates dedicated bearer process of establishing.

In enforcement, carrying is set up module and is further used for when determining that access entity is RN, is that the S1-AP message that the MME by receiving sends on S1 interface is determined, it is RN that MME sets up at initial context the equipment of notifying eNB to access in request message.

One of in enforcement, carrying is set up module and can also be further used for when initiating dedicated bearer process of establishing to RN, in the following ways:

ENB downloads after complete OAM configuration data at RN, initiates dedicated bearer set up request process to RN;

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

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

In enforcement, in eNB, can further include:

Receiver module 1004, the establishment session request sending for receiving MME, it is to be that RN creates default bearing that MME indicates eNB in establishment session request.

In enforcement, receiver module can also be further used for receiving MME by MSISDN or increase IE that to indicate eNB be the establishment session request that creates default bearing for RN.

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

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

In enforcement, sending module can also be further used for when sending ready indication of network to RN, is that RN creates Access Layer context, and to RN, sends RRC and connect reallocation message, set up radio bearer, at RRC, connect in reconfiguration message and notify RN network ready.

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

Opening module, is used to part DRB to open integrity protection, for transmitting S1-AP and/or X2-AP message;

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

Indicating module, indicates eNB to be selected as the SGW/PGW of RN for increasing IE in RRC connection reconfiguration message.

For convenience of description, the each several part of the above device is divided into various modules with function or unit is described respectively.Certainly, when enforcement is of the present invention, the function of each module or unit can be realized in same or multiple software or hardware.

From the above, in the technical scheme providing in the embodiment of the present invention, via node is selected NAS process according to the network side indication of receiving.If RN knows that network side is for RN gets ready, can keep the PDN having set up to connect; Otherwise, discharge existing PDN and connect and re-establish new PDN and connect.

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 the DeNB mode of " whether access entity is RN " on S1 interface; MME notifies the DeNB mode of " whether access entity is RN " on 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 present invention provides can allow RN know that whether core net is for RN has selected suitable node, thereby RN can select corresponding NAS 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, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt complete hardware implementation example, completely implement software example or the form in conjunction with the embodiment of software and hardware aspect.And the present invention can adopt the form at one or more upper computer programs of implementing of computer-usable storage medium (including but not limited to magnetic disc store, CD-ROM, optical memory etc.) that wherein include computer usable program code.

The present invention is with reference to describing according to flow chart and/or the block diagram of the method for the embodiment of the present invention, equipment (system) and computer program.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or block diagram and/or square frame and flow chart and/or 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, the instruction that makes to carry out by the processor of computer or other programmable data processing device produces the device for realizing the function of specifying at flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.

These computer program instructions also can be stored in energy vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work, the instruction that makes to be stored in this computer-readable memory produces the manufacture that comprises command device, and this command device is realized the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame.

These computer program instructions also can be loaded in computer or other programmable data processing device, make to carry out sequence of operations step to produce computer implemented processing on computer or other programmable devices, thereby the instruction of carrying out is provided for realizing the step of the function of specifying in flow process of flow chart or multiple flow process and/or square frame of block diagram or multiple square frame on computer or other programmable devices.

Although described the preferred embodiments of the present invention, once those skilled in the art obtain the basic creative concept of cicada, can make other change and modification to these embodiment.So claims are intended to be interpreted as comprising preferred embodiment and fall into all changes and the modification of the scope of the invention.

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

Claims

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

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

When not notifying the ready-made preparation of RN network, RN carries out attachment removal Detach process, discharging existing PDN connects, and adhere to Attach process and re-establish new PDN and connect, wherein, the ready-made preparation of described network refers to that the base station of the current access of RN is alms giver's evolution base station DeNB, and the service mobility management entity MME of RN supports RN's.

2. the method for claim 1, is characterized in that, the message that RN receives is that 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 DeNB sends connects reallocation message, and RN determines whether DeNB connects in reconfiguration message and notify RN network ready at RRC.

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 dedicated bearer, further comprises:

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

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

Processing module, for when notifying the ready-made preparation of RN network, RN keeps the PDN having set up to connect; When not notifying the ready-made preparation of RN network, RN carries out Detach process, discharging existing PDN connects, and carry out Attach process and re-establish new PDN and connect, wherein, the ready-made preparation of described network refers to that the base station of the current access of RN is alms giver's evolution base station DeNB, and the service mobility management entity MME of RN supports RN's.

7. via node as claimed in claim 6, is characterized in that, the message that determination module is further used for receiving at RN is that MME issues adhering to of RN and accepts message; Determine whether MME accepts the ready-made preparation of message informing RN network by adhering to.

8. via node as claimed in claim 6, is characterized in that, the message that determination module is further used for receiving at RN is that the RRC that DeNB sends connects reallocation message, determines whether DeNB connects in reconfiguration message and notify RN network ready at RRC.

9. via node as claimed in claim 6, is characterized in that, further comprises:

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

10. via node as claimed in claim 9, is characterized in that, further comprises:

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