KR102109822B1 - Method for synchronizing data session information and apparatus for analyzing radius - Google Patents

Abstract

A method for synchronizing data session information is provided, receiving an emergency call event, receiving a charging message generated by a packet processing node from a packet processing node based on the received emergency call event, and analyzing the received charging message And extracting data session information for the wireless terminal and transmitting data session information to the policy management node.

Description

A method for synchronizing data session information and a billing message analysis device therefor {METHOD FOR SYNCHRONIZING DATA SESSION INFORMATION AND APPARATUS FOR ANALYZING RADIUS}

The present invention relates to a method for synchronizing data session information and an apparatus for analyzing a billing message therefor, and more particularly, to a method and apparatus capable of interworking between PGW and PCRF during emergency call processing.

Recently, as the spread of wireless terminals (UEs) such as smart pads, tablet PCs, and smartphones increases, wireless terminals using LTE networks are increasing to provide better services than 3G.

At this time, the method of authenticating the wireless terminal is made by a method of directly interworking between the MME and the service authentication server. Regarding the method of authenticating the wireless terminal, Korean Patent Publication No. 2013-0073728 (published on Jul. 3, 2013), which is a prior art, has a method of reducing unnecessary subscriber request messages delivered to the HSS by directly linking the service authentication server and the MME. It is disclosed.

However, the PGW and PCRF may not be linked due to the overload of the PGW or the failure of the PCRF, which may inevitably cause a data session to be established between the UE and the PGW without policy inquiry. In this case, the Internet is available in the wireless terminal, but the service that still requires authentication cannot be used.

In Korean Patent Publication No. 2013-0073728 (published on July 03, 2013), "Authentication device and method in LTE system" is disclosed.

According to an embodiment of the present invention, a RADIUS analysis device is provided, and a RADIUS message generated from a PGW is received and analyzed, and the necessary information for authenticating the UE in the service authentication server can be synchronized so that the PCRF can also be maintained. It is possible to provide a method for synchronizing data session information and a billing message analysis device therefor. However, the technical problem to be achieved by the present embodiment is not limited to the technical problem as described above, and other technical problems may exist.

As a technical means for achieving the above-described technical problem, an embodiment of the present invention comprises the steps of receiving an emergency call occurrence event, and a charging message generated by the packet processing node from the packet processing node based on the received emergency call occurrence event. The method includes receiving, analyzing the received charging message, extracting data session information for the wireless terminal, and transmitting data session information to the policy management node.

According to any one of the above-described problem solving means of the present invention, a RADIUS analysis apparatus is provided, and RADIUS messages generated from a PGW are received and analyzed, and PCRF can also hold information necessary to authenticate the UE in the service authentication server. So that you can synchronize. Accordingly, even in a situation in which interworking between the PGW and the PCRF is impossible, a service requiring authentication can be used in the UE, and the empirical quality of the user using the wireless terminal can be improved.

1 is a configuration diagram for explaining an LTE network system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating the apparatus for analyzing a billing message shown in FIG. 1.
FIG. 3 is a diagram illustrating an embodiment of a process in which the billing message analysis device shown in FIG. 1 synchronizes data session information.
FIG. 4 is a diagram illustrating a process in which data is transmitted and received between each of the components included in the LTE network system of FIG. 1 according to an embodiment of the present invention.
5 is a flowchart illustrating an operation of synchronizing data session information according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present invention pertains may easily practice. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. In addition, in order to clearly describe the present invention in the drawings, parts irrelevant to the description are omitted, and like reference numerals are assigned to similar parts throughout the specification.

Throughout the specification, when a part is "connected" to another part, this includes not only "directly connected" but also "electrically connected" with another element in between. . Also, when a part is said to "include" a certain component, it means that the component may further include other components, not exclude other components, unless specifically stated otherwise. However, it should be understood that the existence or addition possibilities of numbers, steps, actions, components, parts or combinations thereof are not excluded in advance.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram for explaining an LTE network system according to an embodiment of the present invention. Referring to FIG. 1, the LTE network system 1 includes UE (User Equipment 100), Evolved Node B (eNB 200), SGW (Serving Gateway, 300), MME (Mobility Management Entity, 310), and HLR (Home). Location Register, 330), PGW (PDN Gateway, 400), OCS (Online Charging System, 410), OFCS (Offline Charging System, 430), SPR (Subscriber Profile Repository, 450), RADIUS (Rmote Authentication Dial-In User Services) , 500), PDN (Public Data Network, 600), service authentication server 700, PCRF (Policy and Charging Rules Function, 800). However, since the LTE network system 1 of FIG. 1 is only an embodiment of the present invention, the present invention is not limitedly interpreted through FIG. 1.

UE 100 may be a user terminal. At this time, the UE 100 may be implemented as a terminal that can access a remote server or terminal. The UE 100 is, for example, a wireless communication device in which portability and mobility are guaranteed, and all kinds of smartphones, smartpads, tablet PCs, and the like that can be connected to the PDN 600. It may include a handheld-based wireless communication device.

The eNB 200 may be an LTE base station, or a device that provides a wireless connection between the UE 100 and an LTE network. That is, the eNB 200 may connect the SGW 300 and the UE 100, and manage the handover of the UE 100. At this time, the eNB 200 and the UE 100 may be wirelessly connected.

The SGW 300 controls movement of the UE 100 between 3GPP / E-UTRAN and may perform anchoring during handover of the eNB 200 to the UE 100. For example, when the UE 100 is handed over from one eNB 200 to another eNB 200, handover of the UE 100 may occur with the SGW 300 as an axis. Accordingly, the SGW 300 may operate as an anchor point in intra-LTE mobility.

The MME 310 may control signals between the eNB 200 and the SGW 300, determine routing, and authenticate the UE 100. At this time, the authentication protocol of the MME 310 may be EPS-AKA, and key information for authenticating the UE 100 may be stored in the HLR 330. Accordingly, the MME 310 may receive key information from the HLR 330 to perform authentication for the UE 100. In addition, the MME 310 can manage the EPS bearer. At this time, the EPS bearer (Bearer) may be, for example, a logical tunnel generated between the UE 100 and the PGW 400 (UE (100) -eNB (200) -SGW (300) -PGW (400)) There is, the MME 310 can control the creation, change, and release of the tunnel, etc. In addition, only one EPS bearer is not generated per UE 100, but a plurality can be generated according to each service characteristic, and various types Traffic, i.e., IP flow, may exist in the EPS bearer.MME 310 may also manage the mobility state of the subscriber, for example, the current UE 100 is the LTE network system ( 1) You can manage whether you are connected to, or if you are connected to, the Internet or not (Idle State).

The HLR 330 may be a central database of the LTE network having key information for authentication for each UE 100, subscriber profile, subscriber location information, and the like. At this time, the subscriber profile may include quality of service (QoS) rating information suitable for a service product subscribed to by each subscriber, for example, priority, maximum available bandwidth, and the like.

The PGW 400 may allocate an IP address to the UE 100. At this time, the IP address may be assigned through the UE 100 access procedure defined in 3GPP, not the DHCP protocol. Also, the PGW 400 may perform anchoring for the SGW 300. For example, when the UE 100 is changed from one SGW 300 to another SGW 300 while moving, the PGW 400 may serve as an anchoring point. In addition, the PGW 400 may apply different QoS policies for each UE 100 and manage accounting data for each UE 100. At this time, the accounting data may be, for example, the amount of traffic up and down, access time, etc., and the PGW 400 may deliver the accounting data to the OFCS 430 in the form of a CDR (Charging Data Record). At this time, the accounting data may include a RADIUS message. Accordingly, through the accounting data, it is possible to know the log of when each subscriber was accessed for each subscriber, how much data was used, and how much access was made, and the PGW 400 can generate and manage them all and transmit them to the OFCS 430.

The OCS 410 may centrally manage residual usage (Balance or Credit) for real-time usage for each UE 100 when the UE 100 uses a prepaid. Here, real-time usage can be managed by the PGW 400 and the residual usage can be delivered to the OCS 410. At this time, the OCS 410 may inform the PGW 400 of the corresponding information so that the service can no longer be used for the UE 100 using all the remaining usage.

The OFCS 430 may receive and manage the CDRs transmitted by the PGW 400 centrally.

The SPR 450 may store policy and charging rules for each UE 100. Accordingly, the PCRF 800 can obtain information about the UE 100 from the SPR 450.

When receiving the emergency call generation event, the charging message analysis device 500 may receive a RADIUS message from the PGW 400. Here, the RADIUS message may be a billing message. At this time, the emergency call generation event may be an event based on an inoperable state between the PGW 400 and the PCRF 800. In addition, the billing message analysis apparatus 500 may extract data session information for the UE 100 by analyzing the RADIUS message, and transmit it to the PCRF 800 to synchronize data session information for the UE 100 can do. For example, in a situation in which an emergency call is generated, since the linkage between the PGW 400 and the PCRF 800 is not made, that is, the EPS bearer authenticates the UE 100 in the service authentication server 700 even when it is generated. Since it is not possible, the UE 100 cannot use a service that can be used for authentication of the service authentication server 700. Accordingly, the data session information for the UE 100 requesting the PCRF 800 from the charging message analysis apparatus 500 and the service authentication server 700 is received and analyzed from the PGW 400 and transmitted to the PCRF 800. By doing so, the service can be used in the UE 100. In this case, the service may be, for example, MMS.

The PDN 600 is a public data network, and may be, for example, the Internet or an IP network.

The service authentication server 700 may be a server that authenticates whether the UE 100 is a legitimate subscriber when the UE 100 wants to receive any service. For example, the service may be a mobile operator's specialized data service, MMS, map service, or the like. The service authentication server 700 may perform authentication for the UE 100 for a specialized service for use restriction and use management. At this time, the authentication method of the service authentication server 700, when the UE 100 requests a service, receives the UE's unique identification number and IP address of the UE 100 terminal, and the received IP address is assigned by the PGW 400 It can be done by checking whether it is an IP address and checking whether it is a customer of the operator. At this time, information such as an IP address and a terminal identification number may be received from the PCRF 800.

The PCRF 800 may be a device that determines rules for policies and charging for each UE 100. At this time, the policy may be QoS information to be used by the UE 100, and the charging may be information on whether to perform offline charging or online charging. These information may be transferred from the PCRF 800 to the PGW 400, and the PGW 400 may perform control (QoS, Charging) for the UE 100 based on the information received from the PCRF 800. have.

The method for synchronizing data session information occurring in the LTE network system according to an embodiment of the present invention will be described as an example.

Recently, as the spread of wireless terminals (UEs) such as smart pads, tablet PCs, and smartphones increases, wireless terminals using LTE networks are increasing to provide better services than 3G.

At this time, if the data session between the UE and the PGW is inevitably established without a policy inquiry because the PGW overload or PCRF failure cannot be linked between the PGW and the PCRF, the wireless terminal can use the Internet, but cannot use the service requiring authentication.

Therefore, the method for synchronizing data session information according to an embodiment of the present invention includes a RADIUS analysis device, receives and analyzes a RADIUS message generated from a PGW, and PCRF also analyzes the information required to authenticate the UE in the service authentication server. It can be synchronized for retention. Accordingly, even in a situation in which interworking between the PGW and the PCRF is impossible, a service requiring authentication can be used in the UE, and the empirical quality of the user using the wireless terminal can be improved.

FIG. 2 is a configuration diagram for explaining the billing message analysis device shown in FIG. 1, and FIG. 3 is a view showing an embodiment of a process in which the billing message analysis device shown in FIG. 1 synchronizes data session information. .

Referring to Figure 2, the charging message analysis apparatus 500 according to an embodiment of the present invention includes an event receiving unit 510, a message receiving unit 530, an extraction unit 550, a synchronization unit 570 . At this time, the RADIUS analysis device 500 of FIGS. 2 and 3 may be parallel to the billing message analysis device 500. Also, the UE 100 may be referred to as a wireless terminal, the PGW 400 as a packet processing node, and the PCRF 800 as a policy management node.

The event receiving unit 510 receives an emergency call occurrence event. At this time, the emergency call generation event may be an event corresponding to the inability to interwork between the PGW 400 and the PCRF 800. In addition, the emergency call generation event may be an event generated when a data session is formed without a policy query for the UE 100 from the PGW 400 to the PCRF 800.

The message receiving unit 530 may receive a RADIUS message generated by the PGW 400 from the PGW 400 based on the received emergency call occurrence event. At this time, the RADIUS message may be a message generated from the PGW 400 and transmitted to a RADIUS server (not shown). Here, the RADIUS server may be a server that provides authentication, authorization, and accounting.

The extraction unit 550 analyzes the received RADIUS message to extract data session information for the UE 100. At this time, the RADIUS message may include data session information, and the data session information includes at least one of a unique identification number, IP address information, and location information including a phone number and a Mobile Directory Number (MDN) of the UE 100. can do.

The synchronization unit 570 may synchronize the PGW 400 and the PCRF 800 by transmitting data session information to the PCRF 800. That is, the synchronization unit 570 may allow the PCRF 800 to retain information about the UE 100 held by the PGW 400. At this time, the service authentication server 700 for providing the service requested by the UE 100 PCRF data session information for authenticating the UE 100 based on the IP assigned by the UE 100 to the PGW 400. (800). Then, the service authentication server 700 may authenticate the UE 100 by receiving data session information of the UE 100 stored in the PCRF 800 from the synchronized PCRF 800.

Accordingly, when the user authentication of the service authentication server 700 is completed, the UE 100 may use a service requiring authentication even in a situation in which interworking between the PGW 400 and the PCRF 800 is impossible.

The driving process of the RADIUS analysis apparatus 500 having the above-described configuration will be described with reference to FIG. 3 as an example.

Referring to FIG. 3, ① when interworking between the PGW 400 and the PCRF 800 is impossible, ② the billing message analysis apparatus 500 receives a RADIUS message from the PGW 400 based on an emergency call occurrence event. ③ Then, the billing message analysis apparatus 500 analyzes the RADIUS message and extracts data session information.

④ At this time, the service authentication server 700, the data session information based on the IP assigned to the UE (100) with the PCRF (800), in order to perform authentication as the entire operation to provide the service requested by the UE (100) ( MDN, etc.). ⑤ PCRF 800 is based on the data session information received from the RADIUS analysis device 500, since the information on the UE 100 is synchronized with the PGW 400, the data session to the service authentication server 700 Send information.

⑥ Then, the service authentication server 700 may authenticate whether the UE 100 is a legitimate user using the data session information received from the PCRF 800.

The details not described for the data session information synchronization method of FIGS. 2 and 3 can be easily inferred from the same or described contents of the data session information method through FIG. 1, so the description below will be omitted. Do it.

FIG. 4 is a diagram illustrating a process in which data is transmitted and received between each of the components included in the LTE network system of FIG. 1 according to an embodiment of the present invention. Hereinafter, an example of a process in which data is transmitted and received between each of the components will be described with reference to FIG. 4, but the present application is not limited to such an embodiment, and is illustrated in FIG. 4 according to various embodiments described above. It is apparent to those skilled in the art that the process of transmitting and receiving data can be changed.

Referring to FIG. 4, the UE 100 requests a connection to the eNB 200 (S4100), and the eNB 200 requests to create a session of the PGW 400 through the SGW 300 (S4200), PGW When the linkage between 400 and PCRF 800 is poor (S4300), the billing message analysis device 500 receives an emergency call generation event (S4400).

Then, the billing message analysis apparatus 500 receives the RADIUS message generated in the PGW 400 (S4500), and extracts data session information for the UE 100 from the RADIUS message (S4600).

In addition, the billing message analysis apparatus 500 transmits the extracted data session information to the PCRF 800, thereby updating data that was not synchronized due to poor linkage between the PCRF 800 and the PGW 400 (S4700).

Meanwhile, when a data session information request including an MDN is received based on the IP assigned to the UE 100 from the service authentication server 700 to the PCRF 800 (S4800), the PCRF 800 authenticates the data session information to the service. It transmits to the server 700 (S4810).

Then, the service authentication server 700 authenticates the UE 100 based on data session information in order to provide the service requested by the UE 100 (S4900).

The description of the method for synchronizing data session information in FIG. 4 can be easily inferred from the contents described or described for the method for synchronizing data session information in FIGS. 1 to 3, so the description below is omitted. Do it.

The order between the above-described steps (S4100 to S4900) is only an example, and is not limited thereto. That is, the order between the above-described steps (S4100 to S4900) may be mutually variable, some of which may be executed or deleted simultaneously.

5 is a flowchart illustrating an operation of synchronizing data session information according to an embodiment of the present invention. Referring to FIG. 5, when the RADIUS analysis device receives an emergency call generation event (S5100), based on the received emergency call generation event, the remote authentication dial-in user generated by the PGW from the PGW (PDN GateWay) Services) message is received (S5200).

Here, the RADIUS analysis apparatus analyzes the received RADIUS message and extracts data session information for a user equipment (UE) (S5300).

Then, the RADIUS analysis device transmits data session information to a Policy and Charging Rules Function (PCFR) to synchronize PGW and PCRF (S5400).

The details not described for the data session information synchronization method of FIG. 5 can be easily inferred from the same or described contents of the data session information synchronization method through FIGS. 1 to 4, and thus the description below will be omitted. Do it.

The method for synchronizing data session information according to an embodiment described with reference to FIG. 5 may also be implemented in the form of a recording medium including instructions executable by a computer, such as an application or program module executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism, and includes any information delivery media.

The above description of the present invention is for illustration only, and those skilled in the art to which the present invention pertains can understand that the present invention can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the above detailed description, and it should be interpreted that all changes or modified forms derived from the meaning and scope of the claims and equivalent concepts thereof are included in the scope of the present invention. do.

Claims (5)

In the method for synchronizing data session information executed by the billing message analysis device,
Receiving an emergency call occurrence event according to a state in which interworking between the packet processing node and the policy management node is impossible;
Receiving a billing message generated by the packet processing node from the packet processing node based on the received emergency call occurrence event;
Extracting data session information used for authentication of a wireless terminal requesting a service by analyzing the charging message received from the packet processing node in a state in which interworking between the packet processing node and the policy management node is impossible; And
Transmitting the data session information for the wireless terminal to the policy management node for setting a charging rule for the wireless terminal
Including, data session information synchronization method.
delete ◈ Claim 3 was abandoned when payment of the set registration fee was made.◈ According to claim 1,
The data session information, a method of synchronizing data session information that includes at least one of a unique identification number, IP address information, and location information, including a mobile phone number and a MDN (Mobile Directory Number).
An event receiving unit receiving an emergency call occurrence event according to a state in which interworking between the packet processing node and the policy management node is impossible;
A message receiving unit receiving a charging message generated by the packet processing node from the packet processing node based on the received emergency call occurrence event;
An extracting unit extracting data session information used for authentication of a wireless terminal requesting a service by analyzing the charging message received from the packet processing node in a state in which interworking between the packet processing node and the policy management node is impossible; And
A synchronization unit that transmits the data session information for the wireless terminal to the policy management node for setting charging rules for the wireless terminal
Billing message analysis device comprising a.
◈ Claim 5 was abandoned when payment of the set registration fee was made.◈ The method of claim 4,
The non-call event is an event generated when a data session is formed without a policy query for the wireless terminal from the packet processing node to the policy management node.

Images