Call information processing device, call information processing program, call information processing method, and call information processing system

Abstract

To prevent a transmission disabled state while dealing with a redundant configuration when call information is transmitted in a telephone communication system.SOLUTION: Call information in a first format contained in a first call information file containing the call information in the first format supplied from a first external device is converted into call information in a second format, a second call information file containing the call information in the second format is generated, the generated second call information file is transmitted to a second external device, it is checked whether a file with the same name as the generated file exists in the second external device, the second call information file generated is stored by file generating means, a character string that includes order information indicating the order to the file name of the second call information file and is unique at least among the files stored in the storage means is added, and those of the generated second call information files for which it has been confirmed that no file with the same name exists in the second external device are transmitted to the second external device.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a call information processing apparatus, a call information processing program, a call information processing method, and a call information processing system, and can be applied to, for example, the processing of call history information necessary for the charging service of a telephone communication service.

Background Art

[0002] Conventionally, in a telephone communication system that provides a telephone communication service by a communication carrier or the like, a CDR (Call Detail Record) in which information regarding the call history related to the call (hereinafter also referred to as "call information" or "call detailed information") is set for each call (call) is issued by a call control device. And, in the conventional telephone communication system, generally, a system (hereinafter referred to as "CDR conversion system") that converts the CDR issued by the call control device into a format that can be processed by a system in charge of the charging service (hereinafter referred to as "charging service system") is provided.

[0003] In the conventional CDR conversion system, depending on the operation policy of the telephone communication service provider, it may be operated in a so-called active / active redundant configuration (a configuration in which all redundant systems are in an active state), and the same CDR is converted in each system and the converted data is supplied to the charging service system. In the CDR conversion device of each system constituting the CDR conversion system with such an active / active configuration, as long as the supplied CDRs have the same content, data with the same file name is supplied to the charging service system.

[0004] Further, conventionally, as a telephone communication system in which the transmission path of the CDR is redundant in a plurality of systems of nodes, for example, there is a system of Patent Document 1. The system described in Patent Document 1 has a configuration for removing duplicate records of CDRs generated by switching between nodes due to a failure in a plurality of nodes with a redundant configuration.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Japanese Patent Publication No. 2022-117851 [Overview of the project] [Problems that the invention aims to solve]

[0006] However, in conventional telephone communication systems, if the CDR converter's upstream side (call control device side) retransmits the same CDR as a normal process (for example, retrying a transaction with the same content), and the billing system side generates CDR data with duplicate filenames, transmission will fail.

[0007] In light of the above-mentioned problems, there is a need for a call information processing device, a call information processing program, a call information processing method, and a call information processing system that can prevent transmission failures while supporting redundant configurations when transmitting call information (e.g., CDR) in a telephone communication system. [Means for solving the problem]

[0008] The first call information processing device of the present invention comprises: conversion means for converting call information in a first format contained in a first call information file containing call information in a first format supplied from a first external device into call information in a second format; file generation means for generating a second call information file containing the second format of call information converted by the conversion means; transmission means for transmitting the second call information file generated by the file generation means to a second external device; file confirmation means for checking whether a file with the same name as the file name of the second call information file generated by the file generation means exists in the second external device; and storage means for storing the second call information file generated by the file generation means, wherein the file generation means assigns a string to the file name of the second call information file that includes sequence information indicating the order of generation and is unique among those stored in the storage means; and the transmission means transmits to the second external device any second call information files generated by the file generation means that the file confirmation means has confirmed that no file with the same name exists in the second external device.

[0009] The second call information processing program of the present invention is characterized in that a computer is configured to function as: conversion means for converting call information in a first format contained in a first call information file containing call information in a first format supplied from a first external device into call information in a second format; file generation means for generating a second call information file containing the second format of call information converted by the conversion means; transmission means for transmitting the second call information file generated by the file generation means to a second external device; file verification means for checking whether a file with the same name as the file name of the second call information file generated by the file generation means exists in the second external device; and storage means for storing the second call information file generated by the file generation means, wherein the file generation means assigns a string to the file name of the second call information file that includes sequence information indicating the order of generation and is unique among those stored in the storage means; and the transmission means transmits to the second external device any second call information files generated by the file generation means that the file verification means has confirmed that no file with the same name exists in the second external device.

[0010] The third aspect of the present invention relates to a call information processing method performed by a call information processing device, comprising a conversion means, a file generation means, a transmission means, a file verification means, and a storage means, wherein the conversion means converts the call information in a first format contained in a first call information file containing the call information in a first format supplied from a first external device into a second format; the file generation means generates a second call information file containing the call information in a second format converted by the conversion means; the transmission means transmits the second call information file generated by the file generation means to a second external device; and the file verification means confirms that the file generation means is in the second external device. The storage means checks whether a file with the same name as the generated second call information file exists, stores the second call information file generated by the file generation means, the file generation means assigns a string to the file name of the second call information file that includes sequence information indicating the order in which they were generated and is unique among those stored in the storage means, and the transmission means transmits to the second external device any second call information files generated by the file generation means that the file verification means has confirmed that no file with the same name exists in the second external device.

[0011] The fourth aspect of the present invention is a call information processing system comprising a plurality of call information processing devices, characterized in that the first call information processing device of the present invention is applied as the call information processing device. [Effects of the Invention]

[0012] According to the present invention, when transmitting call information in a telephone communication system, it is possible to prevent a transmission failure state while supporting a redundant configuration. [Brief explanation of the drawing]

[0013] [Figure 1] This diagram shows the configuration of a telephone communication system equipped with a CDR conversion system according to an embodiment. [Figure 2]This figure illustrates the rules for generating the filename of the pre-conversion CDR data file according to the embodiment. [Figure 3] This figure illustrates the rules for generating filenames for converted CDR data files according to the embodiment. [Figure 4] This is a flowchart illustrating the operation of the CDR conversion device according to the embodiment. [Figure 5] This is a sequence diagram illustrating the operation of the CDR conversion system according to the embodiment. [Modes for carrying out the invention]

[0014] (A) Main embodiment Hereinafter, an embodiment of the call information processing device, call information processing program, call information processing method, and call information processing system according to the present invention will be described in detail with reference to the drawings. In this embodiment, an example in which the call information processing device, call information processing program, and call information processing method of the present invention are applied to a CDR conversion device will be described. Furthermore, in this embodiment, an example in which the call information conversion system of the present invention is applied to a CDR conversion system will be described.

[0015] (A-1) Configuration of the embodiment Figure 1 is a diagram showing the configuration of a telephone communication system 1 equipped with a CDR conversion system 10 according to the first embodiment.

[0016] The telephone communication system 1 is a system on the communication carrier side that provides telephone communication services to subscriber terminals UT (for example, terminals equipped with IP telephone communication functionality) on the network N. In this embodiment, the specific configuration of the network N is not limited. Also, in this embodiment, the specific configuration and number of subscriber terminals UT are not limited.

[0017] The telephone communication system 1 shown in FIG. 1 includes a SIP server 20 that corresponds to SIP (Session Initiation Protocol) as a call control signal. Further, the telephone communication system 1 shown in FIG. 1 includes a charging service system 30 as a system for performing charging management (for example, management of charges associated with telephone communication use) for subscribers (users of the subscriber terminal UT).

[0018] The specific configurations of the SIP server 20 and the charging service system 30 are not limited, and devices with similar functions in various telephone communication systems can be applied.

[0019] In the telephone communication system 1, the CDR data issued by the SIP server 20 is supplied to the CDR conversion system 10, converted into a predetermined format that can be processed by the charging service system 30, and a file (hereinafter referred to as the "converted CDR data file") in which the converted CDR data (hereinafter referred to as the "converted CDR data") is stored is transmitted (supplied) to the charging service system 30. The charging service system 30 is provided with a receiving directory 310 as a storage area (storage means) for accumulating and managing the supplied converted CDR data file. The receiving directory 310 is a means capable of storing data in a file format, and the format of directories / folders in various storage systems and operating systems can be applied.

[0020] The CDR conversion system 10 has a redundant configuration by including a plurality of CDR conversion devices 100 that convert CDR data supplied from the SIP server 20 and supply it to the charging service system 30. The CDR conversion devices 100 that make up the CDR conversion system 10 have a redundant configuration where all are active during normal times. The number of CDR conversion devices 100 included in the CDR conversion system 10 is not limited, but in this embodiment, it is assumed to include two CDR conversion devices 100 (100-0 and 100-1), namely the 0th system and the 1st system. That is, in this embodiment, the CDR conversion system 10 has an active / active (ACT / ACT) redundant configuration. Hereinafter, the CDR conversion device 100-0 will be referred to as the "0th system", and the CDR conversion device 100-1 will be referred to as the "1st system".

[0021] As shown in FIG. 1, the 0th system CDR conversion device 100-0 and the 1st system CDR conversion device 100-1 have the same configuration, and each is assumed to have a receiving unit 110, a conversion unit 120, a transmitting unit 130, and a backup unit 140.

[0022] Each CDR conversion device 100 may be configured hardware-wise (for example, by a dedicated chip), or may be configured partially or entirely software-wise. Each CDR conversion device 100 may be configured, for example, by installing a program (a voice processing program according to the embodiment) on a computer including a processor and a memory (for example, a primary memory and a secondary memory). Also, each CDR conversion device 100 may be configured using a hardware-wise separate housing device, or may be configured as a device composed of modules / blades separated within one housing. Furthermore, each CDR conversion device 100 may be configured as an independent device, or may be configured within the same device (computer) as an application with another function.

[0023] The receiving unit 110 is responsible for the function of receiving a file (hereinafter referred to as the "pre-conversion CDR data file") in which CDR data is stored from the SIP server 20.

[0024] The conversion unit 120 is responsible for converting the CDR data of the pre-conversion CDR data file received by the receiving unit 110 into a format that can be processed by the billing system 30, and obtaining the converted CDR data.

[0025] The transmission unit 130 is responsible for storing the converted CDR data converted by the conversion unit 120 into a file to generate a converted CDR data file, and then transmitting it to the billing system 30.

[0026] In this embodiment, the specific specifications of the CDR data files (pre-conversion CDR data file and converted CDR data file) processed by the CDR converter 100 are not limited, and various specifications can be applied. For example, a predetermined CSV (Comma Separated Values) format file may be used as the CDR data file (pre-conversion CDR data file and converted CDR data file) processed by the CDR converter 100. Furthermore, the conversion content by the conversion unit 120 is not limited, and various processing can be applied. For example, the conversion unit 120 may generate the converted CDR data file by deleting some items in the pre-conversion CDR data file.

[0027] The backup unit 140 is responsible for the backup function of accumulating and saving converted CDR data files that have been transmitted or canceled by the transmission unit 130.

[0028] Next, the file name format of the CDR data files before and after conversion, which are processed by the telephone communication system 1, will be explained using Figures 2 and 3.

[0029] Figure 2 shows the rules for generating the filenames of the CDR data files before conversion.

[0030] Figure 2(a) shows the format and specific examples of the filename of the pre-conversion CDR data file. Figure 2(b) shows the format of each element of the filename of the pre-conversion CDR data file.

[0031] As shown in Figure 2, the filename of the pre-conversion CDR data file is in the format of concatenating the two elements, [file identifier] and [date and time], with an underscore (_) in between. Note that the filename of the pre-conversion CDR data file shown in Figure 2 does not include an extension, but it may be added separately.

[0032] As shown in Figure 2, the file identifier field consists of any string (a string of any length composed of any combination of characters). The file identifier can be any characters that are applicable as filenames (for example, characters that are permitted to be used as filenames on the OS).

[0033] Furthermore, as shown in Figure 2, the date and time field is assumed to consist of a string in the YYYYMMDDhhmmss format (YYYY: year, MM: month, DD: day, hh: hour, mm: minute, ss: second) (a 14-character string). Note that the date and time field may be displayed in other data formats. For example, the date and time may be displayed up to the minute (mm) (YYYYMMDDhhmm), or the time may be extended to include seconds.

[0034] As shown in Figure 2, the filename of the pre-conversion CDR data file will be a string such as "xxx_20221024173500". In "xxx_20221024173500", "xxx" corresponds to the file identifier and "20221024173500" corresponds to the date and time.

[0035] Figure 3 shows the rules for generating filenames for converted CDR data files.

[0036] Figure 3(a) shows the format and specific examples of the filename of a converted CDR data file. Figure 3(b) shows the format of each element of the filename of a converted CDR data file.

[0037] As shown in Figure 3, the filename of the converted CDR data file is in the format of concatenating the strings of three elements: [file identifier], [date and time], and [transfer number], separated by an underscore "_". Although the filename of the converted CDR data file shown in Figure 3 does not include an extension, it may be added separately. In other words, in this embodiment, the filename of the converted CDR data file is in the format of the filename of the pre-conversion CDR data file with the transfer number element added. As shown in Figure 3, the format of the transfer number is a sequence number consisting of two digits. The transfer number is a number that is incremented each time a converted CDR data file based on a pre-conversion CDR data file with the same name is generated within each CDR conversion device 100.

[0038] In other words, in the CDR conversion system 10 (each CDR conversion device 100), if multiple pre-conversion CDR data files with the same file name are supplied from the SIP server 20, an incremented transfer number (sequence number) will be applied to the file name assigned to the converted CDR data file each time a file is supplied. For example, in the CDR conversion system 10 (each CDR conversion device 100), if a pre-conversion CDR data file with the file name "xxx_20221024173500" is supplied for the first time, the corresponding converted CDR data file will be assigned the transfer number "01" and become "xxx_20221024173500_01". The next time a pre-conversion CDR data file with the same file name is supplied, the corresponding converted CDR data file will be assigned the transfer number "02" and become "xxx_20221024173500_02".

[0039] Next, the internal configuration of the transmitting unit 130 will be described.

[0040] As shown in Figure 1, the transmission unit 130 includes an existence check processing unit 131 and a transmission processing unit 132.

[0041] The transmission processing unit 132 acquires the converted CDR data converted by the conversion unit 120, stores it in a file with a predetermined filename (for example, the filename shown in Figure 3), creates a converted CDR data file, and then transmits the converted CDR data file to the billing system 30. The transmission processing unit 132 also supplies the generated converted CDR data file to the backup unit 140 for storage.

[0042] The existence check processing unit 131, in response to a request from the transmission processing unit 132, performs an existence check (hereinafter referred to as the "existence check process") to determine whether a file with the same filename as the specified converted CDR data file already exists.

[0043] Based on the results of the existence check processing by the existence check processing unit 131, the transmission processing unit 132 determines the transfer number to be applied to the file name of the converted CDR data file and determines whether or not the final converted CDR data file needs to be transmitted.

[0044] When the transmission processing unit 132 obtains the pre-conversion CDR data file, it generates a filename for the converted CDR data file based on the filename of the pre-conversion CDR data file, and increments the transfer number based on the determination result of the existence check processing unit 131 until there is no longer a file with the same name in the backup unit 140 of the same system (within the same device; local). In other words, the transmission processing unit 132 repeats the process of incrementing the transfer number to be set as the filename of the converted CDR data file until a unique filename is obtained, at least within the backup unit 140 of the same system.

[0045] In the following, in each CDR conversion device 100, a file name that is unique within at least the backup unit 140 of the same system (the file name of the converted CDR data file) will be referred to as the "local unique file name." Furthermore, in the following, a file name that is unique within the billing system 30 (receiving directory 310) (the file name of the converted CDR data file) will be referred to as the "system unique file name."

[0046] Then, when the transmission processing unit 132 obtains a file name that will be a local unique file name, it determines whether or not a file with the same name as that file name exists in the billing system 30 (receiving directory 310) (i.e., whether or not that file name is a system unique file name). Only if the determination result is that it does not exist (i.e., that the file name is a system unique file name), it sends the converted CDR data file with that file name set to the billing system 30 (receiving directory 310).

[0047] As described above, the transmission unit 130 (transmission processing unit 132) increments the transfer number of the converted CDR data file until a local unique file name is obtained. Only if the obtained local unique file name is a system unique file name, the unit sends the converted CDR data file with that file name set to the billing system 30 (receiving directory 310). Otherwise, the transmission of the converted CDR data file is canceled.

[0048] The transmission processing unit 132 causes the converted CDR data file that has been transmitted or canceled to be recorded in the backup unit 140.

[0049] (A-2) Operation of the embodiment Next, the operation of the CDR conversion system 10 of this embodiment (call information conversion method according to the embodiment) will be described.

[0050] Figure 4 is a flowchart showing an example of the processing of the transmission unit 130 that constitutes each CDR conversion device 100.

[0051] The flowchart in Figure 4 shows a common process for each CDR conversion device 100 (100-1, 100-2).

[0052] First, assume that the converted CDR data converted by the conversion unit 120 is supplied to the transmission processing unit 132 of the transmission unit 130 (S101). At this time, assume that the transmission processing unit 132 also retains the file name of the pre-conversion CDR data file.

[0053] When the transmission processing unit 132 obtains the converted CDR data, it sets the transfer number to its initial value (in this case, "01") and generates a file name to be assigned to the converted CDR data (S102). At this time, the transmission processing unit 132 obtains the file identifier and date and time string from the file name of the pre-conversion CDR data file corresponding to the converted CDR data, and applies them to the file name of the newly generated converted CDR data file. Here, let's assume that in the pre-conversion CDR data file, the file identifier string was "xxx" and the date and time string was "20221024173500". Then, in the transmission processing unit 132, the file name for the converted CDR data file with the transfer number set to its initial value (01) will be "xxx_20221024173500_01".

[0054] Next, the transmission processing unit 132 instructs the existence check processing unit 131 to perform an existence check to determine whether a file with the same name as the most recently generated file exists in the backup unit 140 of the same system (i.e., whether it is a locally unique file). The existence check processing unit 131 then performs the instructed existence check and returns the result to the transmission processing unit 132 (S103). If the result of the existence check is "existence found", the transmission processing unit 132 operates from step S104, which will be described later, and if it is "non-existence found", it operates from step S105, which will be described later.

[0055] In step S103 described above, if the result of the existence check is "existent", the transmission processing unit 132 increments the transfer number (adds 1) to generate a new file name to be assigned to the converted CDR data (S104), and returns to the process of step S103 described above to perform the existence check again. Here, for example, if the transfer number is incremented from "01" to "02", the newly generated file name will be "xxx_20221024173500_02".

[0056] In step S103 described above, if the result of the existence check is "not present", the transmission processing unit 132 instructs the existence check processing unit 131 to check whether a file with the same name as the most recently generated file name exists (whether it is a system-unique file name). The existence check processing unit 131, following the instructions of the transmission processing unit 132, refers to the receiving directory 310 of the billing system 30, checks for the existence of a file with the same name, and returns the result (result of the existence check) to the transmission processing unit 132 (S105). If the result of the existence check is "not present", the transmission processing unit 132 operates from step S106 described later, and if it is "present", it operates from step S108 described later.

[0057] If the result of the existence check in step S105 described above is "not present", the transmission processing unit 132 sends the converted CDR data file, which has been given the most recently generated file name (i.e., the system unique file name), to the billing system 30 and has it recorded in the receiving directory 310 (S106). At the same time, the transmission processing unit 132 also stores the converted CDR data file that it sent to the billing system 30 in the backup unit 140 (S107).

[0058] On the other hand, if the result of the existence check in step S105 above is "existent", the transmission processing unit 132 decides to cancel the transmission of the converted CDR data file (S108) and stores the converted CDR data file with the most recently generated file name (a locally unique file name but not a system unique file name) in the backup unit 140 (S109).

[0059] As described above, the transmission unit 130 of each CDR conversion device 100 performs the process of transmitting the converted CDR data file.

[0060] Next, using the sequence diagram in Figure 5, we will explain an example of the operation of the CDR converter 0-series 100-0 and the CDR converter 100-1-series 1 when the transmission unit 130 of each CDR converter 100 performs the processing shown in the flowchart in Figure 4.

[0061] Figure 5 is a sequence diagram showing an example of the transmission process of converted CDR data files by the CDR converter 100-0 (Series 0) and the CDR converter 100-1 (Series 1).

[0062] First, the SIP server 20 issues new CDR data (pre-conversion CDR data) (S201), generates a file of the said CDR data (pre-conversion CDR data file) (S202), and sends it to the CDR converter 100-0 of the 0 series and the CDR converter 100-1 of the 1 series, respectively (S203, S204).

[0063] At this time, the file name of the pre-conversion CDR data file was assumed to be "xxx_20221024173500".

[0064] Here, we will first describe the operation of the Series 0 CDR converter 100-0, which receives the pre-conversion CDR data file, and then describe the operation of the Series 1 CDR converter 100-1.

[0065] In the 0 series CDR conversion device 100-0, the receiving unit 110 receives the pre-conversion CDR data file, and the pre-conversion CDR data in the pre-conversion CDR data file is converted by the conversion unit 120 (converted to a format that can be processed by the billing system 30) to obtain the converted CDR data (S205).

[0066] Next, the transmission unit 130 of the CDR converter 100-0 of the 0 series obtains a local unique file name (a unique file name within the same series) corresponding to the newly acquired converted CDR data file (S206). In the transmission unit 130, the loop processing of steps S102 to S104 shown in Figure 4 above can be applied to obtain the local unique file name corresponding to the converted CDR data file.

[0067] Here, we assume that the transmission processing unit 132 of the 0-series CDR converter 100-0 has obtained "xxx_20221024173500_01" as the local unique file name.

[0068] Next, the transmission unit 130 (existence check processing unit 131) of the 0 series CDR conversion device 100-0 performs an existence check (check whether or not it is a system unique file name) to determine whether or not a file with the same name as the local unique file name corresponding to the converted CDR data file exists in the billing system 30 (receiving directory 310) (S207).

[0069] At this point, the result of the existence check by the transmission unit 130 (existence check processing unit 131) of the Series 0 CDR converter 100-0 is assumed to be "not present". In that case, the most recently obtained file name by the transmission unit 130 of the Series 0 CDR converter 100-0 will be the system-unique file name.

[0070] Therefore, the transmission unit 130 (transmission processing unit 132) of the 0 series CDR converter 100-0 generates a converted CDR data file with the system unique file name "xxx_20221024173500_01" added to the converted data (S208), transmits it to the billing system 30 (S209), and has it recorded in the receiving directory 310 (S210).

[0071] At this time, the transmission unit 130 (transmission processing unit 132) of the 0 series CDR converter 100-0 causes the transmitted converted CDR data file to be recorded in the backup unit 140 of the same system (within its own device) (S211).

[0072] Next, we will describe the operation of the CDR converter 100-1 of system 1, which receives the pre-conversion CDR data file.

[0073] In the transmission unit 130 of the CDR converter 100-1 of the 1 series, a local unique file name corresponding to the newly acquired converted CDR data file is obtained, similar to the 0 series (S212, S213). In this case, the transmission processing unit 132 of the CDR converter 100-1 of the 1 series also obtains "xxx_20221024173500_01" as the local unique file name, similar to the 0 series.

[0074] Next, the transmission unit 130 (existence check processing unit 131) of the 0 series CDR converter 100-1 performs an existence check to determine whether a file with the same name as the acquired local unique file name "xxx_20221024173500_01" exists in the billing system 30 (receiving directory 310) (S214).

[0075] At this time, it is assumed that a file named "xxx_20221024173500_01" has already been recorded in the billing system 30 (receiving directory 310) by the 0-series CDR converter 100-0. In other words, it is assumed that, chronologically, the transmission and recording process of the file named "xxx_20221024173500_01" by the 0-series CDR converter 100-0 (steps S209, S210) is completed before the existence check process by the 1-series CDR converter 100-1 (processing in step S214). In that case, in step S214, the result of the existence check by the transmission unit 130 (existence check processing unit 131) of the 0-series CDR converter 100-1 will be "existence found".

[0076] In this case, the transmission unit 130 (transmission processing unit 132) of the 0 series CDR converter 100-1 generates a converted CDR data file with the system unique file name "xxx_20221024173500_01" added to the converted data (S215), but the transmission is canceled.

[0077] At this time, the transmission unit 130 (transmission processing unit 132) of the 0 series CDR converter 100-1 causes the generated converted CDR data file (converted CDR data file whose transmission was canceled) to be recorded in the backup unit 140 of the same system (within its own device) (S216).

[0078] (A-3) Effects of the Embodiment The CDR conversion system 10 of this embodiment can achieve the following effects.

[0079] In this embodiment of the CDR conversion system 10, each CDR conversion device 100 checks for the existence of converted CDR data files to the billing system 30, thus avoiding the process of sending converted CDR data files with duplicate file names.

[0080] Furthermore, in each CDR conversion device 100 of the CDR conversion system 10 of this embodiment, a transfer number (sequence number) is assigned to the file name of the converted CDR data file. Therefore, even if multiple pre-conversion CDR data files with the same file name are supplied from the higher-level side, it is possible to avoid sending converted CDR data files with duplicate file names to the billing system 30.

[0081] Furthermore, in each CDR conversion device 100 of the CDR conversion system 10 of this embodiment, converted CDR data files (converted CDR data files whose transmission was canceled) with filenames determined to exist in the existence check process for the billing system 30 are also saved in the backup unit 140 of the same system. As a result, even without performing synchronization processing between each CDR conversion device 100, the contents of the converted CDR data files transmitted to the billing system 30 are synchronized (shared) across the entire CDR conversion system 10. Therefore, even if one of the CDR conversion devices 100 stops (for example, due to a failure), the remaining CDR conversion devices 100 can avoid sending converted CDR data files with duplicate filenames.

[0082] (B) Other embodiments The present invention is not limited to the embodiments described above, and modified embodiments such as those exemplified below can also be cited.

[0083] (B-1) In the above embodiment, the formats shown in Figures 2 and 3 are examples of file names for the pre-conversion CDR data file and the converted CDR data file processed by the CDR conversion system 10, but the system is not limited thereto. For example, in the above embodiment, the converted CDR data file is shown as having a transfer number as a sequence number added to the file name of the pre-conversion CDR data file, but the system is not limited to a transfer number (sequence number), and characters or strings representing information indicating the file generation order (hereinafter referred to as "sequence information") may be applied. For example, the transfer number (sequence number) may be replaced with sequence information represented by one or more letters of the alphabet. For example, the initial value of the sequence information (equivalent to "01" in the transfer number) may be set to "A", and then change (increment) to "B", "C", "D", ... "Z". Alternatively, the sequence information may be represented by two or more letters of the alphabet. For example, the initial value of the sequence information may be set to "AA", and then change to "AB", "AC", "AD", ... "AZ", "BA", "BB", ... "ZZ".

[0084] (B-2) In the above embodiment, the CDR conversion system 10 (each CDR conversion device 100) converts the pre-conversion CDR data file supplied from the SIP server 20, which is the first external device, into a converted CDR data file and sends it to the billing system 30, which is the second external device. However, the source and destination of the CDR data files processed by the CDR conversion system 10 (each CDR conversion device 100) are not limited to the above example, and various devices can be applied. [Explanation of Symbols]

[0085] 1...Telephone communication system, 20...SIP server, 10...CDR conversion system, 100, 100-1, 100-2...CDR conversion device, 110...Receiving unit, 120...Conversion unit, 130...Transmitting unit, 131...Existence check processing unit, 132...Transmission processing unit, 140...Backup unit, 30...Billing system, 310...Receiving directory

Claims

1. A conversion means for converting call information in a first format, which is contained in a first call information file containing call information in a first format supplied from a first external device, into call information in a second format, A file generation means that generates a second call information file containing the second format call information converted by the conversion means, A transmission means for transmitting the second call information file generated by the file generation means to a second external device, The second external device includes a file verification means for checking whether a file with the same name as the file name of the second call information file generated by the file generation means exists, The file generation means has a storage means for storing the second call information file generated by the file generation means, The file generation means includes sequence information indicating the order in which the files were generated, and assigns a string to the file name of the second call information file that is unique among those stored in the storage means. The transmission means transmits to the second external device any of the second call information files generated by the file generation means that the file verification means has confirmed that no file with the same name exists in the second external device. A call information processing device characterized by the following:

2. The call information processing device according to claim 1, characterized in that the file generation means sets a string containing a sequence number as sequence information in the file name of the second call information file.

3. The call information processing device according to claim 2, characterized in that, if the file generation means duplicates a file name that is to be assigned to the second call information file, it repeats the process of changing the sequence number to the next number and assigning it to the file name of the second call information file, thereby obtaining a file name that is unique among those stored in the storage means.

4. Computers, A conversion means for converting call information in a first format, which is contained in a first call information file containing call information in a first format supplied from a first external device, into call information in a second format, A file generation means that generates a second call information file containing the second format call information converted by the conversion means, A transmission means for transmitting the second call information file generated by the file generation means to a second external device, The second external device includes a file verification means for checking whether a file with the same name as the file name of the second call information file generated by the file generation means exists, The file generation means is configured to function as a storage means for storing the second call information file generated by the file generation means. The file generation means includes sequence information indicating the order in which the files were generated, and assigns a string to the file name of the second call information file that is unique among those stored in the storage means. The transmission means transmits to the second external device any of the second call information files generated by the file generation means that the file verification means has confirmed that no file with the same name exists in the second external device. A call information processing program characterized by the following features.

5. In a call information processing method performed by a call information processing device, It has a conversion means, a file generation means, a transmission means, a file verification means, and a storage means, The conversion means converts the call information in the first format contained in the first call information file, which includes call information in the first format supplied from the first external device, into call information in the second format. The file generation means generates a second call information file containing the call information in the second format converted by the conversion means, The transmission means transmits the second call information file generated by the file generation means to the second external device. The file verification means checks whether a file with the same name as the file name of the second call information file generated by the file generation means exists in the second external device. The storage means stores the second call information file generated by the file generation means. The file generation means includes sequence information indicating the order in which the files were generated, and assigns a string to the file name of the second call information file that is unique among those stored in the storage means. The transmission means transmits to the second external device any of the second call information files generated by the file generation means that the file verification means has confirmed that no file with the same name exists in the second external device. A call information processing method characterized by the following.

6. A call information processing system comprising a plurality of call information processing devices, characterized in that the call information processing device is one of the call information processing devices described in any one of claims 1 to 3.

Images