WO2010020120A1 - Method, device and system for synchronizing time - Google Patents

Abstract

A method for synchronizing time comprises the steps of: by a client, acquiring clock information; by the client, realizing the time synchronization with a server according to the clock information. A client comprises a clock information acquiring unit, for acquiring clock information; a clock management unit, for realizing the time synchronization with the server according to the clock information acquired by the clock information acquiring unit. A server comprises a clock providing unit, for acquiring clock information from any one of a network time protocol server, a mobile broadcast service server, a content server or a separate Global Position System module; a clock information sending unit, for sending the clock information provided by the clock providing unit to a client. A system for synchronizing time includes the server and the client.

Description

 Time synchronization method, device and system

 This application claims priority to Chinese Patent Application No. 200810210836.9, entitled "A Time Synchronization Method, Apparatus and System", filed on August 20, 2008, the entire contents of which are incorporated herein by reference. In the application.

Technical field

 The present invention relates to the field of communications, and in particular, to a time synchronization method, apparatus, and system.

Background technique

 The Mobile Broadcast Service (BCAST) is a concept of a mobile broadband digital broadcasting service proposed by the Open Mobile Alliance. In broadcasting, it includes a traditional one-to-many broadcasting method and multi-point transmission method, which is dedicated to business. Inventions such as discovery, electronic programming, business guidance, billing, content protection, etc., develop specific business engines and ensure that they are independent of the carrier layer. The entire BCAST system consists of a functional part, a protocol part, and a bearer network part.

 The Open Mobile Alliance standard stipulates that mobile video broadcast services must provide users with Service Guide (SG) information. The service guide provides the user with information about the broadcast content, including the channel name, program name, start time, end time, payment standard, etc. The user can perform program preview, service ordering and unsubscribing, and play the program according to relevant information provided in the service guide. Wait for the operation. The service guide information may be sent by the network side to all users registered at the broadcast service provider in a broadcast manner, or may be requested by the user to send the service guide information to the network side.

 In the prior art, the process of the user viewing the program through the service guide is: the content server sends the program information to the service guide server, where the program information includes a channel name, a program name, a start time, an end time, and the like; the service guide server is provided according to the content server. The program information generation service guide sends the generated service guide to the client; the client displays the service guide to the user, and the user selects the program to be watched according to the service guide; the client receives the program selected by the user according to the service guide.

In the process of implementing the present invention, the inventors have found that the above technical solutions have at least the following drawbacks: For systems that do not implement time synchronization, such as asynchronous Wideband Code Division Multiple Access (WCDMA) systems, clients Compared with the BCAST server time, the client accesses the program through the BCAST service guide, which will make it impossible for the user to watch the program at the correct time, thereby affecting the user experience. Summary of the invention

 The embodiment of the invention provides a time synchronization method, device and system. The technical solution provided by the embodiment of the invention can realize time synchronization between the client and the server, thereby realizing synchronization between the terminal and the server.

 The purpose of the embodiment of the present invention is achieved by the following technical solutions:

 A time synchronization method, including:

 The client obtains clock information;

 The client synchronizes with the server according to the above clock information.

 A client that includes:

 a clock information acquiring unit, configured to acquire clock information;

 The clock management unit is configured to synchronize with the server according to the clock information acquired by the clock information acquiring unit.

 A server, comprising:

 a clock providing unit, configured to obtain clock information from any one of a network time protocol server or a mobile broadcast service server or a content server or a separate global positioning system module;

 The clock information sending unit is configured to send the clock information provided by the clock providing unit to the client. A time synchronization system, including:

 a server, configured to obtain clock information from any one of a network time protocol server or a mobile broadcast service server or a content server or a separate global positioning system module, and send clock information to the client;

 The client is configured to obtain clock information, and synchronize with the foregoing server time according to the clock information.

 It can be seen from the above technical solution provided by the embodiment of the present invention that since the client obtains the clock information and synchronizes with the server according to the clock information, the time of the client can be synchronized with the time of the server, thereby enabling the user and the server. Time synchronization, which in turn enhances the user experience.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only Some embodiments of the present invention, for those of ordinary skill in the art, do not pay Other drawings can also be obtained from these drawings on the premise of inventive labor. 1 is a flow chart of a time synchronization method according to Embodiment 1 of the present invention;

 2 is a signaling diagram of a time synchronization method according to Embodiment 2 of the present invention;

 3 is a signaling diagram of a time synchronization method according to Embodiment 3 of the present invention;

 4 is a signaling diagram of a time synchronization method according to Embodiment 4 of the present invention;

 5 is a signaling diagram of a time synchronization method according to Embodiment 5 of the present invention;

 6 is a flowchart of a time synchronization method according to Embodiment 6 of the present invention;

 7 is a flowchart of a time synchronization method according to Embodiment 7 of the present invention;

 8 is a signaling diagram of a time synchronization method according to Embodiment 8 of the present invention;

 9 is a schematic diagram of a composition of a client according to an embodiment of the present invention;

 FIG. 10 is a schematic diagram showing the composition of a server according to an embodiment of the present invention; FIG.

 11 is a block diagram showing the composition of a time synchronization system according to an embodiment of the present invention;

 FIG. 12 is a schematic diagram of a NTP data format according to an embodiment of the present invention.

detailed description

 BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

 The embodiment of the invention provides a time synchronization method, device and system. The technical solution provided by the embodiment of the invention can realize time synchronization between the client and the server, thereby realizing synchronization between the terminal and the server.

 The above terminals include a client and a user. The client can be a device capable of implementing a mobile broadcast service, such as a mobile phone.

 Embodiment 1

 In this embodiment, the client obtains clock information and implements synchronization with the server time according to the clock information, so that the time of the client can be synchronized with the time of the server.

 A detailed description will be given below with reference to the accompanying drawings.

 Step 101: The client obtains clock information.

The client can obtain the clock information through the local underlying clock, or obtain the clock through the server. Information.

 Obtaining clock information through the local underlying clock may be a signaling message that the client acquires clock information in the mobile communication network.

 The clock information is obtained by the server, and the client sends a request to the server, and the client obtains the clock information sent by the server according to the request; or the clock information sent by the server periodically.

 The request sent by the client to the server may be a service guide acquisition request or a service guide update request, and the client obtains clock information by receiving a service guide containing the clock information. The request sent by the client to the server may also be a time synchronization request, and the client obtains the clock information sent by the server according to the time synchronization request. The time synchronization request may further include a keep update field, where the field indicates whether the client requests to keep the update, and the client obtains the updated clock information sent by the server after the client requests to keep updating according to the keep update field.

 The clock information sent by the client to the server periodically can obtain the clock information by acquiring any of the cell broadcast system message, the push message, and the unstructured supplementary data service message including the clock information. The client obtains the cell broadcast system message including the clock information, and the client may receive the media stream of the cell broadcast system, and extract the clock information from the media stream.

 Step 102: The client synchronizes with the server according to the clock information.

 The client synchronizes with the server according to the clock information. The client can replace the local clock information with the clock information based on the clock information, and provide the replaced clock information to the user, so that the time of the user and the server are synchronized.

 The client can synchronize the time with the server according to the clock information, and can also map the clock information and the local clock information to the client, and provide the mapped clock information to the user, so that the time of the user and the server are kept synchronized.

 In this embodiment, since the client obtains the clock information and synchronizes with the server according to the clock information, the time of the client can be synchronized with the time of the server, so that the time of the user and the server can be synchronized, thereby enhancing the user experience.

 Embodiment 1 is a general description of a method for implementing time synchronization with a server, and a corresponding embodiment is given below for different ways of acquiring clock information.

 Embodiment 2

This embodiment provides a client initiated service guide acquisition request or service guide update request. When the server sends the clock information along with the service guide to the client, the client and server time synchronization scheme is implemented. The basic idea is that in the interactive service guide, after the client initiates a service guide acquisition request or a service guide update request to the server, the server sends the clock information along with the service guide to the client.

 See Figure 2, the specific steps are as follows:

 Step 201: The client sends a service guide acquisition request or a service guide update request to the server; the client may initiate the request by using the request message, and the following is an example of a request message format:

 POST/HTTP/1.1

 Host: www.serviceGuide.com: 8080 Business Guide Server Domain Name and Port

Content-Type: application/xml message body type

 Content-Length: 182 message body length

 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Opera 7.10[en] User Information

 Date: Sun,20Jul200820:55:22GMT Date and time the request was initiated

 <?xml version="1.0" encoding="UTF-8"?>

 <SG Request>

 <type> sgdu + clock— NTP </tpye> Specifies the required response format <fragment_ID>www.example.com/ service/ 101 </fragment— ID > ID of the requested fragment

 </SGRequest >

 The above request message is composed of a message header and a message body. The header field includes the service guide server domain name and port, the message body type, the message body length, the client information, the request request date and time, and the like. The message body is an Extensible Markup Language (XML) document containing the content of the request, where "<type> sgdu + clock- NTP </tpye> " indicates that the request server responds to the Service Guide Delivery Unit (Service Guide Delivery). Unit, SGDU) and Network Time Protocol (NTP) time information, where "<fragment_ID>www.example.com/service/101 </fragment_ID>" indicates the requested service fragment, this fragment is encapsulated In the business guide transfer unit.

Step 202: The server sends a service guide acquisition response or a service guide update response to the client. After receiving the request, the server returns the service guide data and clock information of the response in the payload. The server responds with a request message with a status of "200 OK", and returns a response content according to the request message. The following message format is an example of a server response message.

 HTTP/1.1 200 0K

 Server: Apache/2.0.54 (Unix) Business Guide Server Information

 Content— Type: text/xml message body type

 Content— Length: 168 Message body length

 Date: Sun,20Jul200820:58:00GMT Date and time the message was sent

 <?xml version="1.0" encoding="UTF-8"?>

 <SG Response>

 <sgdu>

 Requested Service Guide Fragment (encapsulated in the Service Guide Transfer Unit)

</sgdu>

 <clock_NTP>

 NTP time information

 </clock_NTP>

 </SG Response> The server returns the requested service guide fragment and NTP time information according to the request message sent by the client, and the information is carried in the message body. The NTP time information consists of an NTP header and four timestamps, which are 48 bytes in total. See Figure 12 for the NTP data format.

 Figure 12 shows the data items in the NT data format as follows:

 1) The NTP header, which is 16 bytes, is: LI: leap year indicator (2bit); VN: version number (3bit); Stratum: layer (8bit); Mode: mode (3bit); Poll Interval: query interval

(8bit); Precision: precision (8bit); Root delay: root delay (32bit); Root Dispersion: root difference (32bit); Reference Identifier: reference identifier (32bit).

 2) Four timestamps, accounting for 32 bytes, are: Reference Timestamp: Reference timestamp (64bit); Originate Timestamp: Original timestamp (64bit); Receive Timestamp: Receive timestamp (64bit); Transmit Timestamp: Transmit Timestamp (64bit).

3) Authenticator: Authenticator, optional, (96bit). NTP data is usually encapsulated in XML or binary format. Taking the XML form as an example, the NTP data items can be placed in the HTTP response message body as a child element of the element 3⁄41001^-NTP>. After receiving the response message, the client parses these elements, reconstructs the NTP data, and performs time synchronization processing.

 The clock information can also be used as a shard in the service guide. That is, a new clock information fragment is added to the service guide. Like other service guide shards, the shard also has a unique identifier. The user can obtain the synchronization time by requesting to acquire or update the clock information fragment.

 The above message format and the way to carry the data are only examples, and can also be implemented by other messages and carrying methods, and the ideas involved are consistent. In addition, in the 200OK header field of the server response, the "Date" field indicates the date and time when the server sent the message. For the case where the time precision is not high, the client can also synchronize the time with the server as the synchronization time.

 Step 203: After obtaining the clock information, the client synchronizes with the server time according to the clock information.

 According to the clock information to achieve synchronization with the server, there are two ways:

 Manner 1: After the client extracts the clock information, the local clock information is replaced by the new clock information constructed according to the clock information. When the BCAST user needs time information, the client local clock can be referred to.

 Manner 2: The client maps the clock information to the local clock information, does not modify the local time of the client, and maps the client local time to the time required by the BCAST user for use by the BCAST user.

 In this embodiment, the client sends a service guide acquisition request or a service guide update request to the server, receives a service guide that is sent by the server and includes the clock information, and synchronizes with the server according to the clock information, thereby enabling the terminal to synchronize with the server time and enhancing the time. user experience.

 The second embodiment is a method for the client to send a request to the server to implement time synchronization. The following describes an embodiment in which the server sends clock information to the client through the cell broadcast system.

 Embodiment 3

This embodiment provides an implementation scheme for sending clock information to a client through a cell broadcast system. The basic idea is that the server periodically sends clock information to the client periodically or periodically, and the client synchronizes after receiving the clock information. This feature is characterized by the fact that there is no need to distinguish between clients, and all clients in the cell range can receive clock information. Referring to Figure 3, the specific process is as follows:

 Step 301: The server periodically forwards the clock information to the cell broadcast system.

 The server typically periodically forwards time information to the cell broadcast system.

 Step 302: The cell broadcast system encapsulates the clock information in a cell broadcast message for broadcasting. If the clock information is too large, the clock information may be compressed before being encapsulated, or the clock message may be split into several cell broadcast message numbers. Issued.

 Step 303: The cell that the client listens to the broadcast clock information speaks, and parses the clock information after receiving the cell broadcast information.

 The client can only listen to the cell broadcast channel of the broadcast clock information if the relevant channel parameters are configured. The client obtains the address of the clock information through the cured cell broadcast address, or through device management, configuration mode, client preset, or manual configuration.

 The foregoing is a method in which the clock information is sent by the cell broadcast, and other methods may be adopted. For example, in the push message mode, the clock information is carried in the form of XML in the push message body. Or carrying clock information in the payload of the cell broadcast system message. The clock information can also be delivered in an unstructured supplementary data service.

 Step 304 is the same as step 203, and details are not described herein again.

 In this embodiment, the client obtains the clock information by acquiring the cell broadcast system message including the clock information, and synchronizes with the server according to the clock information. Further, the client obtains the clock information by acquiring the unstructured supplementary data service message including the clock information. Synchronizing with the server according to the clock information enables the time of the client and the server to be synchronized, thereby synchronizing the time between the terminal and the server, and enhancing the user experience.

 The third embodiment describes a method for implementing time synchronization of sending clock information to a client through a cell broadcast system. An embodiment of sending clock information to a client by means of a push mode is described below.

 Embodiment 4

 This embodiment provides a method for implementing time synchronization of issuing clock information to a client by means of a push. The basic idea is to encapsulate the clock information in the form of XML or binary in the push message body, and deliver the message to the client through the push message.

 Referring to Figure 4, the specific process is as follows:

Step 401: The server hands the clock information to the push proxy gateway. Step 402: The push proxy gateway encapsulates the clock information in the relevant push message and sends the clock information to the client.

 An example of a push message carrying clock information is given below:

 MESSAGE sip:user2@domain.com SIP/2.0

 Via: SIP/2.0/TCP userlpc.domain.com; branch=z9hG4bK776sgdkse Max-Forwards: 70

 P-Asserted-Identity: "John Doe" <sip:john.doe@homel .net>

 From: sip:user@PushSenderAgent.domain.com; tag=49583

 To: sip:user@PushReceiverAgent.domain.com

 Accept-Contact: *; +g.oma.pusheventapp=" mms.ua"

 Call-ID: asd88asd77a@1.2.3.4

 CSeq: 1 MESSAGE

 Content-Type: text/plain

 Content-Length: 18

 2 Push Receiver Agent returns a 200 OK to Push Sender Agent

 SIP/2.0 200 OK

 Via: SIP/2.0/TCP proxy.domain.com; branch=z9hG4bK 123 dsghds; received=192.0.2.1

 Via: SIP/2.0/TCP userlpc.domain.com; branch=z9hG4bK776sgdkse;

 Received=1.2.3.4

 From: sip:user@PushReceiverAgent.domain.com; tag=49394

 To: sip:user@ PushsenderAgent.domain.com; tag=ab8asdasd9

 Call-ID: asd88asd77a@1.2.3.4

 CSeq: 1 MESSAGE

 Content-Length: 152

 Clock information

The clock information is carried in the above message body in XML form or in binary form. The header field of the message "To: sip: user@PushsenderAgent.domain.com;tag=ab8asdasd9" indicates the destination address of the push message, which can be either a client address or a group address. Step 403: After receiving the push message, the client parses the clock information for processing. Step 404 after the clock information is parsed is the same as step 203, and is not mentioned here.

 In the global mobile communication system, the unstructured supplementary data service system can also be used to provide clock information, which can be implemented by means of unstructured supplementary data service notification initiated by the network side, and the clock information is carried in the notification message.

 In this embodiment, the client obtains the push message sent by the push proxy gateway to obtain the clock information, and synchronizes with the server according to the clock information, which can synchronize the time between the client and the server, thereby synchronizing the time between the terminal and the server, and enhancing the time. user experience.

 The fourth embodiment describes a method for implementing time synchronization of sending clock information to a client by means of a push. The following describes an embodiment in which a client requests clock information through an interactive network to implement time synchronization.

 Embodiment 5

 This embodiment provides a method for a client to request clock information through an interactive network to implement time synchronization. The main idea is that the client actively initiates the request information, requesting the clock information, and the server returns the clock information according to the request.

 Referring to FIG. 5, the flow of this embodiment is as follows:

 Step 501: The client initiates a time synchronization request to the server.

 The time synchronization request is used to request the clock information. The format of the request message is as follows:

 GET/example.com/time.html HTTP/ 1.1

 Host: www.clock_Server.com:8080

 Connection: close

 User-agent: Mozilla/4.0

 Keep-update: true

 A keep-update field may be extended in the above request message to indicate whether the server is required to periodically send the updated clock to the client after the request. If the value of this field is "true", the server periodically sends the updated clock information to the client after receiving the client request message.

There are multiple ways to initiate a request message, which can be set according to actual needs. For example, the user automatically initiates a request each time the client is opened, or the user can manually initiate a request. Step 502: The server returns clock information according to the client request.

 After receiving the request initiated by the client, the server carries clock information, such as NTP data, in

In response to the 200 OK message, an example of the message format is as follows:

 HTTP/1.1 200 0K

 Date: Thu, 13 Oct 2007 03:17:33 GMT

 S erver: Apache/2.0.54 (Unix)

 Last— Modified: Mon, 22 Jun 2007 09; 23; 24 GMT

 Content— Length: 6821

 Content ~~ Type: text/xml

 (NTP data...)

 Clock information, such as NTP data, is carried in the body of the message in binary form or as an XML document.

 Step 503: If the server requests the server to keep updating, that is, "keep-update=true", the server periodically sends updated clock information to the client.

 Step 504: The client synchronizes with the server according to the clock information.

 This step is the same as step 203 and will not be mentioned here.

 In this embodiment, the client obtains clock information through a separate request command, synchronizes with the server according to the clock information, and is independent of the service guide architecture, so that the terminal and the server can be time synchronized without relying on the service guide architecture, thereby enhancing the user experience.

 Embodiment 5 provides a method for a client to request clock information through an interactive network to implement time synchronization. An embodiment in which a client extracts clock information from a broadcast program stream to implement time synchronization is described below.

 Embodiment 6

 This embodiment provides a method for a client to extract time information from a broadcast program stream to implement time synchronization. The basic idea is that the media stream or the program stream contains a time stamp, and the client extracts the time information in the media stream in the process of receiving the media stream for use by the BCAST user.

 See Figure 6, the specific process is as follows:

 Step 601: The client starts to receive the media stream of the multimedia broadcast system.

Media streams can be transmitted through different media transmission channels, such as digital video broadcasting systems. Streams, mobile interactive networks are usually transmitted using real-time transport protocols or real-time transport control protocols. Step 602: The client extracts the broadcast time from the media stream.

 The media stream contains time information for media control, system synchronization, etc. For example, the timestamp in the real-time transport protocol is usually used for synchronization of audio and video streams and fast forward and backward control, so the client can extract the time information.

 Step 603: The client processes the extracted time and converts it into a format required by the BCAST user.

 The client processes the extracted time as needed.

 Step 604: Provide the converted time to the BCAST user for use.

 BCAST can use this time for different applications, such as display to the user, or when the user performs some time-related operations as the reference time.

 In this embodiment, the client receives the media stream, extracts the clock information from the media stream, and converts it into a format required by the user, and uses the converted time for the BCAST user to synchronize the time of the BCAST user with the server, thereby enhancing the user body.

 Embodiment 6 describes a method in which a client extracts time information from a broadcast program stream to implement time synchronization. An embodiment of synchronizing a client using a network synchronization time in a synchronous mobile communication network is described below.

 Example 7

 This embodiment provides a method for synchronizing a client by using a network synchronization time to synchronize time in a synchronous mobile communication network. In systems such as time division synchronous code division multiple access and code division multiple access 2000, the base stations are synchronized by the global positioning system time. The basic idea of this embodiment is to extract the time information of the signaling layer of the transport network for use by the BCAST user.

 See Figure 7, the specific process is:

 Step 701: The client obtains clock information through the local underlying clock.

 For example, in the synchronous mobile communication network, time information of the base station may be carried in the signaling, and the client obtains the foregoing signaling information.

 Step 702: The client corrects the local time according to the time to achieve synchronization with the base station.

In this embodiment, the client obtains clock information by acquiring a signaling message including clock information in the mobile communication network, and corrects the local time according to the clock information to achieve time synchronization with the mobile communication network. The client and server time synchronization is achieved, which enhances the user experience.

 The seventh embodiment describes a method for synchronizing a client by using a network synchronization time to realize time synchronization. The following describes an embodiment in which a client obtains clock information through an unstructured supplementary data service request to implement time synchronization.

 Example eight

 This embodiment describes a method for a client to obtain clock information through an unstructured supplementary data service request to implement time synchronization. The main idea is that the client actively initiates an unstructured supplementary data service request, and obtains clock information, and the server requests the server according to the request. The message returns clock information.

 Referring to Figure 8, the flow of this embodiment is:

 Step 801: The client initiates an unstructured supplementary data service request to the server, where the request message includes a clock request.

 The request message can have multiple initiation methods, which can be set according to actual needs. For example, the user automatically initiates a request each time the client opens the client, or the user can manually initiate a request.

 Step 802: The server carries the clock information of the server in the response message according to the request message, and sends the message to the client.

 If the server does not have clock information, the server requests the NTP server to obtain the NTP time information, and the NTP server returns the NTP time according to the request.

 Step 803 is the same as step 203, and details are not described herein again.

 In this embodiment, the client sends the unstructured supplementary data service request including the clock request to the server, obtains the clock information sent by the server according to the request, and synchronizes with the server according to the clock information, so that the time between the client and the server can be synchronized. In turn, the time of the terminal and the server are synchronized, and the user experience is enhanced.

 The above embodiment illustrates the time synchronization method, and the related apparatus is explained below.

 See Figure 9, a client, including:

 The clock information acquiring unit 901 is configured to acquire clock information.

 The clock management unit 902 is configured to perform time synchronization with the server according to the clock information acquired by the clock information acquiring unit 901.

 The above client may further include:

a request sending unit, configured to send a request to the server; The clock information obtaining unit 901 is configured to acquire clock information sent by the server according to the foregoing request. The request sending unit may be further configured to send a service guide obtaining request or a service guide update request to the server. The clock information acquiring unit 901 may further include:

 a service guide processing unit, configured to receive a service guide sent by the server, where the service guide includes clock information;

 And an extracting unit, configured to extract a clock message from the foregoing service guide received by the service guide processing unit. The client may be used to implement the foregoing time synchronization method, but is not limited to implementing the method.

 See Figure 10, a server that includes:

 a clock providing unit 1001, configured to obtain clock information from any one of a network time protocol server, a mobile broadcast service server, a content server, and a separate global positioning system module;

 The clock information transmitting unit 1002 is configured to send the foregoing clock information provided by the clock providing unit 1001 to the client.

 The above server may be used to implement the above time synchronization method, but is not limited to implementing the method.

 The related apparatus for realizing the time synchronization method is explained above, and a time synchronization system is explained below. Referring to FIG. 11, a time synchronization system includes:

 The server 1101 is configured to obtain clock information from any one of a network time protocol server or a mobile broadcast service server or a content server or a separate global positioning system module, and send clock information to the client 1102;

 The client 1102 is configured to obtain clock information, and implement time synchronization with the server 1101 according to the foregoing clock information.

 In the embodiment of the present invention, since the client obtains the clock information and synchronizes with the server according to the clock information, the time of the client can be synchronized with the time of the server, so that the time of the user and the server can be synchronized, thereby enhancing the user experience.

 Further, the client obtains clock information through the local underlying clock or the server, and synchronizes with the server according to the clock information, so that the time of the client and the time of the server are synchronized, thereby synchronizing the time of the user and the server, thereby enhancing The user experience.

Further, the client acquisition server obtains clock information by using any one of a cell broadcast system message, a push message, and an unstructured supplementary data service message including clock information, and according to the clock The information is synchronized with the server time, which can synchronize the time of the client with the time of the server, so that the time of the user and the server can be synchronized, thereby enhancing the user experience.

 Further, the client obtains clock information by sending a request to the server, and synchronizes with the server according to the clock information, so that the time of the client and the time of the server are synchronized, thereby synchronizing the time of the user and the server, thereby enhancing the time. user experience.

 It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium. , including the following steps:

 The client obtains clock information;

 The client synchronizes with the server according to the above clock information.

 The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

 The time synchronization method, device and system provided by the embodiments of the present invention are described in detail. The description of the above embodiments is only for helping to understand the method and the idea of the present invention. Meanwhile, for those skilled in the art, The present invention is not limited by the scope of the present invention.

Claims

Rights request

 A time synchronization method, comprising:

 The client obtains clock information;

 The client synchronizes with the server according to the clock information.

 The time synchronization method according to claim 1, wherein the information obtained by the client is specifically:

 The client obtains clock information through a local underlying clock.

 The time synchronization method according to claim 2, wherein the client obtains clock information through the local bottom clock:

 The client acquires a signaling message in a mobile communication network, where the signaling message includes a clock message

The time synchronization method according to claim 1, wherein the information obtained by the client is specifically:

 The client obtains clock information through a server.

 The time synchronization method according to claim 4, wherein the client obtains clock information through the server:

 The client obtains clock information that is sent by the server at a time.

 The time synchronization method according to claim 5, wherein the clock information periodically sent by the client acquisition server is specifically:

 The client obtains a cell broadcast system message or a push message or an unstructured supplementary data service message containing clock information.

 The time synchronization method according to claim 4, wherein before the client obtains the clock information through the server, the method further includes:

 The client sends a request to the server;

 The i1⁄2 client obtains the clock information through the server as follows:

 The i1⁄2 client obtains clock information sent by the server according to the request.

 8. The time synchronization method according to claim 7, wherein:

The sending, by the client, the request to the server is: the client sends a service guide acquisition request or a service guide update request to the server; The acquiring, by the client, the clock information sent by the server according to the request is: the client receives the service guide sent by the server, and the service guide includes clock information.

 9. The time synchronization method according to claim 7, wherein:

 The sending, by the client, the request to the server is: the client sends a time synchronization request to the server;

 The acquiring, by the client, the clock information sent by the server according to the request is: the client acquiring clock information sent by the server according to the time synchronization request.

 10. The time synchronization method according to claim 9, wherein the time synchronization request further comprises a keep update field;

 After the client obtains the clock information sent by the server according to the time synchronization request, the method further includes:

 The client obtains updated clock information sent by the server according to the keep update field, and the updated clock information is sent by the server after determining that the client requests to keep updating according to the keep update field.

 11. The time synchronization method according to claim 7, wherein:

 The sending, by the client, the request to the server is: the client sending an unstructured supplementary data service request to the server;

 The acquiring, by the client, the clock information sent by the server according to the request is: the client acquiring clock information sent by the server according to the unstructured supplementary data service request.

 The time synchronization method according to claim 1, wherein the acquiring the clock information by the client is specifically:

 The client obtains clock information through a multimedia broadcast program stream.

 The time synchronization method according to any one of claims 1 to 12, wherein the client time synchronization with the server according to the clock information is specifically:

 The client constructs new clock information according to the clock information to replace the local clock information, and provides the replaced clock information to the user.

 The time synchronization method according to any one of claims 1 to 12, wherein the client time synchronization with the server according to the clock information is specifically:

The client maps the clock information with local clock information, and maps the clock signal Information is provided to the user.

 15. A client, characterized in that:

 a clock information acquiring unit, configured to acquire clock information;

 The clock management unit is configured to implement time synchronization with the server according to the clock information acquired by the clock information acquiring unit.

 The client according to claim 15, further comprising:

 a request sending unit, configured to send a request to the server;

 The clock information obtaining unit is configured to acquire clock information sent by the server according to the request.

 The client according to claim 16, wherein the request sending unit is configured to send a service guide acquisition request or a service guide update request to the server;

 The clock information acquiring unit includes:

 a service guide processing unit, configured to receive a service guide sent by the server, where the service guide includes clock information;

 An extracting unit, configured to extract a clock letter from a service guide received by the service guide processing unit

18. A server, comprising:

 a clock providing unit, configured to obtain clock information from any one of a network time protocol server or a mobile broadcast service server or a content server or a separate global positioning system module;

 a clock information sending unit, configured to send, to the client, a clock signal provided by the clock providing unit

19. A time synchronization system, comprising:

 a server, configured to obtain clock information from any one of a network time protocol server or a mobile broadcast service server or a content server or a separate global positioning system module, and send clock information to the client;

 The client is configured to obtain clock information, and synchronize with the server time according to the clock information.