Method, device, equipment, storage medium and product for charging call detail record (cdr)
By receiving and processing vehicle call detail records (CDRs), determining resource sharing relationships, and extracting shared CDRs, the problem that existing systems cannot support resource sharing and billing between vehicle networking services and mobile communications has been solved, enabling accurate billing across business systems.
Patent Information
- Application Number
- CN202410705385.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-03
- Publication Date
- 2025-12-05
- Estimated Expiration
- 2044-06-03
AI Technical Summary
The existing call detail record (CDR) billing system cannot support the cross-business system traffic sharing mode in IoT services, especially the shared billing of vehicle networking services and mobile communication resources.
By receiving vehicle call detail records (CDRs) from network element devices, the system uses vehicle SIM card information to determine if a resource sharing relationship exists. If it does, the shared portion of the CDRs is extracted and sent to the SIM card service support system for billing. If it does not exist, billing is performed directly.
It enables call detail record (CDR) billing across multiple business systems, supports resource sharing and CDR billing between vehicle cards and phone cards, and ensures the accuracy and completeness of billing.
Smart Images

Figure CN118741439B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of mobile communication, in particular to a method and device for classifying telephone bill, equipment, storage medium and product. BACKGROUND
[0002] With the continuous development of Internet of Things technology, the intelligent degree of in-vehicle terminals of the automobile is getting higher and higher, and frequent information transmission with the outside world is needed. Many automobiles begin to need mobile operators to provide mobile communication services.
[0003] At present, users have the demand of sharing and using the mobile communication resources of the automobile and the mobile phone. However, the existing related technical solutions are mainly for the telephone bill charging of traditional mobile phone communication services, such as the charging of call bills and GPRS traffic bills, and do not support the Internet of Things business, not to mention the telephone bill charging of the traffic sharing mode across multiple businesses and between business systems in the emerging vehicle networking business. Therefore, the telephone bill charging scheme across multiple business systems is needed at present. SUMMARY
[0004] The present application provides a method and device for telephone bill charging, equipment, storage medium and product, which can charge the telephone bill across multiple business systems.
[0005] In a first aspect, the present application provides a method for telephone bill charging, which is applied to a vehicle networking business center, and the method comprises the following steps:
[0006] receiving a first telephone bill of a first vehicle sent by a network element device, wherein the first telephone bill contains vehicle card information corresponding to the first vehicle;
[0007] determining whether there is a resource sharing relationship corresponding to a telephone card according to the vehicle card information;
[0008] in the case that there is no corresponding resource sharing relationship of the vehicle card, charging according to the first telephone bill;
[0009] in the case that there is a corresponding resource sharing relationship of the vehicle card, extracting a shared part of the first telephone bill;
[0010] sending the shared part of the telephone bill to a telephone card business support system, so as to charge the shared part of the telephone bill by the telephone card business support system.
[0011] The above method of the application receives the first bill of the first vehicle sent by the network element device, determines whether the vehicle card has a resource sharing relationship corresponding to the phone card by using the vehicle card information in the first bill. If not, the billing is directly performed. If yes, it means that the vehicle card has a phone card associated therewith and can share the communication resources (such as data flow, call duration, etc.), and the shared part of the first bill is extracted and sent to the phone card service support system, so that the phone card service support system performs billing on the shared part of the bill. In this way, the bill billing can be performed across multiple service systems, and the resource sharing and bill billing of the vehicle card and the phone card two service systems are realized.
[0012] In some possible implementation manners, the receiving the first bill of the first vehicle sent by the network element device comprises:
[0013] In the case that the network element has new bill files, the new bill files are collected one by one to a temporary storage location according to the scanning order;
[0014] In the case that the bill file in the temporary storage location is consistent in size with the corresponding bill file in the network element, the bill file in the temporary storage location is moved to a target storage location, and the receiving of the first bill is completed.
[0015] The above method of the application collects the new bill files one by one to a temporary storage location according to the scanning order, and then checks whether the file size of the bill file in the temporary storage location is consistent with the original file. In the case of consistency, the bill file in the temporary storage location is moved to a target storage location, and the receiving of the first bill is completed. The integrity of the received bill file can be ensured.
[0016] In some possible implementation manners, in the case that the bill file in the temporary storage location is consistent in size with the corresponding bill file in the network element, after the bill file in the temporary storage location is moved to a target storage location and the receiving of the first bill is completed, the method further comprises:
[0017] File cleaning information is sent to the network element device, so that the network element device deletes the new bill file or moves the new bill file to a backup storage location.
[0018] The above method of the application sends file cleaning information to the network element device after the receiving of the first bill is completed, so that the network element device cleans the related files, and the space occupation of the network element device by too many files can be avoided.
[0019] In some possible implementation manners, in the case that the vehicle card has a corresponding resource sharing relationship, the shared part of the first bill is extracted, comprising:
[0020] According to the first bill, the resource usage of the vehicle card is counted;
[0021] In a case where the resource usage exceeds a preset resource usage threshold, the first bill is split into a first sub-bill that does not exceed the preset resource usage threshold and a second sub-bill that exceeds the preset resource usage threshold;
[0022] The second sub-bill is taken as a shared part bill in the first bill.
[0023] The above manner of the present application counts the resource usage of the vehicle card through the first bill. If the resource usage exceeds the preset resource usage threshold, the first bill is split into the first sub-bill that does not exceed the preset resource usage threshold and the second sub-bill that exceeds the preset resource usage threshold, and then the second sub-bill is taken as the shared part bill in the first bill. The shared part in the bill can be accurately split.
[0024] In some possible implementation manners, the sending of the shared part bill to the telephone card service support system includes:
[0025] A number home location corresponding to a telephone card having a resource sharing relationship with the vehicle card is obtained;
[0026] The shared part bill is sent to a telephone card service support system corresponding to the number home location.
[0027] The above manner of the present application obtains the number home location corresponding to the telephone card having the resource sharing relationship with the vehicle card, and then sends the shared part bill to the corresponding telephone card service support system according to the number home location. The bill can be accurately sent to the corresponding telephone card service support system.
[0028] In a second aspect, the present application further provides a bill charging method. The method is applied to a telephone card service support system, and includes the following steps:
[0029] Second bills sent by subordinate nodes are received. The subordinate nodes at least include a vehicle networking service center. The second bills are obtained by extracting shared part bills in first bills in a case where the vehicle networking service center determines that a vehicle card has a corresponding resource sharing relationship according to vehicle card information corresponding to the first bills after receiving the first bills sent by network element devices.
[0030] The bills are decoded, and the shared part bills are extracted.
[0031] The shared part bills are charged.
[0032] In some possible implementation manners, the decoding of the bill and the extraction of the shared bill part include:
[0033] selecting a corresponding decoder according to the total number of field separators in the bill;
[0034] decoding the bill by using the decoder to obtain a corresponding bill field;
[0035] extracting the bill in which the field value of the shared bill identification field in the bill field is a preset value as the shared bill part.
[0036] The above manner of the application can accurately extract the shared bill in the bill by using a corresponding decoder to decode the bill according to the total number of field separators in the bill to obtain a bill field, and then extracting the bill in which the field value of the shared bill identification field is a preset value as the shared bill part.
[0037] In some possible implementation manners, before the billing of the shared bill part, the method further includes:
[0038] determining whether the shared bill part has a resource sharing relationship corresponding to a telephone card according to the vehicle card information corresponding to the shared bill part;
[0039] in a case where the resource sharing relationship does not exist, regarding the shared bill part as a wrong bill.
[0040] The above manner of the application can determine whether the shared bill part has a resource sharing relationship corresponding to a telephone card, and regard the shared bill part as a wrong bill in a case where the resource sharing relationship does not exist, thereby verifying the shared bill part and avoiding incorrect billing.
[0041] In a third aspect, the application provides a bill billing device, which includes:
[0042] a receiving module configured to receive a first bill of a first vehicle sent by a network element device, the first bill containing vehicle card information corresponding to the first vehicle;
[0043] a determining module configured to determine whether a vehicle card has a resource sharing relationship corresponding to a telephone card according to the vehicle card information;
[0044] a billing module configured to perform billing according to the first bill in a case where the vehicle card does not have a corresponding resource sharing relationship;
[0045] an extracting module configured to extract a shared bill part in the first bill in a case where the vehicle card has a corresponding resource sharing relationship;
[0046] The sending module is configured to send the shared part of the call record to a telephone card service support system, so that the telephone card service support system charges the shared part of the call record.
[0047] In a fourth aspect, an embodiment of the present application provides a device for call record charging, which comprises a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the method for call record charging as described above.
[0048] In a fifth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer program instructions; the computer program instructions are executed by a processor to implement the method for call record charging as described above.
[0049] In a sixth aspect, an embodiment of the present application provides a computer program product, instructions in the computer program product are executed by a processor of an electronic device to cause the electronic device to perform the method for call record charging as described above.
[0050] The above manner of the present application receives the first call record of the first vehicle sent by the network element device, determines whether the vehicle card has a resource sharing relationship corresponding to the telephone card by using the vehicle card information in the first call record. If not, direct charging is performed. If yes, it is indicated that the vehicle card has a telephone card associated therewith and can share communication resources (such as data flow, call duration, etc.), and the shared part of the first call record is extracted and sent to the telephone card service support system, so that the telephone card service support system charges the shared part of the call record. In this way, call record charging can be performed across multiple service systems, and resource sharing and call record charging of the vehicle card and the telephone card two service systems are realized. BRIEF DESCRIPTION OF DRAWINGS
[0051] The present application can be better understood from the following description of specific embodiments thereof, given by way of example and implemented with reference to the accompanying drawings, in which:
[0052] Other characteristics, objects and advantages of the present application will become more apparent from the following detailed description of non-restrictive embodiments thereof, given by way of example and implemented with reference to the attached drawings, in which the same or similar references denote the same or similar features.
[0053] Figure 1 is a flowchart of a method for call record charging provided by an embodiment of the present application;
[0054] Figure 2 is a flowchart of a method for call record charging provided by another embodiment of the present application;
[0055] Figure 3 is a system timing diagram of a method for call record charging provided by another embodiment of the present application;
[0056] Figure 4 is a structural schematic diagram of an apparatus for bill charging provided by an embodiment of the present application;
[0057] Figure 5 is a hardware structural schematic diagram of the apparatus for bill charging provided by an embodiment of the present application. DETAILED DESCRIPTION
[0058] Features and exemplary embodiments of various aspects of the present application will be described in detail below. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, it will be apparent to one of ordinary skill in the art that the present application can be practiced without some or all of these specific details. The description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application. The present application is in no way limited to any specific configuration and algorithm set forth below, but covers any modification, replacement, and improvement of elements, components, and algorithms without departing from the spirit of the present application. In the accompanying drawings and the following description, well-known structures and techniques are not shown in order to avoid unnecessary obscuring of the present application.
[0059] General Packet Radio Service (GPRS): is a wireless transmission method developed using the concept of "packet switching".
[0060] With the continuous development of Internet of Things technology, the intelligent degree of in-vehicle terminals of the current automobile is getting higher and higher, and frequent information transmission with the outside world is needed. Many automobiles begin to need mobile operators to provide mobile communication services. In the Internet of Vehicles, the vehicle card is one of the key devices for connecting the vehicle with the mobile communication network. The vehicle card can provide communication, navigation, entertainment and other functions of the vehicle, and also generates traffic bills.
[0061] At present, users have the demand of sharing and using the mobile communication resources of the automobile and the mobile phone. In this regard, if the above demand is to be met, the mobile operator needs to support the separation and charging of bills in the sharing mode, separate the different bills of each business system in the vehicle end and the mobile phone end, and then charge the sharing and separate charging parts respectively. However, the existing related technical solutions are mainly for the bill charging of traditional mobile phone communication services, such as the charging of call bills and GPRS traffic bills, and do not support Internet of Things services, not to mention the bill charging of the traffic sharing mode in the emerging Internet of Vehicles business which integrates multiple services and crosses between business systems. Therefore, the bill charging scheme across multiple business systems is needed at present.
[0062] The inventor has found that, in order to realize the above scheme, the vehicle networking service billing accounting system needs to support the separation and billing of bills in a sharing mode. Specifically, when processing the traffic bills of the vehicle card, the bills of each service system are separated according to the subscription mode in the subscription relationship, so as to be billed and the shared communication resources are calculated.
[0063] In the embodiment, the method can be performed by the above bill charging device. In one embodiment of the method for charging bills, as shown in Figure 1 the method includes the following steps S101-S105.
[0064] Step S101: receiving a first bill of a first vehicle sent by a network element device, wherein the first bill contains vehicle card information corresponding to the first vehicle.
[0065] In a specific implementation, the network element device sends the first bill of the first vehicle through the network, and then the first bill is parsed to extract the vehicle card information contained therein. If necessary, after extracting the vehicle card information, data verification and integrity check may be performed to ensure that the extracted information is accurate.
[0066] Step S102: determining whether there is a resource sharing relationship corresponding to the telephone card according to the vehicle card information.
[0067] The resource sharing relationship can be a relationship in which the vehicle card and the telephone card share some communication resources (such as data traffic, call duration, etc.).
[0068] In a specific implementation, after obtaining the vehicle card information, the relevant database is searched according to the unique identifier of the vehicle card to determine whether there is a resource sharing relationship corresponding to the telephone card.
[0069] Step S103: charging according to the first bill in the case where the vehicle card does not exist corresponding resource sharing relationship.
[0070] In a specific implementation, a set of charging rules are preset to determine the charging mode under different conditions. In the case where the vehicle card does not exist corresponding resource sharing relationship, the call duration, data usage, etc. are calculated, and the final fee amount is determined in combination with the set rate.
[0071] Step S104: extracting the shared part of the first bill in the case where the vehicle card exists corresponding resource sharing relationship.
[0072] In a specific implementation, if there is a resource sharing relationship, the corresponding extraction rule can be acquired for subsequent shared part bill extraction. According to the extraction rule, the call record in the first bill is screened and processed, and the shared part bill that meets the sharing rule is extracted.
[0073] Step S105: sending the shared part bill to the phone card service support system for the phone card service support system to charge the shared part bill.
[0074] The phone card service support system can be an integrated service operation and management platform, which can be responsible for the charging of general telecommunications services.
[0075] In a specific implementation, the shared part bill data needs to be formatted according to the format required by the phone card service support system. Then, a communication channel is established between the phone card service support system, and the formatted shared part bill data is sent to the phone card service support system through the selected transmission protocol, so that the phone card service support system can charge.
[0076] The above method of the present application receives the first bill of the first vehicle sent by the network element device, determines whether the vehicle card has a resource sharing relationship with the phone card by using the vehicle card information in the first bill. If not, it directly charges. If yes, it means that the vehicle card has a phone card associated with it, which can share communication resources (such as data flow, call duration, etc.), and then sends the shared part bill in the first bill to the phone card service support system, so that the phone card service support system charges the shared part bill. In this way, bill charging can be performed across multiple service systems, and resource sharing and bill charging of the vehicle card and the phone card two service systems can be realized.
[0077] In some embodiments, the first bill of the first vehicle sent by the receiving network element device includes:
[0078] In the case of scanning that the network element has a new bill file, the new bill file is collected one by one to a temporary storage location according to the scanning order.
[0079] In a specific implementation, the network element is scanned periodically or according to demand to detect whether a new bill file is generated. Specifically, the file list under the specified directory can be checked, and the creation time or naming rule of the file can be compared to determine whether a new bill file is generated. If it is detected that a new bill file is generated, the new bill file is collected one by one according to the scanning order. The collected new bill file is stored in a temporary storage location. The temporary storage location can be a directory specified by the system in advance, or a path dynamically generated according to the configuration.
[0080] In the case that the size of the call record file in the temporary storage location is consistent with the size of the corresponding call record file in the network element, the call record file in the temporary storage location is moved to the target storage location, and the receiving of the first call record is completed.
[0081] In a specific implementation, when it is detected that a new call record file arrives in the temporary storage location, the size information of the file is acquired, and the size information is compared with the size of the corresponding call record file in the network element to determine whether they are consistent. If the size of the call record file in the temporary storage location is consistent with the size of the corresponding call record file in the network element, the call record file is moved from the temporary storage location to the target storage location, and the receiving of the first call record is completed.
[0082] The above method of the present application can ensure the integrity of the received call record file.
[0083] In some embodiments, after the call record file in the temporary storage location is moved to the target storage location in the case that the size of the call record file in the temporary storage location is consistent with the size of the corresponding call record file in the network element, the receiving of the first call record is completed, and the method further comprises:
[0084] The file cleaning information is sent to the network element device, so that the network element device deletes the new call record file or moves the new call record file to a backup storage location.
[0085] In a specific implementation, after the processing of the new call record file is completed, the corresponding cleaning information is generated. The cleaning information can include a list of call record files that need to be deleted, backup storage location information, and the like. The constructed cleaning information is sent to the network element device. After receiving the cleaning instruction, the network element device performs the corresponding cleaning operation according to the content in the instruction. Specifically, the cleaning operation includes deleting the specified call record file or moving the specified call record file to the backup storage location.
[0086] The above method of the present application can avoid the space occupation of the network element device by the excessive files by sending the file cleaning information to the network element device after the receiving of the first call record is completed.
[0087] In some embodiments, in the case that the vehicle card exists a corresponding resource sharing relationship, the shared part of the first call record is extracted, and the method comprises:
[0088] The resource usage of the vehicle card is counted according to the first call record.
[0089] In a specific implementation, the data of the first bill is parsed to extract information related to the resource usage of the vehicle card. For example, the format of the bill file can be parsed to extract data fields such as the vehicle card number and the resource usage. Then, the system accumulates the resource usage of the vehicle card during the first bill.
[0090] In a specific implementation, the data of the first bill is parsed to extract information related to the resource usage of the vehicle card. For example, the format of the bill file can be parsed to extract data fields such as the vehicle card number and the resource usage. Then, the system accumulates the resource usage of the vehicle card during the first bill.
[0091] In a specific implementation, the data of the first bill is parsed to extract information related to the resource usage of the vehicle card. For example, the format of the bill file can be parsed to extract data fields such as the vehicle card number and the resource usage. Then, the system accumulates the resource usage of the vehicle card during the first bill.
[0092] In a specific implementation, the data of the first bill is parsed to extract information related to the resource usage of the vehicle card. For example, the format of the bill file can be parsed to extract data fields such as the vehicle card number and the resource usage. Then, the system accumulates the resource usage of the vehicle card during the first bill.
[0093] The above method of the present application uses the first bill to count the resource usage of the vehicle card. If the resource usage exceeds the preset resource usage threshold, the first bill is split into a first sub-bill that does not exceed the preset resource usage threshold and a second sub-bill that exceeds the preset resource usage threshold. Then, the second sub-bill is used as the shared part of the first bill. This can accurately split the shared part of the bill.
[0094] In some embodiments, the sending of the shared part bill to the phone card service support system includes:
[0095] Obtaining the number home location of the phone card corresponding to the vehicle card in a resource sharing relationship.
[0096] In a specific implementation, the phone card information corresponding to the vehicle card is queried from the database, including the phone card number. Then, the phone card number is used to obtain the corresponding home location information using a service or database for querying the phone number home location.
[0097] Sending the shared part bill to the phone card service support system corresponding to the number home location.
[0098] In a specific implementation, the target phone card service support system is selected according to the number home location, and a communication connection is established with the target phone card service support system. The data of the shared part bill is packaged according to the interface specification of the target system, and sent to the target system through the communication connection.
[0099] The above method of the present application obtains the number belonging to the area of the telephone card corresponding to the resource sharing relationship of the vehicle card, and then sends the shared part of the bill to the corresponding telephone card service support system according to the number belonging to the area. The bill can be accurately sent to the corresponding telephone card service support system.
[0100] In another embodiment of the classification method of the Internet of Things card of the present application, the method can be applied to a telephone card service support system, and the method comprises the following steps S201 to S203. Figure 2
[0101] Step S201: receiving a second bill sent by each subordinate node, wherein the subordinate node at least comprises a vehicle networking service center, and the second bill is obtained by extracting the shared part of the bill from the first bill under the condition that the vehicle card corresponding to the first bill has a corresponding resource sharing relationship after the first bill is received by the vehicle networking service center.
[0102] In a specific implementation, the telephone card service support system receives bills sent by various subordinate nodes. When the second bill is received, it is necessary to identify which subordinate node the bill comes from.
[0103] Step S202: decoding the bill to extract the shared part of the bill.
[0104] In a specific implementation, the received bill data is identified and decoded, and then the shared part is determined according to the specific field, mark or format of the bill. After the shared part of the bill is determined, the relevant information of the shared part of the bill can be cut off or copied from the decoded data.
[0105] Step S203: charging the shared part of the bill.
[0106] In a specific implementation, the shared part of the bill data is parsed and extracted, and the applicable charging rule is determined. Then, the charging rule is applied to record the generated charging data.
[0107] In some embodiments, the decoding of the bill to extract the shared part of the bill comprises:
[0108] According to the total number of field separators in the bill, a corresponding decoder is selected.
[0109] In a specific implementation, the number of separators in the bill needs to be counted. According to the number of separators counted, a corresponding decoder can be selected. For example, if the number of separators is 1, it may mean that there is only one field in each line, and a simple single-field decoder can be selected; if the number of separators is greater than 1, it may mean that each line contains multiple fields, and a decoder supporting multi-field decoding needs to be selected.
[0110] decoding the bill by the decoder to obtain corresponding bill fields.
[0111] In a specific implementation, after the corresponding decoder is determined, the selected decoder is used to decode the bill. The decoder parses the bill data according to the predefined rules and delimiters, converts it into a data structure that the system can understand, and extracts the content of each field from the decoded data.
[0112] Extract the field value of the shared bill identification field in the bill field as a preset value, as a shared part bill.
[0113] In a specific implementation, the value of the shared bill identification field is extracted from the parsed bill data, and then matched with the preset shared identification value. This preset value can be predefined to indicate which bills should be classified as shared parts. For the shared bill identification field value matching the preset value, the system filters out the corresponding bill data as the shared part bill.
[0114] The above-mentioned manner of the present application decodes the bill using the corresponding decoder according to the total number of field delimiters in the bill to obtain the bill fields. Then, the bill whose field value of the shared bill identification field is a preset value is extracted as a shared part bill. The shared bill in the bill can be accurately extracted.
[0115] In some embodiments, before the billing of the shared part bill, the method further comprises:
[0116] According to the vehicle card information corresponding to the shared part bill, it is determined whether the shared part bill has a resource sharing relationship with the phone card.
[0117] In a specific implementation, the vehicle card information associated with the shared part bill is obtained. According to the extracted vehicle card information, the phone card information stored in the system is matched. If the phone card information matching the vehicle card information in the shared part bill is found, the system can determine whether there is a resource sharing relationship.
[0118] In the case where there is no resource sharing relationship, the shared part bill is regarded as a wrong bill.
[0119] In a specific implementation, in the case where there is no resource sharing relationship, the system marks the shared part bill as a wrong bill. For example, a flag bit or a wrong bill code is added in the bill record, so that the subsequent processing program can identify and process these wrong bills.
[0120] The above manner of the present application determines whether the shared part of the call record exists a resource sharing relationship corresponding to the phone card, and in the case that the resource sharing relationship does not exist, the shared part of the call record is regarded as a wrong record. The shared part of the call record is verified to avoid wrong charging.
[0121] As another implementation manner of the present application, a specific traffic sharing rule is first assumed, and then the technical solution of the embodiment is described based on the assumed traffic sharing rule. In the traffic sharing rule, the traffic resource of the phone card can be shared for the "entertainment channel" traffic generated by the vehicle card, and the voice and short message free resources cannot be shared for the vehicle card. The user or the vehicle enterprise can continue to open the "personal entertainment channel" package for the vehicle card through the Internet of Vehicles business system, and the traffic call record after the package is used up is sent to the system corresponding to the phone card for processing. The traffic resource of the vehicle card cannot be shared for the phone card.
[0122] The traffic of the vehicle card is divided into a vehicle machine use channel and a personal entertainment use channel. The vehicle machine use channel is used by the vehicle enterprise, and the vehicle enterprise uniformly pays and controls it. The personal entertainment use channel is used by the individual, and the vehicle enterprise gives the vehicle owner regular or quantitative traffic, and the individual pays after the expiration or exceeding. The Internet of Vehicles call record is obtained after the network element is collected.
[0123] Reference Figure 3 In the call record flow processing process of the embodiment, three basic systems involved are: a network element, a CMIOT, and a provincial BOSS system. The network element is a carrier of a call record and a traffic record, and is also a raw physical device for collecting the call record. The China Mobile Internet of Things system (CMIOT) is a center of the Internet of Vehicles business system, and is a central receiving system for processing the Internet of Vehicles business in the Internet of Things system. The provincial BOSS system is a provincial branch system of the central system, and is a branch business system receiving the call record sent by the CMIOT and other subsystems.
[0124] In the specific implementation, the vehicle terminal accesses the network through the vehicle card, the corresponding network element generates an entertainment channel traffic call record, and then the network element sends the vehicle card entertainment channel traffic call record.
[0125] The vehicle networking service system adopts a secret file transfer protocol (SFTP) mode to collect entertainment channel traffic bill files to the local. Specifically, the vehicle networking service system scans the files under the directory of the opposite end network element through the SFTP link, and then collects the files one by one in the scanning order. The files collected by FTP are first placed in the local temporary directory. If the file size in the temporary directory is consistent with that in the directory of the opposite end network element, it indicates that the file collection is successful. The file in the temporary directory is moved to the decoding directory, and the file in the directory of the opposite end network element is deleted or moved to the backup directory of the opposite end network element.
[0126] Subsequently, the vehicle networking service system obtains the "person-vehicle-home traffic sharing" relationship corresponding to the vehicle card, and processes the entertainment channel traffic bill according to the "person-vehicle-home shared traffic" business subscription attribute information. For example, for the vehicle card without "person-vehicle-home traffic sharing service" or "person-vehicle-home traffic sharing service" invalid (cancellation or suspension), the personal entertainment channel traffic bill is priced by the CMIOT system; for the vehicle card with "person-vehicle-home traffic sharing service" valid, the personal entertainment channel traffic is preferentially used in the CMIOT, and after the vehicle card package is used up, the CMIOT immediately sends the personal entertainment channel bill to the provincial BOSS for charging. At the same time, for the bill that crosses the free resource use threshold, the part of the traffic exceeding the package needs to be split into an independent bill and sent to the provincial BOSS system. In the specific sending process, the vehicle networking service system sorts the vehicle card entertainment channel traffic bill according to the bound person card province, and sends the vehicle card entertainment channel traffic bill to the corresponding provincial BOSS system.
[0127] The provincial BOSS system collects the entertainment channel traffic bill files sent by the CMIOT system to the local through the SFTP mode: after scanning the files under the CMIOT sending directory through SFTP, the files are collected one by one in the scanning order. The files collected by FTP are first placed in the local temporary directory. If the file size in the temporary directory is consistent with that in the CMIOT sending path, it indicates that the file collection is successful. The file in the temporary directory is moved to the decoding directory, and the file in the CMIOT sending directory is deleted or moved to the CMIOT backup directory.
[0128] The provincial BOSS system first decodes the received bill file: according to the total number of field separators in the bill, the bill is matched with a corresponding decoder, and then according to the separator position of each field in the bill in the file, the corresponding field required by the decoding system is decoded, and the parsed field of each bill is saved to the shared memory, such as decoding: calling number, called number, call start time, call end time, traffic sharing bill identifier…etc. After decoding, according to the "traffic sharing bill identifier" field information in the bill, the traffic sharing bill is filtered out, and then the interface format coding file required by the provincial BOSS system is generated.
[0129] The provincial BOSS system distinguishes and processes the traffic bill of the vehicle card entertainment channel according to the "person-vehicle-family traffic sharing" relationship attribute information. If there is no "person-vehicle-family traffic sharing" relationship or the "person-vehicle-family traffic sharing" relationship is invalid, the bill is processed as an error. If the "person-vehicle-family traffic sharing" relationship is suspended, the bill is processed as an error.
[0130] If there is a valid "person-vehicle-family traffic sharing" subscription relationship, the entertainment channel bill is processed for charging. For the case of providing a vehicle card package, the vehicle card exclusive package resources are consumed first, and then the person card package resources are used. After the package resources are used up, the person card package resources are used for charging, or for the case of providing a vehicle card package, the vehicle card package resources are used for charging. The cost of the vehicle card entertainment channel traffic bill is accumulated to the person card account, and the vehicle card entertainment channel traffic bill is stored. Finally, the vehicle card entertainment channel traffic bill is sent to the first level through the provincial BOSS system, and especially for the provinces that share the user ID of the person card and the vehicle card, the vehicle card number needs to be recorded in the bill.
[0131] The above-mentioned embodiments of the present application are directed to the Internet of Vehicles service, and based on the "person-vehicle-family traffic sharing" relationship, the bill collected from the network element side is separated into various traffic bills step by step, and distributed to the respective provincial BOSS system according to the corresponding attribute. The main core process is to judge the attribute of the "person-vehicle-family traffic sharing" subscription relationship from the original traffic bill collected from the network element side, to realize the distribution of the traffic bill from the central system CMIOT to the respective provincial BOSS system according to the corresponding relationship, so as to realize the clear separation of the bill.
[0132] Based on the above-mentioned bill charging method, the present application also provides a specific implementation mode of the bill charging device. Please refer to the following embodiments.
[0133] Firstly, referring to Figure 4 The bill charging device 400 provided by the embodiments of the present application includes the following modules:
[0134] The receiving module 401 is configured to receive a first bill of a first vehicle sent by a network element device, wherein the first bill comprises vehicle card information corresponding to the first vehicle.
[0135] The determining module 402 is configured to determine whether the vehicle card has a corresponding resource sharing relationship with a telephone card according to the vehicle card information.
[0136] The charging module 403 is configured to charge according to the first bill when the vehicle card does not have a corresponding resource sharing relationship.
[0137] The extracting module 404 is configured to extract a shared part bill in the first bill when the vehicle card has a corresponding resource sharing relationship.
[0138] The sending module 405 is configured to send the shared part bill to a telephone card service support system for charging the shared part bill by the telephone card service support system.
[0139] The above manner of the application receives a first bill of a first vehicle sent by a network element device, and determines whether a vehicle card has a corresponding resource sharing relationship with a telephone card according to vehicle card information in the first bill. If not, charging is directly performed. If yes, it is indicated that the vehicle card has a telephone card associated therewith and can share communication resources (such as data flow, call duration, etc.), and then a shared part bill in the first bill is extracted and sent to a telephone card service support system, so that the telephone card service support system charges the shared part bill. In this way, bill charging can be performed across multiple service systems, and resource sharing and bill charging of the vehicle card and the telephone card two service systems are realized.
[0140] As an implementation manner of the application, the bill charging apparatus 400 further comprises:
[0141] The collecting module is configured to collect the new bill files one by one to a temporary storage location in a scanning order when it is scanned that the network element has new bill files.
[0142] The moving module is configured to move the bill file in the temporary storage location to a target storage location when the bill file in the temporary storage location has the same size as a corresponding bill file in the network element, so as to complete receiving of the first bill.
[0143] The above manner of the application collects the new bill files one by one to a temporary storage location in a scanning order, and then checks whether the file size of the bill file in the temporary storage location is consistent with that of the original file. When the file size is consistent, the bill file in the temporary storage location is moved to a target storage location, so as to complete receiving of the first bill. The integrity of the received bill file is ensured.
[0144] As an implementation manner of the present application, the sending module 405 in the call billing device 400 is further configured to send file cleaning information to the network element device, so that the network element device deletes the new call file or moves the new call file to a backup storage location.
[0145] The above manner of the present application can avoid the space occupation of the network element device by the excessive files by sending the file cleaning information to the network element device after the reception of the first call file is completed, so that the network element device cleans the related files.
[0146] As an implementation manner of the present application, the call billing device 400 further comprises:
[0147] The statistical module is configured to count the resource usage of the vehicle card according to the first call file.
[0148] The splitting module is configured to split the first call file into a first sub-call file that does not exceed the preset resource usage threshold and a second sub-call file that exceeds the preset resource usage threshold, if the resource usage exceeds the preset resource usage threshold.
[0149] The processing module is configured to take the second sub-call file as a shared part of the first call file.
[0150] The above manner of the present application can accurately split the shared part of the call file by counting the resource usage of the vehicle card according to the first call file, splitting the first call file into a first sub-call file that does not exceed the preset resource usage threshold and a second sub-call file that exceeds the preset resource usage threshold, and taking the second sub-call file as a shared part of the first call file.
[0151] As an implementation manner of the present application, the call billing device 400 further comprises:
[0152] The obtaining module is configured to obtain a number home of a telephone card that has a resource sharing relationship with the vehicle card.
[0153] The sending module 405 is further configured to send the shared part call file to a telephone card service support system corresponding to the number home.
[0154] The above manner of the present application can accurately send the call file to the corresponding telephone card service support system by obtaining the number home of the telephone card that has the resource sharing relationship with the vehicle card, and sending the shared part call file to the corresponding telephone card service support system according to the number home.
[0155] The various modules in the device for bill charging provided by the embodiments of the present application can implement the various steps in the bill charging method described above and achieve the corresponding effects. For brevity, no further description is given here.
[0156] Figure 5 A structure schematic diagram of hardware for bill charging provided by the embodiments of the present application is shown.
[0157] The device for bill charging can include a processor 501 and a memory 502 having computer program instructions stored therein.
[0158] Specifically, the processor 501 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement one or more embodiments of the present application.
[0159] The memory 502 can include a mass storage for data or instructions. By way of example and not limitation, the memory 502 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 502 can include removable or non-removable (or fixed) media. Where appropriate, the memory 502 can be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, the memory 502 is non-volatile, solid-state memory.
[0160] The memory can include read-only memory (ROM), random-access memory (RAM), magnetic disk storage mediums, optical storage mediums, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software that, when executed (by one or more processors), is operable to implement the operations described with reference to the method for bill charging according to any of the embodiments of the present disclosure.
[0161] The processor 501 implements any of the bill charging methods in the embodiments described above by reading and executing the computer program instructions stored in the memory 502.
[0162] In one example, the device for bill charging can further include a communication interface 503 and a bus 510. Wherein, as shown in FIG. 5, the communication interface 503 is connected to the bus 510, and the bus 510 is connected to the processor 501 and the memory 502. Figure 5As shown, the processor 501, the memory 502, and the communication interface 503 are connected by the bus 510 and accomplish the communication between each other.
[0163] The communication interface 503 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the application.
[0164] The bus 510 includes hardware, software or both to couple the components of the online data traffic billing device to each other. By way of example, and not limitation, the bus can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand (IB) interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these. Where suitable, the bus 510 can include one or more buses. Although particular buses are described and shown in the embodiments of the application, the application contemplates any suitable bus or interconnect.
[0165] In addition, in combination with the method for charging the call bill in the above-mentioned embodiments, the embodiments of the application can provide a computer storage medium to realize. The computer storage medium has computer program instructions stored thereon; the computer program instructions are executed by a processor to realize any of the methods for charging the call bill in the above-mentioned embodiments.
[0166] However, it needs to be clear that the application is not limited to the specific configurations and processes described above and shown in the figures. Also, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here. In the above-mentioned embodiments, several specific steps are described and shown as examples. However, the method process of the application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps, after understanding the spirit of the application.
[0167] The functions shown in the above-described structural block diagrams can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, and the like. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine-readable medium" includes any medium that can store or transfer information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. The code segments can be downloaded via computer networks such as the Internet, intranets, and the like.
[0168] It is also important to note that the examples described herein can be implemented in a variety of systems, including and not limited to a digital electronic circuit, a
[0169] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. Alternatively, computer program implemented steps can be
[0170] The present application can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the algorithms described in the specific embodiments can be modified without departing from the essential spirit of the present application. Thus, the present embodiments are to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
[0171] It will be understood by those skilled in the art that the above described embodiments are to be taken as illustrative and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Other embodiments of the disclosed embodiments, which are apparent to those skilled in the art and which are based on the teachings of the embodiments disclosed in the attached drawings, the specification and the claims, can be implemented by those skilled in the art without undue effort. In the claims, the term "comprising" does not exclude other devices or steps; the indefinite article "a" does not exclude a plurality; the term "first", "second" etc. do not imply any order, but are used for naming purposes only. Any reference signs in the claims should not be construed as limiting the scope of the claims. The functions of the various units can be performed by a single hardware or software module. The fact that different technical features appear in different dependent claims does not mean that a combination of these technical features cannot be used to advantage.
Claims
1. A method of call billing, characterized by, The method is applied to a vehicle network service center, and the method comprises: receiving a first bill of a first vehicle sent by a network element device, the first bill containing vehicle card information corresponding to the first vehicle; determining whether the vehicle card has a corresponding resource sharing relationship with a telephone card according to the vehicle card information; in the case where the vehicle card does not have a corresponding resource sharing relationship, performing charging according to the first bill; in the case where the vehicle card has a corresponding resource sharing relationship, extracting a shared part bill from the first bill; sending the shared part bill to a telephone card service support system for charging of the shared part bill by the telephone card service support system; wherein, in the case where the vehicle card has a corresponding resource sharing relationship, extracting a shared part bill from the first bill comprises: statistically determining resource usage of the vehicle card according to the first bill; in the case where the resource usage exceeds a preset resource usage threshold, splitting the first bill into a first sub-bill that does not exceed the preset resource usage threshold and a second sub-bill that exceeds the preset resource usage threshold; taking the second sub-bill as the shared part bill in the first bill.
2. The method of call accounting according to claim 1, wherein, The receiving of the first bill of the first vehicle sent by the network element device comprises: in the case where the network element has newly added bill files, collecting the newly added bill files one by one to a temporary storage location according to the scanning order; in the case where the bill files in the temporary storage location are consistent in size with corresponding bill files in the network element, moving the bill files in the temporary storage location to a target storage location to complete the receiving of the first bill.
3. The method of call accounting according to claim 2, wherein, After the bill files in the temporary storage location are moved to the target storage location to complete the receiving of the first bill in the case where the bill files in the temporary storage location are consistent in size with corresponding bill files in the network element, the method further comprises: sending file cleaning information to the network element device for deleting the newly added bill files or moving the newly added bill files to a backup storage location by the network element device.
4. The method of call accounting according to claim 1, wherein, The sending of the shared part bill to the telephone card service support system comprises: acquiring a number home location corresponding to the telephone card having a resource sharing relationship with the vehicle card; sending the shared part bill to a telephone card service support system corresponding to the number home location.
5. A method of charging a phone bill, characterized by, The method is applied to a telephone card service support system, and the method comprises: receiving second bills sent by subordinate nodes, the subordinate nodes at least comprising a vehicle network service center, the second bills being obtained by extracting shared part bills from first bills in the case where the vehicle network service center determines that vehicle cards have corresponding resource sharing relationships according to vehicle card information corresponding to the first bills; decoding the bills to extract the shared part bills; performing charging on the shared part bills; wherein, in the case where the vehicle cards have corresponding resource sharing relationships, extracting shared part bills from the first bills comprises: statistically determining resource usage of the vehicle cards according to the first bills; in a case where the resource usage amount exceeds a preset resource usage threshold, splitting the first bill into a first sub-bill that does not exceed the preset resource usage threshold and a second sub-bill that exceeds the preset resource usage threshold; sending the second sub-bill as a shared part bill in the first bill.
6. The method of call accounting according to claim 5, wherein, The decoding of the bill and the extraction of the shared part bill include: selecting a corresponding decoder according to a total number of field separators in the bill; decoding the bill by using the decoder to obtain a corresponding bill field; extracting a bill with a field value of a shared bill identification field in the bill field as a shared part bill.
7. The method of call accounting according to claim 5, wherein, Before the billing of the shared part bill, the method further includes: determining whether the shared part bill has a resource sharing relationship corresponding to a phone card according to vehicle card information corresponding to the shared part bill; in a case where there is no resource sharing relationship, regarding the shared part bill as a wrong bill.
8. A device for charging of a call slip, characterized in that The apparatus includes: a receiving module configured to receive a first bill of a first vehicle sent by a network element device, the first bill containing vehicle card information corresponding to the first vehicle; a determining module configured to determine whether a vehicle card has a resource sharing relationship corresponding to a phone card according to the vehicle card information; a billing module configured to perform billing according to the first bill in a case where the vehicle card does not have a corresponding resource sharing relationship; an extracting module configured to extract a shared part bill in the first bill in a case where the vehicle card has a corresponding resource sharing relationship; a sending module configured to send the shared part bill to a phone card service support system for billing of the shared part bill by the phone card service support system; wherein the extracting module is further configured to count a resource usage amount of the vehicle card according to the first bill; in a case where the resource usage amount exceeds a preset resource usage threshold, split the first bill into a first sub-bill that does not exceed the preset resource usage threshold and a second sub-bill that exceeds the preset resource usage threshold; and send the second sub-bill as a shared part bill in the first bill.
9. A device for charging of a call slip, characterized in that The device includes a processor and a memory having computer program instructions stored therein; the processor reads and executes the computer program instructions to implement the method for billing of the bill according to any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer readable storage medium has computer program instructions stored thereon, and the computer program instructions are executed by a processor to implement the method for billing of the bill according to any one of claims 1-7.
11. A computer program product, characterised in that, The instructions in the computer program product are executed by a processor of an electronic device, so that the electronic device performs the method for billing of the bill according to any one of claims 1-7.
Citation Information
Patent Citations
Resource sharing charging method, charging device and memory library
CN106982126A
Payment method for vehicle, computer equipment and storage medium
CN114202809A