CN111447247B - On-site ticket checking system - Google Patents
On-site ticket checking system Download PDFInfo
- Publication number
- CN111447247B CN111447247B CN201811644542.7A CN201811644542A CN111447247B CN 111447247 B CN111447247 B CN 111447247B CN 201811644542 A CN201811644542 A CN 201811644542A CN 111447247 B CN111447247 B CN 111447247B
- Authority
- CN
- China
- Prior art keywords
- server
- ticket
- ticket checking
- data
- checking
- 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
- 238000004891 communication Methods 0.000 claims abstract description 45
- 238000000034 method Methods 0.000 claims description 10
- 230000007246 mechanism Effects 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 13
- 238000012545 processing Methods 0.000 description 10
- 230000002829 reductive effect Effects 0.000 description 8
- 238000012795 verification Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000670 limiting effect Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000036961 partial effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07B11/00—Apparatus for validating or cancelling issued tickets
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a field ticket checking system, which comprises a plurality of servers and a plurality of ticket checking terminals, wherein the servers and the ticket checking terminals are deployed in the same local area network; one server of the plurality of servers is set as a master server, and the rest servers are set as slave servers; the main server is connected with the ticket data center through an external network, and the slave server is connected with the main server through a local area network; the slave server is configured as a ticket checking server, and the ticket checking server is connected with at least one ticket checking terminal through a local area network; the main server is used for acquiring first ticket data from the ticket data center and issuing the first ticket data to the slave server, and acquiring second ticket data from the ticket checking server and uploading the second ticket data to the ticket data center; the main server is configured to update the first ticket data according to the second ticket data and issue the updated first ticket data to the slave server when the wireless communication connection between the main server and the ticket data center fails.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a field ticket checking system.
Background
With the development of science and technology, more and more ticket checking places (such as stations, cinemas, concerts and the like) realize ticket checking by replacing the traditional manual ticket checking mode with a ticket checking system consisting of a plurality of servers and a plurality of ticket checking terminals.
When the existing ticket checking system is used for checking tickets, each server is respectively in wireless connection with at least one ticket checking terminal and a cloud IDC (Internet Data Center; Chinese: Internet Data Center) storing ticket information through a public external network. Each server acquires ticket information from the IDC, and checks ticket checking data acquired from a ticket checking terminal connected with the server according to the acquired ticket information to acquire a checking result. And then, each server issues the check result to the corresponding ticket checking terminal, and simultaneously informs the IDC that the ticket checking data corresponding to the check result is checked. And the IDC counts the information that the ticket checking data notified by each server is checked, updates ticket information according to the counting result and sends the ticket information to each server.
In an actual ticket checking scene, the span of the traffic flow of people in the ticket checking place is large (small activities are hundreds or thousands, and large activities are hundreds of thousands or even millions). On one hand, a large amount of people flow provides a greater test for field security, and people flow needs to be controlled, guided and evacuated as soon as possible, which has high requirements on the speed and stability of field ticket checking. On the other hand, a large number of wireless communication devices, such as the server and the ticket checking terminal, the security monitoring device, the performance device, and the mobile phone carried by the audience, often exist in the ticket checking field, and these wireless communication devices may cause communication interference with each other, and cause instability or congestion of the external network, so that the wireless communication connection between the server and the cloud IDC, and the wireless communication connection between the server and the ticket checking terminal are unstable, and the ticket cannot be checked.
It is thus clear that prior art's ticket checking system can not be fine satisfies the requirement of actual ticket checking scene, in case appear because the outer net is unstable or the server trouble leads to between server and the high in the clouds IDC, when the wireless communication between server and the ticket checking terminal fails the problem, can only change into the hand and tear the ticket checking mode, perhaps switch the server into standby server temporarily, these all can cause the on-the-spot personnel to be detained, lead to the safety problem.
Disclosure of Invention
The invention aims to provide a novel on-site ticket checking system.
The invention provides a field ticket checking system, comprising: a plurality of servers and a plurality of ticket checking terminals which are deployed in the same local area network;
one of the servers is set as a master server, and the rest of the servers are set as slave servers;
the main server is connected with a ticket data center through an external network, and the slave server is connected with the main server through the local area network;
the slave server is configured as a ticket checking server, and the ticket checking server is connected with at least one ticket checking terminal through the local area network;
the main server is used for acquiring first ticket data from the ticket data center and issuing the first ticket data to the slave server, and acquiring second ticket data from the ticket checking server and uploading the second ticket data to the ticket data center;
the main server is configured to update the first ticket data according to the second ticket data and issue the updated first ticket data to the slave server when the wireless communication connection between the main server and a ticket data center fails.
Optionally, the plurality of servers are configured to reselect one server as a new master server according to a preset mechanism when the original master server goes offline.
Optionally, the main server is also configured as the ticket checking server.
Optionally, the ticket checking server is configured to provide a ticket checking service for the ticket checking terminal connected thereto, and includes: obtaining ticket checking data from the ticket checking terminal, checking the ticket checking data according to the first ticket business data, informing a checking result to the ticket checking terminal, and generating the second ticket business data according to the ticket checking data under the condition of successful checking.
Optionally, the server is configured to: when the ticket data center is taken as an original main server and is offline, the first ticket data which are not sent to the slave server are sent to a new main server when the original main server is online again, and the second ticket data which are not uploaded to the ticket data center are sent to the new main server;
the new main server is used for issuing the first ticket data acquired from the original main server to the auxiliary server and uploading the second ticket data acquired from the original main server to the ticket data center.
Optionally, wherein the main server is configured to maintain a service list; the service list comprises the identification, the address and the role of each ticket checking server;
the role is used for indicating the ticket checking server to be a master server or a slave server.
Optionally, the service list further includes load data of each ticket checking server;
the load data of the ticket checking server comprises the identification, the address and the number of the ticket checking terminals connected with the ticket checking server.
Optionally, the ticket checking terminal is further configured to obtain the service list; the ticket checking terminal acquires the service list, and the method comprises the following steps:
the ticket checking terminal requests the service list from the main server according to a preset period; or,
and the main server issues the updated service list to the ticket checking terminal after updating the service list each time.
Optionally, the ticket checking terminal is configured to: and when the ticket checking server connected with the ticket checking server is offline, selecting another ticket checking server according to the service list.
Optionally, wherein the main server is configured to: and when the slave server is offline or a new slave server is added into the local area network, resetting the ticket checking server for the ticket checking terminal according to the service list.
Optionally, a button for allowing a ticket checker to select a ticket checking server is provided on an interface of the ticket checking terminal, and the button corresponds to the ticket checking servers in the service list one to one.
Optionally, the master server is configured to, when the wireless communication connection between the master server and the ticket data center fails, update the first ticket data according to the second ticket data, and send the updated first ticket data to the slave server.
Optionally, the second ticket data includes any one or a combination of the following data: ticket number, ticket checking time, ticket checking port identification, check-in identification/check-out identification.
Optionally, the local area network is a wired local area network.
Optionally, the local area network is a wired and wireless hybrid local area network, wired communication is performed between the servers, and wireless communication is performed between the ticket checking terminal and the servers.
Optionally, the ticket checking terminal is arranged at a ticket checking site, and the distance between the server and the ticket checking site is within a preset distance range.
According to the on-site ticket checking system provided by the embodiment of the invention, on one hand, the main server and the slave server in the on-site ticket checking system are connected, and the ticket checking terminal and the ticket checking server are connected through the local area network, so that the reliability of communication connection between the main server and the slave server and between the ticket checking terminal and the ticket checking server is improved, and the safety risk of a ticket checking site is reduced. On the other hand, when the main server cannot perform wireless communication with the ticket data center due to instability of the external network, the main server can temporarily replace the role of the ticket data center, update the first ticket data newly stored by the main server according to the second ticket data acquired from each ticket checking server, and issue the updated first ticket data to each slave server, so that each ticket checking server can continue to provide ticket checking services, the reliable stability of the on-site ticket checking system is further improved, and the safety risk of a ticket checking site is reduced.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments of the invention, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments will be briefly described below. It is appreciated that the following drawings depict only certain embodiments of the invention and are therefore not to be considered limiting of its scope. For a person skilled in the art, it is possible to derive other relevant figures from these figures without inventive effort.
Fig. 1 is a schematic structural diagram of an on-site ticket checking system provided by an embodiment of the invention;
FIG. 2 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a ticket checking terminal according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of another field ticket checking system 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.
Referring to fig. 1, fig. 1 schematically illustrates an on-site ticket checking system provided by an embodiment of the present application, where the system includes multiple servers and multiple ticket checking terminals 2000 deployed in the same local area network. One of the servers is set as a master server 1010, and the remaining servers are set as slave servers 1020. The master server 1010 is connected to the ticket data center 3000 via an external network, and the slave server 1020 is connected to the master server 1010 via a local area network. The slave server 1020 is configured as a ticket checking server, and the ticket checking server is connected with at least one ticket checking terminal 2000 through a local area network.
Each of the plurality of servers is a service point for providing processing and communication facilities. For each server, the server may be a unitary server or distributed servers across multiple computers or computer data centers. The servers may be of various types, such as, but not limited to, news servers, mail servers, message servers, advertisement servers, file servers, application servers, interaction servers, database servers, or proxy servers. 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.
In one embodiment, as shown in fig. 2, the server may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, a display device 1500, an input device 1600.
In other embodiments, the server may further include a speaker, a microphone, and the like, which are not limited herein.
The processor 1100 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 1200 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 1300 includes, for example, various bus interfaces such as a serial bus interface, a parallel bus interface, a USB interface, and the like. Communication device 1400 is capable of wired or wireless communication, for example. The display device 1500 is, for example, a liquid crystal display, an LED display touch panel, or the like. The input device 1600 may include, for example, a touch screen, a keyboard, and the like.
Although a plurality of devices of the server are shown in fig. 2, the present invention may relate to only some of the devices.
In this embodiment, the ticket checking terminal 2000 is, for example, a gate, a scanning gun, a PDA (Personal Digital Assistant, handheld terminal), a mobile phone, a tablet computer, a palm computer, a wearable device, and the like.
As shown in fig. 3, the ticket checking terminal 2000 may include a processor 2100, a memory 2200, an interface device 2300, a communication device 2400, a display device 2500, an input device 2600, a speaker 2700, a microphone 2800, and the like.
Processor 2100 may be a central processor, a portable version of a processor, or the like. The memory 2200 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 2300 includes, for example, a USB interface, a headphone interface, and the like. The communication device 2400 can perform wired or wireless communication, for example, the communication device 2400 may include a short-range communication device, such as any device that performs short-range wireless communication based on a short-range wireless communication protocol, such as a Hilink protocol, WiFi (IEEE 802.11 protocol), Mesh, bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, LiFi, and the like, and the communication device 2400 may also include a remote communication device, such as any device that performs WLAN, GPRS, 2G/3G/4G/5G remote communication. The display device 2500 is, for example, a liquid crystal display panel, a touch panel, or the like. The input device 2600 may include, for example, a touch screen, a keyboard, and the like. A user can input/output voice information through the speaker 2700 and the microphone 2800.
Although a plurality of devices of the ticketing terminal 2000 are shown in fig. 3, the invention may relate only to some of the devices therein, e.g., the terminal 2000 relates only to the memory 2200 and the processor 2100, the communication device 2400 and the display device 2500.
In practical applications, the number of the slave servers 1020 connected to the master server 1010 and the number of the ticket checking terminals 2000 connected to the slave servers 1020 in the on-site ticket checking system may be set according to actual requirements, which is not limited in the embodiment of the present disclosure.
According to the on-site ticket checking system provided by the embodiment of the invention, the main server and the slave server in the on-site ticket checking system are connected through the local area network, the reliability of communication connection between the main server and the slave server and between the ticket checking terminal and the ticket checking server is improved, and the safety risk of a ticket checking site is reduced.
In one embodiment, the local area network is a wired local area network, that is, wired communication is adopted between the servers and between the ticket checking terminal and the ticket checking server, and the wired communication can further improve the stability of communication connection between the servers and the ticket checking terminal, thereby improving the reliability of the on-site ticket checking system.
In another embodiment, the local area network adopts a wired and wireless mixed local area network, a wired communication mode is adopted between the servers, and a wireless communication mode is adopted between the ticket checking terminal and the ticket checking server. The ticket checking personnel use the wireless ticket checking terminal, so that the ticket checking operation is more flexible, and when more ticket checking channels need to be opened, the ticket checking personnel can carry the ticket checking terminal to move more easily. This approach compromises the reliability and flexibility of the field ticket checking system.
When the local area network adopts a wired and wireless mixed local area network, a wired communication mode is adopted between the servers, a wireless communication mode is adopted between the ticket checking terminal and the ticket checking server, the ticket checking terminal is arranged on a ticket checking site, the distance between the server and the ticket checking site is within a preset distance range, for example, within 200 meters, and therefore the stability of the wireless connection between the ticket checking terminal and the ticket checking server is ensured.
In one embodiment, one of the plurality of servers may be set as the master server 1010 in two ways:
the first method is as follows: and (4) manual setting.
For example, the user may set the highest configured one of the plurality of servers as the master server 1010. For example, one of the servers with the highest data processing capability is set as the master server 1010.
The second method comprises the following steps: setting according to an election algorithm.
Specifically, any one of the plurality of servers may initiate elections according to an election algorithm, and the other servers vote. If the number of votes obtained by the election initiating server exceeds a preset number of votes (e.g., half of the total number of servers), the election initiating server is set as the primary server 1010. Otherwise, any one of the other servers repeats the above steps until the number of votes obtained by the server initiating election exceeds the preset number of votes, and the server with the number of votes obtained exceeding the preset number of votes is set as the main server 1010.
Or, several servers in the multiple servers respectively initiate elections according to the election algorithm, and other servers vote and elect the server with the highest vote number as the main server 1010.
The election algorithm may be: zookeeper zab's leader Algorithm, Google Chubby Algorithm, Ring leader election Algorithm, balloon Algorithm, etc. The implementation of the election algorithm can depend on hardware factors of the server as election factors, such as the number of CPU cores, the size of a memory and the like, so that the server with higher configuration is selected as a main server as far as possible.
Based on the above, one server of the plurality of servers is set as the main server 1010. Based on this, a server other than the master server 1010 among the plurality of servers is set as the slave server 1020. Meanwhile, the slave server 1020 is configured as a ticket checking server to implement a ticket checking function.
The master server 1010 is used for the ticket data center 3000 to obtain the first ticket data and issue the first ticket data to the slave server 1020, and for the ticket checking server to obtain the second ticket data and upload the second ticket data to the ticket data center 3000.
Specifically, the ticketing data center 3000 stores a plurality of first ticketing data, and each first ticketing data may include the following information: the ticket number, name, field, time of departure, seat number, and status (e.g., sold, unsubscribed, unverified, and verified), and each first ticket data corresponds to a unique ticket, and the ticket number of each ticket is unique. In one embodiment, the stored first ticketing data of the ticketing data center 3000 can be updated in real time, for example, if some tickets are sold before the concert is started, the first ticketing data of the tickets can be updated and the sold identifiers can be added.
Taking the ticket as the movie ticket as an example, the first ticket data includes: ticket number, movie name, play field, opening time, movie hall label, seat number, sold/unsubscribed logo, checked/unchecked logo, etc.
It should be noted that the information included in the first ticketing data is related to a specific ticket checking scenario, and the specific information included in the first ticketing data is not limited in the embodiment of the present invention.
The master server 1010 acquires the first ticket data from the ticket data center 3000, and then issues the first ticket data to the slave server 1020. The slave server 1020 stores the first ticket data in its own memory. Since the slave server 1020 is configured as a ticket checking server, that is, the master server 1010 issues the first ticket data to the ticket checking server, the ticket checking server stores the first ticket data in its memory.
In addition, the ticket checking server generates second ticket data, and uploads the second ticket data to the ticket data center 3000 through the main server 1010. The second ticket data are obtained by the ticket checking server according to the first ticket data and the ticket checking data reported by the ticket checking terminal and are used for representing the ticket data that the ticket checking data are successfully checked and other ticket checking information (such as information of a ticket checking port, ticket checking time and the like), each second ticket data corresponds to a unique ticket, and the second ticket data also carries ticket number information.
After receiving the second ticketing data, the ticketing data center 3000 updates the first ticketing data stored therein according to the second ticketing data. Specifically, the ticket data center 3000 may search, through the ticket number, first ticket data corresponding to the second ticket data, and add a verified identifier to the first ticket data, or further add other related information (for example, information such as a ticket gate, ticket verification time, etc.) included in the second ticket data. In addition, after updating the first ticket data, the ticket data center 3000 may send the updated first ticket data to the slave server 1020 through the master server 1010. The slave server 1020, upon receiving the updated first ticket data, replaces the first ticket information previously stored in its own memory with the updated first ticket data.
The master server 1010 is configured such that, when the wireless communication connection between the master server 1010 and the ticket data center 3000 fails, the master server 1010 updates the first ticket data according to the second ticket data, and issues the updated first ticket data to the slave server 1020.
Specifically, the failure of the wireless communication connection between the host server 1010 and the ticketing data center 3000 may be caused by the following reasons: 1. the external network is unstable, resulting in the main server 1010 not being able to wirelessly communicate with the ticketing data center 3000; 2. the user manually cuts off the wireless communication between the main server 1010 and the ticket data center 3000; 3. the module in the main server 1010 responsible for wireless communication with the ticketing data center 3000 fails; 4. other failures of the primary server 1010 occur and the system is inoperable.
When the wireless communication connection between the master server 1010 and the ticket data center 3000 fails, the master server temporarily replaces the role of the ticket data center, updates the first ticket data newly stored in the master server according to the second ticket data acquired from each ticket checking server, and issues the updated first ticket data to each slave server, so as to ensure that each ticket checking server can continue to provide ticket checking services, further improve the reliable stability of a field ticket checking system, and reduce the safety risk of a ticket checking field.
In particular, when the main server is set/elected, the main server takes the hardware configuration factors of the servers into consideration, is the highest server in all available servers, has strong data processing capacity, and can update the first ticket data at a high speed.
In an alternative embodiment, the servers are configured to reselect one server as a new master server according to a preset mechanism when the original master server goes offline.
Specifically, the main server 1010 and the ticketing data center 3000 are connected based on an external network, and if the external network is unstable, the connection between the main server 1010 and the ticketing data center 3000 is unstable, and further the main server 1010 goes offline. Alternatively, when the primary server 1010 fails, the primary server 1010 is brought down. At this time, the main server 1010 cannot acquire the first ticket data from the ticket data center 3000, and cannot upload the second ticket data acquired from the ticket checking server to the ticket data center 3000.
When the master server 1010 goes offline, the slave server 1020 serving as the ticket checking server cannot transmit the second ticket data to the master server 1010. Based on this, the slave server 1020 as the ticket checking server can know that the master server 1010 is offline. Of course, the slave server 1020 may also know that the master server 1010 is offline in other existing manners, which will not be described herein.
After the slave server 1020 knows that the master server 1010 is offline, the slave server 1020 may reselect a server as a new master server according to a preset mechanism.
The preset mechanism may be to randomly select one of the slave servers 1020 as a new master server. Alternatively, the predetermined mechanism may be that the plurality of slave servers 1020 elect a new master server according to an election algorithm. The specific implementation of the election algorithm can refer to the second mode described above.
After the new master server is selected, the new master server can realize the function of the original master server 1010 which is offline, that is, the new master server is connected with the ticket data center 3000 based on an external network, and acquires first ticket data from the ticket data center 3000 and forwards the first ticket data to the ticket checking server, and forwards second ticket data sent by the ticket checking server to the ticket data center 3000.
In addition, it should be noted that since the slave server 1020 is configured as a ticket checking server and can implement a ticket checking function, the ticket checking terminal connected to the slave server 1020 selected as a new master server can still be connected thereto. Of course, in order to avoid the new master server being overloaded, the slave server 1020 selected as the new master server may be disconnected from the ticket checking terminal 2000 connected thereto. The disconnected ticket checking terminal 2000 is connected to another slave server 1020.
In an embodiment, the new server may further send a request to the ticketing data center 3000 to request the ticketing data center 3000 to resend the first ticketing data sent to the original master server within a preset time period before the current time, and/or the new server sends a request to the slave server 1020 to request the slave server 1020 to resend the second ticketing data reported to the original master server within the preset time period before the current time. In this way, the loss rate of the first ticket data that has not been sent to the slave server 1020 by the original master server 1010 due to the original master server 1010 going off-line and/or the second ticket data that has not been uploaded to the ticket data center 3000 can be reduced.
According to the on-site ticket checking system provided by the embodiment of the invention, the main server which can be connected with an external network is configured in the on-site ticket checking system, ticket business data are transferred between the ticket business data center and the ticket checking server through the main server, and when a plurality of slave servers in the on-site ticket checking system are configured to be offline from the original main server, one server is newly selected as a new main server according to a preset mechanism. Therefore, when the original main server is off-line due to instability or failure of the external network, the rest servers can select a new main server, and the new main server continues to forward the ticket data in the ticket data center and the ticket checking server. Based on the on-site ticket checking system provided by the embodiment of the invention, the ticket data center can acquire the second ticket data in time and update the first ticket data in time, and the ticket checking server can acquire the updated first ticket data in time, so that the failure of a ticket checking mechanism is avoided. The embodiment of the invention further improves the reliability and stability of the on-site ticket checking system and reduces the safety risk of the ticket checking field.
In an alternative embodiment, the ticket verifying server generates the second ticket data by referring to the following contents:
the ticket checking server is used for providing the ticket checking service for the connected ticket checking terminal 2000, and comprises: the ticket checking data is acquired from the ticket checking terminal 2000, the ticket checking data is checked according to the first ticket data, the checking result is notified to the ticket checking terminal 2000, and in case of successful checking, the second ticket data is generated according to the ticket checking data.
For example, the ticket checking terminal 2000 scans an identifier such as a two-dimensional code or a barcode on a ticket to obtain an encrypted character string corresponding to the identifier, and sends the encrypted character string to the ticket checking server. And the ticket checking server decrypts the encrypted character string to obtain ticket checking data corresponding to the ticket.
Alternatively, the ticket checking terminal 2000 scans the identifier such as the two-dimensional code or the barcode on the ticket to obtain the encrypted character string corresponding to the identifier, and decrypts the encrypted character string to obtain the ticket checking data. After obtaining the ticket checking data, the ticket checking terminal 2000 sends the ticket checking data to the ticket checking server.
Wherein, the ticket checking data can include: ticket number, time of ticket check, ticket gate, field, name, seat number, and status (e.g., sold, unsubscribed, unverified, and verified).
And the ticket checking server checks the ticket checking data according to the first ticket business data to generate a checking result. In one example, the specific implementation of the check result obtained by the ticket checking server may be:
and judging whether the ticket number in the ticket checking data is consistent with the ticket number of certain first ticket business data, and if so, generating a check result that the ticket corresponding to the ticket checking data is a legal ticket. Otherwise, generating a check result that the ticket corresponding to the ticket checking data is an illegal ticket, and indicating that the check fails. It should be noted that the check result of the legal ticket does not necessarily indicate that the check is successful, the ticket checking server may further perform the check through the ticket checking data and other information in the first ticket data, and when all preset check items are passed, the check is successful.
Further, when the ticket number in the ticket checking data is consistent with the ticket number in the first ticket business data, whether the ticket checking data is checked is judged. If the ticket is verified, generating a verification result that the ticket verification data is the verified legal ticket.
It should be noted that, the check of the ticket checking data by the ticket checking server is related to the actual ticket checking environment, and correspondingly, the check result is also related to the actual ticket checking environment, which is easily understood by those skilled in the art.
After generating the check result, the ticket checking server sends the check result to the ticket checking terminal 2000. In one example, the ticket checking terminal 2000 performs corresponding sound or light prompts to the user according to different verification results when receiving the verification results. For example, when a check result indicating that the ticket corresponding to the ticket checking data is a legal ticket is received, a voice of "legal ticket can be output, or a green LED lamp is turned on to prompt the user that the ticket is a legal ticket and can pass. For example, when a check result indicating that the ticket corresponding to the ticket checking data is an illegal ticket is received, an alarm sound can be sent out, or a red LED lamp is turned on to prompt the user that the ticket is an illegal ticket and cannot pass through.
Meanwhile, after the ticket checking server generates the checking result, second ticket data is generated according to the ticket checking data under the condition that the checking result is successful. Specifically, if the check result is that the check is successful, the ticket number contained in the ticket checking data is extracted, the checked-out/checked-in identifier is added after the ticket number, and the second ticket data is generated based on the checked-out/checked-in identifier. Optionally, information such as ticket checking time and ticket checking port identifier may be added after the ticket number to generate second ticket data.
In an alternative embodiment, the host server 1010 is also configured as a ticketing server. That is, the host server 1010 may also establish a connection with the ticket checking terminal 2000 through the local area network and store the first ticket data in its own memory. Meanwhile, the second ticket data is generated as a ticket checking server and uploaded to the ticket data center 3000. This embodiment may be seen in particular in the field ticketing system shown in fig. 4.
In an alternative embodiment, when the original master server goes offline and goes online again as the slave server 1020 in the current on-site ticket checking system, the original master server is configured to send the first ticket data that has not been sent to the slave server 1020 to the new master server, and send the second ticket data that has not been uploaded to the ticket data center 3000 to the new master server.
Correspondingly, the new master server is configured to issue the first ticket data acquired from the original master server to the slave server 1020, and upload the second ticket data acquired from the original master server to the ticket data center 3000.
Therefore, the problem that part of the first ticket business data and part of the second ticket business data are lost due to the fact that the original main server is offline can be avoided, the reliable stability of a field ticket checking system is further improved, and the safety risk of a ticket checking field is reduced.
In an alternative embodiment, the main server is used for maintaining a server list, and the service list comprises the identification, the address and the role of each ticket checking server. The role is used for indicating the ticket checking server to be a master server or a slave server.
Specifically, the acquiring, by the main server 1010, the identifier, the address, and the role of the ticket checking server specifically includes: and acquiring the identification, address and role of the slave server as a ticket checking server. When the host server 1010 is configured as a ticket server, the host server 1010 also needs to read its own identity, address, and role. The slave server identifier and the master server identifier may be ID or IP of the server, respectively.
The main server 1010 generates a service list based on the obtained identifiers, addresses, and roles of all the ticket checking servers. In addition, the host server 1010 obtains the identification, address and role of the ticket checking server periodically, for example, to update the service list.
Optionally, the service list further includes load data of each ticket checking server; the load data of the ticket verifying server includes the identification, address, and number of the ticket verifying terminals 2000 connected thereto.
Specifically, the main server 1010 may further instruct the ticket checking server to report the identifier, the address, and the number of the ticket checking terminals connected to the main server when maintaining the service list. Based on this, the main server 1010 can obtain the identifier, address, and number of the ticket checking terminals 2000 connected to the main server, which are reported by the ticket checking server. The ticket checking terminal identifier may be an ID or an IP of the ticket checking terminal 2000.
The main server 1010 generates a service list based on the obtained identifiers, addresses and roles of all the ticket checking servers and the identifiers, addresses and numbers of the ticket checking terminals connected to the main server in the report of the ticket checking servers. In addition, the main server 1010, for example, periodically instructs the ticket checking server to report the identification, address, and number of the ticket checking terminals connected to the main server, thereby updating the service list.
Optionally, the ticket checking terminal 2000 is further configured to obtain a service list in any form described above. The ticket checking terminal 2000 may obtain the service list in the following two ways:
the first method is as follows: the ticket verifying terminal 2000 requests the service list from the main server 1010 according to a preset period.
It should be noted that the preset period can be preset manually.
The second method comprises the following steps: the main server 1010 issues the updated service list to the ticket gate terminal 2000 after updating the service list each time.
In addition, when the main server 1010 issues the server list to the ticket checking terminal 2000, the main server 1010 may issue the service list to the ticket checking server, and the ticket checking server forwards the service list to each ticket checking terminal 2000 connected to the main server.
In addition, each ticket checking terminal 2000 connected to the slave server 1020 may establish a short-time lan-based connection with the master server 1010 according to a preset period to directly request the service list from the master server 1010, and/or the master server 1010 directly issues the service list to the ticket checking terminals 2000.
Based on the service list, the ticket checking terminal 2000 can select different ticket checking servers from the service list according to actual requirements, so that personalized requirements of ticket checking personnel can be met.
Optionally, the ticket checking terminal 2000 is configured to: the interface of the ticket checking terminal 2000 is provided with keys for ticket checking personnel to select the ticket checking server, the keys correspond to the ticket checking servers in the service list one by one, and the ticket checking personnel can select the ticket checking server for the ticket checking terminal 2000 in a manual mode.
In one example, the ticket checking terminal 2000 displays the service list on its interface, a corresponding selection button is provided behind each ticket checking server in the service list, and a ticket checking person can check the identifier, the load condition, and the like of the ticket checking server through the interface, and select the ticket checking server with a lower load at present as the ticket checking server of its own ticket checking terminal 2000.
According to the embodiment, after the ticket checking terminal 2000 is offline with the ticket checking server connected with the ticket checking terminal, a ticket checking person can manually select another ticket checking server, so that the reliability and stability of the on-site ticket checking system are further improved, and the safety risk of a ticket checking site is reduced.
In an alternative embodiment, the ticket verifying terminal 2000 is configured to: and when the ticket checking server connected with the terminal is offline, selecting another ticket checking server according to the service list.
Specifically, when the ticket checking server connected to the ticket checking terminal 2000 fails or the connection between the ticket checking terminal 2000 and the ticket checking server connected to the ticket checking terminal is unstable, the ticket checking server connected to the ticket checking terminal 2000 is offline. When the ticket checking server connected with the ticket checking terminal 2000 is offline, the ticket checking terminal 2000 cannot send the ticket checking data or encrypt the character string to the ticket checking server connected with the ticket checking terminal 2000, and at this time, the ticket checking terminal 2000 cannot complete the ticket checking function. Meanwhile, the ticket checking terminal 2000 knows that the ticket checking server connected thereto is offline based thereon. Certainly, the ticket checking terminal 2000 can also obtain that the ticket checking server originally connected with the ticket checking terminal is offline through other existing manners, which is not described herein again.
The ticket checking terminal 2000 in the on-site ticket checking system of the embodiment of the invention is configured to: when the ticket checking server connected with the ticket checking server is offline, another ticket checking server is selected according to the service list, so that when the ticket checking server is offline, the ticket checking terminal 2000 connected to the ticket checking server automatically selects another ticket checking server to establish local area network connection based on the service list. At this time, the ticket checking terminal 2000 may upload the encrypted character string or the ticket checking data to the another ticket checking server, and receive the checking result sent by the another ticket checking server, thereby continuing to complete the ticket checking.
Based on the above content, in the field ticket checking system provided by the embodiment of the invention, when a certain ticket checking server goes offline, the ticket checking terminal 2000 can automatically select another ticket checking server according to the service list, so that the reliability and stability of the field ticket checking system are further improved, and the safety risk of a ticket checking field is reduced.
In an alternative embodiment, the host server 1010 is configured to: when the slave server 1020 is offline or a new slave server 1020 is added to the local area network, the ticket checking server is newly set for the ticket checking terminal 2000 according to the service list, so that the reliability and the stability of the on-site ticket checking system are further improved, and the safety risk of a ticket checking site is reduced. .
Specifically, when the slave server 1020 goes offline, and the master server 1010 cannot issue the first ticket data to the slave server 1020, the master server 1010 knows that the slave server 1020 goes offline based on the first ticket data. Of course, the master server 1010 may also know to get offline from the slave server 1020 in other existing manners, which will not be described herein. At this time, the master server 1010 deletes the relevant information of the slave server 1020 that has been offline from the service list to update the service list.
The master server 1010 is configured to reset the ticket checking server for the ticket checking terminal 2000 connected with the offline slave server 1020 according to the service list, so as to further improve the reliable stability of the on-site ticket checking system and reduce the security risk of the ticket checking field. For example, the master server 1010 randomly selects one slave server 1020 from the service list, or selects one slave server 1020 with the least number of connected ticket checking terminals 2000 from the service list, and sends an instruction to the selected slave server 1020 to instruct the selected slave server 1020 to actively connect the ticket checking terminal 2000 originally connected with the offline slave server 1020.
Of course, the master server 1010 may also actively connect the ticket checking terminal 2000 connected to the offline slave server 1020 to serve as a ticket checking server of the ticket checking terminal 2000.
In addition, when a new slave server 1020 joins the local area network, the master server 1010 adds the identity, address and role of the newly joined slave server 1020 to the service list to update the service list.
The master server 1010 is configured to set a ticket checking server for the newly joined slave server 1020 according to the service list. For example, the master server 1010 picks up the slave servers 1020 connected to the ticket checking terminal 2000 having a larger number based on the service list, and instructs the slave servers 1020 to disconnect the partial ticket checking terminals 2000 connected thereto. The newly joined slave server 1020 is then instructed to actively connect these disconnected ticket checking terminals 2000.
The present invention may be a computer program product designed separately according to the above-described master service, slave server and ticket checking terminal functions. 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, magnetic, optical, electromagnetic, semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include 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, a punch card or an in-groove protrusion structure having instructions stored thereon, for example, and any suitable combination of the foregoing.
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 over 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 In some embodiments, the various aspects of the present invention are implemented by personalizing electronic circuitry, such as programmable logic circuits, field programmable gate arrays (FPGAs, or Programmable Logic Arrays (PLAs), that execute computer-readable program instructions, with state information of the computer-readable program instructions.
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 (14)
1. A field ticket checking system comprises a plurality of servers and a plurality of ticket checking terminals which are deployed in the same local area network;
one of the servers is set as a master server, and the rest of the servers are set as slave servers;
the main server is connected with a ticket data center through an external network, and the slave server is connected with the main server through the local area network;
the slave server is configured as a ticket checking server, and the ticket checking server is connected with at least one ticket checking terminal through the local area network;
the main server is used for acquiring first ticket data from the ticket data center and issuing the first ticket data to the slave server, and acquiring second ticket data from the ticket checking server and uploading the second ticket data to the ticket data center;
the main server is configured to update the first ticket data according to the second ticket data and issue the updated first ticket data to the slave server when the wireless communication connection between the main server and a ticket data center fails;
wherein, the ticket checking server is used for providing the ticket checking service for the ticket checking terminal connected with the ticket checking server, and comprises: obtaining ticket checking data from the ticket checking terminal, checking the ticket checking data according to the first ticket business data, informing a checking result to the ticket checking terminal, and generating the second ticket business data according to the ticket checking data under the condition of successful checking.
2. The system of claim 1, wherein the plurality of servers are configured to reselect one of the servers as a new primary server according to a predetermined mechanism when an original primary server goes offline.
3. The system of claim 1, wherein the main server is also configured as the ticket proof server.
4. The system of claim 2, wherein the server is configured to: when the ticket data center is taken as an original main server and is offline, first ticket data which are not sent to a slave server are sent to a new main server when the ticket data center is online again, and second ticket data which are not uploaded to the ticket data center are sent to the new main server;
the new main server is used for issuing the first ticket data acquired from the original main server to the auxiliary server and uploading the second ticket data acquired from the original main server to the ticket data center.
5. The system of claim 1, wherein the master server is configured to maintain a list of services; the service list comprises the identification, the address and the role of each ticket checking server;
the role is used for indicating the ticket checking server to be a master server or a slave server.
6. The system of claim 5, wherein the service list further comprises load data for each of the ticket-validating servers;
the load data of the ticket checking server comprises the identification, the address and the number of the ticket checking terminals connected with the ticket checking server.
7. The system of claim 5, wherein the ticketing terminal is further configured to obtain the list of services; the ticket checking terminal acquires the service list, and the method comprises the following steps:
the ticket checking terminal requests the service list from the main server according to a preset period; or,
and the main server issues the updated service list to the ticket checking terminal after updating the service list each time.
8. The system of any of claims 5-7, wherein the ticketing terminal is configured to: and when the ticket checking server connected with the ticket checking server is offline, selecting another ticket checking server according to the service list.
9. The system of any of claims 5-7, wherein the master server is configured to: and when the slave server is offline or a new slave server is added into the local area network, resetting the ticket checking server for the ticket checking terminal according to the service list.
10. The system according to claim 5, wherein a key for ticket checking personnel to select a ticket checking server is provided on the interface of the ticket checking terminal, and the key corresponds to the ticket checking servers in the service list in a one-to-one mode.
11. The system of claim 1, wherein the second ticketing data includes any one or a combination of: ticket number, ticket checking time, ticket checking port identification, check-in identification/check-out identification.
12. The system of claim 1, wherein the local area network is a wired local area network.
13. The system of claim 1, wherein the local area network is a wired and wireless hybrid local area network, the servers are in wired communication, and the ticket checking terminal and the servers are in wireless communication.
14. The system of claim 13, wherein the ticket checking terminal is disposed at a ticket checking site, and the server is within a preset distance range from the ticket checking site.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811644542.7A CN111447247B (en) | 2018-12-29 | 2018-12-29 | On-site ticket checking system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811644542.7A CN111447247B (en) | 2018-12-29 | 2018-12-29 | On-site ticket checking system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111447247A CN111447247A (en) | 2020-07-24 |
| CN111447247B true CN111447247B (en) | 2022-07-12 |
Family
ID=71653874
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811644542.7A Active CN111447247B (en) | 2018-12-29 | 2018-12-29 | On-site ticket checking system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111447247B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113112619B (en) * | 2021-04-07 | 2023-12-05 | 高新现代智能系统股份有限公司 | Ticket checking method, ticket checking equipment, system and storage medium for online ticket card |
| CN113299000A (en) * | 2021-05-20 | 2021-08-24 | 云南师范大学 | Local area network safety voting system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588421A (en) * | 2004-09-02 | 2005-03-02 | 北京网联热线网络有限公司 | Bill test system and bill test method |
| CN1595456A (en) * | 2004-07-06 | 2005-03-16 | 洪朝阳 | A ticket system and using method |
| EP1571798A2 (en) * | 2004-03-02 | 2005-09-07 | Hitachi, Ltd. | Computer system capable of fast failover upon failure |
| CN103714487A (en) * | 2013-12-19 | 2014-04-09 | 广东粤铁科技有限公司 | Ticket system and ticket-buying and ticket-checking method thereof for rail transit |
| CN103731341A (en) * | 2013-12-30 | 2014-04-16 | 广州华多网络科技有限公司 | Method and system for processing instant messaging services |
| CN106789197A (en) * | 2016-12-07 | 2017-05-31 | 高新兴科技集团股份有限公司 | A kind of cluster election method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6567849B2 (en) * | 1998-08-17 | 2003-05-20 | International Business Machines Corporation | System and method for configuring and administering multiple instances of web servers |
| US10771551B2 (en) * | 2017-03-28 | 2020-09-08 | Sap Se | Dynamic topology switch for data replication |
-
2018
- 2018-12-29 CN CN201811644542.7A patent/CN111447247B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1571798A2 (en) * | 2004-03-02 | 2005-09-07 | Hitachi, Ltd. | Computer system capable of fast failover upon failure |
| CN1595456A (en) * | 2004-07-06 | 2005-03-16 | 洪朝阳 | A ticket system and using method |
| CN1588421A (en) * | 2004-09-02 | 2005-03-02 | 北京网联热线网络有限公司 | Bill test system and bill test method |
| CN103714487A (en) * | 2013-12-19 | 2014-04-09 | 广东粤铁科技有限公司 | Ticket system and ticket-buying and ticket-checking method thereof for rail transit |
| CN103731341A (en) * | 2013-12-30 | 2014-04-16 | 广州华多网络科技有限公司 | Method and system for processing instant messaging services |
| CN106789197A (en) * | 2016-12-07 | 2017-05-31 | 高新兴科技集团股份有限公司 | A kind of cluster election method and system |
Non-Patent Citations (2)
| Title |
|---|
| Client/Server Framework-Based Passenger Line Ticket System Using 2-D Barcode on Mobile Phone;Dong Li;《2010 International Conference on E-Business and E-Government》;20100930;全文 * |
| 深圳地铁自动售检票系统信息安全管理建设;牛凤午;《信息科技辑》;20090815;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111447247A (en) | 2020-07-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8923800B2 (en) | Method and apparatus for receiving and providing disaster information | |
| CN111726376B (en) | On-site ticket checking system | |
| AU2014230474B2 (en) | Portable communication device and system and method therefor | |
| CN103118326A (en) | Information pushing method, information pushing device and information pushing system based on geographical location information | |
| CN111447247B (en) | On-site ticket checking system | |
| CN108449723B (en) | Intercom equipment sharing method, intercom equipment and computer readable medium | |
| KR20150116228A (en) | Method for managing contact information and electronic device implementing the same | |
| CN105721450A (en) | Method, device and system for logging in network game | |
| US20140324994A1 (en) | Method and device for transmitting and forwarding a message | |
| KR20220027039A (en) | Disaster evacuation control and management system based on digital twin | |
| US20200066123A1 (en) | Threat detection information distribution system and method | |
| US20150358769A1 (en) | Securing a mobile device by binding to an itinerary | |
| US9986379B2 (en) | Zone-based away messages | |
| US10496274B2 (en) | Geofence parameters based on type of touch on a touch screen | |
| KR20190002573A (en) | Wireless device-based automatic check-in and information sourcing system for safety check management | |
| KR101368780B1 (en) | Multi communication service system and multi communication service method | |
| CN118612234A (en) | Information processing system, information processing device, and computer-readable storage medium | |
| CN103944876B (en) | router access control method, device and router | |
| US10635962B2 (en) | Apparatus for managing baggage, a method for managing baggage and a baggage management system | |
| US20160100354A1 (en) | Terminal device, communication system, and method implemented by the terminal device | |
| US10070275B1 (en) | Device and method for deploying a plurality of mobile devices | |
| US10558722B2 (en) | Provision of on premise ambient service method and apparatus | |
| KR102621301B1 (en) | Smart work support system for non-face-to-face office selling based on metaverse | |
| US10848307B2 (en) | Radio transmission device, reception device, transmission and reception system, and transmission and reception method | |
| JP6068370B2 (en) | Wireless communication apparatus, information communication terminal, communication system control method, and control program |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240614 Address after: Room 201, No. 9 Fengxiang East Street, Yangsong Town, Huairou District, Beijing Patentee after: Youku Culture Technology (Beijing) Co.,Ltd. Country or region after: China Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: ALIBABA GROUP HOLDING Ltd. Country or region before: Cayman Islands |
|
| TR01 | Transfer of patent right |