KR100621203B1 - Method and system for controlling wireless data service for prepaid and limited subscriber - Google Patents

Abstract

The present invention performs subscriber authentication by receiving a subscriber authentication request from an AAA client, transmits an authentication result message to the AAA client using a diameter protocol, and outputs a charging log generated using the charging data received from the AAA client. When the service termination request message is received, the AAA server function unit transmits the service termination request message to the AAA client using the Diameter protocol, and the balance information or use corresponding to the service usage limit corresponding to the subscriber by receiving the billing log. Prepaid and limit subscribers, including a billing function that deducts the available amount and sends a service termination request message to the AAA server function when the service usage limit is exceeded, and a subscriber database that stores balance information or available information and subscriber information. For nothing Relates to a data service control method and system, it can provide usage convenience and versatility of the system's operating environment by applying various call control methods and limits for prepaid subscribers.

Prepaid Subscriber, Billing, Wireless Data Services, Call Control

Description

Method and system for controlling wireless data service for prepaid and limit subscribers {Method and system for controlling wireless data service for prepaid and limited subscriber}             

1 is a diagram illustrating a configuration of a mobile communication service system for processing a conventional limit subscriber.

2 is a schematic diagram of an overall system configuration for performing a method of controlling a wireless data service for a prepaid and limited subscriber in accordance with a preferred embodiment of the present invention.

3 is a block diagram showing a detailed configuration of an AAA server function module according to an embodiment of the present invention.

4 is a block diagram showing a detailed configuration of a billing function module according to an embodiment of the present invention.

5 is a diagram illustrating a format of charging data generated and provided by an AAA client according to an exemplary embodiment of the present invention.

6 is a view schematically showing the function of a billing function module according to an embodiment of the present invention.

7 is a diagram illustrating a format of CDR data generated by a billing function module according to an embodiment of the present invention.

8 illustrates the functionality of an aggregation module 415 in a billing function module in accordance with one preferred embodiment of the present invention.

9 illustrates the functionality of the Standardization Module 420 in the Billing Function Module in accordance with one preferred embodiment of the present invention.

10 illustrates the functionality of the Correlation Module 425 in the Billing Function Module in accordance with one preferred embodiment of the present invention.

11 illustrates the functionality of the PR module 435 in the Billing Function Module in accordance with one preferred embodiment of the present invention.

12 illustrates a general plan that can be applied to wireless LAN and mobile communication services.

13 is a data flow diagram illustrating a method for performing billing for use of a wireless data service by a postpaid subscriber in a subscriber management device according to an embodiment of the present invention.

FIG. 14 is a data flow diagram illustrating a method for performing charging for use of a wireless data service by a prepaid and limit subscriber in a subscriber management device according to an embodiment of the present invention. FIG.

15 is a data flow diagram illustrating an authentication session control process of a Diameter Base Engine according to an embodiment of the present invention.

16 is a data flow diagram illustrating an authentication session control process by an O & M module according to an embodiment of the present invention.

17 is a data flow diagram illustrating an authentication session control process by a prepaid subscriber processor (PrepaidController) according to an embodiment of the present invention.

FIG. 18 is a data flow diagram illustrating a method of processing an end-session-answer message received from an AAA client in a subscriber management device according to an embodiment of the present invention. FIG.

19 is a system configuration diagram illustrating a whole system from a network management point of view according to an embodiment of the present invention.

<Explanation of symbols for the main parts of the drawings>

115: base station transceiver system (BTS)

120: base station controller (BSC)

125: MSC (Mobile services Switching Center)

130: packet data serving node (PDSN)

135: AAA server (Authentication, Authorization and Accounting Server)

140: Usage Data Aggregator (UDA)

145: Service Control Point (SCP)

150: System Activation System (SAS)

155: Billing Mediation System (BMS)

304: Peer Handler

306: Radius peer handler (RADPeerController)

308: Charging Session Handler (AcctSessionController)

310: Prepaid Subscriber Handler (PrepaidController)

312: Authentication session handler (AuthSessionController)

314: Timer

322 Authentication Processor (NASReq)

324: Charge Processor (CCF)

326: Mobile node manager (MobileIP)

328: Diameter Application Group (External)

330: Diameter common message processing unit (Diameter Common Message Function)

332: Diameter Base Accounting Function

334: Base Application Group

342: Thread Manager

344: application register (AppListener)

346: Recv Module

348: O & M Agent

350: O & M Module

410: filtering module

415: Aggregation module

420: Standardization module

425: Correlation module

430: distribution module

435: Prepaid & Rating module

The present invention relates to a wireless data service control method and system for prepaid and limited subscribers, and in particular, by applying various call control methods to prepaid and limited subscribers, the prepaid which can provide convenience and diversity according to the system operating environment. And a method and system for controlling wireless data services for subscribers.

In general, a prepaid service in a mobile communication network refers to a service that enables a mobile subscriber to pay a predetermined amount in advance and receive a communication service within a limit of the amount paid in advance. In particular, the prepaid service that provides the packet data service is achieved through the interworking of the PDSN and the AAA server, which are the main elements of the packet data network.

1 is a diagram illustrating a configuration of a mobile communication service system for processing a conventional limit subscriber.

Referring to FIG. 1, a mobile communication service system 110 for limit subscriber processing may include a base station (BTS), a base station controller (BSC), and a switch (MSC). Center, 125), Packet Data Serving Node (PDSN: 130), AAA Server (Authentication, Authorization and Accounting Server, 135), Usage Data Aggregator (UDA: 140), Service Control System (SCP: Service Control Point, 145), System Activation System (SAS: 150), and Billing Mediation System (BMS: 155).

The initial authentication request for the limit subscriber's use of the wireless data service is initiated by the PDSN 130 sending an authentication request message 6010 to the AAA server 135.

The AAA server 135 transmits the authentication result response message to the PDSN 130 after authenticating the subscriber. At this time, the charging information for the limit subscriber who wants to use the current wireless data service is transmitted to the UDA 140 in the form of a charging log message.

In addition, the UDA 140 receives the limit rate information corresponding to the limit subscriber from the SCP 145, and performs the limit rate calculation using the received limit rate information. If a subscriber exceeding the limit is found while performing the limit rate calculation, UDA 140 sends relevant information to SCP 145, which SCP 145 disconnects from the session currently connected to MSC 125. Send an out of limit message to terminate.

The MSC 125 forwards the call abort request to the BSC 120 to stop using the limit subscriber's wireless data service (i.e., terminate the currently connected session) in response to the over-limit message received from SCP 145. do. The limiting subscriber's use of wireless data service is suspended by the BSC 120 performing a substantial session blocking task in response to a call interruption request received from the MSC 125.

In addition, the SAS 150 transmits new subscriber information to the UDA 140 when a new subscriber exists, and the BMS 155 receives a message (eg, aggregated UDR information) received from the UDA 140. Perform the settlement based on the

As such, the conventional mobile communication service system separates the UDA 140 system for performing the billing function to control the use of the wireless data service of the prepaid and limit subscribers and the additional node SCP 145 for managing the usage limit. There was a problem to be provided. This is because, when the limit subscriber uses the wireless data service over the predetermined limit, the call interruption procedure is performed without including the AAA server 135.

Accordingly, in order to solve the above problems, an object of the present invention is to present a call control method based on a diameter standard in an AAA system, thereby enabling real-time control of the use of wireless data service by a prepaid and limited subscriber. To provide a method and system for controlling wireless data services for prepaid and limit subscribers.

Another object of the present invention is to apply various call control schemes to prepaid and limit subscribers, thereby providing convenience and variety of usage according to the system operating environment, as well as prepaid and limit subscribers to enable efficient response to prepaid and limit subscribers. It is to provide a method and system for controlling a wireless data service.

Yet another object of the present invention is to pre-pay by improving the efficiency of the entire system operation by incorporating a billing and billing function in the AAA system, thereby bringing online a processing method that has been substantially performed offline by a separate billing system. And a method and system for controlling wireless data services for subscribers.

It is still another object of the present invention to provide a method and system for controlling wireless data service for prepaid and limit subscribers that can be universally applied to wireless LAN system and mobile communication service system.

In order to achieve the above objects, according to an aspect of the present invention, in the subscriber management apparatus for performing wireless data service control for prepaid and limit subscribers, receiving a subscriber authentication request from the AAA client to perform subscriber authentication and authentication results Sends a message to the AAA client using a diameter protocol, outputs a billing log generated by using the billing data received from the AAA client, and, if a service termination request message (ASR message) is received, the service termination request. An AAA server function for transmitting a message to the AAA client using the diameter protocol; The billing function unit receiving the billing log to subtract the balance information or the available amount corresponding to the service usage limit corresponding to the subscriber, and transmit the service termination request message to the AAA server function unit when the service usage limit is exceeded. ; And a subscriber database for storing the balance information or the available amount information and subscriber information, wherein the AAA client includes an access point, a packet data serving node (PDSN), a gateway GPRS support node (GGSN), and an IMS ( Provided is a subscriber management device comprising at least one of IP Multimedia Subsystem.

The AAA server function unit processes a peer-related message transmitted and received in a relationship with the AAA client, and performs a conversion between the Radius protocol and the Diameter protocol of the peer-related message. ; A billing session handler that manages a billing related message and a billing related session, wherein the billing related message comprises an ACR message and an ACA message; An authentication session handler that manages an authentication related session and sends related events and commands to the peer handler; A prepaid subscriber processor for performing call control corresponding to the subscriber and transmitting a call control command to the authentication session processor when the usage limit is exceeded; An authentication processor for processing authentication related messages and subscriber authentication, wherein the authentication related messages include an AAR message and an AAA message; A diameter common message processor for processing diameter messages corresponding to a diameter standard, wherein the diameter message includes a STR message, an STA message, an ASR message, an ASA message, an RAR message, and an RAA message; And a thread manager managing a thread used in the subscriber management device.

The charging function unit may include: a filtering module configured to receive the charging log from the AAA server function unit; A collection module for collecting session information corresponding to a wireless Internet service provided through the AAA client using the charging log received through the filtering module; A standardization module for rearranging one or more charging logs collected through the collection module according to a predetermined standardization rule; A synchronization module for synchronizing the charging logs standardized by the standardization module; A prepaid subscriber management module that monitors in real time whether the usage limit is exceeded using the charging logs collected in the collection module, and performs call control in conjunction with the AAA server function unit when the usage limit is exceeded; And a distribution module for transmitting the charging logs synchronized by the synchronization module to a backend system.

The filtering module may receive the charging log from at least one of a transmission control protocol (TCP), a user datagram protocol (UDP), and a file transfer protocol (FTP) from the AAA server function unit.

According to another aspect of the present invention, in a method for performing wireless data service control for prepaid and limit subscribers in a subscriber management device, an authentication request message for authentication of the subscriber for use of wireless data service from an AAA client through a communication network Receiving an AA-Request message; Performing authentication for the subscriber and transmitting an authentication response message (AA-Answer message) to the AAA client when the subscriber is a valid subscriber; Extracting a billing log stored in advance corresponding to the subscriber when a billing start request message (Accounting-Request (START) message) is received from the AAA client; Receiving charging data for the subscriber's use of wireless data service in correspondence with the charging data reporting interval from the AAA client; Subtracting a predetermined usage limit corresponding to the subscriber by using the received charging data; Determining whether the usage limit has been exceeded; If exceeded, generating a limit exceeded message; Sending a service termination request message (Abort-Session-Request message) corresponding to the over-limit message and converted to a diameter protocol to the AAA client; If the subscriber has not terminated the use of the wireless data service, receiving a session termination request message (Session-Termination-Request message) from the AAA client; Terminating the session corresponding to the subscriber in response to the end of use request message; And storing, according to the subscriber, a charging log included in an accounting-request (STOP) message received from the AAA client according to the subscriber. A control method is provided, and a system, apparatus, and a record carrier are provided for enabling the method of controlling the wireless data service.

According to a preferred embodiment of the present invention, in a session control method for wireless data service for prepaid and limit subscribers in an AAA server function unit, wherein the AAA server function unit is an authentication processor (NASReq), an application register unit (AppListener). And a thread manager (System Thread Pool), an authentication session handler (AuthSessionController), and a peer handler (PeerController), wherein the authentication handler generates a service termination request message (Abort-Session-Request message) to the application register. Transmitting; The application registration unit transmitting the service termination request message to the thread manager; The thread manager sending the service termination request message to the authentication session handler; The authentication session handler updating the session table and then sending a response message to the thread manager; The thread manager sending the service termination request to the peer handler; And converting the response message into a diameter message and transmitting the response message to an AAA client, wherein the peer processor provides a session control method for the wireless data service. A system, apparatus, and recording medium are provided for enabling the performance of a session control method for the same.

In this case, the session control may be performed in at least one of an authentication process and a charging process.

According to another preferred embodiment of the present invention, in a method for controlling a session for a wireless data service for a prepaid and a limit subscriber in a subscriber management device, wherein the subscriber management device manages an AAA server function and a usage limit of the subscriber. And a charging function unit, wherein the AAA server function unit includes a prepaid subscriber controller (PrepaidController), an authentication session handler (AuthSessionController), and a peer controller (PeerController)-whether the charging processor has exceeded the usage limit of the subscriber. Determining; Forwarding the session termination request to the prepaid subscriber handler if exceeded; The prepaid subscriber processor extracting an event and a primary key value corresponding to the session termination request and transferring the extracted event and primary key value to the authentication session processor; Generating, by the authentication session processor, the service termination request message (Abort-Session-Request message) by using the event and the primary key value, and updating an authentication session table (Auth-Session Table); The authentication session processor forwarding the event and the service termination request message to the peer handler; And converting, by the peer processor, the service termination request message into a diameter message and transmitting the same to a AAA client. The session control method for a wireless data service is provided. A system, apparatus, and recording medium are provided for enabling the performance of a session control method for the same.

In this case, the primary key value may be a session ID value.

According to another preferred embodiment of the present invention, in a method of controlling a session for a wireless data service for a prepaid and a limit subscriber in an AAA server function, wherein the AAA server function is an O & M agent, an authentication agent. A session handler (AuthSessionController) and a peer handler (received)-receiving a session termination request from an O & M module; Extracting, by the O & M agent, an event and primary key value corresponding to the session termination request, and transferring the extracted event and primary key value to the authentication session handler; Generating, by the authentication session processor, the service termination request message (Abort-Session-Request message) using the event and the primary key value, and updating an authentication session table (Auth-Session Table); And converting the generated service termination request message into a diameter message and transmitting the same to a AAA client, wherein the session control method for a wireless data service is provided. A system, apparatus and a record carrier are provided for enabling the performance of a control method.

In this case, the primary key value may be a session ID value.

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

2 is a diagram schematically showing the overall system configuration for performing a wireless data service control method for prepaid and limit subscribers according to an embodiment of the present invention.

2, a mobile communication service system 210 for performing a wireless data service control method for prepaid and limit subscribers according to the present invention includes an AAA client 220, a subscriber processing system 225, and a subscriber. The management device 230 is included. Of course, in addition to the mobile communication service system 210, a base station (BTS), a base station controller (BSC: base station controller), a switch (MSC: mobile services switching center), etc. will be further included, but the present invention, Since there is little relevance for the description of the features of these components will be omitted. Even if the description of the component is omitted, the entire configuration or function of the mobile communication service system 210 will be readily understood by those skilled in the art.

The AAA client 220 is a device that enables the use of prepaid and limit subscriber wireless data services. For example, the AAA client 220 includes an access point, a packet data serving node (PDSN), a gateway GPRS support node (GGSN), and an IMS ( IP Multimedia Subsystem).

The subscriber processing system 225 stores the information in the subscriber DB 240 of the subscriber management device 230 when information such as a new subscription, a subscription cancellation, or a request for changing subscriber information is received by the mobile communication service system 210. Means.

The subscriber management apparatus 230 includes an AAA server function module 235, a subscriber DB 240, and a billing function module 245.

When the prepaid and limit subscriber sends a request for new subscription or unsubscribe subscriber information change using the mobile communication terminal 105 or a notebook computer (not shown), the subscriber processing system 225 transmits the information to the subscriber management device ( Stored in the subscriber DB 240 in 230. Thereafter, when the prepaid and limit subscriber transmits the wireless data service request using the mobile communication terminal 105 or the like, the AAA client 220 transmits the authentication request to the AAA server function unit 235 in the subscriber management apparatus 230. do. The AAA server function unit 235 performs authentication for the prepaid and limit subscriber using the Diameter Protocol, and sends the authentication result information to the AAA client 220 using the Diameter Protocol. By transmitting, the prepaid and limit subscribers can use the wireless data service. In addition, the AAA server function unit 235 transmits the billing initial data for allowing the subscriber to use the wireless data service to the charging function unit 245, and the charging function unit 245 limits the wireless data service usage of the subscriber. Will be monitored for exceeding. Recognizing that the wireless data service usage limit has been exceeded, the charging function unit 245 transmits the information to the AAA server function unit 235, and the AAA server function unit 235 sends a service stop request to the AAA client 220. By sending a request to stop the wireless data service for the subscriber.

The billing function unit 245, which consists of five modules, calculates billing information for prepaid and limit subscribers who are currently using wireless data services, and provides over-limit information messages in real time for subscribers whose usage limits are exceeded. It passes to the AAA server function 235. In addition, if the user of the wireless data service is not a prepaid or limit subscriber, it is natural that the billing function for the use of the service can also be performed.

Detailed configurations of the AAA server functional unit 235 and the charging function unit 245 and detailed functions of the respective components will be described in detail with reference to the accompanying drawings.

3 is a block diagram showing a detailed configuration of an AAA server function module according to an embodiment of the present invention.

Referring to FIG. 3, the AAA server function unit 235 may be divided into three parts 302, 320, and 340 for convenience.

The first part 302 is a part that performs the logic of the Diameter Base Engine specification itself, and includes a peer handler 304, a Radius peer handler RADPeerController 306, and a charging session handler. AcctSessionController 308, prepaid subscriber handler (PrepaidController, 310), authentication session handler (AuthSessionController, 312) and timer (Timer, 314).

PeerController 304 is a module that performs the function of Diameter Peer concept, and performs basic parsing and transmission functions while processing Peer related messages (DWR / DWA, DPR / DPA). do.

The RADPeerController 306 converts Radius-to-Diameter and Diameter-to-Radius to maintain compatibility with the legacy AAA (Radius) System, and transmits and receives data with the Radius server. Perform the function. PeerController 304 and RADPeerController 306 may be implemented as one device.

The AcctSessionController 308 manages sessions related to charging related messages (Accounting Request (ACR), Accounting Answer (ACA)).

PrepaidController 310 is a module for call control of limit and prepaid users, and transmits a call control command for subscribers exceeding a usage limit to the AuthSessionController 312 through an interface with the charging function unit 245. The call control method will be described in detail later with reference to related drawings.

The AuthSessionController 312 manages a session related to authentication, and performs a function of transmitting an event (eg, a network access identifier (NAI), a server IP, etc.) and a command.

The Timer 314 performs a function of transmitting and receiving an event so as to process a time related function specified in a diameter standard.

Next, the second part 320 is a part that performs logic of a diameter application (Diameter Application) standard itself, authentication processor (NASReq, 322), billing processor (CCF, 324), mobile node manager ( The Diameter Diameter Application Group (328), including the MobileIP (326), the Diameter Common Message Function (330), and the Diameter Base Accounting Function (332). It includes the Base Application Group (334).

The NASReq 322 performs processing of related messages (AAR (AA-Request), AAA (AA-Answer)) and actual subscriber authentication processing.

CCF (Charging Control Function) 324 is a module that performs the charging function proposed by 3GPP, and performs the related charging processing function.

MobileIP 326 is a module that performs authentication function for a mobile node, and is used in a mobile IP and hand-off environment.

The Diameter Common Message Function (330) includes related messages (Session-Termination-Request (STR), Session-Termination-Answer (STA), Abort-Session-Request (ASR), It performs functions of processing ASA (Abort-Session-Answer), RAR (Re-Authorization-Request), and RAA (Re-Authorization-Answer).

The Diameter Base Accounting Function 332 performs Accounting-Request-message (ACR) and Accounting-Request-Answer (ACA) message processing functions that are processed in the base engine.

The third part 340 performs additional functions of the entire module, and includes a thread manager (System Thread Pool) 342, an application registerer (AppListener 344), a receiver (Recv Module 346), and an O & M agent (O & M Agent). 348, and O & M module 350.

The System Thread Pool Module 342 manages threads used throughout the system, thereby providing a thread pool method that can improve overall system performance.

The AppListener 344 acts as a window for the Diameter Application Groups 328 and 334 to register with the Base Engine, and is registered using a built-in list. Manage meter application groups.

The Recv Module 346 manages the Stream Control Transmission Protocol (SCTP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP) interfaces, receives messages using the System Thread Pool Module 342, and bottlenecks. It acts as a mediator so that it does not occur.

The O & M Agent 348 exists between the O & M module 350 and the subscriber management device 230, and serves to synchronize the information changed in the O & M (Operation and Maintenance) module with the internal data of the subscriber management device 230. do. The subscriber management device 230 through the O & M Agent 348 has an advantage of real-time recognition and processing of the operator's request. In addition, the O & M module 350 is largely divided into a CLI (Command Mode Interface) module and a GUI-based module, and are configured to be selectively selected and used according to the preference of the operator.

In addition, although not shown in FIG. 3, the AAA server function 235 searches for a corresponding diameter application when a service termination response message (eg, an Abort-Session-Answer message) is received, and the corresponding function. It may further include a callback handler (CallbackController, 360) for calling.

4 is a block diagram showing a detailed configuration of a billing function module according to an embodiment of the present invention, Figure 5 is a billing generated and provided in the AAA client according to an embodiment of the present invention It is a figure which illustrates the format of data. 6 is a view schematically showing the function of a billing function module according to a preferred embodiment of the present invention, Figure 7 is a billing function module according to a preferred embodiment of the present invention (Billing Function Module) It is a figure which illustrates the format of the CDR material to generate | generate. 8 is a view showing the function of the aggregation module 415 in the billing function module (Billing Function Module) according to an embodiment of the present invention, Figure 9 is a billing function unit according to an embodiment of the present invention ( The function of the standardization module 420 in Billing Function Module) is shown. 10 is a view showing the function of the Correlation Module 425 in the Billing Function Module according to an embodiment of the present invention, Figure 11 is a billing function according to a preferred embodiment of the present invention (Billing) The function of the PR module 435 in the Function Module is shown.

Referring to FIG. 4, the charging function unit 245 may include a filtering module 410, an aggregation module 415, a standardization module 420, a synchronization module 425, and a distribution. Module (Distribution module 430) and prepaid subscriber management module (Prepaid & Rating module 435).

The filtering module 410 is an interface module that receives user's billing information (ie, billing initial data) from the AAA server function unit 235. The filtering module 410 receives charging information for the subscriber who wants to use the current wireless data service from the AAA server function unit 235 by various methods such as UDP / TCP or FTP.

5 illustrates a format of charging data generated by the AAA client 220 and transmitted to the AAA server function 235 and transferred from the AAA server function 235 to the charging function 245.

Referring to FIG. 5, the billing data includes a session ID field 501, an origin-host field 502, an origin-real field 503, and a destination. Domain-Realm field 504, Accounting-Record-Type field 505, Accounting-Record-Number field 506, Charge-Application-Id field 507, Vendor-Specific-Application-Id field 508, User-Name field 509, Accounting-Sub-Session-Id field 510, Charging Session ID (Acct-Session-Id) field 511, Charging Multi-Session-Id field 512, Charging-Interim-Interval field 513, Charging Transmission Pattern It may include an Accounting-Realmtime-Required field 514, an Origin-State-Id field 515, and an Event-Timestamp field 516.

The Session-Id field 501 is a primary key value for distinguishing a call and represents information generated by the AAA client 220 and managed by the AAA server function unit 235.

Origin-Host field 502 indicates the host name of the source where the message was generated, and Origin-Realm field 503 indicates the domain name of the source where the message was generated.

The Destination-Realm field 504 indicates the domain name of the last stage to which the message should be received.

The Accounting-Record-Type field 505 has a value of any one of START, INTERIM, STOP, and EVENT, and the subscriber has started using the wireless data service (START), is still using the service (INTERIM), It is a value for determining whether to stop using the service (STOP) or request a specific service (EVENT).

The Accounting-Record-Number field 506 is used as a separator for classifying billing data generated for a specific service and session, and has a value increasing by one.

The Acct-Application-Id field 507 is a key value for distinguishing the Diameter Application in which the billing data is generated. The value is 1 (NASReq), 2 (MobileIP), 3 (Diameter Base Accounting), and optional. Number (Vendor-specific Application).

The Vendor-Specific-Application-Id field 508 is a key value that a specific vendor assigns to itself when generating a certain diameter application.

The User-Name field 509 is a key value (ID) for identifying a subscriber who is currently using a wireless data service, for example, a network access identifier (NAI), for example, joshua@ntels.com, 0111234567 @ sktelecom. com).

The Accounting-Sub-Session-Id field 510 is a value indicating a new session that depends on the Session-Id.

The Acct-Session-Id field 511 is a value used to assign a new session ID (Session-Id) when charging.

The Acct-Multi-Session-Id field 512 is a key value that can be used in a MobileIP environment. When the subscriber is given a new key value (Session-Id) at the time of hand-off, Acct- It can be applied when matching with the session ID (Session-Id) that is being used using the Multi-Session-Id.

The Acct-Interim-Interval field 513 is information indicating a period in which billing data is transmitted. For example, when the Acct-Interim-Interval value is 60, it means that billing data is transmitted every 60 seconds.

The Accounting-Realmtime-Required field 514 is information for referring to a charging data transmission pattern of the AAA client 1000. For example, if the value of the Accounting-Realmtime-Required field 514 is 'DELIVER_AND_GRANT' and the AAA client 220 has a problem sending the billing data to the subscriber management device 230, the accounting-realmtime-required field 514 sends the billing data to the redundant subscriber management device. This means to allow the transmission and use of the wireless data service. In addition, if the value of the Accounting-Realmtime-Required field 514 is GRANT_AND_STORE and there is a problem in transmitting billing data to the subscriber management device 230, it means that the use of the wireless data service is allowed but the billing data is stored. In addition, if the value of the Accounting-Realmtime-Required field 514 is GRANT_AND_LOSE and there is a problem with the charging data transmission to the subscriber management device 230, it means that the wireless data service is still allowed and the loss of the charging data is not a problem.

The Origin-State-Id field 515 is a value for checking the counterpart between the subscriber processing system 225 and the subscriber management device 230 and is incremented by 1 upon system reboot.

The Event-Timestamp field 516 indicates a time when the AAA client 220 receives an event related to the billing data.

Of course, the format of the billing data for the input data is not limited to the form shown in Figure 5, it is obvious that it can be variously modified, modified according to the purpose of the service provider.

6 schematically shows the function of the charging function 245. That is, the charging function 245 filters the charging data from the AAA client 220 (eg, PDSN) or various service nodes (eg, WAP Gateway, a plurality of service servers, etc.). After receiving the input through the generated consolidated billing data (consolidated Meta CDR), the generated consolidated billing data through the distribution module 430 backend system 440 (eg, billing system (Billing System, customer relationship) Customer relationship management (CRM) devices, enterprise resource planning (ERP) devices, and Fraud Detection & Prevention (FRAD) devices. Each back-end system 440 may use it to perform dependent supplementary services.

7 illustrates a format of the CDR data generated by the charging function unit 245, and includes information that can be used universally in a public network wireless LAN and mobile communication. The generation of the CDR data may be generated by adding additional subscriber data to the initial billing data (see FIG. 5) or may be generated by additional information processing (eg, aggregation, standardization, correlation, etc.).

Referring to FIG. 4 again, the aggregation module 415 is a module for collecting data on the corresponding session that provides the wireless data service. The aggregation module 415 may be configured to charge data in addition to a key value (eg, session-id) for distinguishing a call. Collect the data using the value of the record type included (eg START, INTERIM, STOP or EVENT). 8 schematically illustrates the functionality of the aggregation module 415. That is, the aggregation module 415 may charge based on a specific key and / or a specific rule (Aggregation Rule, Operator Rule) using the charging data received from the AAA client 220 (eg, PDSN). Generate CDR data (see FIG. 7).

In addition, the standardization module 420 performs a function of standardizing the charging data collected according to a method or rule of a desired service provider. In general, after the charging data is collected, the standardization process of the collected charging data is performed. 9 schematically illustrates the functionality of the Standardization Module 420. That is, the standardization module 420 rearranges the charging data collected through the aggregation module 415 to a key designated according to a standardization rule desired by the service provider.

In addition, the Correlation module 425 collects billing data when a particular subscriber uses various types of wireless data services or the billing data generation location is different even though the same service type is used. 11 schematically illustrates the functionality of the Correlation module 425. That is, after the operation of the Aggregation module 415 and the Standardization module 420 is completed, the CDR data (see FIG. 7) is synchronized by the Correlation module 425 (ie, the use of wireless data service of a particular subscriber). Synchronization of the billing data that is generated.

Finally, the PR module 435 is for processing the limit and prepaid subscribers, and checks in real time the degree of billing usage for the use of the wireless data service of the prepaid and limit subscribers, and when the usage limit is exceeded, the AAA server function unit 235 Call control is possible through interworking with. 11 schematically illustrates the functionality of the PR module 435. 11 illustrates a case in which a rate calculation is performed by combining two rate plans (eg, Economic, Business) and three elements (eg, Price Rate, Discount, Mileage). That is, the information on the wireless data service usage history, the specified price plan, the discount or the like of the subscriber is applied to a predetermined price reference table to calculate the rate for the corresponding subscriber, and the calculation is performed. The fee information is stored in the subscriber DB (240). In general, various rate tables may exist for a user according to a service policy, and various rate calculation methods may be applied accordingly.

12 is a diagram illustrating a general plan that can be applied to a wireless LAN and a mobile communication service.

Referring to FIG. 12, a general plan that may be applied to a wireless LAN and a mobile communication service may include a prepaid plan and a postpaid plan. Each rate system may include various methods of charging such as a flat rate plan according to time or period, a flat rate plan specifying a usage limit, and a plan based on packet usage.

FIG. 13 is a data flow diagram illustrating a method for performing billing for use of a wireless data service by a postpaid subscriber in a subscriber management device according to an embodiment of the present invention.

Referring to FIG. 13, in step 1302, the AAA server function unit 235 receives access request information from a user terminal 105 of a subscriber who has subscribed to a general plan. It is apparent that the access request information may be configured in various forms according to the service environment. For example, the information including the ID and password of the subscriber or the MAC address of the notebook computer or the MIN of the terminal may be used. Mobile identification number).

The AAA client 220 transmits an authentication request message (eg, an AA-Request message) to the AAA server function unit 235 in accordance with the access request information received from the user terminal 105 (step 1304). In this case, the AAA client 220 may include an access point, a packet data serving node (PDSN), a gateway GPRS support node (GGSN), and the like.

The AAA server function 235 performs authentication for the subscriber using the received authentication request message (step 1306), and then, if the subscriber is a normal subscriber, an authentication response message including the meaning of approval (for example, , AA-Answer message) is sent to the AAA client 220 (step 1308).

The AAA client 220 transmits an access permission message to the user terminal 105 via the communication network (step 1310). A charging start request message (eg, an Account-Request (START) message) including charging data generated by the AAA server function unit 235 is transmitted to the AAA server function unit 235 (step 1312). In addition, the AAA client 220 adds the subscriber information to the accounting session table. As such, the AAA client 220 will initiate the generation of billing data, and will continue to generate billing data and forward it to the AAA server functional unit 235 until the subscriber terminates use of the wireless data service.

The AAA server function 235 extracts the subscriber charging log (step 1314) and transmits the extracted subscriber charging log to the charging function unit 245 (step 1316). In addition, the AAA server function unit 235 not only adds the subscriber information to the charging session table, but also sets the charging data reporting interval (ie, Acct-Interim-interval). In addition, the AAA server function 235 transmits a charging start response message (eg, an Accounting-Answer message) to the AAA client 220. In the charging start response message, charging data report interval information may be included. Of course, the charging data report interval information may be included in the authentication response message (AAA message).

The billing function 245 stores the subscriber billing log received via step 1316 (step 1318).

The subscriber transmits a service use request for using a specific wireless data service to the AAA client 220 using the user terminal 105 (step 1320), and the AAA client 220 transmits the wireless data corresponding to the received service use request. Perform the service (step 1322).

Thereafter, the AAA client 220 transmits a charging performance request message (eg, an Accounting-Request (INTERIM) message) including the charging data to the AAA server function unit 235 corresponding to the designated charging data reporting interval ( Step 1324). The AAA server function 235 transmits a charging log corresponding to the charging performance request message to the charging function unit 245 (step 1326). In addition, the charging function unit 245 stores the charging log received through step 1326 to correspond to the subscriber. Steps 1324 to 1328 may be repeatedly performed until a service termination request is received from the user terminal 105 or a service disconnection is arbitrarily made.

When the AAA client 220 receives a service termination request or the like from the user terminal 105 (step 1330), the AAA client 220 sends a service termination request message (eg, a STR (Session-Termination-Request) message) in step 1332. Transfer to section 235.

The AAA server function 235 sends a service termination response message (eg, a Session-Termination-Answer (STA) message) to the AAA client 220 (step 1334). The AAA server function 235 then terminates the session for that subscriber.

Thereafter, the AAA client 220 transmits a service termination response message to the user terminal 105 (step 1336), and also to the AAA server function unit 235, a charging termination request message including the last charging data (for example, , Accounting-Request (STOP) message) (step 1338).

The AAA server function 235 transmits the subscriber billing log to the billing function 245 (step 1340), and the billing function 245 stores the received subscriber billing log (step 1342). The AAA server function unit 235 deletes the corresponding subscriber information from the charging session table after transmitting the subscriber charging log. That is, the AAA server function 235 manages a table for a corresponding session until a charging end request message is received, thereby monitoring in real time which subscriber is currently receiving a service. In addition, the AAA server function unit 235 deletes the subscriber information from the charging session table and transmits a charging end response message (eg, an Accounting-Answer (STOP) message) to the AAA client 220.

Thereafter, after a period of time (eg, one month) expires, a request for payment for the use of the subscriber's wireless data service is performed (step 1344).

14 is a data flow diagram illustrating a method for performing billing for use of a wireless data service by a prepaid and a limit subscriber in a subscriber management device according to an embodiment of the present invention.

Although not shown in FIG. 14, the process of receiving the charging log from the AAA server function 235 by the charging function unit 245 may be similarly applied to steps 1302 to 1328 and 1330 to 1342 of FIG. 13. Can be. Therefore, description thereof will be omitted. However, it is obvious that the charging function unit 245 may perform the balance deduction process using the received charging log instead of only storing the charging log.

Referring to FIG. 14, in step 1402, the charging function unit 245 uses the charging log received from the AAA server function unit 235 to determine whether the usage limit of the prepaid and limit subscriber has been exceeded. That is, the charging function unit 245 inquires the balance information of the subscriber using the charging log corresponding to the subscriber periodically received from the AAA server function unit 235 and checks whether the current service usage limit has been exceeded. Judging in real time. If the usage limit has not been exceeded, wait at step 1402. Of course, if the subscriber terminates the use of the wireless data service before the subscriber's usage limit is exceeded, the charging process may be performed by the charging method shown in FIG. 13. However, unlike the case of FIG. 13, the balance reduction operation will be made. However, if the subscriber's wireless data service usage exceeds the usage limit, proceed to step 1404 to send an over-limit message (eg, over-subscriber information) to the AAA server function 235.

The AAA server function 235 sends a service termination request message (eg, an ASR (Abort-Session-Request) message) for the user corresponding to the over-limit message received from the charging function 245 to the AAA client 220. (Step 1406). The AAA client 220 sends a service termination response message (eg, an Abort-Session-Answer message) to the AAA server function 235 (step 1408).

In addition, the AAA server function unit 235 determines whether a service termination request for the use of the wireless data service is received from the subscriber's user terminal 105 or whether the use of the service is randomly disconnected (step 1410). Of course, the step of transmitting a warning message to the user terminal 105 may be preceded so as to recognize whether the subscriber has reached the usage limit.

When the service termination request is received from the user terminal 105, the subscriber stops using the wireless data service and proceeds to step 1416, and when the service termination request is not received, proceeds to step 1412.

In step 1412, the AAA client 220 sends a usage termination request message (eg, a Session-Termination-Request (STR) message) to the AAA server function unit 235 to forcibly terminate the subscriber's use of the wireless data service. send. The AAA server function 235 sends an end of use response message (eg, a session-termination-answer (STA) message) to the AAA client 220 in step 1414 and terminates the session for that subscriber. do.

In addition, the AAA client 220 transmits a charging end request message (eg, an Accounting-Request (STOP) message) including the last charging data to the AAA server function unit 235 (step 1416).

The AAA server function 235 transmits the subscriber billing log to the billing function 245 (step 1418), and the billing function 245 stores the received subscriber billing log (step 1420). The AAA server function unit 235 deletes the corresponding subscriber information from the charging session table after transmitting the subscriber charging log. The AAA server function unit 235 deletes the subscriber information from the charging session table, and transmits a charging end response message (eg, an Accounting-Answer (STOP) message) to the AAA client 220 (step 1422). ).

15 is a data flow diagram illustrating an authentication session control process of a diameter base engine according to an exemplary embodiment of the present invention.

Referring to FIG. 15, in step 1502, an authentication processor (NASReq, 322) generates an authentication response message and transmits it to an application register (AppListener, 344). The authentication response message may be an AA-Answer message or an ASR (Abort-Session-Request) message.

The application registration unit 344 receives an authentication response message (for example, an AAA message or an ASR message) from the authentication processor 322, and transmits the authentication response message to a thread manager (System Thread Pool) 342 (step 1504). . The thread manager 342 checks logic for processing an Auth-Session in step 1506.

The logic for authentication session processing in the thread manager 342 may be configured as follows, for example.

If (LocalAction == Local)

{if (Cmd == ACA) CAcctSessionManager Function Call

    else if (Cmd == AAA) CAuthSessionManager Function Call

    else if (Cmd == ASR)

    {if (config == AcctOnly) {CAcctSessionManager Function Call

        else {CAuthSessionManagerFunction Call}

}}}

Thereafter, in step 1504, the thread manager 342 transmits an authentication response message to the authentication session handler (AuthSessionController, 312), and the authentication session handler 312 updates the session table by the FSM and then sends a response message to the thread manager. do.

In addition, the thread manager 342 transmits an authentication response message to the peer handler 304 in step 1508. In this case, the peer handler 304 may be a concept including a peer handler 304 and a Radius peer handler 306.

The peer processor 304 stores the authentication response message in the transmission queue SendQ in step 1510, converts the authentication response message into a diameter message, and then sends it to the AAA client 220 (step 1512). This completes the authentication process for the subscriber. In this case, the diameter message may be transmitted via a receiver (Recv Module) 346.

The charging session (Acct-Session) control that can occur during the performance of the charging-related function may be possible by the same or similar procedure to the authentication session control process shown in FIG.

That is, when the need for session control is recognized while performing the charging related function, the authentication handler (NASReq) 322 generates a service termination request message (eg, an ASR (Abort-Session-Request) message) and generates the generated service termination request. Send the message to the application register (AppListener, 344).

The application registration unit 344 receives the service termination request message and transmits the service termination request message to the thread manager 342. The thread manager 342 performs subscriber authentication using an authentication session processing function (see algorithm above).

Thereafter, the thread manager 342 transmits a service termination request message to the authentication session handler AuthSessionController 312, and the authentication session handler 312 updates the session table by the FSM and then sends a response message to the thread manager.

In addition, the thread manager 342 transmits a service termination request message to the peer handler 304. In this case, the peer handler 304 may be a concept including a peer handler 304 and a Radius peer handler 306.

The peer processor 304 stores the service termination request message in the transmission queue SendQ, converts the service termination request message into a diameter message, and then transmits the service termination request message to the AAA client 220 (step 1512). The subscriber's wireless data service is terminated. In this case, the diameter message may be transmitted via a receiver (Recv Module) 346.

16 is a data flow diagram illustrating an authentication session control process by an O & M module according to an embodiment of the present invention.

The authentication session control process illustrated in FIG. 16 is a call control method supported in a general O & M environment, and can be applied when an operator requests a call control function for a specific time, a specific service, and a specific user.

Referring to FIG. 16, in step 1602, the O & M module 350 transmits a session termination request to the O & M agent 348. That is, step 1602 is performed when the operator wants to perform a call control according to a specific condition.

The O & M agent 348 extracts an event and primary key (Session-Id) value corresponding to the session termination request received from the O & M module 350 (step 1604), and extracts the extracted event and primary key value from an authentication session handler (AuthSessionController). 312) (step 1606).

The authentication session handler 312 generates a service termination request message (for example, an ASR (Abort-Session-Request) message) using the received event and the primary key value, and updates the authentication session table (Auth-Session Table). (Step 1608). Thereafter, the authentication session handler 312 transmits an event and a service termination request message to a peer handler 304 (step 1610). In this case, the peer handler 304 may be a concept including a peer handler 304 and a Radius peer handler 306.

The peer processor 304 stores the received service termination request message in the transmission queue SendQ and converts the service termination request message into a diameter message (ie DiameterMsg (ASR)) (step 1612).

Thereafter, in step 1614, the peer processor 304 transmits the service termination request message converted to the diameter message to the AAA client 220. In this case, the diameter message may be transmitted via a receiver (Recv Module) 346.

17 is a data flow diagram illustrating an authentication session control process by a prepaid subscriber controller (PrepaidController) according to an embodiment of the present invention.

The authentication session control process shown in FIG. 17 is a structure that can comprehensively accommodate a call control request from the outside and shows a call control method associated with the charging function unit 245.

Referring to FIG. 17, in operation 1702, the charging function unit 245 transmits a session termination request to the prepaid subscriber processor 310. At this time, the session termination request may include a primary key (eg, Session-Id) value.

The prepaid subscriber processor 310 extracts an event and session-Id value corresponding to the session termination request received from the charging function unit 245 (step 1704), and extracts the extracted event and primary key value from the authentication session processor. To the AuthSessionController 312 (step 1706).

The authentication session handler 312 generates a service termination request message (for example, an ASR (Abort-Session-Request) message) using the received event and the primary key value, and updates the authentication session table (Auth-Session Table). (Step 1708). The authentication session handler 312 then sends an event and service termination request message to a peer handler 304 (step 1710). In this case, the peer handler 304 may be a concept including a peer handler 304 and a Radius peer handler 306.

The peer processor 304 stores the received service termination request message in the transmission queue SendQ and converts the service termination request message into a diameter message (ie DiameterMsg (ASR)) (step 1712).

Thereafter, in step 1714, the peer processor 304 sends the service termination request message converted to the diameter message to the AAA client 220. In this case, the diameter message may be transmitted via a receiver (Recv Module) 346.

18 is a data flow diagram illustrating a method of processing an end-session-answer message received from an AAA client in a subscriber management device according to an embodiment of the present invention.

18 illustrates a method of processing an ASA (Abort Session Answer) message received from an AAA client 220 for an ASR (Abort Session Request) message.

Referring to FIG. 18, in step 1802, a thread manager (System Thread Pool) 342 in the AAA server function unit 235 of the subscriber management apparatus 230 receives a service termination response message (type A) from the AAA client 220. That is, DiameterMsg (ASA)) is received. In this case, the diameter message may be received via a receiver (Recv Module) 346.

In step 1804, the thread manager 342 sends a service end response message to the peer handler 304. In this case, the peer handler 304 may be a concept including a peer handler 304 and a Radius peer handler 306.

The peer handler 304 performs a duplication check using an end-to-end value in step 1806, stores the received diameter service termination response message in the reception queue, and sends the destination host name. (Local Action) using the Destination Host and Destination Realm (Destination Realm) information, the service termination response message (that is, Abort-Session) applicable to the diameter message message in the subscriber management device 230 (Answer message). The service termination response message is then transmitted to the thread manager 342.

If the thread manager 342 determines the local action (step 1810) and satisfies the "If (LocalAction! = Local) CAgentManager Function Call", the thread manager 342 events the service termination response and the event to the callback handler 360 in step 1812. Send a message. The callback handler 360 retrieves a callback list to perform a Diameter Application search and a corresponding function call (step 1814), and sends a service end response message to a Diameter Common Message Function (Diameter Common Message Function, 330). (Step 1816) The diameter common message processor 330 performs a function corresponding to the received service termination response message (step 1818), and transmits a response message (return) to the callback processor 360 ( Step 1820. The callback handler 360 sends the received response message to the thread manager 342 (step 1822).

However, if the thread manager 342 determines the local action (step 1710) and satisfies the "If (! Base Diameter Appl.) Thread exit", the event and service conversion is terminated by the authentication session handler (AuthSessionController, 312). Send a response message (step 1824). The authentication session handler 312 updates the authentication session table based on the received service termination response message and the FSM criteria (step 1826), and sends a response message to the thread manager 342 (step 1828).

19 is a system configuration diagram illustrating an entire system from a network management point of view according to an exemplary embodiment of the present invention.

The system diagram of FIG. 19 illustrates a system diagram under a mobile IP or roaming environment, and when a user moves from a home network to a visited network, Subscriber management device 230 performs a broker (Broker, Proxy, or Relay) role in the middle and performs an authentication function. In addition, the subscriber management apparatus 230 according to the present invention is a broker (Broker, Proxy, or Translation Agent) in the middle even when a user requests a service to a legacy AAA server or a diameter server of another network in a roaming environment. ) To help perform the authentication function.

As described above, the wireless data service control method and system for prepaid and limit subscribers according to the present invention provides a call control method based on a diameter standard in an AAA system.

In addition, the present invention not only provides convenience and diversity in use according to the system operating environment by applying various call control methods to the prepaid and limit subscribers, but also enables an efficient response to the prepaid and limit subscribers.

In addition, the present invention can improve the efficiency of the overall system operation by embedding the billing and billing function in the AAA system by the online processing method that was conventionally performed offline by a separate billing system linkage.

In addition, the present invention can be widely applied to a wireless LAN system and a mobile communication service system.

Although the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention as set forth in the claims below It will be appreciated that modifications and variations can be made.

Claims (11)

A subscriber management apparatus for performing wireless data service control for prepaid and limit subscribers, Receives the subscriber authentication request from the AAA client to perform subscriber authentication, and transmits an authentication result message to the AAA client using a diameter protocol, and generates the billing data corresponding to each session ID received from the AAA client. Outputs a billing log, and when a service termination request message (ASR message) is received, transmits the service termination request message to the AAA client using the diameter protocol, and corresponds to the service termination request message from the AAA client; An AAA server function unit for receiving a service termination response message (ASA message); The billing function unit receiving the billing log to subtract the balance information or the available amount corresponding to the service usage limit corresponding to the subscriber, and transmit the service termination request message to the AAA server function unit when the service usage limit is exceeded. ; And It includes a subscriber database for storing the balance information or the available amount information and subscriber information, The AAA client includes at least one of an Access Point, a Packet Data Serving Node (PDSN), a Gateway GPRS Support Node (GGSN), and an IP Multimedia Subsystem (IMS). The method of claim 1, The AAA server function unit, A peer processor for processing a peer-related message transmitted and received in a relationship with the AAA client, and performing a conversion between a Radius protocol and a Diameter protocol of the peer-related message; A billing session handler that manages a billing related message and a billing related session, wherein the billing related message comprises an ACR message and an ACA message; An authentication session handler that manages an authentication related session and sends related events and commands to the peer handler; A prepaid subscriber processor for performing call control corresponding to the subscriber and transmitting a call control command to the authentication session processor when the usage limit is exceeded; An authentication processor for processing authentication related messages and subscriber authentication, wherein the authentication related messages include an AAR message and an AAA message; A diameter common message processor for processing diameter messages corresponding to a diameter standard, wherein the diameter message includes a STR message, an STA message, an ASR message, an ASA message, an RAR message, and an RAA message; And Thread manager that manages threads used in the subscriber management device. Subscriber management apparatus comprising a. The method of claim 1, The charging function unit, A filtering module for receiving the charging log from the AAA server function unit; A collection module for collecting session information corresponding to a wireless Internet service provided through the AAA client using the charging log received through the filtering module; A standardization module for rearranging one or more charging logs collected through the collection module according to a predetermined standardization rule; A synchronization module for synchronizing the charging logs standardized by the standardization module; A prepaid subscriber management module that monitors in real time whether the usage limit is exceeded using the charging logs collected in the collection module, and performs call control in conjunction with the AAA server function unit when the usage limit is exceeded; And Distributed module for transferring the charging logs synchronized by the synchronization module to a backend system Subscriber management apparatus comprising a. The method of claim 3, The filtering module receives the billing log from the AAA server function unit using at least one of Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and File Transfer Protocol (FTP). . delete delete delete A method for controlling a session for a wireless data service for a prepaid and limit subscriber in a subscriber management device, wherein the subscriber management device includes an AAA server function and a billing function for managing a usage limit of the subscriber; The functional unit includes a prepaid subscriber handler (PrepaidController), an authentication session handler (AuthSessionController), and a peer handler ( Determining, by the billing processor, if the usage limit of the subscriber has been exceeded and, if exceeded, forwarding a session termination request to the prepaid subscriber processor; The prepaid subscriber processor extracting an event and session ID value corresponding to the session termination request and transferring the extracted event and session ID value to the authentication session processor; Generating, by the authentication session processor, the service termination request message (Abort-Session-Request message) by using the event and the session ID value, and updating an authentication session table (Auth-Session Table); The authentication session processor forwarding the event and the service termination request message to the peer handler; And The peer processor includes converting the service termination request message into a diameter message and transmitting the converted message to an AAA client. And a service termination response message (Abort-Session-Answer message) corresponding to the service termination request message is received from the AAA client. delete A method for controlling sessions for wireless data service for prepaid and limit subscribers in an AAA server function, wherein the AAA server function includes an O & M agent, an authentication session handler, and a peer controller. Contains Receiving a session termination request from an O & M module; Extracting, by the O & M agent, an event and session ID value corresponding to the session termination request, and transferring the extracted event and session ID value to the authentication session handler; Generating, by the authentication session processor, the service termination request message (Abort-Session-Request message) using the event and the session ID value, and updating an authentication session table (Auth-Session Table); And And converting the generated service termination request message into a diameter message and transmitting the same to a AAA client. And a service termination response message (Abort-Session-Answer message) corresponding to the service termination request message is received from the AAA client. delete

Images