CN111797070A - Ticket data processing method and device - Google Patents
Ticket data processing method and device Download PDFInfo
- Publication number
- CN111797070A CN111797070A CN201910276765.0A CN201910276765A CN111797070A CN 111797070 A CN111797070 A CN 111797070A CN 201910276765 A CN201910276765 A CN 201910276765A CN 111797070 A CN111797070 A CN 111797070A
- Authority
- CN
- China
- Prior art keywords
- ticketing
- ticket
- data
- acquiring
- ticketing system
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
Abstract
The application relates to a ticket data processing method and device. The method comprises the following steps: the ticket data processing component establishes connection with a first ticket system; acquiring ticketing data from the first ticketing system based on the established connection; and carrying out adaptation processing on the ticket data and then transferring the ticket data to a second ticket system. By using the ticket data processing method and device provided by the embodiments of the application, the ticket data can be migrated quickly, the reloading time is saved, the reloading efficiency is improved, and inaccurate ticket data after migration due to too many data changes in the reloading process can be avoided.
Description
Technical Field
The present application relates to the field of big data processing technologies, and in particular, to a ticket data processing method and apparatus.
Background
With the continuous development of computer networks, network ticket booking has become a popular ticket booking mode for various cinemas. Cinema is often required to provide network ticketing services in cooperation with a cinema ticketing platform that manages member data, order data, ticket data, sales data, and the like. At present, a plurality of cinema ticketing platforms which have the qualification of cooperating with cinemas, such as Yunzhi, Huaxia starry sky, Chenxing, Zhongying Bosheng, Woorda, Yingzhongxin and the like, are available in the market. The theatre may choose to work with any of the theatre ticketing platforms above, however, in some cases, the theatre may change the cooperating theatre ticketing platform to obtain better service.
In the process of replacing a cooperative movie and television ticketing platform, a cinema needs to transfer ticketing data from one ticketing platform to another ticketing platform. The related art is that report data in the original ticketing platform is exported, and then the exported report data is imported into a new ticketing platform. At present, the work of exporting and importing the report data is often manually completed by manpower, and after the ticket data is exported from the ticket platform, the exported ticket data needs to be sorted, so that the sorted ticket data is matched with a new ticket platform. In addition, manual operation is prone to errors, which easily results in that the derived data cannot be adapted to a new ticketing platform.
Therefore, a method for migrating ticket data rapidly and accurately is needed in the related art.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides a ticket data processing method and device.
The ticket data processing method and device provided by the embodiment of the application are specifically realized as follows:
a method of ticketing data processing, the method comprising:
the ticket data processing component establishes connection with a first ticket system;
acquiring ticketing data from the first ticketing system based on the established connection;
and carrying out adaptation processing on the ticket data and then transferring the ticket data to a second ticket system.
A ticketing data processing apparatus comprising a processor and a memory for storing processor-executable instructions that when executed by the processor implement:
establishing connection with a first ticketing system;
acquiring ticketing data from the first ticketing system based on the established connection;
and carrying out adaptation processing on the ticket data and then transferring the ticket data to a second ticket system.
A non-transitory computer readable storage medium, wherein instructions of the storage medium, when executed by a processor, enable the processor to perform the ticket data processing method.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Compared with the migration of the ticket data in the prior art, the ticket data processing method and the ticket data processing device provided by the embodiments of the application have at least the following advantages:
(1) the method of the embodiment of the application can avoid manual participation, realize the processes of automatically connecting the first ticketing system, acquiring the ticketing data, migrating the ticketing data and the like, and accurately migrate the ticketing data to the second ticketing system;
(2) the manual processing mode is slow, the ticket data migration is rapidly completed by utilizing the pre-developed ticket data processing assembly, the reloading time is saved, the reloading efficiency is improved, and the inaccurate ticket data after migration due to too much data change in the reloading process is avoided;
(3) in the ticket data migration process, the adaptation processing of the ticket data is completed, so that the ticket data after migration is adapted to various different ticket systems.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram illustrating an application scenario in accordance with an exemplary embodiment.
FIG. 2 is a schematic diagram illustrating an application scenario in accordance with an exemplary embodiment.
Fig. 3 is a flow diagram illustrating a method of ticket data processing according to an exemplary embodiment.
Fig. 4 is a block diagram illustrating a ticket data processing apparatus according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The following describes a ticket data processing method provided in various embodiments of the present application through a specific application scenario.
One theater in suzhou city (the XX shop in the world movie city in the sea of happy blue) requires the replacement of the current ticketing system flamingo system 100 with the phoenix cloud intelligence system 200. In an embodiment of the application, the cinema may be provided with a ticketing data processing component for reloading the ticketing system, which may for example comprise application software or an SDK. As shown in the application scenario diagram of fig. 1, after receiving the ticketing data processing component, the cinema may install the ticketing data processing component in the client 300, and then use the ticketing data processing component to implement migration of ticketing data from the flamingo system 100 to the phoenix cloud intelligence system 200.
Fig. 2 is a user interface presented by the client 200 after installation of the ticketing data processing components, in which the name of the theater currently needing to be reloaded, i.e., "happy blue sea international movie city (XX shop), is presented, and a ticketing system for the user to select the ticketing system needing to be reloaded, i.e.," from flamingo to phoenix intelligence ", is also provided. It should be noted that, after the client 200 installs the ticketing data processing component, the ticketing data processing component may identify a name of a theater, and may also identify a current ticketing system, and the user interface shown in fig. 2 is only an example.
As shown in fig. 2, the user can also select a module to be migrated in the user interface, and in the ticketing system, various ticketing data are often involved, such as ticket data, card data, box office data, member data, scheduling data, and the like. In the application scenario, a user can select data needing to be migrated in a customized manner, and some data which is not needed or is not involved may not be selected. The "start migration" button in fig. 2 may then be clicked, i.e. ticketing data may be successfully migrated from the flamingo system to the phoenix cloud wisdom.
Therefore, by the ticket data processing method, ticket data required by the user can be quickly and accurately migrated from the original ticket system to the target ticket system without contacting the background data.
The following describes the ticket data processing method in detail with reference to the accompanying drawings. Fig. 3 is a schematic method flow diagram of an embodiment of a ticket data processing method provided in the present application. Although the present application provides method steps as shown in the following examples or figures, more or fewer steps may be included in the method based on conventional or non-inventive efforts. In the case of steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application. The method can be executed sequentially or in parallel (for example, in the context of a parallel processor or a multi-thread process) according to the method shown in the embodiment or the figures when the ticket data processing process or the device is executed in practice.
Specifically, an embodiment of a ticket data processing method provided in the present application is shown in fig. 3, where the method may include:
s301: the ticketing data processing component establishes a connection with a first ticketing system.
S303: based on the established connection, ticket data is obtained from the first ticketing system.
S305: and migrating the ticket data to a second ticket system.
In this embodiment, the ticket data processing component may include a module capable of providing a ticket data migration service between ticket systems, and the ticket data processing component may include an application installed on a client, or a software compression package (SDK) capable of being coupled with a ticket system, or the like. The ticketing system may include a network system capable of providing ticketing services to theaters, including, but not limited to, ticketing services, membership services, sales services, film ordering services, marketing services, and the like. At present, 6000 movie theaters are probably set up in China, most of the movie theaters are provided with network ticketing systems, and the operation of the network ticketing systems depends on the cooperative ticketing system. If the cinema needs to replace the cooperating ticketing systems, the ticketing data processing component can be obtained and installed in the client equipment, and then the replacement among the ticketing systems can be realized.
In this embodiment, the ticketing data processing component may establish a connection with a first ticketing system before performing data processing, and the first ticketing system may include a cinema-collaborative historical ticketing system. In the process of establishing a connection with the first ticketing system, a connection with a database of the first ticketing system may be established in a client of a cinema. In one embodiment, after installing the ticketing data processing component in a client (which may be an administrator computer) of a cinema, the ticketing data processing component may start a corresponding program module, such as java-jar xx.
In this embodiment, after establishing the connection with the first ticketing system, the ticketing data processing component may obtain ticketing data from the first ticketing system based on the established connection. In one embodiment, in the case where the ticketing data processing component establishes a connection with a database of the first ticketing system, the ticketing data can be queried from the first ticketing system using Structured Query Language (SQL). In an actual application scenario, ticket fields involved by different ticket systems are different. In addition, even if the same ticket field is used, it is possible that a different field name is used. Therefore, in the embodiment of the present application, in the process of acquiring the ticket data from the first ticket system by using SQL, SQL may be preset, and the SQL may include a ticket field required by the second ticket system. The ticketing fields involved in the ticketing system may include, for example, the member's card number, card type, card balance, card policy, card issuing theater, member name, member type, member phone, member birthday, status, and the like. In one example, in a first ticketing system, the field name of the member card number is a, and in a second ticketing system, the field name of the member card number is member card number 1, so SQL like "select a as member card number 1from table" can be set to extract the data corresponding to the ticketing field member card number from the first ticketing system. In this embodiment of the application, after the ticket data processing component establishes a connection with the database of the first ticket system, the SQL may be used to access the database of the first ticket system, and obtain data corresponding to the ticket field from the database. Because the preset SQL is matched with the field in the second ticketing system, the acquired ticketing data can be migrated to the second ticketing system for use.
In a practical application scenario, the background server of the first ticketing system may intercept direct access to its database by other users for security and confidentiality of data. Based on this, in the embodiment of the present application, the ticketing data processing component may establish a connection with the first ticketing system by means of user login. In some examples, the ticketing data processing component may log into the first ticketing system using a pre-set account login (e.g., a super-administrator identity). Then, based on the authority of the preset account, data corresponding to a preset ticketing field can be acquired from the first ticketing system. Specifically, in one scenario, after establishing a connection with the first ticketing system through a preset account, the ticketing data processing component may send a data packet capture request to the first ticketing system, and after receiving the data packet capture request, the first ticketing system may send related ticketing data to the ticketing data processing component in response to the data packet capture request.
As described above, the ticket data of the first ticketing system and the ticket data of the second ticketing system may refer to different ticket fields, for example, the ticket fields referred to in the first ticketing system include a member card number, a card balance, a card issuing theater, a member name, a member mobile phone, a member birthday, etc., while the ticket fields referred to in the second ticketing system include a member card number, a card type, a card balance, a card policy, a card issuing theater, a member name, a member type, a member mobile phone, a member birthday, a status, etc.
Based on this, in the embodiment of the present application, after receiving the ticket data, the ticket data processing component may perform adaptation processing on the ticket data. In this embodiment, corresponding adaptation modules may be set for different second ticketing systems, where the adaptation modules are configured to adapt the ticketing data, so that the ticketing data is adapted to data required by the second ticketing systems. In one embodiment, in the ticket data processing component, a user may select identification information corresponding to the second ticket system, so that the ticket data processing component may obtain the identification information corresponding to the second ticket system, and then the ticket data processing component may obtain an adaptation module matched with the second ticket system according to the identification information. After the matched adaptation module is obtained, the adaptation module may be used to perform adaptation processing on the data corresponding to the preset ticketing field, and the data corresponding to the preset field after the adaptation processing is migrated to the second ticketing system. In one example, a user may select the second ticketing system in the ticketing data processing component to be a phoenix cloud ticketing system. After the ticket data processing assembly receives that a user selects the phoenix cloud intelligence ticket system, the adaptation module matched with the phoenix cloud intelligence ticket system can be obtained, and the adaptation module is used for carrying out adaptation processing on the ticket data, so that the processed ticket data can be adapted to the data format of the phoenix cloud intelligence ticket system.
In practical applications, the data structure of the ticketing system is huge, and various business modules are involved, such as a member module, a ticketing module, a sales module, and a card and ticket module, so that a plurality of business modules can be arranged in the ticketing system for storing and managing data of different business modules, for example, the business modules correspond to a data table respectively. In the process of reloading the ticket data by using the ticket data processing assembly, the service of selecting the business module by self definition can be provided for the user. For example, the user may choose to obtain the ticketing data for the membership module and the ticketing module without the ticketing data for the other business modules. After the user selects a corresponding service module from the ticket data processing assembly, the ticket data processing assembly can acquire the identification information of at least one service module defined by the user, and the service module belongs to the sub-module of the first ticket system. Then, according to the identification information of the at least one business module, the ticket data of the at least one business module is obtained from the first ticket system.
In this embodiment of the application, after the ticket data processing component obtains the ticket data, the ticket data may be stored offline. In this way, it is achieved that the ticket data is not lost without a network. And subsequently, when the network bandwidth of the ticket data processing component connected to the second ticket system is larger than a preset threshold value, the ticket data is sent to the second ticket system.
In this embodiment, after the ticket data is migrated to the second ticket system, the second ticket system may have a capability of providing services to theater users, and therefore, a theater may provide ticket services to theater users by using the second ticket system, thereby implementing seamless switching from the first ticket system to the second ticket system without affecting normal ticket services of the theater.
Compared with the migration of the ticket data in the prior art, the ticket data processing method provided by each embodiment of the application has at least the following advantages:
(1) the method of the embodiment of the application can avoid manual participation, realize the processes of automatically connecting the first ticketing system, acquiring the ticketing data, migrating the ticketing data and the like, and accurately migrate the ticketing data to the second ticketing system;
(2) the manual processing mode is slow, the ticket data migration is rapidly completed by utilizing the pre-developed ticket data processing assembly, the reloading time is saved, the reloading efficiency is improved, and the inaccurate ticket data after migration due to too much data change in the reloading process is avoided;
(3) in the ticket data migration process, the adaptation processing of the ticket data is completed, so that the ticket data after migration is adapted to various different ticket systems.
Corresponding to the above ticket data processing method, as shown in fig. 4, the present application further provides a ticket data processing apparatus, including a processor and a memory for storing processor executable instructions, where the processor executes the instructions to implement:
establishing connection with a first ticketing system;
acquiring ticketing data from the first ticketing system based on the established connection;
the ticket data is subjected to adaptation processing and then is migrated to a second ticket system
Optionally, in an embodiment of the application, the processor when implementing the step of obtaining the ticket data from the first ticketing system based on the established connection includes:
acquiring a preset Structured Query Language (SQL), wherein the SQL comprises ticket fields required by a second ticket system;
and accessing a database of the first ticketing system by using the structured query language, and acquiring data corresponding to the ticketing fields from the database.
Optionally, in an embodiment of the application, the processor when implementing the step of obtaining the ticket data from the first ticketing system based on the established connection includes:
logging in the first ticketing system by using a preset account;
and acquiring data corresponding to a preset ticket field from the first ticket system based on the authority of the preset account.
Optionally, in an embodiment of the application, when the processor migrates the ticket data after performing the adaptation processing on the ticket data to the second ticket system, the processor includes:
acquiring identification information corresponding to a second ticketing system;
acquiring an adaptation module matched with the second ticketing system according to the identification information;
utilizing the adaptation module to perform adaptation processing on the data corresponding to the preset ticket field;
and migrating the data corresponding to the preset field after the adaptation processing to the second ticketing system.
Optionally, in an embodiment of the application, the processor, when implementing the step of acquiring the ticket data from the first ticket system based on the established connection, includes:
acquiring identification information of at least one service module defined by a user, wherein the service module belongs to a sub-module of the first ticketing system;
and acquiring the ticket data of the at least one service module from the first ticket system according to the identification information of the at least one service module.
Optionally, in an embodiment of the application, when the processor migrates the ticket data after performing the adaptation processing on the ticket data to the second ticket system, the processor includes:
storing the ticket data after the adaptation processing in an off-line manner;
and under the condition that the network bandwidth connected to a second ticketing system is greater than a preset threshold value, the ticketing data is sent to the second ticketing system.
Optionally, in an embodiment of the application, after the implementing step of migrating the ticket data to the second ticket system after performing the adaptation process on the ticket data, the processor further includes:
and providing the ticket service for the user by utilizing the second ticket system.
In another aspect, the present application further provides a computer-readable storage medium, on which computer instructions are stored, and the instructions, when executed, implement the steps of the method according to any of the above embodiments.
The computer readable storage medium may include physical means for storing information, typically by digitizing the information for storage on a medium using electrical, magnetic or optical means. The computer-readable storage medium according to this embodiment may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, 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 specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (15)
1. A method of ticket data processing, the method comprising:
the ticket data processing component establishes connection with a first ticket system;
acquiring ticketing data from the first ticketing system based on the established connection;
and carrying out adaptation processing on the ticket data and then transferring the ticket data to a second ticket system.
2. The method of claim 1, wherein the obtaining ticketing data from the first ticketing system based on the established connection comprises:
acquiring a preset Structured Query Language (SQL), wherein the SQL comprises ticket fields required by a second ticket system;
and accessing a database of the first ticketing system by using the structured query language, and acquiring data corresponding to the ticketing fields from the database.
3. The method of claim 1, wherein the obtaining ticketing data from the first ticketing system based on the established connection comprises:
logging in the first ticketing system by using a preset account;
and acquiring data corresponding to a preset ticket field from the first ticket system based on the authority of the preset account.
4. The method of claim 3, wherein the migrating the ticketing data to a second ticketing system after the adapting comprises:
acquiring identification information corresponding to a second ticketing system;
acquiring an adaptation module matched with the second ticketing system according to the identification information;
utilizing the adaptation module to perform adaptation processing on the data corresponding to the preset ticket field;
and migrating the data corresponding to the preset field after the adaptation processing to the second ticketing system.
5. The method of claim 1, wherein the obtaining ticketing data from the first ticketing system based on the established connection comprises:
acquiring identification information of at least one service module defined by a user, wherein the service module belongs to a sub-module of the first ticketing system;
and acquiring the ticket data of the at least one service module from the first ticket system according to the identification information of the at least one service module.
6. The method of claim 1, wherein the migrating the ticketing data to a second ticketing system after the adapting comprises:
storing the ticket data after the adaptation processing in an off-line manner;
and under the condition that the network bandwidth connected to a second ticketing system is greater than a preset threshold value, the ticketing data is sent to the second ticketing system.
7. The method of claim 1, wherein after the migration of the ticket data into a second ticketing system after the adapting, the method further comprises:
and providing the ticket service for the user by utilizing the second ticket system.
8. A ticketing data processing apparatus comprising a processor and a memory for storing processor-executable instructions that when executed by the processor implement:
establishing connection with a first ticketing system;
acquiring ticketing data from the first ticketing system based on the established connection;
and carrying out adaptation processing on the ticket data and then transferring the ticket data to a second ticket system.
9. The apparatus of claim 8, wherein the processor, when performing the step of obtaining ticketing data from the first ticketing system based on the established connection, comprises:
acquiring a preset Structured Query Language (SQL), wherein the SQL comprises ticket fields required by a second ticket system;
and accessing a database of the first ticketing system by using the structured query language, and acquiring data corresponding to the ticketing fields from the database.
10. The apparatus of claim 8, wherein the processor, when performing the step of obtaining ticketing data from the first ticketing system based on the established connection, comprises:
logging in the first ticketing system by using a preset account;
and acquiring data corresponding to a preset ticket field from the first ticket system based on the authority of the preset account.
11. The apparatus of claim 10, wherein the processor, when migrating the ticketing data into a second ticketing system after the step of implementing adapts the ticketing data, comprises:
acquiring identification information corresponding to a second ticketing system;
acquiring an adaptation module matched with the second ticketing system according to the identification information;
utilizing the adaptation module to perform adaptation processing on the data corresponding to the preset ticket field;
and migrating the data corresponding to the preset field after the adaptation processing to the second ticketing system.
12. The apparatus of claim 8, wherein the processor, when performing the step of obtaining ticketing data from the first ticketing system based on the established connection, comprises:
acquiring identification information of at least one service module defined by a user, wherein the service module belongs to a sub-module of the first ticketing system;
and acquiring the ticket data of the at least one service module from the first ticket system according to the identification information of the at least one service module.
13. The apparatus of claim 8, wherein the processor, when migrating the ticketing data into a second ticketing system after the step of implementing adapts the ticketing data, comprises:
storing the ticket data after the adaptation processing in an off-line manner;
and under the condition that the network bandwidth connected to a second ticketing system is greater than a preset threshold value, the ticketing data is sent to the second ticketing system.
14. The apparatus of claim 8, wherein the processor, after the migration of the ticketing data into the second ticketing system after the adapting step, further comprises:
and providing the ticket service for the user by utilizing the second ticket system.
15. A non-transitory computer readable storage medium, instructions in which, when executed by a processor, enable the processor to perform the ticketing data processing method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910276765.0A CN111797070A (en) | 2019-04-08 | 2019-04-08 | Ticket data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910276765.0A CN111797070A (en) | 2019-04-08 | 2019-04-08 | Ticket data processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111797070A true CN111797070A (en) | 2020-10-20 |
Family
ID=72805224
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910276765.0A Pending CN111797070A (en) | 2019-04-08 | 2019-04-08 | Ticket data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111797070A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113435862A (en) * | 2021-07-20 | 2021-09-24 | 支付宝(杭州)信息技术有限公司 | Bill processing method and device based on mailbox |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1541363A (en) * | 2001-02-28 | 2004-10-27 | �Ҵ���˾ | Data loading from remote data source |
| CN1763745A (en) * | 2005-09-06 | 2006-04-26 | 阎海强 | Structure oriented data migration method and system |
| CN103218402A (en) * | 2013-03-19 | 2013-07-24 | 上海宝信软件股份有限公司 | General database data structure, data migratory system and method thereof |
| CN103440273A (en) * | 2013-08-06 | 2013-12-11 | 北京航空航天大学 | Data cross-platform migration method and device |
| CN104462119A (en) * | 2013-09-18 | 2015-03-25 | 腾讯科技（深圳）有限公司 | Data migration method and device |
| CN105205117A (en) * | 2015-09-09 | 2015-12-30 | 郑州悉知信息科技股份有限公司 | Data table migrating method and device |
| CN105868343A (en) * | 2016-03-28 | 2016-08-17 | 上海携程商务有限公司 | Database migration method and system |
| CN106021517A (en) * | 2016-05-24 | 2016-10-12 | 乐视控股（北京）有限公司 | Network data inputting method and device |
| CN107423334A (en) * | 2017-04-24 | 2017-12-01 | 云宏信息科技股份有限公司 | A kind of automatic data migration method and device for supporting multi-data source |
| CN107977462A (en) * | 2017-12-21 | 2018-05-01 | 泰康保险集团股份有限公司 | Data migration method and device |
-
2019
- 2019-04-08 CN CN201910276765.0A patent/CN111797070A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1541363A (en) * | 2001-02-28 | 2004-10-27 | �Ҵ���˾ | Data loading from remote data source |
| CN1763745A (en) * | 2005-09-06 | 2006-04-26 | 阎海强 | Structure oriented data migration method and system |
| CN103218402A (en) * | 2013-03-19 | 2013-07-24 | 上海宝信软件股份有限公司 | General database data structure, data migratory system and method thereof |
| CN103440273A (en) * | 2013-08-06 | 2013-12-11 | 北京航空航天大学 | Data cross-platform migration method and device |
| CN104462119A (en) * | 2013-09-18 | 2015-03-25 | 腾讯科技（深圳）有限公司 | Data migration method and device |
| CN105205117A (en) * | 2015-09-09 | 2015-12-30 | 郑州悉知信息科技股份有限公司 | Data table migrating method and device |
| CN105868343A (en) * | 2016-03-28 | 2016-08-17 | 上海携程商务有限公司 | Database migration method and system |
| CN106021517A (en) * | 2016-05-24 | 2016-10-12 | 乐视控股（北京）有限公司 | Network data inputting method and device |
| CN107423334A (en) * | 2017-04-24 | 2017-12-01 | 云宏信息科技股份有限公司 | A kind of automatic data migration method and device for supporting multi-data source |
| CN107977462A (en) * | 2017-12-21 | 2018-05-01 | 泰康保险集团股份有限公司 | Data migration method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113435862A (en) * | 2021-07-20 | 2021-09-24 | 支付宝(杭州)信息技术有限公司 | Bill processing method and device based on mailbox |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107450979B (en) | Block chain consensus method and device | |
| US10353913B2 (en) | Automating extract, transform, and load job testing | |
| CN114662159A (en) | Data processing method, device and equipment | |
| US8620998B2 (en) | Mobile application deployment for distributed computing environments | |
| US10140355B2 (en) | Compiling extract, transform, and load job test data cases | |
| CN110008018A (en) | A kind of batch tasks processing method, device and equipment | |
| CN107066519B (en) | Task detection method and device | |
| CN112162915A (en) | Test data generation method, device, equipment and storage medium | |
| CN105704188A (en) | Deployment method and apparatus of applications and services | |
| TWI690187B (en) | Service updating method, device and system | |
| CN111767144A (en) | Transaction routing determination method, device, equipment and system for transaction data | |
| CN112463290A (en) | Method, system, apparatus and storage medium for dynamically adjusting the number of computing containers | |
| CN110602163B (en) | File uploading method and device | |
| US11636139B2 (en) | Centralized database system with geographically partitioned data | |
| US10803246B2 (en) | Decomposing composite product reviews | |
| US9609076B1 (en) | Criteria-based data push | |
| CN111797070A (en) | Ticket data processing method and device | |
| CN109842498B (en) | Client configuration method, server, client and electronic equipment | |
| CN110109986B (en) | Task processing method, system, server and task scheduling system | |
| CN106548331B (en) | Method and device for determining release sequence | |
| CN110971642B (en) | Data processing method and device for cloud computing platform | |
| CN114661826A (en) | Data processing method, device and equipment based on block chain | |
| CN114594944A (en) | Application construction system and device | |
| CN109542401A (en) | A kind of Web development approach, device, storage medium and processor | |
| CN111796864A (en) | Data verification method and device |
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 | ||
| CB02 | Change of applicant information |
Address after: 310052 room 306, floor 3, building 1, No. 699, Wangshang Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Hangzhou taopiao film and Television Culture Co.,Ltd. Address before: 310052 room 306, floor 3, building 1, No. 699, Wangshang Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant before: Hangzhou Chenxi Multimedia Technology Co.,Ltd. |
|
| CB02 | Change of applicant information |