Techniques for delivering emergency payloads for non-voice emergency services

Examples are disclosed for delivering, at user equipment (UE) such as a wireless device, emergency payloads for non-voice emergency services (NOVES). The examples include receiving, at a UE, an emergency payload associated with a NOVES that may include an emergency indicator, a voice message, a video or a text message. An attempt may be made to deliver the emergency payload to a public service answering point (PSAP) and if the attempt is not successful, the emergency payload may be stored at the UE. A number of reattempts may be made to deliver the emergency payload to the PSAP if the attempt is not successful. Based on an acknowledgement of delivery of the emergency payload to the PSAP or aborting reattempts to deliver the emergency payload, the stored emergency payload may be removed from the UE. Other examples are described and claimed.

TECHNICAL FIELD

Examples described herein are generally related to wireless communication devices.

BACKGROUND

Traditionally, emergency situations have been communicated via voice-based calling services such as those associated with a caller dialing 9-1-1 to communicate an emergency. These voice-based calling services were built on the assumption of fixed location phones having landlines and including capabilities that enabled little more than merely placing a voice-based call. Wireless phones have evolved to become a predominate mode of communication and most wireless phones also have non-voice capabilities to include text messaging, capturing video or other means to communicate an emergency situations. Industry organizations and regulatory bodies are currently working together to develop non-voice emergency service (NOVES) guidelines and/or standards to utilize non-voice capabilities of wireless phones to communicate emergency situations and allow local emergency response providers to better respond.

DETAILED DESCRIPTION

Examples are generally directed to improvements for wireless wide area networks (WWANs) using wireless mobile telecommunication cellular or wireless mobile broadband technologies. Wireless mobile broadband technologies may include any wireless technologies suitable for use with wireless devices or user equipment (UE), such as one or more third generation (3G) or fourth generation (4G) wireless standards, revisions, progeny and variants. Examples of wireless mobile broadband technologies may include without limitation any of the Institute of Electrical and Electronics Engineers (IEEE) 802.16m and 802.16p standards, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) and LTE-Advanced (LTE-A) standards, and International Mobile Telecommunications Advanced (IMT-ADV) standards, including their revisions, progeny and variants. Other suitable examples may include, without limitation, Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE) technologies, Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA) technologies, Worldwide Interoperability for Microwave Access (WiMAX) or the WiMAX II technologies, Code Division Multiple Access (CDMA) 2000 system technologies (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, and so forth), High Performance Radio Metropolitan Area Network (HIPERMAN) technologies as defined by the European Telecommunications Standards Institute (ETSI) Broadband Radio Access Networks (BRAN), Wireless Broadband (WiBro) technologies, GSM with General Packet Radio Service (GPRS) system (GSM/GPRS) technologies, High Speed Downlink Packet Access (HSDPA) technologies, High Speed Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA) technologies, High-Speed Uplink Packet Access (HSUPA) system technologies, 3GPP Rel. 8, 9, 10 or 11 of LTE/System Architecture Evolution (SAE), and so forth. The examples are not limited in this context.

By way of example and not limitation, various examples may be described with specific reference to various 3GPP LTE and LTE-A standards, such as the 3GPP LTE Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Universal Terrestrial Radio Access (E-UTRA) and LTE-A Radio Technology 36 Series of Technical Specifications (collectively “3GPP LTE Specifications”), and IEEE 802.16 standards, such as the IEEE 802.16-2009 standard and current third revision to IEEE 802.16 referred to as “802.16Rev3” consolidating standards 802.16-2009, 802.16h-2010 and 802.16m-2011, and the IEEE 802.16p draft standards including IEEE P802.16.1b/D2 Jan. 2012 titled “Draft Amendment to IEEE Standard for WirelessMAN-Advanced Air Interface for Broadband Wireless Access Systems, Enhancements to Support Machine-to-Machine Applications” (collectively “IEEE 802.16 Standards”), and any drafts, revisions or variants of the 3GPP LTE Specifications and the IEEE 802.16 Standards. Although some embodiments may be described as a 3GPP LTE Specifications or IEEE 802.16 Standards system by way of example and not limitation, it may be appreciated that other types of communications system may be implemented as various other types of mobile broadband communications systems and standards. The examples are not limited in this context.

As contemplated in the present disclosure, industry organizations such as 3GPP and regulatory bodies such as the United States Federal Communications Commission (FCC) are currently working together to develop non-voice emergency service (NOVES) guidelines and/or standards to utilize non-voice capabilities of wireless phones to communicate emergency situations. One 3GPP effort is described in technical report (TR) 3GPP TR 22.871, v11.3.0, “3GPP; Technical Specification Group Services and System Aspects; Study on Non-Voice Emergency Services (Release 11)”, published September 2011. Efforts in the United States between 3GPP and the FCC are expected to be in the forefront of the use of NOVES to communicate emergency situations via a wireless device or a UE coupled to a wireless network operated in compliance with one or more 3GPP LTE standards that may include LTE-A.

In some situations, a user of a wireless device or UE may be in an emergency situation and thus may invoke NOVES using the UE. For these situations, a wireless connection to a wireless network may fail and thus an emergency communication does not reach a public service answering point (PSAP) due to the connection failure. Connection failure may be due to a weak or spotty signal quality from base stations or evolved Node Bs (eNBs) for a wireless network connection. Connection failure may also be due to network congestion or even the network being down. Any of these connection failures may be particularly problematic for someone such as a heart attack victim who may not be able to continually try to reattempt to invoke NOVES as that person may quickly become fully incapacitated or unable to make further manual reattempts. It is with respect to these and other challenges that the examples described herein are needed.

In some examples, techniques are implemented for receiving, at a UE capable of operating in compliance with one or more 3GPP LTE standards that may include LTE-A, an emergency payload associated with a NOVES. For these examples, the emergency payload may include an emergency indicator, a voice message, a video or a text message. Attempts may be made to transmit the emergency payload to a PSAP via a wireless communication network. Responsive to an unsuccessful attempt to transmit the emergency payload to the PSAP the emergency payload may be stored at the UE. One or more reattempts may be made to transmit the emergency payload until a successful attempt to transmit the emergency payload has occurred or the NOVES has been aborted. According to some examples, the emergency payload may be purged or removed from the UE responsive to an acknowledgement from the PSAP of receipt of the emergency payload. In some other examples, the emergency payload may be purged or removed from the UE responsive to the NOVES being aborted.

FIG. 1illustrates an example of a first system. As shown inFIG. 1, the first system includes system100. In some examples, as shown inFIG. 1, system100includes user equipment (UE)105coupled to a wireless network110via a wireless communication link (CL)113with base station (BS)112. For these examples, BS112may be an eNB and serve as an access point to wireless network110configured to operate in compliance with one or more 3GPP LTE standards to include LTE-A. BS113may be capable of forwarding communications received from UE105to a mobility management entity (MME)114via communication channel (Comm. Ch.)115. MME114may be configured to manage access to wireless network110and may also be capable of forwarding emergency information routed through wireless network110to a Public Service Answering Point (PSAP)120via Comm. Ch.125.

According to some examples, a user of UE105may invoke a NOVES due to an emergency situation. Logic and/or features of UE105may be capable of generating an emergency payload associated with the NOVES. The emergency payload may include, but is not limited to, an emergency indicator, a voice message, a video or a text message. In some examples, these types of emergency payloads may be pre-configured so that a user of UE105can just press one or more buttons, touch a display icon or make a verbal command to cause UE105to attempt to transmit the emergency payload. For example, a pre-recorded voice message or video message could be sent as part of the emergency payload. Also, a pre-written or pre-typed text message could also be sent with the emergency payload. UE105may also include logic and/or features to include other information with the emergency payload to include location information (e.g., GPS, grid or map coordinates) or a timestamp corresponding to the time the NOVES was invoked.

In some examples, the emergency indicator possibly included in an emergency payload may be situation dependent. For these examples, the emergency indicator may indicate the particular situation. Examples may include, but are not limited to, the user may be located in a residence and an intruder may have broken in to the residence. In other examples, the user may have been in or observed a vehicle accident, may be experiencing a medical emergency (e.g., fall accident, heart attack, stroke or allergic reaction) or may be witnessing a burglary or actually being burglarized. In yet more examples, the user may be physically lost (e.g., in a wilderness area) or may be in the process of being abducted or kidnapped or witness someone else being abducted or kidnapped. Also, workplace violence alert may indicate a situation where a user is threatened by a co-worker to include a co-worker with a knife, gun or other type of deadly weapon.

According to some examples, UE105may attempt to transmit the emergency payload to a PSAP via wireless network110. For these examples, MME114may be capable of identifying that the emergency payload received from UE105is associated with a NOVES and then may determine that PSAP120should receive the emergency payload from UE105. MME114may make the determination based on PSAP120's physical proximity to UE105. For example, UE105may indicate its location is near Portland, Oreg. Therefore, MME114may choose PSAP120due to its physical location near Portland, Oreg. or due to PSAP120providing emergency contact services for the area in or around Portland, Oreg.

As described more below, UE105may include logic and/or features to handle the emergency payload associated with the NOVES. The logic and/or features may be implemented at various layers to include an application layer to execute an emergency call handling application (ECHA) capable of receiving the emergency payload associated with the NOVES and attempting to attach to wireless network110to transmit the emergency payload to PSAP120via wireless network110. In some examples, BS112and/or MME114may serve as or be associated with an emergency access point name (APN) for ECHA to attach to wireless network110. The ECHA may also be capable of storing the emergency payload responsive to an unsuccessful attempt to attach. The ECHA may also be capable of reattempting to transmit the stored emergency payload on at least a periodic basis. The ECHA may also be capable of possibly purging the emergency payload from the UE responsive to receiving an acknowledgement from PSAP120or responsive to the NOVES being aborted.

In some examples, the logic and/or features to handle the emergency payload may be implemented at a non-access stratum (NAS) layer of a 3GPP protocol stack executed by a processor circuit of UE105. For these examples, the NAS layer may be capable of receiving the emergency payload associated with the NOVES and attempt to transmit the emergency payload to PSAP120via wireless network110. The NAS layer may also be capable of storing the emergency payload responsive to an unsuccessful attempt. The NAS layer may also be capable of reattempting to transmit the stored emergency payload on at least a periodic basis. The NAS layer may also be capable of possibly purging the emergency payload from the UE responsive to receiving an acknowledgement from PSAP120or responsive to the NOVES being aborted.

According to some examples, the logic and/or features to handle the emergency payload may be implemented at a radio resource control (RRC) layer of a 3GPP protocol stack executed by a processor circuit of UE105. For these examples, the RRC layer may be capable of receiving the emergency payload associated with the NOVES and attempt to transmit the emergency payload to PSAP120via wireless network110. The RRC layer may also be capable of storing the emergency payload responsive to an unsuccessful attempt. The RRC layer may also be capable of reattempting to transmit the stored emergency payload on at least a periodic basis. The RRC layer may also be capable of possibly purging the emergency payload from the UE responsive to receiving an acknowledgement from PSAP120or responsive to the NOVES being aborted.

In some examples, the logic and/or features to handle the emergency payload may be implemented at an emergency store and forward (ESF) layer of a 3GPP protocol stack executed by a processor circuit of UE105. For these examples, the ESF layer may be a specially designed, task specific layer capable of receiving the emergency payload associated with the NOVES and attempt to transmit the emergency payload to PSAP120via wireless network110. The ESF layer may also be capable of storing the emergency payload responsive to an unsuccessful attempt. The ESF layer may also be capable of reattempting to transmit the stored emergency payload on at least a periodic basis. The ESF layer may also be capable of possibly purging the emergency payload from the UE responsive to receiving an acknowledgement from PSAP120or responsive to the NOVES being aborted.

According to some examples, UE105may be any electronic device having wireless capabilities or equipment. For some examples, UE105may be implemented in a fixed device. A fixed device generally refers to an electronic device designed to be in a fixed, stationary, permanent or otherwise non-moving position or location that does not vary over time. For instance, a fixed device may be installed with fixtures, attachments and housings to prohibit movement, including wired power lines, transmission lines, and so forth. By way of contrast, a mobile device is designed to be portable enough to be frequently moved between various locations over time. It may be appreciated that although a fixed device is generally stationary, some fixed devices may be disconnected from their current equipment in a first fixed location, moved to a second fixed location, and connected to equipment at the second fixed location.

According to some examples, the logic and/or features at BS112may include system equipment, such as network equipment for a communications system or network compliant with one or more 3GPP LTE Specifications (e.g., LTE-A). For example, these base stations may be implemented as evolved Node B (eNB) base stations for a Wireless LTE or LTE-A network. Although some examples are described with reference to a base station or eNB, embodiments may utilize any network equipment for a wireless network. The examples are not limited in this context.

In some examples, Comm. Chs.115or125may be arranged or configured as communication channels separately including one or more communication links via which BS112, MME114or PSAP120may exchange information. These one or more communication links may include various types of wired, wireless or optical communication mediums. For these examples, the communication links may be operated in accordance with one or more applicable communication or networking standards in any version.

FIG. 2illustrates an example process200. In some examples, process200may be for delivering an emergency payload associated with a NOVES invoked by a user of a UE. For these examples, elements of wireless network100as shown inFIG. 1may be used to illustrate example operations related to process200. The described example operations are not limited to implementations on wireless network200.

Beginning at process 2.1 (Receive Emergency Payload), a user may invoke NOVES due to an emergency situation (e.g., a heart attack) and an emergency payload may be received by logic and/or features of UE105. According to some examples, the emergency payload may include an emergency indicator, a voice message, a video or a text message that may have been created by or caused to be created by the user and received by the logic and/or features of UE105.

Proceeding to process 2.2 (Attempt to Tx Emergency Payload), the logic and/or features of UE105may attempt to transmit the emergency payload to PSAP120via wireless network110. In some examples, UE105may attempt to couple to wireless network110through BS112.

Proceeding to process 2.3 (Store Emergency Payload), the logic and/or features of UE105may capable of storing the emergency payload at UE105(e.g., in a store and forward buffer) responsive to an unsuccessful attempt to transmit the emergency payload to PSAP120. In some examples, the unsuccessful attempt may have been caused by such events that include, but are not limited to, an inadequate communication link between UE105and BS112to transmit the emergency payload or even to attach to wireless network110. Other causes may include wireless network110being congested such that even if an adequate communication link was established with BS112, congestion at network elements such as at MME114may cause an unsuccessful attempt to transmit and/or deliver the emergency payload to PSAP120. Also, network112may be temporarily inoperable due to a storm event (e.g., a hurricane), natural disaster (e.g., earthquake) or power outage that may have temporarily disabled network112.

Proceeding to process 2.4 (Reattempt #1), the logic and/or features of UE105may reattempt transmission of the emergency payload. According to some examples, the emergency payload that was previously stored at UE105may be retrieved by the logic and/or features and another attempt made to transmit the emergency payload to PSAP120via wireless network110.

Proceeding to process 2.5 (Reattempt #n), logic and/or features at UE105may reattempt to transmit the emergency payload to PSAP120via wireless network110. In some examples, the logic and/or features may reattempt to transmit the emergency payload for a configurable or set number of n times, where n equates to any positive integer. For these examples, n may be pre-configured by the user of UE105or may be pre-configured based on the type of emergency associated with an invoked NOVES. Also, in addition to a pre-configured value for n, the time interval between each successive attempt may be pre-configured. The pre-configured value for n and the time interval may balance power saving efforts with attempts to send the emergency payload. In some examples, the value for n and/or the time intervals may be adaptively changed based on an algorithm that reduces the value for n and/or shortens/lengthens time intervals based on available battery power for UE105. So in other words, if the battery power is running low, less reattempts and/or less frequent reattempts may be made by the logic and/or features of UE105. Conversely, if the battery power is at a high level or UE105is connected to a power source, more reattempts at a higher frequency may be made.

Proceeding to process 2.6 (Reattempt Successful—Emergency Payload Transmitted), UE105may have successfully transmitted the emergency payload to PSAP120via wireless network120. According to some examples, UE105may have been able to attach to wireless network110either after a first attempt or after n attempts.

Proceeding to process 2.7 (Acknowledgement), UE105may receive an acknowledgement from PSAP120of receipt of the emergency payload. In some examples, as shown inFIG. 2, the acknowledgement may be routed back through wireless network110to UE105.

Proceeding to process 2.8 (Purge Emergency Payload), logic and/or features of UE105may be capable of purging the emergency payload from UE105. According to some examples, the emergency payload may be purged, erased or removed from UE105responsive to receipt of the acknowledgement from PSAP120. Although not shown inFIG. 2, in some other examples, the logic and/or features of UE105may also be capable of purging the emergency payload from UE105based on the number of reattempts exceeding the value for n or based on the user aborting the invoked NOVES.

Proceeding to process 2.9 (Indicate Success/Acknowledgement to User), logic and/or features of UE105may be capable of providing an indication of the successful transmitting or delivery of the emergency payload to PSAP120. In some examples, the indication may be displayed on a display screen for UE105that visually depicts a successful transmission and may also include any instructions received from the PSAP120that may have accompanied the acknowledgement.

FIG. 3illustrates an example second system. As shown inFIG. 3, the example second system includes system300. According to some examples, a process similar to process200described above forFIG. 2may be implemented at a NAS layer of a 3GPP protocol stack executed by a processor circuit for a UE shown inFIG. 3as UE305. For these examples, the NAS layer of UE305may be configured to operate in compliance with one or more 3GPP standards to include LTE-A.

In some examples, the NAS layer may attempt to initiate an emergency session associated with delivering an emergency payload received in association with a NOVES invoked by a user of UE305. For these examples, the emergency payload may be routed through a wireless network that includes eNB312, MME314or emergency interworking function (IWF)316to a destination PSAP such as PSAP320. Also, for these examples, the emergency session may not require authentication and integrity protection. Therefore UE305may attempt to initiate the emergency session as part of an evolved packet system (EPS) mobility management (EMM) procedure with a mobility management entity such as MME314.

According to some examples for the EMM procedure, logic and/or features of UE305may be capable of delivering the emergency payload via an emergency attach to MME314through a wireless communication channel with eNB312. MME314may use emergency IWF316to facilitate the delivery of the emergency payload to PSAP320. This use may include possible protocol translations associated with moving the emergency payload from a wireless network to PSAP320.

In some examples where attempts to initiate the emergency session fail, logic and/or features at UE305may at least temporarily store the emergency payload in a memory structure that maintains an EMM context table. A timestamp to indicate a time when the NOVES was invoked may also be stored with the emergency payload in the EMM context table. Subsequent reattempts to initialize the emergency session may be made to deliver this emergency payload and its timestamp to PSAP320. According to some examples, upon either aborting attempts to initiate the emergency session or based on successfully initiating the emergency session and delivering the emergency payload, the stored emergency payload may be removed, erased or purged from the EMM context table.

In some examples, the NAS layer may attempt to initiate an emergency session that does require integrity protection. For these examples, logic and/or features of UE305may be capable of attempting to initiate the emergency session as part of an EPS session management (ESM) procedure. According to some examples for the ESM procedure, logic and/or features of UE305may be capable of delivering the emergency payload via use of one or more uplink Generic NAS transport messages routed over a wireless communication channel with eNB312and through MME314to emergency IWF316. Similar what was mentioned above for the EMM procedure, MME314may use emergency IWF316to facilitate the delivery of the emergency payload to PSAP320. This use may include possible protocol translations associated with the uplink Generic NAS transport messages used to deliver the emergency payload to PSAP320.

In some examples where attempts to initiate the emergency session fail, logic and/or features at UE305may at least temporarily store the emergency payload in a memory structure that maintains an ESM context table. A timestamp to indicate a time when the NOVES was invoked may also be stored with the emergency payload in the ESM context table. Similar to the EMM procedure, subsequent reattempts to initialize the emergency session may be made to deliver this emergency payload and its timestamp to PSAP320. According to some examples, upon either aborting attempts to initiate the emergency session or based on successfully initiating the emergency session to deliver the emergency payload, the stored emergency payload may be removed, erased or purged from the ESM context table.

According to some examples, emergency IWF316may be used to also translate message received from PSAP320to protocols used by the wireless network that includes MME314and eNB312to enable acknowledgements of receipt of the emergency payload to be received by UE305. For example, using the ESM procedure that includes uplink generic NAS transport messages, emergency IWF316may receive an acknowledgement of delivery of the emergency payload from PSAP320and then forward the acknowledgement to MME314. For this example, either emergency IWF316or MME314may then use one or more downlink generic NAS transport messages to cause the acknowledgement to UE305to be delivered to UE305over a communication link with eNB312.

In some examples, emergency IWF316may act as a service center towards PSAP320. In some deployment scenarios MME314and emergency IWF316may be co-located. In other deployments IWF316may be located with PSAP320. In either deployment, emergency IWF316may serve as an intermediary that delivers an emergency payload from UE305to PSAP320or forwards acknowledgements to UE305from PSAP320that may indicate receipt of the emergency payload by PSAP320.

FIG. 4illustrates an example block diagram for an apparatus400. Although apparatus400shown inFIG. 4has a limited number of elements in a certain topology, it may be appreciated that the apparatus400may include more or less elements in alternate topologies as desired for a given implementation.

The apparatus400may comprise a computer-implemented apparatus400having a processor circuit420arranged to execute layer422. Layer422may include an application layer or may include various layers of a 3GPP protocol stack such as a NAS layer, an RRC layer or an ESF layer. Layer422may further be arranged to implement one or more software components422-a. It is worthy to note that “a” and “b” and “c” and similar designators as used herein are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value for a=8, then a complete set of software components422-amay include components422-1through422-8. The examples are not limited in this context.

According to some examples, apparatus400may be user equipment (e.g., located at or with UE105/305), capable of operating in compliance with one or more 3GPP LTE Specifications. For example, apparatus400may be capable of communicatively coupling to an LTE and/or LTE-A compliant wireless network via one or more eNBs. The examples are not limited in this context.

In some examples, as shown inFIG. 4, apparatus400includes processor circuit420. Processor circuit420may be generally arranged to execute layer422. The processing circuit420can be any of various commercially available processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application, embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®, Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon®, Atom®, and XScale® processors; and similar processors. Dual microprocessors, multi-core processors, and other multi-processor architectures may also be employed as processing circuit420.

According to some examples, apparatus400may include a payload component422-1. Payload component422-1may be capable of receiving NOVES emergency payload410. For these examples, a NOVES may be invoked by a user of a UE that includes apparatus400. NOVES emergency payload410may include one of an emergency indicator, a voice message, a video or a text message. In some examples, payload component422-1may at least temporarily store these types of emergency payloads as indication(s)423-a, video424-b, voice425-cor text426-din a data structure such as a lookup table (LUT) maintained at the UE.

In some examples, indication(s)423-a, video424-b, voice425-cor text426-dmay include pre-configured or pre-recorded content that may be added to or replace NOVE emergency payload410. For example a user that invoked the NOVES by pressing a button or key, touching a display icon or voicing a verbal command. Pressing the button or key, touching the display icon or voicing the verbal command may initiate creation of NOVES emergency payload410and payload component422-1may then add the pre-configured content upon receipt of NOVES emergency payload410.

In some examples, apparatus400may also include an attempt component422-2. Attempt component422-2may be capable of initiating an emergency session. For these examples, the attempt to initiate the emergency session may be part of an EMM or ESM procedure with an MME. The initiation of the emergency session may be include emergency payload Tx attempt(s)415that may attempt to deliver NOVES emergency payload410to a PSAP.

In some examples, apparatus400may also include a deliver component422-3. Deliver component422-3may be capable of delivering NOVES emergency payload410dependent on whether the EMM or the ESM procedure is implemented by attempt component422-2. For examples where the EMM procedure is implemented, deliver component422-3may deliver NOVES emergency payload410upon initiation of the emergency session via an emergency attach to the MME. For examples where the ESM procedure is implemented, deliver component422-3may deliver NOVES emergency payload410upon initiation of the emergency via one or more uplink generic NAS transport messages routed through the MME.

According to some examples, apparatus400may also include an acknowledgement component422-4. Acknowledgement component422-4may be capable of receiving acknowledgement435that may be an acknowledgement of delivery of NOVES emergency payload410to the PSAP following a successful attempt to initiate the emergency session. Acknowledgement component422-4, in some examples, may cause success indication445to be provided to the user that invoked the NOVES. Success indication445may include a visual indication of the successful delivery of the emergency payload and/or may include further instructions that may have been relayed with the acknowledgement.

In some examples, apparatus400may also include a store component422-5. Store component422-5may be capable of storing an emergency payload427-eincluded in or associated with NOVES emergency payload410responsive to a failure to initiate the emergency session by attempt component422-2. In examples were the EMM procedure is implemented by attempt component422-2, emergency payload427-emay be stored by store component422-4in an EMM context table maintained in a memory at the UE that includes apparatus400. In examples where the ESM procedure is implemented by attempt component422-2, emergency payload427-emay be stored by store component422-4in an ESM context table in a memory at the UE that includes apparatus400. In some examples, emergency payload427-emay be also be stored with a timestamp428-fto indicate a time when the NOVES was invoked to indicate the emergency.

According to some examples, apparatus400may also include a reattempt component422-6. Reattempt component422-6may be capable of reattempting to initiate the emergency session to enable delivery component422-3to deliver NOVES emergency payload410to the PSAP. Reattempt component422-6may obtain the emergency payload for NOVES emergency payload410from emergency payload427-e. Reattempt component422-6may also obtain the associated timestamp from timestamp428-f. The obtained emergency payload and associated timestamp may then be included in emergency payload Tx attempt(s)415that may further attempt to deliver NOVES emergency payload410to the PSAP.

In some examples, apparatus400may also include an abort component422-7. Abort component422-7may be capable of causing reattempt component422-6to abort reattempts to initiate the emergency session based on a number of reattempts exceeding a set number of reattempts. The set number may be maintained (e.g., in a LUT) in attempt information429-g. According to some examples, abort component422-7may be capable of maintaining a count of the reattempts by reattempt component422-6and comparing the count to the set number. For these examples, based on the counted number of attempts exceeding the set number, abort component422-7may be capable of preventing reattempt component422-6from making further attempts to initiate the emergency session.

According to some examples, apparatus400may also include a purge component422-8. Purge component422-8may be capable of removing or causing the emergency payload stored by store component422-5to be removed. For example, the emergency payload may be removed from ESM or EMM context tables depending on which procedure is used to attempt or reattempt to initiate the emergency session. Removal of the emergency payload may be responsive to exceeding the set number of reattempts as determined by abort component422-7. Removal of the emergency payload may be responsive to receiving acknowledgement435that indicates delivery of NOVES emergency payload410to the PSAP. Removal of the emergency payload may be responsive to a user of the UE including apparatus400manually aborting any attempts or reattempts to deliver NOVES emergency payload410to the PSAP. Manual aborting may be due the emergency situation no longer being an emergency or the NOVES was invoked by mistake. Removal of the emergency payload is not limited to the above examples, other examples for removal may apply.

Various components of apparatus400and a device implementing apparatus400may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Example connections include parallel interfaces, serial interfaces, and bus interfaces.

A logic flow may be implemented in software, firmware, and/or hardware. In software and firmware embodiments, a logic flow may be implemented by computer executable instructions stored on at least one non-transitory computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage. The embodiments are not limited in this context.

FIG. 5illustrates an example of a logic flow500. Logic flow500may be representative of some or all of the operations executed by one or more logic, features, or devices described herein, such as apparatus400. More particularly, logic flow500may be implemented by payload component422-1, attempt component422-2, deliver component422-3, acknowledge component422-4, store component422-5, reattempt component422-6, abort component422-7or purge component422-8.

In the illustrated example shown inFIG. 5, logic flow500at block502may receive an emergency payload associated with a NOVES, the emergency payload to include at least one of an emergency indicator, a voice message, a video or a text message. In some examples, payload component422-2of apparatus400(e.g., included in UE105/305) may receive NOVES emergency payload410that may include or may cause payload component to add preconfigured information to the received emergency payload.

According to some examples logic flow500at block504may attempt to initiate an emergency session as part of an EMM or ESM procedure with an MME (e.g., MME114/314), the emergency session may be initiated to deliver the emergency payload to a PSAP (e.g., PSAP120/320.

In some examples, logic flow500at block506may store the emergency payload at a UE used by a user to invoke the NOVES responsive to a failure to initiate the emergency session. For these examples, store component422-5may store emergency payload information to include a timestamp to indicate a time when the NOVES was invoked in either an EMM or ESM context table as mentioned above.

According to some examples, logic flow500at block508may reattempt to initiate the emergency session to deliver the emergency payload to the PSAP. For these examples, reattempt component422-6may make reattempts included in emergency payload Tx attempt(s)415. Logic flow at block510may abort attempts to initiate the emergency session based on a number of reattempts exceeding a set number of reattempts. Abort component422-7may maintain a count of reattempts and may abort reattempts by reattempt component422-6based on the count to reattempts exceeding a set number reattempts. Logic flow at block512may remove the emergency payload from the UE. Purge component422-8may cause the emergency payload to be removed from the UE following abort component422-7causing the reattempts to be aborted.

According to some examples, logic flow500at block514, if the reattempts don't exceed the set number or reattempts that lead to aborting reattempts, an acknowledgement may be received. For these examples, the acknowledgement may be an acknowledgement of delivery of the emergency payload to the PSAP following a successful attempt to initiate the emergency session. Also, logic flow500at block514may remove the emergency payload from UE based on receiving the acknowledgement. For these examples, acknowledgement component422-4may receive the acknowledgement and purge component422-8may cause removal of the emergency payload responsive to receiving the acknowledgement.

FIG. 6illustrates an embodiment of a storage medium600. The storage medium600may comprise an article of manufacture. In some examples, storage medium600may include any non-transitory computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage. Storage medium600may store various types of computer executable instructions, such as instructions to implement logic flow500. Examples of a computer readable or machine readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The examples are not limited in this context.

FIG. 7illustrates an embodiment of a device700for use in a broadband wireless access network. Device700may implement, for example, apparatus400, storage medium600and/or a logic circuit770. The logic circuit770may include physical circuits to perform operations described for apparatus400. As shown inFIG. 7, device700may include a radio interface710, baseband circuitry720, and computing platform730, although examples are not limited to this configuration.

The device700may implement some or all of the structure and/or operations for the apparatus400, storage medium600and/or logic circuit770in a single computing entity, such as entirely within a single device. Alternatively, the device700may distribute portions of the structure and/or operations for apparatus400, storage medium600and/or logic circuit770across multiple computing entities using a distributed system architecture, such as a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context.

In one embodiment, radio interface710may include a component or combination of components adapted for transmitting and/or receiving single carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK) and/or orthogonal frequency division multiplexing (OFDM) symbols) although the embodiments are not limited to any specific over-the-air interface or modulation scheme. Radio interface710may include, for example, a receiver712, a transmitter716and/or a frequency synthesizer714. Radio interface710may include bias controls, a crystal oscillator and/or one or more antennas718-f. In another embodiment, radio interface710may use external voltage-controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and/or RF filters, as desired. Due to the variety of potential RF interface designs an expansive description thereof is omitted.

Baseband circuitry720may communicate with radio interface710to process receive and/or transmit signals and may include, for example, an analog-to-digital converter722for down converting received signals, a digital-to-analog converter724for up converting signals for transmission. Further, baseband circuitry720may include a baseband or physical layer (PHY) processing circuit726for PHY link layer processing of respective receive/transmit signals. Baseband circuitry720may include, for example, a processing circuit728for medium access control (MAC)/data link layer processing. Baseband circuitry720may include a memory controller732for communicating with MAC processing circuit728and/or a computing platform730, for example, via one or more interfaces734.

In some embodiments, PHY processing circuit726may include a frame construction and/or detection module, in combination with additional circuitry such as a buffer memory, to construct and/or deconstruct communication frames (e.g., containing subframes). Alternatively or in addition, MAC processing circuit728may share processing for certain of these functions or perform these processes independent of PHY processing circuit726. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

Computing platform730may further include a network interface760. In some examples, network interface760may include logic and/or features to one or more 3GPP LTE or LTE-A specifications or standards. For these examples, network interface760may include logic and/or features to support communication interfaces described in the one or more 3GPP LTE or LTE-A specifications. For these examples, network interface760may enable an apparatus400located with a UE to communicatively couple to base station or eNB for a wireless network via a wireless communications link.

Device700may be, for example, user equipment, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, wireless access point, base station, node B, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Accordingly, functions and/or specific configurations of device700described herein, may be included or omitted in various embodiments of device700, as suitably desired. In some embodiments, device700may be configured to be compatible with protocols and frequencies associated one or more of the 3GPP LTE Specifications and/or IEEE 802.16 Standards for WMANs, and/or other broadband wireless networks, cited herein, although the examples are not limited in this respect.

Embodiments of device700may be implemented using single input single output (SISO) architectures. However, certain implementations may include multiple antennas (e.g., antennas718-f) for transmission and/or reception using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using multiple input multiple output (MIMO) communication techniques.

It should be appreciated that the exemplary device700shown in the block diagram ofFIG. 7may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would be necessarily be divided, omitted, or included in embodiments.

FIG. 8illustrates an embodiment of a broadband wireless access system800. As shown inFIG. 8, broadband wireless access system800may be an internet protocol (IP) type network comprising an internet810type network or the like that is capable of supporting mobile wireless access and/or fixed wireless access to internet810. In one or more embodiments, broadband wireless access system800may comprise any type of orthogonal frequency division multiple access (OFDMA) based wireless network, such as a system compliant with one or more of the 3GPP LTE Specifications and/or IEEE 802.16 Standards, and the scope of the claimed subject matter is not limited in these respects.

In the exemplary broadband wireless access system800, access service networks (ASN)814,818are capable of coupling with base stations (BS)814,820(or eNBs), respectively, to provide wireless communication between one or more fixed devices816and internet810, or one or more mobile devices822and Internet810. One example of a fixed device816and a mobile device822is UE105, with the fixed device816comprising a stationary version of UE105and the mobile device822comprising a mobile version of UE105. ASN812may implement profiles that are capable of defining the mapping of network functions to one or more physical entities on broadband wireless access system800. Base stations814,820(or eNBs) may comprise radio equipment to provide RF communication with fixed device816and mobile device822, such as described with reference to device800, and may comprise, for example, the PHY, MAC, RLC or PDCP layer equipment in compliance with a 3GPP LTE Specification or an IEEE 802.16 Standard. Base stations814,820(or eNBs) may further comprise an IP backplane to couple to Internet810via ASN812,818, respectively, although the scope of the claimed subject matter is not limited in these respects.

Broadband wireless access system800may further comprise a visited connectivity service network (CSN)824capable of providing one or more network functions including but not limited to proxy and/or relay type functions, for example authentication, authorization and accounting (AAA) functions, dynamic host configuration protocol (DHCP) functions, or domain name service controls or the like, domain gateways such as public switched telephone network (PSTN) gateways or voice over internet protocol (VoIP) gateways, and/or internet protocol (IP) type server functions, or the like. However, these are merely example of the types of functions that are capable of being provided by visited CSN824or home CSN826, and the scope of the claimed subject matter is not limited in these respects. Visited CSN824may be referred to as a visited CSN in the case where visited CSN824is not part of the regular service provider of fixed device816or mobile device822, for example where fixed816or mobile device822is roaming away from their respective home CSN826, or where broadband wireless access system800is part of the regular service provider of fixed device816or mobile device822but where broadband wireless access system800may be in another location or state that is not the main or home location of fixed device816or mobile device822.

Fixed device816may be located anywhere within range of one or both base stations814,820, such as in or near a home or business to provide home or business customer broadband access to Internet810via base stations814,820and ASN812,818, respectively, and home CSN826. It is worthy to note that although fixed device816is generally disposed in a stationary location, it may be moved to different locations as needed. Mobile device822may be utilized at one or more locations if mobile device822is within range of one or both base stations814,820, for example.

In accordance with one or more embodiments, operation support system (OSS)828may be part of broadband wireless access system800to provide management functions for broadband wireless access system800and to provide interfaces between functional entities of broadband wireless access system800. Broadband wireless access system800ofFIG. 8is merely one type of wireless network showing a certain number of the components of broadband wireless access system800, and the scope of the claimed subject matter is not limited in these respects.

Some examples may be described using the expression “coupled”, “connected”, or “capable of being coupled” along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, descriptions using the terms “connected” and/or “coupled” may indicate that two or more elements are in direct physical or electrical contact with each other. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

In some examples, example first computer-implemented methods for transmitting an emergency payload may include receiving, at a UE capable of operating in compliance with one or more 3GPP LTE standards that may include LTE-A, an emergency payload associated with a NOVES. The emergency payload may include at least one of an emergency indicator, a voice message, a video or a text message. The first computer-implemented methods may also include attempting to transmit the emergency payload to a PSAP via a wireless communication network. The first computer-implemented methods may also include storing the emergency payload at the UE responsive to an unsuccessful attempt to transmit the emergency payload to the PSAP. The first computer-implemented methods may also include reattempting to transmit the emergency payload until a successful attempt to transmit the emergency payload has occurred or the NOVES has been aborted.

In some examples, the example first computer-implemented methods may also include purging the emergency payload from the UE responsive to an acknowledgement from the PSAP of receipt of the emergency payload or responsive to the NOVES being aborted.

According to some examples, the example first computer-implemented methods may also include reattempting to transmit the stored emergency payload for a configurable number of times. The NOVES may be aborted based on a number of reattempts exceeding the configurable number of times.

In some examples for the example first computer-implemented methods, the unsuccessful attempt to transmit the emergency payload to the PSAP may be caused by one of inadequate signal quality to attach to the wireless communication network, the wireless communication network is temporarily inoperable, or the wireless communication network is congested or overloaded.

According to some examples, the example first computer-implemented methods may also include storing the emergency payload with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency or location information to indicate the location of the UE at the time when the NOVES was invoked.

In some examples for the example first computer-implemented methods, the emergency indicator may include a home intruder alert, a burglary in progress alert, a medical emergency, a vehicle accident, a lost person, an abduction alert or a workplace violence alert.

According to some examples for the example first computer-implemented methods, the UE may include an emergency call handling application to receive the emergency payload associated with the NOVES. For these examples, the emergency call handing application may also attempt to transmit the emergency payload to the PSAP, store the emergency payload responsive to the unsuccessful attempt, reattempt to transmit the stored emergency payload, or purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

In some examples for the example first computer-implemented methods, a NAS layer of a 3GPP protocol stack may be executed by a processor circuit of the UE. For these examples, the NAS layer may receive the emergency payload associated with the NOVES. The NAS layer may also attempt to transmit the emergency payload to the PSAP, store the emergency payload responsive to the unsuccessful attempt, reattempt to transmit the stored emergency payload, or purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

According to some examples for the example first computer-implemented methods, an RRC layer of a 3GPP protocol stack may be executed by a processor circuit of the UE. For these examples, the RRC layer may receive the emergency payload associated with the NOVES. The RRC lay may also attempt to transmit the emergency payload to the PSAP, store the emergency payload responsive to the unsuccessful attempt, reattempt to transmit the stored emergency payload, or purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

In some examples for the example first computer-implemented methods, an emergency store and forward layer of a 3GPP protocol stack may be executed by a processor circuit of the UE. For these examples, the emergency store and forward layer may receive the emergency payload associated with the NOVES. The emergency store and forward layer may also attempt to transmit the emergency payload to the PSAP, store the emergency payload responsive to the unsuccessful attempt, reattempt to transmit the stored emergency payload, or purge the emergency payload from the UE responsive to the acknowledgement or responsive to the NOVES being aborted.

According to some examples for the example first computer-implemented methods, at least one machine readable medium may include a plurality of instructions that in response to being executed on a computing device cause the computing device to carry out the example first computer-implemented method as mentioned above.

In some examples, a first apparatus to transmit an emergency payload may comprise means for performing the second computer-implemented methods as mentioned above.

According to some examples, an example second apparatus to transmit an emergency payload may include a processor circuit for a UE capable of operating in compliance with one or more 3GPP LTE standards that may include LTE-A. The example second apparatus may also include a NAS layer of a 3GPP protocol stack for execution by the processor circuit. For these examples, the NAS layer may include a payload component to receive an emergency payload associated with a NOVES. The emergency payload may include at least one of an emergency indicator, a voice message, a video or a text message. The NAS layer may also include an attempt component to attempt to initiate an emergency session as part of an EMM or ESM procedure with an MME. The emergency session may be initiated to deliver the emergency payload to a PSAP. The NAS layer may also include a store component to store the emergency payload at the UE responsive to a failure to initiate the emergency session. The NAS layer may also include a reattempt component to reattempt to initiate the emergency session to deliver the emergency payload to the PSAP. The NAS layer may also include an acknowledgement component to receive an acknowledgement of delivery of the emergency payload to the PSAP following a successful attempt to initiate the emergency session. For some examples, the emergency payload may then be removed from the UE based on receiving the acknowledgement.

In some examples for the example second apparatus, the NAS layer may also include an abort component to cause the reattempt component to abort reattempts to initiate the emergency session based on a number of reattempts exceeding a set number of reattempts. The NAS layer may also include a purge component to remove the emergency payload from the UE.

According to some examples for the example second apparatus, the store component may store the emergency payload with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency or location information to indicate the location of the UE at the time when the NOVES was invoked.

In some examples for the example second apparatus, the failure to initiate the emergency session may be caused by one of inadequate signal quality to initiate the emergency session with the MME, a wireless communication network managed by the MME is temporarily inoperable or the wireless communication network managed by the MME is congested or overloaded.

According to some examples for the example second apparatus, the attempt component may attempt to initiate the emergency session as part of the EMM procedure. For these examples, the NAS layer may also include a deliver component to deliver the emergency payload via an emergency attach to the MME.

In some examples for the example second apparatus, the store component to store the emergency payload responsive to the failure to initiate the emergency session may include storing the emergency payload in an EMM context table along with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency. For these examples, the deliver component may deliver the stored emergency payload with the timestamp responsive to a successful reattempt to initiate the emergency session.

According to some examples for the example second apparatus, the attempt component to attempt to initiate the emergency session as part of the ESM procedure may include a deliver component for execution by the processor circuit to deliver the emergency payload upon initiation of the emergency session via one or more uplink generic NAS transport messages routed through the MME.

In some examples for the example second apparatus, the store component to store the emergency payload responsive to the failure to initiate the emergency session may include storing the emergency payload in an ESM context table along with a timestamp to indicate a time when the NOVES was invoked to indicate an emergency. For these examples, the deliver component may deliver the stored emergency payload with the timestamp responsive to a successful reattempt to initiate the emergency session.

According to some examples for the example second apparatus, the one or more uplink generic NAS transport messages may be routed through the MME to an emergency IWF. For these examples, the emergency IWF may act as a service center for the PSAP and may translate the one or more uplink generic NAS transport messages to deliver the emergency payload to the PSAP.

In some examples for the example second apparatus, the IWF may receive an acknowledgement of delivery of the emergency payload from the PSAP and may forward the acknowledgement to the MME for the MME to use one or more downlink generic NAS transport messages to deliver the acknowledgement to the acknowledge component.

According to some examples, an example at least one machine readable medium may include a plurality of instructions that in response to being executed on an application for UE capable of operating in compliance with one or more 3GPP LTE standards that may include LET-A cause the application to receive an indication that a user of the UE has invoked a NOVES. The instructions may also cause the application to attempt to attach to a wireless network via an emergency APN to deliver an emergency payload to a PSAP. The emergency payload may include at least one of an emergency indicator, a voice message, a video or a text message. The instructions may also cause the application to store the emergency payload with a timestamp to indicate a time when the NOVES was invoked. The emergency payload may be stored responsive to an unsuccessful attempt to attach to the wireless network. The instructions may also cause the application to reattempt to attach to the wireless network a set number of times. The instructions may also cause the application to deliver the emergency payload with the timestamp responsive to a successful attachment. The instructions may also cause the application to receive an acknowledgement of delivery of the emergency payload to the PSAP and erase the stored emergency payload with the timestamp based on the acknowledgement.

In some examples for the at least one machine readable medium, the set number of times comprises a configurable number of times.

According to some examples for the at least one machine readable medium, the instructions may also cause the application to abort reattempts to attach to the wireless network based on a number of reattempts exceeding the configurable number of times.

In some examples for the at least one machine readable medium, the emergency payload may include at least one of an emergency indicator, a voice message, a video or a text message comprises a preconfigured emergency indicator, a pre-configured voice message, a pre-configured video or a pre-configured text message.

According to some examples for the at least one machine readable medium, the emergency indicator may include a home intruder alert, a burglary in progress alert, a medical emergency, a vehicle accident, a lost person, an abduction alert or a workplace violence alert.

In some examples for the at least one machine readable medium, the unsuccessful attempt to attach to the wireless network via the APN may be caused by one of an inadequate signal quality to attach to the wireless communication network, the wireless communication network is temporarily inoperable, the wireless communication network is congested or the APN is congested or temporarily overloaded.

In some examples, an example third apparatus to transmit an emergency payload for a UE capable of operating in compliance with one or more 3GPP LTE standards that may include LTE-may include means for receiving an indication that a user of the UE has invoked a NOVES. The example third apparatus may also include means for attempting to attach to a wireless network via an emergency APN to deliver an emergency payload to a PSAP. The emergency payload may include at least one of an emergency indicator, a voice message, a video or a text message. The example third apparatus may also include means for storing the emergency payload with a timestamp to indicate a time when the NOVES was invoked. The emergency payload may be stored responsive to an unsuccessful attempt to attach to the wireless network. The example third apparatus may also include means for reattempting to attach to the wireless network a set number of times. The example third apparatus may also include means for delivering the emergency payload with the timestamp responsive to a successful attachment. The example third apparatus may also include means for receiving an acknowledgement of delivery of the emergency payload to the PSAP and erase the stored emergency payload with the timestamp based on the acknowledgement.

According to some examples for the example third apparatus, the unsuccessful attempt to attach to the wireless network via the APN may be caused by one of an inadequate signal quality to attach to the wireless communication network, the wireless communication network is temporarily inoperable, the wireless communication network is congested or the APN is congested or temporarily overloaded.