USRE46885E1 - Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same - Google Patents

Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same Download PDF

Info

Publication number
USRE46885E1
USRE46885E1 US14/984,798 US201514984798A USRE46885E US RE46885 E1 USRE46885 E1 US RE46885E1 US 201514984798 A US201514984798 A US 201514984798A US RE46885 E USRE46885 E US RE46885E
Authority
US
United States
Prior art keywords
bearer services
emergency bearer
service
request message
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US14/984,798
Inventor
Kundan Tiwari
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HTC Corp
Original Assignee
HTC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201161454861P priority Critical
Priority to US201161476533P priority
Priority to US13/419,006 priority patent/US8655305B2/en
Application filed by HTC Corp filed Critical HTC Corp
Priority to US14/984,798 priority patent/USRE46885E1/en
Application granted granted Critical
Publication of USRE46885E1 publication Critical patent/USRE46885E1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H04W76/007
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/50Connection management for emergency connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Abstract

A mobile communication device configured for Non Access Stratum (NAS) signaling low priority is provided. In the mobile communication device, a wireless module performs wireless transmissions and receptions to and from a service network, and a controller module originates an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EMM IDLE mode. The controller module further transmits an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to the service network via the wireless module in response to originating the EXTENDED SERVICE REQUEST message.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This Application is a reissue application of U.S. Pat. No. 8,655,305 B2 issued on Feb. 18, 2014. This application claims priority of U.S. Provisional Application No. 61/454,861, filed on Mar. 21, 2011, and the entirety of which is incorporated by reference herein. This Application also claims priority of U.S. Provisional Application No. 61/476,533, filed on Apr. 18, 2011, and the entirety of which is incorporated by reference herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention generally relates to the handling of requests for emergency bearer services, and more particularly, to methods for requesting emergency bearer services for low priority devices, and apparatuses using the same.

2. Description of the Related Art

For a long time, various machines have been provided to make our lives more convenient in every way. Generally, machines, nowadays, are equipped with computing processors and software to accommodate us with more intelligence-based services. With the advancement of wireless communications, Machine Type Communication (MTC) has been developed to enable communications between remote machines for exchanging information and operating without human interaction. Especially for critical public infrastructures, such as water treatment facilities or bridges, MTC sensors may be employed to monitor the operation statuses of facilities and report measurement results back to control centers using various wireless access technologies, such as the Global System for Mobile communications (GSM) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for Global Evolution (EDGE) technology, Wideband Code Division Multiple Access (WCDMA) technology, Code Division Multiple Access 2000 (CDMA-2000) technology, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) technology, Worldwide Interoperability for Microwave Access (WiMAX) technology, Long Term Evolution (LIE) technology, LTE-Advanced technology, and others.

Take the LTE technology in compliance with the 3GPP TS 24.301 specification, v10.3.0 (referred to herein as the TS 24.301 specification) as an example. A low priority indicator or MTC indicator is defined for indicating that a User Equipment (UE) has low priority for Non Access Stratum (NAS) signaling and is generally tolerant to delays. A UE may be configured for NAS signaling low priority when manufactured, and/or when accessing the service network, by Open Mobile Alliance (OMA) Device Management (DM) and/or Subscriber Identity Module/Universal Subscriber Identity Module (SIM/USIM) Over-The-Air (OTA). For a UE configured for NAS signaling low priority (also referred to as a low priority device), the RRC establishment cause used during originating an EXTENDED SERVICE REQUEST message for requesting packet services is always set to “Delay tolerant”, even if the packet services are for emergency bearer services. As a result, the emergency bearer services will not be prioritized as they should be.

BRIEF SUMMARY OF THE INVENTION

In order to solve the above-mentioned problem, the invention proposes to explicitly indicate the emergency case when originating an EXTENDED SERVICE REQUEST message for requesting emergency bearer services, so that the emergency bearer services may be prioritized in the AS layer and/or the NAS layer.

In a first aspect of the invention, a mobile communication device configured for NAS signaling low priority is provided. The mobile communication device comprises a wireless module and a controller module. The wireless module performs wireless transmissions and receptions to and from a service network. The controller module originates an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EMM IDLE mode, and transmits an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to the service network via the wireless module in response to originating the EXTENDED SERVICE REQUEST message.

In a second aspect of the invention, a method for handling a request for emergency bearer services by a mobile communication device configured for NAS signaling low priority is provided. The method comprises the steps of originating an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EMM IDLE mode, and transmitting an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to a service network in response to originating the EXTENDED SERVICE REQUEST message.

In a third aspect of the invention, a mobile communication device configured for NAS signaling low priority is provided. The mobile communication device comprises a wireless module and a controller module. The wireless module performs wireless transmissions and receptions to and from a service network. The controller module originates an EXTENDED SERVICE REQUEST message for requesting emergency bearer services, and includes a service type in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services. Also, the controller module transmits the EXTENDED SERVICE REQUEST message to the service network via the wireless module.

In a fourth aspect of the invention, a method for handling a request for emergency bearer services by a mobile communication device configured for NAS signaling low priority is provided. The method comprises the steps of originating an EXTENDED SERVICE REQUEST message for requesting emergency bearer services, including a service type in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services, and transmitting the EXTENDED SERVICE REQUEST message to a service network.

Other aspects and features of the present invention will become apparent to those with ordinarily skill in the art upon review of the following descriptions of specific embodiments of mobile communication devices and methods for handling a request for emergency bearer services in low priority devices.

BRIEF DESCRIPTION OF DRAWINGS

The invention can be more fully understood by reading the subsequent detailed description and examples with references made to the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrating a mobile communication environment according to an embodiment of the invention;

FIGS. 2A and 2B show a message sequence chart illustrating the handling of a request for emergency bearer services according to an embodiment of the invention;

FIGS. 3A and 3B show a message sequence chart illustrating the handling of a request for emergency bearer services according to another embodiment of the invention;

FIG. 4 is a flow chart illustrating the method for handling a request for emergency bearer services according to an embodiment of the invention; and

FIG. 5 is a flow chart illustrating the method for handling a request for emergency bearer services according to another embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The following description is of the best-contemplated mode of carrying out the invention. This description is made for the purpose of illustrating the general principles of the invention and should not be taken in a limiting sense. Note that the 3GPP specification(s) described herein are used to teach the spirit of the invention, and the invention is not limited thereto.

FIG. 1 is a block diagram illustrating a mobile communication environment according to an embodiment of the invention. In the mobile communication environment 100, the mobile communication device 110 is configured for NAS signaling low priority, and is wirelessly connected to the service network 120 for obtaining wireless services. The service network 120 may comprise an access network 121 and a core network 122, wherein the access network 121 may be an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) which may comprise at least one eNode-B (eNB), and the core network 122 may be an Evolved Packet Core (EPC) in the LTE/LTE-Advanced technology. The mobile communication device 110 comprises a wireless module 111 for performing the functionality of wireless transmissions and receptions to and from the service network 120, and a controller module 112 for controlling the operation of the wireless module 111 to carry out the communications with the service network 120 in compliance with the communication protocol in use. Taking the LIE technology for example, the communication protocol stack may generally comprise a NAS layer and an AS layer, wherein the NAS layer is a functional layer for providing the signaling and traffic between the mobile communication device 110 and the core network 122, and the AS layer is a functional layer for providing the signaling and traffic between the mobile communication device 110 and the access network 121. Also, the controller module 112 may further control the operation of other functional components, such as a display unit and/or keypad serving as the Man-Machine Interface (MMI), a storage unit storing the program codes of applications, or others. To further clarify, the wireless module 111 may be a Radio Frequency (RF) unit, and the controller module 112 may be a general-purpose processor or a Micro-Control Unit (MCU) of a baseband unit. The baseband unit may contain multiple hardware devices to perform baseband signal processing, including analog to digital conversion (ADC)/digital to analog conversion (DAC), gain adjusting, modulation/demodulation, encoding/decoding, and so on. The RF unit may receive RF wireless signals, convert the received RF wireless signals to baseband signals, which are processed by the baseband unit, or receive baseband signals from the baseband unit and convert the received baseband signals to RF wireless signals, which are later transmitted. The RF unit may also contain multiple hardware devices to perform radio frequency conversion. For example, the RF unit may comprise a mixer to multiply the baseband signals with a carrier oscillated in the radio frequency of the mobile communication system, wherein the radio frequency may be 900 MHz, 2100 MHz, or 2.6 GHz utilized in LTE/LTE-Advanced systems, or others depending on the Radio Access Technology (RAT) in use.

To be more specific, the controller module 112 controls the wireless module 111 for handling a request for emergency bearer services. FIGS. 2A and 2B show a message sequence chart illustrating the handling of a request for emergency bearer services according to an embodiment of the invention. In this embodiment, the handling of the request for emergency bearer services takes place in the mobile communication device 110. For brevity, the NAS layer and AS layer of the communication protocol at the side of the mobile communication device 110 are referred to herein as the UE NAS layer and the UE AS layer, respectively. As shown in FIG. 2A, the UE NAS layer is initially in the EPS (Evolved Packet System) Mobility Management (EMM) IDLE mode, and then triggers to initiate emergency bearer services using an EXTENDED SERVICE REQUEST (ESR) message (step S210). In other words, the UE NAS layer originates the EXTENDED SERVICE REQUEST message for requesting emergency bearer services. Next, the UE NAS layer requests the UE AS layer to establish a Radio Resource Control (RRC) connection for the emergency bearer services (step S220). Specifically, the request comprises an RRC establishment cause which is set to “Emergency call”. In response to the request, the UE AS layer transmits to the access network 121 an RRC CONNECTION REQUEST message comprising an establishment cause which is set to “Emergency call” to indicate an emergency case according to the RRC establishment cause (step S230).

When receiving the RRC CONNECTION REQUEST message, the access network 121 recognizes that the request is for an emergency case according to the received establishment cause, so it replies to the UE AS layer with an RRC CONNECTION SETUP message (step S240). The RRC CONNECTION SETUP message may comprise the parameters and configurations for establishing the RRC connection. When receiving the RRC CONNECTION SETUP message, the UE AS layer establishes an RRC connection according to the received parameters and configurations, and then transmits an RRC CONNECTION SETUP COMPLETE message to the access network 121 (step S250), to complete the RRC connection establishment.

Subsequently, the UE AS layer further indicates the completion of the RRC connection establishment to the UE NAS layer (step S260). After that, the UE NAS layer include a service type Information Element (IE) which is set to “packet service via S1 for emergency bearer services” in the EXTENDED SERVICE REQUEST message, and then transmits the EXTENDED SERVICE REQUEST message to the core network 122 (step S270). Thus, with the setting of the establishment cause to “Emergency call”, both of the UE AS layer and the access network 121 (i.e., the AS layer of the communication protocol at the network side) prioritize the connection establishment and so will further prioritize the requested emergency bearer services. In addition, with the setting of the service type to “packet service via S1 for emergency bearer services”, both of the UE NAS layer and the core network 122 (i.e., the NAS layer of the communication protocol at the network side) will prioritize the requested emergency bearer services.

In another embodiment, the service type IE in the EXTENDED SERVICE REQUEST message may be set to “packet service via S1” instead, and the prioritization of the emergency bearer services may be achieved only by the setting of the establishment cause to “Emergency call” in the UE AS layer.

FIGS. 3A and 3B show a message sequence chart illustrating the handling of a request for emergency bearer services according to another embodiment of the invention. Similar to FIGS. 2A and 2B, the handling of the request for emergency bearer services takes place in the mobile communication device 110. In this embodiment, the UE NAS layer may be initially in the EMM IDLE mode or the EMM CONNECTED mode, and then be triggered to establish emergency bearer services using an EXTENDED SERVICE REQUEST message (step S310). For the case of the UE NAS layer being in the EMM IDLE mode, the UE NAS layer may request the UE AS layer to establish an RRC connection for the emergency bearer services, with an RRC establishment cause set to “Delay tolerant” (step S320), and then the UE AS layer may perform a connection establishment procedure according to the RRC establishment cause (steps S330˜S350) and indicate the completion of the connection establishment procedure to the UE NAS layer (step S360). Note that, the steps S320˜S360 are optional and denoted by a dotted block in FIGS. 3A and 3B, and the steps S330˜S350 are similar to steps S230˜S250 in FIGS. 2A and 2B except with different establishment cause. After that, the UE NAS layer transmits the EXTENDED SERVICE REQUEST message to the core network 122, wherein the EXTENDED SERVICE REQUEST message comprises a service type IE which is set to “packet service via S1 for emergency bearer services” (step S370).

For the case of the UE NAS layer being in the EMM CONNECTED mode, the RRC connection has already been established between the UE AS layer and the access network 121 and the UE NAS layer has already been attached to the core network 122, so the steps S320˜360 may be skipped to proceed to the step S370 directly. Thus, with the setting of the service type to “packet service via S1 for emergency bearer services”, both of the UE NAS layer and the core network 122 (i.e., the NAS layer of the communication protocol at the network side) will prioritize the requested emergency bearer services.

Note that, in FIGS. 2A, 2B, 3A, and 3B, detailed descriptions of other related operations for the service request procedure are omitted herein since they are beyond the scope of the invention, and references may be made to the TS 24.301 specification.

FIG. 4 is a flow chart illustrating the method for handling a request for emergency bearer services according to an embodiment of the invention. In this embodiment, the method may be applied to any mobile communication device which is configured for NAS signaling low priority. To begin the method, the mobile communication device originates an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EMM IDLE mode (step S410). Next, the mobile communication device transmits an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to a service network in response to originating the EXTENDED SERVICE REQUEST message (step S420). To further clarify, the origination of the EXTENDED SERVICE REQUEST message may be triggered by the NAS layer of the communication protocol in the mobile communication device, and the transmission of the RRC CONNECTION REQUEST message may be performed by the AS layer of the communication protocol in the mobile communication device in response to receiving a request from the NAS layer for establishing an RRC connection. Particularly, the request may include an RRC establishment cause to indicate the setting of the establishment cause in the RRC CONNECTION REQUEST message to “Emergency call”. Thus, with the establishment cause indicating an emergency case, both of the AS layers at the UE side and the network side will prioritize the RRC connection establishment, so that the requested emergency bearer services may be further prioritized.

FIG. 5 is a flow chart illustrating the method for handling a request for emergency bearer services according to another embodiment of the invention. Similar to FIG. 4, the method may be applied to any mobile communication device which is configured for NAS signaling low priority. To begin the method, the mobile communication device originates an EXTENDED SERVICE REQUEST message for requesting emergency bearer services (step S510). Also, the mobile communication device includes a service type in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services (step S520), and then transmits the EXTENDED SERVICE REQUEST message to a service network (step S530). In another embodiment, if the mobile communication device is in the EMM IDLE mode when originating the EXTENDED SERVICE REQUEST message, it may perform establishment of an RRC connection before the step S530. To further clarify, the origination of the EXTENDED SERVICE REQUEST message may be triggered by the NAS layer of the communication protocol in the mobile communication device, and the service type may be set to “packet service via S1 for emergency bearer services” to indicate the emergency case. Thus, with the setting of the service type, both of the NAS layers at the UE side and the network side will prioritize the requested emergency bearer services.

While the invention has been described by way of example and in terms of preferred embodiment, it is to be understood that the invention is not limited thereto. Those who are skilled in this technology can still make various alterations and modifications without departing from the scope and spirit of this invention. For example, the method for handling a request for emergency bearer services may also be applied to any low priority devices in compliance with any evolutionary technology of the LTE/LTE-Advanced technology. Therefore, the scope of the present invention shall be defined and protected by the following claims and their equivalents.

Claims (20)

What is claimed is:
1. A mobile communication device, configured for Non Access Stratum (NAS) signaling low priority, comprising:
a wireless module performing, configured to perform wireless transmissions and receptions to and from a service network; and
a processor originating, configured to:
originate an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EPS (Evolved Packet System) Mobility Management (EMM) IDLE mode of a NAS layer, and
transmitting transmit an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to the service network via the wireless module in response to originating the EXTENDED SERVICE REQUEST message and the mobile communication device being configured for NAS signaling low priority,
receive an RRC CONNECTION SETUP message corresponding to the RRC CONNECTION REQUEST message from the service network via the wireless module,
transmit an RRC CONNECTION SETUP COMPLETE message to the service network via the wireless module in response to receiving the RRC CONNECTION SETUP message,
include a service type indicating that the request is for the emergency bearer services in the EXTENDED SERVICE REQUEST message in response to the mobile communication device being configured for NAS signaling low priority, and
transmit the EXTENDED SERVICE REQUEST message to the service network via the wireless module in response to the transmission of the RRC CONNECTION SETUP COMPLETE message.
2. The mobile communication device of claim 1, wherein the establishment cause in the RRC CONNECTION REQUEST message is set to “Emergency call” to indicate the emergency case, according to an RRC establishment cause of a NAS layer.
3. The mobile communication device of claim 1, wherein the emergency bearer services are prioritized in an Access Stratum (AS) layer in response to the establishment cause indicating the emergency case.
4. The mobile communication device of claim 1, wherein the processor further receives an RRC CONNECTION SETUP message corresponding to the RRC CONNECTION REQUEST message from the service network via the wireless module, and transmits an RRC CONNECTION SETUP COMPLETE message to the service network via the wireless module in response to receiving the RRC CONNECTION SETUP message.
5. The mobile communication device of claim 4, wherein the processor further includes a service type in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services, and transmits the EXTENDED SERVICE REQUEST message to the service network via the wireless module in response to the transmission of the RRC CONNECTION SETUP COMPLETE message.
6. The mobile communication device of claim 5 1, wherein the emergency bearer services are prioritized in the NAS layer in response to the service type indicating that the request is for the emergency bearer services.
7. A method for handling a request for emergency bearer services by a mobile communication device configured for NAS signaling low priority, comprising:
originating an EXTENDED SERVICE REQUEST message for requesting emergency bearer services in an EPS (Evolved Packet System) Mobility Management (EMM) IDLE mode of a NAS layer; and
transmitting an RRC CONNECTION REQUEST message comprising an establishment cause indicating an emergency case to a service network in response to originating the EXTENDED SERVICE REQUEST message and the mobile communication device being configured for NAS signaling low priority;
receiving an RRC CONNECTION SETUP message corresponding to the RRC CONNECTION REQUEST message from the service network;
transmitting an RRC CONNECTION SETUP COMPLETE message to the service network in response to receiving the RRC CONNECTION SETUP message;
including a service type indicating that the request is for the emergency bearer services in the EXTENDED SERVICE REQUEST message in response to the mobile communication device being configured for NAS signaling low priority; and
transmitting the EXTENDED SERVICE REQUEST message to the service network in response to the transmission of the RRC CONNECTION SETUP COMPLETE message.
8. The method of claim 7, wherein the establishment cause in the RRC CONNECTION REQUEST message is set to “Emergency call” to indicate the emergency case, according to an RRC establishment cause of a NAS layer.
9. The method of claim 7, wherein the emergency bearer services are prioritized in an AS layer in response to the establishment cause indicating the emergency case.
10. The method of claim 7, further comprising receiving an RRC CONNECTION SETUP message corresponding to the RRC CONNECTION REQUEST message from the service network, and transmitting an RRC CONNECTION SETUP COMPLETE message to the service network in response to receiving the RRC CONNECTION SETUP message.
11. The method of claim 10, further comprising including a service type in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services, and transmitting the EXTENDED SERVICE REQUEST message to the service network in response to the transmission of the RRC CONNECTION SETUP COMPLETE message.
12. The method of claim 11 7, wherein the emergency bearer services are prioritized in the NAS layer in response to the service type indicating that the request is for the emergency bearer services.
13. A mobile communication device, configured for NAS signaling low priority, comprising:
a wireless module performing, configured to perform wireless transmissions and receptions to and from a service network; and
a processor originating, configured to originate an EXTENDED SERVICE REQUEST message for requesting emergency bearer services, including include a service type indicating that the request is for the emergency bearer services in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services in response to the mobile communication device being configured for NAS signaling low priority, and transmitting transmit the EXTENDED SERVICE REQUEST message to the service network via the wireless module.
14. The mobile communication device of claim 13, wherein the emergency bearer services are prioritized in a NAS layer in response to the service type indicating that the request is for the emergency bearer services.
15. A method for handling a request for emergency bearer services by a mobile communication device configured for NAS signaling low priority, comprising:
originating an EXTENDED SERVICE REQUEST message for requesting emergency bearer services;
including a service type indicating that the request is for the emergency bearer services in the EXTENDED SERVICE REQUEST message to indicate that the request is for the emergency bearer services in response to the mobile communication device being configured for NAS signaling low priority; and
transmitting the EXTENDED SERVICE REQUEST message to a service network.
16. The method of claim 15, wherein the emergency bearer services are prioritized in a NAS layer in response to the service type indicating that the request is for the emergency bearer services.
17. The mobile communication device of claim 13, wherein the service type in the EXTENDED SERVICE REQUEST message is set to “packet service via S1 for emergency bearer services” to indicate that the request is for the emergency bearer services.
18. The method of claim 15, wherein the service type in the EXTENDED SERVICE REQUEST message is set to “packet service via S1 for emergency bearer services” to indicate that the request is for the emergency bearer services.
19. A service network, comprising:
an access network, configured to perform wireless transmissions and receptions to and from a mobile communication device configured for NAS signaling low priority; and
a core network, configured to receive an EXTENDED SERVICE REQUEST message, which comprises a service type set to “packet service via S1 for emergency bearer services” to indicate a request for emergency bearer services, from the mobile communication device which is configured for NAS signaling low priority via the access network, and prioritize the request for the emergency bearer services in response to the service type indicating the request for the emergency bearer services.
20. A method for a service network to handle a request for emergency bearer services from a mobile communication device configured for NAS signaling low priority, comprising:
receiving an EXTENDED SERVICE REQUEST message, which comprises a service type set to “packet service via S1 for emergency bearer services” to indicate a request for emergency bearer services, from the mobile communication device which is configured for NAS signaling low priority; and
prioritizing the request for the emergency bearer services in response to the service type indicating the request for the emergency bearer services.
US14/984,798 2011-03-21 2015-12-30 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same Active USRE46885E1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US201161454861P true 2011-03-21 2011-03-21
US201161476533P true 2011-04-18 2011-04-18
US13/419,006 US8655305B2 (en) 2011-03-21 2012-03-13 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
US14/984,798 USRE46885E1 (en) 2011-03-21 2015-12-30 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/984,798 USRE46885E1 (en) 2011-03-21 2015-12-30 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/419,006 Reissue US8655305B2 (en) 2011-03-21 2012-03-13 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same

Publications (1)

Publication Number Publication Date
USRE46885E1 true USRE46885E1 (en) 2018-05-29

Family

ID=45977085

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/419,006 Active 2032-04-11 US8655305B2 (en) 2011-03-21 2012-03-13 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
US14/984,798 Active USRE46885E1 (en) 2011-03-21 2015-12-30 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US13/419,006 Active 2032-04-11 US8655305B2 (en) 2011-03-21 2012-03-13 Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same

Country Status (6)

Country Link
US (2) US8655305B2 (en)
EP (1) EP2503838B1 (en)
JP (1) JP5806154B2 (en)
KR (1) KR101376249B1 (en)
CN (1) CN102695152B (en)
TW (1) TWI436666B (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101929307B1 (en) * 2011-04-11 2018-12-17 삼성전자 주식회사 method and apparatus to control UE Cell reselection priority while UE is in CSG cell
US20120289183A1 (en) * 2011-05-13 2012-11-15 Kundan Tiwari Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
KR101565102B1 (en) * 2012-04-04 2015-11-02 주식회사 케이티 Access Control Method and Apparatus for Machine Type Communication Devices with Dual Priority Applications
US10304347B2 (en) 2012-05-09 2019-05-28 Apple Inc. Exercised-based watch face and complications
KR20140055058A (en) * 2012-10-30 2014-05-09 삼성전자주식회사 Method for deactivating non-emergency bearers and maintaining forbidden ta lists when ue having both emergency and non-emergency bearer moves to a unknown forbidden ta in radio communication system
EP3063981B1 (en) * 2013-10-30 2020-02-19 Interdigital Patent Holdings, Inc. Method and wtru for handling priority services congestion
US9775011B2 (en) 2014-01-31 2017-09-26 Intel Corporation Implementations of application specific access class barring skip functionality in a wireless network
US10313506B2 (en) 2014-05-30 2019-06-04 Apple Inc. Wellness aggregator
WO2016021922A1 (en) * 2014-08-04 2016-02-11 엘지전자 주식회사 Operation method of terminal in wireless communication system and terminal using method
CN106537397B (en) 2014-09-02 2019-12-13 苹果公司 body activity and fitness monitor
US10776739B2 (en) 2014-09-30 2020-09-15 Apple Inc. Fitness challenge E-awards
WO2016099361A1 (en) * 2014-12-19 2016-06-23 Telefonaktiebolaget Lm Ericsson (Publ) Method for assisting a radio network node in setting up a radio resource connection
WO2016144385A1 (en) 2015-03-08 2016-09-15 Apple Inc. Sharing user-configurable graphical constructs
US10368263B2 (en) 2015-04-30 2019-07-30 Samsung Electronics Co., Ltd. Method for forming bearer for public safety in wireless communication system and device therefor
EP3226473B1 (en) * 2016-04-01 2018-12-12 HTC Corporation Device and method of handling user plane evolved packet system optimization procedure
US20170290083A1 (en) * 2016-04-01 2017-10-05 Htc Corporation Device and Method of Handling Radio Resource Control Connection Resume Procedure
DK201770423A1 (en) 2016-06-11 2018-01-15 Apple Inc Activity and workout updates

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100297979A1 (en) 2009-04-14 2010-11-25 Interdigital Patent Holdings, Inc. Method and apparatus for processing emergency calls
US20100317315A1 (en) * 2009-06-16 2010-12-16 Richard Charles Burbidge Method for accessing a service unavailable through a network cell
US20110028120A1 (en) * 2009-07-30 2011-02-03 Chih-Hsiang Wu Method of handling call origination and related communication device
US20110110302A1 (en) * 2009-11-09 2011-05-12 Rene Faurie Determination of Appropriate Radio Resource to be Requested in Case of a Circuit-Switched (CS) Fallback Procedure
US20110117876A1 (en) * 2008-07-04 2011-05-19 Samsung Electronics Co., Ltd. Method for supporting an emergency call in a mobile communication system
US20120113895A1 (en) * 2010-11-10 2012-05-10 John Diachina System and method for providing information indicating the priority level of a non access stratum signaling message and for using the priority level information to select a response
US20120218889A1 (en) * 2011-02-24 2012-08-30 Interdigital Patent Holdings, Inc. Handling of low priority devices
US20120281566A1 (en) * 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
US20120289183A1 (en) * 2011-05-13 2012-11-15 Kundan Tiwari Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
US20120302196A1 (en) * 2010-01-08 2012-11-29 Research In Motion Limited Routing of Messages for Mobile Communication Devices During Emergency Calls
US8351935B2 (en) * 2009-05-04 2013-01-08 Qualcomm Incorporated Apparatus and method for using motion sensor data to select full band scans
US20130016608A1 (en) * 2011-07-12 2013-01-17 Kundan Tiwari Method of Reducing Signaling in Congested Network and Related Communication Device
US20130016607A1 (en) * 2011-01-19 2013-01-17 Kundan Tiwari Method of Handling Emergency Bearer Service in Wireless Communication System
US20130040605A1 (en) * 2011-08-10 2013-02-14 Nokia Siemens Networks Oy Methods and apparatus for radio resource control
US20130237267A1 (en) * 2010-11-08 2013-09-12 Lg Electronics Inc. Rrc connection method and device therefor in wireless communication system
US20160183156A1 (en) * 2010-09-28 2016-06-23 Blackberry Limited Method and apparatus for releasing connection with local gw when ue moves out of the residential/enterprise network coverage

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2854756B1 (en) * 2003-05-07 2005-08-12 Evolium Sas Method for establishing connection in a mobile radiocommunication system
US7735085B2 (en) 2004-05-26 2010-06-08 Qualcomm Incorporated System for application priority based on device operating mode
WO2010081233A1 (en) * 2009-01-15 2010-07-22 Research In Motion Limited System and method for determining establishment causes

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110117876A1 (en) * 2008-07-04 2011-05-19 Samsung Electronics Co., Ltd. Method for supporting an emergency call in a mobile communication system
US20100297979A1 (en) 2009-04-14 2010-11-25 Interdigital Patent Holdings, Inc. Method and apparatus for processing emergency calls
US8351935B2 (en) * 2009-05-04 2013-01-08 Qualcomm Incorporated Apparatus and method for using motion sensor data to select full band scans
US20100317315A1 (en) * 2009-06-16 2010-12-16 Richard Charles Burbidge Method for accessing a service unavailable through a network cell
US20110028120A1 (en) * 2009-07-30 2011-02-03 Chih-Hsiang Wu Method of handling call origination and related communication device
US20110110302A1 (en) * 2009-11-09 2011-05-12 Rene Faurie Determination of Appropriate Radio Resource to be Requested in Case of a Circuit-Switched (CS) Fallback Procedure
US20120302196A1 (en) * 2010-01-08 2012-11-29 Research In Motion Limited Routing of Messages for Mobile Communication Devices During Emergency Calls
US20160183156A1 (en) * 2010-09-28 2016-06-23 Blackberry Limited Method and apparatus for releasing connection with local gw when ue moves out of the residential/enterprise network coverage
US20130237267A1 (en) * 2010-11-08 2013-09-12 Lg Electronics Inc. Rrc connection method and device therefor in wireless communication system
US8995467B2 (en) * 2010-11-10 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) System and method for providing information indicating the priority level of a non access stratum signaling message and for using the priority level information to select a response
US20120113895A1 (en) * 2010-11-10 2012-05-10 John Diachina System and method for providing information indicating the priority level of a non access stratum signaling message and for using the priority level information to select a response
US20130016607A1 (en) * 2011-01-19 2013-01-17 Kundan Tiwari Method of Handling Emergency Bearer Service in Wireless Communication System
US20120218889A1 (en) * 2011-02-24 2012-08-30 Interdigital Patent Holdings, Inc. Handling of low priority devices
US20120281566A1 (en) * 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
US20120289183A1 (en) * 2011-05-13 2012-11-15 Kundan Tiwari Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
US20130016608A1 (en) * 2011-07-12 2013-01-17 Kundan Tiwari Method of Reducing Signaling in Congested Network and Related Communication Device
US20130040605A1 (en) * 2011-08-10 2013-02-14 Nokia Siemens Networks Oy Methods and apparatus for radio resource control

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 10)", 3GPP STANDARD; 3GPP TS 24.301, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V10.1.0, 3GPP TS 24.301, 21 December 2010 (2010-12-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 305, XP050462346
3GPP TS 24.301 V10.1.0 (Dec. 2010); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 10); XP050462346; 305 pages.
HCT et al; 3GPP TSG CT WG1 Meeting #73, St Julians (Malta), Aug. 22-26, 2011; C1-113281; Defining new service type to handle PS emergency call; XP050533801; 6 pages.
HTC, INTERDIGITAL: "Defining new service type to handle PS emergency call", 3GPP DRAFT; C1-113281, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Malta; 20110822, C1-113281, 29 August 2011 (2011-08-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050533801
RESEARCH IN MOTION: "Device properties and RRC establishment cause = Delay tolerant – 24.301", 3GPP DRAFT; C1-111165 REV OF C1-110828 REV OF C1-110747 24301 M2M RRC EST CAUSE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Salt Lake City; 20110221, C1-111165 rev of C1-110828 rev of C1-110747 24301 , 28 February 2011 (2011-02-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP050480586
Research in Motion; 3GPP TSG-CT WG1 Meeting #70, Salt Lake City, Utah (USA), Feb. 21-25, 2011; C1-111165; Device prooperties and RRC establishement cause; XP050480586; 3 pages.

Also Published As

Publication number Publication date
EP2503838B1 (en) 2015-06-17
US20120244828A1 (en) 2012-09-27
EP2503838A3 (en) 2012-10-24
JP5806154B2 (en) 2015-11-10
EP2503838A2 (en) 2012-09-26
TW201240499A (en) 2012-10-01
KR101376249B1 (en) 2014-03-24
CN102695152B (en) 2015-07-22
US8655305B2 (en) 2014-02-18
JP2012199924A (en) 2012-10-18
CN102695152A (en) 2012-09-26
TWI436666B (en) 2014-05-01

Similar Documents

Publication Publication Date Title
US20200137127A1 (en) System and method for determining establishment causes for emergency sessions
JP6577019B2 (en) RAN procedure for extended discontinuous reception (DRX)
JP6204554B2 (en) Cellular network assisted access service registration procedure using session initiation protocol and event framework for access request / alarm
JP6479989B2 (en) Network slice selection
JP5864521B2 (en) Congestion control method used for machine type communication (MTC) device or low priority device, and apparatus using the method
US9055548B2 (en) Method of handling location service and related communication device
EP3349508B1 (en) Method and apparatus for setting up a csfb call in a mobile communication system
KR101264499B1 (en) Method and apparatus for performing a handover in an evolved universal terrestrial radio access network
KR101339044B1 (en) Handling reachability of mobile device when serving core network node changes
US20130329567A1 (en) Delaying network reselection following performance of a circuit switched fallback procedure in a call failure scenario
ES2390813T3 (en) Determination of a type of channel to be requested in case of a switched circuit change procedure
US8615230B2 (en) Method of reporting radio access technology capability and related apparatus
TWI520649B (en) Method of improving semi-persistent scheduling resources reconfiguration in a wireless communication system and related communication device
JP2018511961A (en) On-demand system information
EP2490463A1 (en) Service networks and methods for handling machine type communication device triggering
US8938236B2 (en) Mobile device redirecting technology
KR20120081572A (en) Apparatuses and methods for handling mobility management (mm) back-offs
TWI469598B (en) Method of handling attach procedure and related communication device
EP2285158B1 (en) Method of handling system information reception with measurement gap configuration and related communication device
TWI483636B (en) Mobile communication devices, telecommunication networks, and methods for offloading data traffic
EP2385677B1 (en) Method of controlling packet switched data transmission and related communication device
JP2011508996A (en) User equipment function update in wireless communication
US8666415B2 (en) Method for canceling call initiation in radio access technology change
US8768290B2 (en) Apparatuses and methods for handling of an equivalent public land mobile network (PLMN) list
US20110249635A1 (en) Wireless Apparatuses, Wireless Systems, and Methods for Managing Multiple Component Carriers