# US 2017/0303139 A1 · Methods and systems for providing standalone LTE based communication networks

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

- Number: US 2017/0303139 A1
- Document ID: US20170303139A1
- Status: Published application
- Kind: A1
- Application number: 15/636,033
- Filed: 2017-06-28
- Published: 2017-10-19
- Earliest claimed: 2017-05-17
- Assignees: Indian Institute of Technology Bombay
- Applicants: Indian Institute of Technology Bombay
- Inventors: Abhay Karandikar; Pranav Kumar Jha; Karunakaran Kumar; Pon Nidhya Elango; Pravin P. Magar; Shahid A. Nadaf; Meenakshi Tripathi; Akshatha Nayak M
- Web page: https://patentgrep.com/patent/US20170303139A1

## CPC

- H04L 65/1063: Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42)
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L 65/80: Responding to QoS
- H04W 16/02: Resource partitioning among network components, e.g. reuse partitioning
- H04W 16/18: Network planning tools
- H04W 24/02: Arrangements for optimising operational condition
- H04W 40/12: based on transmission quality or channel quality
- H04W 74/0833: Random access procedures, e.g. with 4-step access
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W 84/10: Small scale networks; Flat hierarchical networks
- H04W 88/02: Terminal devices
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Standalone LTE based communication networks. Embodiments herein disclose methods and systems for providing LTE based communication to at least one User Equipment (UE) over a small region using a rapidly deployable standalone network wherein at least one LTE UE would be able to connect to an Application Server (AS).

## Claims

### Claim 1

An apparatus (101) in a Long Term Evolution (LTE) communication network, the network comprising the apparatus (101) connected to at least one User Equipment (UE) (102) using a LTE over-the-air interface and to an Application Server (AS) (103) using an Internet Protocol (IP) based link, wherein the apparatus (101) comprises of a convergence layer (209) configured for sending IP packets from the UE (102) directly to the AS (103) through the IP based link.

### Claim 2 (depends on 1)

The apparatus, as claimed in claim 1, wherein the apparatus (101) is configured to perform the responsibilities of a traditional LTE eNB and Core Network (CN) nodes for enabling the communication with the UE (102), wherein the UE (102) does not require any changes to communicate with the apparatus (101).

### Claim 3 (depends on 2)

The apparatus, as claimed in claim 2, wherein the apparatus (101) is configured to perform the functionality of LTE entities, the LTE entities comprising a eNodeB, a LTE Mobility Management Entity (MME), a LTE Serving Gateway (SGW), a LTE Packet Data Network (PGW), a Home subscriber Server (HSS) and a Policy and Charging Rules Function (PCRF).

### Claim 4 (depends on 1)

The apparatus, as claimed in claim 1, wherein the apparatus (101) is connected to the Application Server (AS) (103) using an SGi interface.

### Claim 5 (depends on 1)

The apparatus, as claimed in claim 1, wherein the apparatus (101) comprises of control plane and data plane entities (201, 202).

### Claim 6 (depends on 5)

The apparatus, as claimed in claim 5, wherein the control plane (201) and the data plane (202) are separated based on the paradigm of Software Defined Networking (SDN).

### Claim 7 (depends on 5)

The apparatus, as claimed in claim 5, wherein the control plane (201) comprises of a control application (203), a Non-Access Stratum (NAS) layer (204), a Radio Resource Control (RRC) layer (205), a HSS layer (206), a PCRF layer (207), and a Dynamic Host Configuration Protocol (DHCP) server (208).

### Claim 8 (depends on 5)

The apparatus, as claimed in claim 5, wherein the data plane (202) comprises of a LTE eNodeB radio protocol stack for a radio interface towards the UE (102), a Convergence Layer (209), a Layer 2 (214) and a Layer 1 (215) of IP infrastructure for an interface towards the AS (103).

### Claim 9 (depends on 8)

The apparatus, as claimed in claim 8, wherein the LTE radio interface stack in the data plane (202) further comprises a Packet Data Convergence Protocol (PDCP) layer (210), a Radio Link Control (RLC) layer (211), a Media Access Control (MAC) layer (212), and a Physical (PHY) layer (213).

### Claim 10 (depends on 8)

The apparatus, as claimed in claim 8, wherein the convergence layer (209) is configured to route IP packets between the UE (102) and the AS (103), wherein the convergence layer (209) is configured to interface with the LTE radio protocol stack and send packets received from the UE (102) via the radio protocol stack to the AS (103) over the SGi interface.

### Claim 11 (depends on 8)

The apparatus, as claimed in claim 8, wherein the convergence layer (209) is configured to route IP packets between the AS (103) and the UE (102), wherein the convergence layer (209) is configured to send packets received from the AS (103) over the SGi interface to the UE (102) via the radio protocol stack.

### Claim 12 (depends on 8)

The apparatus, as claimed in claim 8, wherein the convergence layer (209) is configured to maintain a one-to-one routing map between LTE EPS bearer identifiers and traffic flow templates for at least one UE (102), to route IP packets between the UE (102) and the apparatus (101) over various bearers and ensure QoS requirements enforced by the PCRF layer (207).

### Claim 13 (depends on 1)

The apparatus, as claimed in claim 1, wherein the apparatus (101) does not comprise of S1 Application Protocol (S1AP), X2 Application Protocol (X2AP), Stream Control Transmission Protocol (SCTP) and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) layer for the Control Plane (GTP-C) layers.

### Claim 14

A method for providing Long Term Evolution (LTE) based communication using a LTE communication network, the network comprising an integrated Core and Access Module (iCAM) module (101) connected to at least one User Equipment (UE) (102) using a LTE over-the-air interface and to an Application Server (AS) (103) using an Internet Protocol (IP) based link, the method comprising
Performing signaling functions of a LTE eNodeB, LTE Mobility Management Entity (MME), LTE Serving Gateway (SGW) and the LTE Packet Data Network (PGW) by a control plane (201) in the iCAM module (101); and
performing data forwarding between the UE (102) and the AS (103) by a convergence layer (209) in a data plane (202) in the iCAM module (101).

### Claim 15 (depends on 14)

The method, as claimed in claim 14, wherein the iCAM module (101) does not comprise of S1 Application Protocol (S1AP), X2 Application Protocol (X2AP), Stream Control Transmission Protocol (SCTP) and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) layer for the Control Plane (GTP-C) layers.

### Claim 16 (depends on 14)

The method, as claimed in claim 14, wherein the convergence layer (209) directly routes data between the UE (102) and the AS (103).

### Claim 17 (depends on 14)

The method, as claimed in claim 14, wherein the convergence layer (209) serves as an interface between a LTE eNodeB radio protocol stack and infrastructure on an interface with the AS (103).

### Claim 18 (depends on 17)

The method, as claimed in claim 17, wherein the method further comprises of a control application (203) configuring the radio protocol stack layers.

### Claim 19 (depends on 18)

The method, as claimed in claim 18, wherein the method further comprises of the control application (203) configuring the convergence layer (209) by controlling its routing map between LTE Evolved Packet System (EPS) bearer identifiers and traffic flow templates, based on the inputs from a Policy and Charging Rules Function (PCRF) layer (207).
