Techniques for supporting emergency short message service (SMS) messages in limited service scenarios

Abstract

This application sets forth techniques for routing emergency (SMS) messages in limited service scenarios. A technique can be implemented by a network entity associated with a mobile network operator (MNO), and includes the steps of: (1) receiving an SMS message from a wireless device, and (2) in response to determining that (i) the wireless device is communicatively coupled to the MNO in a limited service connection due to not being affiliated to the MNO, and (ii) a destination address of the SMS message corresponds to an emergency service: (a) identifying at least one emergency service provider corresponding to the MNO, and (b) providing at least a portion of the SMS message to the emergency service provider.

Description

Technical Field

[0001] The described embodiments describe techniques for managing emergency Short Message Service (SMS) messages sent by wireless devices operating in limited service scenarios. Specifically, these techniques include server-side and device-side implementations that enable emergency SMS messages to be routed to appropriate emergency service providers in limited service scenarios. Background Art

[0002] Many countries around the world are introducing emergency texting services, and there are several examples of successful implementations. For example, emergency texting services are available in many cities in the United States, and these services have been used to report medical emergencies, fires, and robberies. Emergency texting services work by enabling users to send text messages to a special phone number connected to an emergency service provider (e.g., "911" in the United States). Trained personnel eventually receive the message and can then provide assistance. In this regard, emergency texting services are valuable additional services and are likely to become more widely used in the future.

[0003] Emergency text messaging services work well when a given wireless device has access to standard wireless services (e.g., data, voice, short message service (SMS)) provided by the mobile network operator (MNO) to which the wireless device subscribes. However, various problems can arise when the wireless device operates in a limited service scenario. For example, a limited service scenario can occur when the wireless device roams onto a network provided by a different MNO that is not obligated to provide standard wireless services (such as SMS messaging) to the wireless device. Instead, the wireless device is typically only allowed to make emergency calls, thereby limiting the number of options available to the user of the wireless device during a potential emergency. Therefore, if the wireless device is operating in a limited service scenario, the user may encounter problems when attempting to transmit a text message to emergency services.

[0004] In view of the foregoing, there exists a need for improved management of emergency text messages originating from wireless devices operating in limited service scenarios. Summary of the Invention

[0005] This application describes techniques for managing emergency Short Message Service (SMS) messages sent by wireless devices operating in limited service scenarios. Specifically, these techniques include server-side and device-side implementations that enable emergency SMS messages to be routed to appropriate emergency service providers in limited service scenarios.

[0006] One embodiment describes a method for routing emergency (SMS) messages in a limited service scenario. According to some embodiments, the method may be implemented by a network entity associated with a mobile network operator (MNO) and includes the steps of: (1) receiving an SMS message from a wireless device, and (2) in response to determining that (i) the wireless device is communicatively coupled to the MNO under a limited service connection because it is not affiliated with the MNO, and (ii) a destination address of the SMS message corresponds to an emergency service: (a) identifying at least one emergency service provider corresponding to the MNO, and (b) providing at least a portion of the SMS message to the emergency service provider.

[0007] Another embodiment sets forth another method for routing emergency SMS messages in a limited service scenario. According to some embodiments, the method may be implemented by a network entity associated with an MNO and includes the steps of: (1) receiving a request from a wireless device to access wireless services provided by the MNO, and (2) in response to determining that the wireless device is not affiliated with the MNO, providing to the wireless device: (i) an indication that the MNO supports emergency SMS messages, and (ii) an SMSC address of a Short Message Service Center (SMSC) corresponding to the MNO.

[0008] Yet another embodiment describes another method for routing emergency SMS messages in a limited service scenario. According to some embodiments, the method may be implemented by a wireless device and includes the following steps: (1) providing a request to a network entity associated with an MNO to which the wireless device is not affiliated to access wireless services provided by the MNO, (2) receiving from the network entity: (i) an indication that the MNO supports emergency SMS messages, and (ii) an SMSC address of an SMSC corresponding to the MNO, and (3) updating a configuration of the wireless device such that all SMS messages sent by the wireless device are assigned to the SMSC address.

[0009] Other embodiments include a non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to implement the methods and techniques described in this disclosure. Still other embodiments include a hardware computing device that includes a processor that can be configured to cause the hardware computing device to implement the methods and techniques described in this disclosure.

[0010] Other aspects and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate by way of example the principles of the described embodiments.

[0011] This summary is provided for the purpose of summarizing some example embodiments only, in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the above-mentioned features are merely examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The present disclosure will be more readily understood through the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals designate like structural elements.

[0013] Figure 1 Illustrated is a block diagram of different components of an example system configured to implement the various techniques described herein, according to some embodiments.

[0014] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view of certain components of a wireless device illustrated in FIG.

[0015] Figure 3A A method implemented by a network entity for routing emergency SMS messages in a limited service scenario is illustrated according to some embodiments.

[0016] Figure 3B Illustrate the combination according to some embodiments Figure 3A The various entities described may implement Figure 3A A sequence diagram of the method.

[0017] Figure 4 Illustrate an alternative method implemented by a network entity for routing emergency SMS messages in limited service scenarios according to some embodiments (relative to Figure 3A method).

[0018] Figure 5 Illustrate an alternative method implemented by a wireless device for routing emergency SMS messages in limited service scenarios according to some embodiments (relative to Figure 3A method and combined with Figure 4 described).

[0019] Figure 6 A block diagram illustrating exemplary elements of a mobile wireless device according to some embodiments is illustrated. DETAILED DESCRIPTION

[0020] This section describes representative applications of the methods and apparatus according to the present application. These examples are provided solely to add context and aid in understanding the described embodiments. Therefore, it will be apparent to one skilled in the art that the described embodiments may be practiced without some or all of these specific details. In other cases, well-known processing steps have not been described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are possible, such that the following examples should not be considered limiting.

[0021] In the following detailed description, reference is made to the accompanying drawings which form a part of the specification and in which are shown by way of illustration specific embodiments in accordance with the described embodiments. Although these embodiments are described in sufficient detail to enable those skilled in the art to practice the described embodiments, it is to be understood that these examples are not limiting; other embodiments may be used and modifications may be made without departing from the spirit and scope of the described embodiments.

[0022] Limited service scenarios may arise in a variety of situations, including when a wireless device (1) enters into a roaming condition with a "foreign" mobile network operator (MNO) that is different from the wireless device's "home" (i.e., "home") MNO, and (2) no service agreement exists between the foreign MNO and the home MNO obligating the foreign MNO to provide wireless service to the wireless device. In some cases, a network entity (e.g., a server device) associated with the foreign MNO may receive a request from the wireless device to transmit an SMS message to emergency services (e.g., 911 in the United States, 112 in Europe, etc.). When this occurs, it is in the best interest of society for the MNO to send the SMS message to the appropriate emergency service provider (despite the fact that the MNO has no contractual obligation to do so).

[0023] An SMS message sent by a wireless device typically includes at least: (1) a source address (e.g., a telephone number) associated with the wireless device, (2) a Short Message Service Center (SMSC) address associated with a home MNO, (3) a destination address (e.g., a telephone number or short code) of a recipient to whom the SMS message should be delivered, and (4) the message content (e.g., text, image, etc.) to be delivered to the recipient. Typically, the SMSC address is a fixed value obtained from a Subscriber Identity Module (SIM) associated with the home MNO and accessible to the wireless device. In this regard, when a user attempts to deliver an SMS message under the aforementioned roaming conditions, the SMS message will be addressed to the SMSC of the home MNO rather than the SMSC of the foreign MNO. Therefore, when an emergency SMS message is received, the foreign MNO is left with two options, each of which is problematic.

[0024] First, the external MNO could simply ignore the SMS message, potentially exacerbating any danger the user of the wireless device is experiencing. Second, the external MNO could route the SMS message to the home MNO's SMSC (based on the default / home SMSC address included in the SMS message). However, this approach is problematic given that roaming conditions mean there is a geographic difference between the user's / wireless device's current physical location and the physical location of the home MNO's SMSC. In any case, the home MNO's SMSC would attempt to route the SMS message to an emergency service provider that is geographically proximate to the home MNO's SMSC (and likely far from the user's / wireless device's current physical location). Consequently, the emergency service provider would need to work with the user to identify an emergency service provider that is geographically proximate to the user and then proceed to act as an intermediary between the two, potentially exacerbating any danger the user of the wireless device is experiencing.

[0025] Therefore, embodiments describe techniques for managing emergency SMS messages sent by wireless devices operating in limited service scenarios. Specifically, these techniques include server-side and device-side implementations that enable emergency SMS messages to be routed to appropriate emergency service providers in limited service scenarios.

[0026] One embodiment sets forth a method implemented by a network entity associated with an MNO and comprising the steps of: (1) receiving an SMS message from a wireless device, and (2) in response to determining (i) the wireless device is communicatively coupled to the MNO under a limited service connection because it is not affiliated with the MNO, and (ii) a destination address of the SMS message corresponds to an emergency service: (a) identifying at least one emergency service provider corresponding to the MNO, and (b) providing at least a portion of the SMS message to the emergency service provider.

[0027] According to some embodiments, the limited service connection provides access to a first set of functionality that is restricted relative to a second set of functionality that is generally accessible when the wireless device is communicatively coupled to a primary MNO associated with the wireless device. For example, the first set of functionality may include only emergency voice services and emergency SMS messaging services, while the second set of functionality may include data services, voice services, and SMS messaging services.

[0028] According to some embodiments, the network entity may utilize any feasible method to effectively determine that the destination address of the SMS message corresponds to an emergency service. For example, the network entity may perform a lookup of the destination address in a database of destination addresses of emergency service providers capable of communicating with the network entity.

[0029] In some embodiments, the SMS message includes an SMSC address of an SMSC that: (1) is associated with the primary MNO, and (2) is ignored by the network entity. This advantageously enables the disclosed technology to be implemented without modifying the configuration of the wireless device. Specifically, the network entity can ignore the SMSC because it instead routes the SMS message to emergency services (e.g., directly or indirectly). However, it is noted that the network entity may simply route the SMS message to an SMSC that is geographically related to the wireless device (such as an SMSC associated with the network entity with which the wireless device is communicating). For example, the network entity may identify an SMSC that is geographically proximate to the current location of the wireless device and then route the SMS message to that SMSC. The SMSC may then route the message to the appropriate emergency service provider.

[0030] Additionally or alternatively, the configuration of the wireless device may be modified such that, before providing an SMS message to a network entity, the wireless device: (1) detects that the destination address corresponds to an emergency service, and (2) excludes the SMSC field and corresponding value from the SMS message. Alternatively, the configuration of the wireless device may be modified such that, before providing an SMS message to a network entity, the wireless device: (1) detects that the destination address corresponds to an emergency service, and (2) assigns a fixed value to the SMSC field, wherein the fixed value is not associated with any SMSC. These approaches may be beneficial because they may reduce the overall size of the SMS message and may provide an additional way for the network entity to identify the SMS message as an emergency message. Specifically, the network entity may interpret the excluded SMSC field or the fixed value assigned to the SMSC field as an indication that the wireless device has identified that the emergency context applies to the SMS message.

[0031] Another embodiment describes a method implemented by a network entity associated with an MNO and comprising the steps of: (1) receiving a request from a wireless device to access wireless services provided by the MNO, and (2) in response to determining that the wireless device is not affiliated with the MNO, providing to the wireless device: (i) an indication that the MNO supports emergency SMS messages, and (ii) an SMSC address of an SMSC associated with the MNO. According to this method, the wireless device may update its configuration upon receiving the indication and SMSC address so that the provided SMSC address effectively overrides the primary SMSC address of the home MNO that the wireless device normally utilizes when transmitting SMS messages. In this manner, SMS messages received by the network entity from the wireless device will be directed to the SMSC associated with the MNO, where the SMSC may then route the SMS message to an appropriate emergency service provider.

[0032] According to some embodiments, the network entity may provide the indication and SMSC address via a limited service connection established with the wireless device (in response to determining that the wireless device is not affiliated with an MNO). According to some embodiments, the network entity may provide, in addition to providing the indication and SMSC address, destination address information for at least one available emergency service. This may enable the wireless device to display the destination address information in response to receiving a request to draft a first SMS message (relative to the time the wireless device provided a request to access wireless services provided by the MNO). This may be particularly helpful for notifying a user of the wireless device of emergency services available via SMS messaging.

[0033] Yet another embodiment describes a method implemented by a wireless device and comprising the steps of: (1) providing a request to a network entity associated with an MNO to which the wireless device is not affiliated to access wireless services provided by the MNO, (2) receiving from the network entity: (i) an indication that the MNO supports emergency SMS messages, and (ii) an SMSC address of an SMSC corresponding to the MNO, and (3) updating a configuration of the wireless device such that all SMS messages sent by the wireless device are assigned to the SMSC address. As previously described herein, according to this method, the wireless device may update the configuration upon receiving the SMSC address such that the provided SMSC address effectively overrides the primary SMSC address of the home MNO that the wireless device normally utilizes when transmitting SMS messages.

[0034] According to some embodiments, the network entity may provide the indication and the SMSC address via a limited service connection established with the wireless device. According to some embodiments, the wireless device may receive destination address information for at least one emergency service from the network entity. Similarly, this may enable the wireless device to display the destination address information in response to receiving a request to draft a first SMS message associated with providing the request to the network entity.

[0035] These and other embodiments are referenced below. Figures 1 to 6 however, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for illustrative purposes only and should not be construed as limiting.

[0036] Figure 1 1 illustrates a block diagram of various components of a system 100 configured to implement the various techniques described herein, according to some embodiments. More specifically, Figure 1A brief overview of system 100 is illustrated, which includes a wireless device 102 (also referred to as a device, wireless device, mobile device, user equipment (UE)), etc., a group of base stations 112-1 to 112-N managed by different mobile network operators (MNOs) 114, and an emergency service provider 118 in communication with the MNO 114.

[0037] Wireless device 102 may represent a mobile computing device (e.g., Production Apple Watch, etc.). Base stations 112-1 through 112-N may represent cellular wireless network elements including evolved Node Bs (eNodeBs or eNBs) and / or next generation Node Bs (gNodeBs or gNBs) configured to communicate with wireless device 102. MNOs 114 may represent different wireless service providers that provide specific cellular wireless services (e.g., voice, data, SMS, etc.) to which wireless device 102 may subscribe, such as via a subscription account of a user of wireless device 102. According to some embodiments, each MNO 114 may manage and / or be associated with various infrastructure elements, including a network entity 115 (used in conjunction with base stations 112 to provide the various wireless services offered by MNO 114) and a short message service center (SMSC) (used to facilitate the sending of SMS messages). Additional MNO infrastructure entities, such as those used for account management and billing, are not shown.

[0038] like Figure 1 As shown, the wireless device 102 may include processing circuitry (which may include one or more processors 104 and memory 106), at least one embedded universal integrated circuit card (eUICC) 108, and baseband radio circuitry 110 for transmitting and receiving cellular radio frequency signals. The baseband radio circuitry 110 may include analog hardware components, such as antennas and amplifiers, as well as digital processing components, such as signal processors (and / or general / limited-purpose processors) and associated memory. In some embodiments, in addition to or in lieu of the eUICC 108, the wireless device 102 includes one or more physical UICCs 109 (also known as Subscriber Identity Module (SIM) cards). The components of the wireless device 102 work together to enable the wireless device 102 to provide useful features to the user of the wireless device 102, such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and Internet connectivity.

[0039] The eUICC 108 may be configured to store a plurality of electronic SIM (eSIM) profiles for accessing cellular wireless services provided by different MNOs 114 via connections to their respective cellular wireless networks through base stations 112-1 through 112-N. For example, the eUICC 108 may be configured to store and manage one or more eSIM profiles for one or more MNOs 114 for different subscriptions associated with the wireless device 102. To enable access to services provided by the MNOs, the eSIM profiles may be reserved for subsequent download and installation into the eUICC 108. In some embodiments, the eUICC 108 obtains the one or more eSIM profiles from one or more associated MNO provisioning servers (eSIMs). Figure 1 The MNO provisioning server may be maintained by the MNO 114, an OEM manufacturer, a third-party entity, etc. Communication of eSIM profile data between the MNO provisioning server and the eUICC 108 (or between the MNO provisioning server and processing circuitry of the wireless device 102 external to the eUICC 108 (e.g., processor 104)) may use a secure communication channel.

[0040] According to some embodiments, a given emergency service provider 118 may represent an entity capable of providing emergency services to a user (e.g., a 911 call center in the United States, a 112 call center in Europe, etc.). According to some embodiments, one or more of the MNOs 114 may be configured to communicate with one or more of the emergency service providers 118 without utilizing one or more SMSCs 116 (although SMSCs may still be utilized if desired, as described herein). This capability may be implemented using any acceptable method, such as a direct communication line, an indirect communication line, etc., between the emergency service provider 118 and the MNO 114 using any communication protocol. In this way, the MNO 114 may act as an intermediary between the emergency service provider 118 and the wireless device 102 in limited service scenarios, where utilization of the SMSC 116 may otherwise cause any of the various issues described herein. According to an alternative approach, as described herein, the approach may involve the wireless device 102 receiving an SMSC address of an SMSC 116 associated with an MNO 114 through which the wireless device 102 operates in a limited service scenario, which SMSC 116 may act as an intermediary between the wireless device 102 and an appropriate emergency service provider 118.

[0041] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view 200 of certain components of the wireless device 102 is provided. Figure 2As shown, the processor 104 in conjunction with the memory 106 may implement a host operating system (OS) 202 configured to execute applications 204 (eg, native OS applications and user applications). Figure 2 As shown, the eUICC 108 may be configured to implement an eUICC OS 206 that is configured to manage the hardware resources of the eUICC 108 (e.g., a processor and memory embedded in the eUICC 108). The eUICC OS 206 may also be configured to manage the eSIM profiles 208 stored by the eUICC 108, for example, by downloading, installing, deleting, enabling, disabling, modifying, or otherwise performing management of the eSIM profiles 208 within the eUICC 108 and providing access to the eSIM profiles 208 to the baseband radio circuitry 110 to provide access to wireless services to the wireless device 102. The eUICC 108 OS may include an eSIM profile manager 210 that may perform management functions for various eSIM profiles 208. Figure 2 In the illustrated example, each eSIM profile 208 may include a number of SMSC addresses 212 associated with the SMSC 116 of the MNO to which the eSIM profile 208 corresponds. Note that each SMSC address 212 is different from the destination (i.e., recipient) address (e.g., phone number, short code, etc.) to which the SMS message should be delivered. Figure 2 Not illustrated, each eSIM profile 208 may also implement one or more applets that, in conjunction with the baseband radio circuitry 110 and the eUICC 108 , may enable the wireless device 102 to communicate with the MNO 114 and provide useful features to the user of the wireless device 102 .

[0042] Likewise Figure 2As shown, the baseband radio circuitry 110 of the wireless device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, various radio components, etc.) of the baseband radio circuitry 110. According to some embodiments, the baseband radio circuitry 110 may implement a baseband manager 216 configured to interact with the eUICC 108 to establish a secure channel with the MNO provisioning server and obtain information (such as eSIM profile data) from the MNO provisioning server for use in managing the eSIM profiles 208. The baseband manager 216 may be configured to implement services 218, which represent a collection of software modules instantiated by various applets included in the eUICC 108 that enable eSIM profiles 208. For example, the services 218 may be configured to manage different connections between the wireless device 102 and the MNO 114 depending on the different eSIM profiles 208 enabled within the eUICC 108.

[0043] therefore, Figures 1 to 2 A block diagram of various entities that can be used to implement the technology described herein is now described below. Figures 3A to 3B 、 Figure 4 and Figure 5 A more detailed discussion of these techniques is provided, particularly Figures 1 to 2 The way in which the various entities can work together.

[0044] Figure 3A 1 illustrates a method 300 for routing emergency SMS messages in a limited service scenario according to some embodiments. According to some embodiments, the method 300 may be implemented by the network entity 115 of the MNO 114 such that configuration modifications to the wireless device 102 are unnecessary. Figure 3A As shown, method 300 begins at step 302, where network entity 115 receives an SMS message from wireless device 102. Wireless device 102 may send the SMS message in conjunction with or after establishing a communication channel with network entity 115 / MNO 114, e.g., in a roaming scenario where MNO 114 constitutes a "foreign" MNO 114 that is not affiliated with wireless device 102 and is not contractually obligated to provide wireless services that would otherwise be provided by a "home" MNO 114 affiliated with wireless device 102.

[0045] At step 304, network entity 115 determines that wireless device 102 is communicatively coupled to MNO 114 under a limited service connection because it is not affiliated with MNO 114. Furthermore, at step 306, network entity 115 determines that the destination address of the SMS message corresponds to emergency services. Steps 304 and 306 constitute related determinations because if the SMS message is based on an emergency situation, MNO 114 may choose to take action on the SMS message despite the fact that the limited service connection does not contractually obligate MNO 114 to do so.

[0046] At step 308, the network entity 115 identifies at least one emergency service provider 118 corresponding to the MNO 114. According to some embodiments, this step may involve the network entity 115 performing a lookup of the destination address (identified in step 306) in a database of destination addresses of emergency service providers 118 that are capable of communicating with the network entity 115. Figure 1 As described, this may involve identifying an emergency service provider 118 that has a direct communication line, an indirect communication line, or the like with the network entity 115 .

[0047] Additionally, it should be noted that when executing step 308, network entity 115 may analyze any information, at any level of granularity, accessible to network entity 115 to help narrow down appropriate emergency service providers 118. For example, network entity 115 may be configured to identify the emergency service provider 118 that is closest to the current location of wireless device 102 (e.g., as determined by wireless device 102 itself, network entity 115, or some other entity). As another example, network entity 115 may be configured to analyze the message content of an SMS message to obtain additional context regarding the nature of the emergency, which in turn may be used to narrow down appropriate emergency service providers 118. For example, if network entity 115 detects the term "fire" (or some other word or phrase related to fire), network entity 115 may narrow down the scope to emergency service providers 118 that specialize in firefighting services. As another example, if network entity 115 detects the term "robbery" (or some other word or phrase related to robbery), network entity 115 may narrow down the scope to emergency service providers 118 that interface with police services. It should be noted that the foregoing examples are not intended to be limiting. It should also be noted that the network entity 115 may adjust or exclude any of the aforementioned analyses based on the privacy rules to be enforced.

[0048] At step 310, the network entity 115 provides at least a portion of the SMS message to the emergency service provider 118. For example, the network entity 115 may extract from the SMS message (1) a source address (e.g., a phone number) associated with the wireless device 102, (2) a destination address (e.g., a phone number or short code) associated with the emergency service, and (3) the message content, and provide this information to the emergency service provider 118. Note that the network entity 115 may provide additional information that is not included in the SMS message but that may be helpful to the emergency service provider 118, such as the current location of the wireless device 102, the time at which the emergency service provider 118 received the SMS message, the current signal strength observed between the wireless device 102 and at least one base station 112 through which the wireless device 102 and the network entity 115 communicate, etc. Note that the foregoing examples are not intended to be limiting, and any amount / type of information with any level of granularity may be provided to the emergency service provider 118 without departing from the scope of this disclosure.

[0049] In any case, and as described above, the network entity 115 may utilize an appropriate channel to provide the aforementioned information to the emergency service provider 118, such as a direct communication line, an indirect communication line, etc. Figure 3A Not illustrated, but the network entity 115 may receive a response from the emergency service provider 118 and provide the response to the wireless device 102. These steps may then be repeated any number of times to enable communication between the user of the wireless device 102 and the emergency service provider 118 to occur appropriately.

[0050] Figure 3B The above combination according to some embodiments is illustrated Figure 3A A sequence diagram 320 depicts the manner in which various entities may implement method 300. Figure 3B As shown, sequence diagram 320 begins at step 322, which involves wireless device 102 establishing a limited service connection (according to the various techniques described herein) with network entity 115. At step 324, wireless device 102 transmits an SMS message to network entity 115. For example, the SMS message may be transmitted after a user of wireless device 102 drafts the SMS message relating to emergency services and explaining the nature of the emergency.

[0051] At step 326, the network entity 115 determines that the destination address of the SMS message corresponds to an emergency service (e.g., using the method described above in conjunction with Figure 3A At step 328, the network entity 115 identifies at least one emergency service provider 118 corresponding to the MNO (e.g., using the techniques described above in conjunction with Figure 3AAt step 330, network entity 115 provides at least a portion of the SMS message to emergency service provider 118 (e.g., using the techniques described above in conjunction with Figure 3A 310). Figure 3B As shown, step 330 may be performed without utilizing SMSC 116 (of the "home" MNO 114 or another MNO) (although SMSC 116 may still be utilized if desired, as described herein).

[0052] Then, at step 332, the emergency service provider 118 may provide a response to the network entity 115 (e.g., as described above in conjunction with Figure 3A Again, as described Figure 3B As shown, step 332 may be performed without utilizing SMSC 116 (of the "home" MNO 114 or another MNO) (although an SMSC may still be utilized if desired, as described herein). At step 334, network entity 115 may provide a response to wireless device 102. Steps 324 through 334 may then be repeated to enable communication between the user of wireless device 102 and emergency service provider 118 to occur appropriately.

[0053] Figure 4 Illustrate an alternative method for routing emergency SMS messages in limited service scenarios according to some embodiments (relative to Figure 3A Specifically, and in combination with the above Figures 3A to 3B Unlike the techniques described, this alternative approach may involve utilizing SMSC 116. According to some embodiments, method 400 may be implemented by network entity 115 of MNO 114.

[0054] like Figure 4As shown, method 400 begins at step 402, where network entity 115 receives a request from wireless device 102 to access wireless services provided by MNO 114 (e.g., in a roaming scenario, as described herein). At step 404, network entity 115 determines that wireless device 102 is not affiliated with MNO 114. For example, this may involve network entity 115 identifying that wireless device 102 is affiliated with a "home" MNO 114, which has users that MNO 114 is not contractually obligated to support. As another example, network entity 115 may identify that there are some users that are contractually obligated to support "home" MNO 114, but wireless device 102 is not among these users. Note that the foregoing examples are not intended to be limiting, and step 404 may involve network entity 115 effectively identifying that it is not obligated to provide the wireless services (e.g., data, voice, SMS, etc.) that wireless device 102 typically obtains through its "home" MNO 114.

[0055] At step 406, network entity 115 provides wireless device 102 with an indication that MNO 114 supports emergency SMS messages. This indication can be beneficial because it puts wireless device 102 on notice that, while access to standard wireless services will be unavailable, access to emergency services will still be available. At step 408, network entity 115 provides wireless device 102 with the SMSC address of a Short Message Service Center (SMSC) 116 corresponding to MNO 114. Thus, steps 406 and 408 can result in wireless device 102 updating its configuration so that the SMSC address provided by network entity 115 effectively overrides any existing SMSC address utilized by wireless device 102 when transmitting SMS messages. In this way, all SMS messages (such as emergency SMS messages) will be routed to MNO 114's SMSC 116, which is likely geographically proximate to / associated with wireless device 102. SMSC 116 (and / or other entities) can then route such emergency SMS messages to the appropriate emergency service provider 118. Combined with the following Figure 5 A more detailed explanation of the manner in which the wireless device 102 updates its configuration is provided.

[0056] Figure 5 Illustrate an alternative method for routing emergency SMS messages in limited service scenarios according to some embodiments (relative to Figure 3A Method 300 and in combination with the above Figure 4 According to some embodiments, the method 500 may be implemented by the wireless device 102 attempting to transmit an emergency SMS message through the MNO 114. Figure 5As shown, the method 500 begins at step 502, where the wireless device 102 provides a request to a network entity 115 associated with an MNO 114 to which the wireless device is not affiliated to access wireless services provided by the MNO 114 (e.g., as described above in conjunction with Figure 4 402).

[0057] At step 504, the wireless device 102 receives an indication from the network entity 115 that the MNO 114 supports emergency SMS messaging (e.g., as described above in conjunction with Figure 4 At step 506, the wireless device 102 receives the SMSC address of the SMSC 116 corresponding to the MNO 114 from the network entity 115 (e.g., as described above in conjunction with Figure 4 At step 508, the wireless device 102 updates the configuration of the wireless device 102 so that all SMS messages sent by the wireless device 102 are assigned to the SMSC address received at step 506. In this way, the wireless device 102 effectively covers the SMSC address of the "home" SMSC 116 affiliated with the "home" MNO 114 to which the wireless device 102 subscribes. Again, this helps to mitigate the various issues described herein that may occur if emergency SMS messages sent by the wireless device 102 are routed to the "home" SMSC 116.

[0058] Figure 6 1 illustrates a detailed view of a representative computing device 600 that may be used to implement the various methods described herein according to some embodiments. Specifically, the detailed view illustrates various components that may be included in the wireless device 102. Figure 6 As shown, computing device 600 may include a processor 602, which represents a microprocessor or controller for controlling the overall operation of computing device 600. Computing device 600 may also include a user input device 608, which allows a user of computing device 600 to interact with computing device 600. For example, user input device 608 may take a variety of forms, such as buttons, a keypad, a dial, a touch screen, an audio input interface, a visual / image capture input interface, input in the form of sensor data, and the like. Furthermore, computing device 600 may include a display 610, which may be controlled by processor 602 to display information to the user. A data bus 616 may facilitate data transfer between at least storage device 640, processor 602, and controller 613. Controller 613 may be used to interact with and control various devices via an equipment control bus 614. Computing device 600 may also include a network / bus interface 611 communicatively coupled to data link 612. In the case of a wireless connection, network / bus interface 611 may include a wireless transceiver.

[0059] The computing device 600 also includes a storage device 640, which may include a single disk or multiple disks (e.g., a hard drive) and a storage management module that manages one or more partitions within the storage device 640. In some embodiments, the storage device 640 may include flash memory, semiconductor (solid-state) memory, or the like. The computing device 600 may also include random access memory (RAM) 620 and read-only memory (ROM) 622. The ROM 622 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 620 may provide volatile data storage and store instructions related to the operation of the computing device 600. The computing device 600 may also include a secure element (SE) 624, such as the eUICC 108, the UICC 109, or another secure storage device for cellular wireless system access by the wireless device 102.

[0060] Wireless Terminology

[0061] According to various embodiments described herein, the terms "wireless communication device," "wireless device," "mobile wireless device," "mobile station," and "user equipment (UE)" may be used interchangeably herein to describe one or more common consumer electronic devices that may be capable of performing the processes associated with various embodiments of the present disclosure. According to various specific implementations, any of these consumer electronic devices may relate to: a cellular telephone or smartphone, a tablet computer, a laptop computer, a notebook computer, a personal computer, a netbook computer, a media player device, an e-reader device, Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which may include communication via one or more wireless communication protocols, such as protocols used to communicate over the following networks: wireless wide area networks (WWANs), wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), near field communication (NFC), cellular wireless networks, fourth generation (4G) long term evolution (LTE), advanced LTE (LTE-A), and / or 5G or other currently or future developed advanced cellular wireless networks.

[0062] In some embodiments, the wireless communication device may also operate as part of a wireless communication system, which may include a group of client devices, which may also be referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP) (e.g., as part of a WLAN) and / or interconnected with each other (e.g., as part of a WPAN and / or "ad hoc" wireless network). In some embodiments, the client device may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless local area network communication protocol). In some embodiments, the WLAN technology may include a Wi-Fi (or more generally, WLAN) wireless communication subsystem or radio component, which may implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future developed IEEE 802.11 technologies.

[0063] In addition, it should be understood that the UE described herein can be configured as a multimode wireless communication device that is also capable of communicating via different third generation (3G) and / or second generation (2G) RATs. In these scenarios, the multimode UE can be configured to prefer attaching to an LTE network that provides a faster data rate throughput over other 3G legacy networks that provide a lower data rate throughput. For example, in some implementations, the multimode UE can be configured to fall back to a 3G legacy network, such as an evolved High Speed ​​Packet Access (HSPA+) network, or a Code Division Multiple Access (CDMA) 2000 Evolution-Data Only (EV-DO) network, when LTE and LTE-A networks are otherwise unavailable.

[0064] The various aspects, embodiments, implementations, or features of the described embodiments may be used individually or in any combination. Various aspects of the described embodiments may be implemented by software, hardware, or a combination of hardware and software. The described embodiments may also be implemented as computer-readable code on a non-transitory computer-readable medium. A non-transitory computer-readable medium is any data storage device that can store data that can then be read by a computer system. Examples of non-transitory computer-readable media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices. Non-transitory computer-readable media may also be distributed on network-coupled computer systems so that the computer-readable code is stored and executed in a distributed manner.

[0065] In connection with this disclosure, it is understood that the use of personally identifiable information should be subject to privacy policies and practices recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0066] For illustrative purposes, the foregoing description uses specific nomenclature to provide a thorough understanding of the described embodiments. However, it will be apparent to those skilled in the art that specific details are not required in order to practice the described embodiments. Therefore, the foregoing descriptions of specific embodiments are presented for purposes of illustration and description. The foregoing descriptions are not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. It will be apparent to those skilled in the art that, in light of the above teachings, many modifications and variations are possible.

Claims

1. A method for routing an emergency Short Message Service (SMS) message in a limited service scenario, the method comprising, by a network entity associated with a Mobile Network Operator (MNO): receiving an SMS message from a wireless device; and In response to determining that (1) the wireless device is communicatively coupled to the MNO under a limited service connection due to not being affiliated with the MNO, and (2) the destination address of the SMS message corresponds to an emergency service: identifying at least one emergency service provider corresponding to the MNO, and At least a portion of the SMS message is provided to the emergency services provider.

2. The method of claim 1, wherein the SMS message is routed to the emergency service provider without utilizing any Short Message Service Center (SMSC).

3. The method of claim 1 , wherein the limited service connection provides access to a first set of functionality that is restricted relative to a second set of functionality that the wireless device is typically able to access when communicatively coupled to a primary MNO associated with the wireless device.

4. The method of claim 3, wherein the SMS message includes an SMSC address of an SMSC, wherein the SMSC: is associated with the primary MNO, and Ignored by the network entity.

5. The method of claim 1 , wherein the wireless device, before providing the SMS message to the network entity: detecting that the destination address corresponds to the emergency service, and The SMSC field and corresponding value are excluded from the SMS message.

6. The method of claim 1 , wherein the wireless device, before providing the SMS message to the network entity: detecting that the destination address corresponds to the emergency service, and The SMSC field is assigned a fixed value, wherein the fixed value is not associated with any SMSC.

7. The method of claim 1 , wherein determining that the destination address of the SMS message corresponds to an emergency service comprises: A lookup for the destination address is performed in a database of destination addresses of emergency service providers with which the network entity is able to communicate.

8. A method for routing an emergency short message service (SMS) message in a limited service scenario, the method comprising, by a network entity associated with a mobile network operator (MNO): receiving a request from a wireless device to access wireless services provided by the MNO; and In response to determining that the wireless device is not affiliated with the MNO, providing to the wireless device: an indication that the MNO supports emergency SMS messaging, and The SMSC address of the Short Message Service Center (SMSC) corresponding to the MNO.

9. The method of claim 8, further comprising providing the indication in conjunction with the SMSC address: A limited service connection is established with the wireless device.

10. The method of claim 9, wherein the limited service connection provides access to a first set of functionality that is restricted relative to a second set of functionality that the wireless device is generally accessible to when communicatively coupled to a primary MNO associated with the wireless device.

11. The method of claim 10, wherein the SMSC address overrides a primary SMSC address associated with the primary MNO.

12. The method of claim 11, wherein the indication causes the wireless device to update a configuration so that all SMS messages are directed to the SMSC address.

13. The method of claim 8, wherein the network entity further provides to the wireless device: at least one destination address information for emergency services.

14. The method of claim 13, wherein the wireless device displays the destination address information in response to receiving a second request to draft a first SMS message related to providing the request to the network entity.

15. A method for routing an emergency Short Message Service (SMS) message in a limited service scenario, the method comprising, by a wireless device: providing, to a network entity associated with a mobile network operator (MNO) to which the wireless device is not affiliated, a request to access wireless services provided by the MNO; Receiving from the network entity: an indication that the MNO supports emergency SMS messaging, and The SMSC address of the Short Message Service Center (SMSC) corresponding to the MNO; as well as A configuration of the wireless device is updated such that all SMS messages transmitted by the wireless device are directed to the SMSC address.

16. The method of claim 15, further comprising, in conjunction with receiving the indication and the SMSC address: A limited service connection is established with the network entity.

17. The method of claim 16, wherein the limited service connection provides access to a first set of functionality that is restricted relative to a second set of functionality that the wireless device is typically able to access when communicatively coupled to a primary MNO associated with the wireless device.

18. The method of claim 17, wherein the SMSC address overrides a primary SMSC address associated with the primary MNO.

19. The method according to claim 15, further comprising: Receiving from the network entity: at least one destination address information for emergency services.

20. The method of claim 19, further comprising, in response to receiving a second request to draft a first SMS message related to providing the request to the network entity: The destination address information is displayed.

Images