CN115086895B - Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket - Google Patents
Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket Download PDFInfo
- Publication number
- CN115086895B CN115086895B CN202110266652.XA CN202110266652A CN115086895B CN 115086895 B CN115086895 B CN 115086895B CN 202110266652 A CN202110266652 A CN 202110266652A CN 115086895 B CN115086895 B CN 115086895B
- Authority
- CN
- China
- Prior art keywords
- province
- abnormal
- visiting
- ticket
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000002159 abnormal effect Effects 0.000 title claims abstract description 135
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000004044 response Effects 0.000 claims abstract description 81
- 238000013507 mapping Methods 0.000 claims abstract description 19
- 239000000284 extract Substances 0.000 claims abstract description 6
- 230000005856 abnormality Effects 0.000 claims abstract description 3
- 230000006870 function Effects 0.000 description 11
- 230000015654 memory Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000010267 cellular communication Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a method and a system for distinguishing an abnormal local ticket from an abnormal roaming ticket. The method comprises the following steps: the visiting province CG receives a charging message request carrying user SUPI and stores province identification of the visiting province; the visiting province CG transmits the charging information request to the visiting province SCP, and stores the number section, province identification and mapping between each province; the visiting province SCP matches the user SUPI with the number section of each province to determine the user attribution province and the province identification of the province; the visiting province SCP transmits a charging message request to the user home province CHF; under the condition of network abnormality, the visiting province SCP returns a message response carrying an abnormal response code to the visiting province CG, and a province identifier of the user attributing province is added in the message response; the visiting province CG recognizes the abnormal response code to judge that the message response is abnormal message response, and generates an abnormal ticket; the visiting province CG extracts province identification from the abnormal message response and matches with the province identification of the visiting province so as to divide the abnormal ticket into an abnormal local province ticket or an abnormal roaming ticket.
Description
Technical Field
The present disclosure relates generally to the field of mobile internet operations support, and more particularly to handling of abnormal ticket for mobile users.
Background
In the current 5G independent networking (SA) ticket-sorting directory scheme, a Session Management Function (SMF) of a visiting province sends a charging message request to a visiting province Charging Gateway (CG), and the visiting province CG forwards the charging message request to a user home province charging function (CHF) after receiving the charging message request. The user home province CHF adds its own IP address information to the Location (Location) field of the message response after receiving the charging message request, and returns the message response to the visiting province CG. After receiving the message response from the user home province CHF, the visiting province CG generates a ticket according to the charging message request, extracts the IP address in the position field of the message response and matches the IP address with the stored visiting province CHF. If the IP address of the user belonging province CHF is the same as the IP address of the visiting province CHF, the matching is successful, and the generated ticket is put into the ticket catalog; otherwise, the generated ticket is put into the roaming ticket directory. Compared with the scheme of dividing the charging information into the charging information of the user in the current province or the charging information of the roaming user according to the user permanent identifier (SUPI) of the user in the charging information in the prior art, the 5G SA bill division directory scheme reduces the extra CG CPU performance loss caused by the need of matching the charging information with the number segments of each province in the whole country one by one.
However, in a network abnormal scenario, for example, if a packet loss occurs during a transmission process or a load of a CHF of a user home province is too high, and a message cannot be processed, a visited province CG in the current 5G SA ticket directory scheme cannot receive a message response from the CHF of the user home province, where a location field carries an IP address of the visited province, so that only an abnormal ticket can be generated, and it is not possible to distinguish whether a charging message is a charging message of the user of the province or a charging message of a roaming user, so that the abnormal ticket cannot be stored in the current province ticket directory or the roaming ticket directory. It should be noted that, the abnormal charging process and the abnormal settlement process for processing the abnormal local provincial ticket and the abnormal roaming ticket are different, wherein the abnormal charging process is to collect the abnormal local provincial ticket for charging by the visiting provincial charging center, and the abnormal settlement process is to collect the abnormal roaming ticket for roaming settlement by the group settlement center. Because the current 5G SA bill division directory scheme can not store the abnormal bill into the provincial bill directory and the roaming bill directory, the charging side can execute an abnormal charging flow or an abnormal settlement flow only by adopting additional sorting operation on the abnormal bill, and the charging and settlement efficiency is reduced.
To overcome the above-described drawbacks, the present disclosure provides an innovative method and system for distinguishing between an abnormal local ticket and an abnormal roaming ticket.
Disclosure of Invention
The following presents a simplified summary of the disclosure in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this summary is not an exhaustive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. Its purpose is to present some concepts related to the disclosure in a simplified form as a prelude to the more detailed description that is presented later.
According to one aspect of the present disclosure, there is provided a method of distinguishing between an abnormal local ticket and an abnormal roaming ticket, including the steps of: the visiting province CG receives a charging message request carrying a user SUPI, wherein a province identifier of the visiting province is stored in the visiting province CG; the visiting province CG transmits the charging information request to the visiting province SCP, wherein the visiting province SCP stores the number section of each province, the province identifier of each province and the mapping between the number section of each province and the province identifier; the visiting province SCP matches the user SUPI with the number segment of each province to determine the province identity of the user attribution province and the user attribution province; the visiting province SCP transmits a charging message request to the user home province CHF; under the condition that the network abnormal visiting province SCP does not receive the message response carrying the IP address information of the home province CHF from the user home province CHF, the visiting province SCP sends the message response carrying the abnormal response code to the visiting province CG and adds the province identifier of the user home province in the message response; the visiting province CG judges the message response to be abnormal message response by identifying the abnormal response code, and generates an abnormal ticket according to the charging message request; and the visiting province CG extracts the province identifier of the user attribution province from the abnormal message response and matches the province identifier with the stored province identifier of the visiting province so as to divide the abnormal ticket into an abnormal local province ticket or an abnormal roaming ticket.
According to another aspect of the present disclosure, there is provided a system for distinguishing an abnormal local ticket from an abnormal roaming ticket, including a visited province CG for receiving and forwarding a charging message request carrying a user SUPI to an SCP of the visited province, the visited province CG including a province identity storage module for storing a province identity of the visited province; a ticket determining module, configured to receive a response message from the SCP of the visited province, and configured to: under the condition that the message response is identified to comprise the abnormal response code, judging the message response as abnormal message response, and generating an abnormal ticket according to the charging message request; extracting the province mark of the user attribution province from the abnormal message response and matching the province mark with the province mark of the visiting province so as to divide the abnormal ticket into an abnormal local province ticket or an abnormal roaming ticket; the system also comprises a visiting province SCP which is connected with the visiting province CG, the visiting province CHF and SCPs of other provinces, and comprises a mapping storage module which is used for storing the number section of each province, the province identifier of each province and the mapping between the number section of each province and the province identifier; a matching module configured to: matching a user SUPI in a charging message request received from a visiting province CG with a number segment of each province stored in a mapping storage module to determine a user attribution province and a province identification of the user attribution province; and under the condition that the network abnormality does not receive the message response carrying the IP address information returned by the user home province CHF, sending the message response carrying the abnormal response code to the visiting province CG and adding the province identifier of the user home province in the message response.
According to yet another aspect of the present disclosure, there is provided a computer-readable storage medium comprising computer-executable instructions which, when executed by one or more processors, cause the one or more processors to perform a method according to the above aspects of the present disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 illustrates an overall architecture diagram of a system for distinguishing between an abnormal local ticket and an abnormal roaming ticket in accordance with an embodiment of the present disclosure;
FIG. 2 illustrates a flow chart of a method of distinguishing between an abnormal local ticket and an abnormal roaming ticket in accordance with an embodiment of the present disclosure; and
FIG. 3 illustrates an exemplary configuration of a computing device in which embodiments according to the present disclosure may be implemented.
Detailed Description
The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various example embodiments of the disclosure. The following description includes various details to aid in understanding, but these are to be considered merely examples and are not intended to limit the disclosure, which is defined by the appended claims and their equivalents. The words and phrases used in the following description are only intended to provide a clear and consistent understanding of the present disclosure. In addition, descriptions of well-known structures, functions and configurations may be omitted for clarity and conciseness. Those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the present disclosure.
Fig. 1 illustrates an overall architecture diagram of a system for distinguishing between an abnormal local ticket and an abnormal roaming ticket according to an embodiment of the present disclosure.
The system for distinguishing between an abnormal home ticket and an abnormal roaming ticket for each province throughout the country (e.g., province a and province B as shown in fig. 1) includes a Session Management Function (SMF) 100, a billing gateway (CG) 200, a service control point network element (SCP) 300, and a billing function (CHF) 400, which communicate with each other, wherein the SCP300 of each province is connected with the SCPs 300 of the other provinces. Communication between network elements of the 5G SA core network adopts service interface communication, and follows HTTP/2 protocol stack.
In this embodiment, the a-province is set as the visited province, and after receiving a charging message request from the visited province SMF 100, the visited province CG 200 forwards the charging message request to the visited province SCP300. The visited province CG 200 includes a province identity storage module 201, configured to store a province identity of a visited province.
The visited SCP300 comprises a mapping storage module 301 and a matching module 302. The mapping storage module 301 is configured to store a number segment of each province, a province identifier of each province, and a mapping between the number segment of each province and the province identifier. The matching module 302 is configured to match a user SUPI carried in the received charging message request with a number segment of each province stored in the mapping storage module 301, determine that the province is a user home province if the user SUPI is the same as a part of the number segment of one province, and determine a province identifier of the user home province according to a mapping between the number segment of each province and the province identifier.
Under a normal network scenario, if the visited province SCP300 determines that the user home province is the visited province itself, the charging message request is directly forwarded to the CHF400 of the user home province (i.e., the visited province itself). If the visiting province SCP300 determines that the user home province is not the visiting province itself, the charging message request is forwarded to the user home province SCP300 according to the matching result of the matching module 302, which is shown as B province in fig. 1. The matching module 302 of the user home province SCP300 matches the user SUPI with the number segment of each province stored in the mapping storage module 301, and if the user SUPI is the same as a part of the number segments of the user home province, the matching is successful, and the user home province SCP300 forwards the charging message request to the user home province CHF400.
The user home province CHF400 is configured to add its own IP address information to the location field of the message response after receiving the charging message request, and to return the message response to the visiting province SCP300.
The visited province CG 200 also includes a ticket determination module 202. Under a network normal scenario, the visited province CG 200 receives a message response from the visited province SCP300 carrying the IP address information of the user home province CHF400. The ticket determining module 202 is configured to receive a message response from the visiting province SCP300, and compare the IP address of the user home province CHF400 with the IP address of the visiting province CHF, and if the IP address of the user home province CHF is the same as the IP address of the visiting province CHF, determine the generated ticket as the current province ticket; otherwise, the generated ticket is determined as the roaming ticket.
However, in the case of network anomalies, for example, the charging message request is lost on the way from the visiting province SCP300 to the user home province CHF400, or the user home province CHF400 cannot process the charging message request due to too high a load, the visiting province SCP300 does not receive a message response carrying its IP address information from the user home province CHF400. The visiting province SCP300 then sends a message response carrying the abnormal response code to the visiting province CG 200 and adds the province identity of the user's home province determined by the matching module 302 in the location field of the message response.
The ticket determining module 202 of the visited province CG 200 is configured to receive a message response from the visited province SCP300, determine that the message response is an abnormal message response when it is identified that the message response includes an abnormal response code, and generate an abnormal ticket according to the charging message request. The ticket determination module 202 extracts the province identity of the province to which the user belongs in the location field of the message response and matches the province identity of the visited province stored in the province identity storage module 201. If the province identification of the user belonging province is the same as the province identification of the stored visiting province, the generated abnormal ticket is judged to be the abnormal local ticket and is stored in the abnormal local ticket catalog. If the province identification of the user belonging province is different from the stored visiting province identification, the generated abnormal ticket is judged to be the abnormal roaming ticket and is stored in the abnormal roaming ticket directory.
Fig. 2 illustrates a flow chart of a method of distinguishing between an abnormal local ticket and an abnormal roaming ticket in accordance with an embodiment of the present disclosure.
In step S201, the visited province CG receives a charging message request carrying a user SUPI from the visited province SMF, where a province identifier of the visited province is stored in the visited province CG.
In step S202, the visited province CG forwards the charging message request to the visited province SCP, where the number segment of each province, the province identity of each province, and the mapping between the number segment of each province and the province identity are stored in the visited province SCP.
In step S203, the visiting province SCP matches the user SUPI with the number segment of each province to determine the province identity of the user home province and the user home province.
Specifically, the visiting province SCP compares the user SUPI with the number segment of each province. If the SUPI of the user is the same as a part of the number segment of one of the provinces, determining the province as the user attribution province; and determining the province identifier of the province to which the user belongs according to the mapping between the number segment of each province and the province identifier.
In step S204, the visited province SCP forwards the charging message request to the user home province CHF.
Under the normal scene of the network, the user home province CHF receives a charging message request through the user home province SCP, adds own IP address information into a position field of a message response and returns the message response to the visiting province SMF according to an original path. It should be noted that if the user home province is the visiting province itself, the user home province SCP and the visiting province SCP are the same SCP.
However, in a network anomaly scenario, for example, the charging message request is lost in the course of transmission from the visiting province SCP to the user home province CHF, or the user home province CHF cannot process the charging message request because of too high load, the visiting province SCP will not receive a message response carrying the IP address information of the user home province CHF from the user home province CHF.
In this case, in step S205, the visited province SCP sends a message response carrying the abnormal response code to the visited province CG, and adds the province identifier of the home province of the user to the message response.
In step S206, the visited province CG extracts the province identifier of the home province of the user from the abnormal message response, and matches the province identifier of the visited province with the stored province identifier of the home province, so as to divide the abnormal ticket generated based on the abnormal response code into an abnormal local province ticket or an abnormal roaming ticket.
Specifically, the visited province CG judges that the message response is an abnormal message response by identifying an abnormal response code, and generates an abnormal ticket according to the charging message request.
Specifically, when the province identifier of the province belonging to the province of the user is the same as the province identifier of the visiting province stored in the visiting province CG, the visiting province CG judges the generated abnormal ticket as the abnormal local ticket and stores the abnormal ticket in the abnormal local ticket directory. And under the condition that the province identification of the user attribution province is different from the province identification of the stored visiting province, the visiting province CG judges the generated abnormal ticket as an abnormal roaming ticket and stores the abnormal ticket in the abnormal roaming ticket directory.
According to the method and system for distinguishing between abnormal local provinces and abnormal roaming tickets of the present disclosure, in an N40 charging interface of a 5G core network, a Service Control Point (SCP) network element is connected in series between a Charging Gateway (CG) and a charging function unit (CHF), a corresponding province identity and a mapping between them are stored on the SCP for each province number segment nationwide, and the province identity of the local province is stored in the CG. Under the network abnormal scene, the visiting province SCP adds the province identification of the user attribution province in the position field of the abnormal message response sent to the visiting province CG, so that the visiting province CG can judge that the abnormal ticket is the abnormal ticket of the province or the roaming abnormal ticket by matching the province identification of the user attribution province with the stored province identification of the province, thereby realizing the abnormal ticket separation of the abnormal ticket and the storage of the roaming abnormal ticket directory, and reducing the flow of sorting the ticket at the charging side. According to the method and the system, the provincial charging center only needs to collect the abnormal provincial ticket for charging, and the group settlement center only needs to collect the abnormal roaming ticket for provincial settlement, so that the charging and settlement efficiency is improved.
Compared with the prior art, the method and the device enable the visited province CG to avoid matching each charging message request with the number segment of each province nationwide, thereby reducing the performance loss of the CPU.
Fig. 3 illustrates an exemplary configuration of a computing device 1000 capable of implementing embodiments in accordance with the present disclosure.
Computing device 1000 is an example of a hardware device that can employ the above aspects of the present disclosure. Computing device 1000 may be any machine configured to perform processing and/or computing. Computing device 1000 may be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a Personal Data Assistant (PDA), a smart phone, an in-vehicle computer, or a combination thereof.
As shown in fig. 3, computing device 1000 may include one or more elements that may be connected to or in communication with bus 1002 via one or more interfaces. Bus 1002 may include, but is not limited to, an industry standard architecture (Industry Standard Architecture, ISA) bus, a micro channel architecture (Micro Channel Architecture, MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus. Computing device 1000 may include, for example, one or more processors 1004, one or more input devices 1006, and one or more output devices 1008. The one or more processors 1004 may be any kind of processor and may include, but are not limited to, one or more general purpose processors or special purpose processors (such as special purpose processing chips). The processor 1004 may, for example, implement the functions of the various constituent elements of the system shown in fig. 1. Input device 1006 may be any type of input device capable of inputting information to a computing device and may include, but is not limited to, a mouse, keyboard, touch screen, microphone, and/or remote controller. The output device 1008 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers.
The computing device 1000 may also include or be connected to a non-transitory storage device 1014, which non-transitory storage device 1014 may be any storage device that is non-transitory and that may enable data storage, and may include, but is not limited to, disk drives, optical storage devices, solid state memory, floppy disks, flexible disks, hard disks, magnetic tape, or any other magnetic medium, compact disk or any other optical medium, cache memory and/or any other memory chip or module, and/or any other medium from which a computer may read data, instructions, and/or code. Computing device 1000 may also include Random Access Memory (RAM) 1010 and Read Only Memory (ROM) 1012. The ROM 1012 may store programs, utilities or processes to be executed in a non-volatile manner. RAM 1010 may provide volatile data storage and storage that is compatible with the operation of the computing device 1000An off instruction. Computing device 1000 may also include a network/bus interface 1016 coupled to data link 1018. The network/bus interface 1016 may be any kind of device or system capable of enabling communication with external equipment and/or a network and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication devices, and/or chipsets (such as bluetooth) TM Devices, 802.11 devices, wiFi devices, wiMax devices, cellular communication facilities, etc.).
The present disclosure may be implemented as any combination of apparatuses, systems, integrated circuits, and computer programs on a non-transitory computer readable medium. One or more processors may be implemented as an Integrated Circuit (IC), application Specific Integrated Circuit (ASIC), or large scale integrated circuit (LSI), system LSI, super LSI, or ultra LSI assembly that performs some or all of the functions described in this disclosure.
The present disclosure includes the use of software, applications, computer programs, or algorithms. The software, application, computer program or algorithm may be stored on a non-transitory computer readable medium to cause a computer, such as one or more processors, to perform the steps described above and depicted in the drawings. For example, one or more memories may store software or algorithms in executable instructions and one or more processors may associate a set of instructions to execute the software or algorithms to provide various functions in accordance with the embodiments described in this disclosure.
The software and computer programs (which may also be referred to as programs, software applications, components, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural, object-oriented, functional, logical, or assembly or machine language. The term "computer-readable medium" refers to any computer program product, apparatus or device, such as magnetic disks, optical disks, solid state memory devices, memory, and Programmable Logic Devices (PLDs), for providing machine instructions or data to a programmable data processor, including computer-readable media that receives machine instructions as a computer-readable signal.
By way of example, computer-readable media can comprise Dynamic Random Access Memory (DRAM), random Access Memory (RAM), read Only Memory (ROM), electrically erasable read only memory (EEPROM), compact disk read only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer-readable program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or general purpose or special purpose processor. Disk or disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
The subject matter of the present disclosure is provided as examples of apparatuses, systems, methods, and programs for performing the features described in the present disclosure. However, other features or variations are contemplated in addition to the features described above. It is contemplated that the implementation of the components and functions of the present disclosure may be accomplished with any emerging technology that may replace any of the above-described implementation technologies.
In addition, the foregoing description provides examples without limiting the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, replace, or add various procedures or components as appropriate. For example, features described with respect to certain embodiments may be combined in other embodiments.
Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous.
Claims (10)
1. A method for distinguishing an abnormal local ticket from an abnormal roaming ticket comprises the following steps:
the visiting province charging gateway CG receives a charging message request carrying a user permanent identifier SUPI, wherein a province identifier of the visiting province is stored in the visiting province CG;
the visiting province CG transmits the charging information request to the visiting province service control point network element SCP, wherein the visiting province SCP stores the number section of each province, the province identifier of each province and the mapping between the number section of each province and the province identifier;
the visiting province SCP matches the user SUPI with the number segment of each province to determine the province identity of the user attribution province and the user attribution province;
the visiting province SCP forwards a charging message request to a user attribution province charging function unit CHF;
under the condition that the network abnormal visiting province SCP does not receive the message response carrying the IP address information of the home province CHF from the user home province CHF, the visiting province SCP sends the message response carrying the abnormal response code to the visiting province CG and adds the province identifier of the user home province in the message response; and
the visiting province CG extracts the province mark of the user attribution province from the message response and matches the province mark of the visiting province with the stored province mark of the visiting province so as to divide the abnormal ticket generated based on the abnormal response code into an abnormal local province ticket or an abnormal roaming ticket.
2. The method of claim 1, wherein the visiting province SCP matching the user SUPI with the number segment of each province to determine a user home province and a province identity of the user home province comprises:
SCP compares user SUPI with number segment of each province;
if the SUPI of the user is the same as a part of the number segment of one of the provinces, determining the province as the user attribution province; and is also provided with
And determining the province identifier of the province to which the user belongs according to the mapping between the number segment of each province and the province identifier.
3. The method of claim 1 or 2, wherein the visited province CG matching the extracted province identity of the user's home province with the stored province identity of the visited province to distinguish an abnormal ticket as an abnormal local ticket or an abnormal roaming ticket comprises:
under the condition that the extracted province identification of the user attribution province is the same as the stored province identification of the visiting province, the visiting province CG judges the generated abnormal ticket as the abnormal local ticket and stores the abnormal ticket in the abnormal local ticket catalog, and
and under the condition that the extracted province identification of the user attribution province is different from the stored visit province identification, the visit province CG judges the generated abnormal ticket as an abnormal roaming ticket and stores the abnormal ticket in the abnormal roaming ticket directory.
4. A method according to claim 1 or 2, wherein in a normal network scenario, the user home province CHF adds its own IP address information to the location field of the message response after receiving the charging message request, and returns the message response to the visited province SCP.
5. The method according to claim 1 or 2, wherein the visited province CG judges that the message response is an abnormal message response by recognizing an abnormal response code, and generates an abnormal ticket according to the charging message request.
6. A method according to claim 1 or 2, wherein the visited province SCP adds a province identity of the user's home province in a location field of the message response carrying the abnormal response code sent to the visited province CG.
7. A system for distinguishing between an abnormal provincial ticket and an abnormal roaming ticket, comprising:
the visited province charging gateway CG is configured to receive a charging message request carrying a subscriber permanent identifier SUPI and forward the charging message request to a service control point network element SCP of the visited province, where the charging gateway CG includes:
the province identity storage module is used for storing province identities of the visiting provinces;
a ticket determining module, configured to receive a response message from the SCP of the visited province, and configured to:
under the condition that the message response is identified to comprise the abnormal response code, judging the message response as abnormal message response, and generating an abnormal ticket according to the charging message request; and
extracting the province identifier of the user attribution province from the abnormal message response and matching the province identifier with the province identifier of the visiting province so as to divide the abnormal ticket into an abnormal local province ticket or an abnormal roaming ticket;
a visiting province SCP connected with visiting province CG, visiting province charging function unit CHF and SCP of other provinces, comprising:
the mapping storage module is used for storing the number segment of each province, the province identifier of each province and the mapping between the number segment of each province and the province identifier;
a matching module configured to:
matching a user SUPI in a charging message request received from a visiting province CG with a number segment of each province stored in a mapping storage module to determine a user attribution province and a province identification of the user attribution province; and
and under the condition that the network abnormality does not receive the message response carrying the IP address information returned by the CHF of the user home province, sending the message response carrying the abnormal response code to the visiting province CG and adding the province identifier of the user home province in the message response.
8. The system of claim 7, further comprising:
the user attribution province CHF is connected with the user attribution province SCP and is used for receiving a charging message request from the user attribution province SCP under the normal network scene and returning a message response carrying the IP address information of the user attribution province CHF to the visiting province CG through the user attribution province SCP.
9. The system of claim 7 or 8, further comprising:
and the visiting province session management function unit SMF is connected with the visiting province CG and is used for sending a charging message request to the visiting province CG and receiving a message response from the visiting province CG.
10. A computer-readable storage medium comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110266652.XA CN115086895B (en) | 2021-03-11 | 2021-03-11 | Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110266652.XA CN115086895B (en) | 2021-03-11 | 2021-03-11 | Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115086895A CN115086895A (en) | 2022-09-20 |
| CN115086895B true CN115086895B (en) | 2023-11-21 |
Family
ID=83240493
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110266652.XA Active CN115086895B (en) | 2021-03-11 | 2021-03-11 | Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115086895B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007137522A1 (en) * | 2006-06-01 | 2007-12-06 | Huawei Technologies Co., Ltd. | A policy and charging control method, system and device in roaming scenarios |
| CN101621780A (en) * | 2008-07-04 | 2010-01-06 | 中兴通讯股份有限公司 | Off-line roam charging method for IP multimedia subsystem |
| KR20120090608A (en) * | 2011-02-08 | 2012-08-17 | 주식회사 케이티 | Method for blocking abnormal roaming ho and home network for supporting thereof |
| WO2015169044A1 (en) * | 2014-05-05 | 2015-11-12 | 华为技术有限公司 | Session binding method, device and system in roaming scenario |
| CN110896545A (en) * | 2018-09-13 | 2020-03-20 | 中移信息技术有限公司 | Online charging roaming fault positioning method, related device and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647699B (en) * | 2012-04-18 | 2015-08-12 | 中兴通讯股份有限公司 | Strategy and billing control method, V-PCRF and V-OCS |
| WO2017105317A1 (en) * | 2015-12-17 | 2017-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | A wireless device, a radio network node, and methods therein for access control in a communications network |
-
2021
- 2021-03-11 CN CN202110266652.XA patent/CN115086895B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007137522A1 (en) * | 2006-06-01 | 2007-12-06 | Huawei Technologies Co., Ltd. | A policy and charging control method, system and device in roaming scenarios |
| CN101621780A (en) * | 2008-07-04 | 2010-01-06 | 中兴通讯股份有限公司 | Off-line roam charging method for IP multimedia subsystem |
| KR20120090608A (en) * | 2011-02-08 | 2012-08-17 | 주식회사 케이티 | Method for blocking abnormal roaming ho and home network for supporting thereof |
| WO2015169044A1 (en) * | 2014-05-05 | 2015-11-12 | 华为技术有限公司 | Session binding method, device and system in roaming scenario |
| CN105101176A (en) * | 2014-05-05 | 2015-11-25 | 华为技术有限公司 | Session binding method, device and system in roaming scene |
| CN110896545A (en) * | 2018-09-13 | 2020-03-20 | 中移信息技术有限公司 | Online charging roaming fault positioning method, related device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| VoLTE业务自动开通的实施方案;蔺俊燕;;电子技术与软件工程(第14期);全文 * |
| 移动互联网业务拜访地接入改造实践;张科锋;郭威;;电信技术(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115086895A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150112860A1 (en) | Contactless Payment Method, Device, and System | |
| CN105227786A (en) | A kind of means of communication based on virtual-number and device | |
| CN106201783B (en) | A kind of data reconstruction method and device | |
| CN110175828B (en) | User verification method and device based on bank card quick payment signing | |
| US10623405B2 (en) | Communication system, access authentication method and system based on communication system | |
| US11380303B2 (en) | System and method for call classification | |
| CN111787521A (en) | Terminal application permission obtaining method, terminal equipment and USIM | |
| EP3933625A1 (en) | Information verification method, apparatus, and device | |
| CN104486091A (en) | Charging method and device | |
| CN104954431A (en) | Network selection method, device and system | |
| CN115086895B (en) | Method and system for distinguishing abnormal local call ticket from abnormal roaming call ticket | |
| CN113543056B (en) | 5G charging method and device for home routing scene | |
| CN113873450B (en) | Short message configuration method, device, computer equipment and storage medium | |
| CN115795544A (en) | File security attribute storage method and related device | |
| CN113301203B (en) | Method and device for updating historical information data based on address book | |
| CN110875895A (en) | Method, system, equipment and vehicle for realizing intelligent terminal software login | |
| CN114915508A (en) | Apparatus, method and computer program for network apparatus | |
| CN104065717B (en) | Browser communication means, system and SIM card based on mobile terminal | |
| CN114257687A (en) | System and method for processing unwanted telephone calls | |
| CN112671765A (en) | Method and device for verifying validity of wireless network equipment | |
| CN113840249A (en) | Method, charging gateway and system for distinguishing charging call tickets | |
| CN115102771B (en) | Data processing method, terminal device, system, device and storage medium | |
| CN116095681B (en) | Method and equipment for network fusion authentication | |
| KR20190027264A (en) | Recording medium | |
| CN113138999B (en) | Data processing method and device, computer storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |