WO2021158294A1 - Atténuation d'interférence pour communication d'urgence - Google Patents

Atténuation d'interférence pour communication d'urgence Download PDF

Info

Publication number
WO2021158294A1
WO2021158294A1 PCT/US2020/065176 US2020065176W WO2021158294A1 WO 2021158294 A1 WO2021158294 A1 WO 2021158294A1 US 2020065176 W US2020065176 W US 2020065176W WO 2021158294 A1 WO2021158294 A1 WO 2021158294A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile device
network
emergency
network connection
nearby
Prior art date
Application number
PCT/US2020/065176
Other languages
English (en)
Inventor
Amer Aref Hassan
Roy D. Kuntz
Original Assignee
Microsoft Technology Licensing, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Technology Licensing, Llc filed Critical Microsoft Technology Licensing, Llc
Publication of WO2021158294A1 publication Critical patent/WO2021158294A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H04W76/36—Selective release of ongoing connections for reassigning the resources associated with the released connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria

Definitions

  • a landline In traditional 911 or other emergency service calls, for example in the United States, a landline’s location is automatically sent to a dispatcher receiving the call.
  • enhanced 911 e ., e911 or El 12 in Europe
  • a mobile device e.g., a cell phone.
  • FIG. 1 illustrates an example schematic diagram showing an overview of an emergency service communication system according to some examples of the present disclosure.
  • FIG. 2 illustrates an example timing diagram for communication services according to some examples of the present disclosure.
  • FIG. 3 illustrates an example mobile device for displaying information according to some examples of the present disclosure.
  • FIG. 4 illustrates a flowchart of a technique for providing an emergency service at a mobile device according to some examples of the present disclosure.
  • FIG. 5 illustrates a block diagram of an example machine which may implement one or more of the techniques discussed herein according to some examples of the present disclosure.
  • a nearby emergency communication may be given priority for connecting, channels, quality of service metrics, or the like.
  • a nearby emergency communication may include a communication, such as a text or call, that occurs within a communication range of a device.
  • the communication range may include a direct communication range, such as based on whether a signal may be sent or received directly between the device and the nearby device.
  • Protocols for determining or detecting nearby emergency communications may include packet sniffing, network monitoring, or direct communications, such as via Bluetooth, Wi-Fi direct, NFC, or other device to device communication protocols.
  • Network connections that are disconnected or prevented from connection may include Wi-Fi, Bluetooth, cellular radio connection (e.g., to a radio tower, such as an eNodeB), SMS services, satellite, etc.
  • the mobile device may disconnect from a network connection, scale back bandwidth (e.g., lower quality of content received, for example by reducing video quality or switching from a video call to an audio call, or limiting download speeds or accessibility, particularly in background downloads) or inhibit connection to a new network connection in response to identifying that a nearby mobile device has initiated an emergency communication.
  • the systems and methods described herein solve the technical issues involved with congested networks and insufficient bandwidth that causes interference or disconnection during emergency communications.
  • Emergency communications may be given channel priority, but may still face interference from devices proximate to a device initiating an emergency communication (e.g., a call).
  • Techniques that rely on a top-down control do not fully solve these issues because a coordinating device may not be aware of all interfering devices, may not be able to communicate with an interfering device, or may cause further interference issues by communicating with an interfering device.
  • the solutions described herein provide the technical capabilities to disconnect from or prevent from connecting to a new network at a mobile device, for example without coordinated action (e.g., without receiving a message or indication from a coordinating device, such as a radio tower or an emergency service).
  • the mobile device may identify an emergency communication initiating or in progress, and in response disconnect from a network or prevent itself from connecting to a new network, such as to improve the emergency communication by removing interference or potential interference.
  • the solutions described herein may remove interference quicker than a coordinated system as well, since the actions may be taken at individual mobile devices as soon as the emergency communication is identified (rather than needing to wait for a coordinating device to send a communication to each individual mobile device, which in some examples may not even occur).
  • the solutions described herein may separately, or in combination, provide technical capabilities to a mobile device for determining whether to full connect or reconnect to a network when an emergency communication is on-going in the area of the mobile device. For example, a mobile device may temporarily connect or reconnect to a network in a limited network connection (e.g., in a listening only mode) to determine whether an emergency communication is on-going.
  • the limited network connection may include not transmitting or transmitting only signaling necessary to receive messages.
  • the systems and methods described herein may include determining whether to disconnect from a network or not connect to a new network when an emergency communication is identified.
  • a mobile device may determine whether its connection or communication is causing interference or may potentially cause interference to the emergency communication, and if so, disconnect or not connect. In examples where no interference is determined or predicted, the mobile device may continue the connection or connect to the new network, and may continue to monitor the emergency communication to determine whether to disconnect.
  • the systems and methods described herein may include determining whether to use a network.
  • a technique may include canceling data downloads (e.g., background data), restricting non-emergency voice calls, lowering bandwidth usage, or the like.
  • the systems and methods described herein may determine whether to disconnect or not connect to a new network (including using a network) based on connection issues with an identified emergency communication at a nearby device. For example, when the nearby device is having trouble connecting or staying connected, a mobile device may disconnect from a voice call to limit interference. In other examples, identifying the emergency communication may not cause disconnection or no new connections, such as when the emergency communication does not have connection or stability issues.
  • FIG. 1 illustrates an example schematic diagram 100 showing an overview of an emergency service communication system according to some examples of the present disclosure.
  • the schematic diagram 100 includes a mobile device 102 and a nearby device 104 initiating or continuing an emergency communication (e.g., calling 911).
  • the mobile device 102 may identify that the nearby device 104 has initiated or has an on-going emergency communication (e.g., a call), for example in communication with cell tower 106.
  • the mobile device 102 may identify the emergency communication based on network traffic, such as via a wireless signal received by the mobile device 102 (e.g., intercepted or monitored from a communication between the nearby device 104 and the cell tower 106).
  • Emergency communications may be sent in the clear, or partially sent in the clear (e g., without encryption or without being encoded) such that the mobile device 102 may identify the emergency communication without any breach of privacy of the nearby device 104.
  • the mobile device 102 may recognize emergency call setup messages sent by mobile device 104.
  • the mobile device 102 may be connected to the cell tower 106 or a second cell tower 108, or another device 110.
  • the mobile device 102 may disconnect from one or more connected network in response to identifying the emergency communication emanating from the nearby device 104.
  • the mobile device 102 may not disconnect from all or any networks, for example the mobile device 102 may disconnect from a connection with the cell tower 106, but not the cell tower 108, thus maintaining a network connection (but optionally disconnecting from another network connection, depending on whether the cell towers 106 and 108 connect with the mobile device 102 via the same network).
  • the mobile device 102 may disconnect from the cell tower 106 because that tower is in the emergency communication.
  • Other examples may include placing the mobile device 102 into an airplane mode (thus disconnecting from all networks, or a plurality of networks, or any connected networks).
  • the mobile device 102 may disconnect from the cell tower 106 based on a monitored quality of the emergency communication, such as by identifying a threshold number of re-sent voice packets or a threshold number of attempts to reconnect by the nearby device 104, for example.
  • the mobile device may maintain a network connection (e.g., with device 110), such as when that network connection is unlikely to or is not interfering with the emergency communication.
  • the network connection may be limited (e.g., listening only), or have a limited range (e.g., Bluetooth, NFC, etc.) making the network connection unlikely to interfere with the emergency communication.
  • the mobile device 102 is moving from an area or network connection that does not affect the emergency communication (e.g., when the mobile device 102 is connected to the cell tower 108) to an area or network connection that does affect or potentially affect the emergency communication (e.g., when the mobile device is attempting to, is scheduled to, or is connected to the cell tower 106).
  • the mobile device 102 may refrain from connecting to the cell tower 106 so as to not interfere with the emergency communication.
  • the mobile device 102 may provide a warning to a user of the mobile device 102 that connection will be lost (e.g., when the connection with the cell tower 108 disconnects because the cell tower 108 is out of range), for example because the mobile device 102 is entering an area with an emergency.
  • the mobile device 102 may maintain a connection with the cell tower 108 longer than typically because the cell tower 106 is unavailable.
  • the mobile device 102 may attempt alternate network connections, such as via Wi-Fi or device to device connections, satellite, or another cell tower other than 106.
  • the mobile device 102 may sever a network connection (e.g., with cell tower 106) quicker than usual, move up a handoff (e.g., to cell tower 108), or the like.
  • the change to a different cell tower may be done before network protocols typically cause the mobile device 102 to switch towers.
  • a mobile device 102 may typically switch towers when a received signal strength indicator (RSSI) from a first cell tower (current connection) is exceed by an RSSI from a second tower (to be connected).
  • RSSI received signal strength indicator
  • the mobile device 102 may switch to the second cell tower as soon as a minimum RSSI is received, rather than waiting until the RSSI received from the second cell tower exceeds the RSSI from the first cell tower.
  • FIG. 2 illustrates an example timing diagram 200 for communication services according to some examples of the present disclosure.
  • the timing diagram 200 illustrates communications between a network 206 and other devices.
  • This example timing diagram 200 illustrates the specific example where an emergency device 202 (also called a nearby device herein) and a user device 204 are both connected to the network 206 for simplicity of illustration, but other examples may feature similar timing diagrams (e.g., where the user device 204 is connected to another network than network 206).
  • the network 206 may be a proxy for a network device (e.g., a cell tower), and thus devices 202 and 204 may be connected to the same or different devices, even when connected to the same network 206.
  • a network device e.g., a cell tower
  • the timing diagram shows the emergency device 202 initiating an emergency communication or in an on-going emergency communication (e.g., making a call to an emergency service).
  • the user device 204 identifies from network traffic at event 208 that the emergency communication has been initiated or is on-going (e.g., when the user device 204 connects to the network 206 the on-going emergency communication may be identified, when previously initiated). For example, the user device 204 may receive the emergency communication in the clear (or part of the message) and may identify it as an emergency call based upon the number called or information in a message header. The user device 204 may sever its network connection to the network 206 in response to the event 208.
  • the mobile device may attempt to temporarily connect or reconnect to the network 206.
  • the emergency communication is on-going between the emergency device 202 and the network 206, identified at the user device 204 based on network traffic (e.g., wireless signals, a direct communication from the emergency device 202, or the like)
  • the temporary connection may be severed between the user device 204 and the network 206.
  • the mobile device may temporarily connect or reconnect again to try to determine whether the emergency communication is still on-going.
  • the mobile device 204 may fully connect to the network 206 (or another network).
  • the emergency device 202 or the network 206 may send an indication to the mobile device 204 when temporarily connected that the emergency communication has ended.
  • the mobile device 204 may monitor air interference (e.g., for received signals) without connecting.
  • FIG. 3 illustrates an example mobile device 300 for displaying information according to some examples of the present disclosure.
  • the mobile device 300 may include a user interface 302 for displaying information related to the techniques described herein.
  • the user interface 302 may indicate that the mobile device 302 is disconnecting or not connecting to a network due to a nearby emergency communication.
  • the user interface 302 may indicate timing for reconnecting or connecting (e.g., will attempt again in 1 minute).
  • the user interface 302 may indicate that the mobile device 300 has entered airplane mode.
  • the mobile device 300 may provide a warning of disconnection (e.g., 1, 3, 5, 10, etc. seconds), such as via the user interface 302 or via an audible warning.
  • the disconnection delay may balance user need against the need for the emergency call.
  • the user of the mobile device 300 may have an emergency in addition to the identified emergency communication, at overlapping times.
  • the mobile device 300 may override the disconnection protocol and connect (e.g., when the user dials 911). In an example, thought the mobile device 300 enters airplane mode or disconnects from a network, the mobile device 300 may retain an emergency connection (e g., to dial 911).
  • the user interface 302 may include information about the emergency, such as areas to avoid (e.g., in the case of a fire, natural disaster, car crash, etc.).
  • the user interface 302 may provide one or more networks that the mobile device 300 can connect to (e.g., ones that do not or are not predicted to interfere with the emergency communication) for user selection.
  • FIG. 4 illustrates a flowchart of a technique 400 for providing an emergency service at a mobile device according to some examples of the present disclosure.
  • the technique 400 may be performed using a processor or processors of the mobile device (e.g., as discussed in further detail below with respect to FIG. 5).
  • the technique 400 includes an operation 410 to monitor network traffic, on a network, for emergency communications by other mobile devices.
  • the network traffic may be monitored via a network connection based on wireless signals received by the mobile device.
  • the technique 400 includes an operation 420 to identify from the network traffic that a nearby mobile device has initiated an emergency communication to an emergency service system.
  • the initiation may be identified based on the wireless signal sent by the nearby mobile device.
  • the nearby mobile device may be within a communication range of the mobile device (e.g., a direct communication range, such as without any intermediary device needed for communication between the mobile device and the nearby mobile device).
  • the emergency communication may be identifiable via the network traffic.
  • the technique 400 includes an operation 430 to in response to identifying that the nearby mobile device has initiated the emergency communication, disconnect or limit connectivity (e.g., reduce bandwidth or interference, such as by switching to a lower quality video content or to an audio connection), at the mobile device, from at least one network connection or inhibit connection to a new network connection.
  • the mobile device may be placed into airplane mode.
  • disconnecting from the at least one network connection may include disconnecting from the at least one network connection in response to identifying that the network traffic indicates that the nearby mobile device has failed to connect the to the emergency service system or is having difficulty in connecting or maintaining a connection, such as based on the wireless signals received by the mobile device.
  • the technique 400 may include disconnecting from at least one other network in response to identifying that the nearby mobile device has initiated the emergency communication.
  • all networks may be disconnected or prevented from being connected to at the mobile device in response to identifying the initiation of the emergency communication.
  • the network that is disconnected is the network with the network connection used to identify the initiation of the emergency communication.
  • the technique 400 may include an operation to wait a period of time and temporarily reconnect to the at least one network connection after the period of time, for example via a limited network connection.
  • This operation may include, in response to determining that the nearby mobile device is still (e.g., at the time of temporary reconnection by the mobile device) trying to connect to the emergency service system, or determining that the nearby mobile device is connected to the emergency service system in an ongoing connection, disconnecting from the network.
  • This operation may include in response to determining that the nearby mobile device is no longer trying to connect to the emergency service system and determining that the nearby mobile device is not connected to the emergency service system in an ongoing connection based on the wireless signals received by the mobile device, reconnecting to the network via a fully connected network connection.
  • FIG. 5 illustrates a block diagram of an example machine 500 which may implement one or more of the techniques (e g., methodologies) discussed herein according to some examples of the present disclosure.
  • the machine 500 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 500 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 500 may be configured to perform the methods of FIG. 5.
  • the machine 500 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the machine 500 may be a user device, a remote device, a second remote device or other device which may take the form of a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA personal digital assistant
  • STB set-top box
  • mobile telephone a smart phone
  • web appliance a web appliance
  • network router switch or bridge
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms (hereinafter “modules”).
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Machine 500 may include a hardware processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 504 and a static memory 506, some or all of which may communicate with each other via an interlink (e.g., bus) 508.
  • a hardware processor 502 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 504 e.g., main memory
  • static memory 506 e.g., static memory
  • the machine 500 may further include a display unit 510, an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse).
  • the display unit 510, input device 512 and UI navigation device 514 may be a touch screen display.
  • the machine 500 may additionally include a storage device (e g , drive unit) 516, a signal generation device 518 (e.g., a speaker), a network interface device 520, and one or more sensors 521, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 500 may include an output controller 528, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • the storage device 516 may include a machine readable medium 522 on which is stored one or more sets of data structures or instructions 524 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 524 may also reside, completely or at least partially, within the main memory 504, within static memory 506, or within the hardware processor 502 during execution thereof by the machine 500.
  • one or any combination of the hardware processor 502, the main memory 504, the static memory 506, or the storage device 516 may constitute machine readable media.
  • machine readable medium 522 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 524.
  • machine readable medium may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 524.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 500 and that cause the machine 500 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); Solid State Drives (SSD); and CD-ROM and DVD-ROM disks.
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • the instructions 524 may further be transmitted or received over a communications network 526 using a transmission medium via the network interface device 520.
  • the machine 500 may communicate with one or more other machines utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • wireless data networks e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®
  • IEEE 802.15.4 family of standards e.g., Institute of Electrical and Electronics Engineers (IEEE
  • the network interface device 520 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 526.
  • the network interface device 520 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input multiple-output
  • MISO multiple-input single-output
  • the network interface device 520 may wirelessly communicate using Multiple User MIMO techniques.
  • Example 1 is a method performed by a mobile device, the method comprising: monitoring network traffic, on a network via a network connection based on wireless signals received by the mobile device, for emergency communications by other mobile devices; identifying from the network traffic based on the wireless signals, at a processor of the mobile device, that a nearby mobile device has initiated an emergency communication to an emergency service system, the nearby mobile device within a communication range of the mobile device, and the emergency communication identifiable via the network traffic; and in response to identifying that the nearby mobile device has initiated the emergency communication, disconnecting, at the mobile device, from at least one network connection or inhibiting connection to a new network connection.
  • Example 2 the subject matter of Example 1 includes, in response to identifying that the nearby mobile device has initiated the emergency communication, disconnecting from at least one other network.
  • Example 3 the subject matter of Examples 1-2 includes, wherein disconnecting from the at least one network connection includes placing the mobile device into airplane mode.
  • Example 4 the subject matter of Examples 1-3 includes, waiting a period of time; and temporarily reconnecting to the at least one network connection via a limited network connection after the period of time has expired.
  • Example 5 the subject matter of Example 4 includes, in response to determining that the nearby mobile device is still trying to connect to the emergency service system or determining that the nearby mobile device is connected to the emergency service system in an ongoing connection, disconnecting from the at least one network connection.
  • Example 6 the subject matter of Examples 4-5 includes, in response to determining that the nearby mobile device is no longer trying to connect to the emergency service system and determining that the nearby mobile device is not connected to the emergency service system in an ongoing connection based on the wireless signals received by the mobile device, reconnecting to the at least one network connection via a fully connected network connection.
  • Example 7 the subject matter of Examples 1-6 includes, wherein disconnecting from the at least one network connection includes disconnecting from the at least one network connection in response to identifying that the network traffic indicates that the nearby mobile device has failed to connect the to the emergency service system based on the wireless signals received by the mobile device.
  • Example 8 is a mobile device for providing an emergency service, the mobile device comprising: one or more hardware processors; a memory, storing instructions, which when executed, cause the one or more hardware processors to perform operations comprising: monitor network traffic, on a network via a network connection based on wireless signals received by the mobile device, for emergency communications by other mobile devices; identify from the network traffic based on the wireless signals that a nearby mobile device has initiated an emergency communication to an emergency service system, the nearby mobile device within a communication range of the mobile device, and the emergency communication identifiable via the network traffic; and in response to identifying that the nearby mobile device has initiated the emergency communication, disconnect from at least one network connection or inhibiting connection to a new network connection.
  • Example 9 the subject matter of Example 8 includes, wherein the one or more hardware processors are further configured to, in response to identifying that the nearby mobile device has initiated the emergency communication, disconnect from at least one other network.
  • Example 10 the subject matter of Examples 8-9 includes, wherein disconnecting from the at least one network connection includes placing the mobile device into airplane mode.
  • Example 11 the subject matter of Examples 8-10 includes, wherein the one or more hardware processors are further configured to: wait a period of time; and temporarily reconnect to the at least one network connection or connect to the new network connection via a limited network connection after the period of time has expired.
  • Example 12 the subject matter of Example 11 includes, wherein the one or more hardware processors are further configured to, in response to determining that the nearby mobile device is still trying to connect to the emergency service system or determining that the nearby mobile device is connected to the emergency service system in an ongoing connection, disconnecting from the at least one network connection.
  • Example 13 the subject matter of Examples 11-12 includes, in response to determining that the nearby mobile device is no longer trying to connect to the emergency service system and determining that the nearby mobile device is not connected to the emergency service system in an ongoing connection based on the wireless signals received by the mobile device, reconnecting to the at least one network connection via a fully connected network connection.
  • Example 14 the subject matter of Examples 8-13 includes, wherein disconnecting from the at least one network connection includes disconnecting from the at least one network connection in response to identifying that the network traffic indicates that the nearby mobile device has failed to connect the to the emergency service system based on the wireless signals received by the mobile device.
  • Example 15 is an apparatus for providing an emergency service, the apparatus comprising: means for monitoring network traffic, on a network via a network connection based on wireless signals received by the mobile device, for emergency communications by other mobile devices; means for identifying from the network traffic based on the wireless signals, at a processor of the mobile device, that a nearby mobile device has initiated an emergency communication to an emergency service system, the nearby mobile device within a communication range of the mobile device, and the emergency communication identifiable via the network traffic; and in response to identifying that the nearby mobile device has initiated the emergency communication, means for disconnecting, at the mobile device, from at least one network connection or means for inhibiting connection to a new network connection.
  • Example 16 the subject matter of Example 15 includes, in response to identifying that the nearby mobile device has initiated the emergency communication, means for disconnecting from at least one other network.
  • Example 17 the subject matter of Examples 15-16 includes, wherein the means for disconnecting from the at least one network connection include means for placing the mobile device into airplane mode.
  • Example 18 the subject matter of Examples 15-17 includes, means for waiting a period of time; and means for temporarily reconnecting to the at least one network connection via a limited network connection after the period of time has expired.
  • Example 19 the subject matter of Example 18 includes, in response to determining that the nearby mobile device is still trying to connect to the emergency service system or determining that the nearby mobile device is connected to the emergency service system in an ongoing connection, means for disconnecting from the at least one network connection.
  • Example 20 the subject matter of Examples 18 19 includes, in response to determining that the nearby mobile device is no longer trying to connect to the emergency service system and determining that the nearby mobile device is not connected to the emergency service system in an ongoing connection based on the wireless signals received by the mobile device, means for reconnecting to the at least one network connection via a fully connected network connection.
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-20.
  • Example 22 is an apparatus comprising means to implement of any of Examples 1-20.
  • Example 23 is a system to implement of any of Examples 1-20.
  • Example 24 is a method to implement of any of Examples 1-20.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés qui peuvent être utilisés pour fournir un service d'urgence par l'intermédiaire d'un dispositif mobile. Ces systèmes et procédés peuvent consister à utiliser un dispositif mobile pour surveiller un trafic de réseau pour des communications d'urgence par un autre dispositif mobile. Les systèmes et les procédés peuvent consister à identifier à partir du trafic de réseau qu'un dispositif mobile proche a initié une communication d'urgence vers un système de service d'urgence. Ces systèmes et procédés peuvent consister, en réponse à l'identification du fait que le dispositif mobile voisin a initié la communication d'urgence, à déconnecter, au niveau du dispositif mobile, au moins une connexion réseau ou inhiber une connexion vers une nouvelle connexion réseau.
PCT/US2020/065176 2020-02-03 2020-12-16 Atténuation d'interférence pour communication d'urgence WO2021158294A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202016780476A 2020-02-03 2020-02-03
US16/780,476 2020-02-03

Publications (1)

Publication Number Publication Date
WO2021158294A1 true WO2021158294A1 (fr) 2021-08-12

Family

ID=74003968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/065176 WO2021158294A1 (fr) 2020-02-03 2020-12-16 Atténuation d'interférence pour communication d'urgence

Country Status (1)

Country Link
WO (1) WO2021158294A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8249546B1 (en) * 2009-08-18 2012-08-21 Sprint Spectrum L.P. Method and system for improving access to emergency services over a shared wireless communications medium
US20170201461A1 (en) * 2016-01-12 2017-07-13 Qualcomm Incorporated Lte based v2x communication qos and congestion mitigation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8249546B1 (en) * 2009-08-18 2012-08-21 Sprint Spectrum L.P. Method and system for improving access to emergency services over a shared wireless communications medium
US20170201461A1 (en) * 2016-01-12 2017-07-13 Qualcomm Incorporated Lte based v2x communication qos and congestion mitigation

Similar Documents

Publication Publication Date Title
US11197180B2 (en) Terminal apparatus, method, and recording medium
EP3641382A1 (fr) Procédé et dispositif de surveillance de liaison sans fil
CN104780525B (zh) 调整终端到终端通信传输功率的方法、设备、组头和系统
US9485664B2 (en) Idle mode cell selection for licensed shared access
US20200383166A1 (en) Packet Data Network Connection Re-Establishment
CN110213798B (zh) 一种基于Femto网关的分流方法及装置
WO2022095759A1 (fr) Dispositif électronique, procédé de communication sans fil et support de stockage lisible par ordinateur
US20150215216A1 (en) Call Connection Establishment Via Service Specific Access Control
JP4940785B2 (ja) 無線装置、無線通信システム、無線装置の無線通信方法及び無線通信システムの無線通信方法
EP3029995B1 (fr) Dispositif de traitement de communications, procédé de commande et programme de commande de ceux-ci, système de traitement de communications
WO2018095424A1 (fr) Procédé et dispositif de gestion d'état de terminal
US9609491B2 (en) Server apparatus, communication apparatus, and communication method
US20130148562A1 (en) Wireless communication apparatus, data distribution apparatus, and data updating method
WO2021158294A1 (fr) Atténuation d'interférence pour communication d'urgence
EP2849482B1 (fr) Dispositif de gestion, dispositif de commande et procédé de communication
US20210378051A1 (en) Radio Barrier Processing Method And Network Device
US20160044525A1 (en) Method of providing information on a server status, user equipment, and communication system
KR102174043B1 (ko) 서비스 인터럽션 보고
WO2019082348A1 (fr) Dispositif de surveillance et système de surveillance
US9100487B1 (en) Conditional voicemail routing in wireless communication networks
JP6959896B2 (ja) 無線通信システム
WO2016162047A1 (fr) Simplification de fonctionnement de réseau sans fil isolé efficace
KR20150073103A (ko) 유휴 모드 및 접속 모드와 관련된 사용자 장비 이동성 정보의 세부사항 시그널링
CN110062444B (zh) 数据处理方法、终端设备和存储介质
JP6539891B2 (ja) 基地局システム、通信端末、無線通信システム、基地局システムの制御方法、通信端末の制御方法、及び、プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20829159

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20829159

Country of ref document: EP

Kind code of ref document: A1