(19)
(11)EP 3 461 063 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
29.07.2020 Bulletin 2020/31

(21)Application number: 17798574.4

(22)Date of filing:  12.04.2017
(51)International Patent Classification (IPC): 
H04L 12/24(2006.01)
H04L 9/32(2006.01)
(86)International application number:
PCT/CN2017/080191
(87)International publication number:
WO 2017/198010 (23.11.2017 Gazette  2017/47)

(54)

METHOD AND DEVICE FOR DATA VERSION COMPARISON BETWEEN TRANS-TIME ZONE STATIONS

VERFAHREN UND VORRICHTUNG ZUM VERGLEICH VON DATENVERSIONEN ZWISCHEN TRANSZEITZONENSTATIONEN

PROCÉDÉ ET DISPOSITIF DE COMPARAISON DE VERSIONS DE DONNÉES ENTRE STATIONS À TRAVERS DES FUSEAUX HORAIRES


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 17.05.2016 CN 201610326461

(43)Date of publication of application:
27.03.2019 Bulletin 2019/13

(73)Proprietor: Alibaba Group Holding Limited
Grand Cayman (KY)

(72)Inventor:
  • JIANG, Zhen
    Hangzhou Zhejiang 311121 (CN)

(74)Representative: Conroy, John 
Fish & Richardson P.C. Highlight Business Towers Mies-van-der-Rohe-Straße 8
80807 München
80807 München (DE)


(56)References cited: : 
WO-A2-2004/056138
CN-A- 103 186 570
US-A1- 2012 131 185
US-B1- 8 543 675
CN-A- 101 854 615
CN-A- 103 226 603
US-A1- 2014 047 131
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    TECHNICAL FIELD



    [0001] The present application relates to the communications field, and in particular, to a method and device for data version comparison between trans-time zone sites.

    BACKGROUND



    [0002] In internationalized services, because different service sites may be respectively deployed in different countries, a central site is usually used to aggregate service data generated by international sites.

    [0003] However, in an existing data aggregation solution, the service data of the international sites is usually considered to be mutually independent, and the central site usually aggregates the service data of the international sites independently without considering that trans-time zone sites can include the same data as other sites.

    [0004] In such case, when the central site aggregates the same service data on the trans-time zone sites, if the service data has different versions on the trans-time zone sites, when the central site aggregates the service data in a time sequence of sending the service data to a central node, versions of the aggregated service data may be disordered, and consequently, an actual service need cannot be satisfied.

    [0005] WO 2004/056138 describes methods and apparatus for providing consistency in Short Message Service (SMS) timestamp formatting (UTC or non-UTC) for mobile communication devices. In one example, a method involves receiving an SMS message intended for a mobile communication device; identifying whether the SMS message has timestamp data formatted in Coordinated Universal Time (UTC) format or non-UTC format; converting the timestamp data from the UTC format to a non-UTC time format based on an identification that the SMS message has timestamp data formatted in the UTC format; failing to convert the timestamp data to a non-UTC time format based on an identification that the SMS message has timestamp data in the non-UTC format; and causing the SMS message to be sent to the mobile communication device. Further described are methods and apparatus for converting SMS message time stamp information so that terminating Mobile Stations (MS) will display the correct time. It is desired to introduce techniques in such a way to provide for backwards-compatibility. With a backwards-compatible solution, appropriate operation occurs when both a prior version MS operates with an upgraded Message Center (MC) and a newer version MS operates with an MC that has not been upgraded. It is further desired to provide methods and apparatus for consistent SMS message time stamp formatting so that the time of SMS messages stored on a Removable User Identity Module (R-UIM) can be appropriately displayed when the R-UIM is inserted into different Mobile Equipment (ME). WO 2004/056138 does not disclose or suggest several trans-time zone sites modifying the same target data and generating time stamps upon modification, performing data version comparison based on the time stamps, and determining a latest version of the target data based on the comparison.

    SUMMARY



    [0006] The present application provides a method for data version comparison between trans-time zone sites, and the method includes the following: receiving time stamps generated when trans-time zone sites modify the same target data, and the modified target data; when the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, separately performing, based on a time zone of a central site, time zone conversion on the time stamps submitted by the trans-time zone sites; and performing, based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, data version comparison on the target data submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites.

    [0007] Optionally, the method further includes the following: when the time stamps are generated by the trans-time zone sites based on the time zone of the central site, performing, based on the time stamps submitted by the trans-time zone sites, the data version comparison on the target data submitted by the trans-time zone sites.

    [0008] Optionally, the separately performing, based on a time zone of a central site, time zone conversion on the time stamps submitted by the trans-time zone sites includes the following: querying the time zones of the trans-time zone sites; and separately performing, based on a conversion relationship between a time zone of each trans-time zone site and a time zone of a central site, the time zone conversion on the time stamps submitted by the trans-time zone sites.

    [0009] Optionally, the performing, based on the time stamps submitted by the trans-time zone sites, the data version comparison on the target data submitted by the trans-time zone sites includes the following: comparing values of the time stamps submitted by the trans-time zone sites; and determining that target data submitted by a trans-time zone site with the largest time stamp value is the target data of the latest version.

    [0010] Optionally, the method further includes the following: when the target data of the latest version in the target data submitted by the trans-time zone sites is determined, updating locally stored original target data by using the target data of the latest version.

    [0011] The present application further provides a device for data version comparison between trans-time zone sites, and the device includes the following: a receiving module, configured to receive time stamps generated when trans-time zone sites modify the same target data, and the modified target data; a conversion module, configured to separately perform time zone conversion on the time stamps submitted by the trans-time zone sites based on a time zone of a central site, when the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites; and a comparison module, configured to perform, based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, data version comparison on the target data submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites.

    [0012] Optionally, the comparison module is further configured to perform the data version comparison on the target data submitted by the trans-time zone sites, based on the time stamps submitted by the trans-time zone sites, when the time stamps are generated by the trans-time zone sites based on the time zone of the central site.

    [0013] Optionally, the conversion module is configured to query the time zones of the trans-time zone sites; and separately perform, based on a conversion relationship between a time zone of each trans-time zone site and a time zone of a central site, the time zone conversion on the time stamps submitted by the trans-time zone sites.

    [0014] Optionally, the comparison module is configured to compare values of the time stamps submitted by the trans-time zone sites; and determine that target data submitted by a trans-time zone site with the largest time stamp value is the target data of the latest version.

    [0015] Optionally, the device further includes the following: an update module, configured to update locally stored original target data by using the target data of the latest version, when the target data of the latest version in the target data submitted by the trans-time zone sites is determined.

    [0016] In the present application, based on time stamps generated when trans-time zone sites modify the same target data and the target data after the modification, when the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, time zone conversion is separately performed on the time stamps submitted by the trans-time zone sites based on the time zone of a central site; and data version comparison is performed on the target data submitted by the trans-time zone sites based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites. Therefore, when aggregating service data of the trans-time zone sites and the trans-time zone sites modify the same target data, a central node can perform, the time zone conversion on the submitted time stamps based on a time zone of the central node, so that the central node can use time stamps with a unified time zone to perform the version comparison on the modified service data submitted by the trans-time zone sites. Therefore, after the trans-time zone sites modify the same service data, the modified service data submitted by the trans-time zone sites is aggregated in a version sequence without causing disordered service data versions.

    BRIEF DESCRIPTION OF DRAWINGS



    [0017] 

    FIG. 1 is a flowchart illustrating a method for data version comparison between trans-time zone sites, according to an implementation of the present application;

    FIG. 2 is a diagram illustrating an application scenario of data version comparison between trans-time zone sites, according to an implementation of the present application;

    FIG. 3 is a logical block diagram illustrating a device for data version comparison between trans-time zone sites, according to an implementation of the present application; and

    FIG. 4 is a hardware structural diagram illustrating a server including a device for data version comparison between trans-time zone sites, according to an implementation of the present application.


    DESCRIPTION OF IMPLEMENTATIONS



    [0018] In internationalized services, to implement centralized management and control on services of international sites on a central site, the central site usually needs to aggregate service data of the international sites to the central site for centralized storage.

    [0019] However, in actual applications, the services of the international sites are usually independently operated, and the service data on the international sites is usually not interworked. Therefore, in such case, a central node considers the service data of the international sites is mutually independent, and aggregates the service data of the international sites without considering that the international sites can include the same data.

    [0020] In an existing data aggregation solution, the central node usually asynchronously aggregates the service data of the international sites. For example, after modifying certain service data, the international sites can asynchronously submit the modified service data to the central node in a message form for aggregation.

    [0021] However, because the central node aggregates service data of the international sites asynchronously, it can result in disordered data versions. As a result, the central node may incorrectly replace data of the latest version with data of an earlier version. For example, when the international sites submit the service data of the latest version to the central node, a packet including the service data of the earlier version may be sent to the central node after a packet including the service data of the latest version because of a network delay, etc., but the central node usually aggregates data in a sequence of sending the data to the central node. Consequently, versions of aggregated data may be disordered during data aggregation by the central node.

    [0022] In the existing data aggregation solution, to prevent disordered data versions, after any international site modifies certain service data, the international site generates a time stamp based on a time zone of the international site, and then asynchronously submits the time stamp and the modified service data to the central node. When aggregating the service data of the international site, the central node can perform data version comparison based on the time stamp, determine service data of the latest version, and then complete aggregation.

    [0023] However, with deepening of a service internationalization process, service interworking between the international sites is increasingly popularized, and increasingly more service operators support data sharing by different international sites. Therefore, in the existing data aggregation solution, an actual service need cannot be satisfied if the central node aggregates the service data of the international sites without considering that the international sites include the same data.

    [0024] A method for data version comparison between trans-time zone sites is provided in the present disclosure. Time stamps generated when trans-time zone sites modify the same target data and the modified target data are received. When the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, time zone conversion is separately performed on the time stamps submitted by the trans-time zone sites based on a time zone of a central site. Moreover, data version comparison is performed on the target data submitted by the trans-time zone sites based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites. Therefore, when aggregating service data of the trans-time zone sites, a central node can perform, based on a time zone of the central node, the time zone conversion on the time stamps submitted when the trans-time zone sites modify the same target data, so that the central node can use time stamps with a unified time zone to perform the version comparison on the modified service data submitted by the trans-time zone sites. Therefore, after the trans-time zone sites modify the same service data, the modified service data submitted by the trans-time zone sites is aggregated in a version sequence without causing disordered service data versions.

    [0025] With reference to specific application scenarios, the following describes the present application by using specific implementations.

    [0026] Referring to FIG. 1, FIG. 1 illustrates a method for data version comparison between trans-time zone sites, according to an implementation of the present application. The method is applied to the server of a central node, and can include the following steps.

    [0027] Step 101: Receive time stamps generated when trans-time zone sites modify the same target data, and the modified target data.

    [0028] The trans-time zone sites can include service sites that include the same operation service and that are located in mutually different time zones. For example, when the earlier described service is a payment service, the trans-time zone sites can include international sites deployed in different countries that are used to provide a cross-border payment service for a user, or can include service sites deployed in administrative regions with mutually different time zones in the same country that are used to provide a national payment service for a user.

    [0029] The target data can be shared by servers of the trans-time zone sites, and the servers of the trans-time zone sites include service data with corresponding modification permission. A specific service data form is not limited in the present implementation.

    [0030] For example, in a shown application scenario, assume that the servers of the trans-time zone sites can support the user in logging in to the trans-time zone sites based on the same login account. Therefore, the target data can be a login password corresponding to the login account, and the user can access servers of different trans-time zone sites by using the same login account, modify the login password corresponding to the login account by using the accessed servers of the trans-time zone sites, and then submit a modified login password to the server of the central node.

    [0031] The time stamp is used to record a precise time for modifying the target data by the user, and can be represented by total seconds from Greenwich Mean Time 1970-01-01 00:00:00 to the time for modifying the target data by the user.

    [0032] It is worthwhile to note that, in actual applications, to prevent the trans-time zone sites from submitting the same time stamp, the time stamps can be accurate to the more precise duration unit such as a millisecond.

    [0033] In the present implementation, the target data usually can be modified by the user. For example, the user can log in to the servers of the trans-time zone sites by using a client terminal, to modify the target data stored on the servers of the trans-time zone sites.

    [0034] The servers of the trans-time zone sites can generate the time stamps at the back end when the user modifies the target data, record the precise time for modifying the target data by the user, and after the user modifies the target data, submit the generated time stamps and the target data modified by the user to the server of the central node. The server of the central node performs version comparison for aggregation.

    [0035] The servers of the trans-time zone sites can generate the time stamps based on time zones of the trans-time zone sites or based on the time zone of a central site. In actual applications, the time stamps can be generated by the trans-time zone sites through negotiation in advance. For example, in actual applications, the trans-time zone sites and the central site can negotiate, in advance through exchange of a control packet, time zones used for generating the time stamps by the trans-time zone sites.

    [0036] In the present implementation, after generating the time stamps, the servers of the trans-time zone sites can obtain the target data modified by the user, and then submit the generated time stamps and the target data modified by the user to the server of the central node.

    [0037] The servers of the trans-time zone sites can still asynchronously submit the time stamps and the modified target data to a server of the central site by using messages. For example, the servers of the trans-time zone sites can add the time stamps and the modified target data to a packet, and then send the packet to the server of the central node based on information such as an IP address or an interface port of the server of the central site.

    [0038] Step 102: When the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, separately perform, based on a time zone of a central site, time zone conversion on the time stamps submitted by the trans-time zone sites.

    [0039] In the present implementation, when receiving the time stamps and the modified target data submitted by the servers of the trans-time zone sites, the server of the central site can perform, based on the time stamps submitted by the servers of the trans-time zone sites, version comparison on the modified target data submitted by the servers of the trans-time zone sites.

    [0040] The time stamps can be generated by the trans-time zone sites based on the respective time zones of the trans-time zone sites, or based on the time zone of the central site. Therefore, for the two cases, the server of the central node can differently perform, based on the time stamps submitted by the trans-time zone sites, version comparison on the modified target data submitted by the trans-time zone sites.

    [0041] In a shown implementation, if the server of the central site negotiates with the servers of the trans-time zone sites in advance to generate the time stamps by using the respective time zones of the trans-time zone sites, the server of the central site can perform, based on the time zone of the central site, the time zone conversion on the time stamps submitted by the servers of the trans-time zone sites.

    [0042] When performing the time zone conversion on the time stamps submitted by the servers of the trans-time zone sites, the server of the central site can identify, based on locations of the trans-time zone sites, the time zones of the trans-time zone sites, and then perform, based on a conversion relationship between a time zone of a central site and a time zone of a trans-time zone site, the time zone conversion on the time stamps submitted by the trans-time zone sites.

    [0043] For example, assume that the central site is located in Hangzhou with a time zone GMT+8, and the trans-time zone site is a Japan site with a time zone GMT+9. A conversion relationship between the time zone of the central site and the time zone of the Japan site is subtracting one hour. Assume that the Japan site generates a time stamp of N seconds based on the time zone of the Japan site, the central site can subtract 3600 seconds from the time stamp when performing the time zone conversion on the time stamp, and a time stamp obtained after the time zone conversion is N-3600 seconds.

    [0044] Step 103: Perform, based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, data version comparison on the target data submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites.

    [0045] In the present implementation, after performing the time zone conversion on the time stamps submitted by the trans-time zone sites, the server of the central site can perform, based on the time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, the version comparison on the modified target data submitted by the trans-time zone sites.

    [0046] When performing, based on the time stamps obtained after the time zone conversion, the version comparison on the modified target data submitted by the trans-time zone sites, the server of the central site can directly compare values of the time stamps submitted by the trans-time zone sites, because time zones of the time stamps obtained after the time zone conversion and submitted by the trans-time zone sites have been unified; then determine that modified target data submitted by a trans-time zone site with the largest time stamp value is target data of the latest version.

    [0047] In addition, it is worthwhile to note that, to prevent the time stamps obtained after the time zone conversion from including time stamps of the same value, in actual applications, when the servers of the trans-time zone sites generate the time stamps, the time stamps can be accurate to the more precise duration unit such as a millisecond. By using this method, the more precise time stamp duration unit indicates the lower probability of identical values after the server of the central site performs the time zone conversion on time stamps generated by different trans-time zone sites.

    [0048] In a shown implementation, if the server of the central site negotiates with the servers of the trans-time zone sites in advance to generate the time stamps by using the time zone of the central site, the servers of the trans-time zone sites have unified the time zones of the time stamps in advance when respectively generating the time stamps. In such case, after receiving the time stamps and the modified target data submitted by the servers of the trans-time zone sites, the server of the central site does not need to perform the time zone conversion on the time stamps submitted by the trans-time zone sites, and instead, the server of the central site directly uses the time stamps submitted by the trans-time zone sites, to perform the version comparison on the modified target data submitted by the trans-time zone sites.

    [0049] In the present implementation, when determining, through value comparison, the target data of the latest version in the modified target data submitted by the servers of the trans-time zone sites, the server of the central site can use the target data of the latest version to update original target data stored on the server of the central node, so as to ensure that the target data stored on the server of the central node is of the latest version.

    [0050] The following describes the technical solution in the previous implementation in detail by using a specific application scenario.

    [0051] Referring to FIG. 2, FIG. 2 is a diagram illustrating an application scenario of data version comparison between trans-time zone sites disclosed in an implementation.

    [0052] In the scenario, an example in which the earlier described trans-time zone sites deploy international sites in different countries is used for description.

    [0053] Assume that a server of a central site is located in Hangzhou with a time zone GMT+8.

    [0054] The international sites include the following: a Japan site with a time zone GMT+9; a New York site with a time zone GMT-5; and an India site with a time zone GMT+5.

    [0055] The server of the central site located in Hangzhou negotiates with servers of the Japan site, the New York site, and the India site in advance to calculate time stamps by using respective time zones of the Japan site, the New York site, and the India site.

    [0056] The previous target data is data1234, and the target data is shared by the servers of the Japan site, the New York site, and the India site. In addition, the servers of the Japan site, the New York site, and the India site include service data with corresponding modification permission.

    [0057] Assume that the servers of the Japan site, the New York site, and the India site modify the target data data1234 at 8:00 on April 30, 3016, and the time stamps generated by the servers of the Japan site, the New York site, and the India site based on their respective time zones are 1461110400 seconds.

    [0058] The servers of the Japan site, the New York site, and the India site can asynchronously submit the respectively generated time stamps and the modified target data data1234 to the server of the central site located in Hangzhou.

    [0059] After receiving the respectively generated time stamps and the modified target data data1234 by the servers of the Japan site, the New York site, and the India site, the server of the central site can perform, based on the time zone of the central site, time zone conversion on the time stamps generated by the servers of the Japan site, the New York site, and the India site.

    [0060] When a conversion relationship between the time zone GMT+8 of the central site and the time zone GMT+8 of the Japan site is subtracting one hour, the server of the central site can subtract 3600 seconds from the time stamp of 1461110400 seconds after performing, based on the time zone GMT+8 of the central site, the time zone conversion on the time stamp of 1461110400 seconds generated by the server of the Japan site, and a time stamp of the Japan site obtained after the time zone conversion is 1461106800 seconds.

    [0061] When a conversion relationship between the time zone GMT+8 of the central site and the time zone GMT-5 of the New York site is adding 13 hours, the server of the central site can add 46800 seconds to the time stamp of 1461110400 seconds after performing, based on the time zone GMT+8 of the central site, the time zone conversion on the time stamp of 1461110400 seconds generated by the server of the New York site, and a time stamp of the New York site obtained after the time zone conversion is 1461157300 seconds.

    [0062] When a conversion relationship between the time zone GMT+8 of the central site and the time zone GMT+5 of the India site is adding three hours, the server of the central site can add 10800 seconds to the time stamp of 1461110400 seconds after performing, based on the time zone GMT+8 of the central site, the time zone conversion on the time stamp of 1461110400 seconds generated by the server of the India site, and a time stamp of the India site obtained after the time zone conversion is 1461121300 seconds.

    [0063] After performing, based on the time zone GMT+8 of the central site, the time zone conversion on the time stamps generated by the servers of the Japan site, the New York site, and the India site, the server of the central site can use time stamps obtained after the time zone conversion as data version numbers, and perform version comparison on the modified target data data1234 submitted by the servers of the Japan site, the New York site, and the India site.

    [0064] In such case, a version number of the modified target data data1234 submitted by the Japan site is Version1=1461106800; a version number of the modified target data data1234 submitted by the New York site is Version2=1461157300; and a version number of the modified target data data1234 submitted by the India site is Version3=1461121300.

    [0065] The server of the central site identifies, through comparison, that Version2 > Version3 > Version 1. In such case, the server of the central site can determine that the modified target data data1234 submitted by the New York site is of the latest version, and can replace and update locally stored original target data data1234 by using the modified target data data1234 submitted by the New York site.

    [0066] Because the server of the central site uses time stamps with a unified time zone when performing the version comparison, a version sequence of the target data submitted by the servers of the Japan site, the New York site, and the India site is consistent with a sequence of modifying the target data. Therefore, a central node aggregates, in the version sequence, the modified service data submitted by the Japan site, the New York site, and the India site without causing disordered versions.

    [0067] It can be seen from the previous implementations that, in the present application, time stamps generated when trans-time zone sites modify the same target data and the modified target data are received. When the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, time zone conversion is separately performed on the time stamps submitted by the trans-time zone sites based on a time zone of a central site. Moreover, data version comparison is performed on the target data submitted by the trans-time zone sites based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites. Therefore, when aggregating service data of the trans-time zone sites, a central node can perform, based on a time zone of the central node, the time zone conversion on the time stamps submitted when the trans-time zone sites modify the same target data, so that the central node can use time stamps with a unified time zone to perform the version comparison on the modified service data submitted by the trans-time zone sites. Therefore, after the trans-time zone sites modify the same service data, the modified service data submitted by the trans-time zone sites is aggregated in a version sequence without causing disordered service data versions.

    [0068] Corresponding to the previous method implementation, the present application further provides a device implementation.

    [0069] Referring to FIG. 3, the present application provides a device 30 for data version comparison between trans-time zone sites, and the device is applied to a server used as a central site. Referring to FIG. 4, a hardware architecture related to the server including the device 30 for data version comparison between trans-time zone sites generally includes a CPU, a memory, a nonvolatile memory, a network interface, an internal bus, etc. Software implementation is used as an example. The device 30 for data version comparison between trans-time zone sites usually can be understood as a computer program loaded in the memory. After the CPU runs the computer program, a logic device that combines software with hardware is formed. The device 30 includes: a receiving module 301, configured to receive time stamps generated when trans-time zone sites modify the same target data, and the modified target data; a conversion module 302, configured to separately perform time zone conversion on the time stamps submitted by the trans-time zone sites based on a time zone of a central site, when the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites; and a comparison module 303, configured to perform, based on time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, data version comparison on the target data submitted by the trans-time zone sites, so as to determine target data of the latest version in the target data submitted by the trans-time zone sites.

    [0070] In the present implementation, the comparison module 303 is further configured to perform the data version comparison on the target data submitted by the trans-time zone sites based on the time stamps submitted by the trans-time zone sites, when the time stamps are generated by the trans-time zone sites based on the time zone of the central site.

    [0071] In the present implementation, the conversion module 302 is configured to query the time zones of the trans-time zone sites; and separately perform, based on a conversion relationship between a time zone of each trans-time zone site and a time zone of a central site, the time zone conversion on the time stamps submitted by the trans-time zone sites.

    [0072] In the present implementation, the comparison module 303 is configured to compare values of the time stamps submitted by the trans-time zone sites; and determine that target data submitted by a trans-time zone site with the largest time stamp value is the target data of the latest version.

    [0073] In the present implementation, the device 30 further includes: an update module 304, configured to update locally stored original target data by using the target data of the latest version when the target data of the latest version in the target data submitted by the trans-time zone sites is determined.

    [0074] A person skilled in the art can easily figure out another implementation of the present application after considering the specification and practicing the present application. The present application is intended to cover any variations, functions, or adaptive changes of the present application. These variations, functions, or adaptive changes comply with general principles of the present application, and include common knowledge or a commonly used technical means in the technical field that is not disclosed in the present application. The specification and the implementations are merely considered as examples, and the actual scope of the present application are described by the following claims.

    [0075] It should be understood that the present application is not limited to the earlier described accurate structures that are shown in the accompanying drawings, and modifications and changes can be made without departing from the scope of the present application. The scope of the present application is limited only by the appended claims.

    [0076] The previous descriptions are merely example implementations of the present application, but are not intended to limit the present application. Any modification, equivalent replacement, or improvement made without departing from the principle of the present application should fall within the protection scope of the present application.


    Claims

    1. A method for data version comparison between trans-time zone sites, the method comprising:

    when trans-time zone sites modify target data, receiving (101), for each respective trans-time zone site of the trans-time zone sites, a time stamp and modified target data, the time stamp being generated by the respective trans-time zone site;

    when the time stamps are generated by the trans-time zone sites based on respective time zones of the trans-time zone sites, separately performing (102), for each respective trans-time zone site of the trans-time zone sites and based on a time zone of a central site, time zone conversion on the time stamp submitted by the respective trans-time zone site; and

    performing (103), based on the time stamps obtained after the time zone conversion and submitted by the trans-time zone sites, data version comparison on the modified target data submitted by the trans-time zone sites, to determine a latest version of the target data in the modified target data submitted by the trans-time zone sites; wherein

    performing the data version comparison comprises:

    comparing values of the time stamps submitted by the trans-time zone sites; and

    determining that modified target data submitted by a trans-time zone site with the largest time stamp value is the latest version of the target data.


     
    2. The method according to claim 1, further comprising:
    when the time stamps are generated by the trans-time zone sites based on the time zone of the central site, performing, based on the time stamps submitted by the trans-time zone sites, the data version comparison on the modified target data submitted by the trans-time zone sites.
     
    3. The method according to claim 2, wherein separately performing, based on the time zone of a central site, time zone conversion on the time stamps submitted by the trans-time zone sites comprises:

    querying the time zones of the trans-time zone sites; and

    separately performing, based on a conversion relationship between a time zone of each trans-time zone site and a time zone of a central site, the time zone conversion on the time stamps submitted by the trans-time zone sites.


     
    4. The method according to claim 1 or 2, wherein the values of the time stamps correspond to a duration based on duration units, preferably the duration units corresponding to seconds or milliseconds.
     
    5. The method according to claim 1, further comprising:
    when the target data of the latest version in the modified target data submitted by the trans-time zone sites is determined, updating locally stored original target data by using the target data of the latest version.
     
    6. The method according to any one of claims 1 to 5, wherein the trans-time zone sites are configured to perform an operation service and are located in mutually different time zones.
     
    7. The method according to claim 6, wherein the payment service comprises a cross-border payment service or a national payment service.
     
    8. A device (30) for data version comparison between trans-time zone sites, the device comprising a plurality of modules (301, 302, 303, 304) configured to perform each step of the method of any one of claims 1 to 7.
     


    Ansprüche

    1. Verfahren für einen Datenversionsvergleich zwischen zeitzonenübergreifenden Standorten, wobei das Verfahren Folgendes umfasst:

    wenn zeitzonenübergreifende Standorte Zieldaten ändern, Empfangen (101), für jeden jeweiligen zeitzonenübergreifenden Standort der zeitzonenübergreifenden Standorte, eines Zeitstempels und geänderter Zieldaten, wobei der Zeitstempel von dem jeweiligen zeitzonenübergreifenden Standort erzeugt wird;

    wenn die Zeitstempel von den zeitzonenübergreifenden Standorten basierend auf jeweiligen Zeitzonen der zeitzonenübergreifenden Standorte erzeugt werden, separates Durchführen (102), für jeden jeweiligen zeitzonenübergreifenden Standort der zeitzonenübergreifenden Standorte und, basierend auf einer Zeitzone eines zentralen Standorts, der Zeitzonenkonvertierung des von dem jeweiligen zeitzonenübergreifenden Standort übermittelten Zeitstempels; und

    Durchführen (103), basierend auf den Zeitstempeln, die nach der Zeitzonenkonvertierung erhalten und von den zeitzonenübergreifenden Standorten übermittelt wurden, eines Datenversionsvergleichs an von den zeitzonenübergreifenden Standorten übermittelten geänderten Zieldaten, um eine neueste Version der Zieldaten in den von den zeitzonenübergreifenden Standorten übermittelten geänderten Zieldaten zu bestimmen;

    wobei das Durchführen des Datenversionsvergleichs Folgendes umfasst:

    Vergleichen von Werten der von den zeitzonenübergreifenden Standorten übermittelten Zeitstempel; und

    Bestimmen, dass von den zeitzonenübergreifenden Standorten übermittelte geänderte Zieldaten mit dem größten Zeitstempelwert die neueste Version der Zieldaten sind.


     
    2. Verfahren nach Anspruch 1, ferner Folgendes umfassend:
    wenn die Zeitstempel von den zeitzonenübergreifenden Standorten basierend auf der Zeitzone des zentralen Standorts erzeugt werden, Durchführen, basierend auf den von den zeitzonenübergreifenden Standorten übermittelten Zeitstempeln, des Datenversionsvergleichs an den von den zeitzonenübergreifenden Standorten übermittelten geänderten Zieldaten.
     
    3. Verfahren nach Anspruch 2, wobei das separate Durchführen, basierend auf der Zeitzone eines zentralen Standorts, einer Zeitzonenkonvertierung an den von den zeitzonenübergreifenden Standorten übermittelten Zeitstempeln Folgendes umfasst:

    Abfragen der Zeitzonen der zeitzonenübergreifenden Standorte; und

    separates Durchführen, basierend auf einer Konvertierungsbeziehung zwischen einer Zeitzone jedes zeitzonenübergreifenden Standorts und einer Zeitzone eines zentralen Standorts, der Zeitzonenkonvertierung an den von den zeitzonenübergreifenden Standorten übermittelten Zeitstempeln.


     
    4. Verfahren nach Anspruch 1 oder 2, wobei die Werte der Zeitstempel einer Dauer entsprechen, die auf Zeitdauer-Einheiten basiert, vorzugsweise auf Zeitdauer-Einheiten, die Sekunden oder Millisekunden entsprechen.
     
    5. Verfahren nach Anspruch 1, ferner Folgendes umfassend:
    wenn die Zieldaten der neuesten Version in den von den zeitzonenübergreifenden Zeitzonen übermittelten geänderten Zieldaten bestimmt werden, Aktualisieren der lokal gespeicherten ursprünglichen Zieldaten unter Verwendung der Zieldaten der neuesten Version.
     
    6. Verfahren nach einem der Ansprüche 1 bis 5, wobei die zeitzonenübergreifenden Standorte so konfiguriert sind, dass sie einen Betriebsdienst durchführen und sich in voneinander unterscheidenden Zeitzonen befinden.
     
    7. Verfahren nach Anspruch 6, wobei der Zahlungsdienst einen grenzüberschreitenden Zahlungsdienst oder einen nationalen Zahlungsdienst umfasst.
     
    8. Vorrichtung (30) für den Datenversionsvergleich zwischen zeitzonenübergreifenden Standorten, wobei die Vorrichtung mehrere Module (301, 302, 303, 304) umfasst, die so konfiguriert sind, dass sie jeden Schritt des Verfahrens nach einem der Ansprüche 1 bis 7 durchführen.
     


    Revendications

    1. Procédé de comparaison de versions de données entre des sites situés dans différents fuseaux horaires, le procédé comprenant :

    lorsque des sites situés dans différents fuseaux horaires modifient des données cibles, la réception (101), pour chaque site situé dans un fuseau horaire différent respectif des sites situés dans différents fuseaux horaires, d'une estampille temporelle et de données cibles modifiées, l'estampille temporelle étant générée par le site situé dans un fuseau horaire différent respectif ;

    lorsque les estampilles temporelles sont générées par les sites situés dans différents fuseaux horaires en fonction de fuseaux horaires respectifs parmi les sites situés dans différents fuseaux horaires, l'exécution séparée (102), pour chaque site situé dans un fuseau horaire différent respectif parmi les sites situés dans différents fuseaux horaires et en fonction d'un fuseau horaire d'un site central, de la conversion du fuseau horaire sur l'estampille temporelle soumise par le site situé dans un fuseau horaire différent respectif ; et

    l'exécution (103), en fonction des estampilles temporelles obtenues après conversion du fuseau horaire et soumises par les sites situés dans différents fuseaux horaires, d'une comparaison de versions de données sur les données cibles modifiées soumises par les sites situés dans différents fuseaux horaires, pour déterminer une version la plus récente des données cibles dans les données cibles modifiées soumises par les sites situés dans différents fuseaux horaires ;

    dans lequel l'exécution de la comparaison de versions de données comprend :

    la comparaison de valeurs des estampilles temporelles soumises par les sites situés dans différents fuseaux horaires ; et

    la détermination du fait que les données cibles modifiées soumises par un site situé dans un fuseau horaire différent dotées de la plus grande valeur d'estampille temporelle sont la version la plus récente des données cibles.


     
    2. Procédé selon la revendication 1, comprenant en outre :
    lorsque les estampilles temporelles sont générées par les sites situés dans différents fuseaux horaires en fonction du fuseau horaire du site central, l'exécution, en fonction des estampilles temporelles soumises par les sites situés dans différents fuseaux horaires, de la comparaison des versions de données sur les données cibles modifiées soumises par les sites situés dans différents fuseaux horaires.
     
    3. Procédé selon la revendication 2, dans lequel l'exécution séparée, en fonction du fuseau horaire d'un site central, d'une conversion de fuseau horaire sur les estampilles temporelles soumises par les sites situés dans différents fuseaux horaires comprend :

    la consultation des fuseaux horaires des sites situés dans différents fuseaux horaires ; et

    l'exécution séparée, en fonction d'une relation de conversion entre un fuseau horaire de chaque site situé dans un fuseau horaire différent et d'un fuseau horaire d'un site central, de la conversion de fuseaux horaires sur les estampilles temporelles soumises par les sites situés dans différents fuseaux horaires.


     
    4. Procédé selon la revendication 1 ou 2, dans lequel les valeurs des estampilles temporelles correspondent à une durée en fonction d'unités de durée, les unités de durée correspondant de préférence à des secondes ou millisecondes.
     
    5. Procédé selon la revendication 1, comprenant en outre :
    lorsque les données cibles de la version la plus récente dans les données cibles modifiées soumises par les sites situés dans différents fuseaux horaires sont déterminées, la mise à jour des données cibles d'origine stockées localement à l'aide des données cibles de la version la plus récente.
     
    6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel les sites situés dans différents fuseaux horaires sont configurés pour exécuter un service d'exploitation et sont situés dans des fuseaux horaires mutuellement différents.
     
    7. Procédé selon la revendication 6, dans lequel le service de paiement comprend un service de paiement transfrontalier ou un service de paiement national.
     
    8. Dispositif (30) de comparaison de versions de données entre sites situés dans différents fuseaux horaires, le dispositif comprenant une pluralité de modules (301, 302, 303, 304) configurés pour exécuter chaque étape du procédé selon l'une quelconque des revendications 1 à 7.
     




    Drawing

















    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description