Communication control method and apparatus, electronic device, and storage medium

Abstract

Embodiments of the present application provide a communication control method and device, electronic equipment and storage medium, and relate to the technical field of communication, to solve the problem that in the prior art, the charging process for a user is long, which causes the user to continuously use a charging link, thereby limiting the charging process for other users. The method comprises: in the case of receiving a charging session establishment request, generating a file according to the charging session establishment request; feeding back target information to a network element, the target information comprising response information indicating success or response information indicating failure; and according to the file, counting traffic charging.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication control method, apparatus, electronic device and storage medium. Background Technology

[0002] Currently, in 5G user service projects, it is necessary to bill the data traffic generated by 5G users during use.

[0003] In the existing billing process, the mainstream 5G user billing and pricing process is a configuration-free (5Goffline) billing process. In the 5Goffline billing process, after the Charging Function (CHF) module obtains the session control from the network element side, it needs to send it to the Session Management Function (SMF) module for information enhancement. Then, the enhanced information is sent to the billing module for billing and real-time billing discount processing. After that, the processing result is fed back to the Session Management module for billing, and the processing result is fed back to the CHF module and the network element side, thus indicating that a user billing process is complete.

[0004] It is evident that in the existing technology, the billing process for a single user is lengthy, causing that user to continuously use a single billing link, thereby restricting the initiation of billing processes for other users. Summary of the Invention

[0005] This application provides a communication control method to solve the problem in the prior art where the billing process for a single user is too long, causing the user to continuously use a billing link, thereby restricting the initiation of billing processes for other users.

[0006] To solve the above-mentioned technical problems, the embodiments of this application are implemented as follows:

[0007] This application provides a communication control method, the method comprising:

[0008] Upon receiving a billing session establishment request, a file is generated based on the billing session establishment request;

[0009] Feedback of target information to network elements, wherein the target information includes response information indicating success or response information indicating failure;

[0010] According to the document, traffic flow is used for billing.

[0011] Optionally, before calculating traffic usage for billing based on the document, the method further includes:

[0012] Get the dynamic step size;

[0013] According to the dynamic step size, obtain the call detail record (CDR) message;

[0014] Add the call detail record (CDR) message to the file.

[0015] Optionally, before calculating traffic usage for billing based on the document, the method further includes:

[0016] Reclaim timed-out call detail records (CDRs);

[0017] Reclaim abnormal call detail records (CDRs).

[0018] Optionally, before calculating traffic usage for billing based on the document, the method further includes:

[0019] If the number of call detail records (CDRs) in the file exceeds a preset threshold, a circuit breaker will be triggered.

[0020] This application provides a communication control device, the device comprising:

[0021] The generation module is used to generate a file based on the billing session establishment request when a billing session establishment request is received;

[0022] The response module is used to feed back target information to the network element. The target information includes response information indicating success or response information indicating failure.

[0023] The statistics module is used to calculate traffic usage and billing based on the file.

[0024] Optionally, the device further includes:

[0025] The first acquisition module is used to acquire the dynamic step size;

[0026] The second acquisition module is used to acquire call detail records (CDRs) according to the dynamic step size.

[0027] An add module is used to add the call detail record (CDR) messages to the file.

[0028] Optionally, the device further includes:

[0029] The first recycling module is used to recycle timed-out call detail records (CDRs).

[0030] The second recycling module is used to recycle abnormal call detail records (CDRs).

[0031] Optionally, the device further includes:

[0032] The processing module is used to perform circuit breaking when the number of call detail records (CDRs) in the file exceeds a preset threshold.

[0033] This application also provides an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the communication control method as described above.

[0034] This application also provides a readable storage medium, which, when the instructions in the storage medium are executed by the processor of an electronic device, enables the electronic device to perform the aforementioned communication control method.

[0035] Thus, in the embodiments of this application, after receiving the billing session establishment request, the CHF module, based on the real-time billing requirements of postpaid users, generates a file after the 5Goffline pricing process begins. This file is used to store call detail records (CDRs) for backend traffic billing. After generating the file, the CHF module directly responds to the network element with a success or failure message, without needing to perform a series of processing steps before feeding back to the network element. Therefore, in the embodiments of this application, feedback can be given to the network element as early as possible, shortening the user's billing process. This prevents a user from continuously using a single billing link, thus not restricting the initiation of billing processes for other users and allowing billing to be performed on more users.

[0036] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0037] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is one of the flowcharts of the communication control method according to an embodiment of this application;

[0039] Figure 2 This is a second flowchart of the communication control method according to an embodiment of this application;

[0040] Figure 3 This is the third flowchart of the communication control method according to an embodiment of this application;

[0041] Figure 4 This is the fourth flowchart of the communication control method according to an embodiment of this application;

[0042] Figure 5This is a block diagram of a communication control device according to an embodiment of this application;

[0043] Figure 6 This is a block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] In existing technologies, the billing process for a single user is a complex, interconnected series of steps. With the increasing number of 5G users, the message volume grows exponentially. This lengthy processing method makes it difficult to ensure timely and accurate processing at each stage, resulting in numerous message timeouts and errors when returning messages to network elements, significantly increasing the difficulty of call detail record (CDR) processing. Secondly, as the number of 5G users grows, billing capacity must also increase synchronously, requiring each stage to expand its capacity simultaneously. This leads to some stages not reaching full capacity, resulting in extreme waste. Finally, the large amount of interleaving between online and offline messages causes slow order processing in the batch pricing module, making CDRs prone to congestion and loss, posing a significant challenge to the accuracy and timeliness of billing. Therefore,

[0046] See Figure 1 This diagram illustrates a flowchart of the steps of a communication control method according to an embodiment of this application. The method is applied to an electronic device, such as... Figure 1 As shown, the communication control method may include the following steps:

[0047] Step 110: Upon receiving a billing session establishment request, generate a file based on the billing session establishment request.

[0048] Step 120: Feed back target information to the network element. The target information includes response information indicating success or response information indicating failure.

[0049] Step 130: Based on the document, calculate the traffic flow and billing.

[0050] See Figure 2 When the CHF module receives a billing session establishment request, it determines the process type after adjusting the dynamic step size. If it is an offline process, the billing request is written to a file, and the module determines whether the file is successfully generated. If successful, a success message is sent to the network element; if the file generation fails, an error code is sent to the network element.

[0051] Optionally, the response information used to indicate success includes a success message; the response information used to indicate failure includes an error code.

[0052] Thus, in the embodiments of this application, after receiving the billing session establishment request, the CHF module, based on the real-time billing requirements of postpaid users, generates a file after the 5Goffline pricing process begins. This file is used to store call detail records (CDRs) for backend traffic billing. After generating the file, the CHF module directly responds to the network element with a success or failure message, without needing to perform a series of processing steps before feeding back to the network element. Therefore, in the embodiments of this application, feedback can be given to the network element as early as possible, shortening the user's billing process. This prevents a user from continuously using a single billing link, thus not restricting the initiation of billing processes for other users and allowing billing to be performed on more users.

[0053] In the flow of a communication control method according to another embodiment of this application, before step 130, the method further includes:

[0054] Step A1: Obtain the dynamic step size.

[0055] Step A2: Obtain call detail records (CDRs) according to the dynamic step size.

[0056] Step A3: Add the call detail record (CDR) message to the file.

[0057] Optionally, a call detail record (CDR) message is equivalent to a single CDR.

[0058] The CHF module calls the dynamic step size interface and simultaneously processes call detail records (CDRs). If the CDR generation is successful, it retrieves the dynamic step size return information, queries the trigger configuration table, and assembles the response message for the CHF module. If the dynamic step size call fails or times out, the Trigger_value configured in the VOLUME_LIMIT and TIME_LIMIT settings in the trigger configuration table can be used as the default step size.

[0059] In the offline process, when multiple RGs are split, considering that a network element only issues one billing request when there are multiple RGs, and when a billing request contains multiple RGs, the pricing needs to be split among the RGs, which requires splitting at the front end of the pricing process; for timeout recycling, timeout RGs also need to be recycled. Therefore, the CHF module needs to split the RGs and send a message to the SMF module, moving the RG splitting process of the SMF module forward to the CHF module.

[0060] Optionally, the message body can be parsed to add the offline message to the call log.

[0061] Considering the characteristics of the CHF module in the billing architecture, it cannot carry too much business logic to avoid becoming a system bottleneck. Therefore, messages can be directly written in JSON format without being converted to a delimiter format.

[0062] Optionally, one update can be recorded as one call detail record (CDR); one term message can be recorded as one CDR.

[0063] Optionally, files can be created based on the number of call detail records (CDRs). When creating a file, a temporary file is first generated, and a final file is generated when the configured rule is reached. The CDR configuration rule is: if the configured number of CDRs is reached, the temporary file is converted into a final file; when a new record arrives, a new temporary file is created.

[0064] Optionally, files can be written at time intervals. When writing a file, a temporary file is first generated, and when the configured rules are met, a formal file is generated. The configuration rules for call detail records are: if the file generation duration reaches the configured size, the temporary file is converted into a formal file, and when a new record arrives, a new temporary file is written.

[0065] Optionally, the filename is generated according to the specification, and the filename adopts the following format:

[0066] CHFCDR_<hostname / processname>_ <sourceid>_<date and time>[..<extension>]

[0067] The hostname refers to the name of the host.

[0068] SourceId: Uniquely identifies a file;

[0069] Time: Refers to the date and time the call detail record (CDR) file was opened. Described in ASCII format: YYYYMMDDHHMISS;

[0070] File extension: The default extension is "sr".

[0071] For example, the file name is "CHFCDR_tydic135_1009_20200214120000.sr".

[0072] The session ID is enhanced and written to the original file. Because the session ID in the original billing application is in the message header but not in the message body, the message header needs to be parsed first to enhance the session ID, and then the session ID is written to the call detail record (CDR). The source ID is enhanced to provide a unique identifier for the generated file.

[0073] When generating a file, the sourceid needs to be enhanced. The sourceId must be able to uniquely identify a file. When the file reaches the number of records or the file size, the file is cut, and a new sourceId needs to be generated.

[0074] In another embodiment of the communication control method in this application, the original process is full-process message billing. After the backend times out, it will return a timeout exception to the network element side. After the network element side issues an abnormal offline call detail record, it will proceed with the abnormal offline file billing. After modifying the offline process, after the timeout of the link after CHFProxy and the abnormal record of other links in the exception table, it is necessary to add timeout recovery and abnormal recovery processing of the specified task. During recovery, detailed information is obtained from the call detail records dropped by CHFProxy and the call detail records collected originally.

[0075] Meanwhile, it is necessary to consider that there are currently many recycling programs. The newly added 5G process recycling module DC5GReclaim has similar functions to the 4GHB version recycling program and needs to be merged into one module (the merged functional module can be distinguished by configuration or program input parameters).

[0076] In the process of this embodiment, before step 130, the method further includes:

[0077] Step B1: Reclaim timed-out call detail records (CDRs).

[0078] In this step, a timeout recovery method is provided.

[0079] like Figure 3 The diagram shows the timeout recovery process.

[0080] 1. Scan the table DAT_MISS_[LATN_ID] in real time to obtain the corresponding UUID (task pre-occupancy, etc.) of the unreclaimed tasks.

[0081] Second, based on the source_id parsed from the UUID, information such as the original file (delimiter or JSON format) and line numbers is obtained, and the file is downloaded from the distributed file system.

[0082] 3. Generate a new timeout recovery call detail record (CDR) file.

[0083] 4. Insert the message into the task table and trigger a scan of the task table task_5g_offline, source table, etc., and initiate a timeout recycling and re-batch process.

[0084] V. The recycling task retrieves the original call detail records (CDRs) from the source table based on the source_id and performs subsequent recycling processing.

[0085] In this embodiment, the Offline process needs to perform abnormal recovery of timed-out call detail records (CDRs) to ensure that CDRs are not lost. After a timeout, the data is recorded in the dat_miss table. The model design is as follows:

[0086] Table 1

[0087]

[0088]

[0089] The UUID (64-bit) needs to be modified to: 'B' + 11-bit sourceid + 7-bit rowid + 20-bit Rg + 14-bit time YYYYMMDDHHMISS (JSON format) + 10-bit serial number because it involves timeout recycling.

[0090] Step B2: Reclaim abnormal call detail records (CDRs).

[0091] like Figure 4 The diagram shows the exception handling process.

[0092] 1. The original process was billing based on full-process messages. Abnormalities could not be avoided during process processing. When an abnormality occurred on the SMF side, the abnormal information needed to be output and recorded in the abnormality table.

[0093] II. The process for manually customized recycling tasks at the front desk is as follows:

[0094] The front-end can customize exception recovery tasks based on exception type, effective time, expiration time, and local network, and insert them into the recovery task table.

[0095] The recycling process handles unprocessed tasks in the task list by scanning the local network in real time.

[0096] In the flow of a communication control method according to another embodiment of this application, before step 130, the method further includes:

[0097] Step C1: If the number of call detail records (CDRs) in the file exceeds a preset threshold, perform circuit breaker processing.

[0098] In existing technologies, there are many process steps. The timeout threshold for 5G offline billing messages is on the order of seconds. When a 5G billing message times out, the network element will disconnect from the internet and generate an offline file for billing collection. When the network element reconnects to online message billing, the alternation between online message billing and offline file billing will increase the probability of abnormal 5G offline billing.

[0099] When backend backlog occurs, circuit breaking is implemented. The CHF module judges the backlog, and when it reaches a certain level, it can implement backlog "circuit breaking". The CHF module will no longer write files or send billing requests to the SMF module. It can notify the network element to switch offline and directly follow the abnormal offline file billing process.

[0100] In conjunction with the above embodiments, the corresponding improvements in the SMF module are as follows:

[0101] 1. SMF modifies the REQ processing flow to determine if it is an offline process. If so, sub-session management will no longer be performed, and only the main session management will be retained. When an order is issued every time a deduction is made, SM simplifies the session management process, eliminating the need to accumulate multiple update information to issue orders and canceling the process of inserting and updating the session table. If it is an online process, the original processing method will still be maintained.

[0102] Second: SMF modifies the REQ request process to support multiple usage messages. The 5G message REQ process now supports processing multiple usage messages.

[0103] (1) Supports parsing multiple sets of actual deduction data and modifies the interface to support transmitting multiple sets of actual deduction information to the price approval module.

[0104] (2) Support parsing different groups of location information and modify the interface to support sending multiple groups of locations to the pricing module.

[0105] Three: SMF response removal list cutoff, order cutting and order issuance process.

[0106] (1) Ansbolt removes the list cutoff for 5G data services, such as cutoff for cross-month orders, location changes, etc.

[0107] (2) Ansbolt removes the function of switching orders by duration and traffic volume for 5G data services.

[0108] IV. Corresponding improvements to the SMF response process.

[0109] (1) In the offline process, SM needs to determine the process type. If it is offline, it will not return a response to CHFProxy.

[0110] (2) Optimization of SM request and response concurrent processing mechanism.

[0111] There is an issue with concurrent processing of request and response messages within the same 5G session:

[0112] During the processing of a multi-RG request message, the intermediate status of each sub-session record will be updated to "processing". After each RG responds, the status of the sub-session will be updated to "processing completed". Only after all RGs have responded will the network element be responded to.

[0113] Due to the various trigger_type mechanisms of 5G, the following scenarios may exist:

[0114] After message A (multiple RGs, including RG1, RG2, and RG3) requests processing, the intermediate status of all sub-sessions is updated to "processing". If RG1 and RG2 return a response, the intermediate status of those two sub-sessions is updated to "processing completed". Then, when RG3 returns, a response is sent to the network element.

[0115] If an update2 message for RG1 is reported due to the trigger_type condition while RG3 is not responding, the intermediate status of the sub-session of RG1 will be updated to "processing". If RG3 of update1 returns at this time, it needs to respond to the network element. However, if the intermediate status of RG1 is found to be "processing", no response will be returned to the network element, causing a timeout.

[0116] To address the above scenario, the concurrent processing mechanism is optimized. During the REQ request processing flow, the processing status of all RGs for the billing application is recorded in memory. After the RGs complete processing and return a response, the information stored in memory is used to process the response.

[0117] 5. Corresponding improvements to the order processing stage.

[0118] (1) For the offline process, the SMF module no longer generates the order list from the order generation module.

[0119] (2) For offline processes, the SMF module will no longer generate this file.

[0120] (3) For offline processes, the SMF module no longer generates sum files.

[0121] (4) For the offline process, after the SMF module completes the price approval, it will directly send an ACK back to the agent.

[0122] Corresponding improvements in the pricing module:

[0123] I. 5Goffline message pricing and volume release (this document).

[0124] 5G messages use quantity data, and batch pricing generates quantity data messages, which are sent to Stabolt; when outputting the list, batch pricing directly outputs the quantity data file.

[0125] 2. 5Goffline message pricing generates SUM file.

[0126] 5G message SUM file, batch pricing is output in SUM format; assemble SUM file messages to unified order output bolt.

[0127] 3. No response from SM after the 5G offline mode order is issued.

[0128] (1) 5G offline call detail records, pricing is completed, pricing generates list, quantity record, and SUM order, pricing does not require value-added ACK response flag.

[0129] (2) Cancel the response process and stop responding to SM.

[0130] IV. When there is an abnormal price, an abnormal message is generated in topic(5GAbn_chg).

[0131] When a batch price is abnormal, an abnormal list message is sent to 5GAbn_chg, an order is configured, and the order is entered into DAT_ABNORMAL_LTE_[latn_id]_[billing_cycle_id] via the inventory program. The order is then recycled and processed by the recycling program.

[0132] In this application, the process is simplified. The CHF does not need to reserve message information. After receiving the request, the CHF can respond with a success message to the network element and send a billing message request to the session management module for enhancement information. Then, it is sent to the billing module for billing processing, so as to reduce the offline rate of 5G messages and reduce billing complexity.

[0133] The session management module no longer generates orders based on the price approval results. Instead, it sends the enhanced information to the price approval module, which then generates orders directly based on the actual price approval results. This reduces intermediate interactions and improves the system's order generation efficiency.

[0134] Improve the message response process of the procurement and pre-procurement center. After receiving a message from a network element in the 5G-offline process, the CHF module first sends a success message directly to the network element, and then the CHF module sends a message to the backend for subsequent pricing and discount processes.

[0135] Improve the order processing flow of the 5G-online pricing center. Each update is generated by the pricing center, and after the order is generated, a response message is sent to the front end to complete the authorization process.

[0136] In summary, this application achieves the following: 1. The interaction between network elements is directly determined by the CHF module using simple rules, shortening the latency of message interaction with network elements, reducing the process occupation of online messages, increasing message access for more 5G users, and extending the time for 5G message expansion. 2. The CHF module performs message file order placement and forwards the message to the SMF module after splitting the RG (Regular Request) module. The SMF module reduces interaction with the pricing module, directly forwarding session messages to the pricing module for pricing order placement, greatly improving the message processing capabilities of the SMF module. 3. After pricing, the pricing module issues orders without needing to provide feedback to the session management module, reducing message interaction, integrating the processes of 4G and other services, improving the efficiency of pricing and order issuance, and effectively improving the utilization rate of pricing center resources. 4. The CHF module responds promptly to 5G messages from network elements, greatly reducing timeout and abnormal call records. Users do not need to constantly switch between online and offline, reducing anomalies and improving the accuracy of pricing. Fifth, the CHF module, session management module, and pricing module are decoupled from each other. Capacity expansion can be evaluated independently for each module, and expansion can be carried out according to the processing capacity of each module. This avoids the simultaneous and equal expansion of 5G services, thereby indirectly reducing expansion costs.

[0137] See Figure 5 This illustrates a block diagram of a communication control device according to an embodiment of this application, such as... Figure 5 As shown, the communication control device may include:

[0138] The generation module 10 is used to generate a file based on the billing session establishment request when a billing session establishment request is received.

[0139] The response module 20 is used to feed back target information to the network element. The target information includes response information indicating success or response information indicating failure.

[0140] The statistics module 30 is used to calculate traffic and billing based on files.

[0141] Thus, in the embodiments of this application, after receiving the billing session establishment request, the CHF module, based on the real-time billing requirements of postpaid users, generates a file after the 5Goffline pricing process begins. This file is used to store call detail records (CDRs) for backend traffic billing. After generating the file, the CHF module directly responds to the network element with a success or failure message, without needing to perform a series of processing steps before feeding back to the network element. Therefore, in the embodiments of this application, feedback can be given to the network element as early as possible, shortening the user's billing process. This prevents a user from continuously using a single billing link, thus not restricting the initiation of billing processes for other users and allowing billing to be performed on more users.

[0142] Optionally, the device further includes:

[0143] The first acquisition module is used to acquire the dynamic step size;

[0144] The second acquisition module is used to acquire call detail records (CDRs) according to a dynamic step size.

[0145] Add a module to add call detail records (CDRs) to a file.

[0146] Optionally, the device further includes:

[0147] The first recycling module is used to recycle timed-out call detail records (CDRs).

[0148] The second recycling module is used to recycle abnormal call detail records (CDRs).

[0149] Optionally, the device further includes:

[0150] The processing module is used to perform circuit breaking when the number of call detail records (CDRs) in the file exceeds a preset threshold.

[0151] In this application, the process is simplified. The CHF does not need to reserve message information. After receiving the request, the CHF can respond with a success message to the network element and send a billing message request to the session management module for enhancement information. Then, it is sent to the billing module for billing processing, so as to reduce the offline rate of 5G messages and reduce billing complexity.

[0152] The session management module no longer generates orders based on the price approval results. Instead, it sends the enhanced information to the price approval module, which then generates orders directly based on the actual price approval results. This reduces intermediate interactions and improves the system's order generation efficiency.

[0153] Improve the message response process of the procurement and pre-procurement center. After receiving a message from a network element in the 5G-offline process, the CHF module first sends a success message directly to the network element, and then the CHF module sends a message to the backend for subsequent pricing and discount processes.

[0154] Improve the order processing flow of the 5G-online pricing center. Each update is generated by the pricing center, and after the order is generated, a response message is sent to the front end to complete the authorization process.

[0155] See also Figure 6 This illustrates a block diagram of an electronic device according to an embodiment of the present application, such as... Figure 5 As shown, the electronic device 100 includes: a memory 102, a processor 101, and a computer program stored in the memory 102 and executable on the processor 101. When the computer program is executed by the processor, it implements the above-described communication control method.

[0156] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described communication control method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0157] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0158] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0159] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0160] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

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

[0164] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0166] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / sourceid>

Claims

1. A communication control method, characterized in that, The method includes: Upon receiving a billing session establishment request, a file is generated based on the billing session establishment request; the file is used to store call detail records (CDRs). After the file is generated, the target information is directly fed back to the network element. The target information includes response information indicating that the file generation was successful or response information indicating that the file generation failed. Obtain the dynamic step size; if the dynamic step size call fails or times out, use the default step size; According to the dynamic step size or the default step size, obtain the call detail record (CDR) message and add the CDR message to the file; the CDR message is generated based on the no configuration control message. Based on the aforementioned document, traffic volume billing is performed. According to the document, before traffic billing is calculated, the process also includes: recovering abnormal call detail records (CDRs); the recovery of abnormal CDRs includes: inserting the front-end customized abnormal recovery task into the recovery task table; and processing the unprocessed tasks in the recovery task table by scanning the local network in real time.

2. The method according to claim 1, characterized in that, Before calculating traffic volume for billing based on the document, the method further includes: Reclaim timed-out call detail records (CDRs).

3. The method according to claim 1, characterized in that, Before calculating traffic volume for billing based on the document, the method further includes: If the number of call detail records (CDRs) in the file exceeds a preset threshold, a circuit breaker will be triggered.

4. A communication control device, characterized in that, The device includes: The generation module is used to generate a file based on the billing session establishment request upon receiving the billing session establishment request; the file is used to store call detail records (CDRs). The response module is used to directly feed back target information to the network element after the file is generated. The target information includes response information indicating that the file was generated successfully or response information indicating that the file was generated unsuccessfully. The first acquisition module is used to acquire the dynamic step size; if the dynamic step size call fails or times out, the default step size is used. The second acquisition module is used to acquire call detail records (CDRs) according to the dynamic step size or the default step size; the CDRs are generated based on the no-configuration control message. An add module is used to add the call detail record (CDR) messages to the file; The statistics module is used to calculate traffic usage and billing based on the file. The second recycling module is used to recycle abnormal call detail records (CDRs), including: inserting the customized abnormal recycling tasks from the front end into the recycling task table; and processing unprocessed tasks in the recycling task table by scanning the local network in real time.

5. The apparatus according to claim 4, characterized in that, The device further includes: The first recycling module is used to recycle timed-out call detail records (CDRs).

6. The apparatus according to claim 4, characterized in that, The device further includes: The processing module is used to perform circuit breaking when the number of call detail records (CDRs) in the file exceeds a preset threshold.

7. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the communication control method as described in any one of claims 1 to 3.

8. A readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the communication control method according to any one of claims 1 to 3.

Images