KR20030040619A - Method of Identifying Account Session of RADIUS Server in Mobile Telephone Packet Data Network - Google Patents

Abstract

PURPOSE: A method of identifying accounting session information of an RADIUS(Remote Authentication Dial In User Service) server in a mobile communication packet data network is provided to supply information on authentication and rights of a subscriber requesting a packet data service, and to identify an accounting session in the RADIUS server, thereby securing accounting session identifying uniqueness according to each session when the subscriber receives the service. CONSTITUTION: When a call is generated in a mobile communication packet data network(S41), a packet data service node gives an accounting session ID to the call, and transmits an account-request message to a local RADIUS server(S42). The local RADIUS server decides whether a self is a home by using a realm of an NAI(Network Access Identification) attribute(S43). If not, the local RADIUS calculates a packet data service node ID, a self ID, and an access session ID(S44), combines each value in proxy state property format type, and stores the values in a proxy state attribute(S45), then transmits the account-request message to a broker RADIUS server(S46). The broker RADIUS server transmits the account-request message to a home RADIUS server(S47). The home RADIUS server recognizes a proxy state value of the message as an accounting session ID, and identifies each accounting session by storing a corresponding value in a database(S48).

Description

Method of Identifying Accounting Session Information of Radius Server in Mobile Packet Data Network {Method of Identifying Account Session of RADIUS Server in Mobile Telephone Packet Data Network}

The present invention relates to a method for identifying billing session information of a Radius server in a mobile communication packet data network. Particularly, when a subscriber receives a service from a visited network, a mobile communication packet data network is provided to ensure uniqueness of billing identification for each session. Relates to a method for identifying billing session information of a Radius server.

In general, a mobile communication packet data network uses a Radius (Remote Authentication Dial In User Service: RADIUS) server to perform subscriber authentication, authorization, and accounting functions.

As shown in FIG. 1, the structure of the mobile communication packet data network includes a mobile terminal 10, a radio network 20 for managing radio resources, and a packet data service node (PSDN). 50, a local RADIUS server 40 directly connected to the packet data service node 50, and a home radius that manages authentication, authorization information, and billing data of mobile subscribers through an Internet network. A broker that acts as a relay with an authentication relationship between a Home RADIUS Server 70, a Visitor Location Register (VLR) 30 and a Home Location Register (HLR) 60. It is provided with a Broker RADIUSServer 80 and a Home Agent (HA) 90 for providing a mobile IP service.

A conventional procedure for obtaining authentication and service authority information for receiving a mobile communication packet data service is described below with reference to the scenario of FIG.

First, when a packet service is attempted for the first mobile terminal 10, a session is established with the packet data service node 50 through the radio network 20.

In this case, the packet data service node 50 transmits an access request message to the local Radius server 40 for authentication and authorization of the subscriber. The local Radaus server 40 identifies the home Radius server 70 by using Network Access Identification (NAI) information included in an access request message, and the home Radius server ( 70), and transmits an access request message.

At this time, the network access identification information is configured in the form of "mobile terminal number @ realm" and the local Radius server 40 identifies the home Radius server 70 by using the realm.

The home Radius server 70 receives the access request message, translates the realm of the network access identification information, retrieves the information of the corresponding packet service subscriber from the database, performs an authentication procedure, and then authenticates. Upon success, the service authorization information of the subscriber is included in the access-accept message and transmitted to the local Radius server 40. Upon receiving the access-accept message from the home radius server 70, the local radius server 40 forwards the received message to the packet data service node 50.

When the packet data service node 50 receives the access-accept message, the packet data service node 50 confirms that authentication is successful, and provides the packet data service to the subscriber by using the authorization information included in the access-accept message. do.

If the subscriber's authentication succeeds when the mobile packet data service is attempted, the packet data service node 50 includes the charging information collected at the start, the middle, and the end of the service in the accounting request message to store the charge. To the local Radius server 40.

The local Radius server 40 identifies the home Radius server 70 using the network access identification information included in the Account-Requst message, and requests the account to the Home Radius server 70. Requst) delivers a message.

The home Radius server 70 receives an accounting request message, translates the realm of the network access identification information, confirms that it is home, stores the charging information, and stores the local Radius server ( 40), the accounting response message indicating the successful reception of the message is transmitted.

When the local Radius server 40 receives an Accounting Response message from the Home Radius server 70, the local Radius server 40 transmits an Accounting Response message to the packet data service node 50 to charge information. Notify that the storage has been successful.

In general, the Radius server receives the subscriber's authentication and authorization information request message from the packet data service node when the subscriber's call is initiated, and after the subscriber's authentication and authorization verification is completed, the subscriber's billing Receive accounting request message to receive accounting information. At this time, the packet data service node assigns an accounting session ID to an accounting request message so that the Radius server can identify the accounting information of each subscriber. At this time, the accounting request message includes an accounting start request for notifying the start of the accounting, an accounting end request for notifying the end of the accounting, an accounting request for notifying the middle of the accounting between the start and end of the accounting. There is an Account Interim Request message.

As described above, when the subscriber initiates a packet data service call, when the charging start request message is transmitted to the Radius server, the packet data service node grants the charging session ID to the charging session ID attribute in the charging start request message to the home. It provides an ID that allows the Radius server to identify the billing for each session. However, since the charging session ID is a random ID generated by the packet data service node, it may be duplicated between different packet data service nodes. The conventional method transmits the same billing session ID to the home radius server when another packet data service node in the visit network provides the same billing session ID for another call while the subscriber is being served in the visit network. It is done. In this case, the Home Radius server may not have the information about the packet data service node that transmitted the relayed billing information. Therefore, the home Radius server judges that the received message is duplicated and discards the packet by performing an error processing. When receiving an intermediate request message or a charge end request message, there was a problem in that charging information of an invalid ID could be updated.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned general problems, and an object thereof is to provide authentication and authorization information of a subscriber requesting packet data service in a mobile communication packet data data network and to store billing information in a Radius server. By providing a method for identifying a billing session, it is to ensure the uniqueness of billing identification for each session when a subscriber is provided with a service in a network.

1 is a diagram showing the structure of a conventional mobile communication packet data network.

2 is a scenario illustrating a procedure for obtaining authentication and service authority information for receiving a conventional mobile communication packet data service.

3 is a diagram illustrating a structure for identifying charging session information of a Radius server in a mobile communication packet data network according to the present invention.

4 is a flowchart illustrating a charging session information identification method of a Radius server in a mobile communication packet data network according to an embodiment of the present invention.

FIG. 5 is a diagram showing a proxy state attribute format in FIG. 4; FIG.

* Description of the symbols for the main parts of the drawings *

10: mobile terminal 60: HLR

20: Radio Network 70: Home Radius Server

30: VLR 80: Broker Radius Server

40: Regional Radius Server 90: Home Agent

50: PDSN

In the mobile communication packet data network of the present invention for achieving the above object, the billing session information identification method of the Radius server is different from the billing information having the same billing session ID generated in the different packet data service network Identifying through a service node ID; When different packet data service nodes use the same packet data service node ID by each local Radius server, a process of identifying a charging session ID using different Radius IDs may be included. .

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

The present invention relates to a method for identifying billing session information of a Radius server, and provides a method for enabling a home Radius server to identify billing for each session using a proxy state attribute.

The structure for identifying the charging session information of the Radius server in the mobile communication packet data network according to the present invention is as shown in Figure 3, the plurality of packet data service node 50, the local Radius server 40, A broker radius server 80, a home radius server 70, and a database 100 are provided.

In the communication between the packet data service node 50 and the local Radius server 40, the attribute used in the subscriber's authentication and access-request message is also included in the accounting-request message. Can be used.

In addition, other attributes in the subscriber's authentication and access-request message may be used in the accounting-request message. Unlike the other attributes in the Account-Request message, the Proxy-State Attribute does not change its contents from the proxy Radius server located in the middle, but directly to the home Radius server 70. Is sent. Using this property, the local Radius server 40 creates a combined value of the packet data service node ID (ID), the visit AAA (Authentication, Authorization, Accounting) ID, and the billing session ID in the proxy status attribute to request the billing start request. (Account Start Request), Account Interim Request, and Account Stop Request (Account Stop Request) messages included in the transmission, and the Home Radius server 70 transfers this value to the Accounting Session ID. Recognize and identify the session of billing.

A method of identifying charging session information of a Radius server in a mobile communication packet data network according to an embodiment of the present invention will be described with reference to the flowchart of FIG. 4.

First, when a call occurs in the mobile communication packet data network (step S41), the packet data service node 50 grants a charging session ID for the originating call and sends an accounting-request message to the local Radius server 40. (Step S42). The local Radius server 40 receiving the corresponding Accounting-Request message determines whether or not it is home by using a realm of a network access identification (NAI) attribute (step S43). If it is not its own home, the packet data service node ID, its ID, and access session ID which transmitted the message are calculated (step S44), and the respective values are combined in the form of proxy state attribute format and stored in the proxy state attribute. Thereafter (step S45), the accounting request (Account-Request) message is transmitted to the broker Radius server 80 (step S46).

At this time, as shown in Fig. 5, the proxy state attribute format includes a type, a length, a packet data service node ID (PSDN ID), a RADIUS ID, a charging session ID ( Account Session ID).

The broker Radius server 80 transmits a charging request message to the home Radius server 70 using the realm of the network access confirmation attribute (step S47).

The home Radius server 70 receiving the charging request message recognizes the proxy status value in the message as the charging session ID and stores the corresponding value in the database 100 to identify the session of each charging (step S48).

In this case, charging information having the same charging session ID generated in different packet data service networks may be identified by having different packet data service node IDs. In addition, even if different packet data service nodes use the same packet data service node ID by each of the local Radius servers 40, the IDs of the Radius IDs are different from each other.

Although the preferred embodiments of the present invention have been described in detail above, it will be understood by those skilled in the art that the present invention may be modified or modified in various ways. Therefore, changes of the embodiments of the present invention will not be able to escape the technical scope of the present invention.

As described above, the present invention provides a method for identifying a charging session in a Radius server that provides authentication and authorization information of a subscriber requesting packet data services in a mobile communication packet data data network and stores charging information. When the service is provided in the visited network, the uniqueness of the billing identification for each session is guaranteed.

Therefore, it is possible to provide reliable charging information by preventing errors that may occur due to duplication of the charging session ID.

Claims (3)

Identifying charging information having the same charging session ID generated in different packet data service networks through different packet data service node IDs; When different packet data service nodes use the same packet data service node ID by each local Radius server, identifying the billing session ID using different Radius IDs. A method of identifying charging session information of a Radius server in a mobile packet data network. The method according to claim 1, Although the different packet data service nodes use the same packet data service node ID by each of the local Radius servers, the process of identifying using different Radius IDs may include: When a call occurs in a mobile communication packet data network, transmitting a charging request message to a local Radius server by assigning a charging session ID for the generated call; Receiving, by the local Radius server, the billing request message by using a realm of a network access check attribute to determine whether the local Radius server is home or not; If it is not its own home, calculating a packet data service node ID, its own ID, and an access session ID that transmitted the message, combining the packet data service node ID into a proxy state attribute format, and storing it in a proxy state attribute format; The broker Radius server receiving the charging request message transmits the charging request message to the home Radius server using the realm of the network access confirmation attribute; And receiving the billing request message by the home radio server, recognizing the proxy status value in the message as the billing session ID, and storing the value in the database to identify the session of each billing. How to identify billing session information of Radius server in data network. The method according to claim 2, The proxy state attribute format includes a type, a length, a packet data service node ID, a Radius ID, and a charging session ID.