CN109783502B - Settlement method, device and system supporting multi-terminal login and server - Google Patents
Settlement method, device and system supporting multi-terminal login and server Download PDFInfo
- Publication number
- CN109783502B CN109783502B CN201811628065.5A CN201811628065A CN109783502B CN 109783502 B CN109783502 B CN 109783502B CN 201811628065 A CN201811628065 A CN 201811628065A CN 109783502 B CN109783502 B CN 109783502B
- Authority
- CN
- China
- Prior art keywords
- settlement
- database
- historical
- account
- record
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a settlement method, a device, a server and a system supporting multi-terminal login, wherein the method comprises the following steps: responding to a set event, acquiring a first historical settlement record formed by the same account in other login places, and updating a second historical settlement record corresponding to the account in a local database according to the first historical settlement record; in response to a settlement request of a user terminal logging in the account, performing settlement based on the latest second historical settlement record, and independently generating a settlement flow list exclusively belonging to the local server; updating the second historical settlement record according to the settlement running list; and recording the settlement running list to the database of the other login places so as to update the first historical settlement record.
Description
Technical Field
The invention relates to the technical field of cross-region settlement, in particular to a settlement method supporting multi-terminal login, a settlement device supporting multi-terminal login, a settlement system supporting multi-terminal login and a server.
Background
For client applications, two application modes are mainly used at present, one mode is that a plurality of user terminals are not allowed to log in the same account at the same time, and the other mode is that a plurality of user terminals are allowed to log in the same account at the same time for use. For the latter application mode, if the client application provides services such as payment, recharge, etc., more stringent requirements are placed on the logic and performance of the computing system.
Under the scene that a plurality of user terminals are allowed to log in the same account for use at the same time, the existing settlement mode mainly comprises a single data sheet mutual exclusion mode or a distributed transaction mode. The single data sheet mutual exclusion mode is that a settlement data sheet is maintained in a data center, and settlement requests generated by each user terminal for the same account need to be settled in the data center so as to ensure the strong consistency of settlement data. In the distributed transaction mode, although settlement processing can be performed through a plurality of data centers, each data center must negotiate with other data centers before settlement so as to ensure data consistency of each data center before settlement, and further ensure that the current account balance is enough to process the settlement request. Therefore, in the existing main settlement method, settlement data needs to be sent or settlement negotiation needs to be performed through a network before settlement requests are processed, and in the process, problems of network delay, network instability, network disconnection and the like often occur, so that the settlement process is inevitably slow, the failure rate is high, which is more serious in a situation that a plurality of user terminals are used across countries, and the user experience is seriously influenced, and therefore, a new settlement scheme supporting multi-terminal login needs to be provided to solve the problems in the existing international business.
Disclosure of Invention
An object of the embodiments of the present invention is to provide a new technical solution for settlement when multi-terminal login is supported.
According to a first aspect of the present invention, there is provided a settlement method supporting multi-terminal login, comprising:
responding to a set event, acquiring a first historical settlement record formed by the same account in other login places, and updating a second historical settlement record corresponding to the account in a local database according to the first historical settlement record;
in response to a settlement request of a user terminal logging in the account, performing settlement based on the latest second historical settlement record, and independently generating a settlement flow list exclusively belonging to the local server;
updating the second historical settlement record according to the settlement running list;
and recording the settlement running list to the database of the other login places so as to update the first historical settlement record.
Optionally, the settlement request is a payment request, and the settlement running list is a consumption running list corresponding to the payment request, the method further includes:
in response to a settlement request of the user terminal, checking whether the account balance of the account is enough to process the settlement request according to the latest second historical settlement record;
and re-executing the settlement based on the latest second historical settlement record when the settlement request is processed sufficiently.
Optionally, the setting the event includes: and responding to a settlement request of the user terminal, reestablishing a communication connection with a home database of the account, calling between micro services, and setting one or more of a time interval and a time.
Optionally, the step of obtaining a first historical settlement record of the same account formed at other login places includes:
acquiring a home location database of the account;
acquiring the latest historical settlement record from the attribution database as the first historical settlement record;
the step of recording the settlement flow sheet to the database of the other login place to update the first historical settlement record comprises:
recording the settlement flow sheet to the home database to update the first historical settlement record.
Optionally, the step of obtaining the latest historical settlement record from the home database includes:
establishing a first http request, wherein a header of the first http request carries local information of a location where the login is located and attribution information of the account;
starting the local database to acquire the first historical settlement record from the home database through the first http request, wherein the local database and the home database are both SQL databases; and/or the presence of a gas in the gas,
the step of recording the settlement flow sheet to the home database comprises:
establishing a second http request, wherein a header of the second http request carries local information of a location where the login is located and attribution information of the account;
and starting the local database through the second http request to record the settlement running list to the attribution database, wherein the local database and the attribution database are both SQL databases.
Optionally, the step of recording the settlement running list to the home database includes:
after the operation of recording the settlement running list to the attribution database is executed at the current time, detecting whether the operation at the current time is successful;
and in the case that the operation of the current time is not successful, executing the operation of the next time based on the set retransmission condition.
Optionally, the step of independently generating a settlement flow sheet specific to the local server includes:
acquiring an identification number of the local server;
independently generating a settlement flow sheet with an exclusive sheet number, wherein the exclusive sheet number comprises an identification number of the local server.
Optionally, the step of independently generating the settlement running list with the exclusive list number includes:
selecting one of the plurality of senders of the local server to independently generate the settlement running list with the exclusive list number, wherein the exclusive list number further comprises an identification number of the one sender.
According to the second aspect of the present invention, there is also provided a settlement apparatus supporting multi-terminal login, provided on a side of a local server of a login site, comprising:
the first synchronization module is used for responding to a set event, acquiring a first historical settlement record formed by the same account in other login places, and updating a second historical settlement record corresponding to the account in a local database according to the first historical settlement record;
the local settlement module is used for responding to a settlement request of a user terminal logging in the account, performing settlement based on the latest second historical settlement record and independently generating a settlement running list special for the local server;
the local data updating module is used for updating the second historical settlement record according to the settlement running list; and the number of the first and second groups,
and the second synchronization module is used for recording the settlement running list to the databases of other login places so as to update the first historical settlement record.
According to a third aspect of the present invention, there is also provided a server including the settlement apparatus according to the second aspect of the present invention; or, a memory for storing executable instructions and a processor; the processor is configured to operate the server according to the control of the instruction to execute the settlement method according to the first aspect of the present invention.
According to a fourth aspect of the present invention, there is further provided a settlement system supporting multi-terminal login, which includes a plurality of servers according to the third aspect of the present invention, each server corresponds to a data center, and each data center is configured with a dedicated database for storing a respective second historical settlement record.
The method, the device, the server and the system have the advantages that the settlement request of the user terminal can be settled based on the latest historical settlement record of the corresponding account in the local database, the settlement flow list which is exclusively owned by the local server can be independently generated without requiring the negotiation with the servers of other login places for logging in the account during settlement, the settlement speed and the settlement success rate can be improved, and the historical settlement records of the corresponding account in the databases of the other login places can be updated based on the settlement flow list, so that the consistency of the final settlement results of the local server and the servers of the other login places is ensured.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a schematic block diagram showing a hardware configuration of a settlement system supporting multi-terminal login, which can be used to implement an embodiment of the present invention;
FIG. 2 is a functional block diagram of a hardware configuration of a data center according to an embodiment of the present invention;
fig. 3 is a flowchart of a settlement method supporting multi-terminal login according to a first embodiment of the present invention;
fig. 4 is a flowchart of a settlement method supporting multi-terminal login according to a second embodiment of the present invention;
fig. 5 is a functional block diagram of a settlement apparatus supporting multi-terminal login according to an embodiment of the present invention;
FIG. 6 is a functional block diagram of a server according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a hardware structure of a server according to an embodiment of the present invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
< hardware configuration >
Fig. 1 is a block diagram of a hardware configuration of a settlement system 100 supporting multiple-terminal login that can be used to implement an embodiment of the present invention.
As shown in fig. 1, the settlement system 100 supporting multi-terminal login according to the embodiment includes 3 data centers 1000 (see fig. 2), which are a data center 1000A, a data center 1000B, and a data center 1000C, and the data center 1000A, the data center 1000B, and the data center 1000C establish communication connection through a network 2000.
In an international scenario, a plurality of data centers 1000 are usually opened globally, for example, 32 data centers may be opened, or even more, and no limitation is made herein.
When the user roams from the home data center to other data centers, the other data centers logged on the local can be used to complete corresponding services. In this embodiment, the multi-terminal login means allowing multiple user terminals to simultaneously log in the same account, and further allowing multiple user terminals to simultaneously log in the same account in different regions (corresponding to different data centers), for example, allowing at most three user terminals to simultaneously log in the same account.
For example, the data center 1000A may be a data center deployed in germany, and the data center 1000B and the data center 1000C may be a data center deployed in japan and a data center deployed in beijing, respectively, wherein any one of the data centers may be a data center to which an account is attributed, and the attribution is generally a registration place of the account.
The network 2000 may be a wireless communication network or a wired communication network, and may be a local area network or a wide area network. In the settlement system 100 supporting multi-terminal login shown in fig. 1, the data centers 1000A and 1000B, the data centers 1000A and 1000C, and the data centers 1000C and 1000B may communicate with each other through the network 2000. Further, the networks 2000 upon which data center 1000A communicates with data center 1000B, data center 1000A communicates with data center 1000C, and data center 1000C communicates with data center 1000B may be the same or different.
Based on the settlement system 100 of the present embodiment, a plurality of user terminals may log in the same account at locations corresponding to different data centers, for example, the user terminal 3000A logs in the account under the jurisdiction of the data center 1000A, the user terminal 3000B logs in the account under the jurisdiction of the data center 1000B, and the user terminal 3000C logs in the account under the jurisdiction of the data center 1000C.
Fig. 2 is a schematic diagram of a hardware structure of a data center 1000 according to an embodiment of the present invention.
As shown in fig. 2, the data center 1000 of the present embodiment includes at least a server 1100 and a database 1200.
The server 1100 provides a service point for processes, databases, and communications facilities. The server 1100 can be a unitary server or a distributed server across multiple computers or computer data centers. The server may be of various types, such as, but not limited to, a web server, a news server, a mail server, a message server, an advertisement server, a file server, an application server, an interaction server, a database server, or a proxy server. In some embodiments, each server may include hardware, software, or embedded logic components or a combination of two or more such components for performing the appropriate functions supported or implemented by the server. For example, a server, such as a blade server, a cloud server, etc., or may be a server group consisting of a plurality of servers, which may include one or more of the above types of servers, etc.
In this example, the server 1100 may be as shown in FIG. 2, including a processor 1110, a memory 1120, an interface device 1130, a communication device 1140, a display device 1150, and an input device 1160. In this example, the server 1100 may further include a speaker, a microphone, and the like, which are not limited herein. The processor 1110 may be a dedicated server processor, or may be a desktop processor, a mobile version processor, or the like that meets performance requirements, and is not limited herein. The memory 1120 includes, for example, a ROM (read only memory), a RAM (random access memory), a nonvolatile memory such as a hard disk, and the like. The interface device 1130 includes various bus interfaces such as a serial bus interface (including a USB interface), a parallel bus interface, and the like. The communication device 1140 is capable of wired or wireless communication, for example. The display device 1150 is, for example, a liquid crystal display panel, an LED display panel touch display panel, or the like. Input devices 1160 may include, for example, a touch screen, a keyboard, and the like.
In this example, the memory 1120 of the server 1100 is used to store instructions for controlling the execution of the server 1100 to perform at least a settlement method supporting multi-terminal login according to any embodiment of the present invention. The skilled person can design the instructions according to the disclosed solution. How the instructions control the operation of the processor is well known in the art and will not be described in detail herein.
Although shown as multiple devices of server 1100 in fig. 2, the present invention may relate to only some of the devices, e.g., server 1100 may relate to only memory 1120, processor 1110, and communications 1140.
The database 1200 is used for saving the historical settlement records acquired by the server 1100, for example, referring to fig. 1, the database 1200A is used for saving the historical settlement records acquired by the server 1100A, the database 1200B is used for saving the historical settlement records acquired by the server 1100B, and the database 1200C is used for saving the historical settlement records acquired by the data center server 1100C.
The database 1200 may also participate in data synchronization between multiple data centers, for example, the database 1200 is an SQL database, which is, for example, a client application that may install the SQL database on a corresponding server to synchronize data with the client application.
Database 1200 may also be a database server, which may have a hardware structure similar to server 1100, but which primarily implements database management and maintenance functions.
Fig. 2 also shows a hardware structure of the user terminal 3000. As shown in fig. 2, the user terminal 3000 may include a processor 3100, a memory 3200, an interface device 3300, a communication device 3400, a display device 3500, an input device 3600, a speaker 3700, a microphone 3800, and the like.
The user terminal 3000 may be any one of the user terminals 3000A, 3000B, 3000C in fig. 1.
The network in which the user terminal 3000 establishes a communication connection with the data center 1000 may be the same network as the network 2000 in fig. 1 or may be a different network.
In one embodiment, the settlement system is a settlement system corresponding to a shared vehicle service, a client application using a shared vehicle is installed on the user terminal 3000, and the server 1100 of each data center 1000 can support all services using the shared vehicle, including account settlement.
< method examples >
Fig. 3 is a flowchart illustrating a settlement method supporting multiple-end login according to an embodiment of the present invention, where the method is implemented by a local server 1100 at a login location, and the settlement method supporting multiple-end login according to the embodiment may include the following steps S2100 to S2400:
in step S2100, the local server 1100 at the location of the login obtains a first historical settlement record formed by the same account at another login location in response to the setting event, and updates a second historical settlement record corresponding to the account in the local database according to the first historical settlement record.
In step S2100, the local server 1100 is a server that registers a data center to which the location belongs, and for example, the local server 1100 may be the server 1100A of the data center 1000A, or the server 1100B of the data center 1000B.
According to the step S2100, the database 1200 of the data center 1000 where the local server 1100 is located is a local database, for example, the local server 1100 is the server 1100A of the data center 1000A, and the local database is the database 1200A of the data center 1000A.
In this embodiment, from the perspective of any user terminal logging in the same account, the historical settlement records stored in the database at the location where the user terminal logs in, that is, the local database, are the second historical settlement records, and the historical settlement records stored in the databases at other locations are all the first historical settlement records. Thus, for different user terminals logging into the same account, the local server, the local database may correspond to physically different servers and databases.
In this embodiment, for a user terminal logging in the same account, the data center of the login location may be the data center 1000A in fig. 1, the data centers of other login locations may be the data center 1000B and the data center 1000C in fig. 1, where the local server 1100 of the login location may be the server 1100A in fig. 1, the servers of other login locations may be the server 1100B and the server 1100C in fig. 1, the local database of the login location may be the database 1200A in fig. 1, and the databases of other login locations may be the database 1200B and the database 1200C in fig. 1. For other user terminals logging in the same account, the data center of the location where the user terminal logs in may also be the data center 1000B or the data center 1000C in fig. 1, which is not limited herein.
The setting event may include any one or more of responding to a settlement request of the user terminal, re-establishing a communication connection with a home database of the account, making a call between micro services, and setting a time interval to time.
In one example, the setting event may include a settlement request in response to a user terminal.
For example, the settlement request may be a recharge request. According to the example, the user can click "recharge" in the display interface of the corresponding application program APP in the user terminal, at this time, the user terminal reports a recharge request to the local server of the login location, the local server of the login location executes the steps of obtaining a first historical settlement record formed by the same account in other login locations, and updating a second historical settlement record of the account corresponding to the local database according to the first historical settlement record.
Also for example, the settlement request may be a payment request.
In this example, taking shared vehicle usage as an example, after parking a vehicle, a user clicks "end travel" in a display interface of a corresponding application APP in a user terminal, at this time, the user terminal reports a payment request to a local server at a login location to notify the local server 1100 that the user has finished using the vehicle, and the local server at the login location performs a step of acquiring a first historical settlement record formed by the same account at other login locations, and updating a second historical settlement record of an account corresponding to a local database according to the first historical settlement record.
In this example, when the user parks the vehicle, locking can be achieved by operating the lock mechanism of the vehicle, when the vehicle detects that the lock mechanism is changed from the unlocked state to the locked state, a payment request is reported to the local server at the login location to notify the local server at the login location that the user has finished using the vehicle, and the local server at the login location executes the steps of acquiring a first historical settlement record formed by the same account at other login locations and updating a second historical settlement record of the account corresponding to the local database according to the first historical settlement record.
In one example, the provisioning event may include reestablishing a communication connection with a home database of the account.
The attribution is a registration place of the account, that is, an attribution database is a database of an attribution data center, where the attribution data center may be any one of the data center 1000A, the data center 1000B and the data center 1000C in fig. 1, and correspondingly, when the attribution data center is the data center 1000A, the attribution database is the database 1200A; when the angelica attribution data center is the data center 1000B, the corresponding attribution database is the database 1200B; when the home data center is the data center 1000C, the corresponding home database is the database 1200C.
In this example, the communication connection between the local database at the login location and the home database may be disconnected due to network instability, so that when the communication connection between the local database at the login location and the home database is reestablished after the network is recovered, the local server at the login location may perform the steps of obtaining a first historical settlement record formed by the same account at another login location, and updating a second historical settlement record of the account corresponding to the local database according to the first historical settlement record.
In one example, the setup event may include a call between microservices made by a local server.
In this example, when the local server at the login location calls up between the micro services, the step of obtaining a first historical settlement record formed by the same account at other login locations and updating a second historical settlement record of the account corresponding to the local database according to the first historical settlement record may be triggered.
In one example, the set event may be the expiration of a set time interval.
In this example, a time interval may be set in the local server at the location of the login, and when the set time interval arrives, the step of acquiring a first historical settlement record formed by the same account at another login location and updating a second historical settlement record of the account corresponding to the local database according to the first historical settlement record may be performed.
The above examples show different ways of setting the setting event, so that the local server 1100 at the login location can trigger the operation of obtaining the first historical settlement records formed by the same account at other login locations based on different setting events, and then complete the update of the historical settlement records of the corresponding account in the local database, thereby ensuring the final consistency of the historical settlement records of the same account in the local database and the databases at other login locations.
In step S2200, the local server 1100 at the location of the login performs settlement based on the latest second historical settlement record in response to the settlement request of the user terminal logged in the account, and independently generates a settlement flow sheet specific to the local server.
According to this step S2200, when the local server 1100 receives the settlement request, the settlement request may be a payment request or a recharge request, and the settlement may be performed based on the latest second historical settlement record stored in the local database, and the corresponding settlement flow sheet may be independently generated.
In this embodiment, the operation of updating the second historical settlement record based on step S2100 is continuously performed based on the trigger of the setting event, and step S2200 is not implemented on the premise that the operation of updating the second historical settlement record based on step S2100 must be successfully completed, so that the method of this embodiment can directly perform settlement based on the current latest second historical settlement record and independently generate a corresponding settlement running list when a settlement request is received, which obviously improves the response speed and the success rate of completing settlement.
In one example, the step S2200 of independently generating the settlement flow sheet dedicated to the local server 1100 may further include the following steps S2210 to S2220:
in step S2210, the local server 1100 at the location of the login obtains the identification number of the local server.
In step S2210, the local server 1100 at the login location and other servers on the land each have a specific identification number, which is used to distinguish the servers of different data centers, and the identification number may be manually set by an operator or determined by negotiation among the data center servers.
For example, there are 32 data centers provided globally, each including a server, and therefore, in order to distinguish the above 32 data centers, a 5-bit numeric symbol having an identification number of 5 bits may be provided, the 5-bit numeric symbol being composed of binary numbers 0 and 1, and the 5-bit numeric symbol may be expressed as, for example: 00000, 00001, 00010 … … 11111. For example, the local server at the login location is server 1100A, the identification number of server 1100A may be the number "00001", in this case, the servers at other login locations may be server 1100B and server 1100C, the identification number of server 1100B is the number "00010", the identification number of server 1100C is "11111", and the like.
Step S2220, the local server 1100 at the location where the login is made independently generates the settlement running list with the exclusive list number.
The proprietary ticket number includes the identification number of the local server 1100. In this embodiment, the exclusive single number may be a 64-bit digital symbol, the 64-bit digital symbol is composed of binary numbers 0 and 1, and 5 bits are identification numbers of the server, so that even if the servers of different data centers generate settlement streamers simultaneously, each settlement streamer can be uniquely identified by the identification number of the server, and thus, final consistency of the settlement data of the account in each data center (each node) can be realized based on each settlement streamer generated by the same account in different login places.
According to the steps S2210 to S2220, in this example, the settlement running list with the exclusive list number is independently generated based on the identification number of the local server 1100, so that on one hand, the source of the settlement running list can be visually represented, and on the other hand, when the settlement running list is generated independently by a plurality of data centers, the uniqueness of all the settlement running lists can be ensured, and further, the final consistency of the settlement data can be realized according to the settlement running lists generated in different login places.
In an example, the independently generating the settlement running list with the exclusive list number in step S2220 may further include: the local server 1100 logging on to the location selects one of the plurality of issuers of the local server 1100 to independently generate the settlement running list with the exclusive list number.
In this example, the proprietary ticket number also includes the identification number of the selected issuer. The identification number of the number sender can be manually set by an operator or can be configured by a corresponding server.
In this example, each server has 32 transmitters, for example, and in order to distinguish the 32 transmitters, the identification number of the transmitter may be set to be a 5-bit numeric symbol, the 5-bit numeric symbol is composed of binary numbers 0 and 1, and the five-bit numeric symbol may be sequentially expressed as: 00000, 00001, 00010 … … 11111.
In this example, the local server 1100 at the location of the login may independently generate the settlement flow sheet with the exclusive sheet number by randomly assigning one of the above 32 issuers.
In this example, the issuer may independently generate the settlement running list with the exclusive list number according to a preset generation policy.
The preset generation strategy may be: the length of the whole settlement flow list is 64-bit binary number, wherein the 41-bit binary number is a time stamp in milliseconds, for example, when the settlement request is a recharging request, the first 41 bits are used for representing recharging time, and for example, when the settlement request is a payment request, the first 41 bits are used for representing payment time; wherein, the 5-bit binary number is the identification number of the corresponding server; wherein, the 5-bit binary number is the identification number of the sender; there are also 12-bit binary numbers that are serial numbers within milliseconds. This illustrates that each issuer of each data center can generate 4096 settlement streamers per millisecond, while the world can have 32 data centers with 32 issuers per data center, which is sufficient to support application scenarios where there are a large number of streamers generated at the same time, such as settlement scenarios for shared vehicles.
The settlement water flow sheet may include water flow information, such as an expenditure amount or an entry amount, and may further include a settlement time, an account flag, and the like.
In this example, each server corresponds to multiple issuers, which can effectively increase the throughput of each data center for settlement requests, so that each data center can process a large number of settlement requests at the same time and generate a unique settlement list without queuing, thereby effectively improving the response speed of each data center for processing settlement requests.
In step S2300, the local server 1100 registered in the location updates the second historical settlement record according to the settlement flow sheet.
According to this step S2300, the local server 1100 regenerates the settlement flow sheet, and then records the generated settlement flow sheet in the local database, thereby updating the second historical settlement record.
The second historical settlement record may contain all settlement drafts currently acquired, and thus, the account balance of the account may be determined from the second historical settlement record.
For example, when the settlement request is a payment request, "payment amount 2 yuan" is displayed in the settlement flow sheet and "account balance 8 yuan" is displayed in the second historical settlement record, and here, the second historical settlement record may be updated to "account balance 6 yuan".
For another example, when the settlement request is a charge request, the "charge amount 50 yuan" may be displayed in the settlement flow sheet, the "account balance 8 yuan" may be displayed in the second historical settlement record, and the second historical settlement record may be updated to "account balance 58 yuan" here.
In step S2400, the local server 1100 at the login location records the settlement worksheet in the database at the other login location to update the first historical settlement record.
According to this step S2400, after the local server 1100 generates the settlement running list, the local server 1100 records the settlement running list in the databases of other login places to update the first historical settlement record, so that the data center of each login place of the same account can finally obtain the settlement running list generated by the data centers of other login places, thereby ensuring that the settlement data of the same account in different data centers have final consistency.
According to the steps S2100 to S2400, the method according to the embodiment of the present invention can settle the settlement request of the user terminal based on the latest historical settlement record of the account registered in the local database, and does not need to negotiate with the server at the other login location that registers the same account before the settlement, and the settlement does not assume that the latest first historical settlement record must be successfully acquired from the database at the other login location, and the settlement can be completed by independently generating the settlement flow sheet dedicated to the local server as long as the settlement request is received, which can improve the settlement rate and the settlement success rate.
In addition, the method according to the embodiment of the invention can record the generated settlement running list into other land-logging databases to update the first historical settlement record of the same account, thereby ensuring that the local data center and the other land-logging data centers have final consistency on the settlement data of the same account.
In one embodiment, for one account, the home data center may establish a communication connection with each login data center point to point, that is, the settlement streamers generated by the home data center are all reported to the home data center for recording, so that the local server may obtain the first historical settlement records formed by the same account at other login places by contacting the home data center (including the home server and the home database) of the account, so as to implement the simplest and most effective point-to-point interaction and reduce network congestion.
In this embodiment, the acquiring the first historical settlement record of the same account at other login places in step S2100 may further include steps S2110 to S2120 as follows:
step S2110, the local server 1100 at the login location acquires the home database of the account.
Each account may be labeled with home location information, and therefore, the local server 1100 may obtain the home location information of the account from the account information, and further determine a home location data center and a corresponding home location database.
According to step S2110, the home data center and the local data center may be the same data center or different data centers, for example, the local data center is data center 1000A, the local server is server 1100A, the local database is 1200A, the home data center is data center 1000C, and the home database is database 1200C.
In this example, the data centers of the respective user terminals logging in the same account may respectively establish a connection with the home data center to record the generated settlement worksheets in the local database and the home database of the home data center, so that the local server may contact the home server to obtain the first historical settlement record from the home database.
In another example, the local server may contact servers of other login places respectively to obtain the first historical settlement records from databases of other login places respectively.
In step S2120, the local server 1100 at the location of the login acquires the latest historical settlement record from the home database as the first historical settlement record.
In step S2120, since the data centers of the user terminals that log in the same account are connected to the home data center respectively, so as to record the generated settlement orders in the local database and also in the home database of the home data center, the local server 1100 at the login location can directly obtain the latest historical settlement record from the home database as the first historical settlement record.
According to this step S2120, if the login location is the home location, the local server is the home location server, and the local database is also the home location database, which is equivalent to directly obtaining the latest historical settlement record from the local database as the first historical settlement record, in this case, the first historical settlement record is also the second historical settlement record.
Correspondingly, the step of updating the first historical settlement record according to the settlement flow sheet by the local server 1100 logged in the location in the step S2400 may further include: the local server 1100 at the login location records the settlement drafts to the home database to update the first historical settlement record.
Here, since the local server 1100 at the login location records the settlement flow sheet in the home database, the home database can finally obtain the settlement flow sheets generated by the data centers at the respective login locations for one account, and update the first historical settlement record based on the settlement flow sheets.
In one example, the logging of the settlement drafts to the home database by the local server 1100 of the location may further include the following steps S2421 to S2422:
in step S2421, the local server 1100 at the location of the login detects whether the current operation is successful after the current operation of recording the settlement running list in the home database is performed.
In step S2422, when the current operation is not successful, the local server 1100 logging in the location executes the next operation based on the set retransmission condition.
The retransmission condition may be, for example, a timeout without receiving the home data center, or an acknowledgement message returned by the home server indicating successful receipt of the settlement manifold.
According to the above steps S2421 to S2422, in the case that it is detected that the current operation is not successful, the example can execute the next operation based on the set retransmission condition until the settlement pipelining is successfully recorded in the home database, and thus can ensure the final consistency of the settlement data of the same account at each data center.
In one embodiment, the step of obtaining the latest historical settlement record from the home database by the local server 1100 at the location registered in the step S2120 may further include the following steps S2121 to S2122:
step S2121, log in the local server 1100 in the location to establish a first http request.
The header of the first http request carries local information of the login location and attribution information of the account. The local information may be, for example, name information of a location where the user terminal registered in the account is located (i.e., a registered location), and similarly, the location information may be, for example, name information of a location where the account is located.
Step S2122, the local server 1100 at the location of the log-in location starts the local database to obtain the latest historical settlement record from the database at the location of the home via the first http request.
The local database and the home database are both SQL databases, which may also be understood as that the historical settlement records stored in the local database and the home database are both stored in the form of SQL language.
In one example, each time a user terminal triggers a call between micro services based on an http request, a Location field and a roaming Location field are implanted in an http header to identify data Location information of a user, the header is transferred when a restful data interface call is performed between the micro services, and when a client application of an SQL database reads the header, information in the header is changed into an SQL comment form, for example,/' Location ═ BJ; and when the SQL Proxy analyzes the corresponding annotation key word, the corresponding statement is copied into a specified SQL database according to the mapping rules of the data attribution and the land logging (roaming place) to execute data synchronization between the local database and the attribution database.
For example, referring to fig. 1, the home database is a database 1200C, the local database is a database 1200A, the local server is a server 1100A, the other databases are databases 1200B, the "remaining amount a yuan" is displayed in the historical settlement record of the corresponding account in the local database 1200A, the historical settlement record is the second historical settlement record, the "remaining amount X yuan" is displayed in the latest historical settlement record stored in the home database 1200C, and the "remaining amount a yuan" and the "remaining amount X yuan" may or may not coincide at any time but will have final consistency. Here, the local server 1100A may update the second historical settlement record of the account corresponding to the local database 1200A according to the first historical settlement record, so as to update the "remaining amount a yuan" to the "remaining amount X yuan", that is, display the "remaining amount X yuan" in the updated second historical settlement record.
As can be known from the steps S2121 to S2122, the method according to this embodiment may start the local database by sending an http request to obtain the latest historical settlement record from the home database, and since the user terminal may frequently trigger the http request, and the http request may perform call between micro services, in this example, data synchronization between databases is performed through the http request, which is beneficial to accelerating implementation of final consistency of settlement data, so as to reduce the actual defaulting of an account as much as possible, but the case that the account is not defaulting according to the second historical settlement record of the local data center occurs.
In one embodiment, logging the settlement drafts to the home database by the local server 1100 of the location may further include the following steps S2411 to S2412:
step S2411, logging in the local server 1100 at the location to establish a second http request.
And the header of the second http request carries the local information of the login location and the attribution information of the account.
Step S2412, the local server 1100 logging in the location starts the local database through the second http request, and records the settlement flow list to the home database.
The local database and the home database are both SQL databases.
As can be seen from the steps S2411 to S2412, the method of this embodiment may start recording the settlement order in the home database by sending an http request, and since the user terminal may frequently trigger the http request, and the http request may perform call between microservices, in this example, data synchronization between databases is performed by the http request, which is beneficial to accelerating implementation of final consistency of the settlement data.
In an embodiment, referring to fig. 4, the settlement method supporting multi-terminal login in this embodiment may further include the following steps S3100 to S3200:
in step S3100, the local server 1100 at the location of login calculates whether or not the account balance of the account is sufficient to process the settlement request based on the latest second historical settlement record in response to the settlement request from the user terminal.
In step S3200, the local server 1100 at the location registered performs settlement based on the latest second historical settlement record when it is sufficient to process the settlement request.
For example, the settlement pipeline is shown with "2 dollar payment amount" and the second historical settlement record is shown with "4 dollar remaining amount", i.e., the account balance is sufficient to process the payment request, so that the settlement pipeline is settled based on the second historical settlement record.
Correspondingly, the local server 1100 may roll back the settlement request and cancel the settlement operation if the account amount is not sufficient to process the settlement request. Meanwhile, a reminder of insufficient balance can be sent to the user terminal logging in the account.
According to the above steps S3100 to S3200, when the settlement request is a payment request, the embodiment may be to calculate the account balance based on the local second historical settlement record, and when the account balance can process the payment request, the settlement request is settled and the settlement is generated, so as to reduce the frequency of the unpaid use as much as possible.
< apparatus embodiment >
In the present embodiment, a settlement apparatus 5000 supporting multi-terminal login is further provided, and as shown in fig. 5, may include a first synchronization module 5100, a local settlement module 5200, a local data update module 5300, and a second synchronization module 5400.
The first synchronization module 5100 is configured to, in response to a set event, obtain a first historical settlement record formed by the same account at another login location, and update a second historical settlement record corresponding to the account in the local database according to the first historical settlement record.
The local settlement module 5200 is configured to perform settlement based on the latest second historical settlement record in response to a settlement request from the user terminal that has logged in the account, and independently generate a settlement flow sheet specific to the local server.
The local data update module 5300 is configured to update the second historical settlement record according to the settlement pipeline order.
The second synchronization module 5400 is configured to record the settlement flow sheet to the database of the other login location to update the first historical settlement record.
In one embodiment, the settlement request is a payment request and the settlement running sheet is a consumption running sheet corresponding to the payment request.
The local settlement module 5200 is further configured to, in response to a settlement request from the user terminal, check whether the account balance of the account is sufficient for processing the settlement request according to the latest second historical settlement record; and performing settlement based on the latest second historical settlement record under the condition that the settlement request is processed sufficiently.
In one embodiment, the setting event comprises: and responding to a settlement request of the user terminal, reestablishing a communication connection with a home database of the account, calling between micro services, and setting one or more of a time interval and a time.
In one embodiment, the first synchronization module 5100 is further configured to obtain a home database of the account; and acquiring the latest historical settlement record from the home database as the first historical settlement record.
The second synchronization module 5400 is further configured to record the settlement flow sheet to the home database to update the first historical settlement record.
In one embodiment, the first synchronization module 5100 is further configured to establish a first http request; and starting the local database to acquire the first historical settlement record from the home database through the first http request.
And the head of the first http request carries the local information of the location where the login is located and the attribution information of the account.
The local database and the home database are both SQL databases.
The second synchronization module 5400 is further configured to establish a second http request; and starting the local database through the second http request to record the settlement running list to the home database.
And the header of the second http request carries the local information of the location where the login is located and the attribution information of the account.
The local database and the home database are both SQL databases.
In one embodiment, the second synchronization module 5400 is further configured to detect whether the operation of the current time is successful after the operation of recording the settlement running list to the home database is currently performed; and in the case that the operation of the current time is not successful, executing the operation of the next time based on the set retransmission condition.
In one embodiment, the local settlement module 5200 is further configured to obtain an identification number of the local server; independently generating a settlement running list with a special list number.
The exclusive ticket number includes an identification number of the local server.
In one embodiment, the local settlement module 5200 is further configured to select one of the plurality of issuers of the local server to independently generate the settlement running list with the specific list number.
The exclusive single number also comprises an identification number of one of the number senders.
< Server embodiment >
In this embodiment, a server 1100 is also provided, and the server 1200 may be, for example, the server 1100A, the server 1100B, or the server 1000C in fig. 1.
As shown in fig. 6, the server 1100 includes a settlement apparatus 5000 supporting multi-terminal login according to any embodiment of the present invention, for implementing a settlement method supporting multi-terminal login according to any embodiment of the present invention.
As shown in fig. 7, the server 1100 may also include at least one processor 1110 and at least one memory 1120. The memory 1120 is used to store executable instructions. The processor 1110 is configured to operate the server 1100 to perform a settlement method supporting multi-terminal login according to the control of the instruction, according to any embodiment of the present invention.
The present invention may be a system, method and/or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therewith for causing a processor to implement various aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations of the present invention may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, by software, and by a combination of software and hardware are equivalent.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.
Claims (10)
1. A settlement method for supporting multi-terminal login, implemented by a local server of a login location of an account, the local server being a server of a data center to which the login location belongs, the method comprising:
in response to a set event, acquiring the latest historical settlement record from a database of a place of ownership of the account, wherein the latest historical settlement record is used as a first historical settlement record formed by the account at other login places, and updating a second historical settlement record corresponding to the account in a local database according to the first historical settlement record, wherein the local database is a database of a data center of the place of ownership, the place of ownership is a registration place of the account, the database of the place of ownership is a database of a data center of the place of ownership, the data center of the place of ownership is one data center in a settlement system supporting multi-terminal login, and the data center of the place of ownership and the data center of the place of login are different data centers;
in response to a settlement request of a user terminal logging in the account, performing settlement based on the latest second historical settlement record, and independently generating a settlement flow list exclusively belonging to the local server;
updating the second historical settlement record according to the settlement running list;
recording the settlement flow sheet to the home database to update the first historical settlement record.
2. The method of claim 1, wherein the settlement request is a payment request and the settlement blotter is a consumption blotter corresponding to the payment request, the method further comprising:
in response to a settlement request of the user terminal, checking whether the account balance of the account is enough to process the settlement request according to the latest second historical settlement record;
and re-executing the settlement based on the latest second historical settlement record when the settlement request is processed sufficiently.
3. The method of claim 1, wherein the setting an event comprises: and responding to a settlement request of the user terminal, reestablishing a communication connection with a home database of the account, calling between micro services, and setting one or more of a time interval and a time.
4. The method of claim 1, wherein the step of obtaining the most recent historical settlement record from the account's home database comprises:
establishing a first http request, wherein a header of the first http request carries local information of a location where the login is located and attribution information of the account;
starting the local database to acquire the first historical settlement record from the home database through the first http request, wherein the local database and the home database are both SQL databases; and/or the presence of a gas in the gas,
the step of recording the settlement flow sheet to the home database comprises:
establishing a second http request, wherein a header of the second http request carries local information of a location where the login is located and attribution information of the account;
and starting the local database through the second http request to record the settlement running list to the attribution database, wherein the local database and the attribution database are both SQL databases.
5. The method of claim 1, wherein the step of recording the settlement drafts to the home database comprises:
after the operation of recording the settlement running list to the attribution database is executed at the current time, detecting whether the operation at the current time is successful;
and in the case that the operation of the current time is not successful, executing the operation of the next time based on the set retransmission condition.
6. The method of any of claims 1 to 5, wherein the step of independently generating a settlement manifold specific to the local server comprises:
acquiring an identification number of the local server;
independently generating a settlement flow sheet with an exclusive sheet number, wherein the exclusive sheet number comprises an identification number of the local server.
7. The method of claim 6, wherein the step of independently generating a settlement lineup with a proprietary order number comprises:
selecting one of the plurality of senders of the local server to independently generate the settlement running list with the exclusive list number, wherein the exclusive list number further comprises an identification number of the one sender.
8. A settlement device supporting multi-terminal login is arranged on the side of a local server of a login location of an account, wherein the local server is a server of a data center to which the login location belongs, and the settlement device comprises:
the first synchronization module is used for responding to a set event, acquiring the latest historical settlement record from a home database of the account, taking the latest historical settlement record as a first historical settlement record formed by the account in other login places, and updating a second historical settlement record corresponding to the account in a local database according to the first historical settlement record, wherein the local database is a database of a data center to which the login place belongs, the home location is a registration place of the account, the home location database is a database of a home location data center, the home location data center is one data center in a settlement system supporting multi-terminal login, and the home location data center and the data center to which the login place belongs are different data centers;
the local settlement module is used for responding to a settlement request of a user terminal logging in the account, performing settlement based on the latest second historical settlement record and independently generating a settlement running list special for the local server;
the local data updating module is used for updating the second historical settlement record according to the settlement running list; and the number of the first and second groups,
and the second synchronization module is used for recording the settlement running list to the attribution database so as to update the first historical settlement record.
9. A server comprising the settlement apparatus of claim 8; or, a memory for storing executable instructions and a processor; the processor is used for operating the server according to the control of the instruction to execute the settlement method according to any one of claims 1 to 7.
10. A settlement system supporting multiple-end login, comprising a plurality of servers as claimed in claim 9, each server corresponding to a data center, each data center being configured with a dedicated database for storing a respective second historical settlement record.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811628065.5A CN109783502B (en) | 2018-12-28 | 2018-12-28 | Settlement method, device and system supporting multi-terminal login and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811628065.5A CN109783502B (en) | 2018-12-28 | 2018-12-28 | Settlement method, device and system supporting multi-terminal login and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109783502A CN109783502A (en) | 2019-05-21 |
| CN109783502B true CN109783502B (en) | 2021-03-23 |
Family
ID=66497973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811628065.5A Active CN109783502B (en) | 2018-12-28 | 2018-12-28 | Settlement method, device and system supporting multi-terminal login and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109783502B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110443598B (en) * | 2019-08-08 | 2023-03-28 | 上海中通吉网络技术有限公司 | Account settlement method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103443790A (en) * | 2011-03-15 | 2013-12-11 | 阿玛得斯两合公司 | Method and system for synchronization mechanism on multi-server reservation system |
| WO2014194853A1 (en) * | 2013-06-08 | 2014-12-11 | 华为技术有限公司 | Data processing method, system, terminal and server |
| CN105338093A (en) * | 2015-11-16 | 2016-02-17 | 中国建设银行股份有限公司 | Data synchronizing method and system |
| CN105678545A (en) * | 2016-01-04 | 2016-06-15 | 布比（北京）网络技术有限公司 | Digital asset transaction system based on distributed shared general ledger and construction method thereof |
| CN106933547A (en) * | 2015-12-29 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Method, device and more new system that global information is obtained and processed |
| CN108921542A (en) * | 2018-05-30 | 2018-11-30 | 招商银行股份有限公司 | Offline electronic payment method, payment end, gathering end and the storage medium of digital asset |
-
2018
- 2018-12-28 CN CN201811628065.5A patent/CN109783502B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103443790A (en) * | 2011-03-15 | 2013-12-11 | 阿玛得斯两合公司 | Method and system for synchronization mechanism on multi-server reservation system |
| WO2014194853A1 (en) * | 2013-06-08 | 2014-12-11 | 华为技术有限公司 | Data processing method, system, terminal and server |
| CN105338093A (en) * | 2015-11-16 | 2016-02-17 | 中国建设银行股份有限公司 | Data synchronizing method and system |
| CN106933547A (en) * | 2015-12-29 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Method, device and more new system that global information is obtained and processed |
| CN105678545A (en) * | 2016-01-04 | 2016-06-15 | 布比（北京）网络技术有限公司 | Digital asset transaction system based on distributed shared general ledger and construction method thereof |
| CN108921542A (en) * | 2018-05-30 | 2018-11-30 | 招商银行股份有限公司 | Offline electronic payment method, payment end, gathering end and the storage medium of digital asset |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109783502A (en) | 2019-05-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018196239A1 (en) | Communication method for multiple vehicles, vehicle, and server | |
| CN101622587B (en) | Centralized service for awakening a computing device | |
| CN111031058A (en) | Websocket-based distributed server cluster interaction method and device | |
| KR101577920B1 (en) | Location-based group generation method, apparatus and system | |
| CN103973545A (en) | Processing method, device and system of instant message | |
| CN102227899B (en) | Travelling carriage and application server and the method for operation thereof of service are provided to travelling carriage | |
| JP2018509669A (en) | Information push method and device | |
| CN103491217B (en) | A kind of fission mobile phone | |
| EP4117212A1 (en) | Data blind retransmission method and apparatus, storage medium, and terminal device | |
| CN111461831A (en) | Parking control method of vehicle, electronic equipment and vehicle system | |
| CN109783502B (en) | Settlement method, device and system supporting multi-terminal login and server | |
| CN110417905B (en) | Contract issuing method, device, equipment and union chain system | |
| CN104426956A (en) | Terminal status subscription method, apparatus and system | |
| CN105516243A (en) | Remote data transmission method, cloud data gateway and vehicle-mounted terminal | |
| CN103167403A (en) | Authentication method and system of electronic channel service | |
| CN109040981A (en) | Message method, device, storage medium and mobile terminal | |
| EP3015990B1 (en) | Information processing device, and destination information updating method and program | |
| CN103139733B (en) | By the System and method for of note pull-up off-line application program | |
| CN105306429A (en) | Stateful notification | |
| CN114500136B (en) | Smart home networking method, system, equipment and storage medium | |
| CN114040403B (en) | Equipment synchronization method, device and system | |
| CN103167432A (en) | System and method for achieving near-field information sending based on bluetooth transmission protocol | |
| CN113852474B (en) | Task processing method, gateway, computer readable storage medium and electronic device | |
| CN105704237B (en) | A kind of charge processing method and relevant device, server | |
| CN111862398B (en) | Service providing terminal unlocking method and device, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201218 Address after: Room 168, building 6, 741 Hangzhou Road, Yangpu District, Shanghai 200090 Applicant after: HANHAI INFORMATION TECHNOLOGY SHANGHAI Co.,Ltd. Address before: Room Bnan 1231, 2 bungalows, No. 5 Road, College, Haidian District, Beijing, 100191 Applicant before: BEIJING MOBIKE TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |