WO2018060553A1

WO2018060553A1 - Locating user equipment in an emergency via proximity services

Info

Publication number: WO2018060553A1
Application number: PCT/FI2017/050669
Authority: WO
Inventors: Sankaran BALASUBRAMANIAM; Curt Wong
Original assignee: Nokia Technologies Oy
Priority date: 2016-09-30
Filing date: 2017-09-25
Publication date: 2018-04-05

Abstract

Methods and apparatus, including computer program products, are provided for emergency services. In some example embodiments, there may be provided a method that includes receiving, by a user equipment configured with a proximity service, an indication provided by the network to monitor for emergency query codes; receiving, by the user equipment, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and responding to the received emergency query code with an emergency response code to enable locating the user equipment. Related systems, methods, and articles of manufacture are also described.

Description

LOCATING USER EQUIPMENT IN AN EMERGENCY

VIA PROXIMITY SERVICES

Field

The subject matter described herein relates to wireless systems. Background

When there is an emergency such as a disaster, a large quantity of people can be affected. Often, many of these people will carry user equipment, such as cell phone, smart phones, and/or other wireless device configured to access a cellular network. During the emergency, some people may be missing and, as such, their location may not be known. Not having their location may cause numerous issues, the least of which includes difficulties in dispatching services or dispatching services to a user that is no longer at that location. Summary

Methods and apparatus, including computer program products, are provided for emergency services.

In some example embodiments, there may be provided a method that includes receiving, by a user equipment configured with a proximity service, an indication provided by the network to monitor for emergency query codes; receiving, by the user equipment, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and responding to the received emergency query code with an emergency response code to enable locating the user equipment.

In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The user equipment may be provided with the emergency query code and the emergency response code before an event including an emergency. A network node configured with the proximity service may provide to the user equipment the emergency query code and the emergency response code. The indication may be triggered in response to the event including the emergency. The indication may be received via a broadcast directed to a location associated with the event including the emergency. The broadcast may signal a plurality of user equipment to monitor for at least the emergency query code. The emergency query code may be received via a device-to-device link including a PC5 interface. In some example embodiments, there may be provided a method that includes providing, by a network node, an emergency query code and an emergency response code to a user equipment configured with a proximity service, wherein the emergency query code and the emergency response code are provided before an event including an emergency; sending, in response to an event, an indication to the user equipment configured with the proximity service, wherein the indication indicates to the user equipment to monitor for the emergency query code; and receiving a location of the user equipment, when the user equipment responds to the monitored emergency query code by at least sending the emergency response code. In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The emergency query code and the emergency response code may be sent or configured before the event. The network node may be configured with the proximity service. The indication may be provided, such as sent, in response to the event including an emergency. The indication may be provided via a broadcast directed to the location associated with the event including the emergency. The broadcast may signal a plurality of user equipment to monitor for at least the emergency query code.

The above-noted aspects and features may be implemented in systems, apparatus, methods, and/or articles depending on the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

Description of Drawings

In the drawings,

FIG. 1 depicts an example of a signaling diagram 100 for configuring proximity services (ProSe) enabled user equipment to enable emergency related discovery, in accordance with some example embodiments;

FIG. 2 depicts an example of a signaling diagram 200 for discovering a user equipment via proximity services, in accordance with some example embodiments;

FIG. 3A depicts an example of a process 300 for user equipment discovery, in accordance with some example embodiments;

FIG. 3B depicts another example of a process 399 for user equipment discovery, in accordance with some example embodiments; and

FIG. 4 depicts an example of an apparatus, in accordance with some example embodiments. Like labels are used to refer to same or similar items in the drawings. Detailed Description

As noted, during an emergency such as a disaster or the like, locating users is useful. For example, knowing whether a person carrying a user equipment, such as a smartphone, cellphone, and/or the like, is still present at the location of the emergency can be very useful with respect to providing emergency services.

In some example embodiments, the proximity of user equipment to a given location associated with an emergency or disaster may be determined. Moreover, in some example embodiments, 3GPP services such as proximity services (ProSe) may be extended to enable monitoring and discovering user equipment associated with one or more users impacted by a disaster/emergency. See, e.g., 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity-based services (ProSe); Stage 2; Release 13, TS 23.303, herein after TS 23.303.

In some example embodiments, UEs enabled with ProSe may be located in the proximity of an emergency/disaster area, so that an emergency response center can dispatch emergency related services/assistant to the UEs (and thus their users).

FIG. 1 depicts an example of a signaling diagram 100, in accordance with some example embodiments. The signaling diagram depicts one or more user equipment 110A-B, a node 112 including a proximity service function (labeled ProSe function), and a proximity service application server 114 (labeled ProSe AS). The ProSe enabled UEs and the PSAP may be configured in accordance with a standard, such as TS 23.303, although the UEs and PSAP may be configured in accordance with other standards as well.

In some example embodiments, the process 100 may occur before a given emergency, but the process may occur at other times as well.

At 120A-B, service authorization may be performed, in accordance with some example embodiments. For example, the ProSe function 112 may send, at 120 A, a service authorization message indicating to UE 1 10A that it is a disco veree (for example, a device to be discovered via the ProSe), and send, at 120B, a service authorization message indicating to UE HOB that it is a discoverer (for example, a device that is to discover other device(s) via the ProSe). The ProSe function may also configure any relevant policies using other network nodes, such as an Open Mobile Alliance device manager (OMA-DM). At 122, the UE 110A may send a ProSe Discovery User ID (PDUID) to the ProSe AS 114. For example, ProSe enable UE 11 OA may include a ProSe application configured to send the PDUID to the ProSe AS 114, which may then assign and respond, at 124, with a Restricted ProSe Application User ID (RPAUID) to the UE 110A. At 126, UE 110A may send to ProSe function 112 an RPAUID, which may be carried by a discovery request.

The ProSe function 112 may assign a query code, response code, and other parameters to UE 11 OA. In some example embodiments, the ProSe function may also assign a universal Emergency Query Code (EQC) and universal Emergency Response Code (ERC). The EQC and ERC may be mapped to a ProSe function for emergency services including the location of devices as described herein, although the EQC and ERC may be implemented using other indicators and/or may provide other functions as well. In some example embodiments, the EQC and/or ERC may be predefined, so that the UEs know the EQC and ERC and the network does not need to signal the EQC and ERC at the time of the event. The EQC and ERC , may be applicable to a region, country, or worldwide.

At 128, the ProSe function 112 may send to UE 110A the EQC and ERC, as well as other parameters. The ProSe function may provision the EQC and ERC by default to any ProSe enabled UEs. The EQC and ERC enable the UE to monitor for the EQC when specifically triggered by the network (for example, after an emergency event happens).

At 132, the UE HOB may send a PDUID to the ProSe AS 114, which may then assign, at 134, an RPAUID to the UE HOB. At 136, UE HOB may send to ProSe function 112 an RPAUID, which may be carried by a discovery request. At 138, the ProSe function may also assign the EQC and ERC to UE HOB. For example, a group of UE in the vicinity of an emergency may all use the same EQC and ERC during the ProSe process described herein to discover and report UEs. Alternatively or additionally, the EQC and ERC may be specific to a particular country or region. Alternatively or additionally, the EQC and ERC may be common across all regions. Alternatively or additionally, different EQC and ERC may be assigned for different user types or their roles(e.g., a rescuer, police, fire fire fighters, civilians, etc). Alternatively or additionally, different EQC and ERC may be assigned for different emergency situation types (e.g., a UE can detect certain environmental conditions like low temperature, oxygen level, etc). In any case, the UEs may know the values of the EQC and ERC before the emergency event occurs. At 140, UE HOB may send the EQC code to UE 11 OA, in accordance with some example embodiments. The UE HOB may send the EQC code via a cellular link, WiFi, link, a device- to-device link (e.g., Bluetooth, LTE sidelink/PC5, etc.), and/or any other type of link. For example, UE 110A may monitor on an interface (e.g., the PC5 interface) for its assigned EQC. In the case of the PC5 interface, it represents an interface between ProSe enabled UEs, and the PC5 interface can be used for control and user plane traffic associated with ProSe discovery and/or ProSe related communications among UEs and the network, for example. In some example embodiments, ProSe discovery among UE occurs via device-to-device links (e.g., WiFi direct, Bluetooth, Bluetooth Low Energy, and/or a LTE sidelink, such as the PC5 interface and its link to another UE). When UE 110A finds a matching EQC code, UE 110A may then respond at 142 with the assigned ERC, in accordance with some example embodiments. The match procedure may be performed in accordance with TS 23.303 (see, e.g., Model B discovery). For example, if the received EQC as ProSe Query Code matches the Discovery Query Filter, then UE 110A announces the associated ERC as ProSe Response Code on the PC5 interface. UE HOB also monitors on PC5 interface for any ProSe Response Code(s) that might match the Discovery Response Filter(s). When the UE HOB detects a match for ERC as ProSe Response Code, it reports the ERC as ProSe Response Code to the ProSe Function. To illustrate matching further, the UE that are triggered for emergency services start monitoring for the EQC over the proximity interface; the discoverer UE may broadcast the EQC ; and those UEs that receive the broadcast EQC compare the same with the EQC that it is monitoring. If these are the same, then it responds with the EQR on the same interface, which the discoverer UE makes note of. At 144, UE 1 10B may report to the ProSe function 112 the discovery of UE 110A. From the perspective of the discoverer UE HOB, the UE HOB may include a ProSe application configured to send a PDUID to the ProSe AS 114, which may assign an RPAUID to the UE. The UE HOB may then send to ProSe function the RPAUID, which may be carried by a discovery request. The ProSe function may assigns a Query Code, a Response Code, EQC, ERC, and/or the like to UE HOB. This may enable the UE 110B to monitor for the EQC when triggered by the network (after an emergency event happens). UE HOB may announce its EQC to other UEs over the PC5, such as a device-to-device link(s). UE HOB may also monitor the PC5 for the ERC. When UE 110B finds a match and responds with its ERC, UE 110B may respond at 142 and report the match at 144 to the ProSe Function 114. In some example embodiments, process 100 may thus be used to configure the ProSe enabled UEs with an EQC and ERC before an emergency event occurs. FIG. 2 depicts an example of a signaling diagram 200, in accordance with some example embodiments. Like FIG. 1, the signaling diagram depicts one or more user equipment 110A- B, the ProSe function 112, and ProSe AS 114, but FIG. 2 further depicts UE 290, a public safety access point (PSAP) 292, and a cell broadcast (CB) server 294. In some example embodiments, the process 200 may occur when a given emergency event such as a disaster and/or the like occurs, but the process 200 may occur at other times as well.

At 210, an event such as an emergency may occur, in accordance with some example embodiments. Examples of emergency events include an earthquake, fire, hurricane, flood, riot, and/or any other type of emergency related event.

At 212, a UE 290 may make an emergency call that is routed to the PSAP 292, in accordance with some example embodiments. For example, UE 290 may make an emergency call, such as a 911 call (e.g., in the U.S.) or other emergency call. This call may be routed by the network to a certain node, such as the PSAP 292. To illustrate further, when there an earthquake for example, a first responder or other type of caller may make via UE 290 an emergency call at 212, and this call may be automatically routed by the network to the PSAP 292.

In response to receiving the call 212, the PSAP 292 may initiate, at 214, the discovery of one or more UE via the ProSe function, in accordance with some example embodiments. At 216 for example, the PSAP 292 may determine the location of the UE 290 (referred to herein as the event location) and request a cell broadcast (CB) server 294 to trigger a broadcast at the event location associated with the UE 290. To that end, a broadcast by the cellular network may trigger all the UEs in the event location to monitor for the EQC provisioned earlier at process 100. The broadcast may be carried by a cell broadcast service (CBS) provided via CB server 294, although the request to monitor the EQC may be signaled to the UEs in other ways as well (e.g., a specific paging message from base station).

In response to the cell broadcast 218, the UEs 110A-B may start monitoring the EQC, in accordance with some example embodiments. Moreover, the PSAP 292 or other network node may request the ProSe function 112 to configure the UE 290 as a discoverer of ProSe enabled UEs (and the corresponding assignment of the EQC and ERC) in accordance with process 100. At 220 for example, UE 110A may monitor for the EQC, UE HOB may change its role from discoverer to discoveree, while UE 290 may initiate the announcement of the EQC and monitor for responses, such as the ERC. At 222, UE 290 may announce the EQC over the PC5 interface (e.g., a device-to-device link such as an LTE sidelink among user equipment having a ProSe application) and monitors for the ERC, in accordance with some example embodiments. At 224 and 226, UE 110A-B may respond with the ERC once it finds a match of the EQC. When UE 290 finds a matching ERC, UE 290 may report, at 228, to the ProSe function the discovery of UE 110A and/or HOB.

FIG. 3A depicts an example process for UE discovery during an emergency, in accordance with some example embodiments. At 305, a user equipment, such as user equipment 110A may receive an indication provided by the network to monitor for emergency query codes, in accordance with some example embodiments. For example, a network node such as a base station, CB server 294, and/or any other network node may send an indication the UE 110 to monitor for emergency query codes. As noted above, the user equipment 110A (along with other UEs) may receive the indication as a broadcast, such as a cell broadcast.

At 310, a user equipment, such as user equipment 110A, may receive an emergency query code monitored via the proximity service, in accordance with some example embodiments. The emergency query code may be received from another user equipment, such as user equipment 290 for example, configured with a corresponding proximity service.

At 315, a user equipment, such as user equipment 11 OA, may respond to the received emergency query code with an emergency response code, in accordance with some example embodiments. For example, UE 110A may response to UE 290 with the emergency response code (which matches or corresponds to the received emergency query code). The UE 290 may, upon receiving the emergency response code, respond to the network with location information for UE 110A. In this way, the network including for example a PSAP or other network node may be able to provide location information for UE in an emergency via ProSe. FIG. 3B depicts an example process for UE discovery during an emergency from the perspective of the network, in accordance with some example embodiments.

At 392, a network node may provide an emergency query code and an emergency response code to a user equipment configured with a proximity service, in accordance with some example embodiments. For example, a network node including a ProSe function 112 may send to one or more UEs 110A, HOB, and/or 290 the emergency query code and /or the emergency response code. In some example embodiments, the emergency query code and the emergency response code are provided before an event such as an emergency.

At 394, the network may send, in response to an event such as an emergency, an indication to the user equipment configured with the proximity service, in accordance with some example embodiments. For example, the network node may send via a cell broadcast (see, e.g., 218 above) an indication that triggers one or more UEs to begin monitoring via the ProSe function (including for example the PC5 interface) for the emergency query code. At 396, the network may receive a location of the user equipment, such as UE HOB, in accordance with some example embodiments. For example, user equipment 11 OA may respond to UE 190 with an emergency response code. UE 290 may then forward to the network location information for UE 110A. FIG. 4 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments. The apparatus 10 (or portions thereof) may be configured to provide a radio, such as user equipment (for example, user equipment 110A-B, and/or 290). In some example embodiments, the apparatus may include a ProSe application or service. Moreover, the apparatus 10 (or portions thereof) may be configured to provide a network node (e.g., ProSe function, ProSe AS, PSAP, and/or CB server), which may couple to the UEs via a base station. The apparatus may be implemented as any device including a wireless device, a smart phone, a cell phone, a machine type communication device, a wireless sensor, a radio relay, an access point, and/or any other radio including a processor and memory based device. The apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively transmit and receive antennas may be separate. The apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus. Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory. The processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 4 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.

Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 , 802.16, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like.

The apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. For example, the apparatus 10 and/or a cellular modem therein may be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP) and/or the like. For example, the apparatus 10 may be capable of operating in accordance with 2G wireless communication protocols IS- 136, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-95, Code Division Multiple Access, CDMA, and/or the like. In addition, for example, the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division- Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed. It is understood that the processor 20 may include circuitry for implementing audio/video and logic functions of apparatus 10. For example, the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the apparatus 10 may be allocated between these devices according to their respective capabilities. The processor 20 may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the processor 20 may include functionality to operate one or more software programs, which may be stored in memory. In general, processor 20 and stored software instructions may be configured to cause apparatus 10 to perform actions. For example, processor 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the apparatus 10 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, and/or the like. Apparatus 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20. The display 28 may, as noted above, include a touch sensitive display, where a user may touch and/or gesture to make selections, enter values, and/or the like. The processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like. The processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like. The apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices.

As shown in FIG. 4, apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data. For example, the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The apparatus 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and/or any other short-range radio technology. Apparatus 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example. The apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber. In addition to the SIM, the apparatus 10 may include other removable and/or fixed memory. The apparatus 10 may include volatile memory 40 and/or non- volatile memory 42. For example, volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like. Non-volatile memory 42, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may include a cache area for temporary storage of data. At least part of the volatile and/or non-volatile memory may be embedded in processor 20. The memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein with respect to a user equipment and/or a base station. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. In the example embodiment, the processor 20 may be configured using computer code stored at memory 40 and/or 42 to control and/or provide one or more aspects disclosed herein with respect to the user equipment and/or a base station (see, for example, process 100, 200, 300, 399 and/or the like as disclosed herein).

Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware may reside on memory 40, the control apparatus 20, or electronic components, for example. In some example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer- readable media. In the context of this document, a "computer-readable medium" may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 4, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is enhanced location of devices during an emergency.

The subject matter described herein may be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. For example, the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that may include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein. Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations may be provided in addition to those set forth herein. Moreover, the implementations described above may be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. Other embodiments may be within the scope of the following claims.

If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Although various aspects of some of the embodiments are set out in the independent claims, other aspects of some of the embodiments comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes example embodiments, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of some of the embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term "based on" includes "based on at least." The use of the phase "such as" means "such as for example" unless otherwise indicated.

Claims

CLAIMS:

1. An method comprising:

receiving, by a user equipment configured with a proximity service, an 5 indication provided by the network to monitor for emergency query codes;

receiving, by the user equipment, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and

responding to the received emergency query code with an emergency response o code to enable locating the user equipment.

2. The method of claim 1, wherein the user equipment is provided with the emergency query code and the emergency response code before an event including an emergency. 5

3. The method of any of claims 1-2, wherein a network node configured with the proximity service provides to the user equipment the emergency query code and the emergency response code.

4. The method of any of claims 1-3, wherein the indication is triggered in response to the0 event including the emergency, user type, and/or environmental condition.

5. The method of any of claims 1 -4, wherein the indication is received via a broadcast directed to a location associated with the event including the emergency. 5

6. The method of claim 5, wherein the broadcast signals a plurality of user equipment to monitor for at least the emergency query code.

7. The method of any of claims 1-6, wherein the emergency query code is received via a device-to-device link including a PC5 interface.

0

8. An apparatus comprising:

at least one processor; and

at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor,5 cause the apparatus to at least:

receive, by the apparatus configured with a proximity service, an indication provided by the network to monitor for emergency query codes; receive, by the apparatus, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and

respond to the received emergency query code with an emergency response code to enable locating the apparatus.

9. The apparatus of claim 8, wherein the apparatus is provided with the emergency query code and the emergency response code before an event including the emergency, user type, and/or environmental condition.

10. The apparatus of any of claims 8-9, wherein a network node configured with the proximity service provides to the apparatus the emergency query code and the emergency response code.

11. The apparatus of any of claims 8-10, wherein the indication is triggered in response to the event including the emergency.

12. The apparatus of any of claims 8-11, wherein the indication is received via a broadcast directed to a location associated with the event including the emergency.

13. The apparatus of claim 12, wherein the broadcast signals a plurality of user equipment including the apparatus to monitor for at least the emergency query code.

14. The apparatus of any of claims 8-13, wherein the emergency query code is received via a device-to-device link including a PC5 interface.

15. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising:

receiving, by the apparatus configured with a proximity service, an indication provided by the network to monitor for emergency query codes;

receiving, by the apparatus, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and

responding to the received emergency query code with an emergency response code to enable locating the apparatus.

16. An apparatus comprising: means for receiving, by the apparatus configured with a proximity service, an indication provided by the network to monitor for emergency query codes;

means for receiving, by the apparatus, an emergency query code monitored via the proximity service, the emergency query code received from another user equipment configured with a corresponding proximity service; and

means for responding to the received emergency query code with an emergency response code to enable locating the apparatus.

17. The apparatus of claim 16, wherein the apparatus comprises a user equipment.

18. The apparatus of any of claims 16-17 further comprising means for performing any of claims 2-7.

19. A method comprising:

providing, by a network node, an emergency query code and an emergency response code to a user equipment configured with a proximity service, wherein the emergency query code and the emergency response code are provided before an event including an emergency;

sending, in response to an event, an indication to the user equipment configured with the proximity service, wherein the indication indicates to the user equipment to monitor for the emergency query code; and

receiving a location of the user equipment, when the user equipment responds to the monitored emergency query code by at least sending the emergency response code.

20. The method of claim 19, wherein the emergency query code and the emergency response code are provided before the event.

21. The method of any of claims 19-20, wherein the network node is configured with the proximity service.

22. The method of any of claims 19-21, wherein the indication is provided in response to the event including the emergency.

23. The method of any of claims 19-22, wherein the indication is provided via a broadcast directed to the location associated with the event including the emergency.

24. The method of claim 23, wherein the broadcast signals a plurality of user equipment to monitor for at least the emergency query code.

25. An apparatus comprising:

at least one processor; and

at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least:

provide, by the apparatus, an emergency query code and an emergency response code to a user equipment configured with a proximity service, wherein the emergency query code and the emergency response code are provided before an event including an emergency;

send, in response to an event, an indication to the user equipment configured with the proximity service, wherein the indication indicates to the user equipment to monitor for the emergency query code; and

receive a location of the user equipment, when the user equipment responds to the monitored emergency query code by at least sending the emergency response code.

26. The apparatus of claim 25, wherein the emergency query code and the emergency response code are provided before the event.

27. The apparatus of any of claims 25-26, wherein the apparatus comprises a network node is configured with the proximity service.

28. The apparatus of any of claims 25-27, wherein the indication is provided in response to the event including the emergency.

29. The apparatus of any of claims 25-28, wherein the indication is provided via a broadcast directed to the location associated with the event including the emergency.

30. The apparatus of claim 29, wherein the broadcast signals a plurality of user equipment to monitor for at least the emergency query code.

31. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising:

32. An apparatus comprising:

means for providing, by the apparatus, an emergency query code and an emergency response code to a user equipment configured with a proximity service, wherein the emergency query code and the emergency response code are provided before an event including an emergency;

means for sending, in response to an event, an indication to the user equipment configured with the proximity service, wherein the indication indicates to the user equipment to monitor for the emergency query code; and

means for receiving a location of the user equipment, when the user equipment responds to the monitored emergency query code by at least sending the emergency response code.

33. The apparatus of claim 32, wherein the apparatus comprises a network node.

34. The apparatus of any of claims 32-33 further comprising means for performing any of claims 20-24.