# US 8,787,311 B2 · Technique for AT command handling in relation to an EPS packet domain

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

- Number: US 8,787,311 B2
- Document ID: US8787311B2
- Status: Granted
- Kind: B2
- Application number: 13/120,970
- Filed: 2009-08-07
- Published: 2011-09-29
- Granted: 2014-07-22
- Earliest claimed: 2008-09-29
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Jürgen Lerzer; Matthias Grimm; Michael Hohner; Reinhold Schneider
- Inventors: Jürgen Lerzer; Matthias Grimm; Michael Hohner; Reinhold Schneider
- Web page: https://patentgrep.com/patent/US8787311B2

## CPC

- H04W 36/0022: {for transferring data sessions between adjacent core network technologies}
- H04W 28/0252: {per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12)}
- H04W 36/1443: {between licensed networks}
- H04W 76/11: Allocation or use of connection identifiers
- H04W 36/0033: {with transfer of context information}
- H04W 76/12: Setup of transport tunnels
- H04W 76/15: Setup of multiple wireless link connections
- H04W 88/02: Terminal 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 method and system of facilitating the use of AT commands specified for a General Packet Radio Service (GPRS) packet domain in relation to an Evolved Packet System (EPS) packet domain is provided. An embodiment of the present invention comprises defining, in response to an AT command directed to the definition of a secondary Packet Data Protocol (PDP) context, an EPS Service Data Flow (SDF) on the basis of the secondary PDP context.

## Claims

### Claim 1

A method of facilitating the use of AT commands specified for a General Packet Radio Service, or GPRS, packet domain in relation to an Evolved Packet System, EPS, packet domain, the method comprising:
defining, using a microprocessor, in response to an AT command directed to the definition of a secondary Packet Data Protocol, or PDP, context, an EPS Service Data Flow, or SDF, on the basis of the secondary PDP context.

### Claim 2 (depends on 1)

The method of claim 1, wherein the EPS SDF is defined within an existing Packet Data Network, or PDN, connection.

### Claim 3 (depends on 1)

The method of claim 1, wherein each AT command includes a Context Identification, or CID, parameter as reference to the PDP context.

### Claim 4 (depends on 3)

The method of claim 3, further comprising
using the CID parameter included in the AT command as reference to the EPS SDF.

### Claim 5 (depends on 3)

The method of claim 3, further comprising:
using the CID parameter of an EPS default bearer associated with the EPS SDF to link the EPS SDF to a Packet Data Network, or PDN, connection associated with the EPS default bearer.

### Claim 6 (depends on 1)

The method of claim 1 , further comprising:
defining, in response to an AT command directed to the definition of a non-secondary PDP context, an EPS default bearer on the basis of the non-secondary PDP context.

### Claim 7 (depends on 3)

The method of claim 3, further comprising:
using the CID parameter included in the AT command as reference to an EPS default bearer.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
providing a mechanism for defining an EPS dedicated bearer.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
defining the EPS dedicated bearer in response to an AT command including a Context Identification, or CID, parameter; and
using the CID parameter included in the AT command as a reference to the EPS dedicated bearer.

### Claim 10 (depends on 3)

The method of claim 3, wherein an EPS bearer and one or more SDFs on the EPS bearer have been established, and wherein the EPS bearer and the one or more SDFs on the EPS bearer are referenced by dedicated CIDs.

### Claim 11 (depends on 1)

The method of claim 1, wherein the method is performed in an Long Term Evolution, or LTE, mode of a user terminal additionally supporting a legacy UMTS mode.

### Claim 12 (depends on 11)

The method of claim 11, further comprising in the legacy UMTS mode:
interpreting each AT command in a manner specified for the GPRS packet domain.

### Claim 13 (depends on 11)

The method of claim 11, wherein the user terminal is capable of performing at least one of a handover and Radio Access Technology, or RAT, change between LTE network access and legacy UMTS network access, and further comprising:
mapping, in a handover scenario in which n PDP contexts have been defined and n EPS SDFs are associated with one EPS bearer in the EPS packet domain before the handover, the n PDP contexts on one PDP context towards the GPRS packet domain.

### Claim 14 (depends on 1)

The method of claim 1, further comprising providing a conversion logic between GPRS Quality of Service, or QoS, profiles and EPS QoS profiles.

### Claim 15 (depends on 14)

The method of claim 14, wherein the GPRS QoS profiles are compliant with a 3GPP Release 7 or earlier QoS profile and the EPS QoS profiles are compliant with a 3GPP Release 8 or later QoS profile.

### Claim 16 (depends on 14)

The method of claim 14, wherein the conversion logic is used in response to an AT command specifying a QoS profile.

### Claim 17 (depends on 16)

The method of claim 16, wherein the AT command is any of +CGEQREQ, +CGEQMIN, +CGEQOS and +CGEQOSRDP AT commands.

### Claim 18 (depends on 1)

The method of claim 1, further comprising:
providing support for at least one of +CGCMOD AT command and +CGTFT AT command.

### Claim 19 (depends on 1)

The method of claim 1, further comprising:
providing support for +CGACT AT command.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
sending a message relating to an activation of a bearer resource upon activation of the EPS SDF; or
sending a message relating to a release of a bearer resource upon deactivation of the EPS SDF.

### Claim 21 (depends on 5)

The method of claim 5, further comprising
sending a PDN connectivity request message upon activation of the EPS default bearer; or
sending a PDN disconnect request message upon deactivation of the EPS default bearer.

### Claim 22 (depends on 1)

The method of claim 1, wherein the AT command is received from, requested by or triggered by an application.

### Claim 23 (depends on 22)

The method of claim 22, wherein the application is agnostic of whether a connection to the GPRS packet domain or the EPS packet domain exists.

### Claim 24 (depends on 22)

The method of claim 22, wherein the application is configured to dedicatedly handle EPS dedicated bearers.

### Claim 25

A non-transitory computer computer-readable storage medium further comprising computer-readable instructions, when executed by a microprocessor, are configured to:
define, in response to an AT command directed to the definition of a secondary Packet Data Protocol, or PDP, context, an EPS Service Data Flow, or SDF, on the basis of the secondary PDP context.

### Claim 26

A device for facilitating the use of AT commands specified for a General Packet Radio Service, or GPRS, packet domain in relation to an Evolved Packet System, EPS, packet domain, the device comprising:
a component adapted to define, in response to an AT command directed to the definition of a secondary Packet Data Protocol, or PDP, context, an EPS Service Data Flow, or SDF, on the basis of the secondary PDP context.

### Claim 27 (depends on 26)

The device of claim 26, wherein the EPS SDF is defined within an existing Packet Data Network, or PDN, connection.

### Claim 28 (depends on 26)

The device of claim 26, wherein each AT command includes a Context Identification, or CID, parameter as reference to the PDP context.

### Claim 29 (depends on 28)

The device of claim 28, further comprising
a component adapted to use the CID parameter included in the AT command as reference to the EPS SDF.

### Claim 30 (depends on 26)

The device of claim 26, further comprising:
a component adapted to define, in response to an AT command directed to the definition of a non-secondary PDP context, an EPS default bearer on the basis of the non-secondary PDP context.

### Claim 31 (depends on 28)

The device of claim 28, further comprising:
a component adapted to use the CID parameter included in the AT command as reference to the EPS default bearer.

### Claim 32 (depends on 31)

The device of claim 31, further comprising:
a component adapted to use the CID parameter included in the AT command as linkage to a Packet Data Network, or PDN, connection associated with an EPS default bearer.

### Claim 33 (depends on 26)

A user terminal comprising the device of claim 26.