Emergency settlement exemption method, device, equipment, medium and product

Abstract

The present disclosure relates to the technical field of core networks, and in particular to an emergency settlement exemption method, device, equipment, medium and product. The method comprises: obtaining supervision instruction data; obtaining network data and service characteristic data within a coverage range based on the supervision instruction data; and obtaining an emergency settlement exemption result by using an emergency identification model based on the supervision instruction data, the network data and the service characteristic data, the emergency identification model being used to identify whether an emergency event meets a trigger condition of emergency settlement exemption, and the emergency settlement exemption result being used to represent whether to start an exemption process. Through three-dimensional emergency identification of the supervision instruction data, the network data and the service characteristic data, the emergency settlement exemption process can be automatically triggered, the communication support efficiency is improved, and in extreme disasters or other emergency situations, users can quickly obtain free emergency communication services across operators, and communication interruption caused by complex settlement processes is avoided.

Description

Technical Field

[0001] This disclosure relates to the field of core network technology, and in particular to an emergency settlement exemption method, apparatus, equipment, medium and product. Background Technology

[0002] 5G inter-network roaming refers to the temporary access to other operators' networks for communication in emergency scenarios such as earthquakes, floods, or extreme network failures when users cannot connect to their home operator's network. To address such public safety emergencies and provide emergency communication services to users in disaster areas, various operators can implement certain settlement exemption mechanisms for user roaming fees, allowing users to roam for free.

[0003] However, the settlement exemption mechanism in related technologies requires manual approval and multi-stage verification, which makes it difficult for users to obtain exemptions quickly in emergency situations. When disasters occur, the settlement system cannot keep up with emergency needs, and users may not be able to roam in time due to cost issues. Summary of the Invention

[0004] This disclosure is made in view of the above-mentioned problems and provides an emergency settlement exemption method, apparatus, equipment, medium and product.

[0005] According to one aspect of this disclosure, an emergency settlement exemption method is provided, comprising: acquiring regulatory instruction data, the regulatory instruction data being used to characterize the occurrence of an emergency event, the regulatory instruction data including the scope of the emergency event; Based on regulatory instruction data, network data and business characteristic data within the coverage area are obtained. The network data is used to characterize the network status within the coverage area, and the business characteristic data is used to characterize the network behavior characteristics of users within the coverage area. Based on regulatory instruction data, network data, and business characteristic data, an emergency settlement exemption result is obtained using a pre-trained emergency identification model. The emergency identification model is used to identify whether an emergency event meets the triggering conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether to initiate the exemption process.

[0006] The beneficial effects of this solution are as follows: through three-dimensional emergency identification of "regulatory instruction data, network data, and business characteristic data", the emergency settlement exemption process can be automatically triggered, improving communication security efficiency and ensuring that users can quickly obtain free emergency communication services across operators in emergency situations such as extreme disasters, avoiding communication interruptions caused by complex settlement processes.

[0007] Furthermore, according to the emergency settlement exemption method of one aspect of this disclosure, the process for identifying triggering conditions includes: The system determines whether an emergency event meets the first triggering condition based on network data. The first triggering condition includes: determining whether the network data exceeds a preset network threshold and whether an early warning message is received within the coverage area. If the first trigger condition is met, then the trigger condition is confirmed to be met. If the first triggering condition is not met, the emergency event is then judged to meet the second triggering condition based on the business characteristic data. The second triggering condition includes: determining whether the business characteristic data is greater than a preset business threshold, and whether a manual instruction has been received. If the second trigger condition is met, then the trigger condition is confirmed to be met.

[0008] In one or more embodiments, the beneficial effects of this solution are as follows: by setting the trigger priority: first trigger condition > second trigger condition, and introducing a dual verification mechanism, such as "greater than network threshold + early warning information", it is possible to avoid false triggering in non-emergency scenarios and ensure that the emergency settlement exemption mechanism is only activated in real emergency situations.

[0009] Furthermore, the emergency settlement exemption method according to one aspect of this disclosure also includes: In response to the emergency settlement exemption result, the exemption process is initiated by sending exemption instructions and user emergency roaming identifiers to each operator. The exemption instructions are used to instruct each operator to initiate the exemption process for the emergency event, and the user emergency roaming identifiers are used to identify emergency users within the coverage area.

[0010] In one or more embodiments, the beneficial effects of this solution are as follows: by synchronizing exemption instructions and user emergency roaming identifiers to various operators, operators can quickly settle accounts based on exemption instructions and user emergency roaming identifiers without going through multiple approval stages and manual intervention. This helps to solve the problems of slow response and cumbersome operation in traditional settlement processes. The maximum synchronization delay is 3 seconds, which greatly improves the emergency response speed.

[0011] Furthermore, the emergency settlement exemption method according to one aspect of this disclosure also includes: Establish cross-operator settlement exemption rules; the settlement exemption rules include at least one of the following: exemption targets, business scope, time period, and cost sharing.

[0012] In one or more embodiments, the beneficial effects of this solution are as follows: by jointly constructing unified settlement exemption rules with various operators, covering elements such as exemption targets, business scope, time period, and cost bearing, it is possible to avoid settlement disputes and management chaos caused by inconsistent rules, and enhance the consistency and enforceability of cross-operator settlement exemption rules.

[0013] Furthermore, the emergency settlement exemption method according to one aspect of this disclosure also includes: In response to the emergency settlement exemption result, the exemption process is initiated, and the exemption call details of each operator are obtained at preset time intervals. The exempted call detail records are encrypted; The encrypted exemption call detail records are uploaded to the consortium blockchain; the nodes of the consortium blockchain use the PBFT consensus mechanism for verification.

[0014] In one or more embodiments, the beneficial effects of this solution are as follows: by combining consortium blockchain technology with PBFT consensus mechanism and encryption algorithm to store and record exempted call detail records, it is possible to ensure that exempted call detail records cannot be tampered with and improve data credibility.

[0015] Furthermore, the emergency settlement exemption method according to one aspect of this disclosure also includes: According to a preset cycle, the exempted call records stored in the consortium blockchain are audited to obtain abnormal call records in the consortium blockchain; among them, the audit process is used to verify the completeness, compliance and timeliness of the exempted call records. Identify the operator to which the abnormal call detail record belongs and send a rectification notice to that operator.

[0016] In one or more embodiments, the beneficial effects of this solution are as follows: by auditing the exempted call records stored in the consortium blockchain, it is possible to check whether there are any non-compliant abnormal call records; it is also possible to verify the losses of each operator through auditing, provide certain compensation to the operators, reduce the operators' costs, form a closed-loop management of "trigger-exemption-audit-compensation", protect the interests of operators, and promote the efficient scheduling of emergency communication resources.

[0017] According to another aspect of this disclosure, an emergency settlement exemption device is provided, comprising: The instruction acquisition module is used to acquire regulatory instruction data, which is used to characterize the occurrence of emergency events and includes the coverage of the emergency events. The data acquisition module is used to acquire network data and business characteristic data within the coverage area based on regulatory instruction data. The network data is used to characterize the network status within the coverage area, and the business characteristic data is used to characterize the network behavior characteristics of users within the coverage area. The exemption identification module is used to obtain the emergency settlement exemption result based on regulatory instruction data, network data, and business characteristic data using a pre-trained emergency identification model. The emergency identification model is used to identify whether an emergency event triggers the conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether the exemption process should be initiated.

[0018] According to another aspect of this disclosure, a computer device is provided, including a memory, a processor, and a computer program stored in the memory, the processor executing the computer program to implement the method of one aspect above.

[0019] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the method of one aspect above.

[0020] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method of the above-described aspect.

[0021] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0022] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0023] Figure 1 This is a system architecture diagram illustrating an application of an emergency settlement exemption method according to an embodiment of this disclosure.

[0024] Figure 2 This is a flowchart illustrating an application example provided by an embodiment of this disclosure.

[0025] Figure 3 This is a flowchart illustrating an emergency settlement exemption method according to an embodiment of the present disclosure.

[0026] Figure 4 This is a schematic diagram of the structure of an emergency settlement exemption device according to an embodiment of the present disclosure.

[0027] Figure 5 This is a schematic diagram illustrating the structure of a computer device according to an embodiment of the present disclosure.

[0028] Figure 6 This is a schematic diagram illustrating a computer program product according to an embodiment of the present disclosure. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0030] 5G inter-network roaming refers to the temporary access to other operators' networks for communication in emergency scenarios such as earthquakes, floods, or extreme network failures when users cannot connect to their home operator's network. To address such public safety emergencies and provide emergency communication services to users in disaster areas, various operators can implement certain settlement exemption mechanisms for user roaming fees, allowing users to roam for free.

[0031] However, the relevant technologies still have the following problems: (1) The settlement exemption mechanism is complicated and slow to respond, requiring manual approval and multi-stage verification, which makes it impossible for users to obtain exemption quickly in emergency scenarios such as extreme disasters. When a disaster occurs, the settlement system cannot keep up with the emergency needs, and users may not be able to roam in time due to cost issues.

[0032] (2) In emergency scenarios such as extreme disasters, user identity information may be missing, network environment may be poor, and in addition, the settlement exemption rules between operators are inconsistent and resources are limited, which leads to delays in cross-network roaming authentication, difficulty in synchronizing settlement instructions, and insufficient credibility of call detail record evidence, thus affecting the real-time performance, availability and fairness of emergency communication.

[0033] The above description, with reference to the accompanying drawings, describes an emergency settlement exemption method, apparatus, device, medium, and product according to embodiments of the present disclosure. By automatically identifying exemption requirements in emergency scenarios, constructing cross-operator settlement exemption rules, synchronizing settlement exemption instructions, and ensuring the reliable storage of exemption call details, it can support emergency communication networks with mutual backup and interoperability among multiple operators, ensuring users' rapid access and free communication services in extreme situations of "circuit and network outages".

[0034] To facilitate understanding of this embodiment, a detailed description of the emergency settlement exemption method disclosed in this disclosure is provided first. The executing entity of the emergency settlement exemption method provided in this disclosure is generally a computer device with a certain computing capability. This computer device may include, for example, a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, vehicle-mounted device, wearable device, etc. In some possible implementations, this emergency settlement exemption method can be implemented by a processor calling computer-readable instructions stored in memory.

[0035] like Figure 1 The diagram shown is a system architecture diagram of the emergency settlement exemption method provided in this embodiment of the disclosure. It includes an emergency identification module 1, a rule management module 2, a collaborative synchronization module 3, a blockchain evidence storage module 4, and an audit compensation module 5. The emergency settlement exemption method of this embodiment can be applied to various emergency scenarios, such as natural disasters, public health emergencies, and stampedes at large events. For ease of explanation, this embodiment mainly uses natural disasters (such as earthquakes) as the emergency scenario. The following is a detailed description of each module: Emergency Identification Module 1: This module receives and parses regulatory instruction data, network data, and business characteristic data. It then uses a pre-trained emergency identification model to output the emergency settlement exemption result, i.e., to determine whether the triggering conditions for emergency settlement exemption are met.

[0036] The emergency identification model is a three-dimensional identification model built on "regulatory instruction data + network data + business characteristic data". The emergency identification model adopts a trigger priority mechanism, namely, regulatory instruction data > network data (first trigger condition) > business characteristic data (second trigger condition), and sets up a dual verification mechanism to prevent accidental triggering of emergency settlement exemption.

[0037] Regulatory directives can be issued by regulatory authorities and are in structured JSON format, containing, for example, the following fields: - emergency_event_id: A unique identifier for the emergency event; - start_time: Exemption effective date (ISO 8601 format); - end_time: Exemption end time (ISO 8601 format); - coverage_area: Geofencing coordinate set (WGS-84 coordinate system); - exempt_type: Exemption type (such as "natural disaster", "emergency" etc.).

[0038] The set of geofence coordinates represents the coverage area of ​​an emergency event. It should be noted that regulatory instruction data can be digitally signed and verified before being issued to ensure that the source of the instructions is legitimate and has not been tampered with.

[0039] Network data is collected in real time through the core network monitoring systems of various operators. Specific metrics include base station outage rate, transmission interruption rate, and the number of core network failures. The collection frequency can be selected according to actual needs, such as once per minute. A sliding window algorithm is used to calculate the average value over a 5-minute period, followed by normalization. The formula is as follows: Normalized Value =Current Value -Min Value / Max Value -Min Value Among them, Min Value and Max Value These are the minimum and maximum values ​​from historical network data, used to eliminate the impact of differences in network size across different regions.

[0040] Business characteristic data is obtained through the business analysis systems of various operators, including concurrent users roaming across different networks and emergency call frequency. The data collection cycle can be selected according to actual needs, such as once per hour. Time series analysis is used to extract trend features, and Z-score standardization is applied, as shown in the following formula:

[0041] in, The current value of the business characteristic data. The mean, The standard deviation is used to determine the second trigger condition.

[0042] Specifically, the process for identifying triggering conditions includes: 1) Confirm receipt of regulatory instruction data, including emergency event ID, exemption period, coverage area, etc., and initiate the identification process of the emergency identification module.

[0043] 2) Determine whether the first triggering condition is met: whether the network data is greater than the preset network threshold, and whether the coverage area warning information is received.

[0044] Taking the base station outage rate, transmission interruption rate and core network failure number in network data as examples, if the base station outage rate is ≥30%, or the transmission interruption rate is ≥20%, or the number of core network failures is ≥1, and this lasts for 5 minutes, and disaster warning information has been issued in the area where the emergency event occurs, then the first triggering condition is met, and the triggering condition for emergency settlement exemption can be considered to be met.

[0045] 3) If the first triggering condition is not met, determine whether the second triggering condition is met: whether the business characteristic data is greater than the preset business threshold, and whether a manual instruction has been received; Taking the concurrent users of roaming across different networks and the frequency of emergency calls in the business characteristic data as an example, if the concurrent users of roaming across different networks are ≥40%, the frequency of emergency calls is ≥300 times / hour, and lasts for 10 minutes, and at the same time a manual instruction is received after manual confirmation by the regulatory authorities, then the second triggering condition is met, and it can be considered that the triggering condition for emergency settlement exemption is met.

[0046] In summary, the triggering priority is: regulatory instruction data > first triggering condition > second triggering condition, where regulatory instruction data is a necessary condition, and either the first or second triggering condition can be satisfied.

[0047] Rule Management Module 2: Used to store and synchronize unified settlement exemption rules across operators, as shown in Table 1, which is a description table of settlement exemption rules: Table 1

[0048] It should be noted that the elements, contents, and descriptions listed in Table 1 are all exemplary, and specific rules can be set according to actual needs. Optionally, the settlement exemption rules are stored in XML format, supporting version control and dynamic updates to ensure the consistency and enforceability of the rules.

[0049] Collaborative Synchronization Module 3: Used to synchronize exemption instructions and user emergency roaming identifiers to various operators in real time via an encrypted channel.

[0050] If the emergency settlement exemption result output by the emergency identification module 1 indicates that the exemption process should be initiated, it means that the emergency event has met the triggering conditions. At this time, exemption instructions and user emergency roaming identifiers can be issued to major operators. The user emergency roaming identifier is used to identify emergency users within the coverage area of ​​the emergency event. Each operator can quickly identify emergency users based on the user emergency roaming identifier.

[0051] Specifically, data can be synchronized to the operator's Unified Data Management System (UDM), Billing System, and Authentication Management Function (AMF), with synchronization latency controlled within 3 seconds. The TLS 1.3 protocol is used to ensure data transmission security, guaranteeing accurate identification of cross-network emergency users. The user emergency roaming identifier format is "IMSI-Emergency Event ID-EXEMPT," generated by the home operator's UDM and synchronized to the operator's UDM via I-NRF, ensuring accurate identification of cross-network users.

[0052] The user emergency roaming identifier, generated by the home operator and synchronized to the roaming operator via I-NRF, is in the format of "IMSI-Emergency Event ID-EXEMPT". This enables accurate identification of cross-network users, avoids commercial roaming users from being mistakenly included in the exemption scope, and improves the fairness and accuracy of the settlement exemption mechanism.

[0053] Blockchain Evidence Module 4: Used to upload exempted call records to the consortium blockchain for evidence storage, and based on the PBFT consensus mechanism, it ensures that the exempted call records cannot be tampered with.

[0054] Among them, exempted call detail records (CDRs) are those that meet the settlement exemption rules under the triggering conditions of emergency settlement exemption. The number of nodes in the consortium blockchain is ≥3, the upload latency is ≤1 second, and the exempted CDRs adopt an encryption mechanism combining AES-256 symmetric encryption and RSA-2048 asymmetric signature to ensure data security.

[0055] The process for uploading exempted call detail records includes: 1) Collect an exemption call detail record (CDR) once at a preset time interval (e.g., 10 seconds) through the operator's billing system; For example, the fields for exempted call detail records include: - bill_id: Unique identifier for call detail records; - IMSI: International Mobile Subscriber Identity; - msisdn: User's mobile phone number; - service_type: Service type (voice / SMS / data); - duration / flow / count: Business duration / flow / number of transactions; - in_operator / out_operator: Inbound / outbound operator; - access_time / disconnect_time: Access / disconnect time; - Signature: RSA-2048 asymmetric signature; - timestamp: timestamp (ISO 8601 format).

[0056] 2) Encrypt the exempted call detail records (CDRs) using AES-256; 3) Generate an RSA-2048 digital signature; 4) Upload the encrypted exemption call detail record to the consortium blockchain; 5) The nodes of the consortium blockchain use the PBFT consensus mechanism for verification, and the upload is completed after confirmation by three or more nodes.

[0057] Audit Compensation Module 5: Used to audit exempted call detail records stored on the consortium blockchain, check for any abnormal call detail records, and provide cost compensation to operators.

[0058] The specific audit process is as follows: 1) Retrieve all exempted call detail records from the consortium blockchain according to a preset period (e.g., daily); 2) Verify whether the completeness, compliance, and timeliness of each exempted call detail record meet the conditions, for example: Completeness: Deviation rate ≤1%; Compliance: No exemptions will be granted for user call detail records; Timeliness: Upload latency ≤ 10 seconds; 3) Generate the "Emergency Settlement Exemption Audit Report"; 4) If abnormal call records are found, a rectification notice shall be sent to the operator to which the abnormal call records belong, requiring rectification to be completed within 24 hours.

[0059] In addition, major operators can calculate their own exemption costs based on the "Emergency Settlement Exemption Audit Report," and then relevant departments can compensate major operators for their costs, forming a closed-loop management mechanism of "trigger-exemption-audit-compensation" to achieve efficient scheduling and reasonable compensation of emergency communication resources.

[0060] Based on the above embodiments, this embodiment provides an application example, such as... Figure 2 The flowchart shown is for an application example, including S201~S204: S201: Emergency Identification and Exemption Triggering.

[0061] Suppose an earthquake occurs in a province, and the relevant provincial department issues a regulatory instruction with the following content: - emergency_event_id: "E20240901-001"; - start_time: "2024-09-01T10:00:00Z"; - end_time: "2024-09-02T12:00:00Z"; - coverage_area: [[116.4074, 39.9042], [116.4174, 39.9142]]; - exempt_type: "natural disaster".

[0062] The triggering conditions for settlement exemption are as follows: 1) Regulatory instruction triggered: Confirm that regulatory instruction data has been received and start the identification process of the emergency identification module.

[0063] 2) Network status trigger: The base station outage rate in the coverage area is ≥30%, or the transmission interruption rate is ≥20%, or the number of core network failures is ≥1, and this lasts for 5 minutes; at the same time, disaster warning information has been issued for the area.

[0064] 3) Business characteristic trigger: The concurrent number of users roaming across different networks within the coverage area is ≥40% and the frequency of emergency calls is ≥300 times / hour, lasting for 10 minutes; at the same time, manual instructions issued by relevant departments are received.

[0065] The emergency identification module was triggered based on regulatory instructions. Simultaneously, it was detected that the base station outage rate in the area reached 35%, and a disaster warning had been issued for the area, meeting the network status trigger conditions and automatically initiating the exemption process.

[0066] S202: Synchronization Exemption Instruction and User Emergency Roaming Identifier.

[0067] The exemption instruction and the user's emergency roaming identifier ("IMSI-EXEMPT-E20240901-001") are synchronized to each operator's UDM, billing system and AMF through an encrypted channel, with a synchronization delay of ≤3 seconds, to ensure that the user is accurately identified across networks.

[0068] After receiving the exemption instruction and the user's emergency roaming identifier, each operator will grant a settlement exemption according to pre-built settlement exemption rules, which include: 1) Exemption targets: emergency users for roaming in / out, excluding commercial roaming users (who can be verified by both home location and access area). 2) Exempted services: Required exempted services (e.g., emergency calls, regular voice calls, emergency text messages), and optional exempted services (determined based on regular data or designated by relevant departments). 3) Exemption period: The effective time is the time when the instruction is issued, and the end time is 24 hours after the disaster ends. An additional 1-hour transition period may be added depending on the actual situation. 4) Cost allocation: Roaming-in users are covered by the roaming-in operator, while roaming-out users are covered by the home operator.

[0069] S203: Consortium Blockchain Evidence Storage and Auditing.

[0070] The operator's billing system collects exempt call detail records (CDRs) every 10 seconds and uploads them to the consortium blockchain. The consortium blockchain nodes use the PBFT consensus mechanism for verification; the transaction is completed after confirmation by at least 3 nodes, with a transaction latency of ≤1 second.

[0071] Call detail record (CDR) data employs an encryption mechanism combining AES-256 symmetric encryption and RSA-2048 asymmetric signature to ensure data security.

[0072] Every day, all exempted call detail records (CDRs) are retrieved from the consortium blockchain to verify their completeness, compliance, and timeliness, generating an "Emergency Settlement Exemption Audit Report." If any abnormal CDRs are found, a rectification notice is issued to the relevant operator, requiring rectification to be completed within 24 hours.

[0073] S204: Cost recovery and closed-loop management.

[0074] Operators can calculate exemption costs based on the exempted call detail records (CDRs) from the consortium blockchain and submit subsidy applications. The subsidy center's review time is ≤5 working days, and subsidies are disbursed within 10 working days after approval, forming a closed-loop management mechanism of "trigger-exemption-audit-compensation".

[0075] Experimental results show that, compared with traditional solutions, this application example reduces the triggering delay of emergency settlement exemption from 180 minutes to about 2 minutes, the exemption activation delay from 6 hours to 0.5 hours, the settlement dispute rate from 35% to 2%, the user complaint rate from 28% to 3%, and the operator's enthusiasm from 40% to 89%.

[0076] Based on the above embodiments, this embodiment also provides an emergency settlement exemption method, such as... Figure 3 The flowchart shown is for the emergency settlement exemption method, including S301-S303: S301: Obtain regulatory instruction data.

[0077] Among them, regulatory instruction data is used to characterize the occurrence of emergency events, and the regulatory instruction data includes the coverage of emergency events.

[0078] S302: Based on regulatory instruction data, obtain network data and business characteristic data within the coverage area.

[0079] Among them, network data is used to characterize the network status within the coverage area, and service characteristic data is used to characterize the network behavior characteristics of users within the coverage area.

[0080] S303: Based on regulatory instruction data, network data, and business characteristic data, and using a pre-trained emergency identification model, obtain emergency settlement exemption results.

[0081] Among them, the emergency identification model is used to identify whether an emergency event meets the triggering conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether to initiate the exemption process.

[0082] In one or more embodiments, the process for identifying triggering conditions includes: The system determines whether an emergency event meets a first trigger condition based on network data. The first trigger condition includes: determining whether the network data exceeds a preset network threshold and whether a warning message within the coverage area has been received. If the first trigger condition is met, it is confirmed that the trigger condition is met. If the first trigger condition is not met, the system determines whether the emergency event meets a second trigger condition based on business characteristic data. The second trigger condition includes: determining whether the business characteristic data exceeds a preset business threshold and whether a manual instruction has been received. If the second trigger condition is met, it is confirmed that the trigger condition is met.

[0083] The specific triggering conditions are as follows: 1) Confirm receipt of regulatory instruction data, including emergency event ID, exemption period, coverage area, etc., and initiate the identification process of the emergency identification module.

[0084] 2) Determine whether the first triggering condition is met: the base station outage rate is ≥30%, or the transmission interruption rate is ≥20%, or the number of core network failures is ≥1, and this lasts for 5 minutes, while disaster warning information has been issued for the area where the emergency event occurs; 3) If the first triggering condition is not met, determine whether the second triggering condition is met: the concurrent user volume of roaming users on different networks is ≥40%, the frequency of emergency calls is ≥300 times / hour and lasts for 10 minutes, and a manual instruction is received at the same time.

[0085] By setting trigger priorities (first trigger condition > second trigger condition) and introducing a dual verification mechanism, such as "threshold met + disaster early warning information", we can avoid accidental triggering in non-emergency scenarios and ensure that the emergency settlement exemption mechanism is only activated in real emergency situations.

[0086] In one or more embodiments, the method further includes: in response to the emergency settlement exemption result characterization initiating the exemption process, sending exemption instructions and user emergency roaming identifiers to each operator; the exemption instructions are used to instruct each operator to initiate the exemption process for the emergency event, and the user emergency roaming identifiers are used to identify emergency users within the coverage area.

[0087] Specifically, the user emergency roaming identifier format is "IMSI-Emergency Event ID-EXEMPT", which is generated by the home operator's UDM and synchronized to the operator's UDM via I-NRF to ensure accurate identification of cross-network users. By using the "IMSI-Emergency Event ID-EXEMPT" format for the user emergency roaming identifier, generated by the home operator and synchronized to the roaming operator via I-NRF, accurate identification of cross-network users is achieved, preventing commercial roaming users from being mistakenly included in the exemption scope and improving the fairness and accuracy of the settlement exemption mechanism.

[0088] By synchronizing exemption instructions and user emergency roaming identifiers with various operators, operators can quickly settle accounts based on the exemption instructions and user emergency roaming identifiers without going through multiple approval stages and manual intervention. This helps to solve the problems of slow response and cumbersome operation in the traditional settlement process. The synchronization delay is a maximum of 3 seconds, which greatly improves the emergency response speed.

[0089] In one or more embodiments, the method further includes: constructing cross-operator settlement exemption rules; the settlement exemption rules include at least one of the following: exemption targets, business scope, time period, and cost liability.

[0090] For details of the settlement exemption rules, please refer to Table 1. By jointly building a unified settlement exemption rule with various operators, covering elements such as exemption targets, business scope, time period, and cost sharing, we can avoid settlement disputes and management chaos caused by inconsistent rules and enhance the consistency and enforceability of cross-operator settlement exemption rules.

[0091] In one or more embodiments, the method further includes: initiating an exemption process in response to the emergency settlement exemption result representation; obtaining the exemption call detail records (CDRs) of each operator at preset time intervals; encrypting the exemption CDRs; uploading the encrypted exemption CDRs to the consortium blockchain; and verifying the CDRs using the PBFT consensus mechanism.

[0092] Specifically, the process for uploading exempted call detail records includes: 1) Collect an exemption call detail record (CDR) once at a preset time interval (e.g., 10 seconds) through the operator's billing system; For example, the fields for exempted call detail records include: - bill_id: Unique identifier for call detail records; - IMSI: International Mobile Subscriber Identity; - msisdn: User's mobile phone number; - service_type: Service type (voice / SMS / data); - duration / flow / count: Business duration / flow / number of transactions; - in_operator / out_operator: Inbound / outbound operator; - access_time / disconnect_time: Access / disconnect time; - Signature: RSA-2048 asymmetric signature; - timestamp: timestamp (ISO 8601 format).

[0093] 2) Encrypt the exempted call detail records (CDRs) using AES-256; 3) Generate an RSA-2048 digital signature; 4) Upload the encrypted exemption call detail record to the consortium blockchain; 5) The nodes of the consortium blockchain use the PBFT consensus mechanism for verification, and the upload is completed after confirmation by three or more nodes.

[0094] By combining consortium blockchain technology with the PBFT consensus mechanism and encryption algorithm, exempted call records can be stored and recorded, ensuring that the exempted call records cannot be tampered with and improving data credibility.

[0095] In one or more embodiments, the method further includes: auditing the exempted call records stored in the consortium blockchain according to a preset period to obtain abnormal call records in the consortium blockchain; wherein, the auditing process is used to verify the integrity, compliance and timeliness of the exempted call records; confirming the operator to which the abnormal call records belong, and sending a rectification notice to the operator to which the abnormal call records belong.

[0096] Specifically, the audit process is as follows: 1) Retrieve all exempted call detail records from the consortium blockchain according to a preset period (e.g., daily); 2) Verify whether the completeness, compliance, and timeliness of each exempted call detail record meet the conditions, for example: Completeness: Deviation rate ≤1%; Compliance: No exemptions will be granted for user call detail records; Timeliness: Upload latency ≤ 10 seconds; 3) Generate the "Emergency Settlement Exemption Audit Report"; 4) If abnormal call records are found, a rectification notice shall be sent to the operator to which the abnormal call records belong, requiring rectification to be completed within 24 hours.

[0097] Auditing the exempted call records stored in the consortium blockchain can check for non-compliant and abnormal call records. It can also verify the losses of each operator through auditing, provide certain compensation to the operators, reduce the operators' costs, form a closed-loop management of "trigger-exemption-audit-compensation", protect the interests of operators, and promote the efficient scheduling of emergency communication resources.

[0098] According to another aspect of the embodiments of this disclosure, an emergency settlement exemption device is provided, such as... Figure 4 As shown, the device includes: The instruction acquisition module 401 is used to acquire regulatory instruction data, which is used to characterize the occurrence of an emergency event and includes the coverage of the emergency event. Data acquisition module 402 is used to acquire network data and service characteristic data within the coverage area based on regulatory instruction data. The network data is used to characterize the network status within the coverage area, and the service characteristic data is used to characterize the network behavior characteristics of users within the coverage area. The exemption identification module 403 is used to obtain the emergency settlement exemption result based on regulatory instruction data, network data and business characteristic data using a pre-trained emergency identification model; wherein, the emergency identification model is used to identify whether the emergency event triggers the triggering conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether the exemption process is initiated.

[0099] The emergency settlement exemption device is also used to: determine whether an emergency event meets a first triggering condition based on network data; wherein, the first triggering condition includes: determining whether the network data is greater than a preset network threshold, and whether a warning message from the coverage area has been received; If the first trigger condition is met, then the trigger condition is confirmed to be met. If the first triggering condition is not met, the emergency event is then judged to meet the second triggering condition based on the business characteristic data. The second triggering condition includes: determining whether the business characteristic data is greater than a preset business threshold, and whether a manual instruction has been received. If the second trigger condition is met, then the trigger condition is confirmed to be met.

[0100] The emergency settlement exemption device is also used to: initiate the exemption process in response to the emergency settlement exemption result characterization, and send exemption instructions and user emergency roaming identifiers to each operator; the exemption instructions are used to instruct each operator to initiate the exemption process for the emergency event, and the user emergency roaming identifiers are used to identify emergency users within the coverage area.

[0101] The emergency settlement exemption device is also used to: initiate the exemption process in response to the emergency settlement exemption result representation; obtain the exemption call details of each operator at preset time intervals; encrypt the exemption call details; upload the encrypted exemption call details to the consortium blockchain; and verify the exemption call details using the PBFT consensus mechanism.

[0102] The emergency settlement exemption device is also used to: audit the exempted call records stored in the consortium blockchain according to a preset cycle, and obtain abnormal call records in the consortium blockchain; wherein, the audit process is used to verify the completeness, compliance and timeliness of the exempted call records; confirm the operator to which the abnormal call records belong, and send a rectification notice to the operator to which the belong belongs.

[0103] The emergency settlement exemption device and the emergency settlement exemption method provided in this disclosure are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0104] This disclosure also provides a computer device for performing the above-described emergency settlement exemption method. Please refer to... Figure 5 It illustrates a schematic diagram of a computer device provided by some embodiments of this disclosure. For example... Figure 5 As shown, the computer device 5 includes: a processor 500, a memory 501, a bus 502, and a communication interface 503. The processor 500, the communication interface 503, and the memory 501 are connected via the bus 502. The memory 501 stores a computer program that can run on the processor 500. When the processor 500 runs the computer program, it executes the emergency settlement exemption method provided in any of the foregoing embodiments of this disclosure.

[0105] The memory 501 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this device network element and at least one other network element is achieved through at least one communication interface 503 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0106] Bus 502 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 501 is used to store programs. After receiving an execution instruction, the processor 500 executes the program. The emergency settlement exemption method disclosed in any of the foregoing embodiments of this disclosure can be applied to the processor 500, or implemented by the processor 500.

[0107] The processor 500 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 500 or by instructions in software form. The processor 500 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPTA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this disclosure. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this disclosure can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 501. The processor 500 reads the information in memory 501 and, in conjunction with its hardware, completes the steps of the above method.

[0108] The computer device provided in this disclosure and the emergency settlement exemption method provided in this disclosure are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0109] This disclosure also provides a computer-readable storage medium corresponding to the emergency settlement exemption method provided in the foregoing embodiments. The computer-readable storage medium is an optical disc, on which a computer program (i.e., a computer program product) is stored. When the computer program is run by a processor, it executes the emergency settlement exemption method provided in any of the foregoing embodiments.

[0110] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0111] The computer-readable storage medium provided in the above embodiments of this disclosure and the emergency settlement exemption method provided in the embodiments of this disclosure are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0112] This disclosure also provides a computer program product; please refer to [reference needed]. Figure 6 The computer program product 600 carries program code, namely computer program 601. The instructions included in the computer program 601 can be used to execute the steps of the emergency settlement exemption method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0113] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0114] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0115] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0116] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0117] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.

[0118] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0119] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0120] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. An emergency settlement exemption method, characterized in that, include: Acquire regulatory instruction data, which is used to characterize the occurrence of an emergency event, and the regulatory instruction data includes the coverage of the emergency event; Based on the regulatory instruction data, network data and service characteristic data within the coverage area are obtained. The network data is used to characterize the network status within the coverage area, and the service characteristic data is used to characterize the network behavior characteristics of users within the coverage area. Based on the regulatory instruction data, the network data, and the business characteristic data, an emergency settlement exemption result is obtained using a pre-trained emergency identification model; wherein, the emergency identification model is used to identify whether the emergency event meets the triggering conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether the exemption process is initiated.

2. The emergency settlement exemption method as described in claim 1, characterized in that, The process for identifying the triggering conditions includes: The network data is used to determine whether the emergency event meets the first triggering condition; wherein the first triggering condition includes: determining whether the network data is greater than a preset network threshold, and whether the warning information of the coverage area is received; If the first triggering condition is met, then it is confirmed that the triggering condition is met; If the first triggering condition is not met, then the emergency event is determined to meet the second triggering condition based on the business characteristic data; wherein, the second triggering condition includes: determining whether the business characteristic data is greater than a preset business threshold, and whether a manual instruction has been received; If the second triggering condition is met, then it is confirmed that the triggering condition is met.

3. The emergency settlement exemption method as described in claim 1, characterized in that, Also includes: In response to the emergency settlement exemption result indicating the start of the exemption process, exemption instructions and user emergency roaming identifiers are sent to each operator; The exemption instruction is used to instruct each of the operators to initiate an exemption process for the emergency event, and the user emergency roaming identifier is used to identify emergency users within the coverage area.

4. The emergency settlement exemption method as described in claim 1, characterized in that, Also includes: Establish cross-carrier settlement exemption rules; The settlement exemption rules include at least one of the following: exemption targets, business scope, time period, and cost liability.

5. The emergency settlement exemption method as described in claim 1, characterized in that, Also includes: In response to the emergency settlement exemption result, the exemption process is initiated, and the exemption call details of each operator are obtained at preset time intervals. The exempted call detail records are encrypted; The encrypted exemption call detail record is uploaded to the consortium blockchain; the nodes of the consortium blockchain use the PBFT consensus mechanism for verification.

6. The emergency settlement exemption method as described in claim 5, characterized in that, Also includes: According to a preset cycle, the exempted call records stored in the consortium blockchain are audited to obtain abnormal call records in the consortium blockchain; wherein, the audit process is used to verify the completeness, compliance and timeliness of the exempted call records; Identify the operator to which the abnormal call detail record belongs and send a rectification notice to that operator.

7. An emergency settlement exemption device, characterized in that, include: The instruction acquisition module is used to acquire regulatory instruction data, which is used to characterize the occurrence of an emergency event and includes the coverage of the emergency event. The data acquisition module is used to acquire network data and service characteristic data within the coverage area based on the regulatory instruction data. The network data is used to characterize the network status within the coverage area, and the service characteristic data is used to characterize the network behavior characteristics of users within the coverage area. The exemption identification module is used to obtain an emergency settlement exemption result based on the regulatory instruction data, the network data, and the business characteristic data using a pre-trained emergency identification model; wherein, the emergency identification model is used to identify whether the emergency event triggers the triggering conditions for emergency settlement exemption, and the emergency settlement exemption result is used to characterize whether the exemption process is initiated.

8. A computer embedded device, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 6.

Images