Phone bill query telephone charge cost accounting method and related equipment

Abstract

The invention discloses a ticket query telephone charge cost accounting method and related equipment, and relates to the field of charge accounting, and the method comprises the steps: obtaining a ticket file, and carrying out the analysis and storage of the ticket file according to a session ID; classifying the dialogue lists according to the device address and matching the dialogue lists with department information and a staff number table; executing call record query and export according to calling, called, courtyard and time conditions; carrying out call-out detail statistics according to dimensions of numbers, departments and the like, and obtaining call-out times, duration, cost and an internal line call result; and telephone charge classification accounting is performed according to enterprise fee deduction rules in a specified period, and department cost telephone charge, departure personnel telephone charge, salary card withholding and cash payment reports are generated. According to the method, efficient collaborative management of call query, call-out statistics and telephone charge accounting is realized.

Description

Technical Field

[0001] This specification relates to the field of cost accounting, and more specifically, this application relates to a method and related equipment for calculating telephone cost through call detail record (CDR) inquiry. Background Technology

[0002] Existing methods for call record inquiries and telephone bill calculations primarily rely on operator service centers. Users typically need to bring identification documents and application materials stamped with the official seal to the site, resulting in a complex and time-consuming process. Furthermore, the inquiry methods are limited, only allowing printing of call records for a fixed time period, lacking exportable text or table formats. Due to the large volume of call records, manual verification is prone to omissions, and calls between internal short numbers cannot be queried on the operator's end because they do not incur charges, failing to meet enterprises' needs for comprehensive call record management. In addition, traditional inquiry methods only support call details from the previous month, unable to query historical records for the current month or more than six months, resulting in poor timeliness.

[0003] Regarding telephone cost accounting, because operator bills typically include bundled fees such as E1 trunk fees, the number charges on the bill often differ from the actual usage by the company. Some numbers have subscribed to value-added services, but the bills are not categorized according to the company's internal accounting rules, requiring secondary processing of the billing data when allocating telephone costs to departments. Furthermore, manual matching of each number with its corresponding department is necessary, resulting in a large computational load, low efficiency, and a high risk of errors.

[0004] For monitoring abnormal outbound calls, the existing model relies on operators to inform enterprises whether there are cases of landline calls being made without their consent. It lacks proactive monitoring capabilities and is often only discovered after a large number of abnormal outbound calls have occurred, which has a significant lag and cannot provide timely warnings of potential risks.

[0005] In summary, existing technologies have significant shortcomings in terms of ease of call record retrieval, accuracy of telephone bill calculation, and proactive monitoring of abnormal calls, and there is an urgent need for a complete solution that can meet the internal management needs of enterprises. Summary of the Invention

[0006] The summary section introduces a series of simplified concepts, which will be further explained in detail in the detailed description section. This summary section is not intended to limit the key and essential technical features of the claimed technical solution, nor is it intended to determine the scope of protection of the claimed technical solution.

[0007] Firstly, this application proposes a method for calculating telephone charges based on call detail records, including: The call detail records (CDRs) generated in real time are obtained from the U1981 / U1980 voice gateway and CDR software, and the CDRs are stored in a specified path on the server. Based on the creation time and filename of the above call detail record (CDR) file, a parsing operation is performed. The target field is read according to the session ID as the primary key. The parsed CDR data is stored in the database, and the original CDR file is packaged and archived. Based on the device addresses in the call detail records (CDRs), the CDRs are categorized and matched with the department information and employee basic number table in the operation and maintenance system database. The matching results are then linked to the company's internal SMS platform. Based on the user-input caller number, called number, hospital district, start time, and end time, the call record query is performed to generate and export the call record of the target number within the above time period. Based on the above caller ID, the above called number, the above affiliated hospital area, the above affiliated department, the above start time and the above end time, outbound call details are statistically analyzed for the corresponding landline call data to obtain the number of outbound calls, outbound call duration, outbound call cost and internal call statistics. Within the specified statistical period, departmental telephone expenses are classified and accounted for according to the company's deduction rules, generating statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, telephone expenses deducted from salary cards, and telephone expenses paid in cash.

[0008] In one feasible implementation, the parsing operation is performed based on the creation time and filename of the call detail record (CDR) file, the target field is read using the session ID as the primary key, the parsed CDR data is stored in the database, and the original CDR file is packaged and archived, including: The target fields in the above call detail record (CDR) file are read sequentially according to the session ID as the primary key. The read field content is then subjected to field format validation, field type normalization, and abnormal data filtering. After reading the target fields mentioned above, the parsed call detail record data is uniquely stored according to the session ID and written to the database. After the call detail record (CDR) data is successfully stored, the original CDR files will be packaged and archived by date or batch classification for easy traceability and unified management.

[0009] In one feasible implementation, the call detail record (CDR) data is categorized based on the device address within it, and then matched against the department information and employee basic phone number table in the operations and maintenance system database. The matching results are then associated with the enterprise's internal SMS platform, including: The device addresses in the above call detail records (CDRs) are identified, and the CDRs are divided into corresponding classification groups according to the same device address. After completing the above classification, the calling and called numbers in each classification group are matched with the department information and employee basic number table in the operation and maintenance system database to generate matching results; After generating the above matching results, the matching results will be associated with the company's internal SMS platform.

[0010] In one feasible implementation, the above-mentioned call record query based on the user-inputted calling number, called number, affiliated hospital area, start time, and end time, generating and exporting the call records of the target number within the aforementioned time period, includes: Based on the above-mentioned caller ID, called ID, hospital district, start time, and end time, the corresponding call records are retrieved from the database, and the retrieved records are sorted by time and categorized by call direction. After completing the call record query, the call records of the target number within the specified time period are generated and exported in a preset format for users to view, save, or perform further statistical analysis.

[0011] In one feasible implementation, based on the caller ID, the called number, the affiliated hospital area, the affiliated department, the start time, and the end time, the above-mentioned landline call data is analyzed to obtain outbound call details, outbound call count, outbound call duration, outbound call cost, and internal call statistics, including: Based on the above-mentioned caller ID, called ID, hospital district, department, start time, and end time, the corresponding landline call data is retrieved, and the call data is categorized according to the outbound call direction and statistically analyzed. Based on the statistical results, the number of outbound calls, outbound call duration, outbound call cost, and internal call statistics were obtained, and the above statistical results were generated.

[0012] In one feasible implementation, the above-mentioned departmental telephone expense classification and accounting is performed according to the enterprise's deduction rules within a specified statistical period, generating statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, telephone expenses deducted from salary cards, and telephone expenses paid in cash, including: Within the specified statistical period, the call charges stored in the database are calculated according to the company’s internal deduction rules, and the calculated call charges are classified into departmental cost call charges, retiree call charges, salary card deduction call charges, and cash payment call charges. After completing the above classification and accounting, statistical reports on the above departmental cost telephone expenses, the above retiree telephone expenses, the above salary card deduction telephone expenses, and the above cash payment telephone expenses are automatically generated based on the categorized cost data.

[0013] In one feasible implementation, the above method further includes: Within the set monitoring period, behavioral baseline models are established based on the aforementioned real-time call detail record (CDR) data and the aforementioned historical CDR data, respectively, and real-time comparisons are made of changes in call volume, frequency fluctuations, and abnormal call duration for each landline number. When abnormal concurrent outbound calls, abnormal outbound call frequency, or abnormal single call length are detected, the system automatically generates an abnormal alarm log consisting of the abnormal level, abnormal source number, trigger rule, abnormal time, and abnormal details. It also sends a notification SMS to the corresponding administrator based on a preset SMS template, which includes an anomaly summary, reference investigation suggestions, and the corresponding phone number, enabling an immediate response to potential unauthorized call risks.

[0014] Secondly, this invention also proposes a call detail record (CDR) query and telephone cost accounting system, comprising: The acquisition unit is used to acquire real-time generated call detail records (CDR) files from the U1981 / U1980 voice gateway and CDR software, and store the CDR files in a specified path on the server. The parsing unit is used to perform parsing operations based on the creation time and filename of the above call detail record (CDR) file, read the target field according to the session ID as the primary key, store the parsed CDR data in the database, and package and archive the original CDR file. The matching unit is used to classify the call detail records (CDRs) based on the device addresses in the CDRs, match them with the department information and employee basic number table in the operation and maintenance system database, and establish a connection between the matching results and the enterprise's internal SMS platform. The query unit is used to perform call record queries based on the caller's number, called number, hospital area, start time, and end time input by the user, and to generate and export the call records of the target number within the above time period. The statistics unit is used to perform outbound call detail statistics on the corresponding landline call data based on the above-mentioned caller number, the above-mentioned called number, the above-mentioned hospital area, the above-mentioned department, the above-mentioned start time and the above-mentioned end time, and to obtain the outbound call count, outbound call duration, outbound call cost and internal call statistics results. The accounting unit is used to classify and calculate departmental telephone expenses according to the company's deduction rules within a specified statistical period, and generate statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, telephone expenses deducted from salary cards, and telephone expenses paid in cash.

[0015] Thirdly, the present invention also proposes an electronic device, comprising: a memory and a processor, characterized in that the processor is used to execute a computer program stored in the memory to implement the steps of the call detail record query telephone cost accounting method as described in any of the first aspects.

[0016] Fourthly, the present invention also proposes a computer-readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the steps of the call detail record query telephone cost accounting method as described in any of the first aspects.

[0017] In summary, this invention directly parses and stores call detail records (CDRs) generated by the voice gateway through the enterprise intranet and web system, allowing users to query real-time call records without visiting a service center. The system supports precise retrieval based on multiple dimensions such as number, department, hospital area, and time period. It can query not only current month's records but also historical data from the past six months or more, comprehensively solving the problems of limited query channels, data lag, and record omissions in existing technologies. This invention automatically matches CDR data with department information and personnel number lists, and categorizes and statistically analyzes various telephone charges based on internal enterprise deduction rules. It can automatically generate departmental cost telephone charges, retired personnel telephone charges, salary card deductions, and cash payments, avoiding the manual matching, data inconsistencies, and low statistical efficiency of traditional methods, significantly improving the accuracy and efficiency of accounting. This invention can uniformly parse and store information from internal short number calls, internal calls, and different voice device sources, solving the problems of unrecorded internal short number calls and incomplete outbound call statistics in existing technologies, enabling enterprises to comprehensively understand various call behaviors. This invention establishes a behavioral baseline model based on real-time and historical call detail records (CDRs), comparing metrics such as call volume, outbound call frequency, and single-call duration in real time. It can automatically identify abnormal concurrent outbound calls, abnormal frequency outbound calls, and excessively long calls. Upon detecting anomalies, the system immediately generates alarm logs and alerts relevant management personnel via SMS, enabling proactive monitoring of call theft risks and completely overcoming the lag issues inherent in traditional methods relying on operator notifications. After parsing, the invention automatically packages and archives the original CDRs, supporting historical data backup and categorized storage to prevent system crashes caused by accumulated original files, ensuring long-term data integrity and system reliability. It provides a unified and visualized query and statistical interface, improving enterprise management efficiency. The system offers exportable tables, statistical reports, and visualizations, clearly displaying various call records, cost statistics, and anomalies, providing high-value data support for enterprise communication management, cost control, and internal auditing.

[0018] Other advantages, objectives and features of this application will be apparent in part from the description which follows, and in part from what those skilled in the art will understand through study and practice of this application. Attached Figure Description

[0019] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit this specification. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A schematic flowchart of a method for calculating telephone charges by querying call detail records is provided in an embodiment of this application. Figure 2 A schematic diagram illustrating the principle of a call detail record (CDR) query method for calculating telephone charges provided in this application embodiment; Figure 3 A schematic diagram of the structure of a call detail record (CDR) query and telephone cost accounting system provided in this application embodiment; Figure 4 This is a schematic diagram of an electronic device structure provided in an embodiment of this application. Detailed Implementation

[0020] The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The technical solutions of the embodiments of this application will now be clearly and completely described in conjunction with the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them.

[0021] Please see Figure 1 and Figure 2 This is a flowchart illustrating a method for calculating telephone charges through call detail record (CDR) inquiries, as provided in an embodiment of this application. Figure 2 A schematic diagram illustrating the principle of a call detail record (CDR) query method for calculating telephone charges provided in this application embodiment; specifically, it may include: S110: Obtain the real-time generated call detail records (CDR) files from the U1981 / U1980 voice gateway and CDR software, and store the CDR files in a specified path on the server. S120. Based on the creation time and filename of the above call detail record (CDR) file, perform a parsing operation, read the target field according to the session ID as the primary key, store the parsed CDR data in the database, and package and archive the above original CDR file. S130. Classify the call detail records (CDRs) based on the device addresses in the CDRs, and match the fields with the department information and employee basic number table in the operation and maintenance system database. Then, associate the matching results with the enterprise's internal SMS platform. S140. Based on the user-inputted calling number, called number, hospital district, start time, and end time, perform a call record query to generate and export the call records of the target number within the above time period. S150. Based on the above-mentioned caller ID, the above-mentioned called number, the above-mentioned hospital area, the above-mentioned department, the above-mentioned start time and the above-mentioned end time, perform outbound call detail statistics on the corresponding landline call data to obtain the outbound call count, outbound call duration, outbound call cost and internal call statistics results. S160. Within the specified statistical period, calculate the departmental telephone expenses according to the company's deduction rules, and generate statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, telephone expenses deducted from salary cards, and telephone expenses paid in cash.

[0022] For example, in this embodiment, a method for call detail record (CDR) query and telephone cost accounting is provided. By parsing, classifying, matching, statistically analyzing and calculating the CDRs generated in real time by the voice gateway, the method enables real-time querying of enterprise landline call records, outbound call behavior statistics, and accurate allocation of departmental telephone costs.

[0023] First, in step S110, this embodiment uses the U1981 / U1980 voice gateway and its accompanying CDR (CallDetailRecord) software to acquire call detail records (CDRs) generated in the enterprise communication system in real time, and stores the acquired CDRs in a designated path on the server to ensure subsequent unified parsing and centralized management. Then, in step S120, the system performs a parsing operation based on the creation time and filename of the CDRs, using the session ID as the unique primary key to read target fields such as the calling number, called number, call start and end time, call duration, and device address, and writes the parsed CDR data into the database. Simultaneously, to avoid the accumulation of original CDRs leading to server performance degradation, the system performs packaged archiving of the original CDRs to achieve standardized storage of existing files.

[0024] Continuing in step S130, the system categorizes call records based on the device address in the call detail records data and performs field matching with the department information and employee basic number table in the operation and maintenance system database to establish the association between call records and departments and personnel. After the matching is completed, the matching results are linked with the enterprise's internal SMS platform so that the corresponding responsible personnel can be automatically found in subsequent abnormal call alarms or call event notifications.

[0025] In step S140, this embodiment provides a call record query function. Users can input conditions such as caller ID, called number, affiliated hospital area, start time and end time. The system filters call records in the database according to these conditions and generates all call details of the target number within the selected time period after the query is completed. It also supports exporting in table or text form for business personnel to retain or further analyze.

[0026] In step S150, the system performs outbound call detail statistics on the call data of the corresponding landline based on the above-mentioned caller number, the above-mentioned called number, the above-mentioned hospital area, the above-mentioned department, and the above-mentioned time conditions. It calculates the number of outbound calls, the total outbound call duration, and the outbound call cost of each landline within the time period, and also counts the internal call situation. This can be used to analyze the outbound call behavior characteristics and call cost consumption of each department or number.

[0027] Finally, in step S160, within the specified statistical time period, the system classifies and calculates call expenses according to the company's internal telephone fee deduction rules, and categorizes the calculation results into departmental cost telephone expenses, retired personnel telephone expenses, salary card deduction telephone expenses, and cash payment telephone expenses, and automatically generates corresponding statistical reports for the finance department to settle, allocate, and audit the telephone expenses of each department or personnel.

[0028] In summary, this invention directly parses and stores call detail records (CDRs) generated by the voice gateway through the enterprise intranet and web system, allowing users to query real-time call records without visiting a service center. The system supports precise retrieval based on multiple dimensions such as number, department, hospital area, and time period. It can query not only current month's records but also historical data from the past six months or more, comprehensively solving the problems of limited query channels, data lag, and record omissions in existing technologies. This invention automatically matches CDR data with department information and personnel number lists, and categorizes and statistically analyzes various telephone charges based on internal enterprise deduction rules. It can automatically generate departmental cost telephone charges, retired personnel telephone charges, salary card deductions, and cash payments, avoiding the manual matching, data inconsistencies, and low statistical efficiency of traditional methods, significantly improving the accuracy and efficiency of accounting. This invention can uniformly parse and store information from internal short number calls, internal calls, and different voice device sources, solving the problems of unrecorded internal short number calls and incomplete outbound call statistics in existing technologies, enabling enterprises to comprehensively understand various call behaviors. This invention establishes a behavioral baseline model based on real-time and historical call detail records (CDRs), comparing metrics such as call volume, outbound call frequency, and single-call duration in real time. It can automatically identify abnormal concurrent outbound calls, abnormal frequency outbound calls, and excessively long calls. Upon detecting anomalies, the system immediately generates alarm logs and alerts relevant management personnel via SMS, enabling proactive monitoring of call theft risks and completely overcoming the lag issues inherent in traditional methods relying on operator notifications. After parsing, the invention automatically packages and archives the original CDRs, supporting historical data backup and categorized storage to prevent system crashes caused by accumulated original files, ensuring long-term data integrity and system reliability. It provides a unified and visualized query and statistical interface, improving enterprise management efficiency. The system offers exportable tables, statistical reports, and visualizations, clearly displaying various call records, cost statistics, and anomalies, providing high-value data support for enterprise communication management, cost control, and internal auditing.

[0029] In one feasible implementation, the parsing operation is performed based on the creation time and filename of the call detail record (CDR) file, the target field is read using the session ID as the primary key, the parsed CDR data is stored in the database, and the original CDR file is packaged and archived, including: The target fields in the above call detail record (CDR) file are read sequentially according to the session ID as the primary key. The read field content is then subjected to field format validation, field type normalization, and abnormal data filtering. After reading the target fields mentioned above, the parsed call detail record data is uniquely stored according to the session ID and written to the database. After the call detail record (CDR) data is successfully stored, the original CDR files will be packaged and archived by date or batch classification for easy traceability and unified management.

[0030] For example, this system automatically parses call detail records (CDRs) generated by the voice gateway and CDR software to ensure accurate data entry and stable subsequent statistical calculations. The system first triggers the parsing process based on the CDR file's creation time and filename, then sequentially reads target fields from the CDR file, including the calling number, called number, device address, call start time, call end time, and call duration, using the session ID as the primary key. During the reading process, the system performs format validation on each field to check for missing, misaligned, illegal characters, or abnormal timestamps. It further standardizes the field types, such as unifying time formats, number encoding methods, and removing redundant spaces, thereby improving the standardization and usability of the CDR data. Simultaneously, the system performs appropriate filtering on any abnormal data identified during the reading process to prevent incomplete or erroneous CDR records from entering the database.

[0031] After reading all the target fields mentioned above, the system uniquely stores the parsed call detail record (CDR) data according to the session ID and writes it into the corresponding table structure in the database to avoid data conflicts or redundant storage caused by duplicate records in different files. This session ID-based uniqueness constraint ensures that each call record in the database maintains a one-to-one correspondence with its original CDR, improving data reliability.

[0032] After the call detail record (CDR) data is successfully written to the database, the system further archives the original CDR files before parsing. Specifically, the system categorizes the original files by date or batch number and archives them using compression to reduce server storage usage. This standardized archiving management of the original CDR files allows for rapid location of the corresponding CDR file when it is necessary to trace the source of records, check the generation of CDRs, or perform auditing operations, while maintaining the structure and manageability of the overall file system.

[0033] In summary, this embodiment achieves accurate extraction, standardized storage, and efficient traceability of call detail record (CDR) data by parsing, validating, standardizing, and uniquely storing each field of the CDR file, combined with the original file's archiving management mechanism. This improves the stability and reliability of the entire CDR processing flow.

[0034] In one feasible implementation, the call detail record (CDR) data is categorized based on the device address within it, and then matched against the department information and employee basic phone number table in the operations and maintenance system database. The matching results are then associated with the enterprise's internal SMS platform, including: The device addresses in the above call detail records (CDRs) are identified, and the CDRs are divided into corresponding classification groups according to the same device address. After completing the above classification, the calling and called numbers in each classification group are matched with the department information and employee basic number table in the operation and maintenance system database to generate matching results; After generating the above matching results, the matching results will be associated with the company's internal SMS platform.

[0035] For example, the system performs device address classification and field matching on the parsed call detail record (CDR) data to automatically associate CDR records with internal department and personnel information, supporting subsequent statistical analysis and anomaly alerts. In this implementation, the system first identifies the device addresses in the CDR data. By comparing the device address field with a pre-set device address mapping table in the system, CDR records with the same device address are grouped into the same category group to distinguish data sources from different voice gateways or physical lines. This device address-based classification method ensures that subsequent number matching and department association are completed within the same data source range, reducing the risk of cross-matching errors.

[0036] After completing the above classification, the system further performs field matching on the calling and called numbers in each category group. This field matching process is based on the department information table and employee basic number table in the operation and maintenance system database. By comparing the number field, department code field, and personnel correspondence field one by one, the system establishes a mapping relationship between call detail records and their respective departments and personnel. Through this mapping relationship, the system can accurately determine the responsible department or personnel for each call record, thus providing complete data support for telephone billing, outbound call statistics, and data traceability.

[0037] After generating the matching results, the system also links these results to the company's internal SMS platform. This allows the system to automatically select the appropriate SMS recipient and send alerts based on the matched department head information and number binding relationships in the event of abnormal outbound calls, abnormal concurrency, or prolonged calls. Through this linkage mechanism, the system can notify the responsible department or personnel immediately upon the occurrence of abnormal call behavior, enabling timely feedback and rapid investigation, effectively reducing the risk of unauthorized or misused call resources.

[0038] In summary, this embodiment achieves a systematic mapping of call detail record (CDR) data across source, department, and personnel levels through four steps: device address identification, call detail record (CDR) classification, number field matching, and SMS platform association. This makes the entire CDR management process clearer and more efficient, and provides a stable data foundation for subsequent statistical analysis and security alerts.

[0039] In one feasible implementation, the above-mentioned call record query based on the user-inputted calling number, called number, affiliated hospital area, start time, and end time, generating and exporting the call records of the target number within the aforementioned time period, includes: Based on the above-mentioned caller ID, called ID, hospital district, start time, and end time, the corresponding call records are retrieved from the database, and the retrieved records are sorted by time and categorized by call direction. After completing the call record query, the call records of the target number within the specified time period are generated and exported in a preset format for users to view, save, or perform further statistical analysis.

[0040] For example, the system provides a call record query capability based on multi-condition filtering to meet the enterprise's need for precise retrieval of call behavior at different time periods, departments, or numbers. In this implementation, the user can input query conditions such as the caller's number, the called number, the affiliated hospital area, the start time, and the end time. The system then searches the call records stored in the database based on these conditions and filters out all records that match the conditions.

[0041] After completing the above search, the system sorts the retrieved records according to the call start time to present the chronological order of the calls. Simultaneously, the system categorizes the records based on the call direction field, organizing outgoing and incoming calls separately, allowing users to intuitively view the call activity of a number under different call directions. Through these sorting and categorization operations, the system can display the query results in a clear structure, enabling users to quickly understand the call activity of a specified number within the given time period.

[0042] After the call records are processed, the system generates complete call record data for the target number within the specified time period, including fields such as call time, caller ID, called ID, call direction, call duration, and device origin. To facilitate subsequent processing, the system exports the generated call records in a preset format, which can be a table file, text file, or print format. Users can view, save, archive, or use these records for further statistical analysis as needed. This implementation allows enterprise users to quickly obtain complete and accurate call records without accessing the operator's system, improving the efficiency of internal data verification and communication analysis.

[0043] In one feasible implementation, based on the caller ID, the called number, the affiliated hospital area, the affiliated department, the start time, and the end time, the above-mentioned landline call data is analyzed to obtain outbound call details, outbound call count, outbound call duration, outbound call cost, and internal call statistics, including: Based on the above-mentioned caller ID, called ID, hospital district, department, start time, and end time, the corresponding landline call data is retrieved, and the call data is categorized according to the outbound call direction and statistically analyzed. Based on the statistical results, the number of outbound calls, outbound call duration, outbound call cost, and internal call statistics were obtained, and the above statistical results were generated.

[0044] For example, the system performs outbound call detail statistics on the call data of the corresponding landline based on the caller ID, called ID, hospital district, department, start time, and end time input by the user, in order to achieve accurate analysis of outbound call behavior for different departments and different numbers. In specific implementation, the system first retrieves landline call data that meets the filtering conditions from the database based on the above-mentioned caller ID, called ID, hospital district, department, and time conditions, ensuring that the obtained records are all valid calls generated by the target number within the selected time period.

[0045] After retrieving the call data, the system categorizes the data based on the call direction field, distinguishing between outbound and internal call records. It then performs statistical analysis on the outbound call records, calculating the number of outbound calls made to the corresponding number or department within the specified time interval, the cumulative outbound call duration, and the corresponding outbound call costs. Simultaneously, for calls between internal short numbers or extensions, the system calculates the number of occurrences and call duration based on internal call rules, thus generating complete internal call statistics.

[0046] After obtaining the above statistical results, the system summarizes the outbound call count, outbound call duration, outbound call cost, and internal call statistics, and generates structured statistical data for further display, export, or inclusion in the departmental telephone expense calculation process. Through the statistical method of this embodiment, enterprises can comprehensively grasp the outbound call behavior characteristics and call cost of different departments or numbers within the stated time period, providing accurate basis for internal management, budget control, and call cost allocation.

[0047] In one feasible implementation, the above-mentioned departmental telephone expense classification and accounting is performed according to the enterprise's deduction rules within a specified statistical period, generating statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, telephone expenses deducted from salary cards, and telephone expenses paid in cash, including: Within the specified statistical period, the call charges stored in the database are calculated according to the company’s internal deduction rules, and the calculated call charges are classified into departmental cost call charges, retiree call charges, salary card deduction call charges, and cash payment call charges. After completing the above classification and accounting, statistical reports on the above departmental cost telephone expenses, the above retiree telephone expenses, the above salary card deduction telephone expenses, and the above cash payment telephone expenses are automatically generated based on the categorized cost data.

[0048] For example, the system can classify and calculate call charges according to the company's internal deduction rules within a specified statistical period, and automatically generate different categories of telephone charge statistical reports. Specifically, when the user selects a target statistical period, the system retrieves all call charge data for that period from the database and performs calculation processing on each call charge record according to the company's telephone charge deduction rules. The deduction rules typically include departmental allocation rules, telephone charge reduction rules for retired employees, salary card deduction rules, and cash payment rules. The system automatically classifies call charges according to these rules, categorizing the calculated charges into four types: departmental cost telephone charges, retired employee telephone charges, salary card deduction telephone charges, and cash payment telephone charges.

[0049] After completing the above classification and accounting, the system automatically generates statistical reports for various types of telephone expenses based on the categorized cost data. These reports include the total amount for each type of expense, corresponding number details, departmental information, and the basis for calculating each expense, facilitating expense review, reimbursement processing, budget preparation, and internal auditing by the company's finance department. Through this automated accounting process, this embodiment significantly reduces manual statistical costs, improves the accuracy and timeliness of expense accounting, and ensures efficient, transparent, and traceable telephone expense management.

[0050] In one feasible implementation, the above method further includes: Within the set monitoring period, behavioral baseline models are established based on the aforementioned real-time call detail record (CDR) data and the aforementioned historical CDR data, respectively, and real-time comparisons are made of changes in call volume, frequency fluctuations, and abnormal call duration for each landline number. When abnormal concurrent outbound calls, abnormal outbound call frequency, or abnormal single call length are detected, the system automatically generates an abnormal alarm log consisting of the abnormal level, abnormal source number, trigger rule, abnormal time, and abnormal details. It also sends a notification SMS to the corresponding administrator based on a preset SMS template, which includes an anomaly summary, reference investigation suggestions, and the corresponding phone number, enabling an immediate response to potential unauthorized call risks.

[0051] For example, within a set monitoring period, the system first constructs a behavioral baseline model based on the aforementioned real-time call detail record (CDR) data and the aforementioned historical CDR data. By statistically learning the changes in call volume, outbound call frequency fluctuations, and single call duration distribution for each landline number, it forms a normal call behavior pattern for the corresponding number. Subsequently, during operation, the system compares newly generated real-time CDR data with the aforementioned behavioral baseline model in real time to identify whether there are behaviors that significantly deviate from the normal call pattern, including abnormal concurrent outbound calls, abnormally high-frequency outbound calls within a short period of time, and abnormal single outbound call duration exceeding the limit.

[0052] Upon detecting any of the above-mentioned abnormal behaviors, the system immediately generates an anomaly alarm log. This log includes the anomaly level, source number, triggering rule, occurrence time, details, and relevant comparison parameters, facilitating subsequent auditing and risk tracking. Simultaneously, to enable timely intervention and risk control, the system sends a notification SMS to the corresponding administrator based on a preset template. This SMS includes an anomaly summary, suggested troubleshooting steps, and relevant phone number information, allowing administrators to understand the risk situation immediately and take necessary action. Through this anomaly monitoring and alarm mechanism, this embodiment effectively enhances the security of the enterprise's voice communication system, reducing the possibility of abnormal use of call resources or unauthorized calls.

[0053] In one feasible implementation, the above method further includes a call detail record (CDR) statistical analysis module, used to perform multi-dimensional statistical analysis and visualization based on all CDR data stored in the database, to assist managers in macro-analysis and trend judgment of call behavior and cost structure. Specifically, the system first uses all CDR data stored in the database as the main line of analysis, automatically matches the corresponding department information and personnel names, and aggregates and analyzes outbound call data according to a preset statistical period. In one embodiment, the system statistically analyzes the outbound call data of the target number or target department on a daily basis within a statistical period of nearly 30 days, calculates the total number of outbound calls, the total duration of outbound calls, and the total cost of outbound calls each day, and generates a daily outbound call analysis chart based on the statistical results, where the total number of outbound calls is displayed in a line form, and the total duration of outbound calls and the total cost of outbound calls are displayed in a bar form, to intuitively reflect the fluctuation trend of outbound call behavior in the short term. In another embodiment, the system summarizes the outbound call data of the target number or target department on a monthly basis within a statistical period of nearly one year, calculates the total number of outbound calls, total outbound call duration and total outbound call cost for each month, and generates a monthly outbound call analysis chart to display the long-term outbound call trend in a combination of line and bar charts, providing data support for departmental call usage behavior assessment and annual cost budget.

[0054] Furthermore, based on the mapping relationship between caller ID numbers and hospital district information, the system performs statistical analysis of outbound call data at the hospital district level. In practice, within a monthly or annual statistical period, the system calculates the total number of outbound calls, total call duration, and total call cost for each hospital district, displaying the proportion of each district among all hospitals in a pie chart, thus intuitively reflecting the structural distribution of communication resource consumption across different hospitals. Simultaneously, the system supports monthly year-on-year analysis of outbound call data for each hospital district. By comparing the total number of outbound calls, total call duration, and total call cost in the current statistical period with historical data from the same period, it generates monthly year-on-year line charts or bar charts at the hospital district level, displaying the growth or decline trends of outbound call behavior in each hospital district. Through the aforementioned call detail record (CDR) statistical analysis module, the system can transform previously scattered call records into statistically valuable results and trend graphs, enabling managers to comprehensively grasp the characteristics of outbound call behavior and cost changes from multiple levels, including numbers, departments, and hospital districts. This provides intuitive and reliable data support for communication resource management, cost optimization, and anomaly risk assessment.

[0055] Secondly, this invention also proposes a call detail record (CDR) query and telephone cost accounting system, such as... Figure 3 As shown, it includes: The acquisition unit 21 is used to acquire the real-time generated call detail records (CDR) files from the U1981 / U1980 voice gateway and CDR software, and store the CDR files in a specified path on the server. Parsing unit 22 is used to perform parsing operations based on the creation time and file name of the above call detail record (CDR) file, read the target field according to the session ID as the primary key, store the parsed CDR data in the database, and package and archive the above original CDR file. Matching unit 23 is used to classify the call detail record (CDR) data according to the device address in the CDR data, and to perform field matching with the department information and employee basic number table in the operation and maintenance system database, and to establish an association between the matching result and the enterprise's internal SMS platform. Query unit 24 is used to perform call record queries based on the caller's number, called number, hospital district, start time and end time input by the user, and generate and export the call records of the target number within the above time period; The statistics unit 25 is used to perform outbound call detail statistics on the corresponding landline call data based on the above-mentioned caller number, the above-mentioned called number, the above-mentioned hospital area, the above-mentioned department, the above-mentioned start time and the above-mentioned end time, and to obtain the outbound call count, outbound call duration, outbound call cost and internal call statistics results. Accounting unit 26 is used to perform departmental telephone expense classification accounting according to the company's deduction rules within a specified statistical period, and generate statistical reports on departmental cost telephone expenses, retired personnel telephone expenses, salary card deduction telephone expenses, and cash payment telephone expenses.

[0056] In one feasible implementation, a call detail record (CDR) query telephone cost accounting system can also perform any step of the method proposed in the first aspect.

[0057] Thirdly, the present invention also proposes an electronic device 300, such as... Figure 4 As shown, it includes a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, it implements the steps of the call detail record query telephone cost accounting method as described in any of the first aspects.

[0058] Fourthly, the present invention also proposes a computer-readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the steps of the call detail record query telephone cost accounting method as described in any of the first aspects.

[0059] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0060] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can 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, etc.) containing computer-usable program code.

[0061] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, 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 a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0062] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0063] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0064] This application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device performs the voice-based identity recognition process in the corresponding embodiment. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0065] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0066] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0067] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0068] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0069] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0070] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for accounting telephone bill query telephone cost, characterized in that, The method comprises the following steps: obtaining a real-time generated bill file from a U1981 / U1980 voice gateway and CDR software, and storing the bill file in a specified path of a server; performing a parsing operation based on the establishment time and file name of the bill file, reading target fields according to a session ID as a primary key, storing bill data obtained after parsing in a database, and archiving the original bill file; classifying the bill data according to device addresses in the bill data, and performing field matching with department information and a staff basic number table in an operation and maintenance system database, establishing an association between the matching result and an enterprise internal short message platform; performing a call record query based on a user inputted calling number, called number, affiliated hospital, start time and end time, and generating and exporting a call record of a target number within the time period; performing an outbound call detail statistics on corresponding fixed telephone call data based on the calling number, called number, affiliated hospital, affiliated department, start time and end time, to obtain outbound call times, outbound call duration, outbound call cost and internal call statistics results; performing department telephone cost classification accounting according to enterprise deduction rules within a specified statistical time period, to generate statistical reports of department cost telephone cost, retired personnel telephone cost, salary card deduction telephone cost and cash payment telephone cost.

2. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. The parsing operation based on the establishment time and file name of the bill file, reading target fields according to a session ID as a primary key, storing bill data obtained after parsing in a database, and archiving the original bill file comprises the following steps: reading target fields according to a session ID as a primary key in sequence for the bill file, performing field format verification, field type standardization and abnormal data filtering processing on the read field contents; after completing the reading of the target fields, uniquely storing and writing the bill data obtained after parsing into a database according to the session ID; and after successfully storing the bill data, packing and archiving the original bill file in a date classification or batch classification manner, to facilitate subsequent tracing and unified management.

3. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. The classification of the bill data according to device addresses in the bill data, and the field matching with department information and a staff basic number table in an operation and maintenance system database, and the establishment of an association between the matching result and an enterprise internal short message platform comprises the following steps: identifying the device addresses in the bill data, and dividing the bill data into corresponding classification groups according to the same device addresses; after completing the classification, performing field matching of calling numbers and called numbers in each classification group with department information and a staff basic number table in an operation and maintenance system database, to generate matching results; and after generating the matching results, establishing an association between the matching results and an enterprise internal short message platform.

4. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. The call record query based on a user inputted calling number, called number, affiliated hospital, start time and end time, and the generation and export of a call record of a target number within the time period comprises the following steps: According to the calling number, the called number, the affiliated hospital, the start time and the end time, the corresponding call record is retrieved from the database, and the retrieved record is sorted by time and classified by call direction; After the call record query is completed, the call record of the target number in the time period is generated, and the call record is exported in a preset format for the user to view, retain or further statistical analysis.

5. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. According to the calling number, the called number, the affiliated hospital, the start time and the end time, the corresponding call record is retrieved from the database, and the retrieved record is sorted by time and classified by call direction; According to the calling number, the called number, the affiliated hospital, the start time and the end time, the corresponding call record is retrieved from the database, and the retrieved record is sorted by time and classified by call direction; Based on the statistical results, the number of external calls, the external call duration, the external call cost and the internal call statistical results are obtained, and the statistical results are generated.

6. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. In the specified statistical time period, the department telephone fee classification accounting is performed according to the enterprise deduction rules, and the statistical report of department cost telephone fee, retired personnel telephone fee, salary card deduction telephone fee and cash payment telephone fee is generated, including: In the specified statistical time period, the call fee data stored in the database is calculated according to the deduction rules formulated by the enterprise, and the calculated call fee is classified as department cost telephone fee, retired personnel telephone fee, salary card deduction telephone fee and cash payment telephone fee; After the classification accounting is completed, the statistical report of the department cost telephone fee, the retired personnel telephone fee, the salary card deduction telephone fee and the cash payment telephone fee is automatically generated based on the classified fee data.

7. The method of claim 1, wherein the telephone cost accounting method is a call query telephone cost accounting method. The method further comprises: In the set monitoring period, the behavior baseline model is established based on real-time call data and historical call data, and the call volume change, frequency fluctuation and call duration anomaly of each extension number are compared in real time; When detecting abnormal outgoing calls, abnormal outgoing call frequency or abnormal single call duration, the system automatically generates an abnormal alarm log composed of abnormal level, abnormal source number, trigger rule, abnormal time and abnormal details; And based on the preset SMS template, a prompt SMS containing abnormal summary, reference investigation suggestion and corresponding number is sent to the corresponding management personnel, realizing the instant response to the potential risk of illegal calls.

8. A telephone bill query telephone cost accounting system, characterized by comprising: Comprise: The acquisition unit is used for acquiring real-time call file from U1981 / U1980 voice gateway and CDR software, and storing the call file in the specified path of the server; The analysis unit is used for performing analysis operation based on the establishment time and file name of the call file, reading target field according to session ID as primary key, storing the call data obtained after analysis in the database, and packaging and archiving the original call file; The matching unit is used for classifying the phone bill data according to the device address in the phone bill data, and performing field matching with the department information and the staff basic number table in the operation and maintenance system database, and establishing association between the matching result and the enterprise internal short message platform; The query unit is used for executing call record query based on the calling number, the called number, the affiliated hospital, the start time and the end time input by the user, and generating and exporting the call record of the target number in the time period; The statistical unit is used for executing outbound call detail statistics on the corresponding fixed telephone call data based on the calling number, the called number, the affiliated hospital, the affiliated department, the start time and the end time, and obtaining outbound call times, outbound call duration, outbound call cost and extension call statistics results; The accounting unit is used for performing department telephone cost classification accounting according to the enterprise deduction rules in a specified statistical time period, and generating statistical reports of department cost telephone cost, retired staff telephone cost, salary card deduction telephone cost and cash payment telephone cost.

9. An electronic device comprising: The memory and the processor are characterized in that the processor is used for implementing the steps of the phone bill query telephone cost accounting method in any one of claims 1-7 when executing the computer program stored in the memory.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is used for implementing the steps of the phone bill query telephone cost accounting method in any one of claims 1-7 when executed by the processor.

Images