WO2011150968A1 - Procédé et dispositif de communication - Google Patents

Procédé et dispositif de communication Download PDF

Info

Publication number
WO2011150968A1
WO2011150968A1 PCT/EP2010/057731 EP2010057731W WO2011150968A1 WO 2011150968 A1 WO2011150968 A1 WO 2011150968A1 EP 2010057731 W EP2010057731 W EP 2010057731W WO 2011150968 A1 WO2011150968 A1 WO 2011150968A1
Authority
WO
WIPO (PCT)
Prior art keywords
change
status
changes
service
wireless device
Prior art date
Application number
PCT/EP2010/057731
Other languages
English (en)
Inventor
Johan Nohave
Peter Molin
Original Assignee
Malvacom 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 Malvacom Ab filed Critical Malvacom Ab
Priority to PCT/EP2010/057731 priority Critical patent/WO2011150968A1/fr
Publication of WO2011150968A1 publication Critical patent/WO2011150968A1/fr

Links

Classifications

    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • 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/2866—Architectures; Arrangements
    • H04L67/2895—Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
    • 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
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to a method for updating contents of a service between a wireless device, WD, communicating over a wireless interface, and at least a first Internet service, IS, associated with an Internet connected server and where a proxy is used to collect data from the at least first IS for transmission to the WD.
  • a proxy is used to collect data from the at least first IS for transmission to the WD.
  • One object of the present disclosure is to improve wireless device power usage and bandwidth usage. This object is achieved by a method as defined in claim 1 . More specifically, there is disclosed a method for updating contents of a service between a wireless device, WD, communicating over a wireless interface, and at least a first Internet service, IS, associated with an Internet connected server. The method involves using a service proxy device, SP, which is located on the other side of the wireless interface as seen from the WD. The SP maintains a database reflecting IS contents of the WD.
  • the SP When the SP receives or detects information from the first IS regarding a first change to the IS content, the SP determines a latency threshold indicating a first time frame within which a notification of the first change should be pushed to the WD, and when this threshold expires, the SP creates a notification message including the first change, which is pushed to the WD.
  • a latency requirement for an update implies that the updates will be pushed to the WD in their order of urgency which may be determined by the user in different ways.
  • this update may be coordinated with at least one other update which means that overhead may be reduced. This is due to that a queue is created by assigning the latency requirement.
  • the SP may thus check, at the end of the first time frame, whether there are further changes having an unexpired latency threshold, and, if so, select a second change to be included in the notification message. This coordination saves energy and bandwidth resources thanks to the reduced overhead.
  • the first and second changes may be related to first and second ISs, respectively.
  • the SP may maintain WD status information and the second change may be selected among a set of changes based on the WD status information.
  • the WD status information may be used to further delay the pushing of the notification message. This may be used to ensure that the WD does not e.g. waste a low remaining battery level on non-critical updates.
  • the WD status information may include one or more of: battery status, charging status, display status, roaming status, access type status, and application status.
  • the SP may selects the second change among a set of changes and based on the size of the second change and/or based on the latency requirement of the second change.
  • the present disclosure further relates to a server devised for running a proxy application as defined above.
  • the server then includes means for carrying out the indicated steps.
  • the latency threshold above is assigned to the downloading of an update, rather than to the notification of the existence of an update.
  • the WD receives a notification message from the SP, including at least one change regarding the first IS and assigns a latency threshold to the change,
  • the WD initiates, when the latency threshold has expired, a wireless communication pulling/downloading the change from the SP.
  • This method may be varied in different ways in correspondence with the notification method defined above, and there is also considered a WD, which is devised for carrying out the method, i.e. has means for carrying out the required steps.
  • the notification method may be carried out in the WD and the pulling method may be carried out in the SP. Both entities may be devised accordingly.
  • a method for providing authentication in a service proxy device, SP which is devised to accomplish updating of service contents between a wireless device, WD, communicating over a wireless interface, and at least a first Internet service, IS, associated with an Internet connected server, wherein the WD is connected, via the wireless interface to the SP, which maintains a database reflecting IS contents of the WD.
  • the method involves creating an account in the SP for a specific user, linking the user's account to a hardware identity (e.g. an IMEI code) of the WD that the user employs, granting access to the account based on the hardware identity and linking an account in the SP to a specific account on an IS.
  • a hardware identity e.g. an IMEI code
  • Fig 1 illustrates a system where devices and methods of the present disclosure may be employed.
  • Fig 2 illustrates schematically the layout of a wireless device, WD, connected to a number of Internet services, ISs, via a service proxy, SP.
  • Fig 3 illustrates a flow chart for a notification process.
  • Fig 4 illustrates a flow chart for a downloading process.
  • Fig 5 illustrates a wireless device status datasheet.
  • Fig 6 illustrates an authentication scheme
  • Fig 7 illustrates a flow chart for an authentication scheme.
  • FIG 1 illustrates a system where devices and methods of the present disclosure may be employed.
  • a wireless device, WD, 101 which is here illustrated as a mobile phone, is utilized by a user in connection with a num- ber of Internet based services, IS, 102, 103, 104.
  • WD 101 is here illustrated as a mobile phone, which is considered a common embodiment, other WDs are conceivable, such as laptop computers and the like.
  • a broad definition of a WD is a device that, at least temporarily, is capable of communicating via a wireless interface.
  • the WD could in principle be part of a fixed structure, for instance a surveillance or alarm system operating via a cellular phone system.
  • the ISs are usually different information management services, which are often known under a trademark (FLICKR, TWITTER, FACEBOOK, GMAIL, LINKEDIN, etc.) and may encompass a wide variety of services, including all sorts of professional or private cloud computing resources.
  • the WD accesses the ISs via a wireless interface, in the illustrated case via a cellular phone base station 106 or via a wireless local area net- work, WLAN, access point, AP, 107.
  • the base station 106 may be connected to the Internet 109 via a public land mobile network, PLMN, 1 10 and the AP may be connected to a network forming part of the Internet as is well known and will not be discussed further. Needless to say, other access methods are conceivable, e.g. via BLUETOOTH connections.
  • the WD may also switch between different access methods during use or in between sessions.
  • the wireless interface There is generally a desire to use the wireless interface in an efficient way. If the WD is battery operated this is one reason to use the wireless interface as little as possible, as transmissions and receptions of data consume power. Further, the bandwidth of the wireless interface is limited, and excessive bandwidth usage is sometimes heavily charged. Also, the wireless interface may sometimes be slow and function intermittently, which is another reason to use it efficiently.
  • a WD may employ a number of ISs in a straightforward manner. This implies organizing the service processes in the WD as if it were a personal computer with an Ethernet connection to a local area network , LAN where the bandwidth is comparatively huge and cheap, where the latency is negligible, and where power consumption is not an issue at all. The services may then ignore that lower layers use radio communication to carry out data transmissions.
  • a WD's access to Internet services is enhanced by the use of a service proxy, SP, 1 1 1 which to a great extent optimizes the use of the wireless interface, such that an improved access is provided at a given power and/or bandwidth usage.
  • the SP 1 1 1 is an application run on the other side of the wireless interface as seen from the WD 101 .
  • the SP 1 1 1 may, as shown, be run on a server directly connected to the Internet 109.
  • the SP 1 1 1 may include an entity in a PLMN 1 10 or the like, as is faintly illustrated in fig 1 .
  • the SP can access the ISs at virtually no "cost" in terms of bandwidth usage and/or power consumption.
  • the SP operates as the WD's interface towards the ISs. It quickly downloads and/or uploads information from/to the ISs, and appears as seen from the ISs as being the WD itself.
  • the operation of the ISs need not be modified as compared to if they were operating directly vis-a-vis a WD. This is however optionally possible, and can be beneficial in order to take advantage of possibilities that arise when operating towards a device that is not as limited in terms e.g. of bandwidth usage as a WD.
  • the SP may, when operating towards the WD via the wireless interface, optimize the use of the wireless interface, e.g. by co- ordinating transactions with regard to multiple ISs. For instance, a wireless transmission with respect to a first IS may be coordinated with a wireless transmission of a second IS in order to reduce overhead and thus improve bandwidth efficiency.
  • Fig 2 illustrates schematically the layout of a wireless device, WD, connected to a number of Internet services, ISs, via a service proxy, SP.
  • the SP is the WD, as it may replicate all functions of a WD.
  • the SP interacts with the ISs regularly by means of a service connector unit 201 . Usually, this is done on the initiative of the SP, which polls the ISs for updated data, or uploads updated data to the ISs. It is however also possible to let the ISs contact the SP on their initiative. In fact, the SP makes this behavior a lot more attractive, since the SP-to-IS communication can be regarded as "cheap", when compared to the wireless interface communication. It is therefore possible to adapt an IS, which is aware of the fact that it communicates with a SP rather than directly with a WD, such that it pushes updates, etc. to the SP at regular intervals or as a result of an interrupt.
  • the SP may keep track of the status of the WD, and adapt its communication with ISs accordingly. For instance, if the battery of the WD is low, the SP knows that heavy downloading to the WD is not likely to take place soon, and may adjust the updating intervals for e.g. low priority services accordingly. If the WD has roamed to a country where an IS is not relevant, further downloading of data from that IS may be dispensed with until the WD has roamed again.
  • the SP has access to a storage medium 202 which includes a complete data mirror of corresponding data kept on a storage medium 203 in the WD.
  • a storage medium 202 which includes a complete data mirror of corresponding data kept on a storage medium 203 in the WD.
  • the SP receives or detects an update in an IS relating to a certain data set A, this may be expressed as a set of data containing the changes to the data, ⁇ . For each such change a latency requirement or threshold is determined. This allows for coordination of communications via the wireless interface.
  • the SP After receiving a number of updates from different ISs, the SP will thus have a number of such ⁇ -files that should be included in the data mirror to change the data therein. Before such a change takes place, the ⁇ -files should however first be communicated to the WD.
  • the mirror may be used to compute the set of ⁇ -files to achieve optimal data transfer e.g. in terms of low energy usage in the WD.
  • the energy consumption for a transfer process includes not only the energy used to actually transfer the data via the radio interface, but also the energy needed to recover data, e.g. if the data has been compressed before transfer.
  • the optimal selection of transfer methods may be dynamically determined based on WD status (e.g. roaming), wireless interface used (WLAN, UMTS, GRPS, etc.) and user preferences.
  • the communication of ⁇ -files may be achieved in two consecutive steps which both offer possibilities for coordination of update transfers. Firstly, a notification is pushed from the SP to the WD, where the notification comprises a message informing the WD that there is an update to a certain data set, e.g. " ⁇ exists". In principle, if ⁇ is very small, the notification could be replaced with the actual change itself.
  • the WD downloads the corresponding ⁇ -file from the SP.
  • the correspon- ding file in the respective database 202, 203 may be updated.
  • Each of the SP and the WD thus keeps a record 204, 205 with ⁇ -files with which the data in the database should be updated.
  • both those steps can be carried out while coordinating communications regarding updates of different ISs or communications regarding updates with different latency requirements or priorities relating to the same IS.
  • Each of the WD and the SP may further include a functional block 206, 207 for optimizing the data to be transmitted. Such functional block may carry out e.g. image compression or the like as is well known per se.
  • Each of the WD and the SP further comprise a communication scheduler block 208, 209 for optimizing the use of the available bandwidth and the available battery power as will be described, typically by reducing transmission overhead.
  • the WD In order to interface with the SP, the WD has a data access platform, DAP, which in addition to the previously mentioned functional blocks includes an application service interface 210. This interface works against low and high level applications 21 1 , 212 which operate in the WD. As seen from those applications, the DAP can be considered as the IS. The data of the IS can be accessed locally on the mirror 203 in the DAP.
  • DAP data access platform
  • a latency requirement may be associated with each IS or for different services of a particular IS. This means that for a particular change in data received from an IS at the SP, there will be a corresponding time frame within which the change should be transmitted to the WD or within which a notification relating to the change should be transmitted to the WD. The same may of course be true for data changed in the WD which should be transmitted to the SP and forwarded to the IS.
  • Latency requirements may be very different from IS to IS. For instance, a burglar alarm may need to be transferred to the WD within seconds, while non-critical or seldom accessed information could wait for hours or days without the delay causing the user any problem. Latency requirement may also vary within an IS. For instance, an e-mail from a prioritized sender may be transmitted within a minute, while e-mails from other sources can wait longer.
  • a latency requirement may be assigned can be the following.
  • a user that is connected to a social network service, where the user's friends have individual pages with status updates and the like. Typical characteristics of such a service is that is used for leisure (non critical data), and it updates regularly over the day (the users typically update their pages about once a day).
  • the user may typically have 20-30 close friends and more than 100 peripheral friends.
  • the user typically checks for updates 3 or 4 times each day.
  • Updates for close and peripheral friends may be treated differently, even if both types of updates can be designated with a leisure priority level, e.g. compared with an email from a business contact.
  • the update from a close friend can have a latency requirement of 3 hours (i.e. the notification of the update should be pushed and/or the update should be downloaded within that time frame), whereas the peripheral friend's update can have a latency requirement of 48 hours.
  • Additional conditions may also supersede the latency requirement, causing an extended latency or causing a delay in transfer, and may differ between the updates.
  • the close friend's update may be transferred when the WD has roamed to a non-home network, while the peripheral friends update may not, even though its latency threshold has expired.
  • the close friend's update may be pushed also via 3G/UMTS or GPRS networks, while the peripheral friend's update may only be pushed via WLAN connections, etc.
  • Fig 3 illustrates a flow chart for a notification scheduling method 300.
  • the method may primarily be implemented in an SP for downlink communications, but is equally applicable in a WD for uplink communication purposes.
  • the SP receives 301 updates from different ISs, either because the SP polls the ISs for updates or because the ISs push updates to the SP. In any case, a difference between the IS and the corresponding portion of the mirror is detected.
  • the flowchart of fig 3 may indicate that the method proceeds to further steps as will be discussed below, the SP will also remain in the state where it receives updates and the following steps may be dealt with as an interrupt routine dealt with in parallel with the further steps to be described.
  • Each received update is assigned 302 with a latency threshold as has been described earlier.
  • the SP thus collects a number of updates in a queue, and processes these updates in the order that their latency requirements mature.
  • a first update's latency time will expire 303, i.e. the update should be notified.
  • some updates must be processed as soon as they come in, and in those cases the latency requirement is 0 s, i.e. the process jumps directly to this step.
  • a notification message should now be created and pushed to the WD (or from the WD to the SP in the reversed scenario).
  • Push messages can be considered as will be described below.
  • Most push messages imply a certain available space, which may allow more than the first update to be notified.
  • the process therefore optionally checks 304 in the SPs notification queue for updates the latency requirement time frame of which have not yet expired.
  • the process selects 305 at least a second and, if possible with regard to remaining notification message space, even further updates to notify.
  • the selection may be done based on different parameters of the updates in the queue.
  • One option is to choose an update related to the same IS as the first update.
  • a second option is to choose the update with the shortest remaining time until latency requirement expiration.
  • a third option is to choose the update which had the shortest latency time to start with.
  • the SP may maintain a WD status datasheet, and the selection of updates may be affected by the WD status, as will be described in connection with fig 5. Further, the WD status may affect the latency requirements, e.g. if the WD is idle or low on battery, a latency time frame may be extended.
  • a notification message is then created 305, which includes information regarding the first, the second and any further updated. This message is then pushed 306 to the WD.
  • SMS short message
  • Another option is a long poll. Even if, formally, a long poll may not be considered a push message, the technique is used as a push and should be considered as such within the context of the present disclosure.
  • a polling entity sends a poll to a polled entity. If the polled entity has no information to send when receiving the poll, it does not send an empty answer, and instead waits until it actually has information to send or waits until poll timeout. As soon as there is any information to send, the poll is responded to.
  • Other push options may also be considered, such as WAP push.
  • the assignment of a latency time allows the coordination of notifications.
  • the SP may also merge different changes. For instance, a second change may render a first change obsolete. This means that the first change or parts thereof need not be transmitted at all. Thanks to the assigned latency threshold the SP therefore save the corresponding bandwidth/power.
  • the status of the WD and the applications run thereon may also influence the scheduling, as well as the wireless interface used.
  • the SP may look through the queue of updates for updates relating to this application, and determine what to push and which interface to use. Based on the size of the updates, the cost of transferring them all may be cheaper through WLAN, but cost may still be negligible using 3G.
  • the energy consumption for sending all updates through 3G may be better than through WLAN in this case (determined by a threshold). If the battery status of the device is quite low, but not too low, the SP may decide to use 3G and to transfer both updates (close friend's and peripheral friend's) as the extra cost and energy consumption for sending both is negligible. This implies in that both messages are sent before the respective latency threshold has expired.
  • the SP may send data from close friends only. If the social networking application is not in use, the SP can wait until the latency threshold expires and in such cases can send all data, but only from closed friends, and e.g. within a 1 Mbyte limit if the WD is in a roamed state. In another case, when the WD has not roamed, the SP can send all updates including those relating to peripheral friends, since when piggy-backing on an already established connection, less power is consumed.
  • the latency requirements may be superseded as controlled in accordance with WD and WD application status.
  • Fig 4 illustrates a flow chart for a downloading scheduling method 400 according to the present disclosure.
  • this method is applied in the WD as most traffic will probably be downlink.
  • such a method employed in the SP is also considered.
  • the method illustrated in fig 3 can be
  • a latency threshold may be assigned, communications may be coordinated, and latency thresholds may be superseded as discussed above.
  • the WD receives 401 notifications regarding updates from the SP.
  • the WD assigns 402 latency thresholds for the received updates similarly as in the method discussed in connection with fig 3.
  • the latency threshold expires 403.
  • the WD may therefore select 404, from the queue, a number of changes to download, and this selection is done at least in part depending on the status of the WD. For instance, if the WD is on a low battery, only the most important (urgent) changes are selected, or only changes smaller that a certain size (size of the ⁇ -file). The same may apply if the WD has roamed, and access to bandwidth is expensive. On the other hand, if the WD is charging and the WD is using a cheap WLAN hotspot access, all downloads in the queue may be selected.
  • the WD initiates 405 a downloading of a first update, and may add one, a number of, or all further updates to this downloading. As a number of updates are received in one batch, overhead is saved. This can be controlled in correspondence with the notification process discussed earlier. The WD may select, in a number of different ways, which and how many further updates should be downloaded.
  • Fig 5 illustrates a wireless device status datasheet 501 , which contains a number of WD parameters and which is maintained, i.e. regularly updated, by the SP.
  • the values of the different parameters may optionally affect the way in which the SP operates.
  • the WD is active or not.
  • the WD being turned on of course does not imply the need to delay transmission, i.e. to modify latency requirements.
  • the WD turned off means that transmissions can wait, which will probably enable more updates to be coordinated in a fashion that improves efficiency. If the WD is on, the display being active or not may affect the processes similarly, i.e. the display being turned off (WD being on) may delay updates.
  • the WDs roaming status is another important parameter. If the WD is in its home network the transmission cost is probably a lot less than if it has roamed to an away network. Thus, if the WD is not in its home network, it may be preferred to delay transmissions, i.e. to reduce latency requirements. Additionally, some ISs may be less relevant when the WD is away, and may be given a low priority when updates are selected for notification or download.
  • Another parameter is the type of access used or the access options available, e.g. UMTS (Universal Mobile Telephony System), GPRS (General Packet Radio Service), WLAN (Wireless Local Area Network), Ethernet/USB (Universal Serial Bus) cable, etc.
  • UMTS Universal Mobile Telephony System
  • GPRS General Packet Radio Service
  • WLAN Wireless Local Area Network
  • Ethernet/USB Universal Serial Bus
  • a maximum data transfer quota e.g.
  • the battery status is another feature that may be watched. If battery status is low, some updates may be delayed with reduced latency require- ments, or large updates may be less prioritized for notification or downloading.
  • the charging status of the battery i.e. whether or not the battery is being charged may also affect this, i.e. if the WD is being charged, a low battery level need not mean that updates should be delayed.
  • the WD's position e.g. determined by means of GPS, is another feature that may affect an IS update's priority level or latency requirement depending on the IS' relevance for the position in question.
  • the signal strength (i.e. RSSI) may also affect updates.
  • Another feature is the time where the WD resides. Some updates may sometimes wait during night.
  • Fig 6 illustrates generally an authentication scheme
  • fig 7 illustrates a corresponding flow chart.
  • the SP creates 701 an account for each user, which is given a user identity. This may be carried out by means of client software in the wireless device together with the SP, and the user need not deal with this manually.
  • the SP may generate an account identity and optionally a password that allows the user to access the SP account.
  • IMEI International Mobile Equipment Identity
  • the SP may then simply check the hardware entity of the WD with which it communicates, and grant access 703 to the account which is linked to the hardware identity.
  • the SP account may in turn be linked 704 with an IS account.
  • the present disclosure relates to a method for updating data between a wireless device and one or more Internet services running on a server connected to the Internet.
  • a service proxy device which is located on the other side of the wireless interface as seen from the wireless device, is used.
  • the service proxy mirrors Internet service related data on the wireless device and may act as the wireless device as seen from the Internet services.
  • the service proxy may coordinate transmission of notifications and downloads related to different Internet services, such that more efficient use of bandwidth and power may be achieved.
  • the service proxy may further maintain a record regarding wireless device status which may also affect transmissions. Corresponding devices are also considered.

Landscapes

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

Abstract

La présente invention porte sur un procédé de mise à jour de données entre un dispositif sans fil et un ou plusieurs services Internet tournant sur un serveur connecté à l'Internet. Un dispositif mandataire de services, qui se trouve de l'autre côté de l'interface sans fil vu depuis le dispositif sans fil, est utilisé. Le mandataire de services reflète des données relatives à un service Internet sur le dispositif sans fil et peut jouer le rôle du dispositif sans fil vu depuis les services Internet. Le mandataire de services peut coordonner des transmissions de notification et des téléchargements relatifs à différents services Internet, de façon à pouvoir parvenir à une utilisation plus efficace de la bande passante et de l'énergie. Le mandataire de services peut en outre maintenir un enregistrement concernant un état de dispositif sans fil qui peut également influer sur des transmissions. La présente invention porte également sur des dispositifs correspondants.
PCT/EP2010/057731 2010-06-02 2010-06-02 Procédé et dispositif de communication WO2011150968A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/057731 WO2011150968A1 (fr) 2010-06-02 2010-06-02 Procédé et dispositif de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/057731 WO2011150968A1 (fr) 2010-06-02 2010-06-02 Procédé et dispositif de communication

Publications (1)

Publication Number Publication Date
WO2011150968A1 true WO2011150968A1 (fr) 2011-12-08

Family

ID=43500037

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2010/057731 WO2011150968A1 (fr) 2010-06-02 2010-06-02 Procédé et dispositif de communication

Country Status (1)

Country Link
WO (1) WO2011150968A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2511717A (en) * 2011-09-26 2014-09-17 Theappbuilder Ltd Updating mobile applications
GB2517732A (en) * 2013-08-29 2015-03-04 Sim & Pin Ltd System for accessing data from multiple devices
WO2015044597A1 (fr) * 2013-09-30 2015-04-02 Orange Procédé d'accès d'un utilisateur a au moins un service de communication fourni par l'intermédiaire d'un centre informatique d'un système d'informatique en nuage
CN108471445A (zh) * 2018-04-02 2018-08-31 北京奇艺世纪科技有限公司 一种关注对象内容更新通知方法和装置
US10979550B2 (en) 2012-02-23 2021-04-13 TapNav Ltd Mobile communication device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6477548B1 (en) * 1998-09-30 2002-11-05 Casio Computer Co., Ltd. Server computer capable of automatically notifying updated database content to client computer, and program storage medium
US20040088390A1 (en) * 2002-11-05 2004-05-06 Microsoft Method and levels of ping notification
US7028040B1 (en) * 2001-05-17 2006-04-11 Microsoft Corporation Method and system for incrementally maintaining digital content using events
US20060171523A1 (en) * 2002-12-19 2006-08-03 Cognima Ltd. Method of automatically replicating data objects between a mobile device and a server
US20080155112A1 (en) * 2006-12-22 2008-06-26 Nokia Corporation System and method for updating information feeds
WO2010010408A1 (fr) * 2008-07-25 2010-01-28 Vodafone Group Plc Réseau de communication mobile

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6477548B1 (en) * 1998-09-30 2002-11-05 Casio Computer Co., Ltd. Server computer capable of automatically notifying updated database content to client computer, and program storage medium
US7028040B1 (en) * 2001-05-17 2006-04-11 Microsoft Corporation Method and system for incrementally maintaining digital content using events
US20040088390A1 (en) * 2002-11-05 2004-05-06 Microsoft Method and levels of ping notification
US20060171523A1 (en) * 2002-12-19 2006-08-03 Cognima Ltd. Method of automatically replicating data objects between a mobile device and a server
US20080155112A1 (en) * 2006-12-22 2008-06-26 Nokia Corporation System and method for updating information feeds
WO2010010408A1 (fr) * 2008-07-25 2010-01-28 Vodafone Group Plc Réseau de communication mobile

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ARMSTRONG ET AL.: "Efficient and Transparent Dynamic Content Updates for Mobile Clients", MOBISYS '06, 19 June 2006 (2006-06-19)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2511717A (en) * 2011-09-26 2014-09-17 Theappbuilder Ltd Updating mobile applications
US10979550B2 (en) 2012-02-23 2021-04-13 TapNav Ltd Mobile communication device
GB2517732A (en) * 2013-08-29 2015-03-04 Sim & Pin Ltd System for accessing data from multiple devices
US10893045B2 (en) 2013-08-29 2021-01-12 Liberty Labs Limited System for accessing data from multiple devices
WO2015044597A1 (fr) * 2013-09-30 2015-04-02 Orange Procédé d'accès d'un utilisateur a au moins un service de communication fourni par l'intermédiaire d'un centre informatique d'un système d'informatique en nuage
FR3011413A1 (fr) * 2013-09-30 2015-04-03 Orange Procede d'acces d'un utilisateur a au moins un service de communication fourni par l'intermediaire d'un centre informatique d'un systeme d'informatique en nuage
US10193966B2 (en) 2013-09-30 2019-01-29 Orange Method for a user to access at least one communication service provided via a data centre of a cloud computing system
CN108471445A (zh) * 2018-04-02 2018-08-31 北京奇艺世纪科技有限公司 一种关注对象内容更新通知方法和装置
CN108471445B (zh) * 2018-04-02 2021-08-13 北京奇艺世纪科技有限公司 一种关注对象内容更新通知方法和装置

Similar Documents

Publication Publication Date Title
Warren et al. Push notification mechanisms for pervasive smartphone applications
US9438601B2 (en) Operating group resources in sub-groups and nested groups
US8532649B2 (en) Communications management
KR101006114B1 (ko) 콘텐츠 푸시 서비스
JP2017504854A (ja) サブスクリプション通知を実施するための方法および装置
CN102523194A (zh) 使用在场技术的应用信息和命令的传输
CN102227899B (zh) 移动台和向移动台提供服务的应用服务器及其操作方法
CN109819021B (zh) 业务后台及其异步处理业务请求的方法
CN102177697A (zh) 互联网业务控制方法及相关设备和系统
CA2762661A1 (fr) Procede et systeme d'execution selective de services mandates
WO2011150968A1 (fr) Procédé et dispositif de communication
CN108200543B (zh) 短信发送方法和装置
CN110545539B (zh) 基于大数据的自适应链路建立的方法及系统
US20050256959A1 (en) Method of and system for multimedia messaging system interoperability
US9112807B2 (en) System and method for managing network information
US20240049060A1 (en) First node, third node, and methods performed thereby, for handling quality of service in a communications network
JP2003115795A (ja) 通信システム、この通信システムに用いるサーバ、エージェント制御方法、エージェント制御プログラム
CN104541557B (zh) 集成寻呼技术
CN114143729B (zh) 用于与IoT设备进行数据收发的装置、方法及计算机可读存储介质
US8249000B2 (en) Controlling the delivery of messages to a mobile client
US20150208213A1 (en) Messaging system and method with adaptive packet and mobile network message paths
EP3412021B1 (fr) Terminal mobile, module de mise en tampon, et procédés associés pour le téléchargement montant d'un fichier dans un réseau de communication
CN116266830A (zh) 一种多媒体消息的传输方法和装置
CN106900060B (zh) 一种获取、下发应用信息的方法和设备
CN115396865A (zh) 终端漫游数据处理方法及网络设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10721817

Country of ref document: EP

Kind code of ref document: A1