APPARATUS, SYSTEM AND METHOD FOR DUAL CONNECTIVITY

Abstract

An SeNB informs an MeNB that it can configure bearers for the given UE. At this time, the MeNB manages the DRB status, and then sends a key S-KeNB to the SeNB. The MeNB also sends a KSI for the S-KeNB to both of the UE and the SeNB. After this procedure, the MeNB informs an EPC (MME and S-GW) about the new bearer configured at the SeNB, such that the S-GW 50 can start offloading the bearer(s) to the SeNB 30. Prior to the offloading, the EPC network entity (MME or S-GW) performs verification that: 1) whether the request is coming from authenticated source (MeNB); and 2) whether the SeNB is a valid eNB to which the traffic can be offload.

Claims

1. A MN (Master Node) in a mobile communication system including a UE (User Equipment), a SN (Secondary Node), and a MME (Mobility Management Entity), wherein the MN and the SN are connected to the UE for DC (Dual Connectivity), the MN comprising: a memory that stores a set of instructions; and a controller configured to execute the set of instructions that when executed: send, to the SN, a SN Addition request message or a SN Modification request message, receive, from the SN, a SN Addition request acknowledgement message or a SN Modification request acknowledgement message, send, to the UE, a RRCConnectionReconfiguration message including a counter to update a key for the SN, receive, from the UE, a RRCConnectionReconfigurationComplete message, send, to the MME, an E-RAB Modification Indication message including DC configuration information and an indicator showing that the message is for the DC, and receive, from the MME, an E-RAB Modification Confirmation message.

2. The MN according to claim 1, further comprising wherein: the MME is configured to send, to a S-GW (Serving Gateway), a Modify Bearer Request message including the DC configuration information, the S-GW is configure to send the Modify Bearer Request message to a P-GW (PDN gateway), and the P-GW is configured to send a Modify Bearer Response message to the S-GW, and send downlink data to the UE.

3. The MN according to claim 1, wherein the indicator shows that the message is not for a handover.

4. The MN according to claim 1, further comprising: wherein C-plane (Control-plane) signaling is performed by X2-C interface between the MN and the SN and by S1-MME interface between the MN and the MME, and U-plane (User-plane) signaling is performed by X2-U interface between the MN and the SN and by S1-U interface from a S-GW (Serving Gateway) to the MN and the SN.

5. The MN according to claim 1, wherein the MN is configured to derive an updated key for user-plane protection and send the updated key to the SN.

6. The MN according to claim 1, wherein the DC configuration information includes an address of the SN.

7. A method of a MN (Master Node) in a mobile communication system including a UE (User Equipment), a SN (Secondary Node), and a MME (Mobility Management Entity), wherein the MN and the SN are connected to the UE for DC (Dual Connectivity), the method comprising: sending, to the SN, a SN Addition request message or a SN Modification request message; receiving, from the SN, a SN Addition request acknowledgement message or a SN Modification request acknowledgement message; sending, to the UE, a RRCConnectionReconfiguration message including a counter to update a key for the SN; receiving, from the UE, a RRCConnectionReconfigurationComplete message; sending, to the MME, an E-RAB Modification Indication message including DC configuration information and an indicator showing that the message is for the DC; and receiving, from the MME, an E-RAB Modification Confirmation message.

8. A UE (User Equipment) that is connected to a MN (Master Node) and a SN (Secondary Node) for DC (Dual Connectivity), the UE comprising: a memory that stores a set of instructions; and a controller configured to execute the set of instructions that when executed: receive, from the MN, a RRCConnectionReconfiguration message including a counter to update a key for the SN after SN Addition/modification procedure, send, to the MN, a RRCConnectionReconfigurationComplete message, and derive an updated key for a user-plane protection based on the counter.

9. The UE according to claim 8, further comprising wherein: the MN is configured to send, to a MME (Mobility Management Entity), an E-RAB Modification Indication message including DC configuration information and an indicator showing that the message is for the DC, the MME is configured to send, to a S-GW (Serving Gateway), a Modify Bearer Request message including the DC configuration information, the S-GW is configure to send the Modify Bearer Request message to a P-GW (PDN gateway), and the P-GW is configured to send a Modify Bearer Response message to the S-GW, and send downlink data to the UE.

10. The UE according to claim 9, wherein the indicator shows that the message is not for a handover.

11. The UE according to claim 8, further comprising: wherein C-plane (Control-plane) signaling is performed by X2-C interface between the MN and the SN and by S1-MME interface between the MN and a MME (Mobility Management Entity), and U-plane (User-plane) signaling is performed by X2-U interface between the MN and the SN and by S1-U interface from a S-GW (Serving Gateway) to the MN and the SN.

12. The UE according to claim 8, wherein the MN is configured to derive an updated key for the user-plane protection and send the updated key to the SN.

13. A method of a UE (User Equipment) that is connected to a MN (Master Node) and a SN (Secondary Node) for DC (Dual Connectivity), the method comprising: receiving, from the MN, a RRCConnectionReconfiguration message including a counter to update a key for the SN after SN Addition/modification procedure; sending, to the MN, a RRCConnectionReconfigurationComplete message; and deriving an updated key for a user-plane protection based on the counter.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0024] FIG. 1 is a block diagram showing a configuration example of a system according to an exemplary embodiment of the present invention.

[0025] FIG. 2 is a sequence diagram showing an example of optimized SeNB Addition/Modification procedure in the system according to the exemplary embodiment.

[0026] FIG. 3 is a sequence diagram showing a first example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.

[0027] FIG. 4 is a sequence diagram showing a second example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.

[0028] FIG. 5 is a sequence diagram showing a third example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.

[0029] FIG. 6 is a block diagram showing a configuration example of an MeNB according to the exemplary embodiment.

[0030] FIG. 7 is a block diagram showing a configuration example of an MME according to the exemplary embodiment.

DESCRIPTION OF EMBODIMENTS

[0031] Hereinafter, an exemplary embodiment of an apparatus, a system and a method according to the present invention, will be described with the accompanying drawings.

[0032] FIG. 1 shows a configuration example of a system according to this exemplary embodiment, taking as an example the architecture where there is one SeNB per UE.

[0033] This system includes a UE 10, an MeNB 20, an SeNB 30, an MME (Mobility Management Entity) 40, and an S-GW (Serving Gateway) 50. Note that although the illustration is omitted in FIG. 1, the system also includes a P-GW (PDN (Public Data Network) Gateway) 60 as shown in FIGS. 4 to 6.

[0034] As shown by solid lines in FIG. 1, there are provided several interfaces for C-Plane (Control-Plane) signaling. The UE 10 communicates with the MeNB 20 through a Uu interface. The MeNB 20 communicates with the SeNB 30 through an X2-C interface, and communicates with the MME 40 through an S1-MME interface. The S1-MME interface does not exist between the SeNB 30 and the MME 40.

[0035] Further, as shown by dotted lines in FIG. 1, there are also provided several interfaces for U-Plane (User-Plane) communication. Each of the MeNB 20 and the SeNB 30 communicates with the S-GW 50 through an S1-U interface. In this architecture, U-Plane traffic between the UE 10 and the S-GW 50 is transmitted through the MeNB 20 and the SeNB 30 in parallel for the purpose of offloading the MeNB 20 (in other words, for the purpose of offloading the backhaul S1-U interface between the MeNB 20 and the S-GW 50). Moreover, one or more bearers DRB1 to DRBn are established between the UE 10 and the SeNB 30.

[0036] Next, there will be described operation examples of this exemplary embodiment with reference to FIGS. 2 to 5.

1. Optimized SeNB Addition/Modification Procedure

[0037] To counter the problems a) to c) given above, this exemplary embodiment proposes that: [0038] S-KeNB is sent after step S4 SeNB Addition/Modification Command shown in FIG. 2. At step S4, the SeNB 30 informs that it can configure bearers for the given UE 10. [0039] The MeNB 20 manages the DRB status. [0040] The MeNB 20 sends KSI to both of the UE 10 and the SeNB 30.

[0041] FIG. 2 is based on the scenario disclosed in NPL 1 that there is only one MeNB and SeNB per UE. Note that processes at step S4, S6 and S7 are novel part in this invention.

[0042] New step/parameter in key derivation and allocation are as follows.

[0043] Step S4: The SeNB 30 sends to the MeNB 20 its capabilities, if it is different from standard. The capabilities of the SeNB 30 are included in SeNB Addition/Modification Command.

[0044] Step S6: The MeNB 20 sends the S-KeNB and KSI after receiving the SeNB Addition/Modification Command. A new message for sending the S-KeNB and the KSI can be defined as Key Update.

[0045] The reason for performing this step is: reduce the counter value usage. If the MeNB 20 sends the S-KeNB in the SeNB Addition/Modification Request at step S2, and the SeNB 30 does not have radio resource for the UE 10, the MeNB 20 will have to derive a new key and send to next SeNB till it finds the capable SeNB.

[0046] Step S7: the MeNB 20 sends a KSI of S-KeNB to the UE 10 with the counter. This is to make sure that the UE 10 will use the same key as the SeNB 30.

2. Authorization of MeNB and SeNB

[0047] After the SeNB Addition/Modification procedure, the update of the UP path towards the EPC is performed as described in NPL 1. The MeNB 20 should inform the MME 40 and the S-GW 50 about the new bearer configured at the SeNB 30, such that the S-GW 50 can start offloading the bearer(s) to the SeNB 30.

[0048] Before doing the offloading, the network entity (MME 40 or S-GW 50) should perform verification that: 1) whether the request is coming from authenticated source (MeNB); and 2) whether SeNB is a valid eNB to which the traffic can be offload. The network entity (MME 40 or S-GW 50) can be pre-configured with information for the verification, or it can interact with another entity requesting for verification.

[0049] In order to offload the traffic to the correct SeNB 30, the S-GW 50 needs to know that there is offload bearer configured in the SeNB 30 and traffic from the SeNB 30 to the UE 10, on top of SeNB ID (identity) & IP (Internet Protocol) address. Therefore, the SeNB 30 or the MeNB 20 should indicate the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) to the S-GW 50, such that the S-GW 50 knows that dual connectivity is being activated and a new bearer is added to the SeNB 30, and the S-GW 50 should not release the bearer in the MeNB 20. The MME 40 should also be informed that dual connectivity is being activated, such that it can behave accordingly including forwarding the S-GW 50 the information and should not behave same as in handover procedure when Path Switch Request message is received from the MeNB 20.

[0050] FIGS. 3 to 5 show alternatives 1 to 3 for the bearer modification and SeNB verification at the S-GW 50, respectively.

Alternative 1

[0051] This alternative follows the current procedure in NPL 1, FIG. G.1-1, Steps 11-13. The changes are given below:

[0052] At step S11 shown in FIG. 3, the MeNB 20 informs the MME 40 about newly configured SeNB and DRB, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. The MME 40 can forward the S-GW 50 the information in Step S12.

[0053] Step S12: The MME 40 sends bearer modification to the S-GW 50 indicating that this is a DC case together with information that the given DRB of a UE should be sent to the SeNB 30.

[0054] The network entity (MME 40 or S-GW 50) verifies: 1) whether the MeNB 20 is allowed to configure the SeNB 30 for the given UE 10; 2) whether the SeNB 30 is a valid network element; and 3) whether the SeNB 30 is authorized to provide dual connectivity. When the verification is done at the MME 40, it should be after the MME 40 receives Step S11 message. When the verification is done at the S-GW 50, it can happen after it receives the message from the MME 40.

Alternative 2

[0055] The procedure uses Path Switch procedure as indicated in G1 of NPL 1.

[0056] Note that it is initiated by the MeNB 20.

[0057] At step S21 shown in FIG. 4, the MeNB 20 sends Path Switch Request message to the MME 40, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure.

[0058] Step S22: When the MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH (Next Hop) and not increase the NCC (Next-hop Chaining Counter) value it keeps. The MME 40 then sends Modify Bearer Request message to the S-GW 50, includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above.

[0059] Step S23: The S-GW 50 sends Modify Bearer Response to the MME 40, if the verification is successfully completed.

[0060] Step S24: The MME 40 sends Path Switch Request Ack

[0061] (Acknowledgement) to the MeNB 20. The MME 40 should include an indicator to inform the MeNB 20 this is for DC. The MME 40 should not include any NCC value in this message since this is not for handover.

[0062] Step S25: The S-GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages.

[0063] Step S26: The P-GW 60 starts Downlink data.

[0064] The network entity (MME 40 or S-GW 50) should perform the verification as in Alternative 1.

Alternative 3

[0065] The procedure also uses Path Switch procedure as indicated in G1 of NPL 1. Note that it is initiated by the SeNB 30.

[0066] At steps S31-S32 shown in FIG. 5, the SeNB 30 sends Path Switch Request message to the MME 40 via the MeNB 20, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure.

[0067] Step S33: When the MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH and not increase the NCC value it keeps. The MME 40 then sends Modify Bearer Request message to the S-GW 50, includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above.

[0068] Step S34: The S-GW 50 sends Modify Bearer Response to the MME 40, if the verification is successfully completed.

[0069] Steps S35-S36: The MME 40 sends Path Switch Request Ack to the SeNB 30 via the MeNB 20. The MME 40 should include an indicator to inform the MeNB 20 this is for DC. The MME 40 should not include any NCC value in this message since this is not for handover.

[0070] Step S37: The S-GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages.

[0071] Step S38: The P-GW 60 starts Downlink data.

[0072] The network entity (MME 40 or S-GW 50) should perform the verification as in Alternative 1.

[0073] Next, there will be described configuration examples of the MeNB 20 and the MME 40 with reference to FIGS. 6 and 7, respectively.

[0074] As shown in FIG. 6, the MeNB 20 includes a sending unit 21 and a receiving unit 22. The sending unit 21 sends, to the MME 40, the E-RAB Modification Indication message as shown at step S11 in FIG. 3, which includes the DC configuration information and/or the indicator. The receiving unit 22 receives, from the MME 40, the E-RAB Modification Confirmation message as shown at step S13 in FIG. 3. Note that these units 21 and 22 as well as other element(s) of the MeNB 20 can be implemented by at least hardware such as a transceiver which conducts communication with the SeNB 30, the MME 40 and the S-GW 50, a transceiver which conducts wireless communication with the UE 10, as well as a controller like a CPU (Central Processing Unit) which control these transceivers to execute the processes shown in each of FIGS. 2 to 5 or processes equivalent thereto. The MeNB 20 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU).

[0075] As shown in FIG. 7, the MME 40 includes at least a receiving unit 41 and a sending unit 42. The receiving unit 41 receives, from the MeNB 20, the E-RAB Modification Indication message including the DC configuration information and/or the indicator. The sending unit 42 sends, to the S-GW 50, the Modify Bearer Request message as shown at step S22 in FIG. 4, which includes the DC configuration information and/or the indicator. The sending unit 42 may be further configured to send the E-RAB Modification Confirmation message to the MeNB 20. The MME 40 may further include a verifying unit 43. The verifying unit 43 is triggered by the E-RAB Modification Indication message to verify the MeNB 20 and the SeNB 30 for the dual connectivity, as mentioned above. Alternatively, the Modify Bearer Request message may trigger the S-GW 50 to perform such verification. Note that these units 41 to 43 as well as other element(s) of the MME 40 can be implemented by at least hardware such as a transceiver which conducts communication with the MeNB 20 and the S-GW 50, as well as a controller like a CPU which control this transceiver to execute the processes shown in each of FIGS. 2 to 5 or processes equivalent thereto. The MME 40 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU).

[0076] Note that the present invention is not limited to the above-mentioned exemplary embodiment, and it is obvious that various modifications can be made by those of ordinary skill in the art based on the recitation of the claims.

[0077] The whole or part of the exemplary embodiment disclosed above can be described as, but not limited to, the following supplementary notes.

Supplementary note 1

[0078] An MeNB that sends out a key S-KeNB after reception of SeNB Addition/Modification Command, thereby to:

[0079] 1) prevent the S-KeNB being maliciously used by an SeNB that received but the bearer will not be configured for a given UE; and/or

[0080] 2) prevent increase of counter value.

Supplementary note 2

[0081] An MeNB that sends S-KeNB identity to both of an SeNB and a UE.

Supplementary note 3

[0082] A system that re-uses a Path Switch Request message to inform an EPC (MME and/or S-GW) about the SeNB/ new bearer configuration.

Supplementary note 4

[0083] An S-GW that verifies whether an MeNB and an SeNB are authorized to carry the dual connectivity.

Supplementary note 5

[0084] A system, wherein Path Switch procedure is updated for DC that it contains:

[0085] 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address); and

[0086] 2) indicator to show this is for DC.

Supplementary note 6

[0087] A system, wherein an MME and an S-GW behavior in this procedure are updated for dual connectivity that:

[0088] 1) the MME will not compute NH and not increase the NCC value it keeps;

[0089] 2) the MME should include an indicator to inform an MeNB the Path Switch Request Ack message is for DC;

[0090] 3) the MME should not include any NCC value in Path Switch Request Ack message since this is not for handover; and/or

[0091] 4) the S-GW will not release the bearer in the MeNB as in handover procedure.

[0092] This application is based upon and claims the benefit of priority from Japanese patent application No. 2014-043929 filed on Mar. 6, 2014, the disclosures of which is incorporated herein in its entirety by reference.

Reference Signs List

[0093] 10 UE [0094] 20 MeNB [0095] 21, 42 SENDING UNIT [0096] 22, 41 RECEIVING UNIT [0097] 43 VERIFYING UNIT [0098] 30 SeNB [0099] 40 MME [0100] 50 S-GW [0101] 60 P-GW