CN115696441A - Call bill processing method, device, equipment and storage medium - Google Patents
Call bill processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115696441A CN115696441A CN202110852472.XA CN202110852472A CN115696441A CN 115696441 A CN115696441 A CN 115696441A CN 202110852472 A CN202110852472 A CN 202110852472A CN 115696441 A CN115696441 A CN 115696441A
- Authority
- CN
- China
- Prior art keywords
- compression
- ticket
- processed
- original
- user
- 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
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The method compresses an original ticket according to a preset compression strategy, wherein the preset compression strategy comprises a dynamic quota compression strategy, a session-level traffic combination compression strategy, a user-level traffic combination compression strategy, a data algorithm compression strategy and the like, and further combines the compressed tickets according to the ticket charging attributes of the tickets to obtain a target ticket. In addition, the preset compression strategies of the embodiment of the application comprise different compression strategies, so that the compression requirements on the data service call ticket under different scenes are met.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing a ticket.
Background
With the domestic 4G communication, the rapid development of the internet and the commercial use of 5G communication, the number of mobile network users of three operators is also rapidly increasing. The user internet demand is rapidly increased, which results in the volume of data service telephone bills being multiplied.
The increase of the amount of the data service call bills has more and more requirements on hardware resources, particularly network bandwidth, from the network elements to the links of collection, charging, user inquiry and the like, and more severe tests are brought to the timeliness and stability of system processing and user perception guarantee.
In order to relieve the system pressure, the existing method is to expand hardware resources, increase network bandwidth and the like so as to meet the processing requirements of the existing data service ticket. However, the hardware resource expansion and the network bandwidth increase the resource cost and the maintenance cost, and become the non-trivial profit loss of enterprises.
Disclosure of Invention
The application provides a method, a device, equipment and a storage medium for processing telephone bills, which reduce bandwidth consumption by compressing and combining telephone bill quantity and solve the problems in the prior art.
In a first aspect, an embodiment of the present application provides a method for processing a ticket, where the method includes the following steps:
acquiring an original ticket to be processed;
compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises one or more of a dynamic quota compression strategy, a session-level telephone traffic combination compression strategy, a user-level telephone traffic combination compression strategy and a data algorithm compression strategy;
and combining the compressed call tickets according to the call ticket charging attributes of the compressed call tickets to obtain the target call ticket.
In a possible implementation manner, the preset compression policy includes a dynamic quota compression policy, where the dynamic quota compression policy includes a maximum slice quota and a maximum duration which can be authorized by a plurality of users by surfing the internet once;
the compressing the original ticket to be processed according to a preset compression strategy comprises the following steps:
determining the maximum slice quota and duration of single-time internet access authorization of the user corresponding to the original ticket to be processed according to the maximum slice quota and duration of single-time internet access authorization of the plurality of users;
and compressing the original ticket to be processed according to the maximum slice quota and duration corresponding to the original ticket to be processed and authorized by the user for single surfing.
In a possible implementation manner, the preset compression policy includes a session-level traffic merging compression policy;
the compressing the original bill to be processed according to a preset compression strategy comprises the following steps:
determining a target Internet Protocol (IP) request and/or service corresponding to the session in the original ticket to be processed;
and performing session-level telephone traffic combination and compression on the original telephone bill to be processed according to the target IP request and/or the service.
In a possible implementation manner, the preset compression policy includes a user-level traffic merging compression policy, and the user-level traffic merging compression policy includes a correspondence between a user category and a merging compression policy;
the compressing the original ticket to be processed according to a preset compression strategy comprises the following steps:
determining the user category of the user corresponding to the original ticket to be processed;
determining a target combination compression strategy according to the corresponding relation and the user category of the user corresponding to the original call ticket to be processed;
and compressing the original ticket to be processed according to the target combination compression strategy.
In one possible implementation, the preset compression policy includes a data algorithm compression policy, the data algorithm compression policy includes huffman coding and/or string table (LZW) coding;
the compressing the original ticket to be processed according to a preset compression strategy comprises the following steps:
and compressing the original ticket to be processed according to the Huffman code and/or the LZW code.
In a possible implementation manner, the obtaining an original ticket to be processed includes:
and adjusting network element parameters according to a preset threshold value and a preset time period to obtain the original call ticket to be processed.
In a second aspect, an embodiment of the present application provides a device for processing a ticket, where the device includes:
the ticket acquisition module is used for acquiring an original ticket to be processed;
the first processing module is used for compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises one or more of a dynamic quota compression strategy, a session-level telephone traffic combination compression strategy, a user-level telephone traffic combination compression strategy and a data algorithm compression strategy;
and the second processing module is used for combining the compressed call tickets according to the call ticket charging attributes of the compressed call tickets to obtain the target call tickets.
In a possible implementation manner, the preset compression policy includes a dynamic quota compression policy, where the dynamic quota compression policy includes a maximum slice quota and a duration that a plurality of users can authorize at a time when surfing the internet;
the first processing module is specifically configured to:
determining the maximum slice quota and duration of single-time internet access authorization of the user corresponding to the original ticket to be processed according to the maximum slice quota and duration of single-time internet access authorization of the plurality of users;
and compressing the original ticket to be processed according to the maximum slice quota and duration corresponding to the original ticket to be processed and authorized by the user for single surfing.
In a possible implementation manner, the preset compression policy includes a session-level traffic merging compression policy;
the first processing module is specifically configured to:
determining a target IP request and/or service corresponding to the session in the original ticket to be processed;
and according to the target IP request and/or the service, carrying out session-level telephone traffic combination compression on the original telephone bill to be processed.
In a possible implementation manner, the preset compression policy includes a user-level traffic merging compression policy, and the user-level traffic merging compression policy includes a correspondence between a user category and a merging compression policy;
the first processing module is specifically configured to:
determining the user category of the user corresponding to the original ticket to be processed;
determining a target combination compression strategy according to the corresponding relation and the user category of the user corresponding to the original ticket to be processed;
and compressing the original ticket to be processed according to the target combination compression strategy.
In one possible implementation, the preset compression policy includes a data algorithm compression policy, and the data algorithm compression policy includes huffman coding and/or LZW coding;
the first processing module is specifically configured to:
and compressing the original ticket to be processed according to the Huffman code and/or the LZW code.
In a possible implementation manner, the ticket obtaining module is specifically configured to:
and adjusting network element parameters according to a preset threshold value and a preset time period to obtain the original call ticket to be processed.
In a third aspect, an embodiment of the present application provides a ticket processing device, including:
a processor;
a memory; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor, the computer program comprising instructions for performing the method of the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and the computer program causes a server to execute the method according to the first aspect.
In a fifth aspect, the present application provides a computer program product, which includes computer instructions for executing the method of the first aspect by a processor.
The method comprises the steps of obtaining an original ticket to be processed, and further compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises a dynamic quota compression strategy, a session-level traffic combination compression strategy, a user-level traffic combination compression strategy, a data algorithm compression strategy and the like, and combining the compressed tickets according to the ticket charging attributes of the compressed tickets to obtain a target ticket. In addition, the preset compression strategies of the embodiment of the application comprise different compression strategies, so that the compression requirements on the data service call ticket under different scenes are met. In addition, after the conversation list is compressed, the conversation lists are further combined, so that the number of the finally obtained call tickets is small, the data transmission efficiency is improved, and the network bandwidth consumption is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic diagram of a call ticket processing system architecture provided in an embodiment of the present application;
fig. 2 is a schematic flow diagram of a call ticket processing method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another call ticket processing method provided in the embodiment of the present application;
fig. 4 is a schematic diagram of a hierarchical compression strategy provided in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a ticket processing apparatus according to an embodiment of the present application;
fig. 6 is a schematic diagram of a basic hardware architecture of a ticket processing device provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
The terms "first," "second," "third," and "fourth," if any, in the description and claims of this application and the above-described figures are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
With the high-speed development of the internet and the 5G commercial use, the massive call ticket processing brings a severe test to hardware resources, especially network bandwidth. In order to solve the problems, the existing method for processing the data service call bill comprises the steps of expanding hardware resources, improving network bandwidth and the like. However, hardware resource expansion and network bandwidth increase resource cost and maintenance cost.
Therefore, the embodiment of the application provides a ticket processing method, which compresses an original ticket according to a preset compression strategy, wherein the preset compression strategy comprises a dynamic quota compression strategy, a session-level traffic combination compression strategy, a user-level traffic combination compression strategy, a data algorithm compression strategy and the like, and combines the compressed tickets according to the ticket charging attributes of the compressed tickets to obtain a target ticket.
Optionally, the call ticket processing method provided by the present application may be applied to the schematic structure of the call ticket processing system shown in fig. 1, and as shown in fig. 1, the system may include a network element control unit 11, a regional control unit 12, a hierarchical compression unit 13, and a headquarters server 14.
It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the structure of the ticket processing system. In other possible embodiments of the present application, the foregoing architecture may include more or less components than those shown in the drawings, or combine some components, or split some components, or arrange different components, which may be determined according to practical application scenarios, and is not limited herein. The components shown in fig. 1 may be implemented in hardware, software, or a combination of software and hardware.
In the specific implementation process, the area control unit 12 receives the original call ticket reported by the network element control unit 11, and transparently transmits the call ticket to the headquarter server 14 or distributes the call ticket to the hierarchical compression unit 13. The hierarchical compression unit 13 compresses the original call ticket according to a preset compression policy, where the preset compression policy includes a dynamic quota compression policy, a session-level traffic combination compression policy, a user-level traffic combination compression policy, and a data algorithm compression policy, and may complete reporting when a trigger threshold or a duration reaches a limit, that is, report the compressed call ticket to the headquarters server 14. The headquarter server 14 completes the call ticket secondary combination and charging processing according to the call ticket charging attribute, and provides the allowance query function and the like. Therefore, on the premise of ensuring normal use and accurate charging of a user and ensuring user perception, the ticket processing system actually reduces the number of tickets, reduces network bandwidth consumption, and solves the problem that the resource cost and the maintenance cost are increased due to the fact that hardware resources are expanded, the network bandwidth is increased and the like so as to meet the processing requirements of data service tickets.
Here, the ticket processing system may further include a dynamic quota management unit 15, where the dynamic quota management unit 15 may implement poor dynamic management of the maximum slice quota and duration authorized by the user for surfing the internet, and set a gate threshold and a preset time period, so as to reduce the number of times of instruction exchange and reduce the volume of tickets. The area control unit 12 may read the gate threshold and the preset time period of the dynamic quota management unit 15 and issue the gate threshold and the preset time period to the network element control unit 11. The network element control unit 11 receives the door threshold value and the preset time period sent by the area control unit 12, and realizes network element parameter adjustment; and ordering and reporting to the area control unit 12 according to the network element parameter configuration, such as position change, charging condition, network switching, and the like.
In addition, the system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.
The technical solutions of the present application are described below with several embodiments as examples, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 2 is a schematic flow diagram of a call ticket processing method provided in an embodiment of the present application, where an execution subject of the embodiment may be a call ticket processing device in the embodiment shown in fig. 1, and as shown in fig. 2, the method may include:
s201: and acquiring an original ticket to be processed.
The call ticket processing system can adjust the network element parameters according to a preset threshold value and a preset time period to obtain the original call ticket to be processed.
For example, as shown in fig. 1, a regional control unit in a ticket processing system reads a gate threshold and a preset time period of a dynamic quota management unit and issues a network element control unit, the network element control unit receives the gate threshold and the preset time period issued by the regional control unit, so as to adjust network element parameters, and issues a ticket and reports the ticket to the regional control unit according to network element parameter configurations, such as position change, charging conditions, network switching, and the like.
S202: and compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises one or more of a dynamic quota compression strategy, a session-level telephone traffic combination compression strategy, a user-level telephone traffic combination compression strategy and a data algorithm compression strategy.
Here, the preset compression policy may be set according to an actual situation, and for example, the preset compression policy includes a dynamic quota compression policy, a session-level traffic merging compression policy, a user-level traffic merging compression policy, a data algorithm compression policy, and the like.
The dynamic quota compression policy may include a maximum slice quota that a plurality of users can authorize at a time when surfing the internet, and a duration. Illustratively, the dynamic quota compression strategy is based on the calculation of information such as user product tariff ordering, usage accumulation, and allowance, and the user details are used as a trigger source to calculate the maximum slice quota and duration authorized by the user on one-time internet in real time.
The user-level traffic combination compression strategy can comprise a corresponding relation between a user class and a combination compression strategy, for example, the user class belongs to a class A user, and the combination compression strategy is to realize user ticket combination by taking a 50M flow threshold value or a 30-minute time threshold value as a limit according to network element attributes such as an exchanger, a base station, a cell, an RG and the like; the user category belongs to a B-type user, and the combination compression strategy is to realize the combination of user call tickets by taking a 500M flow threshold value or a 1 hour time threshold value as a limit according to network element attributes such as an exchanger, a base station and the like; the user category belongs to the C-class users, and the combination compression strategy is to realize the ticket combination and the like by taking a 1G flow threshold or a 2 hour time threshold as a quota according to the network element attribute of the switch.
The data algorithm compression strategy may include a data compression algorithm, such as a lossless data compression algorithm, e.g., huffman coding, LZW coding, etc.
In the embodiment of the application, the ticket processing system can compress the original ticket according to different compression strategies, so that the compression requirements of the data service ticket under different scenes are met.
S203: and combining the compressed call tickets according to the call ticket charging attribute of the compressed call tickets to obtain the target call ticket.
For example, as shown in fig. 1, after the step compression unit compresses the original ticket according to a preset compression policy, the ticket processing system may complete secondary ticket combination and the like at the headquarters server according to the charging attribute of the ticket, that is, after the dialog ticket is compressed according to the embodiment of the present application, the dialog ticket is further combined, so that the number of the finally obtained tickets is small, the data transmission efficiency is improved, and the network bandwidth consumption is reduced.
The method and the device have the advantages that the original call ticket to be processed is obtained, then the original call ticket to be processed is compressed according to the preset compression strategy, the preset compression strategy comprises a dynamic quota compression strategy, a session level call merging compression strategy, a user level call merging compression strategy, a data algorithm compression strategy and the like, and the compressed call tickets are merged according to the call ticket charging attributes of the compressed call tickets to obtain the target call ticket. In addition, the preset compression strategies of the embodiment of the application comprise different compression strategies, so that the compression requirements on the data service call ticket under different scenes are met. In addition, after the conversation list is compressed, the conversation lists are further combined, so that the number of the finally obtained call tickets is small, the data transmission efficiency is improved, and the network bandwidth consumption is reduced.
In addition, the preset compression policy in the embodiment of the present application includes a dynamic quota compression policy, a session-level telephone traffic combination compression policy, a user-level telephone traffic combination compression policy, a data algorithm compression policy, and the like, and when different compression policies are used to compress the original ticket to be processed, the specific compression processing manners are different, so that fig. 3 provides a schematic flow diagram of another ticket processing method in the embodiment of the present application. As shown in fig. 3, different ways of compressing the original ticket to be processed by using different compression strategies according to the embodiment of the present application are shown in the figure, which includes:
s301: and acquiring an original ticket to be processed.
In step S301, reference is made to the related description of step S201, which is not described herein again.
S302: if the preset compression strategy comprises a dynamic quota compression strategy, wherein the dynamic quota compression strategy comprises the maximum slice quota and the time length which can be authorized by a plurality of users for one-time surfing, the maximum slice quota and the time length which can be authorized by the users for one-time surfing corresponding to the original ticket to be processed are determined according to the maximum slice quota and the time length which can be authorized by the users for one-time surfing, and the original ticket to be processed is compressed according to the maximum slice quota and the time length.
For example, as shown in fig. 1, the above-mentioned ticket processing system may calculate, in the hierarchical compression unit, information such as user product tariff order, usage amount accumulation, and remaining amount as a basis, and a detailed user list is a trigger source, calculate quota information for determining available authorization of a user in real time, that is, maximum slice quota and duration authorized by a plurality of users when surfing the internet at a time, dynamically issue quota data to the area control unit, and control the network element control unit by the area control unit to complete adjustment and validation of network element parameters, and complete ticket accumulation and combination.
S303: and if the preset compression strategy comprises a session-level telephone traffic combination compression strategy, determining a target IP request and/or service corresponding to the session in the original telephone bill to be processed, and carrying out session-level telephone traffic combination compression on the original telephone bill to be processed according to the target IP request and/or the service.
If the user initiates the network session request in the continuous time slice, the ticket processing system can flexibly process the user to the session combination between different target IP requests and different RG services according to different service processing rules and session strategy groups, thereby completing the network control and compressing the ticket volume.
S304: if the preset compression strategy comprises a user-level telephone traffic combination compression strategy which comprises a corresponding relation between a user class and a combination compression strategy, determining the user class of the user corresponding to the original telephone bill to be processed, determining a target combination compression strategy according to the corresponding relation and the user class of the user corresponding to the original telephone bill to be processed, and compressing the original telephone bill to be processed according to the target combination compression strategy.
The correspondence can be determined according to actual conditions, for example, the user category belongs to a user of category a, and the combination compression strategy is to implement the combination of the user call tickets according to network element attributes such as an exchanger, a base station, a cell, an RG and the like, and with a 50M traffic threshold or a 30-minute time threshold as a limit; the user category belongs to a B-class user, and the combination compression strategy is to realize the combination of user call tickets by taking a 500M flow threshold value or a 1 hour time threshold value as a limit according to network element attributes such as an exchanger, a base station and the like; the user category belongs to the C-class users, and the combination compression strategy is to realize the ticket combination and the like by taking a 1G flow threshold or a 2 hour time threshold as a quota according to the network element attribute of the switch. And the ticket processing system determines a target combination compression strategy according to the corresponding relation and the user category of the user corresponding to the original ticket to be processed, so that the original ticket to be processed is compressed according to the target combination compression strategy.
S305: and if the preset compression strategy comprises a data algorithm compression strategy which comprises a Huffman code and/or an LZW code, compressing the original ticket to be processed according to the Huffman code and/or the LZW code.
In addition, the data algorithm compression strategy may further include other compression algorithms, such as Rice, lempel-Ziv, and the like, which is not particularly limited in the embodiment of the present application.
Here, the preset compression policy may include a plurality of compression policies in addition to one compression policy as described above.
For example, the preset compression policy includes a dynamic quota compression policy and a session-level traffic merging compression policy. When the ticket processing system compresses the original ticket to be processed according to the preset compression strategy, the maximum slice quota and duration which can be authorized by a user once and corresponds to the original ticket to be processed can be determined according to the maximum slice quota and duration which can be authorized by a plurality of users once, the original ticket to be processed is compressed according to the maximum slice quota and duration, then, a target IP request and/or service corresponding to a session in the compressed ticket is determined, and the compressed ticket is subjected to session-level traffic combination compression according to the target IP request and/or service.
Similarly, the preset compression policy may include a dynamic quota compression policy and a user-level traffic combination compression policy, or include a dynamic quota compression policy and a data algorithm compression policy, or include a session-level traffic combination compression policy and a user-level traffic combination compression policy, or include a dynamic quota compression policy, a session-level traffic combination compression policy and a data algorithm compression policy, a dynamic quota compression policy, a session-level traffic combination compression policy, a user-level traffic combination compression policy and a data algorithm compression policy, and the like. The ticket processing system may refer to the situation that the preset compression policy includes a dynamic quota compression policy and a session-level traffic combination compression policy when compressing the original ticket to be processed according to the preset compression policy, which is not described herein again.
S306: and combining the compressed call bills according to the call bill charging attributes of the compressed call bills to obtain the target call bill.
Step S306 refers to the related description of step S203, which is not described herein again.
In addition, the above-mentioned ticket processing system may classify a dynamic quota compression policy, a session-level traffic combination compression policy, a user-level traffic combination compression policy, a data algorithm compression policy, and the like included in the preset compression policy, for example, as shown in fig. 4, the dynamic quota compression policy is one level, the session-level traffic combination compression policy is two levels, the user-level traffic combination compression policy is three levels, and the data algorithm compression policy is four levels.
The classification mode may be determined according to an actual situation, for example, the call ticket processing system receives a classification instruction of a user, and then classifies the preset compression policy according to the classification instruction. The above-mentioned hierarchical indication may be that the dynamic quota compression policy is one level, the session level traffic merging compression policy is two levels, the user level traffic merging compression policy is three levels, and the data algorithm compression policy is four levels, etc.
After the ticket processing system obtains the original ticket to be processed, compression strategies of different levels can be adopted to compress the original ticket to be processed. The call ticket processing system can determine the compression policy of which level is adopted according to different modes. For example, after the ticket processing system obtains the original ticket to be processed, the compression policy level of the user is received, and then the compression policy corresponding to the level is determined in the preset compression policy, and the compression policy is used for compressing the original ticket to be processed, so that different compression requirements of different tickets are met, and the ticket processing system is suitable for application.
Here, if the compression policy level of the user includes one level, for example, two levels, the ticket processing system may directly determine a compression policy corresponding to the level in the preset compression policy, and perform compression processing on the original ticket to be processed by using the compression policy. If the compression policy level of the user includes multiple levels, for example, a first level and a second level, the ticket processing system may first determine a compression policy corresponding to the level in the preset compression policy, then determine a maximum slice quota and a duration of single-time internet access authorization of the user corresponding to the original ticket to be processed according to a maximum slice quota and a duration of single-time internet access authorization of the plurality of users, compress the original ticket to be processed according to the maximum slice quota and the duration, then determine a target IP request and/or service corresponding to a session in the compressed ticket, and perform session-level traffic combination compression on the compressed ticket according to the target IP request and/or service. The compression policy levels of other users include multiple levels, which may refer to the above processing and are not described herein again.
The preset compression strategies in the embodiment of the application comprise different compression strategies, so that the compression requirements on the data service call ticket under different scenes are met. In addition, according to the embodiment of the application, the original ticket to be processed is compressed according to a preset compression strategy, and the compressed tickets are combined according to the ticket charging attribute of the compressed tickets to obtain the target ticket, so that the number of the tickets is reduced practically, the network bandwidth consumption is reduced, and the problem that the resource cost and the maintenance cost are increased due to the fact that hardware resources are expanded, the network bandwidth is improved and the like in the prior art to meet the processing requirement of the data service ticket is solved on the premise that the normal use and the charging accuracy of a user are ensured and the perception of the user is guaranteed. After the conversation list is compressed, the conversation lists are further combined, so that the number of the finally obtained call tickets is small, the data transmission efficiency is improved, and the network bandwidth consumption is reduced.
Fig. 5 is a schematic structural diagram of a ticket processing apparatus according to the embodiment of the present application, corresponding to the ticket processing method according to the embodiment. For convenience of explanation, only portions related to the embodiments of the present application are shown. Fig. 5 is a schematic structural diagram of a ticket processing apparatus according to an embodiment of the present application, where the ticket processing apparatus 50 includes: a ticket acquiring module 501, a first processing module 502 and a second processing module 503. The call ticket processing device may be the call ticket processing device itself, or a chip or an integrated circuit that implements the function of the call ticket processing device. It should be noted here that the division of the ticket acquiring module, the first processing module, and the second processing module is only a division of a logic function, and the two may be integrated or independent physically.
The ticket acquiring module 501 is configured to acquire an original ticket to be processed.
The first processing module 502 is configured to perform compression processing on the original ticket to be processed according to a preset compression policy, where the preset compression policy includes one or more of a dynamic quota compression policy, a session-level traffic combination compression policy, a user-level traffic combination compression policy, and a data algorithm compression policy.
And the second processing module 503 is configured to combine the compressed tickets according to the ticket charging attribute of the compressed tickets, so as to obtain a target ticket.
In a possible implementation manner, the preset compression policy includes a dynamic quota compression policy, and the dynamic quota compression policy includes a maximum slice quota and a duration that a plurality of users can authorize at a time when surfing the internet.
The first processing module 502 is specifically configured to:
determining the maximum slice quota and duration of single-time internet access authorization of the user corresponding to the original ticket to be processed according to the maximum slice quota and duration of single-time internet access authorization of the plurality of users;
and compressing the original ticket to be processed according to the maximum slice quota and duration corresponding to the original ticket to be processed and authorized by the user for single surfing.
In one possible implementation, the preset compression policy includes a session-level traffic merging compression policy.
The first processing module 502 is specifically configured to:
determining a target IP request and/or service corresponding to the session in the original ticket to be processed;
and according to the target IP request and/or the service, carrying out session-level telephone traffic combination compression on the original telephone bill to be processed.
In a possible implementation manner, the preset compression policy includes a user-level traffic combination compression policy, and the user-level traffic combination compression policy includes a correspondence between a user category and a combination compression policy.
The first processing module 502 is specifically configured to:
determining the user category of the user corresponding to the original ticket to be processed;
determining a target combination compression strategy according to the corresponding relation and the user category of the user corresponding to the original ticket to be processed;
and compressing the original ticket to be processed according to the target combination compression strategy.
In one possible implementation, the preset compression policy includes a data algorithm compression policy, and the data algorithm compression policy includes huffman coding and/or LZW coding.
The first processing module 502 is specifically configured to:
and compressing the original ticket to be processed according to the Huffman code and/or the LZW code.
In a possible implementation manner, the ticket acquiring module 501 is specifically configured to:
and adjusting network element parameters according to a preset threshold value and a preset time period to obtain the original call ticket to be processed.
The apparatus provided in the embodiment of the present application may be configured to implement the technical solution of the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again in the embodiment of the present application.
Optionally, fig. 6 schematically and respectively provides a possible basic hardware architecture of the ticket processing device according to the present application.
Referring to fig. 6, the ticket processing apparatus includes at least one processor 601 and a communication interface 603. Further optionally, a memory 602 and a bus 604 may also be included.
In the ticket processing device, the number of the processors 601 may be one or more, and fig. 6 only illustrates one of the processors 601. Alternatively, the processor 601 may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Digital Signal Processor (DSP). If the ticket processing device has multiple processors 601, the types of the multiple processors 601 may be different, or may be the same. Alternatively, the multiple processors 601 of the ticket processing device may also be integrated into a multi-core processor.
The communication interface 603 may provide information input/output for the at least one processor. Any one or any combination of the following devices may also be included: a network interface (e.g., an ethernet interface), a wireless network card, etc. having a network access function.
Optionally, the communication interface 603 may also be used for performing data communication between the ticket processing device and other computing devices or terminals.
Further alternatively, fig. 6 shows the bus 604 as a thick line. The bus 604 may connect the processor 601 with the memory 602 and the communication interface 603. Thus, via bus 604, processor 601 may access memory 602 and may also interact with other computing devices or terminals using communication interface 603.
In the present application, the ticket processing device executes the computer instruction in the memory 602, so that the ticket processing device implements the ticket processing method provided in the present application, or the ticket processing device deploys the ticket processing apparatus.
From the viewpoint of logical function division, for example, as shown in fig. 6, the memory 602 may include a ticket obtaining module 501, a first processing module 502, and a second processing module 503. The present invention includes only that the instructions stored in the memory can implement the functions of the ticket acquiring module, the first processing module and the second processing module, respectively, when executed, and is not limited to a physical structure.
In addition, the above-mentioned ticket processing apparatus can be implemented by software as in fig. 6, and can also be implemented by hardware as a hardware module, or as a circuit unit.
The application provides a computer-readable storage medium, and the computer program product includes computer instructions for instructing a computing device to execute the above-mentioned ticket processing method provided in the application.
The embodiment of the present application provides a computer program product, which includes a computer instruction, where the computer instruction is executed by a processor to perform the foregoing call ticket processing method provided in the present application.
The present application provides a chip comprising at least one processor and a communication interface providing information input and/or output for the at least one processor. Further, the chip may also include at least one memory for storing computer instructions. The at least one processor is used for calling and operating the computer instruction so as to execute the call ticket processing method provided by the application.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Claims (10)
1. A method for processing call tickets, comprising:
acquiring an original ticket to be processed;
compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises one or more of a dynamic quota compression strategy, a session-level telephone traffic combination compression strategy, a user-level telephone traffic combination compression strategy and a data algorithm compression strategy;
and combining the compressed call bills according to the call bill charging attributes of the compressed call bills to obtain the target call bill.
2. The method according to claim 1, wherein the preset compression policy includes a dynamic quota compression policy, and the dynamic quota compression policy includes a maximum slice quota and duration that a plurality of users can be authorized for one-time internet access;
the compressing the original bill to be processed according to a preset compression strategy comprises the following steps:
determining the maximum slice quota and duration of single-time internet access authorization of the user corresponding to the original ticket to be processed according to the maximum slice quota and duration of single-time internet access authorization of the plurality of users;
and compressing the original ticket to be processed according to the maximum slice quota and duration corresponding to the original ticket to be processed and authorized by the user for single surfing.
3. The method of claim 1, wherein the preset compression policy comprises a session-level traffic combining compression policy;
the compressing the original ticket to be processed according to a preset compression strategy comprises the following steps:
determining a target internet interconnection protocol request and/or service corresponding to the session in the original ticket to be processed;
and performing session-level telephone traffic combination and compression on the original telephone bill to be processed according to the target internet interconnection protocol request and/or the service.
4. The method of claim 1, wherein the preset compression policy comprises a user-level traffic combination compression policy, and the user-level traffic combination compression policy comprises a correspondence between a user category and a combination compression policy;
the compressing the original bill to be processed according to a preset compression strategy comprises the following steps:
determining the user category of the user corresponding to the original ticket to be processed;
determining a target combination compression strategy according to the corresponding relation and the user category of the user corresponding to the original ticket to be processed;
and compressing the original ticket to be processed according to the target combination compression strategy.
5. The method according to claim 1, wherein the preset compression strategy comprises a data algorithm compression strategy, and the data algorithm compression strategy comprises huffman coding and/or string table coding;
the compressing the original bill to be processed according to a preset compression strategy comprises the following steps:
and compressing the original ticket to be processed according to the Huffman code and/or the string table code.
6. The method of claim 1, wherein the obtaining the original ticket to be processed comprises:
and adjusting network element parameters according to a preset threshold value and a preset time period to obtain the original call ticket to be processed.
7. A ticket processing apparatus, comprising:
the ticket acquisition module is used for acquiring an original ticket to be processed;
the first processing module is used for compressing the original ticket to be processed according to a preset compression strategy, wherein the preset compression strategy comprises one or more of a dynamic quota compression strategy, a session-level telephone traffic combination compression strategy, a user-level telephone traffic combination compression strategy and a data algorithm compression strategy;
and the second processing module is used for combining the compressed call tickets according to the call ticket charging attributes of the compressed call tickets to obtain the target call tickets.
8. A ticket processing apparatus, comprising:
a processor;
a memory; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor, the computer program comprising instructions for performing the method of any of claims 1-6.
9. A computer-readable storage medium, characterized in that it stores a computer program that causes a server to execute the method of any one of claims 1-6.
10. A computer program product comprising computer instructions for executing the method of any one of claims 1-6 by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110852472.XA CN115696441A (en) | 2021-07-27 | 2021-07-27 | Call bill processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110852472.XA CN115696441A (en) | 2021-07-27 | 2021-07-27 | Call bill processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115696441A true CN115696441A (en) | 2023-02-03 |
Family
ID=85059435
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110852472.XA Pending CN115696441A (en) | 2021-07-27 | 2021-07-27 | Call bill processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115696441A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116521634A (en) * | 2023-07-03 | 2023-08-01 | 北京华翔联信科技股份有限公司 | Method, system, electronic equipment and storage medium for processing call ticket data service |
-
2021
- 2021-07-27 CN CN202110852472.XA patent/CN115696441A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116521634A (en) * | 2023-07-03 | 2023-08-01 | 北京华翔联信科技股份有限公司 | Method, system, electronic equipment and storage medium for processing call ticket data service |
| CN116521634B (en) * | 2023-07-03 | 2023-09-08 | 北京华翔联信科技股份有限公司 | Method, system, electronic equipment and storage medium for processing call ticket data service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Huang et al. | Resource allocation and consensus on edge blockchain in pervasive edge computing environments | |
| CN108898440A (en) | Flow exchanging method and device | |
| CN107155093A (en) | A kind of video previewing method, device and equipment | |
| CN112564954A (en) | Network quality prediction method and device | |
| CN115696441A (en) | Call bill processing method, device, equipment and storage medium | |
| CN113486118A (en) | Consensus node selection method and device | |
| CN103200124A (en) | Service strategy adjustment method and service strategy adjustment device | |
| US20180060892A1 (en) | Market segment analysis of product or service offerings | |
| US20220415046A1 (en) | Method for determining video coding test sequence, electronic device and computer storage medium | |
| RU2532714C2 (en) | Method of acquiring data when evaluating network resources and apparatus therefor | |
| US20230032235A1 (en) | Energy efficiency evaluation method and related device | |
| CN111124669A (en) | Operation method, system, terminal and storage medium of distributed SaaS software | |
| CN115840649A (en) | Method and device for allocating partitioned capacity block type virtual resources, storage medium and terminal | |
| CN112394882B (en) | Data storage method and device, storage medium and electronic device | |
| CN108400901A (en) | Test method, terminal device and the computer readable storage medium of application | |
| CN112131267B (en) | Count processing method, device, server and count processing system | |
| CN112217944B (en) | Online ticket processing method, device, equipment and storage medium | |
| US10893151B1 (en) | Data gap bridging methods and systems | |
| CN111797169A (en) | Data storage method, equipment and storage medium | |
| CN102752122B (en) | The acquisition device of multidimensional statistics performance data and method in network management | |
| JP7457169B2 (en) | Data analysis methods, electronic equipment and storage media | |
| CN115033390B (en) | Load balancing method and device | |
| CN115065685B (en) | Cloud computing resource scheduling method, device, equipment and medium | |
| CN108366022A (en) | A kind of method and device of bandwidth allocation | |
| CN110968397B (en) | Analysis method and device for virtual machine capacity management |
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 |