EP2763372B1 - Elektronische Vorrichtung, computerlesbares Medium und Datensynchronisationsverfahren - Google Patents

Elektronische Vorrichtung, computerlesbares Medium und Datensynchronisationsverfahren Download PDF

Info

Publication number
EP2763372B1
EP2763372B1 EP14151851.4A EP14151851A EP2763372B1 EP 2763372 B1 EP2763372 B1 EP 2763372B1 EP 14151851 A EP14151851 A EP 14151851A EP 2763372 B1 EP2763372 B1 EP 2763372B1
Authority
EP
European Patent Office
Prior art keywords
data
electronic apparatus
data synchronization
push
application
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP14151851.4A
Other languages
English (en)
French (fr)
Other versions
EP2763372A1 (de
Inventor
Lan-Chin Huang
Hung-Chi Lo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HTC Corp
Original Assignee
HTC Corp
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 HTC Corp filed Critical HTC Corp
Publication of EP2763372A1 publication Critical patent/EP2763372A1/de
Application granted granted Critical
Publication of EP2763372B1 publication Critical patent/EP2763372B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • the application relates to a synchronization method, and in particular, to a data synchronization method
  • the updating data arriving at the data server are not actively transferred to the client unit. Therefore, unless the user manually initiates the data synchronization between the data server and the client unit, the user will not aware of the new arriving data in the data server. In other words, the updating data arriving the data server will not be updated to the client unit until next cycle of the data synchronization. Further, without knowing whether there are new arrived data in the data server, the periodically performed data synchronizations lead to power consumption.
  • US 2011/185202 A1 discloses coordinating a synchronization interval of a periodic communication between a mobile device and application servers through determining ideal polling interval and a tolerance window. It also discloses sending push notifications and an intelligent push management.
  • WO 2011/148370 A1 discloses a system wherein a notification component which is an intermediary between a client and a server periodically polls the server and if a new mail message is detected it sends an alert to the terminal.
  • the terminal checks if a foreground data retrieval program is currently running and if it is not running it lunches it and the foreground data retrieval program connects to the server and retrieves the new message.
  • EP 1 841 130 A1 discloses a method wherein when an application is inactive, notifications are queued and if the application is running in the foreground, the push notifications are processed to update application data.
  • US 2010/077468 A1 discloses a system wherein when an application is launched, a full synchronization is triggered.
  • the present invention defines a method according to claim 1, an electronic apparatus according to claim 8 and a computer readable medium recording program instructions according to claim 11. Further embodiments are set forth in the dependent claims 2-7, 9 and 10.
  • FIG. 1 is a functional block diagram illustrating an electronic apparatus according to an exemplary example of the present application.
  • the electronic apparatus 100 includes a processing unit 110 and a communication unit 120.
  • the electronic apparatus 100 may be, for example, a computer, a tablet, a smartphone, a personal digital assistant (PDA), a padphone, an ultrabook, a laptop or the like.
  • PDA personal digital assistant
  • the processing unit 110 may be, for example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, an ARM-based processor, and the like. Also, the processing unit 110 may optionally be coupled to a memory circuit to store programming codes, device configurations, a codebook, buffered or permanent data, and etc.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Array
  • the functions of the processing unit 110 may be implemented using programmable units such as a micro-processor, a micro-controller, a DSP chips, FPGA, etc.
  • the functions of the processing unit 110 may also be implemented with separate electronic devices or ICs, and the processing unit 110 may also be implemented with either hardware or software.
  • the processing unit 110 may execute a data application for providing the desired functions of the user.
  • the data application may be, for example, an e-mail application, instant messaging software, a calendar application, a task application or the like.
  • the communication unit 120 may be coupled to the processing unit 110 and configured for processing the radio frequency (RF) signals of wireless communication technologies.
  • the wireless communication technologies may at least include, for example, global system for mobile (GSM), third generation project partnership long term evolution (3GPP LTE), code division multiple access (CDMA), wideband CDMA (WCDMA), high speed packet access (HSPA), and world interoperability for microwave access (WiMAX), etc.
  • the communication unit 120 may be configured for processing the RF signals of wireless local area network communication technologies, e.g., wireless local area network (WLAN).
  • WLAN wireless local area network
  • the communication unit 120 may be configured for wirelessly accessing the Internet through a wireless local area network or other kinds of wireless network.
  • the wireless communication unit 120 may use various wireless local area network technologies such as wireless fidelity (Wi-Fi) standard or IEEE 802.11 standard.
  • the communication unit 120 may receive RF signals of the aforementioned wireless communication technologies through an antenna (not shown).
  • the processing unit 110 may execute a data application for providing the desired functions of the user.
  • the data application may be, for example, an e-mail application, instant messaging software, a calendar application, a task application or the like.
  • the processing unit 110 may control the communication unit 120 to communicate with a data server (such as a mail server) related to the data application and perform a data synchronization with the data server to retrieve data from the data server to update the information of the data application.
  • a data server such as a mail server
  • the communication unit 120 may determine the timing of the data synchronization according to some principles. For example, the communication unit 120 may periodically perform the data synchronization with the data server. By periodically synchronizing with the data server, the overhead (such as and power consumption) of the electronic apparatus 100 could be saved. However, the user may not be able to instantly obtain the latest information from time to time.
  • the communication unit 120 may also perform the data synchronization according to the push-data mechanism. Specifically, when the communication unit 120 performs the data synchronization according to the push-data mechanism, the communication unit 120 may firstly establish a connection with the data server by sending a request (e.g., a Hypertext Transfer Protocol (HTTP) request) to the data server. Next, when there is an updating data, which hasn't been received by the communication unit 120, existing on the data server, the data server may send a push-data notification to the communication unit 120 through the connection. Please notice that the updating data may be, but no limited to, a data being added, deleted, modified or updated.
  • HTTP Hypertext Transfer Protocol
  • the communication unit 120 may accordingly perform the data synchronization to synchronize with the data server to receive the updating data related to the push-data notification.
  • the communication unit 120 may disconnect the connection after receiving the push-data notification through the connection.
  • the data server would instantly notify the electronic apparatus 100 by sending the push-data notification to the communication unit 120, and the communication unit 120 would correspondingly perform the data synchronization with the data server.
  • the communication unit 120 may send the request to the data server to re-establish the connection. Therefore, the push-data mechanism would make the information exchange between the electronic apparatus 100 and the data server more real-time. However, the push-data mechanism may increase the overhead of the electronic apparatus 100 for constantly maintaining the connection.
  • FIG. 2 is a flow chart illustrating a data synchronization method according to an exemplary example of the present application.
  • the method proposed in the present example could be adapted to the electronic apparatus 100 of FIG. 1 , but the application is not limited thereto.
  • the processing unit 110 performs the data synchronization of the data application according to a specific synchronization mode.
  • the specific synchronization mode can be regarded as the default data synchronization configuration of the data application.
  • the specific synchronization mode may represent that the processing unit 110 periodically performs the data synchronization of the data application.
  • the specific synchronization mode may represent that the processing unit 110 performs the data synchronization of the data application in response to a user input. That is, the user could manually control the electronic apparatus 100 to perform the data synchronization by, for example, pushing particular buttons or inputting specific commands, but the application is not limited thereto.
  • step S210 the processing unit 110 may control the communication unit 120 to instantly perform the data synchronization when firstly launching the data application.
  • the data application would be instantly updated when being executed for the first time.
  • the communication unit 120 would synchronize with the mail server to retrieve the mails that have not been received by the electronic apparatus 100.
  • step S220 the processing unit 110 may control the communication unit 120 to perform the data synchronization according to the push-data notification from the data server.
  • the data synchronization of the data application may be switched to be performed according to the push-data mechanism.
  • the details of the push-data mechanism could be referred to the previous discussions, which would not be repeated herein.
  • the information exchange between the electronic apparatus 100 and the data server would be real-time, such that the user may instantly receive the latest data of the data application.
  • the data synchronization performed according to the push-data notification from the data server is performed for only one time.
  • the processing unit 110 can switch from performing the data synchronization according to the push-data notification from the data server to perform the data synchronization according to the specific synchronization mode, but the present application is not limited thereto.
  • step S230 the processing unit 110 may determine whether the data application is switched to be executed in a background of the user interface of the electronic apparatus 100. If no, the processing unit 110 may perform step S250 to determine whether the electronic apparatus 100 is entering into a power saving mode while the data application is still running in foreground.
  • the power saving mode could be generalized to a regular sleep mode, a hibernation mode, a screen-off mode (e.g. due to the display-on timeout reaches a predetermined time period) or other similar modes, which is not limited thereto. If yes, the processing unit 110 may perform step S260 to switch to perform the data synchronization according to the specific synchronization mode.
  • step S230 the processing unit 110 may switch to perform the data synchronization according to the push-data notification from the data server, and subsequently return step S230.
  • step S240 the processing unit 110 may switch to perform the data synchronization according to the specific synchronization mode.
  • the processing unit 110 may periodically perform the data synchronization and/or perform the data synchronization in response to the user input (as default data synchronization configuration prior to S210), instead of performing the data synchronization according to the push-data mechanism. From another point of view, as long as the data application is not executed in the foreground, the data synchronization would be switched to be periodically performed or to be performed in response to the user input, which saves the overhead of the electronic apparatus 100.
  • FIG. 3 is a flow chart illustrating a data synchronization method according to the example of FIG. 2 .
  • the method proposed in the present example could also be adapted to the electronic apparatus 100 of FIG. 1 , but the application is not limited thereto.
  • the processing unit 110 may further perform step S310.
  • step S310 the processing unit 110 may determine whether a data application is switched to be executed in the foreground of the user interface of the electronic apparatus 100. If no, the processing unit 110 may keep performing step S310. If yes, the processing unit 110 may perform step S320. In step S320, the processing unit 110 may switch to perform the data synchronization according to the push-data notification from the data server.
  • the data synchronization would be switched to be performed according to the push-data mechanism for only one time of data synchronization. Once the one time of data synchronization is finished, the data synchronization could be switched back to be performed according to the specific synchronization mode.
  • step S320 the processing unit 110 may subsequently perform steps S330 and S340.
  • step S330 when the electronic apparatus 100 is entering into the power saving mode, the processing unit 110 may switch to perform the data synchronization according to the specific synchronization mode. Therefore, the power consumption of the electronic apparatus 100 could be further reduced while staying in the power saving mode.
  • step S340 when the electronic apparatus 100 exits the power saving mode, the processing unit 110 may switch to perform the data synchronization according to the push-data notification from the data server, which makes the information exchange between the electronic apparatus and the data server more real-time.
  • FIG. 4 is a flow chart illustrating a data synchronization method according to the example of FIG. 3 .
  • the method proposed in the present example could also be adapted to the electronic apparatus 100 of FIG. 1 , but the application is not limited thereto.
  • the processing unit 110 may further perform step S410.
  • step S410 the processing unit 110 may determine whether a data application is switched to be executed in the foreground of the user interface of the electronic apparatus 100. If no, the processing unit 110 may keep performing step S410. If yes, the processing unit 110 may perform step S420.
  • step S420 the processing unit 110 may switch from performing the data synchronization according to the specific synchronization mode to perform the data synchronization according to the push-data notification from the data server.
  • the data synchronization would be switched to be performed according to the push-data mechanism for only one time of data synchronization. Once the one time of data synchronization is finished, the data synchronization could be switched back to be performed according to the specific synchronization mode.
  • the processing unit 110 may subsequently perform steps S430 and S440.
  • step S430 when the electronic apparatus 100 is entering into the power saving mode, the processing unit 110 may switch to perform the data synchronization according to the specific synchronization mode. Therefore, the power consumption of the electronic apparatus 100 could be further reduced while staying in the power saving mode.
  • step S440 when the electronic apparatus 100 exit from the power saving mode, the processing unit 110 may switch to perform the data synchronization according to the push-data notification from the data server, which makes the information exchange between the electronic apparatus and the data server more real-time.
  • the application provides a computer-readable medium, which records a computer program to be loaded into an electronic apparatus to execute the steps of the aforementioned data synchronization method.
  • the computer program is composed of a plurality of program instructions (for example, an organization chart establishing program instruction, a table approving program instruction, a setting program instruction, and a deployment program instruction, etc), and these program instructions are loaded into the electronic apparatus and executed by the same to accomplish various steps of the data synchronization method.
  • the examples of the present application provide a data synchronization method and an electronic apparatus using the same method.
  • the data synchronization of the data application could be properly adjusted according to the execution status of the data application.
  • the data synchronization would be set to be performed according to the specific synchronization mode, which saves the overhead of the electronic apparatus.
  • the data synchronization would be set to be performed according to the push-data mechanism, which makes the information exchange between the electronic apparatus and the data server more real-time.
  • the advantages of the principles related to the data synchronization between the electronic apparatus and the data server could be both achieved by the proposed method of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Claims (11)

  1. Ein Datensynchronisationsverfahren, das an eine elektronische Vorrichtung (100) angepasst ist, die mindestens eine Verarbeitungseinheit (110) und eine Kommunikationseinheit (120) beinhaltet, wobei die Verarbeitungseinheit (110) die Kommunikationseinheit (120) steuert, um mit einem Datenserver zu kommunizieren und Datensynchronisation mit dem Datenserver durchzuführen, wobei das Verfahren Folgendes beinhaltet:
    Bestimmen, durch die Verarbeitungseinheit (110), ob eine Datenanwendung umgestellt ist, um in einem Vordergrund einer Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden, wobei eine Datensynchronisation der Datenanwendung mit einem Datenserver gemäß einer Standard-Datensynchronisationskonfiguration durchgeführt wird, wobei die Standard-Datensynchronisationskonfiguration eine periodische oder manuelle Datensynchronisation ist, statt auf einer Push-Daten-Benachrichtigung basiert; und
    falls ja, Umstellen, durch die Verarbeitungseinheit (110), auf das Durchführen der Datensynchronisation gemäß einer Push-Daten-Benachrichtigung von dem Datenserver, wobei sich die Push-Daten-Benachrichtigung auf Aktualisierungsdaten bezieht,
    wobei das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver Folgendes beinhaltet:
    nach dem Umstellen der Datenanwendung von dem Ausführen im Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung auf das Ausführen im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung,
    Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver lediglich einmal, während die Datenanwendung im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung ausgeführt wird; und
    dann Umstellen von dem Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration, während die Datenanwendung im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung ausgeführt wird.
  2. Verfahren gemäß Anspruch 1, wobei nach dem Schritt des Umstellens auf das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver, ferner beinhaltend:
    Bestimmen, ob die Datenanwendung umgestellt ist, um in einem Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden; und
    falls ja, Umstellen auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration.
  3. Verfahren gemäß Anspruch 2, wobei nach dem Schritt des Bestimmens, ob die Datenanwendung umgestellt ist, um im Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden, ferner beinhaltend:
    falls die Datenanwendung nicht umgestellt ist, um im Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden, Bestimmen, ob die elektronische Vorrichtung (100) in einen Stromsparmodus übergeht; und
    falls ja, Umstellen auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration.
  4. Verfahren gemäß Anspruch 3, wobei, wenn die elektronische Vorrichtung (100) den Stromsparmodus verlässt, Umstellen auf das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver.
  5. Verfahren gemäß einem der vorhergehenden Ansprüche, wobei das Verfahren ferner Folgendes beinhaltet:
    sofortiges Durchführen der Datensynchronisation beim ersten Starten der Datenanwendung; und
    Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver.
  6. Verfahren gemäß einem der vorhergehenden Ansprüche, wobei nach dem Schritt des Umstellens auf das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver, ferner beinhaltend:
    wenn die elektronische Vorrichtung in einen Stromsparmodus übergeht, Umstellen auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration.
  7. Verfahren gemäß Anspruch 6, wobei, wenn die elektronische Vorrichtung den Stromsparmodus verlässt, Umstellen auf das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver.
  8. Eine elektronische Vorrichtung (100), die Folgendes beinhaltet:
    eine eine Datenanwendung ausführende Verarbeitungseinheit (110); und
    eine mit der Verarbeitungseinheit (110) gekoppelte Kommunikationseinheit (120), wobei die Verarbeitungseinheit (110) die Kommunikationseinheit (120) steuert, um mit dem Datenserver zu kommunizieren und Datensynchronisation mit dem Datenserver durchzuführen,
    wobei die Verarbeitungseinheit (110) bestimmt, ob die Datenanwendung umgestellt ist, um in einem Vordergrund einer Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden, wobei eine Datensynchronisation der Datenanwendung mit dem Datenserver gemäß einer Standard-Datensynchronisationskonfiguration durchgeführt wird, wobei die Standard-Datensynchronisationskonfiguration eine periodische oder manuelle Datensynchronisation ist, statt auf einer Push-Daten-Benachrichtigung basiert; und
    falls ja, stellt die Verarbeitungseinheit (110) auf das Durchführen der Datensynchronisation gemäß einer Push-Daten-Benachrichtigung von dem Datenserver um, wobei sich die Push-Daten-Benachrichtigung auf Aktualisierungsdaten bezieht;
    wobei das Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver Folgendes beinhaltet:
    nach dem Umstellen der Datenanwendung von dem Ausführen im Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung auf das Ausführen im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung,
    Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver lediglich einmal, während die Datenanwendung im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung ausgeführt wird; und
    dann Umstellen von dem Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration, während die Datenanwendung im Vordergrund der Benutzerschnittstelle der elektronischen Vorrichtung ausgeführt wird.
  9. Elektronische Vorrichtung gemäß Anspruch 10, wobei die Verarbeitungseinheit (110) ferner bestimmt, ob die Datenanwendung umgestellt ist, um in einem Hintergrund der Benutzerschnittstelle der elektronischen Vorrichtung (100) ausgeführt zu werden; und falls ja, stellt die Verarbeitungseinheit (100) auf das Durchführen der Datensynchronisation gemäß der Standard-Datensynchronisationskonfiguration um.
  10. Elektronische Vorrichtung (100) gemäß Anspruch 10 oder 11, wobei die Verarbeitungseinheit (110) ferner für Folgendes konfiguriert ist:
    sofortiges Durchführen der Datensynchronisation beim ersten Starten der Datenanwendung; und
    Durchführen der Datensynchronisation gemäß der Push-Daten-Benachrichtigung von dem Datenserver.
  11. Ein computerlesbares Medium, das Programmanweisungen aufzeichnet, die zum Durchführen aller Schritte gemäß Anspruch 1 angepasst sind, wenn sie von einer Verarbeitungseinheit durchgeführt werden.
EP14151851.4A 2013-02-01 2014-01-21 Elektronische Vorrichtung, computerlesbares Medium und Datensynchronisationsverfahren Active EP2763372B1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US201361759403P 2013-02-01 2013-02-01

Publications (2)

Publication Number Publication Date
EP2763372A1 EP2763372A1 (de) 2014-08-06
EP2763372B1 true EP2763372B1 (de) 2017-05-10

Family

ID=49958336

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14151851.4A Active EP2763372B1 (de) 2013-02-01 2014-01-21 Elektronische Vorrichtung, computerlesbares Medium und Datensynchronisationsverfahren

Country Status (4)

Country Link
US (1) US9646070B2 (de)
EP (1) EP2763372B1 (de)
CN (1) CN103973766B (de)
TW (1) TWI509514B (de)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102208620B1 (ko) * 2014-03-12 2021-01-28 삼성전자 주식회사 휴대형 전자장치의 절전 방법 및 그에 관한 장치
MX2017014026A (es) * 2015-05-07 2018-03-01 Kodiak Networks Inc Sistema y metodo para la sincronizacion de datos.
CN104994121A (zh) * 2015-05-11 2015-10-21 努比亚技术有限公司 一种实现通知消息推送的方法及装置
US10445165B2 (en) * 2017-08-21 2019-10-15 Hewlett-Packard Development Company, L.P. Inactive application restarting
CN115695445A (zh) * 2021-07-31 2023-02-03 华为技术有限公司 一种数据同步方法、终端和系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7460021B1 (en) * 2005-11-16 2008-12-02 The Weather Channel, Inc. Interactive wallpaper weather map
DE602006016401D1 (de) * 2006-03-29 2010-10-07 Research In Motion Ltd Vorrichtung und zugeordnetes Verfahren zur Erleichterung der Hintergrundverarbeitung von "Push"-Inhalt
US7627683B2 (en) * 2006-12-27 2009-12-01 At&T Mobility Ii Llc System and method for dynamically refreshing an active home screen
US20090144359A1 (en) * 2007-12-04 2009-06-04 Telefonaktiebolaget L M Ericsson (Publ) Mobile access to internet-based application with reduced polling
US9535967B2 (en) * 2008-09-10 2017-01-03 Salesforce.Com, Inc. Method and system for providing efficient and complex database functionality to a mobile device
EP2476239B1 (de) * 2009-09-09 2018-11-07 Telefonaktiebolaget LM Ericsson (publ) Adaption von inhaltsübertragung in mobilfunknetzen
US8904206B2 (en) 2010-01-26 2014-12-02 Motorola Mobility Llc Mobile computing device and method for maintaining application continuity
US20110252422A1 (en) * 2010-04-07 2011-10-13 Apple Inc. Opportunistic Multitasking
US20130067013A1 (en) 2010-05-25 2013-03-14 Emoze Ltd Message synchronization
US9218206B2 (en) 2011-06-20 2015-12-22 Microsoft Technology Licensing, Llc Memory management model and interface for new applications
US8897762B2 (en) * 2012-02-28 2014-11-25 Qualcomm Incorporated Optimizing signaling load overhead and battery consumption for background applications
US9148765B2 (en) * 2012-11-27 2015-09-29 Alcatel Lucent Push service without persistent TCP connection in a mobile network

Also Published As

Publication number Publication date
CN103973766B (zh) 2018-03-13
TW201432569A (zh) 2014-08-16
CN103973766A (zh) 2014-08-06
US9646070B2 (en) 2017-05-09
EP2763372A1 (de) 2014-08-06
TWI509514B (zh) 2015-11-21
US20140222757A1 (en) 2014-08-07

Similar Documents

Publication Publication Date Title
EP2763372B1 (de) Elektronische Vorrichtung, computerlesbares Medium und Datensynchronisationsverfahren
JP6168508B2 (ja) 省電力モードの最適化およびその関連手順
EP2966913B1 (de) Aufwecksteuerungsverfahren, vorrichtung und endgerät
US9451587B2 (en) Paging for longer paging cycles
EP2992713B1 (de) Durch endgerät initiierte strommodusumschaltung
US9999095B2 (en) Method and apparatus for setting up/releasing radio resource control connection between evolved node B and user equipment in communication system
US9781676B2 (en) System and method for reducing power consumption based on data activity sensitive timers
US9955422B2 (en) User equipment power optimization
WO2018107498A1 (zh) 用于非连续接收的方法和装置
US20200178206A1 (en) Ran area id configuration
EP2666313A1 (de) Adaptive peer-erkennung auf basis von nicht-peer-erkennungsübertragungen und einer wifi-vorrichtungsdichte
EP3337222B1 (de) Endgerätaufweckverfahren und -vorrichtung
JP2020535675A (ja) 通信方法、端末デバイス及びネットワークデバイス
JP6668484B2 (ja) システム情報送信方法、システム情報更新方法、及びデバイス
US9185514B1 (en) Orchestration of application updates over a wireless communication network
TW201538010A (zh) 用於管理網路連線的行動裝置和方法以及存儲媒體
CN107820277B (zh) 用于无线网络的父节点装置、终端装置及其数据传输方法
EP2111018A1 (de) Verfahren zum Sparen von Energie- und Radioressourcen in drahtlosen Kommunikationsgeräten
WO2011093790A1 (en) A method, device, and computer program of scheduling transferring of application messages in a mobile device
CN111314272B (zh) 一种任务处理方法及装置
WO2020192936A1 (en) Apparatus, method and computer program for performing radio access notification area update
CN111543030B (zh) 一种信息指示方法及装置、计算机存储介质
JP4895232B2 (ja) 無線通信方法および無線通信装置
JP5519615B2 (ja) 無線通信方法および無線通信装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140121

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HTC CORPORATION

17Q First examination report despatched

Effective date: 20150605

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20170127

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 893395

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170515

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014009541

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 893395

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170510

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170811

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170810

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170910

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170810

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014009541

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20180213

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180131

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180131

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20140121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170510

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20170510

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602014009541

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602014009541

Country of ref document: DE

Representative=s name: WAGNER & GEYER PARTNERSCHAFT MBB PATENT- UND R, DE

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230602

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231207

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20231215

Year of fee payment: 11

Ref country code: FR

Payment date: 20231212

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231205

Year of fee payment: 11