# US 2016/0262190 A1 · Establishing network connectivity for transmitting network traffic to or from machine devices

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

- Number: US 2016/0262190 A1
- Document ID: US20160262190A1
- Status: Published application
- Kind: A1
- Application number: 14/698,499
- Filed: 2015-04-28
- Published: 2016-09-08
- Earliest claimed: 2015-03-02
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Nabil N. BITAR; Kumar K. VISHWANATHAN
- Web page: https://patentgrep.com/patent/US20160262190A1

## CPC

- H04W 76/12: Setup of transport tunnels
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A machine management system provides a system and method for communicating user data with a device connected to a network. The device may register for service by the network, causing the machine management system to establish a special communications path through the network when it is determined that the device is a machine device. Thereafter, user data transmitted by the machine device (or transmitted to the machine device) may be communicated using the special communications path. In certain embodiments, the special communications path may be established such that existing network elements are not involved in the transmission of communications with the machine devices, thereby minimizing the impact on implementing the system and method on existing network elements, alleviating the burden of serving these machine devices using existing network elements and permitting the implementation of device-specific services for machine devices.

## Claims

### Claim 1

A system, comprising:
a user equipment (UE) device;
an eNodeB communicatively connected to the UE device via a radio access network (RAN); and
a machine management system (MMS) communicatively connected to the eNodeB via an S1-MME interface,
wherein the UE device transmits an uplink non-access stratum (NAS) message to the eNodeB over the RAN, the uplink NAS message encapsulating an uplink user data message and including one or more device identifiers of the UE device and a header field indicating that the uplink NAS message contains the encapsulated uplink user data message;
wherein the eNodeB receives the uplink NAS message and forwards to the MMS based on the at least one of the one or more device identifiers over the S1-MME interface;
wherein the MMS receives the uplink NAS message, determines that the uplink NAS message encapsulates the uplink user data message based on the header field, performs de-encapsulation to retrieve the uplink user data message, and forwards the uplink user data message via a network interface to a network.

### Claim 2 (depends on 1)

The system of claim 1,
wherein the MMS receives a downlink user data message from the network through the network interface, the downlink user data message containing at least one of the one or more device identifiers of the UE device, determines based on the at least one device identifier that the UE device is registered to receive messages through the MMS and that the UE is served by the eNodeB, encapsulates the downlink user data message within a downlink NAS message and including the at least one device identifier and the header field indicating that the downlink NAS message contains the encapsulated downlink user data message, and sends the downlink NAS message to the eNodeB through the S1-MME interface,
wherein the eNodeB receives the downlink NAS message and forwards to the UE device over the RAN,
wherein the UE device receives the downstream NAS message, determines that the downlink NAS message encapsulates the downlink user data message based on the header field, and performs de-encapsulation to retrieve the downlink user data message.

### Claim 3 (depends on 1)

The system of claim 1, wherein the uplink NAS message includes lower level protocols containing at least one of the one more device identifiers, and the eNodeB forwards the uplink NAS message to the MMS based on the at least one device identifier present in the lower level protocols.

### Claim 4 (depends on 3)

The system of claim 3, wherein the at least one device identifier is a Public Land Mobile Network ID (PLMN-ID) and the lower level protocols include a Radio Resource Control (RRC) protocol containing the PLMN-ID.

### Claim 5

A method, comprising:
receiving at a machine management system (MMS) from an eNodeB over a first interface an uplink non-access stratum (NAS) message, the uplink NAS message including an uplink user data message encapsulated within the uplink NAS message, the uplink user data message including a destination identifier associated with a destination,
determining at the MMS that the uplink NAS message contains the uplink user data message;
when the uplink NAS message contains the uplink user data message, performing de-encapsulation at the MMS to obtain the uplink user data message, and forwarding the uplink user data message over a second interface to a network for delivery to the destination.

### Claim 6 (depends on 5)

The method of claim 5, wherein determining at the MMS that the uplink NAS message encapsulates the uplink user data message includes checking a field of the uplink NAS message for an indicator that the uplink NAS message encapsulates the uplink user data message.

### Claim 7 (depends on 6)

The method of claim 6, wherein the field of the uplink NAS message is a protocol discriminator field.

### Claim 8 (depends on 5)

The method of claim 5, wherein the first interface is an S1-MME interface, and the second interface is a network interface.

### Claim 9 (depends on 5)

The method of claim 5, further comprising:
receiving at the eNodeB a registration request from a user equipment (UE) device, the registration request including one or more registration NAS messages and one or more device identifiers;
determining at the eNodeB whether the registration request should be forwarded to the MMS or a mobility management entity (MME);
forwarding the registration request to MMS and not to the MME.

### Claim 10 (depends on 9)

The method of claim 9, wherein determining whether the registration request should be forwarded to the MMS or MME includes at least one of: comparing at least one of the one or more device identifiers to stored device identifiers that are associated with the MMS; and determining that the at least one device identifier indicates that the UE device is associated with the MMS.

### Claim 11 (depends on 10)

The method of claim 10, wherein the one or more device identifiers include an International Mobile Subscriber Identity (IMSI), and determining that the at least one device identifier indicates that the UE device is associated with the MMS includes determining whether a Public Land Mobile Network ID (PLMN-ID) portion of the IMSI has been previously designated as being associated with the MMS.

### Claim 12 (depends on 5)

The method of claim 5, further comprising:
receiving a downlink message from the network through the second interface, the downlink message containing a device identifier of a user equipment (UE) device;
determining whether the UE device is registered to receive messages and how to deliver messages;
encapsulating the downlink message within a downlink NAS message;
sending the downlink NAS message to the eNodeB through the first interface for delivery to the UE device.

### Claim 13 (depends on 12)

The method of claim 12, wherein encapsulating the downlink message within the downlink NAS message includes providing an indicator in a field of the downlink NAS message indicating that the downlink NAS message encapsulates the downlink message.

### Claim 14 (depends on 12)

The method of claim 12, wherein determining whether the UE device is registered to receive messages and how to deliver messages includes checking at the MMS for registration information associated with the UE device and determining at the MMS station information associated with the eNodeB.

### Claim 15

A system, comprising:
an S1-MME interface communicatively connected to an eNodeB;
an network interface communicatively connected to a network;
one or more processors, coupled to the S1-MME interface and the network interface, to:
receive an uplink non-access stratum (NAS) message from the eNodeB through the S1-MME interface;
determine whether the uplink NAS message encapsulates an uplink message having a destination identifier associated with a destination;
de-encapsulate the uplink NAS message to retrieve the uplink message;
forward the uplink message to the network through the network interface toward the destination.

### Claim 16 (depends on 15)

The system of claim 15, wherein the one or more processors are further to:
receive a downlink message from the network through the network interface, the downlink message containing a device identifier of a user equipment (UE) device;
determine whether the UE device is registered to receive messages and how to deliver messages;
encapsulate the downlink message within a downlink NAS message;
send the downlink NAS message to the eNodeB through the S1-MME interface for delivery to the UE device.

### Claim 17 (depends on 16)

The system of claim 16, wherein encapsulating the downstream message within the downstream NAS message includes providing an indicator in a field of the downstream NAS message indicating that the downstream message is encapsulated in the downstream NAS message.

### Claim 18 (depends on 16)

The system of claim 16, wherein determining whether the UE device is registered to receive messages and how to deliver messages includes checking for registration information associated with the UE device and determining station information associated with the eNodeB.

### Claim 19 (depends on 15)

The system of claim 15, wherein determining the uplink NAS message encapsulates the uplink message includes checking a field of the uplink NAS message for an indicator that the uplink NAS message encapsulates the uplink message.

### Claim 20 (depends on 19)

The system of claim 19, wherein the field of the uplink NAS message is a protocol discriminator field.
