CN112995934A - Call bill generating method and device and call bill charging result verifying method and device - Google Patents
Call bill generating method and device and call bill charging result verifying method and device Download PDFInfo
- Publication number
- CN112995934A CN112995934A CN201911291082.9A CN201911291082A CN112995934A CN 112995934 A CN112995934 A CN 112995934A CN 201911291082 A CN201911291082 A CN 201911291082A CN 112995934 A CN112995934 A CN 112995934A
- Authority
- CN
- China
- Prior art keywords
- charging
- data
- party
- communication
- ticket
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Meter Arrangements (AREA)
Abstract
The embodiment of the application discloses a method and a device for generating a call ticket and a method and a device for verifying the charging result of the call ticket, wherein the method for generating the call ticket comprises the following steps: acquiring charging rule data of communication cost input by a user, and determining at least one type of charging scene according to the charging rule data; acquiring communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene; and constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene. According to the embodiment, manual field dialing and testing are not needed, the virtual ticket can be automatically generated, the ticket generation efficiency is improved, the ticket generation cost is reduced, and the verification efficiency of the ticket charging result is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for generating a ticket, and a method and an apparatus for verifying a charging result of a ticket.
Background
In the field of mobile communication, charging a call ticket of a user is an important work content. After the user makes mobile communication, such as making a call or sending a short message, the operator server can automatically generate a call ticket of the user, and charge the call ticket of the user through the automatic charging system, and the user needs to pay according to a charging result.
At present, the method for verifying the charging result of the dialog list mainly comprises the following steps: the staff executes manual field dialing test according to the communication scene related to the charge description to generate a real test ticket, the generated test ticket is charged by the automatic charging system, and the staff can compare the charging result with the charge description to obtain a verification conclusion.
In the prior art, the method for generating the test ticket by manual field test has the defects of low efficiency, high cost and the like.
Disclosure of Invention
The embodiment of the application provides a method and a device for generating a call ticket and a method and a device for verifying the charging result of the call ticket, which do not need manual field dialing and testing, can automatically generate a virtual call ticket, improve the generation efficiency of the call ticket, reduce the generation cost of the call ticket and improve the verification efficiency of the charging result of the call ticket.
In order to achieve the technical purpose, the embodiment of the application adopts the following technical scheme:
an embodiment of the present application provides a method for generating a ticket, including:
acquiring charging rule data of communication cost input by a user, and determining at least one type of charging scene according to the charging rule data;
acquiring communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene.
An embodiment of the present application provides a method for verifying a billing result of a ticket, including:
generating virtual ticket data for the charging rule data input by the user by the ticket generating method;
calling a ticket charging system to be verified, and charging the generated virtual ticket data to obtain a first charging result;
charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and verifying whether the charging result of the call ticket charging system is accurate or not according to the first charging result and the second charging result.
An embodiment of the present application provides a ticket generating apparatus, including:
the system comprises an acquisition module, a charging module and a charging module, wherein the acquisition module is used for acquiring charging rule data of communication cost input by a user and determining at least one type of charging scene according to the charging rule data;
the determining module is used for acquiring the communication state data of the charging party and the communication state data of the non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and the construction module is used for constructing the virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value corresponding to the charging scene.
An embodiment of the present application provides a device for verifying a billing result of a ticket, including:
the generating module is used for generating virtual ticket data for the charging rule data input by the user through the ticket generating method;
the first charging module is used for calling a ticket charging system to be verified, charging the generated virtual ticket data and obtaining a first charging result;
the second charging module is used for charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and the verification module is used for verifying whether the charging result of the ticket charging system is accurate or not according to the first charging result and the second charging result.
An embodiment of the present application provides an electronic device, including a memory and a processor, where the memory stores computer-executable instructions, and when the computer-executable instructions run on the processor, the steps of the above-mentioned call ticket generation method or the above-mentioned call ticket charging result verification method can be implemented.
An embodiment of the present application provides a storage medium, where a computer-executable instruction is stored in the storage medium, and when the computer-executable instruction is executed by a processor, the steps of the above-mentioned call ticket generation method or the above-mentioned call ticket charging result verification method can be implemented.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
according to the embodiment of the application, manual field dialing and testing are not needed, and virtual ticket data can be automatically constructed according to the charging rule data input by a user, so that the ticket generation efficiency is improved, the ticket generation cost is reduced, the verification efficiency of the ticket charging result is improved, and the verification cost of the ticket charging result is reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic flow chart of a call ticket generating method according to an embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for verifying a billing result of a ticket according to an embodiment of the present application.
Fig. 3 is a schematic diagram illustrating a module composition of a ticket generating apparatus according to an embodiment of the present application.
Fig. 4 is a schematic diagram illustrating a module composition of a ticket charging result verification apparatus according to an embodiment of the present application.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
The embodiment of the application provides a call ticket generation method and device and a call ticket charging result verification method and device. The call ticket generating method and the call ticket charging result verifying method can be applied to a server side and executed by the server. The server may be a specific device installed in the background of the communication carrier.
Fig. 1 is a schematic flow chart of a call ticket generating method according to an embodiment of the present application, and as shown in fig. 1, the flow includes the following steps:
step S102, obtaining the charging rule data of the communication fee input by the user, and determining at least one type of charging scene according to the charging rule data;
step S104, obtaining the communication state data of the charging party and the communication state data of the non-charging party corresponding to the charging scene from the communication database, and generating the communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and step S106, constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene.
In the embodiment of the application, at least one type of charging scene can be determined according to charging rule data input by a user, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene are obtained from a communication database, and a communication data usage value between the charging party and the non-charging party corresponding to the charging scene is generated, so that virtual ticket data corresponding to the charging scene is constructed according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value. Therefore, according to the embodiment of the application, the virtual ticket data can be automatically generated without manual field dialing and testing, so that the ticket generation efficiency is improved, the ticket generation cost is reduced, and the verification efficiency of the ticket charging result is improved.
In step S102, the server obtains the charging rule data of the communication charges input by the user, where the communication charges include at least one of call charges, traffic charges, and short message charges. Taking the communication charges including the telephone charges and the short message charges as an example, the charging rule data of the communication charges may be, for example: and giving 100 short messages and 100-minute calling time by 50 yuan, wherein the calling party does not collect long-distance fee and roaming fee within 100 minutes, the calling party collects the basic fee of 1 wool/minute after exceeding 100 minutes, collects the long-distance fee and the roaming fee, and the short messages collect the long-distance fee and the roaming fee after exceeding 100 wool/strip.
In step S102, at least one type of charging scenario is determined according to the charging rule data. The charging scenario may be understood as a charging scenario corresponding to various charging situations determined according to the charging rules.
Taking the above charging rule data as an example, the charging scenario includes but is not limited to: (1) the calling call duration is less than 100 minutes, and the calling call can be a local or long-distance or roaming call; (2) the calling call duration is more than 100 minutes, and the calling party is a local call; (3) the calling call duration is more than 100 minutes, and the calling call is a long distance call; (4) the calling call duration is more than 100 minutes, and the calling party is a roaming call; (5) the number of the calling short messages is less than or equal to 100; (6) the number of the calling short messages exceeds 100; (7) any one of the scenes (1) to (4) is combined with the scene (5) or the scene (6).
In this embodiment, at least one type of charging scenario is determined according to the charging rule data by the following steps:
(a1) according to the charging rule data, determining charging relevant factors influencing the charging result from all preset charging factors; the preset charging factors comprise the communication state of a charging party, the communication state of a non-charging party and the usage amount of communication data between the charging party and the non-charging party;
(a2) and determining at least one type of charging scene according to various value conditions of the determined charging related factors.
Specifically, in this embodiment, a plurality of charging factors are preset, including a communication state of a charging party, a communication state of a non-charging party, and a usage amount of communication data between the charging party and the non-charging party. The communication state of the charging party includes, but is not limited to, the location of the communication number of the charging party, the communication channel of the charging party, and the communication role of the charging party, and similarly, the communication state of the non-charging party includes, but is not limited to, the location of the communication number of the non-charging party, the communication channel of the non-charging party, and the communication role of the non-charging party.
The communication channel comprises any one of a common voice channel, a high-definition voice channel, a common video channel, a high-definition video channel, a text short message channel and a multimedia message channel. The communication role comprises any one of a call calling party, a call called party, a call transfer, a short message sending party and a short message receiving party.
The usage amount of the communication data between the charging party and the non-charging party comprises any one of the call duration, the number of short messages and the flow usage amount between the charging party and the non-charging party. In the embodiment of the present application, the charging party and the non-charging party refer to users.
In different charging rule data, the charging factors influencing the charging result are different. For example, in the rule data of "50 yuan includes 10000 short messages and 1 gross money more", the charging result is related to the communication role of the charging party, the usage amount of the communication data between the charging party and the non-charging party, and for example, in the rule data of "50 yuan presents the calling time of 100 minutes, the calling does not charge the long distance fee and the roaming fee within 100 minutes, the basic fee is 1 gross/minute after the calling exceeds 100 minutes, and the long distance fee and the roaming fee are charged", the charging result is related to the communication role of the charging party, the usage amount of the communication data between the charging party and the non-charging party, and the communication state of the charging party. In the two charging rule data, the charging result is related to the communication role of the charging party because in the two charging rule data, the charging is only carried out on the calling party and the charging is not carried out on the called party.
Based on this, in this embodiment, first, through the above-mentioned action (a1), according to the charging rule data, the charging factor that affects the charging result is determined to be obtained from the preset charging factors, and the charging factor that affects the charging result is the charging related factor. Then, at least one type of charging scenario is determined according to the determined charging-related factors through the above-described action (a 2). Specifically, various value conditions of the charging related factors can be determined according to the charging rule data, and at least one type of charging scene can be determined according to the various value conditions of the charging related factors.
For example, the charging rule data is: the 50 Yuan gives 1000-minute call receiving and making time, wherein the total call receiving and making time exceeds 1000 minutes, and then calls are received and made according to the gross hair/minute. It is determined through action (a1) that the charging-related factor is the usage of communication data between the charging party and the non-charging party. By adopting a mode of controlling the value of the charging relevant factors, various charging scenes can be determined to be respectively as follows: (1) the time for contact and beating is within 1000 minutes; (2) the time for the contact and beating is more than 1000 minutes. In this example, since the call and the call are charged, the charging result is not related to the communication role of the charging party.
When the number of the charging relevant factors is multiple, various charging scenes can be determined and obtained according to various value conditions of the charging relevant factors in the above mode.
For example, the charging rule data is: the 50 Yuan gives 1000-minute call receiving and making time, wherein the total call receiving and making time exceeds 1000 minutes, then calls are received and made according to 1 gross/minute, and long-distance fee and roaming fee are charged at the same time. It is determined through the action (a1) that the charging-related factors are the usage amount of communication data between the charging party and the non-charging party, and the communication state of the charging party. By adopting a mode of controlling the value of the charging relevant factors, various charging scenes can be determined to be respectively as follows: (1) the time for contact and beating is within 1000 minutes; (2) the time for receiving and beating is more than 1000 minutes, and the local receiving and beating is carried out; (3) the time for receiving and printing is more than 1000 minutes, and long distance receiving and printing is carried out; (4) the time for receiving and printing is more than 1000 minutes, and the receiving and printing is roaming receiving and printing. In this example, since the call and the call are charged, the charging result is not related to the communication role of the charging party.
After at least one type of charging scene is determined, step S104 is executed to determine communication state data of the charging party, communication state data of the non-charging party, and a usage amount value of the communication data, which correspond to each type of charging scene, in order to generate virtual ticket data corresponding to each type of charging scene.
The communication state data of the charging party includes, but is not limited to, a communication number of the charging party, a location identifier of the communication number of the charging party, a communication role identifier of the charging party, and a communication channel identifier of the charging party. The communication state data of the non-charging party comprises but is not limited to a communication number of the non-charging party, a location identification of the communication number of the non-charging party, a communication role identification of the non-charging party and a communication channel identification of the non-charging party. The communication data usage value includes any one of a call duration value, a short message value and a traffic usage value between the charging party and the non-charging party.
In this embodiment, the communication status data may further include a global unified identification number of the communication number. In the communication state data, the location identification can be represented by the network element charging identification number of the visited place, and the home location identification number can be represented by the home region code identification number.
In this embodiment, before determining the communication state data of the charging party, the communication state data of the non-charging party, and the usage amount value of the communication data corresponding to the charging scenario, a first data requirement, a second data requirement, and a third data requirement corresponding to the charging scenario need to be determined. The first data requirement is a data requirement corresponding to the communication state data of the charging party, and the second data requirement is a data requirement corresponding to the communication state data of the non-charging party; the third data requirement is a data requirement corresponding to the communication data usage size value between the charging party and the non-charging party.
Taking the charging scenario that the calling call duration is greater than 100 minutes and the calling call is a local high-definition voice call as an example, where the charging party is a calling party, and the first data requirement corresponding to the scenario is as follows: the communication number of the charging party is a local number, the location of the communication number of the charging party is local, the attribution of the communication number of the charging party is local, the communication role of the charging party is a calling party, and the communication channel of the charging party is a high-definition voice channel. The second data requirement corresponding to the scene is as follows: the communication number of the non-charging party is a local number, the location of the communication number of the non-charging party is local, the communication role of the non-charging party is called, and the communication channel of the non-charging party is a high-definition voice channel. The third data requirement corresponding to the scene is as follows: the call duration is greater than 100 minutes.
In this embodiment, the communication state data of the charging party and the communication state data of the non-charging party may be obtained from a communication database according to the first data requirement and the second data requirement, where the communication database records a real communication number, a location identifier of the real communication number, a home identifier of the real communication number, a real communication role identifier, and a real communication channel identifier. The data recorded in the communication database are all real data.
For example, in this example, according to the first data requirement and the second data requirement, the communication number of the local user "xiaowang" may be acquired from the communication database as the charging party communication number, and the local identification number may be acquired as the charging party location identifier and the attribution identifier, and the communication number of the local user "dui" may be acquired from the communication database as the non-charging party communication number, and the local identification number may be acquired as the non-charging party location identifier and the attribution identifier. And generating a communication data usage value according to a third data requirement, for example, generating a communication time of 150 minutes, and when the communication data usage value is generated, generating according to a preset numerical value generation algorithm, wherein it is required to ensure that the generated numerical value meets the third data requirement.
Finally, in step S106, virtual ticket data corresponding to the charging scenario is constructed according to the communication state data of the charging party, the communication state data of the non-charging party, and the usage amount of the communication data corresponding to the charging scenario.
In this embodiment, the virtual ticket data is composed of data of a communication state data of a charging party, a communication state data of a non-charging party, and a communication data usage amount value, which are filled in according to a fixed format. After the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to each charging scene are determined and obtained, the determined data can be filled according to a fixed format, and virtual ticket data corresponding to each charging scene is obtained. The generated call ticket data is not call ticket data generated based on real communication behaviors, but call ticket data obtained by constructing according to the acquired data, and therefore the call ticket data is called virtual call ticket data.
In this embodiment, at least one piece of virtual ticket data may be generated for each charging scenario, and the number of the virtual ticket data generated finally is also at least one. Under one condition, the number of the virtual ticket data is at least two, and based on the number, the virtual ticket data corresponding to the charging scene is constructed, which comprises the following steps: and determining the charging result of each virtual ticket data according to the charging logic corresponding to the charging rule data, and sequentially constructing the virtual ticket data corresponding to various charging scenes according to the sequence from low to high of the charging result of each virtual ticket data.
Specifically, when the number of the virtual ticket data is at least two, the charging result of each piece of virtual ticket data is determined according to the charging logic corresponding to the charging rule data, and then the virtual ticket data corresponding to various charging scenes are sequentially constructed according to the sequence from low to high of the charging result of each piece of virtual ticket data.
For example, the charging scenarios are respectively: (1) the time for contact and beating is within 1000 minutes; (2) the time for receiving and beating is more than 1000 minutes, and the local receiving and beating is carried out; (3) the time for receiving and printing is more than 1000 minutes, and long distance receiving and printing is carried out; (4) the time for receiving and printing is more than 1000 minutes, and the receiving and printing is roaming receiving and printing. The method comprises the steps of generating a piece of virtual ticket data for a scene (1), wherein the call duration is 808 minutes, generating a piece of virtual ticket data for a scene (2), the call duration is 1100 minutes, generating a piece of virtual ticket data for a scene (3), the call duration is 1100 minutes, generating a piece of virtual ticket data for a scene (4), and the call duration is 1100 minutes. According to the charging logic corresponding to the charging rule data, the charging result of the virtual ticket data in the scene (4) is the highest (namely the most expensive), the charging result of the virtual ticket data in the scene (3) is the second highest, the charging result of the virtual ticket data in the scene (2) is the second highest, and the charging result of the virtual ticket data in the scene (1) is the lowest (namely the cheapest). Therefore, in this embodiment, the virtual ticket data corresponding to various charging scenarios are sequentially constructed according to the sequence of the charging results of the virtual ticket data from low to high, that is, the virtual ticket data corresponding to various charging scenarios are sequentially constructed according to the sequence of the ticket 4-the ticket 3-the ticket 2-the ticket 1.
In the embodiment, the virtual ticket data corresponding to various charging scenes are sequentially constructed according to the sequence of the charging results of the virtual ticket data from low to high, so that the problem that the virtual ticket data are omitted can be avoided, and the ticket construction accuracy is improved.
In this embodiment, when constructing the virtual ticket data, an initial value-taking domain of each data item (including each data item in the communication state data and the communication data usage amount value) may be obtained, and then the compatibility of the current item with the previous items is checked, and a subtraction operation is performed on all the previous compatible items to obtain a final value-taking domain. Compatibility is defined as: after the call scenario mode of the tariff provision item is instantiated, a call scenario (namely, the aforementioned charge scenario) example is obtained, and is described by a ten-tuple < a charging party number, a charging party attribution, a charging party visiting place (namely, a location), a call channel, an opposite terminal number, an opposite terminal attribution, an opposite terminal visiting place, an opposite terminal operator, a communication channel and a call time range >, wherein a value-taking domain of each tuple is a discrete finite element set. If the value-taking domain of each tuple in the call scenario instance of tariff provision item a has a non-empty intersection with the value-taking domain of the corresponding tuple in the call scenario instance of tariff provision item B, then tariff provision item a is said to be consistent with tariff provision item B. For tariff regulation clause B, for tariff regulation clause a that precedes it and is compatible with it, the subtraction algorithm is: assuming that a tuple is X in the call scenario example, if the range of A.X is not equal to the range of B.X and there is a non-empty intersection, then a set subtraction is performed to subtract the range of A.X from the range of B.X, and the difference is used as the new range of B.X. The method of the compatible subtraction can refer to the existing method of generating the call ticket, and is not described herein again.
In this embodiment, the determined charging scenario is to cover various possible scenarios related to the charging rule data, so that the generated virtual ticket data can sufficiently cover various possible charging situations. When the virtual ticket data is generated, the value of each data item in the generated virtual ticket data is required to be matched with the requirement corresponding to the data item, for example, the call duration meets the requirement of the corresponding call duration, so that the generated virtual ticket data is accurate enough.
Fig. 2 is a schematic flow chart of a method for verifying a billing result of a ticket according to an embodiment of the present application, where as shown in fig. 2, the flow includes:
step S202, generating virtual ticket data for the charging rule data input by the user by the ticket generating method;
step S204, calling a ticket charging system to be verified, and charging the generated virtual ticket data to obtain a first charging result;
step S206, charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and S208, verifying whether the charging result of the ticket charging system is accurate or not according to the first charging result and the second charging result.
In the embodiment of the application, by the ticket generating method, virtual ticket data is generated for charging rule data input by a user, a ticket charging system to be verified is called, the generated virtual ticket data is charged to obtain a first charging result, the generated virtual ticket data is charged according to charging logic corresponding to the charging rule data to obtain a second charging result, and whether the charging result of the ticket charging system is accurate or not is verified according to the first charging result and the second charging result. Therefore, according to the embodiment of the application, manual field dialing and testing are not needed, the virtual ticket data can be automatically generated, the accuracy of the ticket charging result can be verified, and therefore the verification efficiency of the ticket charging result is improved.
The first charging result and the second charging result represent the charge of the call ticket. The second charging result is determined according to the charging logic corresponding to the charging rule data, so that the second charging result is an accurate charging result. And if the first charging result is not equal to the second charging result, determining that the charging result of the ticket charging system to be verified is not accurate. The ticket charging system to be verified can be a cloud system distributed on a cloud server.
In this embodiment, the number of the virtual ticket data is multiple. And if the charging result of the bill charging system is not accurate after verification, determining target bill data with inaccurate charging results in each generated virtual bill data, and outputting the target bill data so as to position the problem of the bill charging system according to the target bill data.
If the first charging result of part of the call ticket data is equal to the second charging result and the first charging result of part of the call ticket data is not equal to the second charging result in the plurality of pieces of virtual call ticket data, the call ticket data of which the first charging result is not equal to the second charging result can be determined as the target call ticket data, and the target call ticket data is output, so that a worker can check the call ticket charging system according to the target call ticket data and determine the problem of the call ticket charging system.
In a specific embodiment, the method for verifying the charging result of the ticket is applied to a server of a communication operator, the server can provide a visual ticket charging result verification system, a user inputs charging rule data through the system, and the system automatically generates virtual ticket data according to the data input by the user and verifies the charging result.
In summary, the call ticket generation method and the call ticket charging result verification method in the embodiment can reduce the call ticket generation cost, improve the call ticket generation efficiency, and improve the charging result verification efficiency. Because the virtual ticket data is generated according to each charging scene, the virtual ticket can cover various charging conditions, and the coverage degree of the ticket is improved. In this embodiment, the above verification method can be used to periodically verify the charging rules of various package tariffs, and to find and adjust the problem of the ticket charging system.
Through verification, the call ticket generation method and the call ticket charging result verification method in the embodiment can find and correct the problem of the call ticket charging system in time, so that the correctness of the charging system is greatly improved, the customer satisfaction is obviously improved, and the asset loss of an operator is avoided. For the condition that the new package charge is on line, the accuracy of the call bill charging system is rapidly determined by the call bill generating method and the call bill charging result verification method in the embodiment so as to carry out corresponding adjustment, so that the time for preparing the new package charge to be on the market is obviously shortened. Moreover, by the ticket generation method and the ticket charging result verification method in the embodiment, labor cost and verification time of ticket charging system verification are greatly reduced, and verification efficiency and verification accuracy are effectively improved.
Fig. 3 is a schematic diagram of module components of a ticket generating apparatus according to an embodiment of the present application, and as shown in fig. 3, the apparatus includes:
an obtaining module 31, configured to obtain charging rule data of communication charges input by a user, and determine at least one type of charging scenario according to the charging rule data;
a determining module 32, configured to obtain, from a communication database, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scenario, and generate a communication data usage amount value between the charging party and the non-charging party corresponding to the charging scenario;
and the constructing module 33 is configured to construct virtual ticket data corresponding to the charging scenario according to the communication state data of the charging party, the communication state data of the non-charging party, and the usage amount of the communication data corresponding to the charging scenario.
Optionally, the obtaining module 31 is specifically configured to: according to the charging rule data, determining charging relevant factors influencing a charging result from all preset charging factors; determining at least one type of charging scene according to various determined value conditions of the charging related factors; the preset charging factors comprise the communication state of a charging party, the communication state of a non-charging party and the usage amount of communication data between the charging party and the non-charging party.
Optionally, the apparatus further includes a requirement determining module, configured to: before communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene are obtained from a communication database, and a communication data usage amount value between the charging party and the non-charging party corresponding to the charging scene is generated, a first data requirement, a second data requirement and a third data requirement corresponding to the charging scene are determined; the first data requirement is a data requirement corresponding to the communication state data of the charging party, and the second data requirement is a data requirement corresponding to the communication state data of the non-charging party; the third data requirement is a data requirement corresponding to a communication data usage value between the charging party and the non-charging party; the communication state data comprises a communication number, a communication number location identification, a communication number attribution identification, a communication role identification and a communication channel identification.
Optionally, the number of the virtual ticket data is at least two; the building block 33 is particularly intended for: determining the charging result of each piece of virtual ticket data according to the charging logic corresponding to the charging rule data; and sequentially constructing the virtual ticket data corresponding to various charging scenes according to the sequence of the charging results of the virtual ticket data from low to high.
In the embodiment of the application, at least one type of charging scene can be determined according to charging rule data input by a user, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene are obtained from a communication database, and a communication data usage value between the charging party and the non-charging party corresponding to the charging scene is generated, so that virtual ticket data corresponding to the charging scene is constructed according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value. Therefore, according to the embodiment of the application, the virtual ticket data can be automatically generated without manual field dialing and testing, so that the ticket generation efficiency is improved, the ticket generation cost is reduced, and the verification efficiency of the ticket charging result is improved.
It should be noted that the call ticket generating apparatus in this embodiment can implement each process of the foregoing call ticket generating method embodiment, and achieve the same function and effect, which is not repeated here.
Fig. 4 is a schematic diagram of a module composition of a ticket charging result verification apparatus according to an embodiment of the present application, and as shown in fig. 4, the apparatus includes:
a generating module 41, configured to generate virtual ticket data for the charging rule data input by the user through the ticket generating method;
the first charging module 42 is configured to invoke a ticket charging system to be verified, charge the generated virtual ticket data, and obtain a first charging result;
a second charging module 43, configured to charge the generated virtual ticket data according to a charging logic corresponding to the charging rule data, so as to obtain a second charging result;
and the verification module 44 is configured to verify whether the charging result of the ticket charging system is accurate according to the first charging result and the second charging result.
Optionally, the apparatus further comprises: an output module to: if the charging result of the call ticket charging system is not accurate after verification, determining target call ticket data with inaccurate charging result in each generated virtual call ticket data; and outputting the target call ticket data so as to perform problem positioning on the call ticket charging system according to the target call ticket data.
In the embodiment of the application, by the ticket generating method, virtual ticket data is generated for charging rule data input by a user, a ticket charging system to be verified is called, the generated virtual ticket data is charged to obtain a first charging result, the generated virtual ticket data is charged according to charging logic corresponding to the charging rule data to obtain a second charging result, and whether the charging result of the ticket charging system is accurate or not is verified according to the first charging result and the second charging result. Therefore, according to the embodiment of the application, manual field dialing and testing are not needed, the virtual ticket data can be automatically generated, the accuracy of the ticket charging result can be verified, and therefore the verification efficiency of the ticket charging result is improved.
It should be noted that the ticket charging result verification apparatus in this embodiment can implement each process of the foregoing ticket charging result verification method embodiment, and achieve the same function and effect, which is not repeated here.
Further, an embodiment of the present specification further provides an electronic device, fig. 5 is a schematic structural diagram of the electronic device provided in an embodiment of the present application, and as shown in fig. 5, the electronic device includes: memory 601, processor 602, bus 603, and communication interface 604. The memory 601, processor 602, and communication interface 604 communicate via the bus 603. the communication interface 604 may include input and output interfaces including, but not limited to, a keyboard, mouse, display, microphone, and the like.
In one embodiment, the electronic device in fig. 5 is a call ticket generating device, and the memory 601 stores computer-executable instructions that can be executed on the processor 602, and when executed by the processor 602, the following process is implemented:
acquiring charging rule data of communication cost input by a user, and determining at least one type of charging scene according to the charging rule data;
acquiring communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene.
Optionally, when executed by the processor, the computer-executable instructions determine at least one type of charging scenario according to the charging rule data, including: according to the charging rule data, determining charging relevant factors influencing a charging result from all preset charging factors; determining at least one type of charging scene according to various determined value conditions of the charging related factors; the preset charging factors comprise the communication state of a charging party, the communication state of a non-charging party and the usage amount of communication data between the charging party and the non-charging party.
Optionally, when the computer executable instructions are executed by the processor, before the obtaining, from a communication database, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scenario, and generating a communication data usage size value between the charging party and the non-charging party corresponding to the charging scenario, the method further includes: determining a first data requirement, a second data requirement and a third data requirement corresponding to the charging scene; the first data requirement is a data requirement corresponding to the communication state data of the charging party, and the second data requirement is a data requirement corresponding to the communication state data of the non-charging party; the third data requirement is a data requirement corresponding to a communication data usage value between the charging party and the non-charging party; the communication state data comprises a communication number, a communication number location identification, a communication number attribution identification, a communication role identification and a communication channel identification.
Optionally, when the computer executable instruction is executed by the processor, the number of the virtual ticket data is at least two; constructing virtual ticket data corresponding to the charging scene, including: determining the charging result of each piece of virtual ticket data according to the charging logic corresponding to the charging rule data; and sequentially constructing the virtual ticket data corresponding to various charging scenes according to the sequence of the charging results of the virtual ticket data from low to high.
In the embodiment of the application, at least one type of charging scene can be determined according to charging rule data input by a user, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene are obtained from a communication database, and a communication data usage value between the charging party and the non-charging party corresponding to the charging scene is generated, so that virtual ticket data corresponding to the charging scene is constructed according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value. Therefore, according to the embodiment of the application, the virtual ticket data can be automatically generated without manual field dialing and testing, so that the ticket generation efficiency is improved, the ticket generation cost is reduced, and the verification efficiency of the ticket charging result is improved.
It should be noted that the ticket generating device in this embodiment can implement each process of the foregoing ticket generating method embodiment, and achieve the same function and effect, which is not repeated here.
In another embodiment, the electronic device in fig. 5 is a ticket charging result verification device, the memory 601 stores computer-executable instructions that can be executed on the processor 602, and when executed by the processor 602, the computer-executable instructions implement the following processes:
generating virtual ticket data for the charging rule data input by the user by the ticket generating method;
calling a ticket charging system to be verified, and charging the generated virtual ticket data to obtain a first charging result;
charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and verifying whether the charging result of the call ticket charging system is accurate or not according to the first charging result and the second charging result.
Optionally, when the computer-executable instructions are executed by the processor, the method further comprises:
if the charging result of the call ticket charging system is not accurate after verification, determining target call ticket data with inaccurate charging result in each generated virtual call ticket data;
and outputting the target call ticket data so as to perform problem positioning on the call ticket charging system according to the target call ticket data.
In the embodiment of the application, by the ticket generating method, virtual ticket data is generated for charging rule data input by a user, a ticket charging system to be verified is called, the generated virtual ticket data is charged to obtain a first charging result, the generated virtual ticket data is charged according to charging logic corresponding to the charging rule data to obtain a second charging result, and whether the charging result of the ticket charging system is accurate or not is verified according to the first charging result and the second charging result. Therefore, according to the embodiment of the application, manual field dialing and testing are not needed, the virtual ticket data can be automatically generated, the accuracy of the ticket charging result can be verified, and therefore the verification efficiency of the ticket charging result is improved.
It should be noted that the ticket charging result verification device in this embodiment can implement each process of the foregoing ticket charging result verification method embodiment, and achieve the same function and effect, which is not repeated here.
Further, another embodiment of the present specification also provides a computer-readable storage medium, which in one embodiment is used for storing computer-executable instructions, and when the computer-executable instructions are executed by a processor, the following process is implemented:
acquiring charging rule data of communication cost input by a user, and determining at least one type of charging scene according to the charging rule data;
acquiring communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene.
Optionally, when executed by the processor, the computer-executable instructions determine at least one type of charging scenario according to the charging rule data, including: according to the charging rule data, determining charging relevant factors influencing a charging result from all preset charging factors; determining at least one type of charging scene according to various determined value conditions of the charging related factors; the preset charging factors comprise the communication state of a charging party, the communication state of a non-charging party and the usage amount of communication data between the charging party and the non-charging party.
Optionally, when the computer executable instructions are executed by a processor, before the communication state data of the charging party and the communication state data of the non-charging party corresponding to the charging scenario are acquired from a communication database, and a communication data usage size value between the charging party and the non-charging party corresponding to the charging scenario is generated, the method further includes: determining a first data requirement, a second data requirement and a third data requirement corresponding to the charging scene; the first data requirement is a data requirement corresponding to the communication state data of the charging party, and the second data requirement is a data requirement corresponding to the communication state data of the non-charging party; the third data requirement is a data requirement corresponding to a communication data usage value between the charging party and the non-charging party; the communication state data comprises a communication number, a communication number location identification, a communication number attribution identification, a communication role identification and a communication channel identification.
Optionally, when the computer executable instruction is executed by the processor, the number of the virtual ticket data is at least two; constructing virtual ticket data corresponding to the charging scene, including: determining the charging result of each piece of virtual ticket data according to the charging logic corresponding to the charging rule data; and sequentially constructing the virtual ticket data corresponding to various charging scenes according to the sequence of the charging results of the virtual ticket data from low to high.
In the embodiment of the application, at least one type of charging scene can be determined according to charging rule data input by a user, communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene are obtained from a communication database, and a communication data usage value between the charging party and the non-charging party corresponding to the charging scene is generated, so that virtual ticket data corresponding to the charging scene is constructed according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value. Therefore, according to the embodiment of the application, the virtual ticket data can be automatically generated without manual field dialing and testing, so that the ticket generation efficiency is improved, the ticket generation cost is reduced, and the verification efficiency of the ticket charging result is improved.
It should be noted that the storage medium in this embodiment can implement each process of the foregoing ticket generation method embodiment, and achieve the same function and effect, which is not repeated here.
In another embodiment, the computer-readable storage medium is used for storing computer-executable instructions, which when executed by a processor implement the following process: :
generating virtual ticket data for the charging rule data input by the user by the ticket generating method;
calling a ticket charging system to be verified, and charging the generated virtual ticket data to obtain a first charging result;
charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and verifying whether the charging result of the call ticket charging system is accurate or not according to the first charging result and the second charging result.
Optionally, when the computer executable instructions are executed by a processor, the method further comprises:
if the charging result of the call ticket charging system is not accurate after verification, determining target call ticket data with inaccurate charging result in each generated virtual call ticket data;
and outputting the target call ticket data so as to perform problem positioning on the call ticket charging system according to the target call ticket data.
In the embodiment of the application, by the ticket generating method, virtual ticket data is generated for charging rule data input by a user, a ticket charging system to be verified is called, the generated virtual ticket data is charged to obtain a first charging result, the generated virtual ticket data is charged according to charging logic corresponding to the charging rule data to obtain a second charging result, and whether the charging result of the ticket charging system is accurate or not is verified according to the first charging result and the second charging result. Therefore, according to the embodiment of the application, manual field dialing and testing are not needed, the virtual ticket data can be automatically generated, the accuracy of the ticket charging result can be verified, and therefore the verification efficiency of the ticket charging result is improved.
It should be noted that the storage medium in this embodiment can implement each process of the foregoing ticket charging result verification method embodiment, and achieve the same function and effect, which is not repeated here.
The computer-readable storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for generating call tickets, comprising:
acquiring charging rule data of communication cost input by a user, and determining at least one type of charging scene according to the charging rule data;
acquiring communication state data of a charging party and communication state data of a non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and constructing virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the usage amount value of the communication data corresponding to the charging scene.
2. The method of claim 1, wherein determining at least one type of charging scenario according to the charging rule data comprises:
according to the charging rule data, determining charging relevant factors influencing a charging result from all preset charging factors; determining at least one type of charging scene according to various determined value conditions of the charging related factors;
the preset charging factors comprise the communication state of a charging party, the communication state of a non-charging party and the usage amount of communication data between the charging party and the non-charging party.
3. The method according to claim 1, wherein before obtaining the communication state data of the charging party and the communication state data of the non-charging party corresponding to the charging scenario from a communication database, and generating the communication data usage size value between the charging party and the non-charging party corresponding to the charging scenario, the method further comprises:
determining a first data requirement, a second data requirement and a third data requirement corresponding to the charging scene; the first data requirement is a data requirement corresponding to the communication state data of the charging party, and the second data requirement is a data requirement corresponding to the communication state data of the non-charging party; the third data requirement is a data requirement corresponding to a communication data usage value between the charging party and the non-charging party;
the communication state data comprises a communication number, a communication number location identification, a communication number attribution identification, a communication role identification and a communication channel identification.
4. The method of claim 1, wherein the number of the virtual ticket data is at least two; constructing virtual ticket data corresponding to the charging scene, including:
determining the charging result of each piece of virtual ticket data according to the charging logic corresponding to the charging rule data;
and sequentially constructing the virtual ticket data corresponding to various charging scenes according to the sequence of the charging results of the virtual ticket data from low to high.
5. A method for verifying the charging result of a call ticket is characterized by comprising the following steps:
generating virtual ticket data for the charging rule data input by the user by the method of any one of claims 1 to 4;
calling a ticket charging system to be verified, and charging the generated virtual ticket data to obtain a first charging result;
charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and verifying whether the charging result of the call ticket charging system is accurate or not according to the first charging result and the second charging result.
6. The method of claim 5, further comprising:
if the charging result of the call ticket charging system is not accurate after verification, determining target call ticket data with inaccurate charging result in each generated virtual call ticket data;
and outputting the target call ticket data so as to perform problem positioning on the call ticket charging system according to the target call ticket data.
7. A ticket generating apparatus, comprising:
the system comprises an acquisition module, a charging module and a charging module, wherein the acquisition module is used for acquiring charging rule data of communication cost input by a user and determining at least one type of charging scene according to the charging rule data;
the determining module is used for acquiring the communication state data of the charging party and the communication state data of the non-charging party corresponding to the charging scene from a communication database, and generating a communication data usage value between the charging party and the non-charging party corresponding to the charging scene;
and the construction module is used for constructing the virtual ticket data corresponding to the charging scene according to the communication state data of the charging party, the communication state data of the non-charging party and the communication data usage value corresponding to the charging scene.
8. A bill charging result verification device is characterized by comprising:
a generating module, configured to generate virtual ticket data for the charging rule data input by the user according to the method of any one of claims 1 to 4;
the first charging module is used for calling a ticket charging system to be verified, charging the generated virtual ticket data and obtaining a first charging result;
the second charging module is used for charging the generated virtual ticket data according to the charging logic corresponding to the charging rule data to obtain a second charging result;
and the verification module is used for verifying whether the charging result of the ticket charging system is accurate or not according to the first charging result and the second charging result.
9. An electronic device comprising a memory and a processor, the memory having stored thereon computer-executable instructions that, when executed on the processor, are capable of performing the steps of the method of any of claims 1-5 or any of claims 6-7.
10. A storage medium having stored thereon computer-executable instructions, which when executed by a processor, are capable of performing the steps of the method of any of claims 1-5 or any of claims 6-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911291082.9A CN112995934A (en) | 2019-12-16 | 2019-12-16 | Call bill generating method and device and call bill charging result verifying method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911291082.9A CN112995934A (en) | 2019-12-16 | 2019-12-16 | Call bill generating method and device and call bill charging result verifying method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112995934A true CN112995934A (en) | 2021-06-18 |
Family
ID=76343006
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911291082.9A Pending CN112995934A (en) | 2019-12-16 | 2019-12-16 | Call bill generating method and device and call bill charging result verifying method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112995934A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101730043A (en) * | 2008-10-29 | 2010-06-09 | 中国移动通信集团吉林有限公司 | Pricing test method and system |
| CN102014364A (en) * | 2011-01-05 | 2011-04-13 | 湖南大学 | Semiautomatic charging accuracy testing method based on virtual call test |
| CN102340756A (en) * | 2010-07-21 | 2012-02-01 | 中国移动通信集团福建有限公司 | Charge test method and charge test device |
| WO2014200427A1 (en) * | 2013-06-14 | 2014-12-18 | Nt8 Software Solutions (Singapore) Pte Ltd | Verification method and system |
| CN105245396A (en) * | 2014-07-11 | 2016-01-13 | 华为软件技术有限公司 | Fee verification method and fee verification system |
| CN105553677A (en) * | 2015-12-04 | 2016-05-04 | 中国移动通信集团广东有限公司 | Charging verification audit system |
| CN108632047A (en) * | 2017-03-21 | 2018-10-09 | 华为技术有限公司 | A kind of determination method and device of tariff data |
| CN109871309A (en) * | 2017-12-04 | 2019-06-11 | 中国移动通信集团公司 | A kind of charge system test cases generation method and system |
-
2019
- 2019-12-16 CN CN201911291082.9A patent/CN112995934A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101730043A (en) * | 2008-10-29 | 2010-06-09 | 中国移动通信集团吉林有限公司 | Pricing test method and system |
| CN102340756A (en) * | 2010-07-21 | 2012-02-01 | 中国移动通信集团福建有限公司 | Charge test method and charge test device |
| CN102014364A (en) * | 2011-01-05 | 2011-04-13 | 湖南大学 | Semiautomatic charging accuracy testing method based on virtual call test |
| WO2014200427A1 (en) * | 2013-06-14 | 2014-12-18 | Nt8 Software Solutions (Singapore) Pte Ltd | Verification method and system |
| CN105245396A (en) * | 2014-07-11 | 2016-01-13 | 华为软件技术有限公司 | Fee verification method and fee verification system |
| CN105553677A (en) * | 2015-12-04 | 2016-05-04 | 中国移动通信集团广东有限公司 | Charging verification audit system |
| CN108632047A (en) * | 2017-03-21 | 2018-10-09 | 华为技术有限公司 | A kind of determination method and device of tariff data |
| CN109871309A (en) * | 2017-12-04 | 2019-06-11 | 中国移动通信集团公司 | A kind of charge system test cases generation method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110557729B (en) | Roaming charging method and device | |
| EP2159960A1 (en) | Billing testing method and billing device | |
| CN108632047B (en) | Method and device for determining tariff data | |
| WO2012171369A1 (en) | Method and system for calculating call charge of terminal | |
| CN113112254A (en) | Regional message sharing method and device | |
| CN106484603A (en) | A kind of service test method and device | |
| CN109327815B (en) | Income calculation method and device for logic station | |
| CN113037510A (en) | Charging method, charging device and computer readable storage medium | |
| CN115099839A (en) | Data auditing method, device and storage medium | |
| CN111209060A (en) | Capability development platform processing method and device | |
| EP3104550B1 (en) | Mobile digital cellular telecommunication system with advanced functionality for rating correction | |
| CN115150764B (en) | Tariff configuration method, tariff configuration device, tariff configuration equipment and tariff configuration medium | |
| CN112995934A (en) | Call bill generating method and device and call bill charging result verifying method and device | |
| CN111984519A (en) | Test method and device for service system | |
| CN1322706C (en) | Method of realizing real time segmental charging | |
| US8625758B2 (en) | Method, a telecommunication system and a network node for sponsoring a communication service | |
| CN110300000B (en) | Charging mode changing method and device, electronic equipment and readable storage medium | |
| CN108964932A (en) | A kind of charging method, device and computer readable storage medium | |
| CN113129091B (en) | Recommendation method and device for tariff package | |
| CN113011869A (en) | Test data generation method and device and computer readable storage medium | |
| EP3331196A1 (en) | Telecommunication system for monitoring and controlling of a network providing resource to a user | |
| CN115131085A (en) | Method, device and equipment for processing super package bills | |
| CN113657635A (en) | Method for predicting communication user loss and electronic equipment | |
| CN109636190B (en) | Method and device for acquiring base station operation information | |
| US9432523B1 (en) | System, method, and computer program for rerating customer events in parallel with executing one or more open sessions in a consumer telecommunication network |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210618 |