WO2014057350A2 - Procédé et système pour déclencher un mode avion pour un équipement utilisateur - Google Patents

Procédé et système pour déclencher un mode avion pour un équipement utilisateur Download PDF

Info

Publication number
WO2014057350A2
WO2014057350A2 PCT/IB2013/002527 IB2013002527W WO2014057350A2 WO 2014057350 A2 WO2014057350 A2 WO 2014057350A2 IB 2013002527 W IB2013002527 W IB 2013002527W WO 2014057350 A2 WO2014057350 A2 WO 2014057350A2
Authority
WO
WIPO (PCT)
Prior art keywords
time
take
monitoring
motion detector
user equipment
Prior art date
Application number
PCT/IB2013/002527
Other languages
English (en)
Other versions
WO2014057350A3 (fr
Inventor
Subash Mandanapu
Satya Mallya
Original Assignee
Orange
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 Orange filed Critical Orange
Publication of WO2014057350A2 publication Critical patent/WO2014057350A2/fr
Publication of WO2014057350A3 publication Critical patent/WO2014057350A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters
    • H04W4/027—Services making use of location information using location based information parameters using movement velocity, acceleration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/12—Details of telephonic subscriber devices including a sensor for measuring a physical value, e.g. temperature or motion

Definitions

  • the present system generally relates to mobile devices or handsets, and more specifically to the activation of the in-flight mode for such devices.
  • Today user equipments such as mobile devices (smartphones, pad, portable computers ...) can use various communication technologies, such as 3G, 4G, WiFi, BluetoothTM, Infra Red ... These technologies can be disruptive to other neighboring electronic devices, especially when the mobile devices are used on board a plane.
  • the present system relates to method for automatically activating an inflight mode on a user equipment on board a plane, the user equipment comprising a motion detector, the method comprising:
  • the monitoring of the user equipment motion, through the motion detector is only limited to the preset time, also called here after a monitoring time-off, from the received take-off time.
  • the start and the duration of the monitoring are controlled in the present system, so as to limit undue battery use, that would limit further use of the user equipment in its in-flight mode (flight mode in short) during the flight.
  • the start and the duration of the monitoring define a monitoring window, limited in time. If the take-off is measured during the time, in an additional embodiment of the present system, the in-flight mode will be activated. Provided take-off is delayed, and the monitoring time-off lapses, another monitoring window will be defined, by requesting an updated take-off time.
  • the present system also relates to a user equipment comprising an in-flight mode and a motion detector, the user equipment being arranged to:
  • the present system also relates to an application embodied on a computer readable medium and arranged to automatically activate an in-flight mode for a user equipment on board a plane, the user equipment comprising a motion detector, the application comprising instructions to: - receive a ⁇ the user equipment a take-off time for the plane,
  • FIG. 1 shows a mobile device in accordance with an embodiment of the present system
  • FIG. 2 shows an exemplary embodiment of the present system
  • FIG. 3 shows an exemplary flowchart for the take-off monitoring in accordance with another embodiment of the present system.
  • FIG. 4 shows an exemplary flowchart for the landing monitoring in accordance with an additional embodiment of the present system.
  • an operative coupling may include one or more of a wired connection and/or a wireless connection between two or more devices that enables a one and/or two-way communication path between the devices and/or portions thereof.
  • an operative coupling may include a wired and/or wireless coupling to enable communication through a transmission between a mobile device and another electronic device such as an airline booking server or an airport server.
  • An operative coupling may also relate to an interaction between program portions and thereby may not describe a physical connection so much as an interaction based coupling.
  • rendering and formatives thereof as utilized herein refer to providing content, such as digital media or a graphical user interface (GUI), such that it may be perceived by at least one user sense, such as a sense of sight and/or a sense of hearing.
  • GUI graphical user interface
  • the present system may render a user interface on a touch display device so that it may be seen and interacted with by a user.
  • rendering may also comprise all the actions required to generate a GUI prior to the display, like e.g. a map image or a GUI comprising a plurality of icons generated on a server side for a browser application on a mobile device.
  • a mobile device provides an enhanced in-flight mode activation through taking into account a take-off time and a validity period for this take-off time.
  • an application program (AP) - or software - may be seen as any tool that functions and is operated by means of a computer, with the purpose of performing one or more functions or tasks for a user or another application program.
  • AP application program
  • a GUI of the AP may be displayed on the mobile device display.
  • FIG. 1 is an illustration of an exemplary mobile device 1 10 used in the present system.
  • the mobile device 1 10 comprises a display device 140, a processor 1 12, a controller 1 13 of the display device, a motion detector or motion sensor module 120, a connection manager 130 and an in-flight mode module 1 15 (in-flight module in short) .
  • GUI graphical user interface
  • An input device (not shown in FIG. 1 ) and display device 140 appear thus as one of the same to the user.
  • Processor 1 13 may control the rendering and/or the display of the GUI on the display device 140 depending on the type of application program (AP) , i.e. resident or web-based. Processor 1 13 may also handle the user entries according to the present method, like the provision of the travelling itinerary or take off time. The user entries to interact with an application program may be provided through interactions with the touch panel 140.
  • AP application program
  • the touch panel 140 can be seen as an input device allowing interactions with a finger of a user or other devices such as a stylus.
  • Touch sensor interface or touch panel 140 may include any suitable circuitry to convert analog signals corresponding to touch input received over its surface into any suitable digital touch input data. Such touch input data can, for example, be used to make selections of portions of the GUI of an AP.
  • the input received from a user's touch is sent to the processor 133.
  • the touch panel 140 is configured to detect and report the (location of the) touches to the processor 133, which can interpret the touches in accordance with the application program and the currently displayed GUI .
  • the processor 133 can initiate a task, e.g. a control of the AP like the activation of the in-flight module or client 1 15 of the present device.
  • the touch panel 140 can be based on sensing technologies including but not limited to capacitive sensing, resistive sensing, surface acoustic wave sensing, pressure sensing, optical sensing, and/or the likes.
  • a number of different components or features, controlled by processor 133, may be provided with the mobile device 100, like a motion detector 120, a connection manager 130 and the in-flight module 1 15 of the present system.
  • Each may comprise a hardware component (for instance a motion sensor, antenna and switch respectively) and a software component to drive the hardware component.
  • One or more motion sensors 120 are available, the readings or outputs of which are input to and used by the processor 1 13 as illustrated here after.
  • the output signal of the motion sensors 120 can include electronic or wireless signals, for example.
  • Such sensors may include an accelerometer, a gyroscope or even a GPS.
  • the monitoring of the motion detector 120 will be controlled through the in-flight module 1 15 as described here after.
  • a connection manager 130 is available also and operatively coupled to the present in-flight module 1 1 5.
  • the connection manager handles the connectivity of the electronic device 100 with the different available communication technologies such as 3G, 4G, Wifi, Bluetooth, Infra Red ...
  • the connection manager 130 is operable to shut down all connectivity or some, depending on its configuration or the requirement of an AP or the user. Under the control of the present in-flight module 1 15, the processor 133 will control the connection manager 1 30 to shut down all connections so as to activate the in- flight mode.
  • the in-flight module 1 15 of the present system may be seen as a client or AP, either available directly with the electronic device 100, with its operating system (OS) or may be downloaded from an application store or service platform the electronic device 100 has access to.
  • OS operating system
  • FIG. 2 presents another exemplary embodiment of the present electronic device 100, illustrated as a mobile device 200, comprising a touch interface 240 and an inflight module 215.
  • Mobile device 200 is operatively coupled to an airline booking server 260 for collecting data about a travelling itinerary, the data comprising for instance a take-off time for a plane and a flight number.
  • the connection may be achieved through either an online booking AP available on the mobile device 200, a web page access or a message, like an SMS or an email.
  • the mobile device 200 is further operatively coupled to an airport server 265 to collect updated take-off time for a place.
  • airport server 265 to collect updated take-off time for a place.
  • the present in-flight module 215 is operable to: - collect and store from the airline booking server 265 travelling itinerary data for a user, as mentioned before.
  • travelling itinerary data may comprise a take-off time ⁇ and a flight number so that the flight can be subsequently tracked with the airport server 265, when a take-off time update is needed.
  • information may be readily available through a booking operation, when the user of mobile device 200 buys a flight ticket (email, SMS, message ... passed on by the airline booking server 265 to the in-flight module 215, e.g. through a booking AP) .
  • the travelling itinerary data may be entered directly by the user, through an input GUI of the in-flight module 215,
  • the monitoring may start at the take-off time, or within X minutes prior to take-off time.
  • X may be seen as a take-off time confidence value or margin, to make sure the motion detector is monitored soon enough before the take-off time known from the itinerary data.
  • the margin may be a predefined margin as explained here after.
  • the monitoring may comprise the activation of the motion detector 120 provided it was not activated prior to the take-off time (when no margin is requested) or Tro-X (with a take-off time margin),
  • Y may be seen as monitoring activity duration, or a (take-off) monitoring time-off, of the in-flight module 215,
  • stopping the monitoring may comprise deactivating the motion detector 120 of FIG. 1 , to preserve the battery resources even further, - request an updated take-off time to the airport server 265.
  • the request may comprise some of the user travelling itinerary data, like the flight number so as to retrieve updated data for this flight.
  • the airport server may actually correspond to air flight scheduling server, a centralized server operatively connected to different airport servers and that collects realtime flight schedules for airports world-wild. Such servers exist today and are accessible through APs available on app stores,
  • the take-off time margin X may be used again. Provided the motion detector was deactivated, the resuming will comprise its activation.
  • FIG. 3 shows an illustrative process flow diagram in accordance with an embodiment of the present system as seen in FIG. 2.
  • An in-flight module or AP is running on the processor of the mobile device 200. Such an AP allows the implementation of the enhanced in-flight mode of the present system.
  • the user of the mobile device 200 will activate the in-flight module or AP, for instance after its download or directly if available with the mobile device as purchased or with its OS.
  • the in-flight module will collect or receive travelling itinerary data for the user.
  • the data may include as already explained a flight number and its take-off time.
  • the information may be provided through different means as mentioned before, provision beyond the scope of the present system.
  • the in-flight module will start the monitoring of the motion detector based on the received take-off time. This means that the monitoring may start at take-off time. Alternatively, a preset take-off time margin may be used to start the monitoring sooner than the take-off time. The start of the monitoring is still based on the received take-off time, but with a predefined margin to avoid any anticipated take-off.
  • the predefined take-off margin may be user defined through a configuration GUI for the in-flight module. Alternatively, it may be based on a confidence value attached to the airline company and/or the airport the user is leaving from. The predefined margin may also be based on historical data for this specific flight. The predefined margin may even be a negative value so as to start the monitoring after the take-off time, when statistical or history data show that the airport is always congested.
  • the take-off time minus the predefined take-off margin, ⁇ - ⁇ as defined earlier, may be seen as an estimated take-off time for starting the monitoring of the motion detector.
  • the present in-flight module will start monitoring the motion detector only after the take-off time is reached (answer Yes to act 320) . Provided the takeoff time is yet to come, the in-flight module will stand by (answer No to act 320) .
  • the in-flight module of the present system will then start a monitoring loop
  • the in-flight module will collect the readings of the motion detector, and used known technologies to get an estimate of the user equipment motion.
  • the take- off as corresponding to a brutal acceleration of the plane, will impart the same characteristic acceleration or more generally motion to the mobile device 200.
  • Such a motion is characterized by a motion signature, based on the chosen motion estimation.
  • Such a motion estimate is disclosed in US201 1 125454.
  • a take-off signature is very different than a taxi signature (slow motion of the plane heading to the take-off track) .
  • Different sensors may be used in the motion estimation model, such as accelerometer, GPS, gyroscope or other motion sensors.
  • the in-flight module will turn off all connectivity. To do so, it will control through the user equipment processor the connectivity manager to shut down all connections. Thus the in-flight mode is activated in act 335 for the mobile device 200.
  • the (take-off monitoring) time-off Y may be defined user configuration. Alternatively, it may be based on historical data, related to average taxi time for the gate to the take-off track. Both the X and Y times may be provided by the airport server or a dedicated server for the in-flight module.
  • the in-flight module will further check in a subsequent act 340 if the time-off Y is lapsed.
  • the monitoring of the motion detector will carry on.
  • the monitoring may be periodic, with e.g. a periodicity set so as to avoid a large demand on the battery resources of the mobile device 200.
  • a monitoring window is defined through the pair (take-off time, monitoring time-off) .
  • the monitoring window limited in time allows significant resource saving over existing solutions.
  • the in-flight module 215 will continue at act 350 with requesting to the airport server 365 an updated take-off time.
  • the request will comprise the flight number or flight identifier so as to retrieve an updated take-off time.
  • Requesting an updated take-off time for the plane allows the in-flight module to define another monitoring window with the pair (updated take-off time, monitoring time-off) . Thus there is no unnecessary continuation of the monitoring from the initial take-off time once the time-off has lapsed.
  • the present in-flight module can resume at step
  • the wait for the new take-off time may be based on the actual (received) take-off time, or based on an estimate take-off time, taking into account the same takeoff time margin X defined earlier.
  • a different take-off time margin may be associated to delay situations, and based on additional history data for such a situation.
  • the take-off time margin X may even be seen as a dynamic data that the airport server 265 can update depending on the traffic and time of the day.
  • the time-off Y may also be updated, depending on congestion at the time of take-off for the airport.
  • Y may be seen as a dynamic value, updated by the airport server 265 based on the real time traffic at the airport and average taxi time at the time it is requested.
  • the time-off Y may thus, in an additional embodiment of the present system, be updated either with the request for the new take-off time, or when the updated take-off time is reached (either actual or estimate as defined before) .
  • the same type of update applies to the take-off time margin X.
  • the inflight module may wait for some additional time and request another updated take-off time. After a number of requests, the in-flight module may prompt the user for further action.
  • the user of user equipment 200 may at any time disable the in-flight module so as to keep a normal functioning of the user equipment.
  • the in-flight module may also be used to monitor the landing motion of the plane, so as to deactivate the in-flight mode after landing.
  • the travelling itinerary may also comprise a landing time. The logic presented in relation to FIG. 3 is restarted in FIG. 4, showing the in-flight mode management regarding the landing of the plane.
  • the user may be requested to configure the in-flight module or AP to handle the landing of the plane as well (using for instance a landing control option) .
  • the in-flight module will receive the landing time along the take-off time as described earlier. The landing time may be requested at a separate moment, for instance after the activation of the landing control, provided the user equipment still has connectivity.
  • the user equipment will monitor if the landing time has been reached (the actual value as explained before, and an estimate using a landing time margin X' , similar to the take-off time margin X) .
  • the in-flight module will start monitoring the motion detector and check whether the motion sensor readings match a landing motion signature. Provided so (answer Yes to act 432), the in-flight mode will be deactivated in a further act 435, resuming connectivity for the user equipment.
  • a landing monitoring time-off Y' may be defined to set the duration of the landing monitoring.
  • Y' is a second present value and the pair (landing time, landing monitoring time off) will define a landing monitoring window for the in-flight module. The monitoring will resume as long as the (landing monitoring) time-off Y' has not lapsed (loop of acts 430 to 440) . Contrary to the embodiment of FIG.
  • Act 450 may correspond to either the end of the monitoring or a prompt to the user to request further instructions. This may be the case if the landing is delayed due to traffic around an airport and the pilot is requested to wait in the air and delay the landing.
  • the update to the landing time may be simultaneous to the take-off time update request of act 350 in FIG. 3, as a delay in take-off will have a similar delay in landing.
  • the landing time is updated (subsequent to a take-off time update)
  • the landing monitoring illustrated in FIG. 4 will be carried out with the updated landing time, instead of the initial value.
  • X' , Y' may be time intervals identical to the take-off counterpart X, Y, or different values based on historical statistic associated to the landing phase of a plane. For instance, Y', the duration or time-off of the landing monitoring may be longer than the time-off Y of the take-off monitoring as the pilot may be regularly asked to delay his landing on this specific airport. Conversely, the duration Y of the take-off monitoring may be longer as the airport is notoriously congested around the take-off tracks.
  • any of the disclosed elements may be comprised of hardware portions (e.g., including discrete and integrated electronic circuitry), software portions (e.g., computer programming), and any combination thereof;
  • f) hardware portions may be comprised of one or both of analog and digital portions
  • any of the disclosed devices or portions thereof may be combined together or separated into further portions unless specifically stated otherwise; h) no specific sequence of acts or steps is intended to be required unless specifically indicated; and
  • the term "plurality of" an element includes two or more of the claimed element, and does not imply any particular range of number of elements; that is, a plurality of elements may be as few as two elements, and may include an immeasurable number of elements.
  • the system or systems described herein may be implemented on any form of computer or computers and the components may be implemented as dedicated applications or in client-server architectures, including a web-based architecture, and can include functional programs, codes, and code segments.
  • Any of the computers may comprise a processor, a memory for storing program data and executing it, a permanent storage such as a disk drive, a communications port for handling communications with external devices, and user interface devices, including a display, keyboard, mouse, etc.
  • these software modules may be stored as program instructions or computer readable codes executable on the processor on a non- transitory computer-readable media such as read-only memory (ROM), random- access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storage devices.
  • the computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
  • This media is readable by the computer, stored in the memory, and executed by the processor.
  • one or more parts of the system may be implemented by a computer processor with associated memory and timing circuitry (not separately shown) that is a functional part of the system and is activated by, and facilitates functionality of other components or parts of the system.
  • the present disclosure may be described in terms of functional block components and various processing steps. Such functional blocks may be realized by any number of hardware and/or software components that perform the specified functions. For example, embodiments of the present disclosure may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, where the elements of various aspects of the present disclosure are implemented using software programming or software elements the aspects of the present disclosure may be implemented with any programming or scripting language such as C, C++, Java, assembler, or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Functional aspects may be implemented in algorithms that execute on one or more processors. Furthermore, aspects of the present disclosure could employ any number of conventional techniques for electronics configuration, signal processing and/or control, data processing and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • User Interface Of Digital Computer (AREA)
  • Traffic Control Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil pour activer automatiquement un mode avion sur un équipement utilisateur à bord d'un avion, l'équipement utilisateur comprenant un détecteur de mouvement. Le procédé comprend la réception au niveau de l'équipement utilisateur d'un horaire de décollage pour l'avion, le début du suivi de la part du détecteur de mouvement en fonction de l'horaire de décollage, et l'arrêt du suivi de la part du détecteur de mouvement lorsque les lectures qu'il effectue ne correspondent pas à la signature de décollage après un temps pré-établi à partir du début du suivi.
PCT/IB2013/002527 2012-09-28 2013-09-27 Procédé et système pour déclencher un mode avion pour un équipement utilisateur WO2014057350A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201261707144P 2012-09-28 2012-09-28
US61/707,144 2012-09-28

Publications (2)

Publication Number Publication Date
WO2014057350A2 true WO2014057350A2 (fr) 2014-04-17
WO2014057350A3 WO2014057350A3 (fr) 2014-07-31

Family

ID=50150726

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2013/002527 WO2014057350A2 (fr) 2012-09-28 2013-09-27 Procédé et système pour déclencher un mode avion pour un équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2014057350A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104536552A (zh) * 2014-12-03 2015-04-22 惠州Tcl移动通信有限公司 一种移动终端飞行模式下开机的方法及系统
CN106254633A (zh) * 2016-07-25 2016-12-21 北京小米移动软件有限公司 手机模式调整方法和装置
WO2019034755A1 (fr) * 2017-08-18 2019-02-21 Ulrich Berger Procédé de liaison d'un terminal radio mobile à une station de base
CN113485423A (zh) * 2021-07-12 2021-10-08 一飞(海南)科技有限公司 机群表演起飞时间更新方法、系统、介质、终端、产品及应用
EP4068735A1 (fr) * 2021-03-29 2022-10-05 Sony Group Corporation Fonctionnement d'un dispositif électronique pendant le transport

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110125454A1 (en) 2009-11-20 2011-05-26 Qualcomm Incorporated In flight detection

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2758807C (fr) * 2009-04-16 2018-09-04 Andrew N. Lemmon Systeme et procede de gestion de dispositifs sans fil a bord d'un aeronef

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110125454A1 (en) 2009-11-20 2011-05-26 Qualcomm Incorporated In flight detection

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104536552A (zh) * 2014-12-03 2015-04-22 惠州Tcl移动通信有限公司 一种移动终端飞行模式下开机的方法及系统
CN106254633A (zh) * 2016-07-25 2016-12-21 北京小米移动软件有限公司 手机模式调整方法和装置
EP3276927A1 (fr) * 2016-07-25 2018-01-31 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et appareil de réglage de modes de combiné
CN106254633B (zh) * 2016-07-25 2019-07-09 北京小米移动软件有限公司 手机模式调整方法和装置
WO2019034755A1 (fr) * 2017-08-18 2019-02-21 Ulrich Berger Procédé de liaison d'un terminal radio mobile à une station de base
EP4068735A1 (fr) * 2021-03-29 2022-10-05 Sony Group Corporation Fonctionnement d'un dispositif électronique pendant le transport
CN113485423A (zh) * 2021-07-12 2021-10-08 一飞(海南)科技有限公司 机群表演起飞时间更新方法、系统、介质、终端、产品及应用
CN113485423B (zh) * 2021-07-12 2022-12-13 一飞(海南)科技有限公司 机群表演起飞时间更新方法、系统、介质、终端、产品及应用

Also Published As

Publication number Publication date
WO2014057350A3 (fr) 2014-07-31

Similar Documents

Publication Publication Date Title
JP6178473B2 (ja) 機内飛行システム、コックピットディスプレイシステム拡張方法およびコンピュータ読み取り可能媒体
TWI521434B (zh) 基於使用者活動起始背景更新
US10721327B2 (en) Dynamic scheduling system for planned service requests
US10979551B2 (en) Method and apparatus for pushing notification, mobile terminal, and graphical user interface
WO2014057350A2 (fr) Procédé et système pour déclencher un mode avion pour un équipement utilisateur
US10218836B2 (en) Method for providing service based on awareness and an electronic device thereof
TWI557555B (zh) 基於使用者活動之行動裝置之動態調整
KR102446325B1 (ko) 어플리케이션 프로그램 운용 방법 및 이를 지원하는 전자 장치
US8762756B1 (en) Statistical approach to power management for electronic devices
US20190311629A1 (en) Generating and managing virtual queues at congested venues
US11424927B2 (en) Continuity of access to avionic data outside of the cockpit of an aircraft
WO2013169794A2 (fr) Mise en concordance de contextes inférés dans un calendrier et propagation d'étiquettes
US20180063670A1 (en) Background management of mobile applications
US11017297B2 (en) System and methods to provide seamless information exchange between certified and uncertified applications
US10692023B2 (en) Personal travel assistance system and method for traveling through a transport hub
KR20170033121A (ko) 서비스 처리 방법 및 이를 구현하는 전자 장치
KR102476103B1 (ko) 공유 컨텐츠 운용 방법 및 이를 지원하는 전자 장치
US10627252B2 (en) Device, system and method for assisting a pilot of an aircraft
KR102598270B1 (ko) 차량 탑승 인식 방법 및 이를 구현한 전자 장치
US9268612B2 (en) Deployment of mobile workloads based on proximity
US20200027378A1 (en) Avionic data management and distribution of displays
WO2020176107A1 (fr) Activation d'un mode de vol connecté
EP3054709B1 (fr) Procédé et appareil permettant d'établir une communication à courte portée
KR20150108224A (ko) 어플리케이션 관리 방법 및 그 장치
US20210160655A1 (en) Device location method

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: 13830216

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 13830216

Country of ref document: EP

Kind code of ref document: A2