WO2017190328A1

WO2017190328A1 - Terminal, short message service centre and information synchronization method

Info

Publication number: WO2017190328A1
Application number: PCT/CN2016/081173
Authority: WO
Inventors: 刘恒进; 蔺波; 甄斌
Original assignee: 华为技术有限公司
Priority date: 2016-05-05
Filing date: 2016-05-05
Publication date: 2017-11-09

Abstract

The present application relates to the field of mobile communications, in particular to an information synchronization method, and a short message service centre and a terminal for realizing the method. The method comprises: a short message service centre receiving a first short message from a first terminal, wherein the first short message comprises an identifier of an object and state information about the object; and the short message service centre sending a second short message to a second terminal associated with the first terminal, wherein the second short message comprises the identifier of the object and the state information about the object, and the second short message is used for updating a state of the object on the second terminal. The method is convenient and has low implementation complexity by using a short message to synchronize information on different terminals.

Description

Terminal, short message service center and method for information synchronization

Technical field

The present invention relates to the field of communications, and in particular, to a terminal, a short message service center, and a method for synchronizing information.

Background technique

With the development of diversity of mobile terminals and the widespread use of wearable devices, one user can have multiple terminals at the same time. In order to enhance the user experience, information needs to be synchronized between multiple terminals. Generally, information synchronization between multiple terminals can be classified into originating synchronization and receiving synchronization. For example, a scene of originating synchronization is: user A owns terminal B and terminal C. After user A dials out the call using terminal B, the terminal B can display the dialed out of the terminal B. phone. For another example, a scenario in which the receiving end is synchronized is: the user A' owns the terminal B' and the terminal C'. When the terminal C' reads a short message, the terminal C' can display the above read short message in the terminal B'. A short message that has been read on terminal C'.

At present, in order to synchronize information between multiple terminals, the multiple terminals need to be produced by the same manufacturer, or the same account needs to be used on the multiple terminals, or multiple terminals need to be directly connected to the WIFI. Therefore, the current synchronization scheme has more restrictions.

Summary of the invention

The embodiments of the present invention provide a terminal, a short message service center, and a method for synchronizing information, so as to more conveniently synchronize information on multiple terminals.

In a first aspect, an embodiment of the present invention provides a method for synchronizing information. The method comprises:

The short message service center receives the first short message from the first terminal, where the first short message includes an identifier of the object and status information of the object; the short message service center sends a second short message to the second terminal associated with the first terminal, The second short message includes an identifier of the object and status information of the object, The second short message is used to update the state of the object on the second terminal.

The above method utilizes a short message to update the state of the corresponding object on different terminals, so that synchronization of multiple terminals can be conveniently implemented. Compared with the prior art, there are fewer restrictions on the terminal, and the implementation complexity is lower.

Those skilled in the art will appreciate that the above method is described from the perspective of a short message service center.

As an optional design, the first terminal may be a user equipment, the second terminal may be a wearable device, or the first terminal is a wearable device, and the second terminal is a user equipment. With this solution, different terminals can be designed and produced by different vendors without having to make a private synchronization protocol.

As an optional design, the short message service center may obtain the association relationship between the first terminal and the second terminal from other network elements such as the home subscriber server or the home location register, or may obtain the first terminal from the short message service center. The relationship with the second terminal. The association relationship may be pre-configured, or may be reported by the first terminal or the second terminal. Optionally, the reporting manner may be that the short message is used for reporting, for example, the first terminal or the second terminal sends a third short message to the short message service center, where the third short message includes the association between the first terminal and the second terminal. For example, the first terminal may carry the identifier of the second terminal in the first short message to indicate that the first terminal and the second terminal have an association relationship. By reporting the association relationship by means of short messages, the association relationship between different terminals can be dynamically adjusted, and the real-time performance is good.

As an optional design, the short message service center may store the above association relationship in the short message service center, or may be stored in the home user server or the home location register. Storing the foregoing association relationship on the home subscriber server or the home location register may facilitate other short message service centers to acquire the association relationship.

As an optional design, the short message service center may send a message to the home subscriber server or the home location register to indicate that the association relationship between the first terminal and the second terminal is saved, so that the home subscriber server or the home location register stores the foregoing. connection relation.

As an optional design, the second short message may be a short message of a state synchronization type. This type is a new type of short message. This type of short message does not have to be displayed to the user, can Processed in the background of the terminal to protect the user experience. Optionally, the first short message may also be a short message of a state synchronization type.

As an optional design, the above object may be an object of a phone class or an object of a message class. This application does not limit this. By setting different objects on the terminal, it is possible to synchronize various objects on the terminal.

In a second aspect, an embodiment of the present invention provides another method for synchronizing information. The method includes:

The first terminal acquires the status information of the object, and the first terminal sends a first short message to the short message service center, where the first short message includes the identifier of the object and status information of the object, where the first short message is used to update the first The state of the object on the second terminal, the first terminal and the second terminal are associated with each other.

In the second aspect, related possible designs may refer to various alternative designs in the first aspect, and are not described herein.

Those skilled in the art will appreciate that the method of the second aspect is described from the perspective of the first terminal.

In a third aspect, an embodiment of the present invention provides another method for information synchronization. The method includes:

The second terminal receives the second short message, where the second short message includes the identifier of the object and the status information of the object, and the second terminal updates the status of the object on the second terminal to the status indicated by the status information.

In the third aspect, related possible designs may refer to various alternative designs in the first aspect, and are not described herein.

Those skilled in the art will appreciate that the method of the third aspect is described from the perspective of the second terminal.

In a fourth aspect, an embodiment of the present invention provides a short message service center. The short message service center has a function of realizing the behavior of the short message service center in the method of the first aspect, the second aspect or the third aspect. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the short message service center includes a processor and a communication unit, and the processor is configured to support the base station to perform a corresponding function in the above method. The communication unit is configured to support communication between the short message service center and the terminal, and send or receive the short message involved in the foregoing method to the terminal. The short message service center may further include a memory, the storage The device is coupled to the processor and stores the necessary program instructions and data of the short message service center.

In a fifth aspect, an embodiment of the present invention provides a terminal. The terminal has a function of implementing the first terminal behavior of the first aspect or the second aspect method. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The modules can be software and/or hardware.

In a possible design, the structure of the terminal includes a transceiver and a processor, and the transceiver is configured to support the terminal to send a first short message to the short message service center, where the processor can be used to acquire state information of the object and control the The transceiver sends the first short message to the short message service center.

In a sixth aspect, an embodiment of the present invention provides another terminal. The terminal has a function of implementing the behavior of the second terminal in the first aspect or the method of the third aspect. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The modules can be software and/or hardware.

In a possible design, the structure of the terminal includes a transceiver and a processor, the transceiver is configured to support the terminal to receive the second short message, and the processor is configured to control the transceiver to receive the second short message and The status of the object on the second terminal is updated to the status indicated by the status information of the object included in the second short message. The second short message may be received from the short message service center or may be received from the first terminal.

In a seventh aspect, an embodiment of the present invention provides a communication system, where the system includes the foregoing first terminal and a second terminal.

In an eighth aspect, the embodiment of the present invention provides another communication system, where the system includes the foregoing short message service center and the first terminal or the second terminal.

In a ninth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the short message service center, which includes a program designed to execute the above aspects.

According to a tenth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the first terminal, which includes a program designed to perform the above aspects.

In an eleventh aspect, an embodiment of the present invention provides a computer storage medium, configured to be stored as Computer software instructions for the second terminal, comprising programs designed to perform the above aspects.

The embodiments of the present invention use short messages to synchronize information of different terminals. Compared with the prior art, the restrictions on the terminals are less, and the existing network devices can be reasonably utilized for synchronization, which is convenient.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. One of ordinary skill in the art can also obtain other drawings based on these drawings without paying for inventive labor.

FIG. 1 is a schematic diagram of a wireless network according to an embodiment of the present invention;

2 is a schematic flowchart of an information synchronization method according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a short message server according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.

detailed description

FIG. 1 is a schematic diagram of a wireless network according to an embodiment of the present invention. As shown in FIG. 1, the wireless network includes a terminal A, a short message service center (referred to as SC, service center, which may also be referred to as a short message service center), a terminal B, and a terminal B'. The terminal can exchange information with the short message service center through the wireless access network. For convenience of explanation, FIG. 1 omits the relevant network element of the radio access network. The technical solution described in the embodiments of the present invention can be applied to a wireless network adopting various wireless communication technologies. For example, a network using access technology such as code division multiple access, frequency division multiple access, time division multiple access, orthogonal frequency division multiple access, single carrier frequency division multiple access, and various subsequent evolved networks, such as 4.5G (generation) ) Network, 5G network, Internet of Things, etc. In the present application, the terms "network", "wireless network", "wireless communication network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning.

This application uses the network shown in FIG. 1 as an example to describe the technical solution. It should be noted that the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the embodiments of the present invention. The technical solutions of the present invention are not limited to the technical solutions provided by the embodiments of the present invention. It is known to those skilled in the art that the technical solutions provided by the embodiments of the present invention are similar to the following as the evolution of the network architecture and the emergence of new service scenarios. Technical issues are equally applicable.

The terminals involved in the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to wireless modems, and various forms of user devices (user Equipment, UE), mobile station (MS), terminal equipment (TE), etc. For convenience of description, in the present application, the above mentioned devices are collectively referred to as terminals. In Fig. 1, there is an association relationship between the terminal B and the terminal B'. For example, terminal A can be a mobile phone and terminal B' can be a smart watch associated with terminal B. For another example, terminal B may be a mobile phone, and terminal B' may be a tablet computer having some or all of the mobile communication functions associated with the terminal B. For ease of explanation, FIG. 1 only lists two related associated terminals, and three or more terminals may be associated in an actual network. As an alternative embodiment, the terminal typically includes a processor, a memory, and a transceiver. The memory may be used to store a program for controlling and managing the behavior of the terminal, and the processor may be configured to execute a program in the memory to control and manage the behavior of the terminal, and the transceiver is configured to receive or send information.

The short message service center involved in the present application is a network element entity having the functions of receiving a short message from a terminal, sending a short message to the terminal, storing a short message, and receiving a short message report. As an optional implementation manner, the network element entity may include a processor, a memory, and a communication circuit. The memory may store a program related to short message processing, and the processor may execute the above program to implement a related function of short message processing, and the communication circuit may receive or send a short message. In the present application, short messages and short messages are sometimes used instead, and those skilled in the art can understand the correct meaning according to the context.

The terminal can access an external network through a radio access network (RAN) and a core network (CN). With the development of technology, terminals can also directly access external networks through wireless access networks.

In the present application, an object is an information object suitable for synchronization between different terminals. Exemplarily, the object can be perceived by the user on the terminal by means of information recording, and can also be used by other The mode is perceived by the application on the terminal, which is not limited in this application. There can be multiple objects on the terminal, such as a phone class object, or a short message class object. A phone-related object can be considered a phone class object, for example, a phone number, an incoming call, or an active call can be considered a phone class object. The object associated with the short message may be a short message class object, for example, a short message, a multimedia message, and a voice message. Those skilled in the art can understand that the types of objects on the terminal are not limited to the above examples. According to different division criteria, there may be more kinds of objects, such as reminder objects, image class objects, and the like.

In the present application, the status information is information for embodying the state of the object. Exemplarily, for a phone number, the status information may be an incoming call record, an outgoing call record, or a total duration of the call; for an incoming call, the status information may be the time of the call, whether the call has been reminded, or whether it has been returned. Dialing information; for a short message, the status information may be whether it has been read, whether the short message has been reminded, whether the short message has been replied, and the like. The status information of the present application may be determined according to actual business needs, and the specific scope and content thereof are not limited in this application.

It can be understood by those skilled in the art that the terminal receiving or transmitting the short message in the present application refers to the terminal transmitting the short message through the wireless communication technology, and the specific implementation of the present application is not limited.

Those skilled in the art will appreciate that in this application, the meaning of the update may be understood broadly, for example, may be the insertion, modification, or deletion of information.

In the present application, the state of the update object is sometimes expressed as the state of the synchronization object. In the present application, "update" and "synchronization" are used interchangeably, and those skilled in the art can understand the correct meaning according to the meaning of the context.

Those skilled in the art can understand that in the present application, the home subscriber server or home location register can be used to store user related information, such as subscription data and the like.

Those skilled in the art can understand that in the present application, the short message of the state synchronization type refers to a short message mainly used for state synchronization of an object. Optionally, the receiving and sending of such short messages is transparent to the user, that is, can be understood as not being perceived by the user.

Those skilled in the art can understand that the association relationship between the two terminals may be a direct association relationship or may be an indirect association relationship. For example, a record in which "terminal A is associated with terminal B" in the network can be understood as a direct relationship between terminal A and terminal B. For another example, a record in which "terminal A is associated with user D" and "terminal B is associated with user D" in the network can be understood as an indirect association relationship between terminal A and terminal B.

Those skilled in the art will appreciate that the identity of the terminal is a type of information that can be used to identify the terminal. Exemplarily, the identifier of the terminal includes, but is not limited to, a phone number of the terminal, an address of the terminal, a temporary identifier assigned by the network to the terminal, or an international mobile subscriber identity of the terminal.

Those skilled in the art will appreciate that the identification of an object is a type of information that can be used to identify the object. Illustratively, the identity of an object includes, but is not limited to, a globally unique temporary identity assigned to the object, or the name of the object, and the like.

For a clearer description of the technical solution of the embodiment of the present invention, the embodiment of the present invention uses a short message class object as an example for description. It should be noted that the technical solution of the present invention is also applicable to other types of objects.

FIG. 2 is a schematic diagram of information synchronization according to an embodiment of the present invention.

210: Terminal A sends a short message M to the SC.

Optionally, after part 210, the SC may send a message report to the terminal A for the short message M, which is used to inform the terminal A whether the short message M is successfully received by the SC.

220: The SC sends a short message M to the terminal B.

Optionally, after part 220, the terminal B may send a message report to the SC for the short message M, where the message report is used to inform the SC that the short message M is successfully received by the terminal B.

230: The SC sends a short message M to the terminal B'.

The 220 and 230 parts are in no particular order.

Optionally, the association relationship between the terminal B and the terminal B' may be stored on the SC, or the SC may acquire the association relationship between the terminal B and the terminal B' from the home subscriber server or the home location register. After the SC learns that the terminal B and the terminal B' have an association relationship, the short message M sent to the terminal B can be sent. Send to terminal B'.

Alternatively, after the 230 portion, the terminal B' may send a message report to the SC for the short message M, which is used to inform the SC that the short message M was successfully received by the terminal B'.

Alternatively, the 230 portion can be replaced by a 230' portion.

230': Terminal B sends a short message M to terminal B'.

The short message M from the terminal A is received by both the terminal B and the terminal B' described above.

When the user reads the short message M at the terminal B, the status of the short message M on the terminal B is updated to read. In order to synchronize the state of the short message M on the terminal B' with the state of the short message M on the terminal B, the embodiment of the present invention provides the following solution. It can be understood that the object that needs to be synchronized here is the short message M.

240: The terminal B sends a first short message to the SC.

The first short message includes the identifier of the short message M and the status information “read” of the short message M.

250: The SC sends a second short message to the terminal B'.

The second short message includes the identifier of the short message M and the status information “read” of the short message M.

As an optional implementation manner, the association relationship between the terminal B and the terminal B' may be stored on the SC. As another alternative implementation manner, the SC may acquire the association relationship between the terminal B and the terminal B' from the home subscriber server or the home location register.

Through the 240 and 250 parts, the terminal B' can obtain the latest status information of the short message M, so that the status update of the short message M on the terminal B' can be realized.

260: Terminal B' updates the status of short message M to "read".

According to the foregoing solution provided by the embodiment of the present invention, the state of the short message M on the terminal B and the terminal B' can be conveniently synchronized by using a short message. Compared with the prior art, the terminal B and the terminal B' may not be produced by the same manufacturer, the terminal B and the terminal B' may not need to provide a private interface, and the terminal B and the terminal B' may log in without using the same account, and the terminal B And terminal B' may not have to be in the same Under the WLAN, the solution of the embodiment of the present invention greatly simplifies the synchronization behavior of information on the terminal B and the terminal B'.

As an optional implementation manner, the SC can obtain the association relationship between the terminal B and the terminal B' in the following manners.

An optional manner is that the terminal B sends a third short message to the SC, where the third short message includes the association relationship between the terminal B and the terminal B'. After receiving the third short message, the SC may save the association relationship on the SC.

In another optional manner, the terminal B sends the association relationship between the terminal B and the terminal B' to the SC through the first short message of the 140 part, and the SC saves the association relationship after receiving the first short message. That is to say, the first short message includes the identifier of the short message M, the status information "read" of the short message M, and the association relationship between the terminal B and the terminal B'. The terminal B may add the identifier of the terminal B' to the first short message to indicate that the terminal B and the terminal B' have an association relationship, that is, the first short message includes the identifier of the short message M, and the status information of the short message M has been Read "and the identity of terminal B'.

Another alternative is that the SC acquires the association relationship between the terminal B and the terminal B' from the home subscriber server or the home location register. Specifically, the SC requests the home subscriber server or the home location register to acquire information of the terminal associated with the terminal B, and the home subscriber server or the home location register returns the information of the terminal B' to the SC.

Another alternative is to pre-configure the association between the terminal B and the terminal B' on the SC.

As an optional implementation manner, after the SC acquires the association relationship between the terminal B and the terminal B′, if the association relationship does not exist on the SC, the SC may save the association relationship on the SC, so that the AS does not need to go to other The network element obtains the association relationship. A person skilled in the art can understand that after the SC saves the association relationship, a periodic timer can be set for the association relationship, which is beneficial for the SC to obtain the latest information about the terminal associated with the terminal B.

As an optional implementation manner, after the SC acquires the association relationship between the terminal B and the terminal B', the association relationship may be saved in the home subscriber server or the home location register. Specifically, the SC may send to the home subscriber server or the home location register to indicate to save the terminal B and A message of the association relationship of the terminal B'.

As an alternative embodiment, the type of the second short message sent to the terminal B' may be a state synchronization type. When the terminal B' receives the short message of this type, the user may not be prompted, which can enhance the user experience.

As an optional implementation manner, the type of the first short message sent by the terminal B may be a state synchronization type. After the terminal B sends the short message of the type, the user does not need to perceive the sending of the message, which can enhance the user experience.

As an optional implementation manner, in order to implement the short message of the state synchronization type, a new short message type may be defined on the existing short message type technology, that is, the short message transmission layer (SM-TL, short) Message transfer layer) defines a new type of protocol data unit (PDU). For example, a PDU of the type SMS-SUMBIT-STATUS-UPDATE may be added, and the TP-MTI (transfer protocol-message type indicator) field may be represented by a reserved field "11". Those skilled in the art can understand that the TP-MTI field can also be extended to 3 bits to represent more PDU types. The PDU of the SMS-SUMBIT-STATUS-UPDATE type may include a TP-MTI field, a transport center-timestamp (TP-SCTS) field, and a short message state (TP-MS, transfer protocol-message status). ) field. The TP-SCTS can be used as the identifier of the short message M, and the TP-MS is a new field, which can be used to indicate the state of the short message M. For related content related to the short message in the prior art, reference may be made to the content of the protocol ETSI TS 123 040 v 13.0.0 (2016-03), especially the content of the ninth chapter (protocol and protocol architecture), which is not described herein.

As an optional implementation, the following parts may also be included before the 240 part:

231: Terminal B sends an update request message to terminal B'.

The update request message includes the identifier of the short message M and the status information “read” of the short message M.

Optionally, the update request message may be the first short message or the second short message. This way Terminal B's existing short message processing functionality can be utilized without having to specifically add a proprietary synchronization protocol.

Optionally, the terminal B may send the update request message by using a short-range communication technology (for example, Bluetooth technology, radio frequency identification technology, Zigbee technology, etc.).

232: Terminal B' sends an update response message to terminal B.

The update response message indicates that the update failed.

As an optional implementation, in the 230 part, the technical solution of the embodiment of the present invention may also be used to synchronize the short message M to the terminal B'. Here, the synchronized object is the inbox. E.g:

230-1: Terminal B sends a fourth short message to the SC.

The fourth short message includes an identifier of the inbox, and status information of the inbox, the status information of the inbox includes a short message M, and further status information of the inbox may further include a short message M. Related Information.

230-2: The SC sends a fifth short message to the terminal B'.

The fifth short message includes the identifier of the inbox and the status information of the inbox. After receiving the fifth short message, the terminal B' knows that the synchronized object is the inbox of the short message according to the identifier of the inbox, and according to the status information of the inbox, the acquiring needs to add a short message in the inbox. M.

Exemplarily, the fourth short message and the fifth short message may also be the short message of the above-mentioned SMS-SUMBIT-STATUS-UPDATE type, which is not described here.

Through 230-1 and 230-2, the terminal B' can complete the synchronization of the inbox of the short message with the terminal B by means of a short message, which is convenient and efficient.

It should be understood by those skilled in the art that the description of the method for synchronizing information provided by the embodiment of the present invention is different from the perspective of different network element entities. For example, from the perspective of a short message service center, the method can include 240 portions and 250 portions; from the perspective of terminal B, the method can include 240 portions; from the perspective of terminal B', the method can include 250 portions and 260 portions.

In order to implement the method shown in FIG. 2, an embodiment of the present invention provides a short message service center and a terminal.

FIG. 3 is a schematic structural diagram of a short message service center according to an embodiment of the present invention. The short message service center may be the short message service center (SC) involved in FIGS. 1 and 2.

As shown in FIG. 3, the short message service center includes a controller/processor 301, a memory 302, and a communication unit 303. The controller/processor 301 is configured to perform various functions related to short message processing. The communication unit 303 is configured to receive and send short messages, and may also be used to interact with other network entities, such as a home subscriber server or a home location register. Illustratively, communication unit 303 can include one or more ports to connect with external network elements. The communication unit 303 can be controlled by the controller/processor 301. The controller/processor 301 and the communication unit 303 can also be used in a method of performing information synchronization provided by an embodiment of the present invention, such as the process related to the SC in FIG. 2 and/or other processes for the techniques described in this application. . For example, the controller/processor 301 can control the communication unit 303 to perform the functions of the first short message sent by the SC receiving terminal B in the 240 part and the 250 part and the second short message sent to the terminal B', for example, in the 230-1 part. The fourth short message sent by the terminal B is received, and the fifth short message is sent to the terminal B' in 230-2. The memory 302 is used to store program codes and data of the short message service center. The controller/processor 301 can implement control of the communication unit 303 by executing the above-described program code.

It will be appreciated that Figure 3 only shows a simplified design of the short message service center. In practical applications, the short message service center may include any number of processors, controllers, memories, communication units, etc., and all short message service centers that can implement the present invention are within the scope of the present invention.

FIG. 4 is a simplified schematic diagram showing a possible design structure of a terminal provided by an embodiment of the present invention. The terminal relates to the terminal B or the terminal B' in Figs. 1 and 2. The terminal includes a transmitter 401, a receiver 402, a controller/processor 403, a memory 404, and a modem processor 405.

The transmitter 401 conditions (e.g., analog conversion, filtering, amplifying, upconverting, etc.) the output samples and generates an uplink transmission signal that is transmitted via an antenna to the base station in the above embodiment. In the downlink transmission, the antenna receives the downlink transmission signal transmitted by the base station in the above embodiment. Receiver 402 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples. In modem processor 405, encoder 406 receives the data and control information to be transmitted in the upstream transmission and processes (e.g., formats, codes, and interleaves) the data and control information. Modulator 407 further processes (e.g., symbol maps and modulates) the encoded data and control messages and provides For output sampling. Demodulator 409 processes (e.g., demodulates) the input samples and provides symbol estimates. The decoder 408 processes (e.g., deinterleaves and decodes) the symbol estimate and provides decoded data and signaling messages that are sent to the terminal. Encoder 406, modulator 407, demodulator 409, and decoder 408 may be implemented by a composite modem processor 405. These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems). It will be appreciated that the transmitter 401 and the receiver 402 can be integrated together, referred to as a transceiver. In other words, the transceiver can implement the functions of the transmitter 401 and the receiver 402.

As an optional design, the controller/processor 403 controls and manages the action of the terminal, and is used to perform the processing performed by the terminal B in the foregoing embodiment. For example, in the 240 part, the terminal B sends the first short message to the SC. For example, in the 231 part, the terminal B sends an update request message to the terminal B′, and in the 232 part, the terminal B receives the update response message sent by the terminal B′, and for example, in the part 230-1, the terminal B sends the fourth short message to the SC. . The memory 404 is used to store program codes and data for implementing the functions of the terminal B.

As another alternative design, the controller/processor 403 controls and manages the actions of the terminal for performing the processing by the terminal B' in the above embodiment. For example, terminal B' receives the second short message in portions 250 and 260, and terminal B' updates the state of the object (e.g., short message M) (e.g., updated to "read"). For another example, in the 231 part, the update request message sent by the terminal B is received, and in the 232 part, the update response message is sent to the terminal B. For another example, in the section 230-1, the fourth short message or the like is sent to the SC. The memory 404 is used to store program codes and data for implementing the functions of the terminal B'.

The controller/processor for performing the above-described terminal or base station functions of the present invention may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate array ( FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.

The steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions. The software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art. In the medium. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment. Of course, the processor and the storage medium may also reside in the device as discrete components.

Those skilled in the art will appreciate that in one or more examples described above, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

It will be understood by those of ordinary skill in the art that the drawings are only a schematic diagram of an embodiment, and the modules or processes in the drawings are not necessarily required to implement the invention.

The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. The scope of the protection, any modifications, equivalent substitutions, improvements, etc., which are made on the basis of the technical solutions of the present invention, are included in the scope of the present invention.

Claims

A method for synchronizing information, comprising:

The short message service center receives a first short message from the first terminal, where the first short message includes an identifier of the object and status information of the object;

The short message service center sends a second short message to the second terminal associated with the first terminal, where the second short message includes an identifier of the object and status information of the object, where the second short message is used. Updating the state of the object on the second terminal.
The method of claim 1 further comprising:

The short message service center acquires an association relationship between the first terminal and the second terminal from a home subscriber server, or a home location register, or the short message service center.
The method of claim 1 further comprising:

The short message service center receives a third short message, where the third short message is used to indicate an association relationship between the first terminal and the second terminal.
The method of claim 1, wherein the first short message further comprises an identification of the second terminal.
The method of claim 3 or 4, further comprising:

The short message service center stores the association relationship between the first terminal and the second terminal on the home subscriber server, or the home location register, or the short message service center.
A method according to any one of claims 1 to 5, wherein

The message type of the second short message is a state synchronization type.
A method according to any of claims 1-6, wherein

The object includes a phone class object or a short message class object.
A short message service center, comprising: a processor and a communication unit,

The communication unit is configured to receive a first short message, where the first short message includes an identifier of the icon and status information of the object;

The processor is configured to instruct the communication unit to send a second short message to the second terminal associated with the first terminal, where the second short message includes an identifier of the object and status information of the object, where the The second short message is used to update the state of the object on the second terminal.
A short message service center according to claim 8 wherein:

The processor is further configured to acquire, by the communication unit, an association relationship between the first terminal and the second terminal from a home subscriber server or a home location register, or is further configured to acquire the foregoing from the short message service center. The association relationship between the first terminal and the second terminal.
A short message service center according to claim 8 wherein:

The communication unit is further configured to receive a third short message, where the third short message is used to indicate an association relationship between the first terminal and the second terminal.
The short message service center according to claim 8, wherein the first short message further comprises an identifier of the second terminal.
A short message service center according to claim 10 or 11, wherein

The processor is further configured to save, by the communication unit, an association relationship between the first terminal and the second terminal in a home subscriber server or a home location register, or to save the location on the short message service center. The association relationship between the first terminal and the second terminal is described.
A short message service center according to any one of claims 8 to 12, characterized in that

The message type of the second short message is a state synchronization type.
A short message service center according to any one of claims 8 to 13, characterized in that

The object includes a phone class object or a short message class object.
A terminal, comprising:

a processor, configured to acquire state information of the object;

a transceiver, configured to send a first short message to the short message service center, where the first short message includes an identifier of the object and status information of the object, where the first short message is used to update the second terminal The state of the object, the terminal is associated with the second terminal.
The terminal according to claim 15, wherein the transceiver is further configured to:

Sending, to the second terminal, an update request message, where the update request message includes an identifier of the object and status information of the object, where the update request message is used to update a state of the object on the second terminal;

Receiving an update response message from the second terminal, the update response message indicating that the update failed.
A terminal according to claim 15 or 16, wherein

The first short message further includes an identifier of the second terminal.
A terminal according to any of claims 15-17, characterized in that

The object includes a phone class object or a short message class object.
A terminal, comprising:

a transceiver, configured to receive a second short message, where the second short message includes an identifier of the object and status information of the object;

a processor, configured to update a status of the object on the terminal to be indicated by the status information status.
The terminal according to claim 19, wherein the transceiver is further configured to:

Receiving an update request message from the first terminal, the update request message including an identifier of the object and status information of the object;

If the status of the object on the terminal is updated to the status indicated by the status information, an update response message is sent to the first terminal, where the update response message indicates that the update failed.
A terminal according to claim 19 or 20, characterized in that

The object includes a phone class object or a short message class object.
A terminal according to any one of claims 19 to 21, characterized in that

The terminal is a wearable device.