Gateway selection method and device

Abstract

The present invention relates to the technical field of wireless communications. Disclosed are a gateway selection method and device, which are used to solve the problem of how to select a packet data gateway (PGW) for a mobile relay node (RN). In the present invention, a mobility management entity (MME) receives an initial UE message carrying identity indication information of the RN and sent by a donor base station DeNB; acquiring subscription data of the RN from a home subscriber server (HSS); the MME determining, according to the identity indication information and/or subscription data of the RN, whether the RN is a mobile RN, and if the determination is yes, selecting a PGW located in a core network as the PGW of the RN. By means of the present invention, the problem of how to select the PGW for the mobile RN is solved.

Claims

1. A method of selecting a gateway, comprising: a Mobility Management Entity, MME, receiving an Initial UE message carrying identity indication information of a Relay Node, RN, sent from a Donor evolved Node B, DeNB, and acquiring subscription data of the RN from a Home Subscriber Server, HSS; and the MME determining whether the RN is a mobile RN according to the identity indication information and/or the subscription data of the RN, and selecting a Packet data Gateway, PGW, located in a core network as the PGW of the RN upon determining that the RN is a mobile RN.

2. The method of claim 1, wherein the MME determining whether the RN is a mobile RN according to the identity indication information of the RN comprises: the MME judging whether the identity indication information of the RN indicates that the RN is a mobile RN, and if so, then determining that the RN is a mobile RN.

3. The method of claim 1, wherein the MME determining whether the RN is a mobile RN according to the identity indication information and the subscription data of the RN comprises: the MME judging whether the identity indication information of the RN indicates that the RN is a mobile RN and whether there is mobile RN indication information in the subscription data, and if both results of the judging are positive, then determining that the RN is a mobile RN.

4. The method of claim 1, wherein the MME determining whether the RN is a mobile RN according to the subscription data of the RN comprises: the MME judging whether there is mobile RN indication information in the subscription data, and if so, then determining that the RN is a mobile RN.

5. The method of claim 1, wherein the selecting a PGW of a core network as a PGW of the RN comprises: the MME selecting a PGW of a core network as the PGW of the RN according to an Access Point Name, APN, in the subscription data or local pre-configured information or an APN reported from the RN.

6. The method of claim 5, wherein the selecting a PGW of a core network as the PGW of the RN according to an APN in the subscription data comprises: when there are two APNs in the subscription data, the MME selecting one with a specific flag from the two APNs, inquiring a Domain Name System, DNS, server for PGWs according to the selected APN and selecting one of the PGWs as the PGW of the RN, wherein the specific flag indicates that the APN with the flag is used to select PGWs enabling an RN to operate normally as an evolved Node B; or when there are two APNs in the subscription data, the MME selecting one without a specific flag from the two APNs, inquiring a DNS server for PGWs according to the selected APN and selecting one of the PGWs as the PGW of the RN, wherein the specific flag indicates that the APN with the flag is used to select PGWs in connection with an OAM; or when there is one APN in the subscription data, the MME inquiring a DNS server for PGWs according to the APN and selecting one of the PGWs as the PGW of the RN.

7. The method of claim 5, wherein the selecting a PGW of a core network as the PGW of the RN according to the local pre-configured information comprises: when there is an APN of PGWs in the local pre-configured information, the MME inquiring a DNS server for the PGWs according to the APN and selecting one of the PGWs as the PGW of the RN; or when there an IP address of a PGW in the local pre-configured information, the MME selecting the PGW with the IP address as the PGW of the RN.

8. A method of indicating an identity, comprising: a mobile Relay Node, RN, sending to a Donor evolved Node B, DeNB, identity indication information indicating itself as an RN or a mobile RN in the course of establishing a Radio Resource Control, RRC, connection with the DeNB during second phase, so that a Mobility Management Entity, MME, receives an Initial UE message carrying identity indication information of the RN sent from the DeNB and acquires subscription data of the RN from a Home Subscriber Server, HSS; and determines whether the RN is a mobile RN according to the identity indication information and/or the subscription data of the RN, and selects a Packet data Gateway, PGW, located in a core network as the PGW of the RN upon determining that the RN is a mobile RN.

9. The method of claim 8, wherein before the mobile RN establishes the RRC connection with the DeNB, the method further comprises: the mobile RN downloading from an Operation and Maintenance, OAM, system, an Access Point Name, APN, referring to PGWs enabling an RN to operate normally as an evolved Node B; or the mobile RN acquiring a locally preconfigured APN referring to PGWs enabling an RN to operate normally as an evolved Node B; and the mobile RN sending the APN to the DeNB in a Non Access Stratum, NAS, message while sending the identity indication information indicating itself as an RN or a mobile RN to the DeNB.

10. A method of forwarding an identity indicator, comprising: a Donor evolved Node B, DeNB, receiving identity indication information, sent from a mobile Relay Node, RN, indicating it as an RN or a mobile RN in the course of establishing a Radio Resource Control, RRC, connection with the mobile RN; and the DeNB sending an Initial UE message, carrying the identity indication information, to a Mobility Management Entity, MME, so that the MME receives the Initial UE message and acquires subscription data of the RN from a Home Subscriber Server, HSS; and determines whether the RN is a mobile RN according to the identity indication information and/or the subscription data of the RN, and selects a Packet data Gateway, PGW, located in a core network as the PGW of the RN upon determining that the RN is a mobile RN.

11. The method of claim 10, further comprising: the DeNB receiving an NAS message, carrying an APN, sent from the mobile RN while receiving the identity indication information sent from the mobile RN; and wherein the Initial UE message further carries the NAS message carrying the APN.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a structural diagram of an E-UTRAN network including an RN in the prior art;

(2) FIG. 2 is a node relationship diagram for a mobile RN in the prior art;

(3) FIG. 3 is a schematic flow chart of a method according to an embodiment of the invention;

(4) FIG. 4 is a schematic flow chart of another method according to an embodiment of the invention;

(5) FIG. 5 is a schematic flow chart of a further method according to an embodiment of the invention;

(6) FIG. 6 is a schematic flow chart of still another method according to an embodiment of the invention;

(7) FIG. 7A is a schematic flow chart of a first embodiment of the invention;

(8) FIG. 7B is a schematic flow chart of a second embodiment of the invention;

(9) FIG. 7C is a schematic flow chart of a third embodiment of the invention;

(10) FIG. 7D is a schematic flow chart of a fourth embodiment of the invention;

(11) FIG. 7E is a schematic flow chart of a fifth embodiment of the invention;

(12) FIG. 7F is a schematic flow chart of a sixth embodiment of the invention;

(13) FIG. 8 is a schematic structural diagram of an apparatus according to an embodiment of the invention;

(14) FIG. 9 is a schematic structural diagram of another apparatus according to an embodiment of the invention;

(15) FIG. 10 is a schematic structural diagram of a further apparatus according to an embodiment of the invention;

(16) FIG. 11 is a schematic structural diagram of still another apparatus according to an embodiment of the invention.

DETAILED DESCRIPTION

(17) In order to address the issue of how to select a PGW for a mobile RN at the network side, embodiments of the invention provides for a mobile RN a method of indicating an identity, provides for a DeNB a method of forwarding an identity, provides for an HSS a method of sending subscription data and provides for an MME a method of selecting a gateway, which will be described below respectively.

(18) Referring to FIG. 3, a method of indicating an identity according to an embodiment of the invention includes the following steps:

(19) Step 30: A mobile RN enters a second phase of startup; and

(20) Step 31: The mobile RN establishes an RRC connection with a DeNB; and sends to the DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing the RRC connection.

(21) In the step 31, the mobile RN can send to the DeNB the identity indication information indicating the mobile RN as an RN or a mobile RN in an RRC Setup Complete message, that is, the identity indication information is carried in the RRC Setup Complete message.

(22) Preferably after the mobile RN establishes the RRC connection with the DeNB, the mobile RN can download from an Operation and Maintenance (OAM) system an APN referring to PGWs enabling an RN to operate normally as an evolved Node B; and can a locally preconfigured APN referring to PGWs enabling an RN to operate normally as an evolved Node B. Correspondingly the mobile RN sends the APN to the DeNB while the mobile RN sending the identity indication information indicating itself as an RN or a mobile RN to the DeNB. Specifically the mobile RN sends the APN to the DeNB in a Non Access Stratum (NAS) message in the RRC Setup Complete message, that is, the APN is carried in the NAS message in the RRC Setup Complete message.

(23) Referring to FIG. 4, a method of forwarding an identity indicator according to an embodiment of the invention includes the following steps:

(24) Step 40: A DeNB receives identity indication information, sent from a mobile RN, indicating itself as an RN or a mobile RN in the course of establishing an RRC connection with the mobile RN; and

(25) Step 41: The DeNB sends an Initial UE message, carrying the identity indication information, to an MME.

(26) In the step 40, the DeNB can receive the identity indication information sent from the mobile RN in an RRC Setup Complete message, that is, the identity indication information is carried in the RRC Setup Complete message.

(27) Preferably the DeNB also receive an NAS message, carrying an APN, sent from the mobile RN along with the identity indication information sent from the mobile RN; and correspondingly the NAS message is carried in the Initial UE message.

(28) Referring to FIG. 5, a method of sending subscription data according to an embodiment of the invention includes the following steps:

(29) Step 50: An HSS receives a Locate Update Request sent from an MME; and

(30) Step 51: The HSS returns subscription data of a mobile RN to the MME, where the subscription data includes mobile RN indication information and/or an APN referring to PGWs enabling an RN to operate normally as an evolved Node B.

(31) In the step 51, the subscription data can further include an APN referring to PGWs for connection with an OAM, and then the APN referring to PGWs enabling an RN to operate normally as an evolved Node B is provided with a specific flag indicating that the APN with the flag is used to select PGWs enabling an RN to operate normally as an evolved Node B. Alternatively the APN referring to PGWs for connection with an OAM is provided with a specific flag indicating that the APN with the flag is used to select PGWs in connection with an OAM.

(32) As illustrated in FIG. 6, a method of selecting a gateway according to an embodiment of the invention includes the following steps:

(33) Step 60: An MME receives an Initial UE message, sent from a DeNB, carrying identity indication information of an RN;

(34) Step 61: The MME acquires subscription data of the RN from an HSS;

(35) Step 62: The MME determines whether the RN is a mobile RN from the identity indication information and/or the subscription data of the RN; and

(36) Step 63: The MME selects a PGW located in a core network as a PGW of the RN upon determining that the RN is a mobile RN.

(37) In the step 62, the MME can determine whether the RN is a mobile RN from the identity indication information of the RN particularly as follows:

(38) the MME judges whether the identity indication information of the RN indicates that the RN is a mobile RN, and if so, then the MME judges that the RN is a mobile RN; otherwise, the MME determines that the RN is a fixed RN and selects a PGW and an SGW for the fixed RN as in the prior art when the RN is a fixed RN.

(39) In the step 62, the MME can determine whether the RN is a mobile RN from the identity indication information and the subscription data of the RN particularly as follows:

(40) The MME judges whether the identity indication information of the RN indicates that the RN is a mobile RN and whether there is mobile RN indication information in the subscription data, and if both results of the judging are positive, then the MME judges that the RN is a mobile RN; otherwise, the MME determines that the RN is a fixed RN and selects a PGW and an SGW for the fixed RN as in the prior art when the RN is a fixed RN.

(41) In the step 62, the MME can determine whether the RN is a mobile RN from the subscription data of the RN particularly as follows:

(42) The MME judges whether there is mobile RN indication information in the subscription data, and if so, then the MME judges that the RN is a mobile RN; otherwise, the MME determines that the RN is a fixed RN.

(43) In the step 63, the MME can select a PGW of a core network as a PGW of the RN particularly as follows:

(44) the MME selects a PGW of a core network as a PGW of the RN according to an APN in the subscription data or local pre-configuration information or an APN reported from the RN.

(45) Specifically the MME can select a PGW of a core network as a PGW of the RN according to an APN in the subscription data particularly as follows:

(46) When there are two APNs in the subscription data, the MME selects one with a specific flag from the two APNs, inquires a Domain Name System (DNS) server for information about PGWs according to the selected APN and selects one of the found PGWs as the PGW of the RN, where the specific flag indicates that the APN with the flag is used to select PGWs enabling an RN to operate normally as an evolved Node B; or

(47) When there are two APNs in the subscription data, the MME selects one without a specific flag from the two APNs, inquires a DNS server for PGWs according to the selected APN and selects one of the found PGWs as the PGW of the RN, where the specific flag indicates that the APN with the flag is used to select PGWs in connection with an OAM; or

(48) When there is one APN in the subscription data, the MME inquires a DNS server for information about PGWs according to the APN and selects one of the found PGWs as a PGW of the RN.

(49) The MME can select a PGW of a core network as a PGW of the RN according to the local pre-configuration information particularly as follows:

(50) When there is an APN referring to PGWs enabling an RN to operate normally as an evolved Node B in the local pre-configuration information, the MME inquires a DNS server for the PGWs according to the APN and selects one of the PGWs as the PGW of the RN; or

(51) When there an IP address of a PGW enabling an RN to operate normally as an evolved Node B in the local pre-configuration information, the MME selects the PGW with the IP address as the PGW of the RN.

(52) The MME can select a PGW of a core network as a PGW of the RN according to an APN reported from the RN particularly as follows:

(53) when the APN reported from the RN is carried in an NAS message in the Initial UE message, the MME acquires the APN in the NAS message, inquires a DNS server for information about PGWs according to the APN and selects one of the found PGWs as a PGW of the RN.

(54) Preferably the MME can further select an SGW at a shorter distance and lightly loaded for the RN according to the geographical location where the RN currently resides and load conditions of respective SGWs upon determining that the RN is a mobile RN.

(55) The invention will be described below in connection with particular embodiments thereof:

First Embodiment

(56) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to subscription data and selects a PGW according to the subscription data, and as illustrated in FIG. 7A:

(57) Step 1: A mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(58) When the mobile RN notifies the DeNB that the mobile RN is a mobile RN, the identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message.

(59) When the mobile RN notifies the DeNB that the mobile RN is an RN, RN identity indication information carried in an existing RRC Connection Setup Complete message can be reused.

(60) Step 2: The DeNB sends the identity indication information to an MME in an Initial UE message upon reception of the identity indication information in the course of establishing the RRC connection.

(61) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is mobile RN indication information in the subscription data; and the subscription data further includes two APNs: one of the APNs is used to select PGWs in connection with an OAM; and the other APN is used to select PGWs enabling an RN to operate normally as an evolved Node B; or the subscription data includes one APN, and a PGW corresponding to the APN can be both a PGW enabling an RN to operate normally as an evolved Node B and a PGW enabling an RN to access an OAM.

(62) When there are two APNs in the subscription data, the APN used to select a PGW enabling an RN to operate normally as an evolved Node B is provided with a specific flag indicating that the APN is used to select PGWs enabling an RN to operate normally as an evolved Node B; or the APN used to select a PGW for connection with an OAM is provided with a specific flag indicating that the APN with the flag is used to select PGWs in connection with an OAM.

(63) Step 4: The MME knows that the current RN is a mobile RN from the mobile RN indication information in the subscription data and selects a PGW for the mobile RN according to the APN with or without the specific flag in the subscription data (i.e., the APN used to select a PGW enabling an RN to operate normally as an evolved Node B). The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(64) In this step, if the MME receives an IP address of a PGW reported from the DeNB, then the MME ignores the IP address.

(65) Step 5: The MME accepts an Attach request of the mobile RN and sends an S1 Context Setup Request to the DeNB.

(66) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

Second Embodiment

(67) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to identity indication information sent from the mobile RN and selects a PGW according to subscription data, and as illustrated in FIG. 7B:

(68) Step 1: A mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(69) The identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message.

(70) Step 2: The DeNB sends the identity indication information to an MME in an Initial UE message upon reception of the identity indication information in the course of establishing the RRC connection.

(71) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is RN indication information in the subscription data; and the subscription data further includes two APNs: one of the APNs is used to select PGWs in connection with an OAM; and the other APN is used to select PGWs enabling an RN to operate normally as an evolved Node B; or the subscription data includes one APN, and a PGW corresponding to the APN can be both a PGW enabling an RN to operate normally as an evolved Node B and a PGW enabling an RN to access an OAM.

(72) When there are two APNs in the subscription data, the APN used to select a PGW enabling an RN to operate normally as an evolved Node B is provided with a specific flag indicating that the APN is used to select PGWs enabling an RN to operate normally as an evolved Node B; or the APN used to select a PGW for connection with an OAM is provided with a specific flag indicating that the APN with the flag is used to select PGWs in connection with an OAM.

(73) Step 4: The MME knows that the current device is an RN from the RN indication information in the subscription data and determines that the RN is a mobile RN according to the identity indication information sent from the DeNB and then selects a PGW for the mobile RN according to the APN with or without the specific flag in the subscription data (i.e., the APN used to select a PGW enabling an RN to operate normally as an evolved Node B). The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(74) Step 5: The MME accepts an Attach request of the mobile RN and sends an 51 Context Setup Request to the DeNB.

(75) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

Third Embodiment

(76) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to identity indication information sent from the mobile RN and selects a PGW according to local pre-configuration information, and as illustrated in FIG. 7C:

(77) Step 1: A mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(78) When the mobile RN notifies the DeNB that the mobile RN is a mobile RN, the identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message.

(79) Step 2: The DeNB sends the identity indication information to an MME in an Initial UE message upon reception of the identity indication information in the course of establishing the RRC connection.

(80) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is RN indication information in the subscription data; and the subscription data further includes one APN used to select a PGW for connection with an OAM.

(81) Step 4: The MME knows that the current device is an RN from the RN indication information in the subscription data and determines that the RN is a mobile RN according to local pre-configuration information and then selects a PGW for the mobile RN according to the local pre-configuration information. The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(82) The local pre-configuration information includes APN information of PGWs, information about an IP address of a PGW which can be a mobile RN, etc.

(83) Step 5: The MME accepts an Attach request of the mobile RN and sends an 51 Context Setup Request to the DeNB.

(84) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

Fourth Embodiment

(85) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to subscription data and selects a PGW according to local pre-configuration information, and as illustrated in FIG. 7D:

(86) Step 1: A mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(87) When the mobile RN notifies the DeNB that the mobile RN is a mobile RN, the identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message.

(88) When the mobile RN notifies the DeNB that the mobile RN is an RN, RN identity indication information carried in an existing RRC Connection Setup Complete message can be reused.

(89) Step 2: The DeNB sends the identity indication information to an MME in an Initial UE message upon reception of the identity indication information in the course of establishing the RRC connection.

(90) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is mobile RN indication information in the subscription data; and the subscription data further includes one APN used to select a PGW for connection with an OAM.

(91) Step 4: The MME knows that the current RN is a mobile RN from the mobile RN indication information in the subscription data and selects a PGW for the mobile RN according to the local pre-configuration information. The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(92) The local pre-configuration information includes APN information of PGWs, information about an IP address of a PGW which can be a mobile RN, etc.

(93) Step 5: The MME accepts an Attach request of the mobile RN and sends an 51 Context Setup Request to the DeNB.

(94) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

Fifth Embodiment

(95) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to identity indication information sent from the mobile RN and selects a PGW according to an APN in an NAS message, and as illustrated in FIG. 7E:

(96) Step 0: A mobile RN downloads, from OAM, APN information referring to PGWs enabling an RN to operate normally as an evolved Node B or acquires locally preconfigured APN information referring to PGWs enabling an RN to operate normally as an evolved Node B.

(97) The mobile RN can download the APN information from the OAM in a first phase of startup.

(98) Step 1: The mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(99) The identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message, and the APN information can be carried in an NAS message of the RRC Setup Complete message.

(100) Step 2: The DeNB sends the identity indication information, and the NAS message, carrying the APN information, to an MME in an Initial UE message upon reception of the identity indication information and the NAS message carrying the APN information in the course of establishing the RRC connection.

(101) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is RN indication information in the subscription data; and the subscription data further includes one APN used to select a PGW for connection with an OAM.

(102) Step 4: The MME knows that the current device is an RN from the RN indication information in the subscription data and determines that the RN is a mobile RN according to the identity indication information sent from the DeNB and then selects a PGW for the mobile RN according to the APN carried in the NAS message. The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(103) Step 5: The MME accepts an Attach request of the mobile RN and sends an S1 Context Setup Request to the DeNB.

(104) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

Sixth Embodiment

(105) In this embodiment, an MME determines whether a mobile RN is a fixed RN or a mobile RN according to subscription data and selects a PGW according to an APN in an NAS message, and as illustrated in FIG. 7F:

(106) Step 0: A mobile RN downloads, from OAM, APN information referring to PGWs enabling an RN to operate normally as an evolved Node B or acquires locally preconfigured APN information referring to PGWs enabling an RN to operate normally as an evolved Node B.

(107) The mobile RN can download the APN information from the OAM in a first phase of startup.

(108) Step 1: The mobile RN sends to a DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(109) When the mobile RN notifies the DeNB that the mobile RN is a mobile RN, the identity indication information indicating that the mobile RN is a mobile RN can be carried in an RRC Setup Complete message, and the APN information can be carried in an NAS message of the RRC Setup Complete message.

(110) When the mobile RN notifies the DeNB that the mobile RN is an RN, RN identity indication information carried in an existing RRC Connection Setup Complete message can be reused, and the APN information can be carried in an NAS message of an RRC Setup Complete message.

(111) Step 2: The DeNB sends the identity indication information, and the NAS message, carrying the APN information, to an MME in an Initial UE message upon reception of the identity indication information and the NAS message in the course of establishing the RRC connection.

(112) Step 3: The MME initiates a Locate Update procedure to an HSS, and the HSS sends subscription data of the mobile RN to the MME, where there is mobile RN indication information in the subscription data; and the subscription data further includes one APN used to select a PGW for connection with an OAM.

(113) Step 4: The MME knows that the current RN is a mobile RN from the mobile RN indication information in the subscription data and selects a PGW for the mobile RN according to the APN carried in the NAS message. The MME can select an SGW for the mobile RN as in the mechanism to select an SGW for a UE in the prior art; the MME sends an IP address of the selected PGW and other information to the SGW in a Session Setup procedure; and the SGW performs a Session Setup procedure with the PGW.

(114) Step 5: The MME accepts an Attach request of the mobile RN and sends an S1 Context Setup Request to the DeNB.

(115) Step 6: The DeNB establishes an air interface bearer with the RN in an RRC Connection Reconfigure process.

(116) Referring to FIG. 8, an embodiment of the invention further provides an MME including:

(117) a reception component 801 is configured to receive an Initial UE message, carrying identity indication information of an RN, sent from a DeNB;

(118) an acquiring component 81 is configured to acquire subscription data of the RN from a Home Subscriber Server (HSS);

(119) a determination component 82 is configured to determine whether the RN is a mobile RN according to the identity indication information and/or the subscription data of the RN; and

(120) a selection component 83 is configured to select a PGW of a core network as the PGW of the RN when it is determined that the RN is a mobile RN.

(121) Furthermore the determination component 82 is configured:

(122) to judge whether the identity indication information of the RN indicates that the RN is a mobile RN, and if so, to determine that the RN is a mobile RN; otherwise, to determine that the RN is fixed RN.

(123) Furthermore the determination component 82 is configured:

(124) to judge whether the identity indication information of the RN indicates that the RN is a mobile RN and whether there is mobile RN indication information in the subscription data, and if both judge results are positive, to determine that the RN is a mobile RN; otherwise, to determine that the RN is fixed RN.

(125) Furthermore the determination component 82 is configured:

(126) to judge whether there is mobile RN indication information in the subscription data, and if so, to determine that the RN is a mobile RN; otherwise, to determine that the RN is fixed RN.

(127) Furthermore the selection component 83 is configured:

(128) to select a PGW of a core network as the PGW of the RN according to an Access Point Name (APN) in the subscription data or local pre-configuration information or an APN reported from the RN.

(129) Furthermore the selection component 83 is configured:

(130) when there are two APNs in the subscription data, to select one with a specific flag from the two APNs, to inquire a DNS server for information about PGWs according to the selected APN and to select one of the found PGWs as a PGW of the RN, where the specific flag indicates that the APN with the flag is used to select PGWs enabling an RN to operate normally as an evolved Node B; or

(131) when there are two APNs in the subscription data, to select one without a specific flag among the two APNs, to inquire a DNS server for information about PGWs according to the selected APN and to select one of the found PGWs as a PGW of the RN, where the specific flag indicates that the APN with the flag is used to select PGWs in connection with an OAM; or

(132) when there is one APN in the subscription data, to inquire a DNS server for information about PGWs according to the APN and to select one of the PGWs as the PGW of the RN.

(133) Furthermore the selection component 83 is configured:

(134) when there is an APN of PGWs in the local pre-configuration information, to inquire a DNS server for information about PGWs according to the APN and to select one of the PGWs as the PGW of the RN; or

(135) when there an IP address of a PGW in the local pre-configuration information, to select the PGW with the IP address as the PGW of the RN.

(136) Furthermore the selection component 83 is configured:

(137) when the APN reported from the RN is carried in a Non Access Stratum (NAS) message in the Initial UE message, to acquire the APN in the NAS message, to inquire a DNS server for information about PGWs according to the APN and to select one of the PGWs as the PGW of the RN.

(138) Furthermore the MME further includes:

(139) a selection component 84 is configured to select an SGW for the RN according to the geographical location where the RN currently resides and load conditions of respective Serving Gateways (SGWs).

(140) Referring to FIG. 9, an embodiment of the invention further provides a mobile RN including:

(141) an establishment component 90 is configured to establish an RRC connection with a DeNB upon entry into a second phase of startup; and

(142) an indication component 91 is configured to send to the DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection.

(143) Furthermore the indication component 91 is configured:

(144) to send to the DeNB the identity indication information indicating the mobile RN as an RN or a mobile RN in an RRC Setup Complete message.

(145) Furthermore the mobile RN further includes:

(146) an obtainment component 92 is configured to download from an OAM, an Access Point Name (APN) referring to PGWs enabling an RN to operate normally as an evolved Node B, or, to acquire locally preconfigured APN referring to PGWs enabling an RN to operate normally as an evolved Node B, before the RRC connection is established with the DeNB; and

(147) the indication component 91 is further configured to send the APN to the DeNB in a NAS message while sending the identity indication information indicating the mobile RN as an RN or a mobile RN to the DeNB.

(148) Furthermore the indication component 91 is further configured:

(149) to send the APN to the DeNB in a Non Access Stratum (NAS) message in the RRC Setup Complete message.

(150) Referring to FIG. 10, an embodiment of the invention further provides a DeNB including:

(151) a reception component 100 is configured to receive identity indication information, sent from a mobile RN, indicating the mobile RN as an RN or a mobile RN in the course of establishing an RRC connection with the mobile RN; and

(152) a sending component 101 is configured to send an Initial UE message, carrying the identity indication information, to an MME.

(153) Furthermore the reception component 100 is configured:

(154) to receive the identity indication information sent from the mobile RN in an RRC Setup Complete message.

(155) Furthermore the reception component 100 is further configured:

(156) to receive an NAS message, carrying an APN, sent from the mobile RN while receiving the identity indication information sent from the mobile RN; and

(157) wherein the Initial UE message sent from the sending component 101 further carries the NAS message carrying the APN.

(158) Referring to FIG. 11, an embodiment of the invention further provides an HSS including:

(159) a reception component 110 is configured to receive a Locate Update Request sent from an MME; and

(160) a response component 111 is configured to return subscription data of a mobile RN to the MME, where the subscription data includes mobile RN indication information and/or an Access Point Name (APN) referring to PGWs enabling an RN to operate normally as an evolved Node B.

(161) Furthermore the subscription data returned from the response component 111 further includes an APN referring to PGWs for connection with an OAM; and

(162) The APN, returned from the response component 111, referring to PGWs enabling an RN to operate normally as an evolved Node B is provided with a specific flag indicating that the APN with the flag is used to select PGWs enabling an RN to operate normally as an evolved Node B; or the APN referring to PGWs in connection with an Operation and Maintenance (OAM) system is provided with a specific flag indicating that the APN with the flag is used to select PGWs in connection with an OAM.

(163) In summary, advantageous effects of the invention include:

(164) In the solutions according to the embodiments of the invention, a mobile RN establishes an RRC connection with a DeNB upon entry into a second phase of startup and sends to the DeNB identity indication information indicating the mobile RN as an RN or a mobile RN in the course of establishing the RRC connection; the DeNB sends an Initial UE message, carrying the identity indication information, to an MME upon reception of the identity indication information, sent from the mobile RN, indicating the mobile RN as an RN or a mobile RN; and the MME acquires subscription data from an HSS upon reception of the Initial UE message sent from the DeNB, determines whether the RN is a mobile RN according to the identity indication information and/or the subscription data, and if so, then the MME selects a PGW of a core network as a PGW of the RN. Apparently the inventive method enables a solution to selecting a PGW for a mobile RN to thereby address the issue of how to select a PGW for a mobile RN.

(165) Those skilled in the art shall appreciate that the embodiments of the invention can be embodied as a method, a system or a computer program product. Therefore the invention can be embodied in the form of an all-hardware embodiment, an all-software embodiment or an embodiment of software and hardware in combination. Furthermore the invention can be embodied in the form of a computer program product embodied in one or more computer useable storage mediums (including but not limited to a disk memory, a CD-ROM, an optical memory, etc.) in which computer useable program codes are contained.

(166) The invention has been described in a flow chart and/or a block diagram of the method, the device (system) and the computer program product according to the embodiments of the invention. It shall be appreciated that respective flows and/or blocks in the flow chart and/or the block diagram and combinations of the flows and/or the blocks in the flow chart and/or the block diagram can be embodied in computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a specific-purpose computer, an embedded processor or a processor of another programmable data processing device to produce a machine so that the instructions executed on the computer or the processor of the other programmable data processing device create means for performing the functions specified in the flow(s) of the flow chart and/or the block(s) of the block diagram.

(167) These computer program instructions can also be stored into a computer readable memory capable of directing the computer or the other programmable data processing device to operate in a specific manner so that the instructions stored in the computer readable memory create an article of manufacture including instruction means which perform the functions specified in the flow(s) of the flow chart and/or the block(s) of the block diagram.

(168) These computer program instructions can also be loaded onto the computer or the other programmable data processing device so that a series of operational steps are performed on the computer or the other programmable data processing device to create a computer implemented process so that the instructions executed on the computer or the other programmable device provide steps for performing the functions specified in the flow(s) of the flow chart and/or the block(s) of the block diagram.

(169) Although the preferred embodiments of the invention have been described, those skilled in the art benefiting from the underlying inventive concept can make additional modifications and variations to these embodiments. Therefore the appended claims are intended to be construed as encompassing the preferred embodiments and all the modifications and variations coming into the scope of the invention.

(170) Evidently those skilled in the art can make various modifications and variations to the invention without departing from the essence and scope of the invention. Thus the invention is also intended to encompass these modifications and variations thereto so long as the modifications and variations come into the scope of the claims appended to the invention and their equivalents.