+

US9008606B2 - Method for requesting emergency service at mobile station in a wireless communication system - Google Patents

Method for requesting emergency service at mobile station in a wireless communication system Download PDF

Info

Publication number
US9008606B2
US9008606B2 US13/260,242 US201013260242A US9008606B2 US 9008606 B2 US9008606 B2 US 9008606B2 US 201013260242 A US201013260242 A US 201013260242A US 9008606 B2 US9008606 B2 US 9008606B2
Authority
US
United States
Prior art keywords
emergency
request
emergency service
base station
message
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.)
Expired - Fee Related, expires
Application number
US13/260,242
Other languages
English (en)
Other versions
US20120064854A1 (en
Inventor
Ae Ran YOUN
Yong Ho Kim
Ki Seon Ryu
Hee Jeong CHO
Young Soo Yuk
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.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to US13/260,242 priority Critical patent/US9008606B2/en
Assigned to LG ELECTRONICS INC. reassignment LG ELECTRONICS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KIM, YONG HO, RYU, KI SEON, CHO, HEE JEONG, YOUN, AE RAN, YUK, YOUNG SOO
Publication of US20120064854A1 publication Critical patent/US20120064854A1/en
Application granted granted Critical
Publication of US9008606B2 publication Critical patent/US9008606B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H04W4/22—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H04W72/042—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—
    • H04W76/007—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • the present invention relates to wireless communication, and more particularly, to a method for requesting an emergency service in a wireless communication system and a Mobile Station (MS) using the same.
  • MS Mobile Station
  • Emergency services are intended to notify occurrence of emergencies to persons, countries, or communities and deal with the emergencies.
  • an emergency service provides a person in an emergency situation with a rescue operation and issues an emergency warning about a specific disaster area.
  • emergency services wireless emergency rescue service and wireless emergency alert service.
  • the wireless emergency rescue service locates a wireless mobile communication user and provides safe rescue assistance to him, when a fire, a crime or any other emergency has occurred to him.
  • the wireless emergency alert service alerts wireless subscribers within a specific geographical area of an upcoming storm, earthquake, tsunami, or Chemical, Biological and Radiological (CBR) accident by issuing an emergency notification. To issue the alert, a warning message is broadcast to all MSs located in the specific area.
  • the wireless emergency alert service involves simple message broadcasting or detection of the locations of MSs, thus not imposing much load on a network.
  • MAC Medium Access Control
  • the use of resources at or above the MAC layer may be readily controlled according to the access feature of each subscriber.
  • no restriction is imposed on the physical layer in an emergency situation, which leads to overheated competition for radio resources.
  • the resulting resource dissipation causes network inefficiency.
  • MSs with high priority e.g. governmental terminals, public institute terminals, etc.
  • MSs may have difficulty in initial network entry and in inter-Radio Access Technology (RAT) handover.
  • RAT inter-Radio Access Technology
  • BS Base Station
  • An object of the present invention devised to solve the problem lies on a method for requesting an emergency service to a Base Station (BS) during initial network entry at a Mobile Station (MS).
  • BS Base Station
  • MS Mobile Station
  • Another object of the present invention devised to solve the problem lies on a method for requesting an emergency service to a BS in a connected state at an MS.
  • Another object of the present invention devised to solve the problem lies on an MS for requesting an emergency service to a BS during initial network entry.
  • a further object of the present invention devised to solve the problem lies on an MS for requesting an emergency service to a BS in a connected state.
  • the object of the present invention can be achieved by providing a method for requesting an emergency service to a BS during initial network entry at an MS in a mobile communication system, including transmitting an emergency message to the BS using an emergency Flow Identifier (FID), and receiving from the BS information about resources allocated according to a default service flow parameter predefined for the emergency service by the BS.
  • FID emergency Flow Identifier
  • the emergency service requesting method may further include transmitting to the BS a ranging request message including an emergency service indicator indicating an emergency service request, and receiving from the BS a ranging response message including an emergency FID allocated by the BS as a response to the emergency service request.
  • the emergency FID may be the emergency FID received in the ranging response message.
  • the emergency service requesting method may further include establishing an emergency service flow by a Dynamic Service Addition (DSA) transaction with the BS, if the default service flow parameter is not predefined for the emergency service.
  • DSA Dynamic Service Addition
  • a method for requesting an emergency service to a BS in a connected state at an MS in a mobile communication system including transmitting a bandwidth request to the BS using an emergency FID, and receiving an ACKnowledgment (ACK) signal for the bandwidth request from the BS.
  • ACK ACKnowledgment
  • the emergency service requesting method may further include transmitting to the BS a DSA request message including an emergency service indicator indicating an emergency service request, and receiving from the BS a DSA response message including an emergency FID allocated by the BS as a response to the emergency service request.
  • the emergency FID may be the emergency FID received in the DSA response message.
  • the emergency service requesting method may further include establishing an emergency service flow by a DSA transaction with the BS, if the default service flow parameter is not predefined for the emergency service.
  • an MS for requesting an emergency service to a BS during initial network entry in a mobile communication system including a transmission module for transmitting an emergency message to the BS using an emergency FID, and a reception module for receiving from the BS information about resources allocated according to a default service flow parameter predefined for the emergency service by the BS.
  • the MS may further include a transmission module for transmitting to the BS a ranging request message including an emergency service indicator indicating an emergency service request, and a reception module for receiving from the BS a ranging response message including an emergency FID allocated by the BS as a response to the emergency service request.
  • the emergency FID may be the emergency FID received in the ranging response message.
  • the MS may further include an emergency service flow setup module for establishing an emergency service flow by a DSA transaction with the BS, if the default service flow parameter is not predefined for the emergency service.
  • an MS for requesting an emergency service to a BS in a connected state in a mobile communication system including a transmission module for transmitting a bandwidth request to the BS using an emergency FID, and a reception module for receiving an ACK signal for the bandwidth request from the BS.
  • the MS may further include a transmission module for transmitting to the BS a DSA request message including an emergency service indicator indicating an emergency service request, and a reception module for receiving from the BS a DSA response message including an emergency FID allocated by the BS as a response to the emergency service request.
  • the emergency FID may be the emergency FID received in the DSA response message.
  • the MS may further include an emergency service flow setup module for establishing an emergency service flow by a DSA transaction with the BS, if the default service flow parameter is not predefined for the emergency service.
  • an emergency communication can be efficiently supported between an MS and a BS during initial network entry or in a connected state.
  • FIG. 1 is a diagram illustrating a signal flow for an operation for requesting an emergency service during network entry at a Mobile Station (MS), in the case where an emergency Flow Identification (FID) has been defined for the emergency service in a Base Station (BS) according to an exemplary embodiment of the present invention.
  • MS Mobile Station
  • FID emergency Flow Identification
  • FIG. 2 is a diagram illustrating a signal flow for an operation for requesting an emergency service during network entry at an MS, in the case where an emergency FID has not been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • FIG. 3 is a diagram illustrating a signal flow for an operation for requesting an emergency service in a connected state at an MS, in the case where an emergency FID has been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • FIG. 4 is a diagram illustrating a signal flow for an operation for requesting an emergency service in a connected state at an MS, in the case where an emergency FID has not been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a signal flow for an operation for piggybacking an extended header with emergency service notification information and transmitting the extended header to a BS at an MS according to an exemplary embodiment of the present invention.
  • FIG. 6 is a block diagram of an MS for requesting an emergency service according to an exemplary embodiment of the present invention.
  • MS Mobile Station
  • UE User Equipment
  • AMS Advanced Mobile Station
  • BS Base Station
  • UE User Equipment
  • eNB enhanced Node B
  • AP Access Point
  • an MS may receive information from a BS on a DownLink (DL) and transmit information to the BS on an UpLink (UL).
  • the information transmitted from or received at the MS includes data and various control information and a variety of physical channels are defined according to the types and usages of the information.
  • Service flow parameters for an emergency service may be predefined in a system. If a default service flow has been predefined for an emergency service flow, an emergency Flow Identifier (FID) for the default service flow may be either predefined or allocated by a BS.
  • FID emergency Flow Identifier
  • the MS may request an emergency service to the BS during initial ranging.
  • An emergency FID may be predefined or not for the emergency service.
  • FIG. 1 is a diagram illustrating a signal flow for an operation for requesting an emergency service during network entry at an MS, in the case where an emergency FID has been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • the MS and the BS may establish an emergency service flow via a Dynamic Service Addition (DSA) transaction in step S 110 .
  • DSA Dynamic Service Addition
  • the MS may communicate with the BS using the predefined FID without going through the complete service flow setup through DSA transaction step S 110 . That is, when the emergency service flow parameters are predefined, the MS may transmit a Medium Access Control (MAC) message such as an Advanced Air Interface Ranging Request (AAI_RNG-REQ) message using the predefined FID to the BS in step S 120 . Then the BS may allocate resources to the MS according to the default service flow parameters defined for the emergency service and notify the MS of the allocated resources in step S 130 .
  • MAC Medium Access Control
  • AI_RNG-REQ Advanced Air Interface Ranging Request
  • FIG. 2 is a diagram illustrating a signal flow for an operation for requesting an emergency service during network entry at an MS, in the case where an emergency FID has not been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • An emergency FID for the emergency service may not be predefined in the BS. Then the MS may request the emergency service to the BS using a dedicated ranging code (a dedicated preamble) defined for supporting the emergency service.
  • a dedicated ranging code a dedicated preamble
  • the MS may transmit a ranging request message (e.g. AAI_RNG-REQ) including an emergency service indicator indicating an emergency service request to the BS in step S 210 .
  • the BS may allocate an emergency FID and transmit a ranging response message (e.g. Advanced Air Interface Ranging Response (AAI_RNG-RSP)) including the allocated emergency FID to the MS in step S 220 .
  • AAI_RNG-RSP Advanced Air Interface Ranging Response
  • the MS and the BS may need to perform a DSA transaction to establish an emergency service flow in step S 230 . However, if the default service flow parameters have been defined, the MS and the BS do not need to perform the DSA transaction.
  • step S 240 the MS may transmit an emergency message indicating an emergency service request using the emergency FID included the received ranging response message, to the BS. Then the BS may allocate (grant) resources to the MS according to the default service flow parameters and notify the MS of the allocated resources in step S 250 .
  • An emergency FID value may be reserved. Table 1 below lists exemplary FIDs including the reserved emergency FID.
  • Control FID unicast control FID when PDU is allocated by unicast assignment A-MAP IE; broadcast control FID when PDU is allocated by broadcast assignment A-MAP-IE
  • the reserved emergency FID value may be ‘1111’.
  • the reserved FID for supporting the emergency service that is, the emergency FID illustrated in Table 1 may be transmitted to MSs on a broadcast channel by the BS.
  • the emergency FID may be cell-specific and changed by the BS. If the MS and the BS agreed on an emergency FID, the BS needs to indicate the emergency FID to the MS on a particular channel. Also, neighbor BSs may use the same emergency FID.
  • a network-connected MS requests an emergency service to a BS
  • the MS may transmit Bandwidth Request (BR) to the BS using a predefined emergency FID in order to notify an emergency service request.
  • BR Bandwidth Request
  • the predefined emergency FID may be included in a signaling header and/or an extended header.
  • the MS may use an emergency service indicator or a predetermined value for a specific parameter (e.g. request size, Quality of Service (QoS), priority, scheduling type, etc.).
  • Table 2 illustrates an exemplary BR header including the reserved emergency FID.
  • an FID field for signaling header includes the reserved emergency FID which may be a predetermined value (e.g. ‘1111’).
  • the MS may perform a BR procedure using the predefined emergency FID in the connected state to notify the BS of the emergency service request.
  • BR procedures There are two types of BR procedures, 5-step BR and 3-step BR.
  • An emergency service request method will be described according to the 5-step or 3-step BR procedure.
  • FIG. 3 is a diagram illustrating a signal flow for an operation for requesting an emergency service in a connected state at an MS, in the case where an emergency
  • FID has been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • the MS and the BS may establish an emergency service flow through a DSA transaction in step S 310 .
  • the MS may communicate with the BS using the predefined emergency FID without going through the complete service flow setup through the DSA transaction in step S 310 . That is, if the emergency FID has been defined for the emergency service, the MS may transmit a BR indicator to the BS in step S 320 .
  • the MS may receive a UL grant for a BandWidth Request (BW-REQ) message from the BS in step S 330 .
  • BW-REQ BandWidth Request
  • the MS may transmit a BW-REQ message including emergency service notification information to the BS in step S 340 .
  • the BS may transmit an ACKnowledgment (ACK) signal for the BW-REQ message to the MS in step S 350 .
  • the MS may perform UL scheduled transmission to the BS in step S 360 .
  • BW-REQ BandWidth Request
  • FIG. 4 is a diagram illustrating a signal flow for an operation for requesting an emergency service in a connected state at an MS, in the case where an emergency FID has not been defined for the emergency service in a BS according to an exemplary embodiment of the present invention.
  • the MS may transmit an Advanced Air Interface Dynamic Service Addition Request (AAI_DSA-REQ) message including an emergency service indicator to the BS in step S 410 .
  • the BS may transmit an Advanced Air Interface Dynamic Service Addition Response (AAI_DSA-RSP) message including an emergency FID to the MS in step S 420 .
  • AAA_DSA-RSP Advanced Air Interface Dynamic Service Addition Response
  • the MS and the BS may establish an emergency service flow through a DSA transaction in step S 430 .
  • the MS may communicate with the BS without going through the complete service flow setup through the DSA transaction step S 430 .
  • the MS may transmit a BR indicator to the BS in step S 440 and receive a UL grant for a BW-REQ message from the BS in step S 450 .
  • the MS may transmit a BW-REQ message indicating an emergency service request by the emergency FID to the BS in step S 460 .
  • the BS may transmit an ACK signal for the received BW-REQ message to the MS in step S 470 .
  • the MS may perform UL scheduled transmission to the BS in step S 480 .
  • the BW-REQ message that the MS transmits in step S 340 of FIG. 3 or in step S 460 of FIG. 4 may take the form of a MAC signaling header. Details of the MAC signaling header are illustrated in Table 3. Table 3 illustrates an exemplary MAC signaling header.
  • Type field identifies a MAC signaling header type.
  • the Type field may be represented in 4 bits.
  • a signaling header format may be identified by the Type field of the MAC signaling header.
  • Table 4 lists exemplary type values that indicate MAC signaling header types.
  • Table 4 there are exemplary type field values for respective MAC signaling header types.
  • Table 5 illustrates another example of type field values for MAC signaling header types in the MAC signaling header of Table 3.
  • a Type field value that identifies a MAC signaling header type indicating an emergency service request may be predetermined, for example, ‘1111’.
  • a BR header may be configured in an emergency service header format as illustrated in Table 6.
  • the MS may request the emergency service to the BS by transmitting a signaling header including an emergency service indicator.
  • Table 7 illustrates an example of a signaling header including an emergency service indicator.
  • Table 8 illustrates a BR header configured in an STID header format, unlike Table 6.
  • the BR header illustrated in Table 8 may include an emergency service indicator indicating an emergency service request.
  • the MS may transmit a BR header including the emergency service indicator to the BS in order to indicate an emergency service request.
  • the emergency service indicator may occupy one bit.
  • Table 9 illustrates a BR header without the STID header format.
  • the BR header illustrated in Table 9 may include an emergency service indicator indicating an emergency service request.
  • the BR header illustrated in Table 9 may include an emergency service indicator indicating an emergency service request.
  • the emergency service indicator may be one bit.
  • the MS transmits a service-specific BR header without the STID header format to the BS in order to indicate an emergency service request.
  • Table 10 illustrates an example of the service-specific BR header without the STID header format.
  • Table 11 illustrates an exemplary sleep control header format including an emergency service indicator.
  • the MS may request an emergency service to the BS by transmitting a sleep control header including an emergency service indicator.
  • Table 12 illustrates an exemplary AMS battery level report header that the MS transmits to the BS in order to request an emergency service.
  • the MS may notify the BS of an emergency service request by transmitting an AMS battery level report header including an emergency service indicator.
  • the MS may transmit an extended header including an emergency service indicator to the BS in order to request an emergency service.
  • Table 13 illustrates an example of a piggybacked BR extended header.
  • the MS may request an emergency service to the BS by transmitting a BR extended header including an emergency service indicator (for example, of one bit) to the BS.
  • an emergency service indicator for example, of one bit
  • the MS may request an emergency service using a predetermined value for a specific parameter such as BR request size/length, QoS, priority, scheduling type, etc.
  • Table 14 Table 15 and Table 16 illustrate examples of distinguishing emergency service by scheduling (service) types, priority levels (or QoS IDs).
  • the MS may set a request size or length parameter to a predefined value for the usage of an emergency service request, or transmit a request size or length parameter using full bits (all is (e.g. 0x7FF) or all 0s) in such a manner that indicates an emergency service request.
  • Information specifying the request size/length is not signaled and thus the request size/length needs to be preset. For instance, if the request size parameter is set to 0x7FF and 100 bytes is a preset request size, the BS may allocate resources in which to transmit 100 bytes of data to the MS.
  • partial bits of the request size/length parameter may be used. Specifically, 4 bits are predefined (e.g. value 0xF) for the usage of the emergency service, with respect to a 7-bit request size/length parameter.
  • the MS may transmit a quick access message including information indicating an emergency service request to the BS.
  • the quick access message may include a 12-bit STID, and a reserved emergency FID (e.g. ‘1111’) or a signaling FID (e.g. ‘1011’).
  • a request size set to ‘0000’ or a request size and service type set to ‘0000’ may further be included in the quick access message.
  • the MS may request an emergency service to the BS using the reserved emergency FID (e.g. ‘1111’).
  • the preamble when the MS transmits a preamble and data to request a bandwidth, the preamble may include a scheduling type/priority (e.g. 3 or 4 bits) indicating an emergency service request.
  • the data may include a Cyclic Redundancy Check (CRC) (7 to 10 bits).
  • CRC Cyclic Redundancy Check
  • a power report (2 bits) and scheduling type 2 (1 bit) may be further included in the data.
  • the MS may transmit to the BS a partial STID (3 or 4 bits) in the preamble, and a scheduling type/priority (e.g. 2 or 3 bits) indicating an emergency service request and a request size (7 bits) in the BR data.
  • the data may further include scheduling type 2 (1 bit) selectively.
  • the MS may transmit to the BS a partial STID (3 or 4 bits) in the preamble, and scheduling type 1 (2 bits), an emergency service indicator (1 bit), and a request size (7 bits) in the data.
  • the data may further include scheduling type 2 (1 bit) selectively.
  • the MS may transmit to the BS a reserved emergency FID (4 bits) in the preamble, and scheduling type 1 (2 bits) in the data.
  • the data may further include a request size (6 or 7 bits) and scheduling type 2 (1 bit) selectively.
  • the MS may transmit a preamble for an emergency service in a SuperFrame Header (SFH) to the BS, or the preamble for an emergency service may be predefined Scheduling type 1 (2 bits) may be included in the data.
  • the data may further include a request size (6 or 7 bits) and scheduling type 2 (1 bit) selectively.
  • the MS may transmit an STID and a predetermined BR index (e.g. 0000) in a quick access message to the BS in order to request a bandwidth.
  • the MS may indicate an emergency service request to the BS using the predetermined BR index.
  • the MS may transmit an emergency service request to the BS by an extended header. That is, the MS may transmit an extended header piggybacked with emergency service notification information.
  • the MS may transmit emergency service notification information to the BS by the extended header.
  • the extended header may include a request type, a whole or partial STID, an FID/QoS ID, a request size, and a grant interval.
  • the request type may indicate a one-time additional request. If the request type is set to ‘01’, this may indicate a periodic allocation request. If the request type is set to ‘10’, this may indicate release of periodic allocation (that is, when a service is terminated or in the absence of transmission data).
  • the request size may be used along with the grant interval. If the request type is ‘00’, it may be used for the usage of the corresponding field.
  • the grant interval may be used along with the request size. If the request type is ‘01’, the grant interval may be used for the usage of the corresponding field. As much resources as an initial allocation size for the emergency service may be allocated.
  • FIG. 5 is a diagram illustrating a signal flow for an operation for piggybacking an extended header with emergency service notification information and transmitting the extended header to a BS at an MS according to an exemplary embodiment of the present invention.
  • the MS may transmit an emergency service request to the BS in the 3-step BR procedure.
  • the MS may transmit a BR indicator piggybacked with emergency service notification information to the BS in step S 510 .
  • the BS may transmit an ACK signal to the MS in step S 520 .
  • the MS may perform UL scheduled transmission to the BS in step S 530 .
  • the MS may piggyback an extended header with a request type set to a predetermined value (e.g. ‘01’) and a grant interval set to 20 ms in step S 530 .
  • the BS may transmit a UL grant to the MS in step S 540 .
  • step S 550 the MS may perform UL scheduled transmission 20 ms after step S 530 .
  • the MS may transmit an extended header with a request type set to a predetermined value (e.g. ‘10’) to the BS.
  • a predetermined value e.g. ‘10’
  • FIG. 6 is a block diagram of an MS for requesting an emergency service according to an exemplary embodiment of the present invention.
  • an MS 50 includes a processor 51 , a memory 52 , a Radio Frequency (RF) unit 53 , a display unit 54 , and a user interface unit 55 .
  • the functionality of each layer may be implemented in the processor 51 .
  • the memory is connected to the processor 51 , for storing an operating system, applications, and general files.
  • the display unit 54 displays various pieces of information.
  • the display unit 54 may be configured with a known element such as Liquid Crystal Display (LCD), Organic Light Emitting Diode (OLED), etc.
  • LCD Liquid Crystal Display
  • OLED Organic Light Emitting Diode
  • the user interface unit 55 may be configured with a combination of known user interfaces such as a keypad, a touch screen, etc.
  • the RF unit 53 is connected to the processor 51 , for transmitting and receiving RF signals.
  • the RF unit 53 may be separated into a transmission module (not shown) and a reception module (not shown).
  • a method for requesting an emergency service in a wireless communication system using FFR and an MS using the same according to the present invention are applicable to an IEEE 802.16m system, and other systems.
  • Exemplary embodiments described above are combinations of elements and features of the present invention.
  • the elements or features may be considered selective unless otherwise mentioned.
  • Each element or feature may be practiced without being combined with other elements or features.
  • an embodiment of the present invention may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present invention may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions of another embodiment. It is obvious to those skilled in the art that claims that are not explicitly cited in each other in the appended claims may be presented in combination as an exemplary embodiment of the present invention or included as a new claim by a subsequent amendment after the application is filed.
  • the exemplary embodiments of the present invention may be achieved by various means, for example, hardware, firmware, software, or a combination thereof.
  • the methods according to the exemplary embodiments of the present invention may be achieved by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • processors controllers, microcontrollers, microprocessors, etc.
  • the methods according to the exemplary embodiments of the present invention may be implemented in the form of a module, a procedure, a function, etc.
  • software code may be stored in a memory unit and executed by a processor.
  • the memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)
US13/260,242 2009-04-02 2010-04-02 Method for requesting emergency service at mobile station in a wireless communication system Expired - Fee Related US9008606B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/260,242 US9008606B2 (en) 2009-04-02 2010-04-02 Method for requesting emergency service at mobile station in a wireless communication system

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US16623109P 2009-04-02 2009-04-02
KR1020100026220A KR101691827B1 (ko) 2009-04-02 2010-03-24 무선 통신 시스템에서의 단말의 긴급 서비스 요청 방법
KR10-2010-0026220 2010-03-24
PCT/KR2010/002042 WO2010114333A2 (fr) 2009-04-02 2010-04-02 Procédé de demande de service d'urgence au niveau d'une station mobile dans un système de communication sans fil
US13/260,242 US9008606B2 (en) 2009-04-02 2010-04-02 Method for requesting emergency service at mobile station in a wireless communication system

Publications (2)

Publication Number Publication Date
US20120064854A1 US20120064854A1 (en) 2012-03-15
US9008606B2 true US9008606B2 (en) 2015-04-14

Family

ID=42828878

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/260,242 Expired - Fee Related US9008606B2 (en) 2009-04-02 2010-04-02 Method for requesting emergency service at mobile station in a wireless communication system

Country Status (3)

Country Link
US (1) US9008606B2 (fr)
KR (1) KR101691827B1 (fr)
WO (1) WO2010114333A2 (fr)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2437566A4 (fr) * 2009-05-25 2016-06-01 Lg Electronics Inc Procédé et appareil de transmission/réception d'informations d'attribution de ressource dans un système de communications sans fil
KR20110025015A (ko) * 2009-09-01 2011-03-09 엘지전자 주식회사 멀티 캐리어 시스템의 슬립모드 동작 방법 및 장치
KR101673187B1 (ko) * 2009-10-30 2016-11-08 삼성전자주식회사 통신 시스템에서 레인징 요청 메시지 전송을 위한 상향링크 자원 요구 방법 및 장치
KR101592039B1 (ko) * 2010-03-02 2016-02-05 삼성전자주식회사 통신 시스템에서 플로우 정보 관리 방법 및 장치
KR101724700B1 (ko) * 2010-06-24 2017-04-07 삼성전자주식회사 무선 통신 시스템에서 자원 할당 방식 정보 송수신 방법 및 그 장치
KR20120093491A (ko) * 2011-02-15 2012-08-23 삼성전자주식회사 무선 통신 시스템에서 긴급 통신 서비스 제공 방법 및 장치
KR101860564B1 (ko) 2011-05-03 2018-05-23 한국전자통신연구원 기지국의 통신 방법, 단말의 통신 방법 및 중계국의 통신 방법
US8976693B2 (en) * 2011-07-15 2015-03-10 Electronics And Telecommunications Research Institute Method for reporting emergency and terminal in mobile communication system
US9277408B2 (en) * 2011-10-10 2016-03-01 Lg Electronics Inc. Method and device for authorizing user equipment in a wireless communication system
US10805938B2 (en) 2015-03-17 2020-10-13 Lg Electronics Inc. Data transmission/reception method and apparatus for terminal in wireless communication system
WO2016208829A1 (fr) * 2015-06-26 2016-12-29 엘지전자(주) Procédé permettant la transmission et la réception de données de liaison montante dans un système de communication sans fil, et dispositif associé
CN109547993A (zh) * 2017-07-25 2019-03-29 西安中兴新软件有限责任公司 一种无线终端初始接入的方法和装置
CN113541978B (zh) * 2020-04-13 2025-03-28 中兴通讯股份有限公司 一种云持续集成告警处理方法、服务器及存储介质
TWI783292B (zh) * 2020-11-09 2022-11-11 緯創資通股份有限公司 行動通訊裝置與基於多媒體廣播群播服務之緊急廣播方法

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040203573A1 (en) 2003-01-13 2004-10-14 Chin Mary W. Emergency intersystem paging for emergency call back
EP1575327A1 (fr) 2004-03-11 2005-09-14 Lucent Technologies Inc. Procédé d'association des données de rappel avec un appel d'urgence vers un centre d'appels
WO2006114043A1 (fr) 2005-04-25 2006-11-02 Huawei Technologies Co., Ltd. Procede de gestion d’un service d’urgence dans un reseau de communication
US20070053306A1 (en) 2005-09-02 2007-03-08 Qwest Communications International Inc Location based rules architecture systems and methods
US20080009262A1 (en) * 2006-05-12 2008-01-10 Interdigital Technology Corporation Method and apparatus for supporting an emergency call in a wireless metropolitan area network
US20090109932A1 (en) * 2007-10-25 2009-04-30 Nokia Siemens Networks Oy Fast urgent services support over 802.16 air interface
US20090186594A1 (en) * 2008-01-18 2009-07-23 Samsung Electronics Co. Ltd. System and method for providing an emergency service in a communication system
US20100124901A1 (en) * 2008-11-14 2010-05-20 Qualcomm Incorporated Methods and systems for emergency call handling with position location over communication networks
US20100135205A1 (en) * 2007-01-31 2010-06-03 Nokia Corporation Emergency and priority calling support in wimax

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040203573A1 (en) 2003-01-13 2004-10-14 Chin Mary W. Emergency intersystem paging for emergency call back
EP1575327A1 (fr) 2004-03-11 2005-09-14 Lucent Technologies Inc. Procédé d'association des données de rappel avec un appel d'urgence vers un centre d'appels
WO2006114043A1 (fr) 2005-04-25 2006-11-02 Huawei Technologies Co., Ltd. Procede de gestion d’un service d’urgence dans un reseau de communication
US20070280430A1 (en) * 2005-04-25 2007-12-06 Huawei Technologies Co., Ltd. Method for handling emergency service in network communication
US20070053306A1 (en) 2005-09-02 2007-03-08 Qwest Communications International Inc Location based rules architecture systems and methods
US20080009262A1 (en) * 2006-05-12 2008-01-10 Interdigital Technology Corporation Method and apparatus for supporting an emergency call in a wireless metropolitan area network
US20100135205A1 (en) * 2007-01-31 2010-06-03 Nokia Corporation Emergency and priority calling support in wimax
US20090109932A1 (en) * 2007-10-25 2009-04-30 Nokia Siemens Networks Oy Fast urgent services support over 802.16 air interface
US20090186594A1 (en) * 2008-01-18 2009-07-23 Samsung Electronics Co. Ltd. System and method for providing an emergency service in a communication system
US20100124901A1 (en) * 2008-11-14 2010-05-20 Qualcomm Incorporated Methods and systems for emergency call handling with position location over communication networks

Also Published As

Publication number Publication date
WO2010114333A3 (fr) 2010-12-23
WO2010114333A2 (fr) 2010-10-07
KR101691827B1 (ko) 2017-01-02
US20120064854A1 (en) 2012-03-15
KR20100110265A (ko) 2010-10-12

Similar Documents

Publication Publication Date Title
US9008606B2 (en) Method for requesting emergency service at mobile station in a wireless communication system
US12069550B2 (en) Method for selecting, in selection period, subframe excluding subframe relating to subframe in which transmission has been performed during sensing period in wireless communication system, and terminal using same
US11317382B2 (en) Method for transmitting V2X message by terminal in wireless communication system, and terminal using same method
US10536826B2 (en) Method for selecting resource to be used for performing V2X communication within range satisfying latency requirement in wireless communication system, and terminal using same
US10397855B2 (en) Access attempt method and user equipment, and access control method and base station
US9078257B2 (en) Random backoff for extended access barring
US9380559B2 (en) Method and apparatus for transmitting multicast data to M2M devices in a wireless access system
CA3036351A1 (fr) Procede pour reserver un nombre fini de ressources utilisees pour effectuer une communication v2x dans un systeme de communication sans fil, et terminal d'utilisation associe
CN107027095A (zh) 机器对机器（m2m）终端、基站和方法
KR20160037118A (ko) 무선 통신 시스템에서 방송 자원 혼잡 제어 방법 및 장치
KR20160079043A (ko) 무선 통신 시스템에서 MBMS(multimedia broadcast multicast service) 관심을 결정하는 방법 및 장치
US9084163B2 (en) Apparatus and method for performing carrier switching operation for E-MBS service in multicarrier system
US20240373403A1 (en) Method and apparatus for paging
KR101578007B1 (ko) 긴급 모드에서의 신호 전송 방법
WO2023063262A1 (fr) Dispositif de communication, station de base et procédé de communication

Legal Events

Date Code Title Description
AS Assignment

Owner name: LG ELECTRONICS INC., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YOUN, AE RAN;KIM, YONG HO;RYU, KI SEON;AND OTHERS;SIGNING DATES FROM 20110908 TO 20110920;REEL/FRAME:027192/0314

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20190414

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载