# US 2015/0146519 A1 · Apparatus and Methods for Supporting Control Plane Data

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

- Number: US 2015/0146519 A1
- Document ID: US20150146519A1
- Status: Published application
- Kind: A1
- Application number: 14/087,545
- Filed: 2013-11-22
- Published: 2015-05-28
- Earliest claimed: 2013-11-22
- Assignees: General Dynamics Broadband Inc.
- Applicants: General Dynamics Broadband Inc.
- Inventors: Robert Zakrzewski
- Web page: https://patentgrep.com/patent/US20150146519A1

## CPC

- H04W 24/04: Arrangements for maintaining operational condition
- H04W 8/06: Registration at serving network Location Register, VLR or user mobility server
- H04W 8/30: Network data restoration; {Network data reliability; Network data fault tolerance}
- H04W 12/041: Key generation or derivation
- H04W 12/043: using a trusted network node as an anchor
- H04W 12/06: Authentication
- H04W 88/005: {Data network PoA devices}
- H04W 88/14: Backbone network devices
- H04W 92/24: between backbone network devices
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A wireless communications system supports control plane data and comprises: a first mobility management entity, MME; at least one second mobility management entity, MME; and a terminal device; wherein both the first MME and the at least one second MME are allocated to interoperate to support control plane data for the terminal device.

## Claims

### Claim 1

A wireless communications system supporting control plane data comprising:
a first mobility management entity, MME;
at least one second mobility management entity, MME operably coupled to the first MME; and
a terminal device;
wherein both the first MME and the at least one second MME are allocated to support control plane data for the terminal device.

### Claim 2 (depends on 1)

The wireless communications system of claim 1 wherein the at least one second MME comprises a processor arranged to monitor at least a subset of control plane data handled by the first MME.

### Claim 3 (depends on 2)

The wireless communications system of claim 2 wherein the processor is arranged to modify at least a subset of control plane data to be handled by the first MME.

### Claim 4 (depends on 2)

The wireless communications system of claim 2 wherein the processor is arranged to monitor control plane data passed between a serving gateway, S-GW, and the first MME.

### Claim 5 (depends on 2)

The wireless communications system of claim 2 wherein the processor is arranged to monitor, in a first mode of operation control plane data passed between the terminal device and the first MME when the first MME and the at least one second MME are operably coupled and operational.

### Claim 6 (depends on 5)

The wireless communications system of claim 5 wherein the processor is further arranged to terminate at least one or:
received Non-Access Stratum, NAS, protocol messages and forward all NAS signalling to the first MME;
S1AP protocol messages and forward all S1AP signalling to the first MME.

### Claim 7 (depends on 1)

The wireless communications system of claim 1 wherein the terminal device performs a dual registration to both the first MME and the at least one second MME.

### Claim 8 (depends on 7)

The wireless communications system of claim 7 wherein the terminal device performs a dual registration to both the first MME and the at least one second MME by issuing a single registration request that results in context information of the terminal device being kept at both the first MME and the at least one second MME.

### Claim 9 (depends on 1)

The wireless communications system of claim 1 wherein the at least one second MME comprises at least a subset of the MME functionality of the first MME.

### Claim 10 (depends on 2)

The wireless communications system of claim 2 wherein the processor is arranged to build and update context information associated with the terminal device.

### Claim 11 (depends on 10)

The wireless communications system of claim 10 wherein the processor is operably coupled to a memory element arranged to store the terminal device context information.

### Claim 12 (depends on 1)

The wireless communications system of claim 1 wherein the at least one second MME processor monitors control plane data between the terminal device and the first MME following a receipt of a security key, KASME, or a whole authentication vector from the first MME, such that the at least one second MME is able to use the same security association between the terminal device and the first MME.

### Claim 13 (depends on 1)

The wireless communications system of claim 1 wherein the at least one second MME comprises a processor arranged to detect a communication link failure between the at least one second MME and the first MME, and in response thereto switch to a second mode of operation when the first MME and the at least one second MME are no longer operably coupled or the first MME is deemed non-operational.

### Claim 14 (depends on 13)

The wireless communications system of claim 13 wherein the at least one second MME processor is arranged to both terminate and handle: NAS protocol messages, S1AP protocol messages and general packet radio service, GPRS, tunneling protocol control, GTP-c, messages via a S11 interface.

### Claim 15 (depends on 13)

The wireless communications system of claim 13 wherein the at least one second MME processor is arranged to track the terminal device mobility in an evolved packet system connection management, ECM, idle mode and arrange a S1 handover in ECM connected mode of the terminal device.

### Claim 16 (depends on 13)

The wireless communications system of claim 13 wherein the at least one second MME processor is arranged not to perform one or more of the following in the first mode of operation and to perform one or more of the following in the second mode of operation:
trigger or coordinate paging with the terminal device;
manage an authentication, AKA, procedure with the terminal device;
handle a security mode command procedure with the terminal device;
choose a target MME when relocation is required at handover for the terminal device;
invoke one or more core network node selection functions;
manage ECM-IDLE/ECM-CONNECTED transitions of the terminal device.

### Claim 17 (depends on 13)

The wireless communications system of claim 13 wherein the at least one second MME processor is arranged to invoke one or more core network node selection functions that operably re-couples to the first MME when a connection thereto becomes operational.

### Claim 18 (depends on 17)

The wireless communications system of claim 17 wherein the at least one second MME processor triggers the terminal device to initiate a tracking area update, TAU, process to cause the terminal device context information at the at least one second MME to be transferred to the first MME, and the at least one second MME reverts to a proxy mode of operation.

### Claim 19

A proxy mobility management entity, MME, located in a wireless communications system that comprises an additional first MME wherein the first MME is operational and operably coupled to the proxy MME such that they are both allocated to support control plane data for the terminal device; the proxy MME comprising a processor arranged to:
monitor and modify GTP control plane data passed between a serving gateway, S-GW, and the first MME via a S11 interface; and
monitor and modify S1AP messages from a base station;
monitor and terminate control plane data passed between the terminal device and the first MME; and in response thereto terminate received Non-Access Stratum, NAS, protocol messages and forward NAS signalling to the first MME.

### Claim 20 (depends on 19)

The proxy MME of claim 19 wherein the processor monitors control plane data between the terminal device and the first MME following a receipt of a security key (KASME) or a whole authentication vector from the first MME, such that the processor is able to use the same security association between the terminal device and the first MME.

### Claim 21 (depends on 19)

The proxy MME of claim 19 wherein the processor is further arranged to detect a communication link failure between the proxy MME and the first MME or the first MME is deemed non-operational, and in response thereto switch to a mode of operation where the proxy MME assumes responsibility for at least a subset of functions of the first MME.

### Claim 22 (depends on 19)

The proxy MME of claim 19 wherein the processor is arranged to build and update context information associated with the terminal device.

### Claim 23 (depends on 21)

The proxy MME of claim 21 wherein the processor is arranged not to perform one or more of the following in the first mode of operation:
trigger or coordinate paging with the terminal device;
manage an authentication, AKA, procedure with the terminal device;
handle a security mode command procedure with the terminal device;
choose a target MME when relocation is required at handover for the terminal device;
invoke one or more core network node selection functions;
manage ECM-IDLE/ECM-CONNECTED transitions of the terminal device.

### Claim 24 (depends on 21)

The proxy MME of claim 21 wherein the processor is arranged to:
terminate and handle GTP control plane data; and
terminate and handle S1AP messages from a base station;
terminate and handle received Non-Access Stratum, NAS, protocol messages.

### Claim 25

A method of operation of a wireless communications system supporting control plane data with a terminal device using a first mobility management entity, MME, and a proxy mobility management entity, MME; the method comprising, at the proxy MME:
monitoring and modifying GTP control plane data passed between a serving gateway, S-GW, and the first MME via a S11 interface; and
monitoring and modifying S1AP messages from a base station;
monitoring and terminating control plane data passed between the terminal device and the first MME; and in response thereto terminating received Non-Access Stratum, NAS, protocol messages and forward NAS signalling to the first MME.

### Claim 26 (depends on 25)

A non-transitory computer program product comprising executable program code for a wireless communications system supporting control plane data with a terminal device using a first mobility management entity, MME, and a proxy mobility management entity, MME, the executable program code operable for, when executed at the proxy MME, performing the method of claim 25.
