# US 2015/0103766 A1 · Technique for Data-Over-NAS Signalling

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

- Number: US 2015/0103766 A1
- Document ID: US20150103766A1
- Status: Published application
- Kind: A1
- Application number: 14/387,401
- Filed: 2012-03-30
- Published: 2015-04-16
- Earliest claimed: 2012-03-30
- Assignees: Telefonaktiebolaget L M Ericsson (publ)
- Inventors: György Miklós; Rikard Eriksson; Johan Rune; Joachim Sachs
- Web page: https://patentgrep.com/patent/US20150103766A1

## CPC

- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 76/20: Manipulation of established connections
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A technique for signalling activation or deactivation of a data-over-non-access-stratum, NAS, transmission scheme is disclosed, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode. In a method aspect, there are steps of determining a trigger condition indicating a need for the data-over-NAS transmission scheme, and signalling an indication for activation or deactivation in response to fulfilment or non-fulfilment of the determined trigger condition. In another method aspect, there may be steps of receiving the indication for activation or deactivation, and activating or deactivating the data-over-NAS transmission scheme in response to the signalled indication.

## Claims

### Claim at position 1

1-33. (canceled)

### Claim 34

A method for signalling activation or deactivation of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, wherein the method comprises:
determining a trigger condition indicating a need for the data-over-NAS transmission scheme; and
signalling, during transition from the idle mode to a connected mode, an indication for activation or deactivation in response to fulfilment or non-fulfilment of the determined trigger condition,
wherein activating includes activating the data-over-NAS transmission scheme on a first subset of bearers, and deactivating includes deactivating the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 35 (depends on 34)

The method according to claim 34, wherein the determining step comprises matching at least one data packet against a filter, and wherein the signalling step is performed responsive to a determination that the at least one uplink or downlink data packet matches the filter.

### Claim 36 (depends on 35)

The method according to claim 35, wherein the filter further comprises one of the following:
a timeout threshold, wherein matching includes matching all data packets against the filter before the timeout threshold is reached;
a size threshold of a number of bytes, wherein matching includes matching byte sizes of all data packets against the filter before a timeout is reached; and
a Token Bucket.

### Claim 37 (depends on 36)

The method according to claim 36, wherein a Mobility Management Entity (MME) comprises the filter, and the method further comprises:
maintaining, by the MME, at least one bearer for a predetermined period of time when the data packet traffic reaches the threshold; and
establishing, by the MME, the at least one bearer in the connected mode responsive to a determination that the data packet traffic still reaches the threshold when the predetermined period of time has passed.

### Claim 38 (depends on 34)

The method according to claim 34, wherein the determining step is performed by the terminal.

### Claim 39 (depends on 34)

The method according to claim 34, wherein the determining step is performed by at least one of a Packet Data Network Gateway (PGW) and Serving Gateway (SGW).

### Claim 40 (depends on 34)

The method according to claim 34, wherein the determining step is performed by a Mobility Management Entity (MME).

### Claim 41 (depends on 34)

The method according to claim 34, wherein the signalling step is performed by a Packet Data Network Gateway (PGW) and comprises signalling the indication to the terminal via an Update Bearer Request message and a Downlink NAS Transport message.

### Claim 42 (depends on 34)

The method according to claim 34, wherein the signalling step is performed in the terminal and comprises signalling the indication to a Mobility Management Entity (MME) via the base station via an Update Delivery Method Request message and an Update Delivery Method Response message.

### Claim 43 (depends on 34)

The method according to claim 34, wherein the signalling step is performed in a Mobility Management Entity (MME) and comprises signalling the indication to the terminal via an Update Delivery Method Request message and an Update Delivery Method Response message, both messages being initially transmitted by the MME.

### Claim 44 (depends on 34)

The method according to claim 34, further comprising:
routing the data packets over at least one bearer, comprising:
accommodating at least one of the data packets in NAS signalling-related messages during establishment of the at least one bearer in the connected mode; and
routing subsequent data packets over the at least one bearer in the connected mode upon completion of the establishment.

### Claim 45 (depends on 44)

The method according to claim 44, further comprising:
determining whether substantially all data packets in a given communication are to be transmitted using the data-over-NAS transmission scheme; and
aborting the establishment responsive to an affirmative determination.

### Claim 46

A method for activating or deactivating of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, wherein the method comprises:
receiving, during transition from the idle mode to a connected mode, an indication for activation or deactivation; and
activating or deactivating the data-over-NAS transmission scheme in response to the indication,
wherein activating includes activating the data-over-NAS transmission scheme on a first subset of bearers, and deactivating includes deactivating the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 47 (depends on 46)

The method according to claim 46, further comprising:
routing, after activation of the data-over-NAS transmission scheme on at least one bearer, the data packets over the at least one bearer.

### Claim 48 (depends on 47)

The method according to claim 47, wherein the data packets are transmitted on an uplink of the at least one bearer.

### Claim 49 (depends on 48)

The method according to claim 48, wherein the determining step comprises thresholding uplink traffic against a traffic volume threshold, and if a traffic volume of the uplink traffic is below the traffic volume threshold, the data-over-NAS transmission scheme is used, and if the traffic volume is equal to or greater than the traffic volume threshold, the data packets are transmitted over at least one bearer established in the connected mode.

### Claim 50 (depends on 48)

The method according to claim 48, further comprising a separate Packet Data Network (PDN) connection involving a first bearer and a second bearer, wherein individual Internet Protocol (IP) addresses are respectively assigned to the first and second bearers, and wherein only one of the first and second bearers employs the data-over-NAS transmission scheme.

### Claim 51 (depends on 47)

The method according to claim 47, wherein the data packets are transmitted on a downlink of the bearer.

### Claim 52 (depends on 51)

The method according to claim 51, further comprising transmitting the data packet from a Mobility Management Entity (MME) to the terminal by:
paging the terminal responsive to a determination that the terminal is not in the connected mode;
receiving, at the MME, a Service Request message responsive to the paging; and
establishing a connection via the Evolved Packet System (EPS) S1 interface, wherein S1 is an interface between the base station and the MME for the control plane between the base station and the MME.

### Claim 53 (depends on 47)

The method according to claim 47, wherein the routing step comprises utilizing a radio bearer established in the connected mode for transmitting the data packets assigned to the data-over-NAS transmission scheme.

### Claim 54 (depends on 47)

The method according to claim 47, wherein the routing is at least partially performed between a Serving Gateway (SGW) to a Mobility Management Entity (MME).

### Claim 55 (depends on 54)

The method according to claim 54, further comprising:
establishing a GTP-U tunnel between the MME and the SGW based on signalling on a S11 interface, wherein GTP-U corresponds to a user plane of a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP), and the S11 interface corresponds to an interface between the MME and the SGW in Evolved Packet System (EPS).

### Claim 56 (depends on 55)

The method according to claim 55, further comprising:
utilizing S1-U tunnelling between the MME and the SGW, wherein S1-U corresponds to a user-plane part of an S1 interface, and wherein the S1 interface corresponds to and interface between the Radio Access Network and the Core Network in EPS.

### Claim 57 (depends on 54)

The method according to claim 54, further comprising:
extending a GTP-C protocol on a S11 interface by a functionality of carrying the data packets, wherein GTP-C corresponds to a control plane of a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP), and the S11 interface corresponds to an interface between the MME and the SGW in Evolved Packet System (EPS).

### Claim 58 (depends on 54)

The method according to claim 54, further comprising:
accommodating the data packets in a Downlink Data Notification message.

### Claim 59 (depends on 46)

The method according to claim 46, further comprising:
releasing Radio Resource Control (RRC) and an S1 connection upon completion of the data-over-NAS transmission scheme, wherein S1 is an interface between the base station and a Mobility Management Entity (MME) for a control plane between the base station and the MME.

### Claim 60 (depends on 59)

The method according to claim 59, wherein the MME releases the S1 connection upon reception of a release indication.

### Claim 61 (depends on 60)

The method according to claim 60, further comprising:
accommodating the release indication in a data-over-NAS message.

### Claim 62

A non-transitory computer readable medium storing a computer program for signalling activation or deactivation of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, the computer program comprising program instructions that, when executed on at least one processor, cause the at least one processor to:
determine a trigger condition indicating a need for the data-over-NAS transmission scheme; and
signal, during transition from the idle mode to a connected mode, an indication for activation or deactivation in response to fulfilment or non-fulfilment of the determined trigger condition,
wherein activation includes activation of the data-over-NAS transmission scheme on a first subset of bearers, and deactivation includes deactivation of the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 63

A non-transitory computer readable medium storing a computer program for activating or deactivating of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, the computer program comprising program instructions that, when executed on at least one processor, cause the at least one processor to:
receive, during transition from the idle mode to a connected mode, an indication for activation or deactivation; and
activate or deactivate the data-over-NAS transmission scheme in response to the indication,
wherein activation includes activation of the data-over-NAS transmission scheme on a first subset of bearers, and deactivation includes deactivation of the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 64

A network entity for signalling activation or deactivation of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, wherein the network entity is configured to:
determine a trigger condition indicating a need for the data-over-NAS transmission scheme; and
signal, during transition from the idle mode to a connected mode, an indication for activation or deactivation in response to fulfilment or non-fulfilment of the determined trigger condition, wherein activation includes activation of the data-over-NAS transmission scheme on a first subset of bearers, and deactivation includes deactivation of the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 65

A network entity for activation or deactivation of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, wherein the network entity is configured to:
receive, during transition from the idle mode to a connected mode, an indication for activation or deactivation; and
activate or deactivate the data-over-NAS transmission scheme in response to the indication, wherein activation includes activation of the data-over-NAS transmission scheme on a first subset of bearers, and deactivation includes deactivation of the data-over-NAS transmission scheme on a second subset of bearers different from the first subset.

### Claim 66

A network system comprising:
a network entity for signalling activation or deactivation of a data-over-non-access-stratum (NAS) transmission scheme, the transmission scheme being for transmitting data packets over the NAS between a terminal and a base station, and being started in an idle mode, wherein the network entity for signalling activation or deactivation is configured to:
determine a trigger condition indicating a need for the data-over-NAS transmission scheme; and
signal, during transition from the idle mode to a connected mode, an indication for activation or deactivation in response to fulfilment or non-fulfilment of the determined trigger condition, wherein activation includes activation of the data-over-NAS transmission scheme on a first subset of bearers, and deactivation includes deactivation of the data-over-NAS transmission scheme on a second subset of bearers different from the first subset; and
network entity for activation or deactivation of the data-over-NAS transmission scheme configured to:
receive, during transition from the idle mode to the connected mode, the indication for activation or deactivation; and
activate or deactivate the data-over-NAS transmission scheme in response to the indication.
