Packet data network connections for multi priority wireless devices

• US 9,294,213 B2
• Filed: 12/28/2012
• Issued: 03/22/2016
• Est. Priority Date: 05/11/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Gupta, Vivek, Jain, Puneet K.
• Primary Examiner(s): Patel, Jay P
• Application Number:
  US13/729,568
• Publication Number:
  US 20130301547A1
• Time in Patent Office: 1,180 Days
• Field of Search: 370/329
• US Class Current: 1/1
• CPC Class Codes: H04B 1/56 with provision for simultaneous communication in two directions
• CPC Class Codes: H04B 15/00 Suppression or limitation of noise or interference by means associated with receiver H04B1/10
• CPC Class Codes: H04B 7/024 Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0456 Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
• CPC Class Codes: H04B 7/0473 taking constraints in layer or codeword to antenna mapping into account
• CPC Class Codes: H04B 7/0486 taking channel rank into account
• CPC Class Codes: H04B 7/0626 Channel coefficients, e.g. channel state information [CSI]
• CPC Class Codes: H04B 7/063 Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
• CPC Class Codes: H04B 7/0632 Channel quality parameters, e.g. channel quality indicator [CQI]
• CPC Class Codes: H04B 7/0639 Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
• CPC Class Codes: H04B 7/0647 Variable feedback rate
• CPC Class Codes: H04B 7/065 Variable contents, e.g. long-term or short-short
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04J 3/00 Time-division multiplex systems H04J14/00 takes precedence; relay systems H04B7/14; selecting techniques H04Q
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04J 3/26 in which the information and the address are simultaneously transmitted
• CPC Class Codes: H04L 1/0026 Transmission of channel quality indication
• CPC Class Codes: H04L 1/1803 Stop-and-wait protocols
• CPC Class Codes: H04L 1/1822 involving configuration of automatic repeat request [ARQ] with parallel processes
• CPC Class Codes: H04L 27/2627 : Modulators
• CPC Class Codes: H04L 5/0007 : the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/001 : the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0035 : Resource allocation in a cooperative multipoint environment
• CPC Class Codes: H04L 5/0053 : Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0073 : Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 5/0096 : Indication of changes in allocation
• CPC Class Codes: H04L 5/14 : Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 5/1469 : using time-sharing
• CPC Class Codes: H04L 65/00 : Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04W 16/14 : Spectrum sharing arrangements between different networks
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 36/00 : Hand-off or reselection arrangements
• CPC Class Codes: H04W 36/0055 : Transmission or use of information for re-establishing the radio link
• CPC Class Codes: H04W 36/0061 : of neighbour cell information
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/0094 : Definition of hand-off measurement parameters
• CPC Class Codes: H04W 36/04 : Reselecting a cell layer in multi-layered cells
• CPC Class Codes: H04W 36/16 : Performing reselection for specific purposes
• CPC Class Codes: H04W 36/18 : for allowing seamless reselection, e.g. soft reselection
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 36/30 : by measured or perceived connection quality data
• CPC Class Codes: H04W 36/32 : by location or mobility data, e.g. speed data
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/023 : using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/06 : Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 48/20 : Selecting an access point
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0225 : using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 52/0229 : where the received signal is a wanted signal
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0251 : using monitoring of local events, e.g. events related to user activity
• CPC Class Codes: H04W 56/00 : Synchronisation arrangements
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/12 : Wireless traffic scheduling
• CPC Class Codes: H04W 72/1215 : for collaboration of different radio technologies
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/27 : between access points
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 72/51 : based on terminal or device properties
• CPC Class Codes: H04W 72/54 : based on quality criteria
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 72/56 : based on priority criteria
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/18 : Management of setup rejection or failure
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

A device and method for forming a packet data network (PDN) connection at a dual access priority mode configured user equipment (UE) is disclosed. The method comprises sending, from the UE to a mobility management entity (MME), a PDN connectivity request message that includes a NAS signaling priority override indicator to indicate that the PDN connection has a different NAS signaling priority mode than an existing PDN connection. The existing PDN connection is operating in a first signaling priority mode. The existing PDN connection is deactivated at the UE. A new PDN connection, operating in a second NAS signaling priority mode, is established at the UE.

Claims

1. A mobile station (MS) or user equipment (UE) having a dual access non access stratum (NAS) signaling priority mode, having one or more processors configured to:

send a packet data network (PDN) connectivity request message, a bearer resource modification request message, or a bearer resource allocation request message to a specific Access Point Name (APN) with a low priority indicator set to a status that the MS or UE is configured for NAS signaling low priority;

receive a reject message with an evolved packet system (EPS) session management (ESM) cause value indicating a rejection due to insufficient resources; and

send a PDN connectivity request message to the specific APN with the low priority indicator set to a status that the MS or UE is not configured for NAS signaling low priority,

wherein the PDN connectivity request message includes a device properties information element (IE) to indicate the dual access NAS signaling priority mode of the MS or UE.

2. The MS or UE of claim 1, wherein the one or more processors are further configured to:

determine that a PDN connection exists that is established with the low priority indicator set to a status that the MS or UE is not configured for NAS signaling low priority; and

send a bearer resource modification request message for the PDN connection with the low priority indicator set to a status that the MS or UE is not configured for NAS signaling low priority.

3. The MS or UE of claim 1, wherein the one or more processors are further configured to:

determine that a PDN connection exists that is established with the low priority indicator set to a status that the MS or UE is not configured for NAS signaling low priority; and

send a bearer resource allocation request message for the PDF connection with the low priority indicator set to a status that the MS or UE is not configured for NAS signaling low priority.

4. The MS or UE of claim 1, wherein the one or more processors are further configured to establish multiple PDN connections with different NAS signaling priorities using the specific APN.

5. The MS or UE of claim 1, wherein the MS or UE includes an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port.

24. The MS or UE of claim 1, wherein the one or more processors are further configured to receive the reject message with the evolved packet system (EPS) session management (ESM) cause value indicating the rejection due to insufficient resources and a timer T3396 value.

6. A method for forming a packet data network (PDN) connection at a multi-access priority mode configured user equipment (UE) or mobile station (MS), comprising:

sending, from the UE or MS to a mobility management entity (MME), a PDN connectivity request message that includes a NAS signaling priority override indicator to indicate that the PDN connection has a different NAS signaling priority mode than an existing PDN connection, wherein the NAS signaling priority override indicator is sent in a device properties information element (IE);

deactivating the existing PDN connection with the MME, wherein the existing PDN connection is operating in a first NAS signaling priority mode; and

establishing, at the UE or MS, a new PDN connection for the application, wherein the new PDN connection operates in a second NAS signaling priority mode.

7. The method of claim 6, wherein sending the PDN connectivity request further comprises:

sending the PDN connectivity request message, from the UE or MS, with a same Access Point Name (APN) and PDN type as the existing PDN connection.

8. The method of claim 7, further comprising sending a PDN connectivity request message, from the UE or MS, with the same APN after deactivating the existing PDN connection, to establish the new PDN connection with the MME for the application.

9. The method of claim 7, further comprising sending a PDN connectivity request message, from the UE or MS, with a different APN, to establish the new PDN connection with the MME for the application.

10. The method of claim 6, wherein sending the PDN connectivity request further comprises:

sending the NAS signaling priority override indicator to indicate one of

low priority is not overridden; and

low priority is overridden with normal priority.

11. The method of claim 10, wherein the NAS signaling priority override indicator is sent in bit 2 of octet 1 of a device properties IE.

12. The method of claim 6, wherein sending the PDN connectivity request further comprises:

sending a device properties IE with a low priority indicator to indicate one of;

the UE or MS is not configured for NAS signaling low priority; and

the UE or MS is configured for NAS signaling low priority.

13. The method of claim 12, wherein the NAS signaling priority indicator is sent in bit 1 of octet 1 of the device properties IE.

14. The method of claim 6, wherein sending the PDN connectivity request further comprises sending a device properties IE with a priority indicator to indicate one of a plurality of NAS signaling indicator levels.

15. The method of claim 6, wherein establishing the new PDN connection further comprises:

deactivating evolved packet system (EPS) bearer contexts at the MME for the existing PDN connection without sending a notification to the UE or MS to reduce network overhead in establishing the PDN connection with the different NAS signaling priority mode.

16. The method of claim 6, wherein establishing the new PDN connection further comprises:

receiving, at the UE or MS, a PDN connectivity reject message that multiple PDN connections for a given APN are not allowed.

17. A user equipment (UE) or mobile station (MS) having a dual access non-access stratum (NAS) signaling priority mode with one or more processors configured to:

receive, from a mobility management entity (MME), a packet data network (PDN) connectivity reject message with an evolved packet system (EPS) session management (ESM) cause value indicating a rejection due to insufficient resources and a timer T3396 value in response to a PDN connectivity request message for one of a low priority NAS signaling priority mode and a normal priority NAS signaling priority mode;

stop the timer T3396 when the timer T3396 is running;

start the timer T3396 with a selected value; and

send a PDN connectivity request message with a different NAS signaling priority mode to the MME after the timer T3396 has expired,

wherein a device properties information element (IE) included in the PDN connectivity request message indicates one of the low priority NAS signaling priority mode or the normal priority NAS signaling priority mode.

18. The UE or MS of claim 17, wherein the one or more processors are further configured to:

receive, at the UE or the MS, an attach reject message that is not integrity protected; and

start the timer T3396 with a random value within a selected range.

19. The UE or MS of claim 17, wherein the one or more processors are further configured to:

receive, at the UE or the MS, an attach reject message that is integrity protected;

start the timer T3396 with the timer T3396 value provided in the PDN connectivity reject message.

20. The UE or MS of claim 17, wherein the one or more processors are further configured to start the timer T3396 with the timer T3396 value received from the MME, wherein the timer T3396 value is determined at the MME based on current traffic conditions.

21. The UE or MS of claim 17, wherein the one or more processors are further configured to:

receive a bearer resource allocation reject message from the MME at the UE or the MS with an ESM cause value indicating a rejection due to insufficient resources and a timer T3396 value;

start the timer T3396 with the value provided in a T3396 value information element (IE) in the bearer resource allocation reject message; and

send the PDN connectivity request message, a bearer resource modification request message, or a bearer resource allocation request message after the timer T3396 expires or the timer T3396 is stopped.

22. The UE or MS of claim 17, wherein the one or more processors are further configured to:

receive a bearer resource modification reject message from the MME at the UE or MS with an ESM cause value indicating a rejection due to insufficient resources and a timer T3396 value;

start the timer T3396 with the value provided in a T3396 value information element (IE) in the bearer resource modification reject message; and

send the PDN connectivity request message, a bearer resource modification request message, or a bearer resource allocation request message after the timer T3396 expires or the timer T3396 is stopped.

23. The UE or MS of claim 17, wherein the UE or MS is one of a mobile station (MS) and a machine to machine (M2M) device, and the UE or MS includes an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port.