CN112187481B - User online record management method, device and system - Google Patents
User online record management method, device and system Download PDFInfo
- Publication number
- CN112187481B CN112187481B CN201910602315.6A CN201910602315A CN112187481B CN 112187481 B CN112187481 B CN 112187481B CN 201910602315 A CN201910602315 A CN 201910602315A CN 112187481 B CN112187481 B CN 112187481B
- Authority
- CN
- China
- Prior art keywords
- radius charging
- charging message
- radius
- default bearer
- packet
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1425—Charging, metering or billing arrangements for data wireline or wireless communications involving dedicated fields in the data packet for billing purposes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure provides a user online record management method, device and system. After receiving the Radius charging message, the user online record management device judges whether the Radius charging message is sent by a PGW, judges whether the Radius charging message corresponds to a default bearer under the condition that the Radius charging message is sent by the PGW, extracts corresponding attribute information from the Radius charging message under the condition that the Radius charging message corresponds to the default bearer, and generates corresponding user online record information according to the attribute information. The method and the device can accurately identify the online state of the user in a 4G network scene.
Description
Technical Field
The present disclosure relates to the field of communications, and in particular, to a method, an apparatus, and a system for managing user online records.
Background
In the related art, the IP address tracing system establishes a User online status base based on an MDN (Mobile Directory Number), an IP address and session time by extracting a MDN (Mobile Directory Number), an IP address and a session time of a Radius (Remote Authentication Directory In User Service) charging start and end message sent by a PGW (PDN GateWay)/PDSN (Packet Data Serving Node).
Disclosure of Invention
The inventor finds out through research that the network bearer of the 4G user comprises a default bearer and a proprietary bearer, and the user IP addresses of the default bearer and the proprietary bearer are the same. Therefore, the existing network IP address tracing system cannot distinguish the bearer type corresponding to the received charging packet. This can lead to the situation that: when the system receives one of the messages bearing the corresponding charging end, the user is judged to be offline by mistake, so that the judgment of the online state of the user is disordered, and the data accuracy is low.
Therefore, the scheme capable of accurately generating the user online record information is provided.
According to a first aspect of the embodiments of the present disclosure, a method for managing a user online record is provided, which includes: after receiving a Radius charging message of a remote user dialing authentication system, judging whether the Radius charging message is sent by a packet data gateway (PGW); judging whether the Radius charging message corresponds to a default bearer or not under the condition that the Radius charging message is sent by a packet data gateway (PGW); under the condition that the Radius charging message corresponds to a default bearer, extracting corresponding attribute information from the Radius charging message; and generating corresponding user online record information according to the attribute information.
In some embodiments, determining whether the Radius charging packet corresponds to a default bearer includes: and judging whether the Radius charging message corresponds to a default bearer or not according to a service Quality Class Identifier (QCI) included in a designated field of the Radius charging message.
In some embodiments, the Radius charging packet is ignored if the Radius charging packet does not correspond to a default bearer.
In some embodiments, when the Radius charging packet is not sent by a packet data gateway PGW, a step of extracting corresponding attribute information from the Radius charging packet is performed.
In some embodiments, the subscriber presence record includes at least one of a mobile subscriber directory number, MDN, a session identification, an IP address, a subscriber time online, a subscriber time offline, a gateway IP, a QCI, or a subscriber location.
According to a second aspect of the embodiments of the present disclosure, there is provided a user online recording management apparatus, including: the device comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to receive a Radius charging message of a remote user dialing authentication system; the first identification module is configured to judge whether the Radius charging message is sent by a packet data gateway (PGW) after the receiving module receives the Radius charging message; a second identification module, configured to determine whether the Radius charging packet corresponds to a default bearer when the Radius charging packet is sent by a packet data gateway PGW; the information processing module is configured to extract corresponding attribute information from the Radius charging message under the condition that the Radius charging message corresponds to a default bearer; and the record generating module is configured to generate corresponding user online record information according to the attribute information.
In some embodiments, the second identifying module is configured to determine whether the Radius charging packet corresponds to a default bearer according to a quality of service class identifier, QCI, included in a specified field of the Radius charging packet.
In some embodiments, the information processing module is further configured to ignore the Radius charging packet if the Radius charging packet does not correspond to a default bearer.
In some embodiments, the information processing module is further configured to, when the Radius charging packet is not sent by a packet data gateway PGW, perform an operation of extracting corresponding attribute information from the Radius charging packet.
In some embodiments, the subscriber presence record includes at least one of a mobile subscriber directory number, MDN, a session identification, an IP address, a subscriber time online, a subscriber time offline, a gateway IP, a QCI, or a subscriber location.
According to a third aspect of the embodiments of the present disclosure, there is provided a user online recording management apparatus, including: a memory configured to store instructions; a processor coupled to the memory, the processor configured to perform a method implementing any of the embodiments described above based on instructions stored by the memory.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a user online record management system, including the user online record management apparatus according to any of the embodiments described above.
According to a fifth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, in which computer instructions are stored, and when executed by a processor, the computer-readable storage medium implements the method according to any of the embodiments described above.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a flow chart of a user online record management method according to an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart illustrating a user online record management method according to another embodiment of the present disclosure;
FIG. 3 is a schematic structural diagram of a user online record management apparatus according to an embodiment of the present disclosure;
FIG. 4 is a schematic structural diagram of a user online record management apparatus according to another embodiment of the present disclosure;
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
Fig. 1 is a schematic flow chart of a user online record management method according to an embodiment of the present disclosure. In some embodiments, the user online record management method steps are performed by a user online record management device.
In step 101, after receiving the Radius charging packet, it is determined whether the Radius charging packet is sent by a PGW.
In some embodiments, whether the Radius charging packet is sent by the PGW may be determined by a Network Attached Storage (NAS) IP address.
In step 102, when the Radius charging packet is sent by the PGW, it is determined whether the Radius charging packet corresponds to a default bearer.
In some embodiments, it is determined whether the Radius charging packet corresponds to a default bearer according to a QCI (QoS Class Identifier) included in a designated field of the Radius charging packet. The designated field is the Vendor-Specific field in the Radius accounting message.
For example, if the QCI value is 8, 9, or 5, it indicates that the Radius charging packet corresponds to the default bearer.
In step 103, corresponding attribute information is extracted from the Radius charging packet when the Radius charging packet corresponds to the default bearer.
In some embodiments, the attribute information includes information such as an MDN number, a session identifier, a user IP address, a charging start time, and a charging end time.
In step 104, corresponding user online record information is generated according to the attribute information.
In some embodiments, the subscriber presence record includes at least one of a mobile subscriber directory number, MDN, a session identification, an IP address, a subscriber time online, a subscriber time offline, a gateway IP, a QCI, or a subscriber location.
In the user online record management method provided in the above embodiment of the present disclosure, the Radius charging packet corresponding to the default bearer is identified by using the QCI, and then the attribute information in the packet is extracted to generate the user online record. Therefore, the online state of the user can be accurately identified in the 4G network scene.
Fig. 2 is a flowchart illustrating a user online record management method according to another embodiment of the disclosure. In some embodiments, the user online record management method steps are performed by a user online record management device.
In step 201, a Radius charging packet is received.
In step 202, it is determined whether the Radius charging packet is sent by the PGW.
If the Radius charging message is sent by the PGW, step 203 is executed; if the Radius charging packet is not sent by the PGW, step 204 is executed.
In step 203, it is determined whether the Radius charging packet corresponds to a default bearer.
In some embodiments, it is determined whether the Radius charging packet corresponds to a default bearer according to a QCI included in a designated field of the Radius charging packet. The designated field is the Vendor-Specific field in the Radius accounting message. For example, if the QCI value is 8, 9, or 5, it indicates that the Radius charging packet corresponds to the default bearer.
If the Radius charging message corresponds to the default bearer, execute step 204; in case the Radius charging packet does not correspond to the default bearer, step 206 is performed.
In step 204, corresponding attribute information is extracted from the Radius accounting message.
In some embodiments, the attribute information includes information such as an MDN number, a session identifier, a user IP address, a charging start time, and a charging end time.
In step 205, corresponding user online record information is generated according to the attribute information.
In some embodiments, the subscriber presence record includes at least one of a mobile subscriber directory number, MDN, a session identification, an IP address, a subscriber time online, a subscriber time offline, a gateway IP, a QCI, or a subscriber location.
In step 206, the Radius accounting message is ignored.
Fig. 3 is a schematic structural diagram of a user online record management apparatus according to an embodiment of the present disclosure. As shown in fig. 3, the user online record management apparatus includes a receiving module 31, a first identifying module 32, a second identifying module 33, an information processing module 34, and a record generating module 35.
The receiving module 31 is configured to receive a Radius accounting packet.
The first identifying module 32 is configured to determine whether the Radius charging packet is sent by the PGW after the receiving module receives the Radius charging packet.
The second identifying module 33 is configured to determine whether the Radius charging packet corresponds to a default bearer, when the Radius charging packet is sent by a PGW.
In some embodiments, the second identifying module 33 is configured to determine whether the Radius charging packet corresponds to a default bearer according to a QCI included in a specified field of the Radius charging packet. The designated field is the Vendor-Specific field in the Radius accounting message.
For example, if the QCI value is 8, 9, or 5, it indicates that the Radius charging packet corresponds to the default bearer.
The information processing module 34 is configured to extract corresponding attribute information from the Radius charging packet when the Radius charging packet corresponds to a default bearer.
In some embodiments, the attribute information includes information such as an MDN number, a session identifier, a user IP address, a charging start time, and a charging end time.
In some embodiments, the information processing module 34 is further configured to ignore the Radius charging packet in case the Radius charging packet does not correspond to a default bearer.
In some embodiments, the information processing module 34 is further configured to, in a case that the Radius accounting packet is not sent by the packet data gateway PGW, perform an operation of extracting corresponding attribute information from the Radius accounting packet.
The record generation module 35 is configured to generate corresponding user online record information according to the attribute information.
In some embodiments, the subscriber presence record includes at least one of a mobile subscriber directory number, MDN, a session identification, an IP address, a subscriber time online, a subscriber time offline, a gateway IP, a QCI, or a subscriber location.
Fig. 4 is an exemplary block diagram of a user online record management apparatus according to another embodiment of the present disclosure. As shown in fig. 4, the user online record management apparatus includes a memory 41 and a processor 42.
The memory 41 is used for storing instructions, the processor 42 is coupled to the memory 41, and the processor 42 is configured to execute the method according to any one of the embodiments in fig. 1 and fig. 2 based on the instructions stored in the memory.
As shown in fig. 4, the user online record management apparatus further includes a communication interface 43 for information interaction with other devices. Meanwhile, the device also comprises a bus 44, and the processor 42, the communication interface 43 and the memory 41 are communicated with each other through the bus 44.
The memory 41 may comprise a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 41 may also be a memory array. The storage 41 may also be partitioned, and the blocks may be combined into virtual volumes according to certain rules.
Further, the processor 42 may be a central processing unit CPU, or may be an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present disclosure.
The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the instructions, when executed by a processor, implement a method according to any one of the embodiments shown in fig. 1 or fig. 2.
The present disclosure also provides a user online record management system, which includes the user online record management apparatus according to any one of fig. 3 or fig. 4.
In some embodiments, the functional unit modules described above can be implemented as a general purpose Processor, a Programmable Logic Controller (PLC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic device, discrete Gate or transistor Logic, discrete hardware components, or any suitable combination thereof for performing the functions described in this disclosure.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (13)
1. A user online record management method comprises the following steps:
after receiving a Radius charging message of a remote user dialing authentication system, judging whether the Radius charging message is sent by a packet data gateway (PGW);
judging whether the Radius charging message corresponds to a default bearer or not under the condition that the Radius charging message is sent by a PGW (packet data gateway);
under the condition that the Radius charging message corresponds to a default bearer, extracting corresponding attribute information from the Radius charging message;
and generating corresponding user online record information according to the attribute information.
2. The method of claim 1, wherein determining whether the Radius charging packet corresponds to a default bearer comprises:
and judging whether the Radius charging message corresponds to a default bearer or not according to a service Quality Class Identifier (QCI) included in a designated field of the Radius charging message.
3. The method of claim 1, further comprising:
and under the condition that the Radius charging message does not correspond to the default bearer, ignoring the Radius charging message.
4. The method of claim 1, wherein,
and under the condition that the Radius charging message is not sent by the PGW, executing the step of extracting corresponding attribute information from the Radius charging message.
5. The method of any one of claims 1-4,
the subscriber presence record includes at least one of a mobile subscriber directory number MDN, a session identifier, an IP address, a subscriber presence time, a subscriber absence time, a gateway IP, a QCI, or a subscriber location.
6. A user online record management apparatus, comprising:
the device comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to receive a Radius charging message of a remote user dialing authentication system;
the first identification module is configured to judge whether the Radius charging message is sent by a packet data gateway (PGW) after the receiving module receives the Radius charging message;
a second identification module, configured to determine whether the Radius charging packet corresponds to a default bearer when the Radius charging packet is sent by a PGW;
the information processing module is configured to extract corresponding attribute information from the Radius charging message under the condition that the Radius charging message corresponds to a default bearer;
and the record generating module is configured to generate corresponding user online record information according to the attribute information.
7. The apparatus of claim 6, wherein,
and the second identification module is configured to judge whether the Radius charging message corresponds to a default bearer according to a quality of service (QCI) included in a designated field of the Radius charging message.
8. The apparatus of claim 6, wherein,
the information processing module is further configured to ignore the Radius charging packet if the Radius charging packet does not correspond to a default bearer.
9. The apparatus of claim 6, wherein,
the information processing module is further configured to, in a case that the Radius charging packet is not sent by a PGW, perform an operation of extracting corresponding attribute information from the Radius charging packet.
10. The apparatus of any one of claims 6-9,
the subscriber presence record includes at least one of a mobile subscriber directory number MDN, a session identifier, an IP address, a subscriber presence time, a subscriber absence time, a gateway IP, a QCI, or a subscriber location.
11. A user online record management apparatus, comprising:
a memory configured to store instructions;
a processor coupled to the memory, the processor configured to perform implementing the method of any of claims 1-5 based on instructions stored by the memory.
12. A user online record management system comprising the user online record management device according to any one of claims 6-11.
13. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions which, when executed by a processor, implement the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910602315.6A CN112187481B (en) | 2019-07-05 | 2019-07-05 | User online record management method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910602315.6A CN112187481B (en) | 2019-07-05 | 2019-07-05 | User online record management method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112187481A CN112187481A (en) | 2021-01-05 |
| CN112187481B true CN112187481B (en) | 2022-08-02 |
Family
ID=73914598
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910602315.6A Active CN112187481B (en) | 2019-07-05 | 2019-07-05 | User online record management method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112187481B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113067710A (en) * | 2021-03-17 | 2021-07-02 | 恒安嘉新（北京）科技股份公司 | Online user query method and device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101730035A (en) * | 2009-03-19 | 2010-06-09 | 中兴通讯股份有限公司 | Processing method for attaching user equipment (UE), mobility management entity (MME) and UE |
| CN106792615A (en) * | 2016-12-31 | 2017-05-31 | 中国移动通信集团江苏有限公司 | Method and system for recovering the online charging state of user |
| WO2018057077A1 (en) * | 2016-09-21 | 2018-03-29 | Mavenir Systems, Inc. | Method and system for session resilience in packet gateways |
| CN108123807A (en) * | 2016-11-29 | 2018-06-05 | 中国电信股份有限公司 | The system and method that user identity is traced to the source in broadband network |
-
2019
- 2019-07-05 CN CN201910602315.6A patent/CN112187481B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101730035A (en) * | 2009-03-19 | 2010-06-09 | 中兴通讯股份有限公司 | Processing method for attaching user equipment (UE), mobility management entity (MME) and UE |
| WO2018057077A1 (en) * | 2016-09-21 | 2018-03-29 | Mavenir Systems, Inc. | Method and system for session resilience in packet gateways |
| CN108123807A (en) * | 2016-11-29 | 2018-06-05 | 中国电信股份有限公司 | The system and method that user identity is traced to the source in broadband network |
| CN106792615A (en) * | 2016-12-31 | 2017-05-31 | 中国移动通信集团江苏有限公司 | Method and system for recovering the online charging state of user |
Non-Patent Citations (1)
| Title |
|---|
| "S5-113168 Discussion paper on charging triggering for deferred IPv4 addressing".《3GPP tsg_sa\WG5_TM》.2011, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112187481A (en) | 2021-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107645524B (en) | Message pushing processing method and device | |
| CN107911249B (en) | Method, device and equipment for sending command line of network equipment | |
| CN107645722B (en) | Private network selective access method and system, public network MME, HSS and base station | |
| CN106993048B (en) | Determine method and device, information recommendation method and the device of recommendation information | |
| CN110267314B (en) | Method and device for switching network slices | |
| US10623405B2 (en) | Communication system, access authentication method and system based on communication system | |
| CN109951430B (en) | Data processing method and device | |
| CN112187481B (en) | User online record management method, device and system | |
| US9036631B2 (en) | Identifying Gn/Gp mode at PCRF | |
| CN113507471A (en) | Method, device, router and storage medium for acquiring terminal system type | |
| CN109121157B (en) | Network speed limit determining method, terminal and storage medium | |
| CN111162918A (en) | Service fulfillment management method and device | |
| CN114222284A (en) | Terminal equipment identification method and device and readable storage medium | |
| CN108768849A (en) | Message processing method and device | |
| CN108647315A (en) | Collecting method and system | |
| CN111277449B (en) | Safety testing method and device for voice service equipment | |
| CN106507382B (en) | Diameter message routing method and routing agent node | |
| CN107483508B (en) | Message filtering method, device, equipment and storage medium | |
| CN114980075B (en) | Address allocation method, session management functional entity and communication system | |
| CN106612262B (en) | Method, device and system for establishing PCC session | |
| CN105897934A (en) | Service request processing method and device realized on server | |
| CN107872836B (en) | Method and system for policy configuration according to user terminal type | |
| CN106664637A (en) | Routing information configuration method and apparatus | |
| CN105284141B (en) | A kind of method and device of charging | |
| WO2017101592A1 (en) | Calling method and system |
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 |