Browse Prior Art Database

OPTIMIZED DATA TRANSFER IN PACKET CORE FOR MACHINE TYPE COMMUNICATION DEVICES

IP.com Disclosure Number: IPCOM000244414D
Publication Date: 2015-Dec-09

Publishing Venue

The IP.com Prior Art Database

Related People

Hajimulla S: AUTHOR [+8]

Abstract

Mechanisms and systems are provided to attach Machine Type Communication (MTC) devices to Long-Term Evolution (LTE) networks without establishing a bearer. Small volumes of data are transmitted over an existing control path between Mobility Management Entities (MME) and MTC Interworking Function (IWF) after successful attach operation. This approach saves resources needed to establish a Packet Data Network (PDN) context at the Signaling Gateway (SGW) and the Packet Data Network Gateway (PGW) as small data is carried through Network-Attached Storage (NAS) signaling using generic NAS transport containers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 18% of the total text.

Page 01 of 12

OPTIMIZED DATA TRANSFER IN PACKET CORE FOR MACHINE TYPE COMMUNICATION DEVICES

  AUTHORS: Hajimulla S Joe Chemparathy Dhinesh Sivasankar

Mayank Singhal Venkatesh K Pankaj Tripathi Pradeep Vallur Naveen Reddy

CISCO SYSTEMS, INC.

ABSTRACT

    Mechanisms and systems are provided to attach Machine Type Communication (MTC) devices to Long-Term Evolution (LTE) networks without establishing a bearer. Small volumes of data are transmitted over an existing control path between Mobility Management Entities (MME) and MTC Interworking Function (IWF) after successful attach operation. This approach saves resources needed to establish a Packet Data Network (PDN) context at the Signaling Gateway (SGW) and the Packet Data Network Gateway (PGW) as small data is carried through Network-Attached Storage (NAS) signaling using generic NAS transport containers.

DETAILED DESCRIPTION

    Machine Type Communication (MTC) is a form of data communication, which involves one or more entities that do not necessarily need human interaction. MTC is of short duration and involves small and infrequent data transmissions to a MTC server. Whenever a MTC device wants to send any data to the MTC server or vice versa, the MTC device needs to attach to the mobile packet core network and establish a separate data session, even if it is to send only a few bytes of data. The overhead involved in signaling messages for setting up the bearer context is high. This overhead is magnified when a high number of MTC devices are trying to attach to the mobile packet core

Copyright 2015 Cisco Systems, Inc.

1


Page 02 of 12

network simultaneously. The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.682 defines system architecture for MTC. 3GPP architecture for MTC is shown in FIG. 1.

FIG. 1

    3GPP TS 23.682 introduces new interfaces and entities to carry network initiated small data transmissions named "Device Trigger Delivery". Device triggers are delivered as Mobile Terminated (MT) Short Message Services (SMS) (MT SMS) messages via serving nodes Mobility Management Entity (MME) services, Serving General Packet Radio Services (GPRS) Support Node (SGSN) and Mobile Switching Centre (MSC), which provide the service towards specific user equipment (UE).

    In a Long-Term Evolution (LTE) network, the device triggers are directly encapsulated into Network-attached storage (NAS) messages and handled by the MME that forwards the device triggers to a special entity SMS Service Center (SC) (SMS-SC).

Copyright 2015 Cisco Systems, Inc.

2


Page 03 of 12

However, a SMS message size does not typically exceed 140 bytes. This limits the MTC to a small data size to be carried by the mobile network.

    With the current 3GPP architecture, MTC devices need to establish a bearer towards the MTC server for any mobile originated data transfer. Considering the nature of MTC devices, it does not scale as expected with the traditional fourth generation (4G) connection setup procedures. A MTC device ha...