CN106776698A - Ticket information method for refreshing and system based on optimization caching - Google Patents
Ticket information method for refreshing and system based on optimization caching Download PDFInfo
- Publication number
- CN106776698A CN106776698A CN201610998016.5A CN201610998016A CN106776698A CN 106776698 A CN106776698 A CN 106776698A CN 201610998016 A CN201610998016 A CN 201610998016A CN 106776698 A CN106776698 A CN 106776698A
- Authority
- CN
- China
- Prior art keywords
- ticket
- information
- refreshing
- cache
- level
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present invention discloses the ticket information method for refreshing based on optimization caching, including：On ticket information exhibition platform, ticket information refreshing corresponding with ticketing service rank is set and represents strategy, represent for carrying out corresponding ticket information refreshing according to ticketing service rank；The information data of ticketing service is received, when obtaining ticketing service for first order ticketing service with ticketing service hierarchical policy set in advance contrast according to information data, then the ticket information for calling caching to obtain ticketing service from database in real time carries out refreshing and represents；When obtaining ticketing service for second level ticketing service according to information data and ticketing service hierarchical policy set in advance contrast, then detect that ticketing service represents request, there is when representing request of ticketing service, the ticket information of acquisition ticketing service carries out refreshing and represents from database.The present invention solves the problems, such as that the refresh rate of network ticket booking platform displaying ticket information in the prior art is slow.
Description
Technical Field
The invention relates to the technical field of ticket booking systems, in particular to a ticket information refreshing method and system based on optimized cache.
Background
With the rapid development of internet technology, the wide distribution and the rapid transmission based on the internet bring much convenience to the work and the life of people. People are more and more active in shopping behaviors based on the internet, and the trouble that a user needs to go to a site for shopping is eliminated in internet shopping, so that the user can order goods at home.
Along with the expansion of the working and living range of people, the network ticket booking platform breaking regional limitation comes up, and various tickets for life, such as airplane tickets, train tickets, bus tickets, ball tickets, movie tickets, concert tickets and the like, can be ordered through the network ticket booking platform. The network ticket booking platform facilitates the daily life of users, but the network ticket booking information is large in amount and changes every moment, and how to display ticket information to the users in real time is a great challenge for the network ticket booking platform. The number and variety of network tickets are large, and various information data are changed in real time, which is obviously infeasible to process and present to users in real time by human.
The existing network ticket booking platform provides real-time ticket data updating conditions for users in a data caching mode, but the pressure of frequent ticket information refreshing on platform caching is gradually increased, and information refreshing is slow, so that some important information is not known by the users, and the use experience of the users is not facilitated. Moreover, for some popular tickets, the information needs to be updated in real time, for some branched tickets, the search and refresh can be carried out through the input of a user, if the scheme of carrying out the real-time refresh is unified, the pressure of the platform cache can be greatly increased, and more resources can be wasted; if the search refreshing is carried out through the user input, a lot of important ticket information can be missed.
Therefore, it is an urgent problem to be solved in the art to provide an intelligent refresh presentation scheme for ticket information on a ticket booking platform according to the actual needs of a user.
Disclosure of Invention
In view of the above, the invention provides a ticket information refreshing method and system based on optimized cache, which solve the technical problem that no intelligent ticket information refreshing display exists on a ticket platform in the prior art.
In order to solve the technical problem, the invention provides a ticket information refreshing method based on optimized cache, which comprises the following steps:
setting a ticket information refreshing and displaying strategy corresponding to the ticket grade on a ticket information displaying platform, and refreshing and displaying corresponding ticket information according to the ticket grade;
receiving information data of the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is a first-level ticket according to comparison between the information data and a preset ticket grading strategy;
when the ticket is obtained by comparing the information data with a preset ticket grading strategy and is a second-level ticket, detecting a display request of the ticket, and acquiring ticket information of the ticket from the database for refreshing and displaying when the display request of the ticket exists;
when the ticket is obtained as a third-level ticket by comparing the information data with a preset ticket grading strategy, calling the cache to acquire the ticket information of the ticket from the database in real time according to the preset real-time display times to perform refreshing display of the real-time display times; and when the real-time display times are exceeded, detecting the display request of the ticket, and when the display request of the ticket exists, acquiring the ticket information of the ticket from the database to perform refreshing display.
Further, when receiving information data of a ticket, and comparing the information data with a preset ticket classification policy to obtain that the ticket is a first-level ticket, calling a cache to obtain the ticket information of the ticket from a database in real time for refreshing and displaying, further comprising:
and acquiring a time period/place for receiving the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is acquired as a first-level ticket by comparing the time period/place with a preset corresponding relation between the time period/place of the ticket and the ticket level.
Further, when receiving information data of a ticket, and comparing the information data with a preset ticket classification policy to obtain that the ticket is a first-level ticket, calling a cache to obtain the ticket information of the ticket from a database in real time for refreshing and displaying, further comprising:
and acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset correspondence between the importance degree of the ticket and the ticket level.
Further, wherein the method comprises:
receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
Further, wherein the caching further comprises: redis caching; the real-time display times further include: 50-2000 times.
In another aspect, the present invention further provides a system for refreshing ticket information based on optimized cache, including: the system comprises a setting module, a first-stage ticket business display module, a second-stage ticket business display module and a third-stage ticket business display module; wherein,
the setting module is used for setting a ticket information refreshing and displaying strategy corresponding to the ticket level on a ticket information displaying platform and for refreshing and displaying the corresponding ticket information according to the ticket level;
the first-stage ticket business presentation module is used for receiving information data of the ticket business, and calling a cache to acquire the ticket business information of the ticket business from a database in real time for refreshing presentation when the ticket business is the first-stage ticket business according to the comparison between the information data and a preset ticket business grading strategy;
the second-stage ticket showing module is used for detecting the showing request of the ticket when the ticket is obtained by comparing the information data with a preset ticket grading strategy and is a second-stage ticket, and obtaining the ticket information of the ticket from the database for refreshing and showing when the showing request of the ticket exists;
the third-level ticket showing module is used for calling the cache to acquire the ticket information of the ticket from the database in real time according to the preset real-time showing times to carry out refreshing showing of the real-time showing times when the ticket is the third-level ticket according to the comparison between the information data and the preset ticket grading strategy; and when the real-time display times are exceeded, detecting the display request of the ticket, and when the display request of the ticket exists, acquiring the ticket information of the ticket from the database to perform refreshing display.
Further, the first-level ticket service presenting module is further configured to:
and acquiring a time period/place for receiving the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is acquired as a first-level ticket by comparing the time period/place with a preset corresponding relation between the time period/place of the ticket and the ticket level.
Further, the first-level ticket service presenting module is further configured to:
and acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset correspondence between the importance degree of the ticket and the ticket level.
Further, wherein the system comprises: the ticket information refreshing frequency distribution module is used for:
receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
Further, wherein the caching further comprises: redis caching; the real-time display times further include: 50-2000 times.
Compared with the prior art, the ticket information refreshing method and system based on the optimized cache have the advantages that:
(1) the ticket information refreshing method and system based on optimized cache analyze the data information refreshing level of each ticket, acquire the data information from the database for displaying according to the refreshing frequency corresponding to the preset information refreshing level, distribute the corresponding cache information refreshing mechanism according to different ticket information characteristics, and solve the problem of slow refreshing speed of the ticket information displayed by the network ticket booking platform in the prior art.
(2) The ticket information refreshing method and system based on optimized cache automatically distribute the information refreshing frequency according to the refreshing frequency characteristics required by each ticket on the network ticket booking platform, save the cache resources and reduce the data updating pressure of the cache while ensuring the timely refreshing of the ticket data information.
Of course, it is not necessary for any product in which the present invention is practiced to achieve all of the above-described technical effects simultaneously.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a schematic flowchart of a ticket information refreshing method based on optimized cache according to embodiment 1 of the present invention;
fig. 2 is a schematic flowchart of a ticket information refreshing method based on optimized cache according to embodiment 2 of the present invention;
fig. 3 is a schematic structural diagram of an optimized cache-based ticketing information refresh system according to embodiment 3 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.
Example 1
As shown in fig. 1, which is a schematic flow chart of the ticket information refreshing method based on optimized cache according to this embodiment, the method described in this embodiment solves the technical problem that no ticket information is intelligently refreshed and displayed on a ticket platform in the prior art. The ticket information refreshing method based on the optimized cache comprises the following steps:
step 101, setting a ticket information refreshing and displaying strategy corresponding to the ticket level on a ticket information displaying platform, and performing corresponding ticket information refreshing and displaying according to the ticket level.
Wherein the ticket information at least comprises: the fare of the ticket, the time of use of the ticket and the current remaining amount. When a user orders a ticket, the ticket price, the service time and the current remaining amount of the ticket needing to be ordered can be browsed through the ticket information display platform, and whether the user needs to order the ticket can be actually determined by combining the user with the ticket information display platform.
The current ticket information refreshing and showing is realized by a mode that all ticket information is acquired from a database through a system cache and is shown on a platform, but a large amount of ticket information is updated on the ticket information showing platform every moment, and the updating and showing of the ticket information through the cache can greatly increase the cache pressure of the ticket information showing platform, so that the problem of slow ticket information refreshing and showing speed is caused, and the user is not favorable for timely and accurately acquiring related information of the ticket.
Step 102, inputting the information data of the ticket to the ticket information display platform according to the ticket information provided by the ticket supplier.
The ticket information display platform receives the ticket information provided by each ticket supplier and displays the ticket information to the user, so that the function of conveniently searching various tickets and ordering by the user is realized.
And 103, according to the received information data of the ticket, comparing the received information data with a preset ticket grading strategy to obtain that the ticket is a first-level ticket, calling a cache to acquire the latest ticket information of the ticket from a database in real time for refreshing and displaying.
Wherein, the ticket classification strategy further comprises: and the corresponding relation between the information data of the ticket and the ticket grade.
Preferably, in this embodiment, the ticket level is divided into three levels, and the ticket level can also be divided in a finer step according to the actual situation, ticket information data is acquired in real time and displayed based on a cache in comparison with the ticket setting of a more important level, and a passive display mechanism based on a user request search is set for the ticket of a less important level or a less high user attention, so that cache resources of a platform are saved to a certain extent, the working pressure of the cache is reduced, and the timeliness and the accuracy of displaying the ticket information with a higher user attention are improved.
And step 104, comparing the information data with a preset ticket classification strategy to obtain that the ticket is a second-level ticket, and displaying the ticket in real time without calling a cache.
And 105, when the user searches the second-level ticket, generating a display request of the ticket on the ticket information display platform.
And 106, detecting whether the display request of the ticket exists on a ticket information display platform, and acquiring the latest ticket information of the ticket from the database for refreshing and displaying when the display request of the ticket exists.
The database is used for storing information data of each ticket, including ticket information such as ticket price, service time, remaining amount and the like of the ticket.
And 107, when the ticket is the third-level ticket obtained by comparing the information data with a preset ticket classification strategy, calling the cache to acquire the latest ticket information of the ticket from the database in real time according to the preset real-time display times to perform refresh display of the real-time display times, and detecting the display times of the third-level ticket.
And 108, stopping calling the cache to perform real-time refreshing display on the information data of the third-level ticket when the display frequency of the third-level ticket is detected to exceed the real-time display frequency.
And step 109, when the user searches for the third-level ticket, generating a presentation request of the ticket on the ticket information presentation platform.
And step 110, detecting whether a presentation request of the third-level ticket exists, and acquiring the latest ticket information of the ticket from the database for refreshing presentation when the presentation request of the ticket exists.
The ticket information refreshing method based on the optimized cache is characterized in that corresponding cache information refreshing mechanisms are allocated according to different ticket information characteristics, and the problem that the refreshing speed of the ticket information displayed by a network ticket booking platform in the prior art is low is solved.
Example 2
Fig. 2 is a schematic flow chart of a ticket information refreshing method based on optimized cache according to this embodiment. In this embodiment, specific contents of a timing/fixed point ticket refreshing mechanism based on a cache are described on the basis of embodiment 1, and the method in this embodiment includes the following steps:
step 201, setting a ticket information refreshing and displaying strategy corresponding to the ticket level on a ticket information displaying platform, and performing corresponding ticket information refreshing and displaying according to the ticket level.
Step 202, inputting the information data of the ticket to the ticket information display platform according to the ticket information provided by the ticket supplier.
Step 203, obtaining a time period/place for receiving the ticket, and calling a cache to obtain the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is obtained as a first-level ticket according to the time period/place and the preset corresponding relation between the time period/place of the ticket and the ticket level.
And 204, acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset corresponding relation between the importance degree of the ticket and the ticket level.
And step 205, when the ticket is obtained as a second-level ticket by comparing the information data with a preset ticket classification strategy, the cache is not called for real-time display.
And step 206, when the user searches the second-level ticket, generating a presentation request of the ticket on the ticket information presentation platform.
And step 207, detecting whether the display request of the ticket exists on a ticket information display platform, and acquiring the latest ticket information of the ticket from the database for refreshing and displaying when the display request of the ticket exists.
And 208, when the ticket is the third-level ticket obtained by comparing the information data with a preset ticket classification strategy, calling the cache to acquire the latest ticket information of the ticket from the database in real time according to the preset real-time display times to perform refresh display of the real-time display times, and detecting the display times of the third-level ticket.
And 209, stopping calling the cache to perform real-time refreshing display on the information data of the third-level ticket when the display frequency of the third-level ticket is detected to exceed the real-time display frequency.
Step 210, when the user searches for the third-level ticket, generating a presentation request of the ticket on a ticket information presentation platform.
And step 211, detecting whether the third-level ticket display request exists, and acquiring the latest ticket information of the ticket from the database for refreshing display when the third-level ticket display request exists.
Step 212, receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
Wherein, the cache further comprises: redis caching; the real-time display times further include: 50-2000 times.
Redis cache, a key-value storage system, supports relatively more stored value types, including string, list, set, and zset. These data types all support push/pop, add/remove, and intersect union and difference, and richer operations, and these operations are all atomic. On this basis, Redis supports various different ways of ordering. In order to ensure efficiency, data is cached in a memory, updated data can be periodically written into a disk or modification operation can be periodically written into an additional recording file, master-slave synchronization is realized on the basis, and the cache-based data refreshing speed and accuracy are improved.
According to the ticket information refreshing method based on the optimized cache, the information refreshing frequency is automatically distributed according to the refreshing frequency characteristics required by each ticket on the network ticket booking platform, the ticket data information is guaranteed to be refreshed in time, cache resources are saved, and the data updating pressure of the cache is reduced.
Example 3
As shown in fig. 3, which is a schematic structural diagram of the optimized cache-based ticketing information refresh system according to this embodiment, the optimized cache-based ticketing information refresh system according to this embodiment is used for implementing the optimized cache-based ticketing information refresh method according to the foregoing embodiment. The system of the embodiment comprises: a setting module 301, a first-level ticket showing module 302, a second-level ticket showing module 303 and a third-level ticket showing module 304.
The setting module 301 is coupled to the first-level ticket information presentation module 302, and is configured to set, on a ticket information presentation platform, a ticket information refresh presentation policy corresponding to a ticket level, and to perform corresponding ticket information refresh presentation according to the ticket level.
The first-level ticket business presentation module 302 is coupled with the setting module 301 and the second-level ticket business presentation module 302, and is configured to receive information data of a ticket business, and call a cache to obtain ticket business information of the ticket business from a database in real time for refresh presentation when the ticket business is a first-level ticket business obtained by comparing the information data with a preset ticket business grading strategy.
The second-level ticket presenting module 303 is coupled to the second-level ticket presenting module 302 and the third-level ticket presenting module 304, and is configured to detect a presentation request of the ticket when the ticket is obtained as a second-level ticket by comparing the information data with a preset ticket classification policy, and obtain the ticket information of the ticket from the database for refresh presentation when the presentation request of the ticket exists.
The third-level ticket showing module 304 is coupled to the second-level ticket showing module 303, and configured to call the cache to obtain the ticket information of the ticket from the database in real time according to the preset real-time showing times to perform refresh showing of the real-time showing times when the ticket is the third-level ticket according to comparison between the information data and a preset ticket grading policy; and when the real-time display times are exceeded, detecting the display request of the ticket, and when the display request of the ticket exists, acquiring the ticket information of the ticket from the database to perform refreshing display.
Further, the first-level ticket service presenting module 302 is configured to:
and acquiring a time period/place for receiving the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is acquired as a first-level ticket by comparing the time period/place with a preset corresponding relation between the time period/place of the ticket and the ticket level.
The first-level ticket presentation module 302 is further configured to:
and acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset correspondence between the importance degree of the ticket and the ticket level.
The above system further comprises: a ticket information refresh frequency allocation module 305 coupled to the third-level ticket display module 304, for:
receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
The cache further comprises: redis caching; the real-time display times further include: 50-2000 times.
According to the embodiments, the ticket information refreshing method and system based on the optimized cache have the following beneficial effects:
(1) the ticket information refreshing method and system based on optimized cache analyze the data information refreshing level of each ticket, acquire the data information from the database for displaying according to the refreshing frequency corresponding to the preset information refreshing level, distribute the corresponding cache information refreshing mechanism according to different ticket information characteristics, and solve the problem of slow refreshing speed of the ticket information displayed by the network ticket booking platform in the prior art.
(2) The ticket information refreshing method and system based on optimized cache automatically distribute the information refreshing frequency according to the refreshing frequency characteristics required by each ticket on the network ticket booking platform, save the cache resources and reduce the data updating pressure of the cache while ensuring the timely refreshing of the ticket data information.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, 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.
Although some specific embodiments of the present invention have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustrative purposes only and are not intended to limit the scope of the present invention. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.
Claims (10)
1. A ticket information refreshing method based on optimized cache is characterized by comprising the following steps:
setting a ticket information refreshing and displaying strategy corresponding to the ticket grade on a ticket information displaying platform, and refreshing and displaying corresponding ticket information according to the ticket grade;
receiving information data of the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is a first-level ticket according to comparison between the information data and a preset ticket grading strategy;
when the ticket is obtained by comparing the information data with a preset ticket grading strategy and is a second-level ticket, detecting a display request of the ticket, and acquiring ticket information of the ticket from the database for refreshing and displaying when the display request of the ticket exists;
when the ticket is obtained as a third-level ticket by comparing the information data with a preset ticket grading strategy, calling the cache to acquire the ticket information of the ticket from the database in real time according to the preset real-time display times to perform refreshing display of the real-time display times; and when the real-time display times are exceeded, detecting the display request of the ticket, and when the display request of the ticket exists, acquiring the ticket information of the ticket from the database to perform refreshing display.
2. The optimized cache based ticketing information refresh method of claim 1, wherein receiving information data of a ticketing, calling a cache to obtain ticketing information of the ticketing from a database in real time for refresh presentation when the ticketing is obtained as a first-level ticketing according to comparison of the information data and a preset ticketing classification policy, and further comprising:
and acquiring a time period/place for receiving the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is acquired as a first-level ticket by comparing the time period/place with a preset corresponding relation between the time period/place of the ticket and the ticket level.
3. The optimized cache based ticketing information refresh method of claim 1, wherein receiving information data of a ticketing, calling a cache to obtain ticketing information of the ticketing from a database in real time for refresh presentation when the ticketing is obtained as a first-level ticketing according to comparison of the information data and a preset ticketing classification policy, and further comprising:
and acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset correspondence between the importance degree of the ticket and the ticket level.
4. The optimized cache based ticketing information refresh method of claim 1, further comprising:
receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
5. The optimized cache based ticketing information refresh method of claim 1, wherein said caching further comprises: redis caching; the real-time display times further include: 50-2000 times.
6. An optimized cache based ticketing information refresh system, comprising: the system comprises a setting module, a first-stage ticket business display module, a second-stage ticket business display module and a third-stage ticket business display module; wherein,
the setting module is used for setting a ticket information refreshing and displaying strategy corresponding to the ticket level on a ticket information displaying platform and for refreshing and displaying the corresponding ticket information according to the ticket level;
the first-stage ticket business presentation module is used for receiving information data of the ticket business, and calling a cache to acquire the ticket business information of the ticket business from a database in real time for refreshing presentation when the ticket business is the first-stage ticket business according to the comparison between the information data and a preset ticket business grading strategy;
the second-stage ticket showing module is used for detecting the showing request of the ticket when the ticket is obtained by comparing the information data with a preset ticket grading strategy and is a second-stage ticket, and obtaining the ticket information of the ticket from the database for refreshing and showing when the showing request of the ticket exists;
the third-level ticket showing module is used for calling the cache to acquire the ticket information of the ticket from the database in real time according to the preset real-time showing times to carry out refreshing showing of the real-time showing times when the ticket is the third-level ticket according to the comparison between the information data and the preset ticket grading strategy; and when the real-time display times are exceeded, detecting the display request of the ticket, and when the display request of the ticket exists, acquiring the ticket information of the ticket from the database to perform refreshing display.
7. The optimized cache-based ticketing information refresh system of claim 6, wherein said first level ticketing presentation module is further configured to:
and acquiring a time period/place for receiving the ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing presentation when the ticket is acquired as a first-level ticket by comparing the time period/place with a preset corresponding relation between the time period/place of the ticket and the ticket level.
8. The optimized cache-based ticketing information refresh system of claim 6, wherein said first level ticketing presentation module is further configured to:
and acquiring the importance degree of the received ticket, and calling a cache to acquire the ticket information of the ticket from a database in real time for refreshing and showing when the ticket is acquired as a first-level ticket by comparing the importance degree with the preset correspondence between the importance degree of the ticket and the ticket level.
9. The optimized cache-based ticketing information refresh system of claim 6, further comprising: the ticket information refreshing frequency distribution module is used for:
receiving information data of the ticket, comparing the information data with a preset ticket grading strategy to obtain a ticket grade of the ticket, and comparing the information data with a corresponding relation between the preset ticket grade and a ticket information refreshing frequency to obtain the ticket information refreshing frequency of the ticket;
and calling a cache for updating the ticket information based on the ticket, and acquiring the ticket information of the ticket from the database for updating and displaying.
10. The system for optimally caching based ticketing information for refreshing of claim 6, wherein said cache further comprises: redis caching; the real-time display times further include: 50-2000 times.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610998016.5A CN106776698A (en) | 2016-11-14 | 2016-11-14 | Ticket information method for refreshing and system based on optimization caching |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610998016.5A CN106776698A (en) | 2016-11-14 | 2016-11-14 | Ticket information method for refreshing and system based on optimization caching |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106776698A true CN106776698A (en) | 2017-05-31 |
Family
ID=58973504
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610998016.5A Pending CN106776698A (en) | 2016-11-14 | 2016-11-14 | Ticket information method for refreshing and system based on optimization caching |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106776698A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107403270A (en) * | 2017-07-21 | 2017-11-28 | 携程旅游网络技术（上海）有限公司 | Freight space information automatic scheduling method, system, storage medium and electronic equipment |
| CN113010586A (en) * | 2021-04-21 | 2021-06-22 | 携程旅游网络技术（上海）有限公司 | Method, working platform, equipment and medium for realizing ordering of ticket information |
| CN115525667A (en) * | 2022-10-12 | 2022-12-27 | 赫中企云(北京)信息服务有限公司 | Rule hot updating method during program operation |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070130237A1 (en) * | 2005-12-06 | 2007-06-07 | International Business Machines Corporation | Transient cache storage |
| CN101278540A (en) * | 2005-10-03 | 2008-10-01 | 阿玛得斯两合公司 | System and method for maintaining consistency of cached content in a multi-tier software system designed to interface with a large database |
| CN102474715A (en) * | 2009-08-13 | 2012-05-23 | 雅虎公司 | System and method for precaching information on a mobile device |
| CN105630982A (en) * | 2015-12-25 | 2016-06-01 | 中国民航信息网络股份有限公司 | Flight data caching method and system |
-
2016
- 2016-11-14 CN CN201610998016.5A patent/CN106776698A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101278540A (en) * | 2005-10-03 | 2008-10-01 | 阿玛得斯两合公司 | System and method for maintaining consistency of cached content in a multi-tier software system designed to interface with a large database |
| US20070130237A1 (en) * | 2005-12-06 | 2007-06-07 | International Business Machines Corporation | Transient cache storage |
| CN102474715A (en) * | 2009-08-13 | 2012-05-23 | 雅虎公司 | System and method for precaching information on a mobile device |
| CN105630982A (en) * | 2015-12-25 | 2016-06-01 | 中国民航信息网络股份有限公司 | Flight data caching method and system |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107403270A (en) * | 2017-07-21 | 2017-11-28 | 携程旅游网络技术（上海）有限公司 | Freight space information automatic scheduling method, system, storage medium and electronic equipment |
| CN107403270B (en) * | 2017-07-21 | 2020-10-02 | 携程旅游网络技术（上海）有限公司 | Cabin space information automatic scheduling method, system, storage medium and electronic equipment |
| CN113010586A (en) * | 2021-04-21 | 2021-06-22 | 携程旅游网络技术（上海）有限公司 | Method, working platform, equipment and medium for realizing ordering of ticket information |
| CN115525667A (en) * | 2022-10-12 | 2022-12-27 | 赫中企云(北京)信息服务有限公司 | Rule hot updating method during program operation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2596425B1 (en) | Membership tracking and data eviction in mobile middleware scenarios | |
| US10963144B2 (en) | Graphically organizing content in a user interface to a software application | |
| US7912812B2 (en) | Smart data caching using data mining | |
| EP3876107B1 (en) | Apparatus, systems, and methods for analyzing movements of target entities | |
| US10783213B2 (en) | Flexible graph system for accessing organization information | |
| EP2874077B1 (en) | Stateless database cache | |
| US7822775B2 (en) | Method and system for managing complex database information | |
| US12430335B2 (en) | System and method for improved cache utilization using an organizational memory to generate a dashboard | |
| CN109542892A (en) | Method, device and system for realizing relation of real-time database | |
| CN105809314A (en) | Method and system for asset management | |
| US20130238665A1 (en) | Managing records displayed in a tree list | |
| CN104462455A (en) | Method and device for displaying and processing network data | |
| CN103699611B (en) | Microblog flow information extracting method based on dynamic digest technology | |
| US20090164486A1 (en) | Business intelligence data extraction on demand | |
| CN108304454B (en) | Invoice data real-time aggregation device based on big data | |
| US10789262B2 (en) | Progressive chart rendering | |
| US7593957B2 (en) | Hybrid data provider | |
| EP3493073A1 (en) | Workflow driven database partitioning | |
| CN106776698A (en) | Ticket information method for refreshing and system based on optimization caching | |
| CN102945536A (en) | Data presentation system and method adaptable to distributed hydrological water resource database | |
| CN112527917B (en) | Data processing method and device | |
| US10698965B2 (en) | Database query based recommendation engine | |
| US20130041897A1 (en) | Content-based information aggregation | |
| CN104252468B (en) | For maximizing the method and its system of the information gain of continuous events | |
| CN102129468B (en) | Method for displaying customizable cluster state |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170531 |
|
| RJ01 | Rejection of invention patent application after publication |