CN117202251A - Method, device and storage medium for generating and testing ticket - Google Patents

Abstract

The present disclosure provides a ticket generating and testing method, device and storage medium, wherein the method comprises: generating a ticket file based on ordering information and office data information of a product service; judging whether field information in the ticket file is consistent with office data information or not, and judging whether text expression errors exist in the ticket file or not; under the first situation, the ticket cost is calculated, and the ticket cost is compared with the charging result of the service operation support system, wherein the first situation is that field information in the ticket file is consistent with office data information and text expression errors do not exist in the ticket file; and outputting first information for indicating the passing of the test in response to the fact that the ticket cost is the same as the charging result of the service operation support system.

Description

Method, device and storage medium for generating and testing ticket

Technical Field

The present disclosure relates to the field of natural language processing, and in particular, to a ticket generating and testing method, device, and storage medium.

Background

And the user orders AI products in the mobile cloud service network, and enjoys the free amount provided every day after opening the service, and performs step charging according to times after exceeding the free amount. The automatic testing tool of open source is usually used manually to call the algorithm capability, generate the corresponding ticket file, the fields such as the manual call quantity and office data are compared with the key fields in the ticket file according to the algorithm capability, and when the step call quantity reaches more than one million levels, the ticket file generation, the ticket key field check and verification and the step cost calculation are all extremely time-consuming and energy-consuming.

Disclosure of Invention

The present disclosure provides a ticket generation and test method, device, and storage medium to solve the problems in the related art, and the method can complete an automated test of cross-ladder ticket generation, data verification, and fee billing.

An embodiment of a first aspect of the present disclosure provides a ticket generating and testing method, including: generating a ticket file based on the order information and office data information of the product service; judging whether field information in the ticket file is consistent with office data information or not, and judging whether text expression errors exist in the ticket file or not; under the first situation, the ticket cost is calculated, and the ticket cost is compared with the charging result of the service operation support system, wherein the first situation is that field information in the ticket file is consistent with office data information and text expression errors do not exist in the ticket file; and outputting first information for indicating that the test is passed in response to the ticket cost being the same as the charging result of the service operation support system.

In some embodiments of the present disclosure, the method further comprises: in a second case, outputting second information, the second information being used to indicate that the test fails, wherein the second case includes: the key fields in the ticket file are inconsistent with the ordering data of the product service, and/or the ticket file has text expression errors, and/or the ticket cost is different from the charging result of the business operation support system.

In some embodiments of the present disclosure, before generating the ticket file based on the order information and the office data information of the product service, the method further comprises: order information and office data information of product services are acquired.

In some embodiments of the present disclosure, obtaining order information and office data information for a product service includes: acquiring the type of the product service and a bill specification file; invoking an order interface corresponding to the product service, opening the product service, and storing order information of the product service, wherein the order information at least comprises opening time and order number; and calling a local data interface of the product service to acquire local data information, wherein the local data information at least comprises a charging mode, unit price and total amount, and the charging mode at least comprises a step charging rule.

In some embodiments of the present disclosure, generating the ticket file based on the order information and the office data information of the product service includes: from the opening time of the product service, carrying out call ticket data construction once at intervals of a first preset time according to the right interval forward of the ladder charging rule; judging whether the call ticket data is constructed successfully or not according to the status code returned by the product capability request interface; and generating a corresponding bill file based on the bill specification file in response to successful bill data construction.

In some embodiments of the present disclosure, determining whether there is a text expression error in the ticket file includes: traversing the ticket file, analyzing text description information in the ticket file, and performing intelligent text correction by using an AI text correction algorithm to obtain a correction result; judging whether a word expression error exists in the ticket file according to the error correction result, wherein the word expression error comprises at least one of the following: sentence redundancy, punctuation errors, word errors, etc.

In some embodiments of the present disclosure, calculating the ticket cost includes: traversing the office data information through an AI keyword extraction algorithm, and extracting charging rules in the office data information; and calculating the bill cost according to the charging rule.

An embodiment of a second aspect of the present disclosure provides a ticket generating and testing apparatus, including: the generation module is used for generating a ticket file based on the ordering information and office data information of the product service; the judging module is used for judging whether field information in the ticket file is consistent with the office data information or not and judging whether text expression errors exist in the ticket file or not through an artificial intelligence AI text error correction algorithm; the system comprises a calculation module, a service operation support system and a word list management module, wherein the calculation module is used for calculating the cost of the word list through an AI keyword extraction algorithm under the first condition, and comparing the cost of the word list with the charging result of the service operation support system, wherein the first condition is that field information in the word list file and information in office data are included, and text expression errors do not exist in the word list file; and the output module is used for responding to the fact that the ticket cost is the same as the charging result of the service operation support system, and outputting first information which is used for indicating that the test is passed.

An embodiment of a third aspect of the present disclosure proposes a communication device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described in the embodiments of the first aspect of the present disclosure.

An embodiment of a fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method described in the embodiment of the first aspect of the present disclosure.

In summary, the ticket generating and testing method provided by the present disclosure includes generating a ticket file based on order information and office data information of a product service; judging whether field information in the ticket file is consistent with office data information or not, and judging whether text expression errors exist in the ticket file or not; under the first situation, the ticket cost is calculated, and the ticket cost is compared with the charging result of the service operation support system, wherein the first situation is that field information in the ticket file is consistent with office data information and text expression errors do not exist in the ticket file; and outputting first information for indicating the passing of the test in response to the fact that the ticket cost is the same as the charging result of the service operation support system.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

Fig. 1 is a schematic flow chart of a ticket generating and testing method according to an embodiment of the disclosure;

FIG. 2 is a flow chart of a ticket generating and testing method according to an embodiment of the present disclosure;

FIG. 3 is a main flow chart of a ticket generating and testing method according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a ticket generating and testing device according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram of a hardware composition structure of a communication device according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure.

And the user orders AI products in the mobile cloud service network, and enjoys the free amount provided every day after opening the service, and performs step charging according to times after exceeding the free amount. The method is characterized in that an open source automatic test tool is manually used for calling algorithm capability, AI voice dictation capability is taken as an example, day calling steps are (0,500), (500,30 ten thousand), (30 ten thousand, 100 ten thousand), (100 ten thousand, 300 ten thousand), (300 ten thousand, 500 ten thousand and more than 500 ten thousand, according to different ladder specifications, an open source automatic test tool such as Jmeter, postman, filder and the like is manually used for calling interface capability batch, and a ticket file is correspondingly generated.

The disadvantages of the ladder ticket test in the related art mainly include that firstly, the mobile cloud AI capability is used in the related art, and the product ordering can be completed only by manually selecting regions and available areas on the product ordering page, charging modes and checking service protocols; secondly, after the algorithm capability is opened, a user needs to manually call the algorithm capability according to the ladder specification to generate a corresponding ticket file; thirdly, manually checking wrongly written words, wrongly used words, wrongly punctuation and the like in the ticket standard file; secondly, the word segment of the ticket is complex, the assertion is lacking, the problem that the ticket cannot be positioned quickly is solved, and the user needs to manually compare the fields such as the call quantity and office data with the key fields in the ticket file according to the algorithm capability; finally, the inter-step charging rule is complex, and the user needs to manually calculate the charging amount.

All the above points need to manually open service, read the bill rules Fan Wenjian, generate bill files, and then test the format of the conversation bill and the key fields of the bill. Not only consumes energy and time, but also has extremely high probability of manual misoperation, and seriously influences the test efficiency and the engineering construction progress.

In order to solve the problems in the related art, the present disclosure provides a method for generating and testing a ticket, where the method can complete the following test by only providing a ticket specification document and a product type (product type), including calling a mobile cloud AI subscription interface, and automatically completing the opening of product service capability; according to the opening time of the product, automatically constructing ticket data at preset time intervals according to the right interval forward of the office data ladder rule, and generating a corresponding ticket file; automatically traversing word description information in a ticket document, acquiring key fields of the ticket, and automatically judging whether information such as punctuation errors, word errors, pen errors and the like exists in the document by using a word error correction algorithm; according to the step call quantity and the value in office data, automatically making assertion comparison with the content of the bill file, including whether the generated bill data is correct or not; and automatically traversing office data ladder charging rules and automatically calculating ticket cost.

The present disclosure will be described in further detail with reference to the accompanying drawings and specific embodiments.

Fig. 1 is a schematic flow chart of a ticket generating and testing method according to an embodiment of the disclosure. The ticket generation and test method provided by the embodiment of the disclosure comprises the following steps:

step 101, generating a ticket file based on the order information and office data information of the product service.

In the embodiment of the disclosure, the product service mainly refers to a cloud service on a cloud platform, and the cloud service comprises services based on cloud computing technology, adopting an internet mode, providing basic resources, platform capability, software application and the like.

In some embodiments of the present disclosure, the product services include AI (Artificial Intelligence ) class of business, such as AI speech dictation, AI scoring, real-name authentication, and the like.

In an embodiment of the present disclosure, a ticket (Call Detail Record, CDR) file is used to record the process of using a product service by a user, and the ticket file is automatically generated according to a preset document format.

In some embodiments, prior to generating the ticket file based on the order information and office data ladder information for the product service, the method further comprises: and acquiring ordering information and office data cross-ladder information of the product service.

In some embodiments, obtaining order information and office data cross-ladder information for a product service includes: the method comprises the steps of obtaining the type of product service, calling a corresponding ordering interface of the product service according to the type of the product service, opening the product service capability, obtaining ordering information of the product service, calling an office data interface of the product service, and obtaining office data information. Taking AI speech dictation capability as an example, acquiring the type of the product service as the AI speech dictation capability, automatically calling a subscription interface of the corresponding AI speech dictation capability on the cloud platform, opening the AI speech dictation capability, generating an order, reserving information such as order number OrderID, time stamp TimeStamp, client code and the like corresponding to the order, automatically calling the AI speech dictation capability interface, and acquiring office data key information including information such as charging mode charge mode, unit price, total Amount of money Amount and the like.

In some embodiments of the present disclosure, the charging method for the product service is step charging, the obtained office data information includes step charging rules, for example, the step charging rules are that the daily call volume of the product service reaches (0,500) and (500,30 ten thousand) charging standards are 0.02 yuan/time and 0.01 yuan/time respectively.

It should be noted that the related art requires a user to manually order at an order page when ordering a product service, and in the embodiment of the present disclosure, an order interface is automatically called to order according to the type of the provided product service.

Step 102, judging whether the field information in the ticket file is consistent with the office data information, and judging whether the word expression error exists in the ticket file.

In some embodiments of the present disclosure, the field information in the ticket file is compared with the office data information by asserting, and whether the field information in the ticket is consistent with the key information such as the field and the call volume in the office data is determined.

In some embodiments of the present disclosure, a ticket file is traversed, text description information in the ticket file is obtained, a text error correction algorithm is used to determine whether error information such as punctuation errors, word errors, pen errors, and the like exist in the ticket file, if no text expression errors exist in the ticket file, the method is continuously executed, if yes, the test is failed, and the test is ended.

It should be noted that the present disclosure is not limited in order between determining whether field information in the ticket file is consistent with office data information and determining whether there is a text expression error in the ticket file.

Step 103, in the first situation, the ticket cost is calculated, and the ticket cost is compared with the charging result of the service operation support system, wherein in the first situation, the field information in the ticket file is consistent with the office data information, and the word expression error does not exist in the ticket file.

In an embodiment of the present disclosure, ticket fees are automatically calculated when field information in the ticket file is consistent with office data information and there is no text expression error.

In some embodiments of the present disclosure, a key extraction algorithm is employed to traverse office data ladder billing rules and calculate ticket costs based on the office data ladder billing rules.

In the embodiment of the disclosure, the charging result of the service operation support system is used as a standard to determine whether the calculated ticket cost is correct, wherein the service operation support system (Business & Operation Support System, BOSS) is developed from the charging system of the telecommunication department, and covers the functions of the previous charging, settlement, business, accounting, customer service and other systems, and performs centralized and unified planning and integration on various service functions.

And 104, outputting first information for indicating that the test is passed in response to the ticket cost being the same as the charging result of the service operation support system.

In the embodiment of the present disclosure, as can be seen from the combination of step 103 and step 104, the method may be used for generating a ticket file and calculating ticket cost, and testing whether the generated ticket file and ticket cost are correct, if the data in the ticket file is consistent with office data information, the ticket file has no text expression error and the ticket cost is calculated correctly, the test passes, and thus automatic verification of the generated ticket file, ticket document format and ticket cost is realized.

In some embodiments of the present disclosure, the method further comprises: and judging whether the bill cost is the same as the charging result of the service operation support system.

In some embodiments of the present disclosure, the method further comprises: in a second case, outputting second information, the second information being used to indicate that the test fails, wherein the second case includes: the key fields in the ticket file are inconsistent with the ordering data of the product service, and/or the ticket file has text expression errors, and/or the ticket cost is different from the charging result of the business operation support system.

In summary, the solution provided by the present disclosure includes generating a ticket file based on subscription information and office data information of a product service; judging whether field information in the ticket file is consistent with office data information or not, and judging whether text expression errors exist in the ticket file or not; under the first situation, the ticket cost is calculated, and the ticket cost is compared with the charging result of the service operation support system, wherein the first situation is that field information in the ticket file is consistent with office data information and text expression errors do not exist in the ticket file; and outputting first information for indicating the passing of the test in response to the fact that the ticket cost is the same as the charging result of the service operation support system.

As shown in fig. 2, fig. 2 is a flow chart of a ticket generating and testing method according to an embodiment of the present disclosure, and the embodiment of fig. 2 is further disclosed based on the embodiment shown in fig. 1. The ticket generation and test method provided by the embodiment of the disclosure comprises the following steps:

in step 201, the type of product service and the ticket specification document are obtained.

In some embodiments of the present disclosure, the product services include AI (Artificial Intelligence ) class business, and the types of product services include AI speech dictation, AI scoring, real name authentication, and the like.

In some embodiments of the present disclosure, obtaining the type of product service includes obtaining a type of product service entered by a user.

In some embodiments of the present disclosure, the ticket gauge Fan Wenjian is used to gauge the file format of the ticket file, e.g., a canonical ticket file in the ticket gauge file is composed of a header record, a ticket record, and a tail record, a canonical field value length, a field arrangement order, a field in which a canonical ticket needs to be recorded, a fill-in requirement, and so on.

Step 202, calling an order interface corresponding to the product service, opening the product service, and storing order information of the product service, wherein the order information at least comprises opening time and order number.

In some embodiments of the present disclosure, according to a product service such as AI speech dictation capability required by a user, an order interface corresponding to the product service is automatically invoked, the product service is opened, and an order number OrderID and a TimeStamp corresponding to the order are reserved.

Step 203, calling a local data interface of the product service to obtain local data information, wherein the local data information at least comprises a charging mode, unit price and total amount, and the charging mode at least comprises a step charging rule.

In some embodiments of the present disclosure, an office data interface of a product service is automatically invoked to obtain office data key information, such as obtaining field information of charging mode (charge mode), total Amount (Amount), unit price (UnitPrice) and the like in office data.

And 204, starting from the opening time of the product service, carrying out call ticket data construction once at intervals of a first preset time according to the right interval forward of the ladder charging rule.

In some embodiments of the present disclosure, the charging mode of the product service is a step charging, taking the AI speech dictation service as an example, the AI speech dictation algorithm capability calls steps of (0,500), (500,30 tens of thousands), (30 tens of thousands, 100 tens of thousands), (100 tens of thousands, 300 tens of thousands), (300 tens of thousands, 500 tens of thousands, and more than 500 tens of thousands, and the charging standards of different steps are different, for example, the daily adjustment amount reaches 400, the unit price is 0.05 each time, the daily adjustment amount reaches 20 tens of thousands, the unit price within 500 is 0.05 each time, more than 500 times, and the unit price of 501 to 20 tens of thousands is 0.02 each time.

In some embodiments of the present disclosure, the designed automatic generation ticket is automatically constructed according to the information acquired in steps 202 and 203, using the Python language and Pytest framework, according to the opening time, the right interval of the ladder charging rule and the following time, and the ticket data is automatically constructed every 1 hour, and the interface is invoked to insert the data into the ES (Elasticsearch) server.

It should be noted that, according to the right interval of the ladder charging rule, the call ticket data construction is performed once every a first preset time, which is favorable for successfully constructing the cross-ladder data, and the cross-ladder data refers to the call ticket data spanning two or more ladder charging rule intervals.

Further, in some embodiments of the present disclosure, according to the information obtained in steps 202 and 203, using Python language and Pytest frame, aggregating the usage amount of each user algorithm capability through a user number calling table, traversing the aggregation result, querying each user, obtaining the instance id corresponding to each algorithm, obtaining order data such as opening time, ordering relation, charging mode, order number (orderlnumber), customer code, etc. through a bill dependent information interface, generating a bill record according to the right section of the ladder rule, and storing the bill data into ES.

And step 205, judging whether the call ticket data is successfully constructed according to the status code returned by the product capability request interface.

In some embodiments of the present disclosure, as shown in fig. 5, according to the product capability request interface response status code, whether the cross-ladder data is constructed successfully is primarily determined, and if the status code is OK, it is indicated that the cross-ladder call volume is constructed successfully; if not OK is returned, the cross-ladder call ticket construction fails.

And step 206, responding to successful ticket construction, and generating a corresponding ticket file based on the ticket standard file.

In some embodiments, the method further comprises: in response to the ticket data construction failure, returning to step 204, the ticket data construction is resumed.

Step 207, it is determined whether the field information in the ticket file is consistent with the office data information.

In some embodiments of the present disclosure, after a preset time for generating ticket data according to step 204, it is determined whether field information in the ticket file is consistent with office data information.

In some embodiments of the present disclosure, if a ticket is constructed once every 1 hour, a corresponding ticket file is obtained according to a subscription relationship of a user subscribing to a product service according to the next 1 hour 15 minutes of the last generated ticket, and the ticket file information is compared with office data information obtained in step 203, so as to determine whether field information in the ticket is consistent with key information such as fields (e.g. ChargeMode, amount, unitPrice) and call volume in the office data.

In some embodiments, the method further comprises: in response to the field information in the ticket file not being consistent with the office data information, step 2013 is executed, and second information is output, wherein the second information is used for indicating that the test is not passed and the test is ended.

In some embodiments, field information in the ticket file is compared with office data information in an assertion manner, that is, if the result is correct, the method of the disclosure is continuously executed, and if the result is wrong, the method of the disclosure is stopped, so that the problem in the ticket file can be quickly located, and manual check is not needed.

And step 208, traversing the ticket file, analyzing the text description information in the ticket file, and performing intelligent text correction by using an AI text correction algorithm to obtain a correction result.

In some embodiments of the disclosure, an automatic ticket file intelligently parses text description information in the ticket file according to an AI text extraction algorithm, and then uses an AI text correction algorithm to perform intelligent text correction on the text description in the ticket file to obtain an AI intelligent text correction result.

Step 209, judging whether the word expression error exists in the ticket file according to the error correction result.

In some embodiments of the present disclosure, the text expression error includes at least one of: sentence redundancy, punctuation errors, word errors, etc.

In some embodiments of the present disclosure, it is determined whether there is a text expression error in the ticket document based on the AI intelligent text correction result.

In some embodiments, the method further comprises: and in response to the text expression error in the ticket file, executing step 2013, and outputting second information, wherein the second information is used for indicating that the test is not passed and ending the test.

Step 2010, calculating ticket cost in response to the field information in the ticket file being consistent with the office data information and the ticket file having no text expression errors.

In some embodiments of the present disclosure, calculating the ticket cost includes: traversing the office data information through an AI keyword extraction algorithm, and extracting charging rules in the office data information; and calculating the bill cost according to the charging rule.

And step 2011, judging whether the bill cost is consistent with the charging result of the service operation support system.

In step 2012, in response to the ticket fee being consistent with the billing result of the service operation support system, first information is output, the first information being used to indicate that the test passes.

In some embodiments, the method further comprises: and in response to the ticket fee not consistent with the charging result of the service operation support system, executing step 2013, and outputting second information, wherein the second information is used for indicating that the test is not passed and ending the test.

In summary, the embodiment of the disclosure provides a new idea of automatic generation and test of a step-crossing ticket, and according to order time and step-crossing information of office data, automatic order and automatic accurate generation of step-crossing ticket data are realized by combining an intelligent algorithm based on the new idea, and step-crossing ticket cost is automatically calculated, wherein the embodiment of the disclosure can rapidly extract key information in office data to assist in ticket generation and test by using an AI keyword extraction algorithm, and traverse ticket documents by using an AI text error correction algorithm to perform text error correction, solve text errors which are not easy to find by manpower, improve document verification efficiency and document accuracy, and save a large amount of manpower investment.

The embodiment of the disclosure also provides a ticket generating and testing device, as shown in fig. 4. Fig. 4 is a schematic structural diagram of a ticket generating and testing device according to an embodiment of the present disclosure, where the ticket generating and testing device 300 includes:

a generation module 310 for generating a ticket file based on the order information and office data information of the product service;

a judging module 320, configured to judge whether field information in the ticket file is consistent with the office data information, and judge whether a text expression error exists in the ticket file through an artificial intelligence AI text error correction algorithm;

the calculating module 330 is configured to calculate a ticket fee according to an AI keyword extraction algorithm, and compare the ticket fee with a charging result of a service operation support system, where the first case is that field information in the ticket file and information in office data are in the ticket file, and there is no text expression error in the ticket file;

and the output module 340 is configured to output first information in response to the ticket fee being the same as the charging result of the service operation support system, where the first information is used to indicate that the test passes.

In some embodiments of the present disclosure, the output module 340 is further to: in a second case, outputting second information, the second information being used to indicate that the test fails, wherein the second case includes: the key fields in the ticket file are inconsistent with the ordering data of the product service, and/or the ticket file has text expression errors, and/or the ticket cost is different from the charging result of the business operation support system.

In some embodiments of the present disclosure, the apparatus further includes an obtaining module for obtaining order information and office data information of the product service before generating the ticket file based on the order information and office data information of the product service.

In some embodiments of the present disclosure, the obtaining module is specifically configured to: acquiring the type of the product service and a bill specification file; invoking an order interface corresponding to the product service, opening the product service, and storing order information of the product service, wherein the order information at least comprises opening time and order number; and calling a local data interface of the product service to acquire local data information, wherein the local data information at least comprises a charging mode, unit price and total amount, and the charging mode at least comprises a step charging rule.

In some embodiments of the present disclosure, the generating module 310 is specifically configured to: from the opening time of the product service, carrying out call ticket data construction once at intervals of a first preset time according to the right interval forward of the ladder charging rule; judging whether the call ticket data is constructed successfully or not according to the status code returned by the product capability request interface; and generating a corresponding bill file based on the bill specification file in response to successful bill data construction.

In some embodiments of the present disclosure, the determining module 320 is specifically configured to: traversing the ticket file, analyzing text description information in the ticket file, and performing intelligent text correction by using an AI text correction algorithm to obtain a correction result; judging whether a word expression error exists in the ticket file according to the error correction result, wherein the word expression error comprises at least one of the following: sentence redundancy, punctuation errors, word errors, etc.

In some embodiments of the present disclosure, the computing module 330 is specifically configured to: traversing the office data information through an AI keyword extraction algorithm, and extracting charging rules in the office data information; and calculating the bill cost according to the charging rule.

In summary, according to the ticket generating and testing device disclosed by the disclosure, the automatic testing of step-crossing ticket generation, data verification and fee charging is completed through the generating module, the judging module, the calculating module and the output module.

The ticket generating and testing device provided in the above embodiment belongs to the same concept as the ticket generating and testing method embodiment provided in the embodiment of the present disclosure, and the specific implementation process of the ticket generating and testing device is detailed in the method embodiment and will not be described herein.

Fig. 5 is a schematic diagram of a hardware composition structure of a communication device according to an embodiment of the disclosure, as shown in fig. 5, the communication device 400 includes at least one processor 402; and a memory 401 communicatively coupled to the at least one processor 402; wherein the memory 401 stores instructions executable by the at least one processor 402, the instructions being executable by the at least one processor 402 to implement the steps of the VPN access method for a control device according to the embodiments of the present disclosure; alternatively, the instructions are executed by the at least one processor 402 to implement the steps of the embodiments of the present disclosure as applied to ticket generation and testing methods.

Optionally, the communication device may be specifically a control device in the embodiment of the present application, and the communication device may implement a corresponding flow implemented by the control device in each method in the embodiment of the present application, which is not described herein for brevity.

It will be appreciated that communication interface 403 is also included in the communication device. The various components in the communication device are coupled together by a bus system 404. It is appreciated that the bus system 404 serves to facilitate connected communications between these components. The bus system 404 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as bus system 404 in fig. 5.

It will be appreciated that memory 401 may be volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory

And a nonvolatile memory. Wherein the non-volatile Memory may be a Read Only Memory (ROM), a programmable Read Only Memory (PROM, programmable ReadOnly Memory), an erasable programmable Read Only Memory (EPROM, erasable Programmable Read Only Memory), an electrically erasable programmable Read Only Memory (EEPROM, electrically Erasable Programmable Read Only Memory), a magnetic random access Memory (FRAM, ferromagnetic random access Memory), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a compact disk Read Only (CD ROM, compact Disc Read Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The memory 401 described in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The methods disclosed in the embodiments of the present disclosure described above may be applied to the processor 402 or implemented by the processor 402. The processor 402 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the methods described above may be performed by integrated logic circuitry in hardware or instructions in software in processor 402. The processor 402 may be a general purpose processor, DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. Processor 402 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the application can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium in the memory 401 and the processor 402 reads the information in the memory 401, in combination with its hardware, to perform the steps of the method as described above.

In an exemplary embodiment, the communication device may be implemented by one or more application specific integrated circuits (ASIC, application Specific Integrated Circuit), DSP, programmable logic device (PLD, programmable Logic Device), complex programmable logic device (CPLD, complex Programmable Logic Device), FPGA, general purpose processor, controller, MCU, microprocessor, or other electronic element for performing the aforementioned methods.

The present public security embodiment also provides a non-transitory computer readable storage medium storing computer instructions, where the computer instructions are configured to cause the computer to implement the steps of the VPN access method applied to the control device according to the embodiment of the present application when executed; or, the computer instructions are used for implementing the steps of the VPN access method applied to the VPN client according to the embodiment of the present application when the computer executes the steps.

Optionally, the computer readable storage medium may be applied to the control device in the embodiment of the present application, and the computer instructions cause the computer to execute corresponding processes implemented by the control device in each method of the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer readable storage medium may be applied to the VPN client in the embodiment of the present application, and the computer instructions cause a computer to execute corresponding processes implemented by the VPN client in each method of the embodiment of the present application, which are not described herein for brevity.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.

The units described as separate units may or may not be physically separate, and units 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.

Alternatively, the above-described integrated units of the present application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in essence or a part contributing to the prior art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A ticket generating and testing method, the method comprising:

generating a ticket file based on the order information and office data information of the product service;

judging whether field information in the ticket file is consistent with the office data information or not, and judging whether text expression errors exist in the ticket file or not;

in a first situation, calculating ticket cost, and comparing the ticket cost with a charging result of a business operation support system BOSS, wherein in the first situation, field information in a ticket file is consistent with office data information, and text expression errors do not exist in the ticket file;

and outputting first information in response to the ticket expense being the same as the charging result of the service operation support system, wherein the first information is used for indicating that the test is passed.

2. The method according to claim 1, wherein the method further comprises:

in a second case, outputting second information, the second information being used to indicate that the test does not pass, wherein the second case includes: the key fields in the ticket file are inconsistent with the ordering data of the product service, and/or the ticket file has text expression errors, and/or the ticket cost is different from the charging result of the business operation support system.

3. The method according to claim 1 or 2, wherein before generating a ticket file based on the order information and office data information of the product service, the method further comprises:

and acquiring order information of the product service and the office data information.

4. A method according to claim 3, wherein said obtaining subscription information for said product service and said office data information comprises:

acquiring the type of the product service and a bill specification file;

invoking an order interface corresponding to the product service, opening the product service, and storing order information of the product service, wherein the order information at least comprises opening time and order number;

and calling a local data interface of the product service to acquire local data information, wherein the local data information at least comprises a charging mode, unit price and total amount, and the charging mode at least comprises a step charging rule.

5. The method of claim 4, wherein generating a ticket file based on the order information and the office data information of the product service comprises:

from the opening time of the product service, carrying out call ticket data construction once at intervals of a first preset time according to the right interval forward of the ladder charging rule;

judging whether the call ticket data is constructed successfully or not according to the status code returned by the product capability request interface;

and generating a corresponding bill file based on the bill specification file in response to the bill data construction success.

6. The method of claim 1, wherein said determining whether there is a text expression error in the ticket file comprises:

traversing the ticket file, analyzing word description information in the ticket file, and performing intelligent text correction by using an AI text correction algorithm to obtain a correction result;

judging whether a text expression error exists in the ticket file according to the error correction result, wherein the text expression error comprises at least one of the following: sentence redundancy, punctuation errors, word errors, etc.

7. The method of claim 1, wherein calculating a ticket cost comprises:

traversing the office data information through an AI keyword extraction algorithm, and extracting charging rules in the office data information;

and calculating the bill cost according to the charging rule.

8. A ticket generating and testing apparatus, the apparatus comprising:

the generation module is used for generating a ticket file based on the ordering information and office data information of the product service;

the judging module is used for judging whether field information in the ticket file is consistent with the office data information or not and judging whether text expression errors exist in the ticket file or not through an artificial intelligence AI text error correction algorithm;

the system comprises a calculation module, a service operation support system and a word list management module, wherein the calculation module is used for calculating the cost of the word list through an AI keyword extraction algorithm under the first condition, and comparing the cost of the word list with the charging result of the service operation support system, wherein the first condition is that field information in the word list file and information in office data are included, and text expression errors do not exist in the word list file;

and the output module is used for responding to the fact that the ticket cost is the same as the charging result of the service operation support system, and outputting first information which is used for indicating that the test is passed.

9. A communication device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 7.

10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1 to 7.