# US 10,375,614 B2 · Apparatus, system and method for dual connectivity

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,375,614 B2
- Document ID: US10375614B2
- Status: Granted
- Kind: B2
- Application number: 15/123,494
- Filed: 2015-03-05
- Published: 2017-03-16
- Granted: 2019-08-06
- Earliest claimed: 2014-03-06
- Assignees: NEC Corporation
- Applicants: NEC Corporation
- Inventors: Xiaowei Zhang; Anand Raghawa Prasad
- Web page: https://patentgrep.com/patent/US10375614B2

## CPC

- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 12/041: Key generation or derivation
- H04W 12/0433: Key management protocols
- H04W 36/00695: {using split of the control plane or user plane}
- H04W 12/122: Counter-measures against attacks; Protection against rogue devices
- H04W 88/08: Access point devices
- H04W 92/20: between access points
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 1

A mobile communication system for DC (Dual Connectivity), comprising:
a UE (User Equipment);
a MeNB (Master eNodeB);
a SeNB (Secondary eNodeB);
a MME (Mobility Management Entity);
a S-GW (Serving Gateway); and
a P-GW (PDN Gateway), wherein:
the UE is connected to the MeNB and the SeNB, C-Plane (Control-Plane) signaling is performed by X2-C interface between the MeNB and the SeNB and by S1-MME interface between the MeNB and the MME,
U-Plane (User-Plane) data is performed by X2-U interface between the MeNB and the SeNB and by S1-U interface from the S-GW to the MeNB and the SeNB,
the MeNB sends an SeNB Addition request message or an SeNB Modification request message to the SeNB, and
receives an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB,
the UE receives a RRCConnectionReconfiguration message from the MeNB,
and sends a RRCConnectionReconfigurationComplete message to the MeNB,
the MeNB sends a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME,
the MME sends a Modify Bearer Request message including the DC configuration information to the S-GW,
the S-GW sends the Modify Bearer Request message to the P-GW, and
the MeNB receives a response message from the MME, and
derives a security key for the SeNB and sends the security key to the SeNB for key update.

### Claim 2 (depends on 1)

The mobile communication system according to claim 1, the DC configuration information includes an address of the SeNB.

### Claim 3 (depends on 1)

The mobile communication system according to claim 1, wherein bearers are offloaded to the SeNB.

### Claim 4

A MeNB (Master evolved Node B) in a mobile communication system for DC (Dual Connectivity) including a UE (User Equipment), a SeNB (Secondary eNodeB), a MME (Mobility Management Entity), a S-GW (Serving Gateway), and a P-GW (PDN Gateway), the MeNB comprising:
a sender configured to send an SeNB Addition request message or an SeNB Modification request message to the SeNB, send a RRCConnectionReconfiguration message to the UE, and send a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME; and
a receiver configured to receive an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB, receive a RRCConnectionReconfigurationComplete message from the UE, and receives a response message from the MME, wherein:
the MME sends a Modify Bearer Request message including the DC configuration information to the S-GW,
the S-GW sends the Modify Bearer Request message to the P-GW,
the MeNB derives a security key for the SeNB and sends the security key to the SeNB for key update,
the UE is connected to the MeNB and the SeNB, C-Plane (Control-Plane) signaling is performed by X2-C interface between the MeNB and the SeNB and by S1-MME interface between the MeNB and the MME, and
U-Plane (User-Plane) data is performed by X2-U interface between the MeNB and the SeNB and by S1-U interface from the S-GW to the MeNB and the SeNB.

### Claim 5 (depends on 4)

The MeNB according to claim 4, the DC configuration information includes an address of the SeNB.

### Claim 6 (depends on 4)

The MeNB according to claim 4, wherein bearers are offloaded to the SeNB.

### Claim 7

A UE (User Equipment) in a mobile communication system for DC (Dual Connectivity) including a MeNB (Master eNodeB), a SeNB (Secondary eNodeB), a MME (Mobility Management Entity), a S-GW (Serving Gateway), and a P-GW (PDN Gateway), the UE comprising:
a controller configured to connect to the MeNB and the SeNB, perform C-Plane (Control-Plane) interface with the MeNB, and perform U-Plane (User-Plane) interface with the MeNB and the SeNB;
a receiver configured to receive a RRCConnectionReconfiguration message from the MeNB; and
a sender configured to send a RRCConnectionReconfigurationComplete message to the MeNB, wherein:
the MeNB sends an SeNB Addition request message or an SeNB Modification request message to the SeNB, receives an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB, sends a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME,
the MME sends a Modify Bearer Request message including the DC configuration information to the S-GW,
the S-GW sends the Modify Bearer Request message to the P-GW,
the MeNB receives a response message from the MME, and
the MeNB derives a security key for the SeNB and sends the security key to the SeNB for key update.

### Claim 8 (depends on 7)

The UE according to claim 7, the DC configuration information includes an address of the SeNB.

### Claim 9 (depends on 7)

The UE according to claim 7, wherein bearers are offloaded to the SeNB.

### Claim 10

A method of a mobile communication system for DC (Dual Connectivity) including at least a UE (User Equipment), a MeNB (Master eNodeB), a SeNB (Secondary eNodeB), a MME (Mobility Management Entity), a S-GW (Serving Gateway), and a P-GW (PDN Gateway), comprising:
sending an SeNB Addition request message or an SeNB Modification request message to the SeNB;
receiving an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB;
receiving a RRCConnectionReconfiguration message from the MeNB;
sending a RRCConnectionReconfigurationComplete message to the MeNB;
sending a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME;
sending a Modify Bearer Request message including the DC configuration information to the S-GW;
sending the Modify Bearer Request message to the P-GW; and
receiving a response message from the MME,
wherein:
the MeNB derives a security key for the SeNB and the MeNB sends the security key to the SeNB for key update,
the UE connects to the MeNB and the SeNB, C-Plane (Control-Plane) signaling is performed by X2-C interface between the MeNB and the SeNB and by S1-MME interface between the MeNB and the MME, and
U-Plane (User-Plane) data is performed by X2-U interface between the MeNB and the SeNB and by S1-U interface from the S-GW to the MeNB and the SeNB.

### Claim 11 (depends on 10)

The method according to claim 10, the DC configuration information includes an address of the SeNB.

### Claim 12 (depends on 10)

The method according to claim 10, wherein bearers are offloaded to the SeNB.

### Claim 13

A method of a MeNB (Master evolved Node B) in a mobile communication system for DC (Dual Connectivity) including a UE (User Equipment), a SeNB (Secondary eNodeB), a MME (Mobility Management Entity), a S-GW (Serving Gateway), and a P-GW (PDN Gateway), the method comprising:
sending, an SeNB Addition request message or an SeNB Modification request message to the SeNB;
sending a RRCConnectionReconfiguration message to the UE;
sending a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME;
receiving an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB;
receiving a RRCConnectionReconfigurationComplete message from the UE; and
receiving a response message from the MME, wherein
the MME sends a Modify Bearer Request message including the DC configuration information to the S-GW,
the S-GW sends the Modify Bearer Request message to the P-GW,
the MeNB derives a security key for the SeNB and sends the security key to the SeNB for key update,
the UE is connected to the MeNB and the SeNB,
C-Plane (Control-Plane) signaling is performed by X2-C interface between the MeNB and the SeNB and by S1-MME interface between the MeNB and the MME, and
U-Plane (User-Plane) data is performed by X2-U interface between the MeNB and the SeNB and by S1-U interface from the S-GW to the MeNB and the SeNB.

### Claim 14 (depends on 13)

The method according to claim 13, the DC configuration information includes an address of the SeNB.

### Claim 15 (depends on 13)

The method according to claim 13, wherein bearers are offloaded to the SeNB.

### Claim 16

A method of a UE (User Equipment) in a mobile communication system for DC (Dual Connectivity) including a MeNB (Master eNodeB), a SeNB (Secondary eNodeB), a MME (Mobility Management Entity), a S-GW (Serving Gateway), and a P-GW (PDN Gateway), comprising:
connecting to the MeNB and the SeNB;
performing C-Plane (Control-Plane) interface with the MeNB;
performing U-Plane (User-Plane) interface with the MeNB and the SeNB;
receiving a RRCConnectionReconfiguration message from the MeNB; and
sending a RRCConnectionReconfigurationComplete message to the MeNB, wherein:
the MeNB sends an SeNB Addition request message or an SeNB Modification request message to the SeNB, receives an SeNB Addition request acknowledgement message or an SeNB Modification request acknowledgment message from the SeNB, and sends a message including DC configuration information and an indicator to show that the DC configuration information is for the DC and not that the UE has changed cells in a handover procedure to the MME,
the MME sends a Modify Bearer Request message including the DC configuration information to the S-GW,
the S-GW sends the Modify Bearer Request message to the P-GW,
the MeNB receives a response message from the MME, and
the MeNB derives a security key for the SeNB and sends the security key to the SeNB for key update.

### Claim 17 (depends on 16)

The method according to claim 16, the DC configuration information includes an address of the SeNB.

### Claim 18 (depends on 16)

The method according to claim 16, wherein bearers are offloaded to the SeNB.
