KR102096442B1 - Apparatus for managing session of Always On Devices and method thereof - Google Patents

Abstract

The present invention discloses a session management device and a session management method for dividing and managing a session of a persistent connection terminal every period. The session management apparatus according to the present invention is configured to receive a longest session period of a continuous connection terminal and a longest session period. Longest session period setting unit for setting; A message receiving unit for receiving a billing message; A session dividing unit for dividing a session of the persistent connection terminal based on the set longest session period and generating identification information of each divided session; And a session management unit that calculates the usage amount for each divided session based on the received billing message and matches and stores the identification information. According to the present invention, the persistent session connection of the persistent connection terminal is divided every set period, and the management of the usage and billing is synchronized with the management of the divided session to clarify the management.

Description

Apparatus for managing session of Always On Devices and method thereof

The present invention relates to a technique for managing a session of a persistent connection terminal, and more particularly, to a session management device and a session management method for dividing the session of the persistent connection terminal every period, and accumulating usage for each divided session unit. will be.

Among terminals that receive network service from a communication company, there is a terminal that is always connected without terminating access to the network, and such a terminal is referred to as an Always On Devices. A persistent connection terminal is a terminal that is assigned a unique public IP address and session through a communication subscription line, and means a terminal that is always connected to a network, such as a router on a wired Internet.

1 is a schematic configuration diagram of a conventional general network control system 100.

The network control system 100 includes a user terminal 11 using a network service, a wired / wireless router 12 providing network service to the user terminal 11, a NAS 13 providing network service to the wired / wireless router 12, and It comprises a AAA (14) to receive and process the session / billing message from the NAS (13).

A persistent connection terminal such as a wired / wireless router 12 connects to an access network, receives a session from the NAS 13 corresponding to a network access server, and connects to the home user terminal 11 through the assigned session. Provide services. The user terminal 11 such as a PC / IP TV / smartphone is connected to the router 12 by wire or wireless. Therefore, in the network of the user's premises, the wired / wireless router 12 is always connected to the access network, and for the connection session of the wired / wireless router 12, the NAS 13 continuously provides a service by creating a charging session for the premises service. The NAS 13 generates the corresponding charging information and transmits it to the AAA 14 corresponding to the authentication server to link the charging information. The AAA 14 processes the authentication of the router 12, and responds to the NAS 13 with the result of the authentication process.

The message for billing is generated based on the usage of the indoor terminal 11 measured by the NAS 13, and is managed by three types of billing messages: start / stop / interim. The NAS 13 transmits three messages to the AAA 14 using RADIUS or Diameter protocols. The Start message is information indicating that a session has been started, and usage and usage time will start at 0, and will be managed by specifying the session ID for the new session. The Stop message informs the AAA 14 that the session has been terminated, including information on the total usage and usage time until the end of the session.

The interim message is a charging message that is periodically generated for the loss of the message and the control according to the short-term usage during the duration of the session. Interim messages are generally generated for each specific cycle (for example, 1 hour, 12 hours, 24 hours, etc.), usage, or for each of the cycles in which the two are combined + the usage, such as usage and usage time during the cycle Inform the change. In a special case, an interim message is sometimes used to notify the change immediately when a major event in the user session occurs, such as a change in the user IP.

Here, the charging information for the usage-based control so far is generated and charged and controlled in the form of CDR (Charging Data Records). In the existing volume-based products, the CDR is based on processing for a predetermined session. However, in the situation that the number of continuous connection terminals that are being progressed on a yearly basis exceeds the seconds, minutes, and hours of use of a session, the termination of the session does not occur in the past, and thus the charging process due to the termination of the session is processed. Event is not fired.

That is, the existing charging and control method is a form in which a session is generated to perform control while using the session, and the charging is processed after the session ends. However, in the situation in which the usage time of a session is progressing on an annual basis beyond the seconds, minutes, and time units, the termination of the session is delayed without delay in the past based on the CDR.

Korean Registered Patent 10-1126990 (2012.03.27.)

An object of the present invention is to provide a session management apparatus and a session management method for managing a process of dividing session management for each period and accumulating usage for each divided session for the persistent connection terminal. Is done.

The session management apparatus for managing a session of a persistent connection terminal according to the present invention for solving the above technical problem includes: a longest session period setting unit for setting a longest session period for a charging criterion of a persistent connection terminal; A message receiving unit receiving a charging message for the persistent connection terminal; A session dividing unit for dividing the session of the persistent connection terminal and generating identification information of each divided session based on the longest session period; And a session management unit that calculates the usage amount for each divided session based on the billing message and matches and stores the identification information.

According to an aspect of the present invention, the session division unit, after starting a session based on a start charging message received by a network connection of the persistent connection terminal, references the intermediate charging message received immediately before the end of the longest session period. Split the session into.

Here, the session management unit calculates usage from all billing messages received within the longest session period for each divided session.

According to another aspect of the present invention, the session partitioning unit starts a session based on a start charging message received by a network connection of the persistent connection terminal, and then based on an intermediate charging message received immediately after the end of the longest session period. Split the session.

Here, the session management unit calculates usage from all billing messages received within the longest session period and the intermediate billing message received immediately after the end of the longest session period for the first split session, and the longest session period from the second split session The usage amount is calculated from the charging message from the second intermediate charging message received within to the intermediate charging message received immediately after the end of the longest session period.

Preferably, the session division unit extracts session information from the billing message and adds a sequence to the extracted session information to generate identification information of each divided session.

Here, the session management unit calculates the usage amount of the one line by summing the usage of each of the plurality of persistent connection terminals connected to one line.

Furthermore, the session management apparatus provides basic service for a persistent connection terminal having a simultaneous connection number equal to or less than a preset number on one line, and quality of the basic service for a persistent connection terminal concurrently connecting the preset number of connections. In addition, it further includes a session access limiter to limit the provision of degraded services.

Here, the session access limiter restores the quality of service of the persistent connection terminal providing the degraded service to the basic service when a connection termination occurs among the persistent connection terminals providing the basic service.

Furthermore, a session connection limiter for limiting the provision of a deteriorated service compared to the quality of the basic service is further provided for providing a basic service for a persistent connection terminal pre-registered in one line and for a persistent connection terminal not previously registered in one line. do.

In order to solve the above technical problem, a session management method for managing a session of a persistent connection terminal according to the present invention includes setting a longest session period for a charging criterion of a persistent connection terminal in a session management method in a session management device. ; Receiving a billing message for the persistent connection terminal; Dividing a session of the persistent connection terminal based on the longest session period and generating identification information of each divided session; And calculating a usage amount for each of the divided sessions based on the billing message, and matching and storing the identification information.

According to an aspect of the present invention, a control criterion for managing and charging a divided session is provided to a persistent connection terminal, and session control and usage are collected by processing session management and usage management according to session division every period set in the control criterion And it is possible to manage the network service that the actual control of the billing process is matched.

Since session control and billing of usage are forcibly generated by the set control criteria, it is easy to manage the service history, and it is possible to respond to customer claims or service confirmation requests through a history inquiry with a clear standard.

The control criteria can manage the service of the network according to various settings such as usage and daily, so that when the conditions set in the control criteria are satisfied, corresponding session interruption and traffic control can be controlled.

The following drawings attached to the present specification illustrate preferred embodiments of the present invention, and serve to further understand the technical idea of the present invention together with the detailed description of the invention described below, and therefore, the present invention is described in such drawings. It should not be interpreted as being limited to.
1 is a schematic configuration diagram of a conventional general network control.
2 is a schematic configuration diagram of a session management system according to an embodiment of the present invention.
3 is a schematic internal structure diagram of the session management apparatus of FIG. 2.
4 is a schematic flowchart of a process in which the session management apparatus of FIG. 2 divides a session by day.
FIG. 5 is a schematic flowchart of a process in which the session management apparatus of FIG. 2 manages usage for a plurality of persistent connection terminals.
FIG. 6 is a schematic flowchart of a process in which the session management apparatus of FIG. 2 provides a rate limiting service to a persistent connection terminal connected over a session.
FIG. 7 is a schematic flowchart of a process in which the session management apparatus of FIG. 6 returns to the basic service for a persistent connection terminal connected over a session.
8 is a schematic flowchart of a process in which the session management apparatus of FIG. 2 provides a rate limiting service to an unregistered terminal.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, the terms or words used in the present specification and claims should not be construed as being limited to ordinary or lexical meanings, and the inventor appropriately explains the concept of terms in order to explain his or her invention in the best way. Based on the principle that it can be defined, it should be interpreted as meanings and concepts consistent with the technical spirit of the present invention.

Therefore, the embodiments shown in the embodiments and the drawings described in this specification are only the most preferred embodiments of the present invention and do not represent all of the technical spirit of the present invention, and thus can replace them at the time of application. It should be understood that there may be equivalents and variations.

2 is a schematic configuration diagram of a session management system 200 according to an embodiment of the present invention.

The session management system 200 according to an embodiment of the present invention has the constituent parts 21 to 24 corresponding to the constituent parts 11 to 14 of the network control system 1 of FIG. 1, and the session management device 25 ).

The session management device 25 controls the division and charging of the session against the persistent connection terminal 22 such as a router. The billing message (Account Request (Start, Interim, or Stop)) of usage information based on the protocol of RADIUS or Diameter generated by the NAS 23 and sent to the AAA 24 is a session management device from the AAA 24 by interworking. (25). The session management device 25 divides the session of the persistent connection terminal 22 based on the received charging message, and collects / manages the usage of the divided session. For reference, usage data is included for Interim and Stop among billing messages. The amount of usage included refers to the amount of data and packets that the persistent connection terminal 22 communicates through the assigned session.

3 is a schematic internal structural diagram of the session management device 25 of FIG. 2.

The session management apparatus 25 according to an embodiment of the present invention includes a longest session period setting unit 251 for setting the longest session period, a message receiving unit 252 for receiving a billing message based on the session usage, and the longest session It includes a session division unit 253 for dividing a session for each cycle of and a session management unit 254 for calculating and storing the usage of the divided session. In addition, the session management device 25 is configured to include a session connection limiter 255 to limit the number of sessions available for simultaneous access.

The longest session period setting unit 251 sets the longest session period of the persistent connection terminal 22. The persistent connection terminal 22 is continuously connected without the session established once. In order to divide the continuously connected sessions and manage the divided sessions in regular periodic units, the longest session period setting unit 251 records and sets the period in which the longest session set by the administrator is allowed in the DB.

Here, the period may be varied and there is no particular limitation. For example, if the longest session period setting unit 251 is set to a cycle that arrives every 24 hours starting at 0 o'clock, a new cycle starts every 0 o'clock every day, and the longest session is allowed only for 24 hours of the period, beyond 24 hours There is no persistent connection, and the session is split.

The message receiving unit 252 receives a billing message of a session based on usage generated by the NAS 23 through the AAA 24. The received charging message follows RADIUS or Diameter protocol and is divided into Start, Interim and Stop messages. When the persistent connection terminal 22 accesses the network and receives a public IP address, the start message is generated once as the first charging message informing the creation and start of a session by network access. The Interim message is an intermediate charging message that is generated at regular intervals while the session of the persistent connection terminal 22 that is connected to the network is maintained. The Stop message is generated once as the last charging message informing the end of the session by the end of the network connection of the persistent connection terminal 22.

The session dividing unit 253 maintains the communication connection of the persistent connection terminal 22 while maintaining the session of the persistent connection terminal 22 that is continuously connected for each arrival of the period set by the longest session period setting unit 251. Split into split sessions. When the cycle arrives, an event, timer, etc., of the arrival of the cycle may occur. That is, when the session dividing unit 253 detects the arrival of a cycle, the currently connected session is divided into a previous split session and a new split session.

For reference, the session division unit 253 logically divides the session management in the state in which the physical communication connection state generated by the persistent connection terminal 22 is maintained, terminates the previous division session, and creates a new division session. To create. Then, the persistent connection terminal 22 is divided and managed by the session unit logically by the session division unit 253. That is, the physical session of the persistent connection terminal 22 is maintained as long as the network connection of the persistent connection terminal 22 is not terminated, and the session management device 25 logically establishes a session of the persistent connection terminal 22. It is divided and managed.

Specifically, the session division unit 253 generates start information of the first division session for the Start billing message received through the message reception unit 252 and records it in the session DB 201. Subsequently, when an interim message is periodically received through the message receiving unit 252, the session division unit 253 records intermediate information of the duration of the session in the session DB 201. If the Stop message is received by the end of the network connection of the persistent connection terminal 22, the session division unit 253 records the session termination information in the session DB 201.

Here, the session dividing unit 253, when receiving the start message, when the preset longest session period ends and detects the start of a new longest session period, the session division unit 253 refers to the start time of the new period (in other words, the end time of the existing period). In this case, the session is divided based on the time point of the interim message received immediately before or the interim message received immediately after. The reason for dividing the session based on the reception time of the interim message immediately before or after the cycle, not the start time of the cycle, is that the management processing of session, usage, and charging is synchronized by the charging message Interim. Therefore, the session division unit 253 divides the session based on the interim message immediately before or after the start of the cycle to maintain the synchronization processing based on the billing message.

For example, if the cycle starts every 12 o'clock at midnight on a daily basis, after the period starts at 12 midnight, the session divider 253 first receives the last interim message before 12 o'clock or after 12 o'clock. According to the splitting time of the session corresponding to the time when the interim message received is received, the previous splitting session is terminated and the splitting of the session creating a new splitting session is processed. By the session division processing, the session division unit 253 records the time information at the time of the session division into the session DB 201 at the end time of the previous split session and the start time of the new split session. Of course, when the stop message is received, the session division unit 253 ends the session division processing.

Here, the session dividing unit 253 identifies each split session in a manner that the session ID is the same and the sequence is incremented and added each time a first split session is created when a start message is received and a subsequent split session is generated. The information is generated and recorded in the session DB 201 together with the start time of the divided session. In addition, the session division unit 253 additionally records the end time in the session DB 201 at the end of each divided session. Then, the session of the persistent connection terminal 22 is managed by being divided into a previous session and a new session, with the latest billing message reception time as the splitting time at the start of the cycle. The new splitting session continues and when the cycle arrives, it becomes the old splitting session after termination.

The session management unit 254 calculates the usage of each divided session, and stores identification information of the divided session and the calculated usage information in the usage DB 202.

Specifically, when a start billing message is received through the message receiving unit 252, the session manager 254 initializes the usage information of the first split session and records it in the usage DB 202 together with the identification information of the split session. Thereafter, whenever an interim message is periodically received in the first split session through the message receiving unit 252, the session manager 254 extracts usage information from the interim message and uses the extracted usage information as the total usage of the split session. The accumulated usage information and the accumulated usage information are recorded in the usage DB 202 together with the identification information of the divided session. If a stop message is received by the end of the network connection of the persistent connection terminal 22, the session manager 254 uses the usage information extracted from the stop message in the usage DB 201 and the total usage information accumulated in the current split session. Is recorded in the usage DB 202.

Here, the session management unit 254, for each split session generated after the first split session, when the previous split session ends, the total usage accumulated from the start interim message of the previous split session to the last interim message is the previous split session. It is stored in the usage DB 202 as the total usage. In addition, the session manager 254 initializes the usage information of the new split session and stores it in the usage DB 202 together with the identification information of the new split session. Subsequently, if the message receiving unit 252 receives the Interim message every predetermined period while the new split session continues, the session management unit 254 records usage information and accumulated usage information extracted from the Interim message in the usage DB 202 do.

Since the charging can be calculated by using the split session information and usage information that are synchronized and managed based on the interim message that is periodically generated in the process of the continuous connection, the continuous connection terminal 22 is also billed according to the periodic session management and the usage collection in parallel. Imposition becomes possible. As the management unit becomes clear, when various claims are filed, the cause of the claim is analyzed and resolved through the DB.

For convenience of description, hereinafter, it is assumed that the session is split when the first Interim charging message is received after one cycle is changed every 12 midnight, while the communication of the persistent connection terminal 22 is continuously connected, after 0 o'clock every day When the first Interim message of the persistent connection terminal 22 is received, the session division unit 253 records the end information of the previous day divided session and the start information of the same day divided session in the session DB 201. In addition, the session manager 254 records the total usage of the previous day's divided session and the initialized usage of the same day divided session in the usage DB 202. Then, from the second split session corresponding to the second day, the accumulated usage from the second interim message received within the longest session period to the interim message received immediately after 0 o'clock on the third day is the total usage of the second session (1 day). It becomes.

The session connection limiter 255 limits the number of sessions according to the connection of the plurality of persistent connection terminals 22 simultaneously connected to one line. Of course, the continuous connection terminals 22 simultaneously accessing one circuit are assigned a unique session as terminals having different public IP addresses. The plurality of terminals connected to the indoor wired / wireless router and assigned a private IP address is not the persistent connection terminal, but the wired / wireless router assigned the public IP address is the continuous connection terminal 22. For example, when a plurality of wired / wireless routers are used at home, the plurality of wired / wireless routers may be continuous connection terminals 22 simultaneously connected. Alternatively, when one wired / wireless router and the terminal are simultaneously connected to one circuit and are respectively assigned a public IP address, the two devices may be the continuous connection terminal 22.

The limit of the number of sessions guarantees the quality of the communication speed determined according to the basic service for the persistent connection terminal 22 in which the session is set below the number of sessions set by the session access limiter 255. However, for the persistent connection terminal 22 that is requested to establish a session in excess of the set number of sessions, session access is allowed with the quality of the rate limiting service having a communication speed lower than the communication speed of the basic service.

On the other hand, it is possible to manage the simultaneous connection of the persistent connection terminal 22 through various service degradation methods in addition to the speed limit service. For example, the session access limiter 255 can perform control according to a policy such as redirecting to a page notifying of excessive use of the persistent connection terminal 22 requesting network access or blocking access. Do.

When the number of sessions is set to n-1 (n> 2) in the rate limiting service, the session access limiter 255 connects to the persistent connection terminal 22 requesting session access until the number of sessions becomes n-1. Default service. When the n-th session access is requested, the session access limiter 255 sets the rate limiting service to the requested persistent connection terminal 22. Then, the NAS 23 provides a network service at a communication speed according to the quality of service set for the session connection request of the persistent connection terminal 22.

Here, the session connection limiting unit 255 provides a sustained connection terminal that is provided with a basic service while providing a rate limiting service to the persistent connection terminal 22 connected since the nth time exceeding a predetermined number of sessions n-1 ( When the session of 22) ends, the n-th persistent connection terminal 22 is switched from the rate limiting service to the basic service to improve the speed quality. That is, the session access limiter 255 provides the deterioration quality service (eg, rate limiting service, redirect service and access blocking service, etc.) provided to the nth persistent connection terminal 22 as a basic service (eg, speed quality recovery, redirect) Release and allow access, etc.).

In addition, the session access limiter 255 may set the quality of the basic service only for the pre-registered persistent connection terminal 22 after registering the information of the persistent connection terminal 22 receiving the provision of the basic service. That is, the unregistered terminal is provided with a deteriorated quality service compared to the basic service.

Of course, the session access limiter 255 may manage the session by simultaneously limiting the number of sessions and limiting the number of registered terminals. The session access limiter 225 receives information on the number of sessions n-1 allowed for the basic service and the persistent connection terminal 22. The session access limiter 225 may set the quality of the basic service to the persistent connection terminal 22 only until the number of sessions n-1 is reached, for the previously registered persistent connection terminal 22 only. Of course, the session access limiter 255 sets the quality of the rate limiting service for the n-th connection and the unregistered persistent connection terminal 22 after the number of sessions exceeded.

4 is a schematic flowchart of a process in which the session management device 25 of FIG. 2 divides a session by day. When at least one persistent connection terminal 22 is connected to one line, a session is divided and processed for each persistent connection terminal 22, and this embodiment with reference to FIG. 4 is one continuous connection terminal for one line Suppose (22) is connected.

In the session management device 25, a cycle of the longest session is set in order to generate charging reference data for the persistent connection terminal 22. When the period is set, the session and the usage amount of the continuous connection terminal 22 are divided and managed based on the time of reception of the latest billing message of the period.

"Reference time # 1" is the start time of the first cycle, and reference time # 2 is the start time of the second cycle. "Reference time # 1" is 00:00 on August 1 and "Reference time # 2" is 00:00 on August 2 (or 24 hours on August 1).

By the network connection of the persistent connection terminal 22, the session management device 25 receives the "Start" billing message from the AAA 24, and adds sequence information (new session starts with Seq: 1) to the session ID. To generate identification information of the divided session, and store the generated divided session identification information in the session DB 201 (S41). Here, the session management device 25 extracts the session ID from the "Start" billing message, and adds the sequence information "Seq: 1" identifying the split session to the extracted session ID to generate the split session identification information.

After the session is created, the session management device 25 receives the "Interim" billing message from the AAA 24 every predetermined period. Each time the "Interim" message is received, the session management device 25 stores the session information of the message in the session DB 201, and accumulates and stores the usage information of the message in the usage DB 202.

Thereafter, when the reference time is changed to “reference time # 2”, the session management device 25 receives the first “Interim #n” message coming after the reference time # 2, and the previous session (session ID + ”Seq: 1 ") Is terminated, and the accumulated usage in the previous session (session ID +" Seq: 1 ") until the point of receipt of the message is recorded in the usage DB 202 as the total usage corresponding to the previous session (S42). The time when the "Interim #n" message is received is the end of the previous day's usage and the start of the today's usage.

When the previous split session ends, the session management device 25 adds sequence information "Seq: 2" identifying the new split session to the session ID to generate identification information of the new split session and records it in the session DB 201 From then on, incoming usage is accumulated for a new split session (session ID + "Seq: 2") and recorded in the usage DB 202 (S43). End of the session (S42) and creation (S43) is to logically divide the session that is continuously connected every session period. Here, the usage amount of the portion shown by hatching indicates that it is processed as used for "reference time # 1" even though the usage amount used for "reference time # 2" is included.

Subsequently, if the usage accumulated in the new split session (session ID + "Seq: 2") is terminated through the stop message of the account request, the session management device 25 uses the usage up to the end of the new split session (session ID + The session is terminated by accumulating with the usage of "Seq: 2" (S44).

Through the above session management, the session management device 25 manages the session of the persistent connection terminal 22 as a divided session (eg, 0 to 24 hours per day) divided every period to manage sessions and calculate daily usage. And billing calculations in synchronization.

FIG. 5 is a schematic flowchart of a process in which the session management apparatus 25 of FIG. 2 manages usage for a plurality of persistent connection terminals 22, and a plurality of persistent connection terminals having different public IP addresses are connected to one line. This is an embodiment of managing the usage of multiple sessions on a line-by-line basis.

A service control policy for a plurality of persistent connection terminals 22 having different public IP addresses according to a communication subscription line of one line can be managed as one. Each persistent connection terminal 22 has a MAC address that uniquely identifies the terminal. When the persistent connection terminal 22 with the MAC address of "MAC1" accesses the network, the session management device 25 receives the "Start" message from the AAA 24, extracts the session ID from the Start message, and then performs the sequence. ) To generate a number and store the combined value of the session ID and the sequence number in the session DB 201 as session identification information of the persistent connection terminal 22 having the MAC address of "MAC1", corresponding to the generated session identification information The usage information is initialized and stored in the usage DB 202 (S51).

While the persistent connection terminal 22 of "MAC1" is connected to the session, the session management device 25 periodically receives an "Interim" message, and receives a message about session information in the session DB 201 at each time of receiving the charging message. The information is updated and the usage amount is accumulated in the usage DB 202 (S52).

Here, when the persistent connection terminal 22 with the MAC address of "MAC2" accesses the network, the session management device 25 receives the "Start" message of "MAC2" from the AAA 24, and the session ID in the Start message. After extracting and generating a sequence number, the value that combines the session ID and the sequence number is stored in the session DB 201 as session identification information of the persistent connection terminal 22 having "MAC2" (S53). Here, since the session ID of "MAC2" and the session ID of "MAC1" are uniquely distinguished from each other, the sequence numbers given to the persistent connection terminal 22 of "MAC1" and the persistent connection terminal 22 of "MAC2" are the same. You may do it. Accordingly, in this embodiment, the same 1 is used as the sequence number for the two persistent connection terminals.

Thereafter, the session management device 25 stores three usage amounts of "MAC1", "MAC1" + "MAC2", and "MAC2" at each time of receiving the message in the usage DB 202 (S54).

Here, the session management device 25 accumulates the usage of “MAC1” each time an Interim message is received according to the connection of “MAC1” and stores it in the usage DB 202. If “MAC2” is accessed while “MAC1” is connected, the session management device 25 uses the amount of “MAC1” + “MAC2” in the interval of the interim charging message in which “MAC1” and “MAC2” are simultaneously connected. 202). Of course, each usage amount of “MAC1” and “MAC2” is accumulated in usage DB 202. When a stop message of “MAC1” is received while in a concurrent connection, the session management device 25 stores the total usage of the corresponding session of “MAC1” in the usage DB 202. Then, while the connection of “MAC2” is maintained, the session management device 25 accumulates the usage of “MAC2” each time an Interim message is received and stores it in the usage DB 202. Then, when the three usages of "MAC1", "MAC1" + "MAC2", and "MAC2" shown are summed up, it becomes the accumulated usage of the circuit.

In the above-described embodiment with reference to FIG. 5, for each persistent connection terminal 22, the session is divided for the longest session period and the usage is accumulated for each divided session. However, as in the embodiment described with reference to FIG. For the persistent connection terminal 22, the session is divided for each longest session period, so that the usage is accumulated for each divided session, and the usage for one communication subscription line is the usage of each persistent connection terminal 22 described with reference to FIG. 5. Can be calculated in a way.

FIG. 6 is a schematic flowchart of a process in which the session management apparatus 25 of FIG. 2 provides a rate limiting service to the persistent connection terminal 22 connected over the session. This is an embodiment of providing a rate limiting service when a plurality of persistent connection terminals 22 assigned different public IP addresses are connected to one line.

When a plurality of persistent connection terminals 22 are connected to the network, the session management device 25 is required to manage a plurality of sessions at the same time. Basically, concurrent session control operates in a form of blocking access to a terminal that is accessed later at the time of authentication.

The most basic method 1 is a method of controlling the IP address connected to the corresponding physical line to one when the persistent connection terminal 22 attempts to connect to the NAS 23. That is, only one terminal can be connected to one line. However, in recent years, additional terminals other than home PCs such as routers, IP TVs, and Internet phones are rapidly increasing, and furthermore, it is not a suitable method as IP terminals are rapidly increasing due to the popularization of smart phones.

A further possible method 2 is to allow access only to sessions in which AAA 24 allows simultaneous access, and if the number is exceeded, the connection of the persistent connection terminal 22 is blocked. This is a method of performing control at the time of authentication to access the network, and is generally used for network control. That is, only one simultaneous connection of n-1 continuous connection terminals 22 is allowed on one line. If n-1 terminals are simultaneously connected, the connection of the n-th terminal is not permitted. However, the session management apparatus 25 provided by the present invention additionally allows access of the nth or later terminals.

The session management apparatus 25 allows the session connection of the persistent connection terminal 22 until the set number of sessions n-1 is reached (S61).

In the state in which the session management apparatus 25 permits simultaneous access of n-1 persistent connection terminals 22, it receives the “Start” message of the n-th terminal having a MAC address of “MACn” (S62). When the terminal “MACn” after nth or more that exceeds n-1 sessions allowing simultaneous access is accessed, the session management device 25 degrades the quality of the network to allow various deterioration quality services such as allowing access. Can provide. For example, as a speed limiting service, which is one of various deteriorating quality services, a speed limiting service is limitedly provided with deteriorated quality by setting the bandwidth to 2 Mbps through network control. At this time, the session management device 25 may perform additional functions such as sending an SMS / E-mail or the like to inform the n-th and subsequent terminals through pop-up notification. Of course, if a session connection of any one of the n-1 terminals being simultaneously connected is released, the session management device 25 can improve the service with the quality of the basic service in the order of the first connection among the n-th and subsequent terminals. have.

When the "Start" message for the nth and subsequent terminals is received, the session management device 25 transmits a "CoA" (Change of Authorization) for session control (S63). The transmitted "CoA" is received by NAS 23 via AAA 24.

The NAS 23 provides a rate limiting service in which quality is deteriorated at a limited speed by lowering the "QoS" to the quality of the basic service to the nth and subsequent persistent connection terminals 22 requesting access (S64).

7 is a schematic flowchart of the process of returning to the basic service for the persistent connection terminal 22 connected to the excess session in FIG. 6. This is an embodiment of providing a rate limiting service when a plurality of persistent connection terminals 22 assigned different public IP addresses are connected to one line.

In the process of providing the basic service quality for only n-1 session accesses, the session management device 25 receives a “Start” message according to the session access of the nth or more terminals (S71).

The session management device 25 transmits a “CoA” for session control of the rate limiting service to the “Start” message for the nth or more terminals (S72). The transmitted "CoA" is received by NAS 23 via AAA 24.

The NAS 23 provides a rate limiting service corresponding to the received “CoA” to the persistent connection terminal 22 (S73).

Here, when the persistent connection terminal 22 of “MAC2” among the continuous connection terminals 22 connected to the 1st to n-1th existing connections is terminated, the session management device 25 responds to the termination of the connection. Stop "message is received (S74).

The session management device 25 transmits a “CoA” for session recovery, which increases the quality of the basic service, to the n-th terminal having the MAC address of “MACn”, which has been provided with a rate limiting service with deterioration quality (S75). The transmitted "CoA" is transmitted to the NAS 23 via the AAA (204).

The NAS 23 improves the communication speed with the quality of the basic service for the n-th terminal having the MAC address of “MACn”, and transmits the processing result to the session management device 25 through the AAA 24 (S76). .

FIG. 8 is a schematic flowchart of a process in which the session management device 25 of FIG. 2 provides a rate limiting service to the unregistered persistent connection terminal 22.

The session management device 25 provides a basic service only to the pre-registered persistent connection terminal 22 (S81). Here, the n-1 persistent connection terminals 22 from the pre-registered "PC 1" to "PC n-1" are provided with basic services. Therefore, the preset number of sessions is filled.

Thereafter, in the state allocated to the pre-registered terminal until the n-1 th session, the persistent connection terminal 22 of “PC 2” terminates the connection and receives a “Start” message for the unregistered terminal (PC n) When (S82), the session management device 25 transmits a "CoA" for session control of the rate limiting service to the received "Start" message (S83). The transmitted "CoA" is received by NAS 23 via AAA 24.

The NAS 23 provides a rate limiting service corresponding to the received "CoA" to the unregistered persistent connection terminal (PC n) 22 (S84). That is, although the pre-registered persistent connection terminal 22 of "PC 2" terminates the connection and n-2 persistent connection terminals smaller than a preset number of sessions n-1 are connected, "PC n" is not registered. Since it is a persistent connection terminal, a speed limit service is provided. Thereafter, when the persistent connection terminal 22 of the “PC 2” reconnects, the set number of sessions remains and the persistent connection terminal 22 of the “PC 2” is a previously registered persistent connection terminal, so the session management device 25 "PC 2" provides basic services.

As described above with reference to FIG. 8, a technique for providing a basic service only for the pre-registered persistent connection terminal 22 may be combined with a technique for providing a basic service according to the number of session connections in FIG. 6. In the parallel service, the session management device 25 registers the number of sessions (for example, n-1) capable of receiving the basic service and the information of the persistent connection terminal 22. The session management device 25 provides a basic service only to the pre-registered persistent connection terminals 22 until the number of sessions is n-1. Here, not only the unregistered terminal but also the pre-registered terminal are allowed to access with the quality of the speed limit service from the nth or more connections.

For reference, among the n-th or more connected persistent connection terminals 22, the pre-registered terminal having the fastest access time is the one of the continuous connection terminals 22 in the 1 to n-1 connection as in the process of FIG. It can be restored to the basic quality of service by terminating the connection.

In the above-described embodiment, the term "~ unit" is not used as a term for a hardware classification of the session management device 2. Therefore, a plurality of components may be integrated into one component, or a component may be divided into a plurality of components. Further, the component part may mean a component part of hardware, but may also mean a component part of software. Therefore, it should be understood that the present invention is not particularly limited by the term "~ part".

Although the present invention has been described by means of limited embodiments and drawings, the present invention is not limited by this, and the technical idea of the present invention and the claims to be described below by those skilled in the art to which the present invention pertains Of course, various modifications and variations are possible within the scope of the scope.

21: user terminal 22: router
23: NAS 24: AAA
25: session management device 200: session management system

Claims (20)

delete delete A longest session period setting unit for setting the longest session period for the charging criterion of the persistent connection terminal;
A message receiving unit receiving a charging message for the persistent connection terminal;
After starting a session based on the start charging message received by the network connection of the persistent connection terminal, the session is divided based on the longest session period, and the intermediate charging message received immediately before the end of the longest session period is A session dividing unit for dividing a session by reference; And
It includes a session management unit for calculating the usage amount for each of the divided sessions based on the billing message and matching and storing identification information,
The session management unit,
A session management device characterized in that usage is calculated from all billing messages received within the longest session period for each divided session. delete A longest session period setting unit for setting the longest session period for the charging criterion of the persistent connection terminal;
A message receiving unit receiving a charging message for the persistent connection terminal;
After starting a session based on the start charging message received by the network connection of the persistent connection terminal, the session is divided based on the longest session period, but the intermediate charging message received immediately after the end of the longest session period A session dividing unit for dividing a session by reference; And
It includes a session management unit for calculating the usage amount for each of the divided sessions based on the billing message and matching and storing identification information,
The session management unit,
For the first split session, usage is calculated from all billing messages received within the longest session cycle and intermediate billing messages received immediately after the end of the longest session cycle,
From the second split session, the session management apparatus is characterized in that usage is calculated from the charging message from the second intermediate charging message received within the longest session period to the intermediate charging message received immediately after the end of the longest session period. The method of claim 3 or 5,
The session division unit,
Session management apparatus characterized in that the session information is extracted from the billing message and a sequence is added to the extracted session information to generate identification information of each of the divided sessions. The method of claim 3 or 5,
The session management unit,
Session management apparatus characterized in that the usage of each of the plurality of persistent connection terminals connected to one line is summed and calculated as the usage of the one line. The method of claim 3 or 5,
To provide a basic service for a persistent connection terminal having a simultaneous connection of a predetermined number or less on a single line, and to provide a deteriorated service compared to the quality of the basic service for a persistent connection terminal that concurrently connects in excess of the preset number. And a session connection limiting unit for limiting. The method of claim 8,
The session connection limiting unit,
A session management apparatus comprising restoring the service quality of the persistent connection terminal providing the deteriorated service to the basic service when a connection termination occurs among the persistent connection terminals providing the basic service. The method of claim 3 or 5,
It further comprises a session access limiter for limiting the provision of a degraded service compared to the quality of the basic service for a persistent connection terminal that has not been registered in advance, while providing a basic service for a persistent connection terminal that has been previously registered in one line. Session management device. delete delete In the session management method in the session management device,
Setting a longest session period for a charging criterion of the persistent connection terminal;
Receiving a billing message for the persistent connection terminal;
After starting a session based on the start charging message received by the network connection of the persistent connection terminal, the session of the persistent connection terminal is divided based on the longest session period, and identification information of each divided session is generated. Dividing the session based on the reception time of the intermediate billing message received immediately before the end of the longest session period; And
Calculating a usage amount for each of the divided sessions based on the billing message, and matching and storing the identification information;
The storing step,
A session management method characterized in that usage is calculated from all billing messages received within the longest session period for each divided session. delete In the session management method in the session management device,
Setting a longest session period for a charging criterion of the persistent connection terminal;
Receiving a billing message for the persistent connection terminal;
After starting a session based on the start charging message received by the network connection of the persistent connection terminal, the session of the persistent connection terminal is divided based on the longest session period, and identification information of each divided session is generated. Dividing the session based on the time point of receiving the intermediate billing message received immediately after the end time of the longest session period; And
Calculating a usage amount for each of the divided sessions based on the billing message, and matching and storing the identification information;
The storing step,
For the first split session, usage is calculated from all billing messages received within the longest session cycle and intermediate billing messages received immediately after the end of the longest session cycle,
Starting from the second split session, the session management method is characterized in that usage is calculated from the charging message from the second intermediate charging message received within the longest session cycle to the intermediate charging message received immediately after the end of the longest session cycle. The method of claim 13 or 15,
The generating step,
Session management method characterized in that the session information is extracted from the billing message and a sequence is added to the extracted session information to generate identification information of each of the divided sessions. The method of claim 13 or 15,
And summing the usage of each of the plurality of persistent connection terminals connected to one circuit to calculate the usage of the one circuit. The method of claim 13 or 15,
To provide a basic service for a persistent connection terminal having a simultaneous connection of a predetermined number or less on a single line, and to provide a deteriorated service compared to the quality of the basic service for a persistent connection terminal that concurrently connects in excess of the preset number. Session limiting method further comprising the step of limiting. The method of claim 18,
And recovering the service quality of the persistent connection terminal providing the deteriorated service to the basic service when a connection termination occurs among the persistent connection terminals providing the basic service. The method of claim 13 or 15,
Further comprising the step of providing a basic service for a persistent connection terminal that is pre-registered in one line and providing a degraded service compared to the quality of the basic service for a persistent connection terminal that is not registered in advance. How to manage sessions.

Images