WO2011045009A1 - Mécanisme d'ar d'un message d'état par sms - Google Patents
Mécanisme d'ar d'un message d'état par sms Download PDFInfo
- Publication number
- WO2011045009A1 WO2011045009A1 PCT/EP2010/006182 EP2010006182W WO2011045009A1 WO 2011045009 A1 WO2011045009 A1 WO 2011045009A1 EP 2010006182 W EP2010006182 W EP 2010006182W WO 2011045009 A1 WO2011045009 A1 WO 2011045009A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- client
- network instance
- message
- sms
- network
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 55
- 230000005540 biological transmission Effects 0.000 claims abstract description 15
- 238000004590 computer program Methods 0.000 claims abstract description 6
- 230000000007 visual effect Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 6
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
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
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
- H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- 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
- 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
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
- H04M1/72433—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for voice messaging, e.g. dictaphones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
Definitions
- the present invention relates to a method, a client, a system, a program and a computer program product for a status SMS acknowledgement mechanism if the SMS message exchange is used for communication between a client and a network instance, especially if the SMS message exchange is used for
- Synchronization is a procedure in a mobile radio network.
- Synchronization comprises e.g. the data adjustment between a first dataset stored in a first device and a second dataset stored in a second device.
- Synchronization e.g. between a network instance and a client is realized by exchanging messages using the Short Message System (SMS) via a user interface (Ul).
- SMS message exchange (in the following also called message exchange) allows the introduction of the client to the network instance.
- a subscriber of a service in the following also called provisioned subscriber
- SIM subscriber identity module
- the subscriber installs the client in this terminal.
- the client and the server must be synchronized.
- This synchronization is initiated by transmission of a status message (in the following also called STATE SMS or STATUS SMS) from the client to the server.
- STATE SMS in the following also called STATE SMS
- STATUS SMS a synchronization message
- the server transmits a synchronization message (in the following also called SYNC SMS) comprising the data according to the service (e.g. addresses, phone numbers etc).
- SMS message exchange Important for the SMS message exchange is the awareness of the installed software version of the client.
- Different service implementations i.e. different software versions, (in the following also called client types) use different SMS message formats.
- IMAP Internet Message Access Protocol
- client types i.e. different software versions
- SMS message formats i.e. SMS message formats
- client type software version i.e. SMS message format
- the client must have the adequate client type (software version i.e. SMS message format) installed to read the synchronization message from the server. If the client has the wrong version (leading to the wrong SMS message format) installed the synchronization message must be rejected and the synchronization has failed.
- An object of the present invention is to provide a method, a client, a system, a program and a computer program product for communication between a client (in the following also called WM client) and a network instance (in the following also called Visual Voicemail (WM) network instance, WM server or server) by using a Status short message system (SMS) acknowledgement mechanism to assure the communication, especially the synchronization, between the client and the network instance using an SMS message exchange.
- SMS Status short message system
- the object of the present invention is achieved by a method for communication between a client and a network instance wherein the client uses a short message system (SMS) in a mobile radio network, wherein the method comprises a first step and a second step, wherein the first step comprises the transmission of a status message between the client and the network instance and wherein the second step comprises the transmission of an acknowledgement message between the client and the network instance.
- SMS short message system
- the status message is sent by the client the status message is in the following also called first client status message, mobile originated (MO) Status SMS or MO State SMS.
- MO mobile originated
- MO mobile terminated
- MT mobile terminated
- the acknowledgement message is sent by the network instance the acknowledgement message is also called network instance acknowledgement message or MT acknowledgement SMS.
- the acknowledgement message is sent by the client the acknowledgement message is also called client acknowledgement message or MO acknowledgement SMS.
- the status message comprises at least one of a first format information or a first data information
- the second step comprises the transmission of an acknowledgement message between the client and the network instance, wherein the acknowledgement message comprises at least one of a second format information referring to the first format information or a second data information referring to the first data information.
- the second format information comprises an acceptance information referring to the acceptance of the first format information and/or the second data information comprises a usability information referring to the usability of the first data information.
- Standard SMS acknowledge provides only the confirmation of the SMS message delivery. It does not say anything about understanding of the content of the SMS message (e.g. content format acceptance, correctness of transferred information).
- standard SMS acknowledgement (on lower layer) is extended by the acknowledgement provided directly by the WM client/server (on application layer).
- the SMS acknowledgement is handled on the application layer and does not directly relate to already existing SMS protocol acknowledgement mechanism designed for SMS protocol layer (lower layer).
- the acknowledgement message according to the present invention works in combination with SMS protocol layer acknowledgement (SMS-SUBMIT-REPORT), i.e. the combination of both acknowledgements (on SMS protocol layer and on WM application layer) provides the advantage of the method according to the present invention.
- the present invention it is advantageously possible to assure the communication, especially the synchronization, between client and network instance using SMS communication even if an error in the communication between client and network instance during the synchronization process occurs e.g. if the status message is not correctly transmitted or the content of the status message is not correctly interpreted or the status message is generated using a wrong client type and therefore rejected.
- the content of the status message is e.g. the request for synchronization between the client and the network instance or e.g. the information about the software version installed in a terminal by a provisioned subscriber or e.g. a message format used in the status message.
- Two exemplary error cases that are avoidable by the present invention are described in the following.
- the subscriber with WM version 1 service inserts a Subscriber Identity Module (SIM) card into a terminal equipped with a WM version 2 client (client type 2).
- SIM Subscriber Identity Module
- client type 2 the initial mobile originated (MO) STATE SMS is lost because of a mistake
- the WM network instance keeps trying to synchronize the WM client using the WM version 1 (client type 1 ) SMS message format by sending a mobile terminated (MT) SYNC SMS client type 1 message to the WM client.
- MT mobile terminated
- the MT SYNC SMS message is rejected so that the synchronization between WM client and WM network instance has failed.
- a regular voicemail subscriber i.e. a subscriber that has yet neither client type 1 nor client type 2 provisioned inserts a SIM card into a terminal and installs the WM version 1 client (client type 1 ).
- the MO STATE SMS message is delivered but rejected by the network instance because the WM service is not provisioned yet. After this rejection the regular voicemail subscriber requests by error provisioning of a client type 2 WM version which is the wrong WM version because client type 1 is installed.
- the WM network instance sends a MT STATE SMS message using client type 2 to the WM client using client type 1. Because of the different client types the WM client rejects the MT STATE SMS message so that the synchronization between WM client and WM network instance has failed (this error case is called delayed provisioning with wrong WM client type).
- acknowledgement message is not correctly interpreted both the client and the network instance dispose of predefined error case procedures.
- error case procedures it is possible to assure the exchange of the necessary information for the SMS message exchange (e.g. user interface attributes) between the client and the network instance.
- the acknowledgement message using the application layer.
- acknowledgement message comprises an information identifying the related status message.
- the acknowledgment message comprises at least a part of the text of the related status message so that it is definitely clear that the acknowledgement message relates to the related status message.
- a part of the text comprises preferably 10 characters, more preferably 50 characters, more preferably 100 characters.
- acknowledgment e.g. comprises the information that the status message was interpreted as a status message that requests the synchronization between the client and the server.
- the client comprises a user interface (Ul) and the acknowledgement message comprises Ul attributes.
- the MO acknowledgement SMS comprises Ul specific attributes in order to find out the WM client type.
- the acknowledgement message comprises e.g. information about the client type version especially the software version that is installed e.g. in the client by the subscriber or the software version that is provisioned and installed in the network instance.
- CCM customer relationship management
- a third step comprises the transmission of a further status message between the client and the network instance in case that the acknowledgement message was not received.
- the client or the network instance is able to send the status message again in case that the first status message was not or not adequately delivered or in case that the content of the status message was not correctly interpreted.
- this resending of the status message it is avoidable that synchronization fails because of a message delivery problem or because or a misinterpretation of the content of the status message.
- the method comprises a fourth step wherein the fourth step comprises that the client sends a request for reconfiguration to the network instance in case that the acknowledgement message was not received.
- the client requests the reconfiguration of the Ul according to the information brought by the request for reconfiguration.
- This reconfiguration means e.g. that the network instance changes the message format or the software version for the status message and sends the status message again to the client. This possibility allows to save time and makes the synchronization process fast compared to the prior art.
- the client comprises a Visual Voicemail (WM) client.
- WM Visual Voicemail
- the present invention is usable with known services such as WM. To ensue e.g. that any subscriber of the WM service is informed if a new message is available the WM client must be synchronized with the WM network instance so that the present invention with the method for synchronization assures the efficiency of services such as WM.
- the invention further relates to a client using a short message system (SMS) in a mobile radio network, wherein communication between the client and a network instance comprises the transmission of a status message between the client and the network instance and the transmission of an acknowledgement message between the client and the network instance.
- SMS short message system
- the client disposes of predefined error case procedures. By these error case procedures it is possible to exchange the necessary information for the SMS message exchange (e.g. user interface attributes) between client and network instance. Furthermore it is advantageously possible to transmit the acknowledgement message using the application layer.
- the application layer it is possible to use the client according to the present invention in applications like MMS, FTP or HTTP.
- the client comprises a synchronization function, wherein the client comprises a user interface, wherein the synchronization function is usable to manually request the
- the client requests the reconfiguration of the Ul according to the information brought by the request for reconfiguration.
- the subscriber is able to request reconfiguration of the Ul to assure that synchronization is possible. So it is avoidable that the subscriber must wait until the reconfiguration is executed by the network instance.
- the subscriber is able to initiate the synchronization process which is especially advantageous for example if the subscriber puts the SIM card out of a terminal and back into the terminal.
- the invention further relates to a system using a short message system in a mobile radio network, wherein the system comprises a client and a network instance, wherein communication between the client and the network instance comprises a status message between the client and the network instance and an acknowledgement message between the client and the network instance.
- the SMS communication even if an error in the SMS communication between client and network instance during the synchronization process occurs. Furthermore it is advantageously possible to transmit the acknowledgement message using the application layer.
- the application layer it is possible to use the system according to the present invention in applications like MMS, FTP or HTTP.
- the invention further relates to a program comprising a computer readable program code and a computer program product comprising a computer readable program code for controlling a client using a short message system in a mobile radio network, wherein communication between the client and a network instance comprises a status message between the client and the network instance and an acknowledgement message between the client and the network instance.
- Figure 1 shows schematically a cell of a mobile radio network.
- Figure 2 shows schematically an exchange of information between a network instance and a client according to a first embodiment of the present invention.
- Figure 3 shows schematically an exchange of information between a network instance and a client according to a second embodiment of the present invention.
- Figure 4 shows schematically an exchange of information between a network instance and a client according to a third embodiment of the present invention.
- Figure 5 shows schematically a block diagram of a client algorithm.
- Figure 6 shows schematically a block diagram of a network instance algorithm.
- Figure 7 shows schematically a block diagram of a network instance algorithm.
- FIG. 1 shows schematically a cell 100 of a mobile radio network.
- the mobile radio network comprises a core network 101 with a network instance 102 (in the following also called server) and a multitude of base stations, one thereof, a base station 103 is connected to a client 104.
- the client 104 is a WM client and the network instance 102 is a WM network instance.
- Visual Voicemail is the process of adding a visual aspect to phone voicemail such as allowing
- voicemails are converted to text by use of advanced speech recognition software. These voicemails are sent e.g. via SMS to the WM client so it allows better management of voicemail messages and saves time filtering spam.
- FIG. 2 shows schematically an exchange of information between the network instance 102 and the client 104 according to a first embodiment of the present invention.
- This synchronization process occurs if for example a subscriber of a WM service inserts a SIM card into a terminal.
- the client 104 sends a first client status message 200 (in the following also called status message) to the network instance 02.
- this first client status message 200 the client 104 sends information that are necessary for the synchronization process i.e. user interface attributes for the communication via SMS messages.
- the network instance 102 sends a network instance acknowledgement message (in the following also called acknowledgement message) 201 to the client 104.
- a network instance acknowledgement message in the following also called acknowledgement message
- the network instance acknowledgement message 201 comprises the information for the client 104 about the user interface attributes for the communication via SMS messages. If the client 104 accepts this information then the synchronization process is successful. This synchronization process by an acknowledgement message is generic and is usable in any cases when the synchronization of the client 104 is assured by using the SMS message exchange. As a security feature it is possible that the network instance acknowledgement message 201 comprises a second keyword 202 to differentiate between the network instance acknowledgment message 201 and a status message so that errors are avoidable.
- This first embodiment is the basic principle of the present invention.
- the synchronization according to the present invention is assured by sending the acknowledgement message from the server to the client.
- This acknowledgement message is related to the status message so that the client realizes that the status message has not only reached the server but furthermore that the content of the status message was correctly interpreted by the network instance.
- This interpretation comprises that the network instance understands the status message as a
- the present invention allows the network instance to realize that the status message has not only reached the client but furthermore that the content of the status message was correctly interpreted by the client.
- FIG. 3 shows schematically an exchange of information between the network instance 102 and the client 104 according to a second embodiment of the present invention.
- This synchronization process occurs for example if the following error case occurs.
- a non WM subscriber also called not provisioned for client type 1 or type 2 inserts a SIM card into a terminal and installs a WM client type 1 on the terminal.
- the WM client type 1 sends a first client status message 200 to the network instance 102.
- the WM network instance rejects the first client status message 200 because the WM client type 1 is not provisioned yet.
- the network instance 102 sends a first network instance status message 300 (in the following also called status message) using WM client type 2 to the client 104 using client type 1.
- the first network instance status message 300 is rejected by the client 104 and no client acknowledgement message (in the following also called acknowledgement message) is sent back from the client 104 to the network instance 102.
- the network instance 102 sends a second network instance status message (in the fllowing also called further status message) 301 using client type 1 to the client 104.
- the client 104 uses client type 1 the client 104 sends the client
- the client acknowledgement message 302 and a status message the client acknowledgement message 302 comprises for example a first keyword 303.
- acknowledgement message 302 also comprises the User Interface attributes for the communication via SMS messages.
- FIG. 4 shows schematically an exchange of information between the network instance 102 and the client 104 according to a third embodiment of the present invention.
- the client 104 does not receive the network instance acknowledgement message 201 from the network instance 102 the client 104 sends a second client status message (in the following also called status message) 400 to the network instance 102.
- the network instance 102 sends the network instance acknowledgement message 201 to the client 104.
- the network instance acknowledgement message 201 comprises the information for the client 104 about the User Interface attributes for the communication via SMS messages. If the client 104 accepts this information then the synchronization process is successful.
- FIG. 5 shows schematically a block diagram of a client algorithm that is possible to use if a method according to the present invention is implemented into the client 104.
- the first client status message 200 is generated.
- an acknowledgement SMS timer is reset. The acknowledgement SMS timer is necessary because the client 104 should not wait longer than a predetermined waiting time for the network instance acknowledgement message 201.
- a SMS generation retry counter is updated. The SMS generation retry counter is necessary because the client 104 should not send more than a predetermined amount of client status messages.
- the client 104 is waiting for the network instance acknowledgement message 201.
- the client 104 decides if the client 104 received the network instance acknowledgement message 201 or not. If the client 104 received the network instance acknowledgement message 201 the client algorithm comes to the end 507. In this case the synchronization procedure is successful. If the client 104 did not receive the network instance acknowledgement message 201 and the acknowledgement SMS timer has exceeded the predetermined waiting time then in block 505 the client 104 decides if the SMS generation retry counter has exceeded the predetermined amount of status messages or not. If the SMS generation retry counter has exceeded then in block 506 the client 104 is set into the synchronization failure status and the algorithm comes to the end 507. In this case the
- SMS generation retry counter has not exceeded in block 500 a second client status message 400 is generated and the client algorithm is repeated. The client algorithm is repeated until either the client 104 is synchronized or the client 104 is set into the synchronization failure status.
- FIG. 6 shows schematically a block diagram of a network instance algorithm that is possible to use if a method according to the present invention is implemented into the network instance 102.
- the first network instance status message 300 is generated.
- a network instance acknowledgement SMS timer is reset.
- the network instance acknowledgement SMS timer is implemented because the network instance 102 should not wait longer than a network instance predetermined waiting time for the client acknowledgement message 302.
- a network instance SMS generation retry counter is updated.
- the network instance SMS generation retry counter is necessary because the network instance 102 should not send more than a predetermined amount of network instance status messages.
- the network instance 102 is waiting for the client acknowledgement message 302.
- the network instance 102 decides if the network instance 102 received the client acknowledgement message 302 or not. If the network instance 102 received the client acknowledgement message 302 the network instance algorithm comes to the end 607. In this case the synchronization procedure is successful. If the network instance 102 did not receive the client acknowledgement message 302 and the network instance acknowledgement SMS timer has exceeded the network instance predetermined waiting time then in block 605 the network instance 02 decides if the network instance SMS generation retry counter has exceeded the predetermined amount of network instance status messages or not. If the network instance SMS generation retry counter has exceeded then in block 606 the network instance 102 starts a Ul version reconfiguration process (also called client type reconfiguration process). In this case the synchronization is not
- a second network instance status message 301 is generated and the network instance algorithm is repeated.
- the network instance algorithm is repeated until either the network instance 102 is synchronized or the Ul version reconfiguration process is started.
- FIG. 7 shows schematically a block diagram of a network instance algorithm in the case that the Ul version reconfiguration process is started (also called client type reconfiguration process).
- the Ul version reconfiguration process is started.
- the Ul version is set to the next Ul version.
- the Ul version is set to the next Ul version.
- the first network instance status message 300 is sent to the client 104.
- 703 is decided if the client acknowledgement message 302 is received or not. If the client acknowledgement message 302 is received then the Ul version reconfiguration process comes to the end 706. If the client acknowledgement message 302 is not received then in block 704 is decided if all Ul versions are checked out. If all Ul versions are checked out then in block 705 the client 104 is set into the version- failure status and the Ul version reconfiguration process comes to the end 706. In this case the synchronization has failed. If not all Ul versions are checked out then in block 701 the Ul version is set to the next Ul version and the version reconfiguration process is started again. The version reconfiguration process is repeated until either the client 104 is synchronized or the client 104 is set into the version-failure status.
- the subscriber is able to manually initiate the transmission of the first client status message 200 to the network instance 102.
- This is possible by using a synchronization function that is implemented in the client 104. If this synchronization function is used the synchronization procedure begins.
- the synchronization function is realizable as a button to manually press by the subscriber or as a software button implemented in the client software. This leads to the advantage that the subscriber is able to initiate the synchronization procedure and it is not necessary that the subscriber waits until the customer relationship management (CRM) initiates the synchronization procedure.
- CRM customer relationship management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Human Computer Interaction (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention porte sur une méthode, un client, un système et un programme informatique de communication utilisant dans un réseau radio mobile, un SMS pour communiquer entre un client (104) et une instance (102) de réseau, la synchronisation consistant à transmettre un message d'état (200) entre le client (104) et l'instance (102) de réseau et à transmettre un message d'AR (202) entre le client (104) et l'instance (102) de réseau.
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US25159509P | 2009-10-14 | 2009-10-14 | |
US61/251,595 | 2009-10-14 | ||
EP09012989.1 | 2009-10-14 | ||
EP09012989 | 2009-10-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011045009A1 true WO2011045009A1 (fr) | 2011-04-21 |
Family
ID=41611374
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2010/006182 WO2011045009A1 (fr) | 2009-10-14 | 2010-10-11 | Mécanisme d'ar d'un message d'état par sms |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2011045009A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9560497B2 (en) | 2014-05-02 | 2017-01-31 | Telecommunication Systems, Inc. | Multi-segment short message with a read acknowledgment request |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6449622B1 (en) * | 1999-03-08 | 2002-09-10 | Starfish Software, Inc. | System and methods for synchronizing datasets when dataset changes may be received out of order |
WO2002071219A2 (fr) * | 2001-03-07 | 2002-09-12 | Matchtip Limited | Systeme de stockage de donnees |
US20030045311A1 (en) * | 2001-08-30 | 2003-03-06 | Tapani Larikka | Message transfer from a source device via a mobile terminal device to a third device and data synchronization between terminal devices |
US20070207785A1 (en) * | 2003-07-14 | 2007-09-06 | Saurav Chatterjee | Integration of enterprise voicemail in mobile systems |
US20080085728A1 (en) | 2006-10-05 | 2008-04-10 | Verizon Services Corp. | Short message service (sms) data transfer |
US20080132257A1 (en) * | 2006-12-05 | 2008-06-05 | Kenny Fok | Methods and apparaus for requesting wireless communication device performance data and providing the data in optimal file size |
US20090154663A1 (en) * | 2007-12-13 | 2009-06-18 | Verizon Corporate Resources Group Llc | Self-provisioning, notification, retrieval, and submission of visual voice mail |
EP2076070A1 (fr) * | 2007-12-24 | 2009-07-01 | Qualcomm Incorporated | Fourniture d'un service de messages courts CDMA transparent à l'aide de dispositifs mobiles non-CDMA, de cartes à puce et de réseaux |
US20090203389A1 (en) * | 2008-02-07 | 2009-08-13 | Syncplanet Llc | Systems and methods for synchronizing information using short message services and email services |
GB2460346A (en) * | 2008-05-30 | 2009-12-02 | Vodafone Plc | Managing data delivery according to data type and origin |
EP2184897A1 (fr) * | 2007-08-02 | 2010-05-12 | Huawei Technologies Co., Ltd. | Procédé, appareil et système pour rapporter l'état de transmission |
-
2010
- 2010-10-11 WO PCT/EP2010/006182 patent/WO2011045009A1/fr active Application Filing
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6449622B1 (en) * | 1999-03-08 | 2002-09-10 | Starfish Software, Inc. | System and methods for synchronizing datasets when dataset changes may be received out of order |
WO2002071219A2 (fr) * | 2001-03-07 | 2002-09-12 | Matchtip Limited | Systeme de stockage de donnees |
US20030045311A1 (en) * | 2001-08-30 | 2003-03-06 | Tapani Larikka | Message transfer from a source device via a mobile terminal device to a third device and data synchronization between terminal devices |
US20070207785A1 (en) * | 2003-07-14 | 2007-09-06 | Saurav Chatterjee | Integration of enterprise voicemail in mobile systems |
US20080085728A1 (en) | 2006-10-05 | 2008-04-10 | Verizon Services Corp. | Short message service (sms) data transfer |
US20080132257A1 (en) * | 2006-12-05 | 2008-06-05 | Kenny Fok | Methods and apparaus for requesting wireless communication device performance data and providing the data in optimal file size |
EP2184897A1 (fr) * | 2007-08-02 | 2010-05-12 | Huawei Technologies Co., Ltd. | Procédé, appareil et système pour rapporter l'état de transmission |
US20090154663A1 (en) * | 2007-12-13 | 2009-06-18 | Verizon Corporate Resources Group Llc | Self-provisioning, notification, retrieval, and submission of visual voice mail |
EP2076070A1 (fr) * | 2007-12-24 | 2009-07-01 | Qualcomm Incorporated | Fourniture d'un service de messages courts CDMA transparent à l'aide de dispositifs mobiles non-CDMA, de cartes à puce et de réseaux |
US20090203389A1 (en) * | 2008-02-07 | 2009-08-13 | Syncplanet Llc | Systems and methods for synchronizing information using short message services and email services |
GB2460346A (en) * | 2008-05-30 | 2009-12-02 | Vodafone Plc | Managing data delivery according to data type and origin |
Non-Patent Citations (1)
Title |
---|
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Technical realization of Short Message Service (SMS) (3GPP TS 23.040 version 8.5.0 Release 8)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, no. V8.5.0, 1 June 2009 (2009-06-01), XP014044518 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9560497B2 (en) | 2014-05-02 | 2017-01-31 | Telecommunication Systems, Inc. | Multi-segment short message with a read acknowledgment request |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100677497B1 (ko) | 단말기의 중복 통보 메시지 처리 방법 | |
EP1954086B1 (fr) | Carte (U)SIM en mode serveur et méthode de communication avec client | |
CN101355524B (zh) | 一种消息处理方法、系统、服务器和终端 | |
US6895005B1 (en) | Business logic server for facilitating the transmission of a data download to a mobile wireless unit | |
US8260954B2 (en) | Process for communication between a device running a mobile device platform and a server over the air, as well as related system | |
CN100512314C (zh) | 一种优化Push通告消息的方法 | |
CN101814971A (zh) | 一种手机文件传输方法 | |
WO2002019664A2 (fr) | Procede et appareil pour l'acces multiple a distance a des modules d'identite d'abonnes | |
JP2012533926A (ja) | 電話番号の検証のための方法および装置 | |
EP2611226A1 (fr) | Procédé et système de traitement pour démarrage par liaison radio | |
US20100185741A1 (en) | Method for delivering cpm message and server thereof | |
US20100146075A1 (en) | Mobile radio communication device and method of managing connectivity status for the same | |
JP2004104780A (ja) | 公衆移動通信ネットワークと連動する私設無線ネットワークのショートメッセージサービスサーバ及びサービス方法 | |
EP2227066A1 (fr) | Procédé et dispositif de mise en uvre de service de messagerie | |
CN104270302B (zh) | 在线订单的传送系统及传送方法 | |
EP1648185B1 (fr) | Procédé pour la transmission de messages de télécharge en lot | |
US7835758B2 (en) | Method and mobile apparatus of receiving a multimedia message | |
US7194551B1 (en) | System and method for downloading data to a mobile wireless unit using over-the-air parameter administration services | |
WO2012062051A1 (fr) | Procédé et système pour la distribution de messages multimédia | |
WO2011045009A1 (fr) | Mécanisme d'ar d'un message d'état par sms | |
EP2542010B1 (fr) | Procédé pour l'accès d'un client de messagerie électronique mobile à un serveur, et terminal mobile | |
CN102598735B (zh) | 建立应用会话的方法、设备和相应通知 | |
KR20040022364A (ko) | 멀티미디어 메시징 서비스에서 멀티미디어 메시지를분할하여 올리는 방법 및 시스템 | |
EP2491701A1 (fr) | Mécanisme de détection de client automatique | |
CN101267458A (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: 10779687 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: 10779687 Country of ref document: EP Kind code of ref document: A1 |