# US 2012/0252481 A1 · Machine to machine communication in a communication network

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

- Number: US 2012/0252481 A1
- Document ID: US20120252481A1
- Status: Published application
- Kind: A1
- Application number: 13/078,619
- Filed: 2011-04-01
- Published: 2012-10-04
- Earliest claimed: 2011-04-01
- Assignees: Cisco Technology, Inc.
- Inventors: Sourabh ANPAT; Nirav SALOT
- Web page: https://patentgrep.com/patent/US20120252481A1

## CPC

- H04W 8/06: Registration at serving network Location Register, VLR or user mobility server
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 60/04: using triggered events
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

This disclosure relates to a system and method for providing machine to machine communication in a communication network. Although machines are ever more capable of sensing and processing information, machines are expected to garner even more intelligence by autonomously communicating the sensed and processed information with other machines. Therefore, machine to machine (M2M) communication is emerging as an important application of a communication network. Despite the opportunity, accommodating a large number of machines in a communication network is a challenge for network operators. This disclosure provides systems and methods for efficiently accommodating M2M communication in a communication network.

## Claims

### Claim 1

A method comprising:
maintaining mobility information at a Mobility Management Entity (MME) in a communication network, wherein the MME is associated with at least one mobile device including a first mobile device and the mobility information includes mobility management context associated with the first mobile device;
initiating a network session termination procedure to cause a release of resources associated with the first mobile device;
in response to a location update request message from the first mobile device, executing a location update procedure using the mobility information associated with the first mobile device and maintaining location information of the first mobile device;
receiving a paging trigger message initiated by an application server, wherein the paging trigger message includes an identification of the first mobile device to indicate that the first mobile device be paged; and
sending a paging request message to the first mobile device to cause the first mobile device to attach to the communication network to accommodate data communication with the application server.

### Claim 2 (depends on 1)

The method of claim 1, further comprising analyzing subscription information associated with the first mobile device in order to select a location server for the first mobile device, wherein the subscription information is received from a home subscriber server (HSS).

### Claim 3 (depends on 1)

The method of claim 1, further comprising receiving a service request message from the first mobile device and sending a service rejection message to the first mobile device, wherein the service rejection message indicates that the first mobile device be attached to the communication network before requesting for service.

### Claim 4 (depends on 1)

The method of claim 1, wherein the paging request message includes a system architecture evolution-temporary mobile subscriber identity (S-TMSI) of the first mobile device assigned by the MME.

### Claim 5 (depends on 1)

The method of claim 1, wherein the mobile device includes a machine-type communication (MTC) device and the application server includes an MTC server.

### Claim 6 (depends on 1)

The method of claim 1, wherein the network session termination procedure is initiated in response to an expiration of a UE inactivity timer indicating an end of data communication between the first mobile device and the application server.

### Claim 7 (depends on 1)

The method of claim 1, further comprising sending a message to a location server to cause the location server to update location information of the first mobile device, wherein the location server is associated with the application server.

### Claim 8 (depends on 7)

The method of claim 7, wherein the location server is configured to maintain a binding information indicating that the MME is serving the first mobile device.

### Claim 9 (depends on 8)

The method of claim 8, wherein the location server is integrated with the application server to provide an integrated service to the first mobile device.

### Claim 10

An MME comprising:
an interface that is configured to provide communication with a location server and a mobile device;
a memory that is configured to maintain mobility information associated with the mobile device;
a module that is configured to execute a tracking area update (TAU) procedure with the mobile device by accessing the mobility information associated with the mobile device, initiate a network session termination procedure to cause a release of communication resources associated with the mobile device, and send a paging request message to the mobile device to cause the mobile device to attach to a communication network.

### Claim 11 (depends on 10)

The MME of claim 10, wherein the module is further configured to analyze subscription information associated with the first mobile device in order to select a location server for the first mobile device, wherein the subscription information is received from a home subscriber server (HSS).

### Claim 12 (depends on 10)

The MME of claim 10, wherein the module is further configured to receive a paging trigger message initiated by an application server, the paging trigger message indicating that the mobile device be paged.

### Claim 13 (depends on 12)

The MME of claim 12, wherein the paging request message includes a system architecture evolution-temporary mobile subscriber identity (S-TMSI) of the mobile device assigned by the MME.

### Claim 14 (depends on 10)

The MME of claim 10, wherein the module is further configured to send a message to the location server to cause the location server to update location information associated with the mobile device.

### Claim 15 (depends on 10)

The MME of claim 10, wherein the location server is configured to maintain a binding information indicating that the MME is serving the mobile device.

### Claim 16 (depends on 10)

The MME of claim 10, wherein the network session termination procedure is initiated in response to an expiration of a timer indicating an end of data communication between the first mobile device and the application server.

### Claim 17 (depends on 10)

The MME of claim 10, wherein the mobile device executing the TAU procedure with the module is in an idle state.

### Claim 18

Logic encoded on one or more tangible media for execution and when executed operable to:
maintain mobility information in a communication network, wherein the mobility information includes mobility management context associated with a mobile device;
initiate a network session termination procedure to trigger release of communication resources associated with the mobile device;
in response to a location update request message from the mobile device, execute a location update procedure using the mobility information associated with the mobile device;
maintain location information of the mobile device;
receive a paging trigger message initiated by an application server, wherein the paging trigger message includes an identification of the mobile device indicating that the mobile device be paged; and
send a paging request message to the mobile device to cause the mobile device to attach to the communication network and to cause the mobile device to accommodate data communication with the application server.

### Claim 19 (depends on 18)

The logic of claim 18, wherein the paging request message includes a system architecture evolution-temporary mobile subscriber identity (S-TMSI) of the mobile device assigned by an MME.

### Claim 20 (depends on 18)

The logic of claim 18, further operable to send a message to a location server to cause the location server to update location information of the mobile device.
