CN112804344B - Scenic spot ticketing system - Google Patents

Scenic spot ticketing system Download PDF

Info

Publication number
CN112804344B
CN112804344B CN202110123500.4A CN202110123500A CN112804344B CN 112804344 B CN112804344 B CN 112804344B CN 202110123500 A CN202110123500 A CN 202110123500A CN 112804344 B CN112804344 B CN 112804344B
Authority
CN
China
Prior art keywords
ticket
cloud
ticketing
server
local
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
Application number
CN202110123500.4A
Other languages
Chinese (zh)
Other versions
CN112804344A (en
Inventor
危勇刚
程进
龙竹桑
杨军
李杰梅
罗磊
谢秋敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hunan Huilv Cloud Network Technology Co ltd
Original Assignee
Hunan Huilv Cloud Network Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hunan Huilv Cloud Network Technology Co ltd filed Critical Hunan Huilv Cloud Network Technology Co ltd
Priority to CN202110123500.4A priority Critical patent/CN112804344B/en
Publication of CN112804344A publication Critical patent/CN112804344A/en
Application granted granted Critical
Publication of CN112804344B publication Critical patent/CN112804344B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2379Updates performed during online database operations; commit processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0603Catalogue ordering
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/14Travel agencies
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07BTICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B1/00Machines for printing and issuing tickets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/141Setup of application sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/146Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

The scenic spot ticketing system comprises the cloud ticketing server and the local ticketing server, wherein ticket data between the cloud ticketing server and the local ticketing server are synchronized through long-term network connection, so that the ticket data are always consistent. In the setting mode, the local server and the cloud can synchronize all information in time, so that the information in the two ticket service servers is kept consistent, and even if any one server fails, the synchronized ticket information stored in the other server can also ensure the complete interaction process of ticket selling and checking. The situation that the ticket service server cannot run due to power failure and network outage and ticket service operation interruption in a scenic spot is caused is effectively avoided, high-efficiency stable operation of the scenic spot is guaranteed, and service data of a ticket service system can be well stored timely and synchronously.

Description

Scenic spot ticketing system
Technical Field
The invention relates to the technical field of scenic spot ticket selling and checking, in particular to a scenic spot ticketing system.
Background
The current scenic spot ticketing system on the market is usually deployed in a scenic spot local area or a cloud end, and when ticket selling and checking are carried out, the scenic spot ticketing system is operated based on a single server, under the common condition, network access connection is normal, scenic spot power supply is stable, and the system can be stably operated. The tourist can purchase tickets in scenic spot ticketing windows, self-service ticket machines and network ticketing channels, the system can correspondingly generate codes of each ticket in disorder, the codes of the tickets are converted into two-dimensional codes to be printed on paper tickets or electronic two-dimensional code tickets are pushed to mobile phones and other devices for buying the tickets, when the tourist visits the scenic spot to a park for playing by swiping the gate through the two-dimensional codes on the paper tickets or the electronic tickets, the gate is connected to a ticketing server ticket code library through a network through the codes for identifying the tickets to perform data comparison with the currently identified ticket codes, and the check result is returned to realize ticket checking.
However, in many scenic spots, due to various factors such as remote geographical locations and complex field conditions, the network and power supply in the scenic spot are often unstable, and once power failure and network outage occur, the ticketing server fails to transmit data with the ticketing end and the core-selling end, each link in the ticketing service in the scenic spot is affected, so that the system is in a paralyzed state, and the ticketing operation in the scenic spot is interrupted.
Disclosure of Invention
The technical problem to be solved by the invention is to overcome the defects of the prior art and provide a scenic spot ticketing system which is simple and practical, stable in operation, less influenced by environment and strong in data storage capacity.
In order to solve the technical problems, the technical scheme provided by the invention is as follows:
a scenic spot ticketing system comprises a cloud ticketing server, wherein the cloud ticketing server is used for putting tickets with different attributes and different selling prices in more than one scenic spot on the channel ticketing section of an online scene, generating corresponding first ticket data after obtaining orders from the channel ticketing end of the online scene, and storing the corresponding first ticket data in the cloud; the cloud ticket service server is also used for receiving ticket checking information from the cloud ticket checking terminal, comparing the ticket checking information with first ticket data stored in the cloud terminal to complete ticket checking verification, and updating the first ticket data;
the system also comprises a local ticketing server deployed in a corresponding scenic spot, wherein the local ticketing server is used for generating tickets with different attributes and different selling prices to be put on the channel ticketing terminals of an off-line scene according to the scenic spot playing items and the basic ticket types of the corresponding scenic spot, and generating corresponding second ticket data after obtaining orders from the channel ticketing sections of the off-line scene and storing the second ticket data in the local; the local ticket business server is also used for receiving ticket checking information from the local ticket checking terminal, comparing the ticket checking information with second ticket data stored locally to complete ticket checking verification, and updating the second ticket data;
and the local ticket server and the cloud ticket server perform data synchronization through long-term network connection to keep the contents of the first ticket data and the second ticket data consistent when the network is smooth.
As a further improvement of the above technical solution:
and when the local ticketing server and the cloud ticketing server are connected through the network for data synchronization, a unique synchronization ID is generated each time for data transmission.
And when the network between the local ticket business server and the cloud ticket business server is not smooth, the cloud ticket business server does not perform ticket checking and checking on the ticket data which is provided with the synchronous ID and is not updated through the ticket checking and checking.
Cloud ticket checking terminal and high in the clouds ticket service server wireless or wired communication connection, cloud ticket checking terminal includes: the system comprises a wireless mobile terminal provided with a cancel-after-verification small program and a handset with a wireless mobile network connection function;
the local ticket checking terminal is in wireless or wired communication connection with the local ticket service server, and comprises: a gate arranged in the scenic spot or at the door, and a handset.
When the network between the local ticketing server and the cloud ticketing server is not smooth, or the network between the cloud ticket checking terminal and the cloud ticketing server is not smooth, the ticket is sold and checked according to the following rules:
and when the local ticket service server receives ticket checking information from the local ticket checking terminal and compares the ticket checking information with second ticket data stored locally, and the ticket checking information is found to exist in the second ticket data and the second ticket data is not updated through ticket checking, the ticket checking is finished and the second ticket data is updated.
Local ticketing service server and the network between the high in the clouds ticketing service server is unobstructed, and when the network between cloud ticket checking terminal and the high in the clouds ticketing service server is unobstructed, the ticket is sold and checked according to the following rules:
and when the cloud ticket service server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with second ticket data stored in the cloud end, the second ticket data is found to have the ticket information and not have a synchronous ID, and the second ticket data is not updated through ticket checking, and then the ticket checking is checked and updated.
When the network between the local ticket business server and the local ticket checking terminal is not smooth, the ticket is sold and checked according to the following rules:
the cloud ticket checking terminal is adopted for checking tickets, and when the cloud ticket business server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with first ticket data stored in the cloud terminal, and the first ticket data is found to have the ticket information and is not updated through ticket checking, the ticket checking is completed, and the first ticket data is updated.
When the network of the local ticket checking terminal is not smooth, the ticket is sold and checked according to the following rules:
the local ticket checking terminal is adopted for checking the ticket, and the local ticket checking terminal adopts a symmetric encryption mode to check and punch the paper ticket issued by the local ticket business server.
Compared with the prior art, the invention has the advantages that:
the scenic spot ticketing system comprises the cloud ticketing server and the local ticketing server, wherein ticket data between the cloud ticketing server and the local ticketing server are synchronized through long-term network connection, so that the ticket data are always consistent. In the setting mode, the local server and the cloud can synchronize all information in time, so that the information in the two ticket service servers is kept consistent, and even if any one server fails, the synchronized ticket information stored in the other server can also ensure the complete interaction process of ticket selling and checking. The situation that the ticket service server cannot run due to power failure and network outage and ticket service operation interruption in a scenic spot is caused is effectively avoided, high-efficiency stable operation of the scenic spot is guaranteed, and service data of a ticket service system can be well stored timely and synchronously.
Drawings
Fig. 1 is a schematic diagram of a scenic spot ticketing system of the present invention.
Detailed Description
In order to facilitate an understanding of the invention, the invention will be described more fully and in detail below with reference to the accompanying drawings and preferred embodiments, but the scope of the invention is not limited to the specific embodiments below.
Example (b):
as shown in fig. 1, the scenic spot ticketing system of this embodiment includes a cloud ticketing server, where the cloud ticketing server is configured to put tickets with different attributes and different selling prices in more than one scenic spot on a channel ticketing section of an online scene, and generate corresponding first ticket data after obtaining an order from the channel ticketing end of the online scene, and store the first ticket data in a cloud; the cloud ticket business server is also used for receiving ticket checking information from the cloud ticket checking terminal, comparing the ticket checking information with the first ticket data stored in the cloud terminal to complete ticket checking and verification, and updating the first ticket data;
the system also comprises a local ticketing server deployed in a corresponding scenic spot, wherein the local ticketing server is used for generating tickets with different attributes and different selling prices to be put on the channel ticketing terminal of an off-line scene according to scenic spot playing items and basic ticket types of the corresponding scenic spot, and generating corresponding second ticket data after obtaining orders from a channel ticketing section of the off-line scene and storing the second ticket data in the local; the local ticket service server is also used for receiving ticket checking information from the local ticket checking terminal, comparing the ticket checking information with second ticket data stored locally to finish ticket checking and verification, and updating the second ticket data;
when the network is smooth, the local ticket server and the cloud ticket server perform data synchronization through long-term network connection so as to keep the contents of the first ticket data and the second ticket data consistent. In the setting mode, the local server and the cloud can synchronize all information in time, so that the information in the two ticket service servers is kept consistent, and even if any one server fails, the synchronized ticket information stored in the other server can also ensure the complete interaction process of ticket selling and checking. The situation that the ticket service server cannot run due to power failure and network outage and ticket service operation interruption in a scenic spot is caused is effectively avoided, high-efficiency stable operation of the scenic spot is guaranteed, and service data of a ticket service system can be well stored timely and synchronously.
In this embodiment, when the local ticketing server and the cloud ticketing server perform data synchronization through long-term network connection, a unique synchronization ID is generated each time for data transmission. When the network between the local ticketing server and the cloud ticketing server is not smooth, the cloud ticketing server does not perform ticket checking and checking on ticket data which is provided with a synchronous ID and is not updated through ticket checking and checking, but performs ticket checking and checking on synchronized ticket information through the local ticket checking terminal. The setting mode ensures that one ticket information can be checked only once, avoids data abnormity caused by repeated ticket checking and verification of two ticket servers, and ensures the accuracy of operation.
In this embodiment, cloud ticket checking terminal and high in the clouds ticketing service server wireless or wired communication are connected, and cloud ticket checking terminal includes: the system comprises a wireless mobile terminal provided with a cancel-after-verification small program and a handset with a wireless mobile network connection function; the local ticket checking terminal is connected with the local ticket service server in a wireless or wired communication manner, and comprises: a gate arranged in the scenic spot or at the door, and a handset.
In this embodiment, when the outside network connection failure of scenic spot leads to synchronous exception, namely the network between local ticketing server and the cloud ticketing server is not unobstructed, sell and examine the ticket according to the following rule:
the local ticketing server and the cloud ticketing server cannot synchronize ticket data with each other, so that ticket selling and checking information is stored in the local ticketing server and the cloud ticketing server, when tourists visit scenic spots to check tickets, tickets can be checked through the local ticket checking terminal when the tourists buy the tickets through the local ticketing server, and tickets can be checked through the cloud ticket checking terminal when the tourists buy the tickets through the cloud ticketing server. And when the connection of the external network of the scenic spot is recovered, the external network is synchronized again.
In this embodiment, when the high in the clouds ticketing server trouble, when the network between cloud ticket checking terminal and the high in the clouds ticketing server is unobstructed promptly, the visitor arrives the scenic spot and plays behind the trouble, and local ticketing server still can normal operating, therefore the visitor can purchase the ticket locally, later checks through local ticket checking terminal. And the ticket purchasing information of the tourists who purchase tickets before the fault is synchronized to the local ticket service server, so that the ticket checking is carried out by adopting the local ticket checking terminal, and when the local ticket service server receives the ticket checking information from the local ticket checking terminal and compares the ticket checking information with second ticket data stored in the local, the ticket checking verification is finished and the second ticket data is updated when the ticket checking information is found to exist in the second ticket data and the second ticket data is not updated through the ticket checking verification.
In this embodiment, the network between local ticketing server and the high in the clouds ticketing server is unobstructed, and when the network between cloud ticket checking terminal and the high in the clouds ticketing server is unobstructed, sell and examine the ticket according to following rule: the cloud ticket checking terminal is adopted for checking tickets, when the cloud ticket business server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with second ticket data stored in the cloud end, the second ticket data is found to have the ticket information and not have a synchronous ID, and the second ticket data is not updated through ticket checking, checking and checking are completed. Namely: and the synchronized second ticket data is verified by the local ticket checking terminal, and the unsynchronized second ticket data is verified by the cloud ticket checking terminal.
In this embodiment, when scenic spot outage trouble or intranet trouble, local ticketing server and local when examining the network between the ticket terminal unobstructed, the visitor comes the scenic spot to play behind the trouble, and high in the clouds ticketing server still can normal operating this moment, therefore the visitor can pass through high in the clouds ticketing server and buy the ticket and examine the ticket through cloud examination ticket terminal. And the ticket purchasing information of the tourists who purchase tickets before the fault is synchronized to the cloud ticket business server, so that the tourists can check and sell tickets through the cloud ticket checking terminal. When the cloud ticket business server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with first ticket data stored in the cloud terminal, and the first ticket data is found to have the ticket checking information and is not updated through ticket checking, ticket checking is completed, and the first ticket data is updated.
In this embodiment, when the network of the local ticket checking terminal is not smooth, that is, the local gate is disconnected, after the tourist purchases the ticket and takes out the paper ticket, the ticket can be sold and checked according to the following rules: the local ticket checking terminal is adopted for checking the ticket, and the paper ticket issued by the local ticket business server is checked and punched by adopting a symmetrical encryption mode. And after the network is recovered, synchronizing.
The above description is only a preferred embodiment of the present invention, and the scope of the present invention is not limited to the above-described examples. It should be apparent to those skilled in the art that modifications and variations can be made without departing from the technical spirit of the present invention.

Claims (6)

1. A scenic spot ticketing system comprises a cloud ticketing server, wherein the cloud ticketing server is used for putting tickets with different attributes and different selling prices in more than one scenic spot on the channel ticketing section of an online scene, generating corresponding first ticket data after obtaining orders from the channel ticketing end of the online scene, and storing the corresponding first ticket data in the cloud; the cloud ticket service server is also used for receiving ticket checking information from the cloud ticket checking terminal, comparing the ticket checking information with first ticket data stored in the cloud terminal to complete ticket checking verification, and updating the first ticket data;
the method is characterized in that: the system also comprises a local ticketing server deployed in a corresponding scenic spot, wherein the local ticketing server is used for generating tickets with different attributes and different selling prices to be put on the channel ticketing terminals of an off-line scene according to the scenic spot playing items and the basic ticket types of the corresponding scenic spot, and generating corresponding second ticket data after obtaining orders from the channel ticketing sections of the off-line scene and storing the second ticket data in the local; the local ticket business server is also used for receiving ticket checking information from the local ticket checking terminal, comparing the ticket checking information with second ticket data stored locally to complete ticket checking verification, and updating the second ticket data;
the local ticket server and the cloud ticket server perform data synchronization through long-distance network connection when the network is smooth so as to keep the contents of the first ticket data and the second ticket data consistent;
when the local ticketing server and the cloud ticketing server are connected through a network for data synchronization, a unique synchronization ID is synchronously generated each time for data transmission;
and when the network between the local ticket business server and the cloud ticket business server is not smooth, the cloud ticket business server does not carry out ticket checking and verification on the ticket data which is provided with the synchronous ID and is not updated through the ticket checking and verification.
2. The scenic spot ticketing system of claim 1, wherein: cloud ticket checking terminal and high in the clouds ticketing service server wireless or wired communication are connected, cloud ticket checking terminal includes: the system comprises a wireless mobile terminal provided with a verification and cancellation applet and a handset with a wireless mobile network connection function;
the local ticket checking terminal is in wireless or wired communication connection with the local ticket service server, and comprises: the system comprises a gate arranged in a scenic spot or at a doorway and a handset.
3. The scenic spot ticketing system of any one of claims 1-2, wherein: when the network between the local ticketing server and the cloud ticketing server is not smooth, or the network between the cloud ticket checking terminal and the cloud ticketing server is not smooth, the ticket is sold and checked according to the following rules:
and when the local ticket service server receives ticket checking information from the local ticket checking terminal and compares the ticket checking information with second ticket data stored locally, and the ticket checking information is found to exist in the second ticket data and the second ticket data is not updated through ticket checking, the ticket checking is finished and the second ticket data is updated.
4. A scenic spot ticketing system as claimed in claim 1, wherein: the local ticketing server and the network between the cloud ticketing servers are not smooth, and when the network between the cloud ticket checking terminal and the cloud ticketing servers is smooth, the tickets are sold and checked according to the following rules:
and when the cloud ticket service server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with second ticket data stored in the cloud end, the second ticket data is found to have the ticket information and not have a synchronous ID, and the second ticket data is not updated through ticket checking, and then the ticket checking is checked and updated.
5. A scenic spot ticketing system as claimed in any one of claims 1 to 2, wherein: when the network between the local ticket business server and the local ticket checking terminal is not smooth, the ticket is sold and checked according to the following rules:
the cloud ticket checking terminal is adopted for checking tickets, and when the cloud ticket business server receives ticket checking information from the cloud ticket checking terminal and compares the ticket checking information with first ticket data stored in the cloud terminal, and the first ticket data is found to have the ticket information and is not updated through ticket checking, the ticket checking is completed, and the first ticket data is updated.
6. A scenic spot ticketing system as claimed in any one of claims 1 to 2, wherein: when the network of the local ticket checking terminal is not smooth, the ticket is sold and checked according to the following rules:
the local ticket checking terminal is adopted for checking the ticket, and the local ticket checking terminal adopts a symmetric encryption mode to check and punch the paper ticket issued by the local ticket business server.
CN202110123500.4A 2021-01-29 2021-01-29 Scenic spot ticketing system Active CN112804344B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110123500.4A CN112804344B (en) 2021-01-29 2021-01-29 Scenic spot ticketing system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110123500.4A CN112804344B (en) 2021-01-29 2021-01-29 Scenic spot ticketing system

Publications (2)

Publication Number Publication Date
CN112804344A CN112804344A (en) 2021-05-14
CN112804344B true CN112804344B (en) 2022-10-21

Family

ID=75812691

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110123500.4A Active CN112804344B (en) 2021-01-29 2021-01-29 Scenic spot ticketing system

Country Status (1)

Country Link
CN (1) CN112804344B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113516786A (en) * 2021-08-13 2021-10-19 上海哔哩哔哩科技有限公司 Gate ticket checking method and system
CN114490701B (en) * 2022-03-11 2022-07-05 环球数科集团有限公司 Intelligent scenic spot offline ticket data processing method, system and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104702593A (en) * 2015-01-16 2015-06-10 苏州江河行信息技术有限公司 Electronic certificate online and offline integrated verification system and method
CN204480330U (en) * 2015-03-24 2015-07-15 磁石网络科技(长沙)有限公司 Tickets Systems
CN204537226U (en) * 2015-04-22 2015-08-05 湖南城市学院 A kind of tourist attractions ticket point management control system
CN106779678A (en) * 2016-11-24 2017-05-31 深圳市久通物联科技股份有限公司 A kind of public transport ticket checking method and terminal based on Quick Response Code Yu high in the clouds wallet
CN109741147A (en) * 2019-01-04 2019-05-10 深圳前海微众银行股份有限公司 Card certificate management method, device, equipment and computer readable storage medium
CN111726376A (en) * 2019-03-19 2020-09-29 阿里巴巴集团控股有限公司 On-site ticket checking system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075353A (en) * 2007-06-14 2007-11-21 高英杰 Electronic multifunctional ticket system
CN101901505A (en) * 2010-05-27 2010-12-01 邵贵平 Offline electronic ticketing system and method thereof
US20130325525A1 (en) * 2012-05-21 2013-12-05 Boost3, Llc Systems and methods for an integrated online portal and marketplace for event-related items
CN103714487A (en) * 2013-12-19 2014-04-09 广东粤铁科技有限公司 Ticket system and ticket-buying and ticket-checking method thereof for rail transit
CN103646335B (en) * 2013-12-27 2017-07-04 税友软件集团股份有限公司 A kind of electronic invoice detection method and device
CN109657763A (en) * 2017-10-10 2019-04-19 方正国际软件(北京)有限公司 A kind of application method of electronic ticket and electronic ticket
CN110796745A (en) * 2018-08-01 2020-02-14 北京思源理想控股集团有限公司 Ticket checking system and method based on ibeacon module
CN111970160B (en) * 2020-09-07 2023-02-10 福建票付通信息科技有限公司 Ticket system architecture

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104702593A (en) * 2015-01-16 2015-06-10 苏州江河行信息技术有限公司 Electronic certificate online and offline integrated verification system and method
CN204480330U (en) * 2015-03-24 2015-07-15 磁石网络科技(长沙)有限公司 Tickets Systems
CN204537226U (en) * 2015-04-22 2015-08-05 湖南城市学院 A kind of tourist attractions ticket point management control system
CN106779678A (en) * 2016-11-24 2017-05-31 深圳市久通物联科技股份有限公司 A kind of public transport ticket checking method and terminal based on Quick Response Code Yu high in the clouds wallet
CN109741147A (en) * 2019-01-04 2019-05-10 深圳前海微众银行股份有限公司 Card certificate management method, device, equipment and computer readable storage medium
CN111726376A (en) * 2019-03-19 2020-09-29 阿里巴巴集团控股有限公司 On-site ticket checking system

Also Published As

Publication number Publication date
CN112804344A (en) 2021-05-14

Similar Documents

Publication Publication Date Title
CN112804344B (en) Scenic spot ticketing system
US9462266B2 (en) Display apparatus, display apparatus fault analysis system and display apparatus fault analysis method
CN106487578B (en) Error recovery method, and Internet of things system and charging system applying same
CN103186466B (en) Information interactive testing device and method based on association automatic generating test case
CN105933888B (en) A kind of eSIM card method for burn-recording and device based on NFC
CN106126367A (en) A kind of self checking method and system of file
CN105814591A (en) Verification information transmission method and terminal
JP2013140453A5 (en)
CN103095678A (en) Method of managing incoming commands related to contactless applications within a wireless apparatus
CN107566449A (en) Portable power source leasing method, system, mobile terminal, server, lease terminal
CN110908875B (en) Inspection method and device based on operation terminal
CN107078806A (en) Optical transceiver apparatus and method
CN104283926A (en) Data synchronization method, device and server
CN104486413A (en) Information processing system
CN107464382A (en) Integrated tax control machine and tax control method
CN108133425A (en) Method, apparatus of settling a claim and computer readable storage medium
CN108021580A (en) A kind of data synchronization updating method and its system
CN104702593A (en) Electronic certificate online and offline integrated verification system and method
CN101753516B (en) Synchronous play method based on LED text advertisements
CN106993015A (en) Synchronous method, system and the security server of transaction
CN109542647A (en) Information transmitting administrative method and device, electronic equipment, storage medium
CN102891704A (en) Communication information medium and method for realizing conversion of communication information
CN110475215A (en) Message editing, transmission and the method for display and its server and terminal
CN106303011A (en) The method and device that a kind of theme obtains
JP2008147754A (en) Communication device and communication management system

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