WO2007039496A1 - Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage - Google Patents

Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage Download PDF

Info

Publication number
WO2007039496A1
WO2007039496A1 PCT/EP2006/066655 EP2006066655W WO2007039496A1 WO 2007039496 A1 WO2007039496 A1 WO 2007039496A1 EP 2006066655 W EP2006066655 W EP 2006066655W WO 2007039496 A1 WO2007039496 A1 WO 2007039496A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
request
setting
specific setting
access
Prior art date
Application number
PCT/EP2006/066655
Other languages
English (en)
Inventor
Tobias Lindquist
Peter Van Sebille
Original Assignee
Sony Ericsson Mobile Communications Ab
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 Sony Ericsson Mobile Communications Ab filed Critical Sony Ericsson Mobile Communications Ab
Priority to EP06806802.2A priority Critical patent/EP1941356B1/fr
Publication of WO2007039496A1 publication Critical patent/WO2007039496A1/fr

Links

Classifications

    • 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/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality

Definitions

  • the present invention relates to an electronic apparatus that includes a server device and at least one client device.
  • the server device is adapted to manage access to data for a specific setting, and is responsive to the client device.
  • the present invention also relates to methods for managing access to data for settings of the electronic device.
  • settings may be provided, for which data is required.
  • a plurality of applications in the electronic apparatus may require access to the data for the settings.
  • an image may in a first application e.g. be data for a wallpaper setting of a display.
  • the same image may be data for a setting of a phonebook, such as a picture setting of a phonebook entry.
  • the image may be stored at a single location, such as a flash memory.
  • Each of the first and second applications need to manage and keep track of the storage location of the image to be able to access it.
  • the electronic apparatus may include a plurality of storage locations, e.g.
  • SIM Subscriber Identity Module
  • Smart card Smart card
  • cache memory in addition to the flash memory.
  • Settings may be stored at each of the storage locations. For each of the storage locations, different rules and mechanisms may apply for accessing the stored data. Furthermore, each storage location may have multiple rules and mechanisms for storing data and for accessing stored data. Thus, each application that needs access to data stored at a single and/or different storage locations may need to manage multiple rules and mechanisms for managing storage of data. The more applications, storage locations and/or different rules and access mechanisms per storage locations that are implemented, the more complex the management of the data for settings will be.
  • the electronic apparatus may include a communication platform, which implements all functions for communicating with the network.
  • the functions of the communication platform may be invisible to a user of the electronic apparatus.
  • the electronic apparatus may also include an operational platform for implementing applications visible to the user.
  • Each of the platforms may be connected to one or several storage locations, wherein data for settings may be stored.
  • the communication platform and the operational platform may be interconnected by e.g. a data channel and a control channel. Communication between the operational platform and the communication platform may be performed according to predetermined rules, provided by e.g. protocols, which may be relatively complex.
  • Different communication and operational platforms may store settings on different storage locations. For example, in one system, vibrator settings are stored in a memory connected to the communication platform, but in another in a memory connected to the operational platform. Thus, when a manufacturer is changing e.g. a communication platform, the storage location of settings may be changed. Consequently, it may be necessary to update applications on the operational platform to make sure that they are referring to the correct storage location and apply the correct rules and mechanisms for managing the settings data.
  • One or several applications implemented in the operational platform may require access to data for a setting stored in a storage location connected to the communication platform.
  • one or several applications implemented in the communication platform may require access to data for a setting stored in a storage location connected to the operational platform.
  • each application manage the address to the storage location, but also the predetermined rules, according to which the application may communicate with the platform, to which the storage location is connected.
  • the management of access to data for a setting may be relatively cumbersome.
  • storage requirements of each application may become relatively large. This is a disadvantage, especially in a portable communication apparatus, wherein the storage capacity may be relatively limited.
  • an electronic apparatus includes a server device and at least one client device.
  • the client device is adapted to interact with the server device to access data for a setting.
  • the data is stored in a memory device.
  • the server device includes at least one interface module that is adapted to manage access to data for a specific setting.
  • the interface module may be adapted to register the physical storage location of data for said specific setting.
  • the interface module may be adapted to handle at least one of a request to set data of a setting, get data of a setting, change data of a setting, and handle subscription to at least one change notification.
  • the interface module may be provided by a software plug-in.
  • the server device may be responsive to at least one API received from a client device for accessing data for the specific setting.
  • the server device may be responsive to at least one client device implemented in an operational platform and at least one client device implemented in a communication platform.
  • the interface module or the server device may be adapted to register a change of data for the specific setting, and notify any client device having a subscription for a notification of the changed setting.
  • a first memory device may be connected to the operational platform and a second memory device may be connected to the communication platform.
  • the electronic apparatus may be a portable or handheld mobile radio communication equipment, a mobile radio terminal, a mobile telephone, a pager, a communicator, an electronic organizer, a smartphone or a computer.
  • a method for accessing data for a setting of an electronic device includes receiving in a server device a request for access to data for a specific setting. The request is issued by a client device. The specific setting for which data is requested is identified based on the request. The request is forwarded to an interface module that is responsible for managing access to data for said specific setting.
  • Access to the data may be managed in accordance with the request type of the request.
  • the step of managing may include determining a main setting the received request pertains to, and forward data for any sub-setting of the main setting.
  • the step of managing may include determining whether the request is a set request and, when the request is a set request, accessing the data pertaining to the specific setting by storing data received in the request message and registering the storage location thereof.
  • the step of managing may include determining whether the request is a get request and, when the request is a get request, accessing the data pertaining to the specific setting by retrieving said data from a memory device and forwarding said data to the client device from which the request message was received.
  • the step of managing may include determining whether the request is a change notification request and, when the request is a change notification request, accessing the data pertaining to the specific setting by registering that data pertaining to the specific setting is changed, and issuing a change notification including said data to any client device subscribing to a change notification pertaining to the specific setting.
  • a computer program product includes computer program code means for executing the method for accessing data for a setting of an electronic device, when said computer program code means are run by an electronic device having computer capabilities.
  • a computer readable medium having stored thereon a computer program product includes computer program code means for executing the method for accessing data for a setting of an electronic device, when said computer program code means are run by an electronic device having computer capabilities.
  • a computer program product is configured to access data for a setting of an electronic device.
  • the computer program product includes a computer readable storage medium having computer readable program code embodied therein.
  • the computer readable program code includes computer readable program code that is configured to receive at a server device a request for access to data for a specific setting of the electronic device, said request being issued by a client device. It also includes computer readable program code that is configured to identify based on the request the specific setting for which data is requested, and computer readable program code that is configured to forward the request to an interface module that is responsible for managing access to data for said specific setting.
  • the computer program product further includes computer readable program code that is configured to manage access to the data in accordance with a type the request, and computer readable program code that is configured to manage access to the data in accordance with a type the request.
  • the computer readable program code that is configured to manage access to the data in accordance with a type the request may include computer readable program code that is configured to determine a main setting to which the received request pertains and to forward data for any sub-setting of the main setting.
  • the computer readable program code that is configured to manage access to the data in accordance with a type the request may include computer readable program code that is configured to determine whether the request is a set request and, when the request is a set request, to access the data pertaining to the specific setting by storing data received in the request message and registering the storage location thereof.
  • the computer readable program code that is configured to manage access to the data in accordance with a type the request may include computer readable program code that is configured to determine whether the request is a get request and, when the request is a get request, to access the data pertaining to the specific setting by retrieving said data from a memory device and forwarding said data to the client device from which the request message was received.
  • the computer readable program code that is configured to manage access to the data in accordance with a type the request may include computer readable program code that is configured to determine whether the request is a change notification request and, when the request is a change notification request, to access the data pertaining to the specific setting by registering that data pertaining to the specific setting is changed, and issuing a change notification including said data to any client device subscribing to a change notification pertaining to the specific setting.
  • Fig. 1 is schematic view of an electronic apparatus connected to a network according to some embodiments of the present invention.
  • Fig. 2 is a block diagram of one embodiment of the electronic apparatus according to some embodiments of the present invention.
  • Fig. 3 is a flow-chart of one embodiment of the method for accessing data for at least one setting according to some embodiments of the present invention.
  • Computer program instructions may be provided to a processor circuit of a general purpose computer, special purpose computer, ASIC, and/or other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or operational block or blocks.
  • the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
  • Fig. 1 illustrates an electronic apparatus 1.
  • the electronic apparatus 1 may comprise a man-machine interface, such as a keypad 2, a display 3, a joystick 4, a microphone 5 and a loudspeaker 6, though which a user may interact with the electronic apparatus 1.
  • a man-machine interface such as a keypad 2, a display 3, a joystick 4, a microphone 5 and a loudspeaker 6, though which a user may interact with the electronic apparatus 1.
  • the electronic apparatus 1 may be a communication apparatus. Thus, the electronic apparatus may be connected to a network 10.
  • a database 11 may be connected to the network 10 and may be accessible through the network 10. In the database 11, data for settings for the electronic apparatus 1 may be stored.
  • Settings as used in this description may be any setting that may be altered manually by a user or automatically by the electronic device 1 itself, possibly in response to received information from a remote device. Settings may also be altered by a client device or application, by requests issued on a system bus, or as result of network events, e.g. information has been received from a network. The data may be changed from a first value or content to a second value or content.
  • the electronic apparatus 1 may comprise various applications for carrying out functions within the electronic apparatus 1.
  • the applications may be provided within an operational platform.
  • the applications may be provided within a communication platform.
  • the operational platform may comprise systems software run by an application processor, such as a CPU (Central Processing Unit), which may also be referred to as the ACPU (Application CPU).
  • the communication platform may comprise both hardware and software for carrying out e.g. communication with the network 2.
  • the communication platform may comprise a CPU, which may be referred to as a CCPU, (Communication CPU), for providing various applications.
  • the ACPU and the CCPU may run different operational systems.
  • the communication platform and the operational platform may interact to exchange information.
  • Fig. 2 illustrates a server device 20 of the electronic apparatus 1.
  • the server device 20 may be implemented by software run by a processor, such as the application processor or the communication processor.
  • the server device 20 may be operatively connected or be adapted to interact with at least one client device 21a-21c.
  • Each client device 21a-21c may implement a certain application.
  • Each client device 21a-21c may be implemented with software run by one or several processors.
  • Each client device 21a-21c may be adapted to interact with the server device 20 to access data for settings stored in at least one memory device 22a-22c.
  • the server device comprises at least one interface module 23a-23c.
  • Each interface module 23a-23c is adapted to manage access to data for a specific setting. The data for a specific setting may be required by more than one client device 21a- 21c.
  • each interface module 23a-23c may manage access to data for a specific setting in response to or in accordance with a request received from a client device 21a-21c requiring access to said data.
  • Each client device 21a-21c does not have to store or have knowledge of e.g. the storage location of the data for a setting, as the server device 20 manages access to the data for the setting.
  • the data for the specific setting may be stored at a single storage location.
  • Centralized management of access to data for a specific setting is an advantage, as the complexity of the system will be reduced when the client devices 21a-21c do not have to have any information for managing the data for the settings.
  • the storage requirements for managing data for settings will be reduced with centralized management. Furthermore, it will only be necessary to store data for a specific setting at a single storage location.
  • the electronic apparatus 1 may comprise a variety of memory devices 22a- 22c for storing data of settings.
  • the data for the specific setting may be stored at a single memory device 22a-22c.
  • data for different settings may be stored in different memory devices 22a-22c.
  • Memory device 22a may be a memory of a SIM (Subscriber Identity Module).
  • Memory device 22b may be a flash memory.
  • Memory device 22c may be a memory card.
  • the electronic apparatus 1 may comprise other types of memory devices, such as a cache memory, a ROM (Read Only Memory), a RAM (Random Access Memory), a memory card, a smart card, and/or a hard disk.
  • Data for a setting may also be stored at the database 11 connected to the network 2.
  • data for a setting may be stored in a memory device of a device, which is external to the electronic apparatus 1.
  • the external device may e.g. be accessible through an accessory connector or a short-range radio link, such as a Bluetooth® link.
  • Each interface module 23a-23c may be implemented with a software component or program, such as a plug-in module.
  • the interface module may be adapted to interact with other software programs to provide a certain function.
  • Each plug-in may be adapted to register the physical storage location of data for a specific setting.
  • each interface module 23a-23c may be adapted to keep track of the storage location for the data of the specific setting. The storage location may be altered, which the interface module 23a-23c thus may keep track of. This is an advantage, as the storage location of data for a specific setting may move without the need to update any code in the client device 21a-21c.
  • Each interface module 23a-23c may be adapted to manage different storage mechanisms and/or rules for a single storage location. For example, on a certain storage location, such as a flash memory, a database with settings and a text file with settings may be stored. The database and the text file may require different rules and methods to access the settings, which the single interface module 23a-23c may manage.
  • a single interface module 23a-23c may implement a single storage mechanism of a certain storage location.
  • a first interface module may be provided for managing settings accessible through the database of the certain storage location.
  • a second interface module may be provided for managing settings accessible through the text file of the certain storage location.
  • Interface module 23 a may for example be adapted to manage setting A.
  • Interface module 23b may be adapted to manage setting B.
  • Interface module 23 c may be adapted to manage setting C.
  • Each specific setting may be owned and managed by a single interface module 23 a. This is an advantage, as it may ensure that data for a specific setting is uniform without the need of synchronization of data. Consequently, the reliability of the electronic apparatus 1 increases and the data processing requirements is reduced.
  • the interaction and communication between the client modules 21a-21c and the interface modules 23a-23c may be provided by program interfaces, which comprise standardized software instructions. Said interaction may be provided by one or several APIs (Application Programming Interface).
  • a first program interface may provide a GET[Setting X, ClientID] request or request type. [Setting X, ClientID] identifies the specific setting for which data is requested, Setting X in this case, and ClientID is an identifier of the requesting client device 21a-21c, to which the response should be transmitted.
  • a GET request may be issued by a client device 21a-21c, to gain access to data of for the specific setting, and received and processed by the server device 20.
  • a second program interface may provide a Set[Setting X, Data] request or request type. [Setting X, Data] identifies the specific setting for which data is requested, Setting X in this case, and Data is the data which should be stored for Setting X.
  • a Set request may be issued by a client device 21a-21c, to store and/or alter data for the specific setting, and received by the server device 20.
  • a third program interface may provide a NotifyOnChange[Setting X,
  • ClientID request or request typetype.
  • [Setting X] identifies the specific setting for which a notification of any change is requested, setting X in this case, and ClientID is an identifier for identifying the requester to which the change notification should be transmitted.
  • the NotifyOnChange request may be a subscription for a change notification indicating that a change of the data pertaining to Setting X has occurred.
  • a NotifyOnChange request may be issued by a client device 21a-21c, to subscribe to a notification when a setting has been changed, and may be received by the server device 20.
  • any new data for the specific setting may be included.
  • the Set, Get, and NotifyOnChange requests are only given as examples. The invention is not limited to these examples. Any request to gain access to data for a setting may be managed by the server device 20.
  • the server device 20 may be adapted to retrieve or identify, from the request issued by the client device 21a-21c, the specific setting to which a received program interface pertains. When the specific setting has been identified, the request may be forwarded to the interface module 23a-23c being responsible for the identified setting. For example, requests Get[Setting A, ClientID X], Set[Setting A, Data], and NotifyOnChange[Setting A, ClientID] may all be forwarded to interface module 23a being responsible for Setting A.
  • requests Get[Setting B, ClientID X], Set[Setting B, Data], and NotifyOnChange [Setting B, ClientID] may all be forwarded to interface module 23b being responsible for Setting B; and requests Get[Setting C, ClientID X], Set[Setting C, Data], and NotifyOnChange[Setting C, ClientID] may all be forwarded to interface module 23 c being responsible for Setting C.
  • Each interface module 23a-23c may be adapted to manage storage of data for a certain setting, e.g. the Get request; caching of data for a specific setting; subscription to change notifications, i.e. the NotifyOnChange request; and altering of data for a specific setting, i.e. the Set request. If several client devices 21a-21c have posted a subscription for a change notification, said notification may be issued substantially simultaneously to all subscribing client devices 21a-21c. This is an advantage, as all client devices 21a-21c will have access to the same data for a setting pertaining to the notification.
  • the interface modules 23a-23c may be adapted to implement logic and policies for managing the requests.
  • the interface modules 23a-23c may thus comprise instructions, such as protocols, for communication between platforms, with memory devices, networks, and/or external devices.
  • the server device 20 may be implemented by the operational processor, but the storage location for a specific setting may be connected to the communication platform. Then, the interface module 23a-23c may carry out the communication between the platforms. Also, the interface module 23a-23c may manage the storage address for the data of the specific setting it manages access to, subscriber information, etc.
  • one or several interface modules 23a-23c may be configured to implement a backup and/or restore function. The backup function may be aware of one or several of the memory devices 22a-22c.
  • the backup function need not be aware of the specific settings stored on the memory devices 22a- 22c.
  • the backup function may be configured to backup data stored on one or several of the memory devices 22a-22c. For example, only data stored on an internal flash memory device and an external flash memory device may be included in the backup function.
  • the backed up data may be stored on an memory device dedicated for backup data.
  • a backup operation may e.g. be initiated by an end user.
  • the server device 20 may be adapted to instruct interface modules 23a-23c to backup all the data for settings they are responsible for and store the data on the memory device dedicated for the backup data.
  • the interface modules 23a-23c not included in the backup function will retrieve all settings on the memory device 22a-22c (similar as they would in response to a Get request), and store the data on the memory device dedicated for the backup data. However, any interface module 23a-23c which manage settings on a memory device 22a-22c included in the backup function need to do nothing in response to the instruction from the server device 20 to backup data.
  • a restore operation may be performed.
  • a restore operation may be imitated by an end user, e.g. after a previous backup.
  • the server device 20 may instruct interface modules 23a-23c to restore data for the settings they are responsible for.
  • the interface modules 23a-23c which manage data for settings stored on memory devices not included in the backup function, may restore the settings from the memory device dedicated for backup data and store the data on the memory device 22a-22c where the settings need to be stored.
  • Interface modules 23a-23c which manage data for settings on a memory device 22a-22c which is included in the backup function, need to do nothing in response to restore instructions from the server device 20.
  • a setting may comprise a main setting.
  • Each main setting may comprise a plurality of sub-settings.
  • the data of all sub-settings of a main setting may be returned.
  • Setting A may pertain to settings for a communication account.
  • the sub-settings for the communication account may e.g. comprise a username, a password, an IP address, a DNS address, and data compression settings.
  • Data for settings of the communication account may be required by a first client device 21a-21c, such as a communication module.
  • the first client device may require the data of the settings of the communication account to be able to establish a connection to the network 10.
  • the data for sub-settings for the communication account may also be required by a second client device 21a-21c.
  • the second client device 21a-21c may be a user interface module.
  • the user interface module may display the data of the settings of the communication account on the display 3.
  • each of the first and the second client devices may access the data of the sub-settings of the communication account by only identifying the main-setting in a Get request.
  • the server 20 may respond by including in a response the data pertaining to all sub- settings of the main setting.
  • the necessary communication between the server device 20 and the client devices 21a-21c may be decreased. This can be useful in all embodiments. However, it may be especially useful if the first and the second client devices 21a-21c are provided in separate platforms.
  • the first client device may be provided in the communication platform, whereas the second client device may be provided in the operational platform.
  • settings for connectivity such as of an Internet account, preferred networks, or short-range communication, such as IR (Infra Red) or Bluetooth®; messaging, such as SMS (Short Message Service) and/or MMS (Multimedia Message Service).
  • SMS Short Message Service
  • MMS Multimedia Message Service
  • Data for settings of e.g. a divert call application i.e. the phone number to which calls should be diverted, may be stored at the database 11.
  • a client device 21a- 21c applying a setting for the divert call could be an interface enabling inputting the phone number by a user.
  • An interface module 23a-23c may administer the storage location of the data pertaining to the setting of the divert call application.
  • Another client device 21a-21c requiring access to the data pertaining to the divert call setting could be a communication interface.
  • the communication interface may request access to the data of the divert call setting to be able to divert the call.
  • a first application or client device access data for a setting through an interface module
  • a second application or client device access the data for the setting directly from the memory device 22a-22c, which may be connected to the platform on which the second application is implemented.
  • data for the setting of "vibrate on incoming call” may be stored on a memory device 22a-22c connected to the communication platform.
  • a client device implemented on the operational platform may implement a user interface for this setting and may use an interface module 23a-23c to access the data for this setting.
  • a client device implemented on the communication platform and having the need for the data of the setting of "vibrate on incoming call” may access the data directly from the memory device 22a-22c.
  • Fig. 3 illustrates one embodiment of a method for managing access to data for settings of the electronic apparatus 1.
  • a setting request is received by the server device 20 from a client device 21a-21c.
  • the specific setting which the request pertains to and for which data is requested, is identified by the server device 20 based on the request.
  • the request is forwarded to the interface module 23a-23c being responsible for managing access to data for the specific setting.
  • it is determined whether the request is a Get request. If the answer in step 103 is yes, the procedure proceeds to step 104.
  • step 104 the data pertaining to the specific setting of the request is retrieved from the memory device 22a-22c, in which it is stored. Thus, the storage location of the data for the specific setting has to be determined. The determination of the storage location is made within the interface module 23a-23c responsible for the specific setting.
  • step 105 the data for the specific setting retrieved from the memory device 22a-22c is forwarded to the client device 21a-21c from which the request was received. Then, the procedure is ended. If the answer in step 103 is no, the procedure proceeds to step 106. In step 106 it is determined whether the request is a Set request. If the answer in step 106 is yes, the procedure proceeds to step 107.
  • step 107 the data pertaining to the specific setting is set, i.e. the data is stored in a memory device 22a-22c.
  • the storage location i.e. the address to the memory device 22a-22c, is registered in or accessible by the interface module 23a-23c being responsible for the specific setting.
  • the interface module 23a-23c being responsible for the specific setting.
  • data for the specific setting is already stored in a memory device 22a-
  • step 22c the stored data may be changed to the data received in the request. Then, the procedure proceeds to step 108.
  • step 108 it is determined whether the interface module 23a-23c being responsible for the specific setting has any subscription for a change notification registered. If data was changed in step 107 and a subscription for a change notification is registered, a change notification is issued to the subscribing client device 21a-21c. The changed data of the specific setting may also be included in the change notification. Then, the procedure is ended. If the answer in step 106 is no, the procedure proceeds to step 109. In step 109, it is determined whether the request is a NotifyOnChange request. If the answer in step 109 is yes, the procedure proceeds to step 110.
  • step 110 the subscription of a change notification for the specific setting is registered in the interface module 23a-23c being responsible for the specific setting. Then, the procedure is ended. If the answer in step 108 is no, e.g. if the request is not recognized, the procedure may result in an error and thus be ended. In some other embodiments, also other types of requests may be processed. This may be done e.g. after step 109. Also, in some other embodiments, not all steps according to the embodiment of Fig. 3 are carried out. For example, it is not necessary to include all of steps 103, 106, and 108, and the steps following a yes of the determinations made therein.
  • the determination made in step 103 may be made by the server device 20 directly before forwarding the request to the interface module 23a-23c. Alternatively, the server device 20 performs the determination indirectly in one of its interface modules 23a-23c. Also, in another embodiment, a single identifying step is provided, wherein the type of the received request is determined, i.e. whether the received request is a Get, Set, or NotifyOnChange request. Then, the request could be managed according to the steps following the determination steps in the embodiment of Fig. 3. In one embodiment, data pertaining to a setting may be included in a change notification. However, in another embodiment, the change notification does not include any data of the setting.
  • the client device having a subscription to the change notification is adapted to issue a Get request to get the latest values of the data of the changed setting in response to a change notification.
  • This may be useful for a) keeping the solution simple, and b) reducing the amount of data being transferred.
  • two Set requests for setting A are issued for setting a relatively short after one another, either by a single client device, e.g. client device 21a, or by separate client devices, e.g. client devices 21a and 21b.
  • client device 21c has subscribed to be notified on changes to data for setting A.
  • client device 21c has not yet been able to process a first change notification for setting A by the time a second notification is received. Therefore, client device 21a may instead be adapted to issue a separate Get request for setting A when it receives a change notification therefore. Then, it can issue the Get request when it is ready to process it. Furthermore, if the second change notification is received before a first Get request is issued in response to the first change notification, it may only be necessary to issue a Get request in response to the second change notification, wherein the data communication will be reduced compared to issuing a Get request also in response top the first change notification.
  • the administration of subscription may be centrally administered by the sever device 20.
  • change notifications may be centrally issued by the server device 20.
  • the server device 20 may make the determinations made in steps 103, 106 and 109.
  • the server device 20 may be utilized in a wide variety of electronic devices, which have a need to store data for settings at storage locations.
  • the electronic apparatus 1 may e.g. be a portable or handheld mobile radio communication equipment, a mobile radio terminal, a mobile telephone, a pager, a communicator, an electronic organizer, a smartphone or a computer. In the embodiment of Fig. 1, the electronic apparatus 1 is exemplified by a mobile telephone.
  • the network 10 may be any type of wired or wireless communication network, such as a telecommunication network, a WAN (Wide Area Network) a LAN (Local Area Network), or a WLAN (Wireless Local Area Network).
  • a telecommunication network such as a telecommunication network, a WAN (Wide Area Network) a LAN (Local Area Network), or a WLAN (Wireless Local Area Network).
  • WAN Wide Area Network
  • LAN Local Area Network
  • WLAN Wireless Local Area Network
  • management of access to data for settings is centralized in the server 20. This eliminates the possibility for race conditions, e.g. that two or more client devices 21a- 21c tries to change data of a specific setting simultaneously or that data of a setting is set to an incorrect value. Another advantage may be that clients with different priority do not get the wrong information in a setting due to race conditions.
  • the server device 20 can mitigate any such condition by queuing and arbitration of requests, e.g. for settings and alterations of settings.
  • notification of a change of data of a setting may be issued substantially simultaneously to multiple client devices 21a-21c. Thus, conflicts between client devices 21a-21c may be avoided.
  • backup and restoration of data for settings are simplified as the server device 20 has knowledge of the storage locations of data for all settings.
  • Backup data of data for settings may e.g. be stored in a computer and easily be transferred to the server device 20, which may restore data for settings from the backup data.
  • a master reset may easily be made, wherein all settings are reverted to data for a setting originally defined, which has been set during manufacturing.
  • the originally defined data for a setting may be included in the interface module 23a-23c responsible for the specific setting.
  • server device 20 may be adapted to queue several settings if they are received sufficiently close in time such that they cannot be handled immediately. Therefore, the server device 20 may also be adapted to arbitrate between different queued requests, e.g. if they have different priority.
  • Some embodiments of the invention may be carried out in a computer program product that is configured in accordance with the methods and functions described herein. Accordingly, some embodiments of the invention may be carried out when the computer program product is loaded and run in a system having computer capabilities, such as a processor.
  • Computer program, software program, program product, or software, as referred to herein means any expression, in any programming language, code or notation, of a set of instructions intended to cause a system having a processing capability to perform a particular function directly or after conversion to another language, code or notation.
  • the computer program product may be stored on a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne un appareil électronique (1) et un procédé de gestion des accès aux données en vue d’un réglage. L’appareil électronique (1) comprend un dispositif serveur (20) et au moins un dispositif client (21a-21c) qui est approprié à une interaction avec le dispositif serveur (20) pour accéder aux données d’un réglage. Les données sont stockées dans un dispositif de mémoire (22a-22c). Le dispositif serveur (20) comprend au moins un module d’interface (23a-23c) approprié à la gestion des accès aux données pour un réglage donné.
PCT/EP2006/066655 2005-09-30 2006-09-22 Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage WO2007039496A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP06806802.2A EP1941356B1 (fr) 2005-09-30 2006-09-22 Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/240,211 2005-09-30
US11/240,211 US8150944B2 (en) 2005-09-30 2005-09-30 Electronic apparatus with server device for managing setting data

Publications (1)

Publication Number Publication Date
WO2007039496A1 true WO2007039496A1 (fr) 2007-04-12

Family

ID=37668219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2006/066655 WO2007039496A1 (fr) 2005-09-30 2006-09-22 Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage

Country Status (5)

Country Link
US (1) US8150944B2 (fr)
EP (1) EP1941356B1 (fr)
CN (1) CN101278261A (fr)
TW (1) TWI400921B (fr)
WO (1) WO2007039496A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5565027B2 (ja) * 2010-03-26 2014-08-06 富士ゼロックス株式会社 処理装置、処理システム及び処理制御プログラム
KR102143441B1 (ko) * 2013-11-15 2020-08-11 삼성전자주식회사 전자장치 및 전자장치의 인증정보 업데이트 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US20020124092A1 (en) * 2000-02-10 2002-09-05 Pascal Urien Method for registering a user on an internet-type network directory server and/or for locating a user on said network, and smart card therefor
EP1426865A2 (fr) * 2002-11-05 2004-06-09 Sun Microsystems, Inc. Système et procedé pour gérer des informations de configuration d'un système d'ordinateurs répartis

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4634547B2 (ja) * 1998-06-30 2011-02-16 株式会社東芝 リアルタイム情報配信方法
FR2805107B1 (fr) * 2000-02-10 2002-04-05 Bull Cp8 Procede de gestion de transmissions de donnees multimedias via un reseau de type internet, notamment de donnees telephoniques, et carte a puce pour la mise en oeuvre du procede
US7194503B2 (en) * 2001-06-29 2007-03-20 Microsoft Corporation System and method to query settings on a mobile device
US7603447B2 (en) * 2004-07-30 2009-10-13 Research In Motion Limited Method and system for coordinating device setting between a communications client and its host device
US20060085517A1 (en) * 2004-10-04 2006-04-20 Markku Kaurila Download user agent plug-in for facilitating over-the-air downloading of media objects

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US20020124092A1 (en) * 2000-02-10 2002-09-05 Pascal Urien Method for registering a user on an internet-type network directory server and/or for locating a user on said network, and smart card therefor
EP1426865A2 (fr) * 2002-11-05 2004-06-09 Sun Microsystems, Inc. Système et procedé pour gérer des informations de configuration d'un système d'ordinateurs répartis

Also Published As

Publication number Publication date
EP1941356B1 (fr) 2016-01-13
EP1941356A1 (fr) 2008-07-09
CN101278261A (zh) 2008-10-01
US8150944B2 (en) 2012-04-03
US20070076227A1 (en) 2007-04-05
TW200803364A (en) 2008-01-01
TWI400921B (zh) 2013-07-01

Similar Documents

Publication Publication Date Title
JP6929497B2 (ja) クロスブロックチェーンインタラクション方法、装置、システム、および電子デバイス
CA2629694C (fr) Service centralise d'invitation a emettre
US20030206192A1 (en) Asynchronous message push to web browser
US8832304B2 (en) Protocol agnostic notification system
US20070291859A1 (en) Past presence hints
US20080040441A1 (en) Push e-mail inferred network presence
US9065788B2 (en) Method, device and system for voice communication
EP2146476A2 (fr) Accès à distance aux informations d'un terminal mobile à partir d'une extension d'un navigateur web
CN111786998A (zh) 基于微服务调用的权限管理方法、装置及存储介质
US10834033B2 (en) Method and system for transferring messages between messaging systems
CN112685709B (zh) 一种授权令牌管理方法、装置、存储介质及电子设备
US8326913B2 (en) Method and system for service contract discovery
EP2974159B1 (fr) Procédé, dispositif et système permettant une communication vocale
WO2021226781A1 (fr) Procédé et appareil de mise à jour de règle de pare-feu, serveur et support d'enregistrement
EP1941356B1 (fr) Appareil électronique avec dispositif serveur destiné à la gestion de données de réglage
US9577967B2 (en) Method and system for managing an informational site using a social networking application
JP4890740B2 (ja) ウェブブラウザに対する非同期メッセージのプッシュ
CN112995266A (zh) 一种信息推送方法及相关设备
CN112511595B (zh) 一种消息推送方法及消息服务系统
CN112612848B (zh) 数据实时同步的方法及装置、系统、电子设备、存储介质
JP2010068346A (ja) 通信サーバ装置、アドレス解決方法およびアドレス解決プログラム
US11025773B1 (en) Virtual communication service for mobile devices
US10944658B2 (en) Method, apparatus and system for method for start-up of monitoring of monitor objects in a computer-integrated telecommunications environment
JP6076018B2 (ja) 呼制御装置、登録処理方法、及びプログラム
US20220321696A1 (en) Presence based presentation of call identification information

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680035932.3

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006806802

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2006806802

Country of ref document: EP