KR20100138110A - An entry management method of binding table using multi-thread for multimedia service stablity - Google Patents

Abstract

PURPOSE: A method for managing the entry of a binding table using multi-thread for multimedia service stability is provided to generate multi-thread to manage the maintenance time of a binding table. CONSTITUTION: An entry management unit receives an entry update message from a terminal within a home network, and creates and generates the entry of a binding table according to the information included in the entry update message. A thread management unit creates a thread which manages the created entry whenever generating a new entry to the binding table. The thread management unit manages the maintenance time of the entry of the binding table by using the thread.

Description

Binding Table Entry Management using Multi-Threading to Provide Stable Multimedia Service in Home Network Environments [ANB EUNTV RMB MAAN MEVN MV ETV YG MV LBI VHD iv MV

The present invention relates to a binding table entry management method using multi-threads to provide a stable multimedia service in a home network environment. More particularly, the present invention relates to a service mobility support server for realizing multimedia service mobility using an IP router in a home network. The present invention relates to a method for preventing entry overflow of a binding table managed and controlled by an agent and managing entry retention time.

With the recent increase in the number of households with multiple PCs, the expansion of the networking digital consumer market, the demand for home entertainment, and the development of technology, multimedia streaming services such as TV, movies, dramas and music can be enjoyed in the home network. With the development, many technologies for receiving multimedia streaming service in the home network have been studied. However, there is no research on the technology for providing a seamless multimedia streaming service regardless of the user's movement by using the IP router in the home network.

In addition, by using the binding table in the IP router, even if users in the home network move between terminals in the home network, a seamless multimedia service can be provided. However, there is a problem that the binding table overflows, so that the entry can be stably maintained. Skill is essential.

Resolves the problem of binding table overflow caused by the accumulation of entries that should be deleted because entries are not deleted when the user disconnects when the user receiving the multimedia service in the home network repeats the request without the service release. We need a way to do this.

In addition, there is a need for an entry maintenance method to prevent irregular deletion of the binding table entry.

The present invention has been made to solve the above problems, the binding table entry management method using a multi-threaded to provide a stable multimedia service in a home network environment according to the invention manages the maintenance time of the binding table by creating a multi-thread The purpose is to prevent entry overflow of the binding table.

In addition, if an overflow of the binding table occurs, a normal entry may be deleted and abnormally disconnected multimedia services may occur.However, even if a user moves frequently in a home network by preventing an entry overflow, It aims to provide a stable and seamless multimedia streaming service.

In the binding table entry management method using the multi-thread of the present invention for solving the above problems, receiving an entry update message from the terminal in the home network, and generates or generates an entry in the binding table according to the information contained in the entry update message. Updating, creating a thread for managing the generated entry each time a new entry is created in the binding table, and managing the maintenance time of the entry in the binding table using the thread.

In the above configuration, the managing of the entry retention time of the binding table may include: searching for a managed entry of the thread in the binding table using a thread and extracting entry retention time data of a managed entry from a predetermined initial state. Determining whether the setting value is updated or set to a set value, and if the entry holding time data is set or updated to an initial setting value, storing the entry holding time data as a counting variable value in a storage unit, and counting stored in the storage unit. Subtracting the variable value by a predetermined size after a predetermined time, storing the subtracted counting variable value as updated entry holding time data in a managed entry of the binding table, and counting the above-described steps performed by a thread. Repeat until the value is a predetermined entry hold end value Performs can be achieved, including the step of: if the counting value of the variable a is a predetermined entry holding the end value, deleting a managed entry and deletes the thread that manages the managed entry.

Also in the above configuration, the step of managing the entry retention time,

The thread receives the entry holding time initial setting value of the managed entry and stores the counting variable value as a counting variable value, and repeatedly counts the counting variable value by a predetermined size over a predetermined time period so that the counting variable value has a predetermined entry holding end value. In this case, the management target entry may be deleted, but when receiving an entry update message for a specific entry, the counting variable value of the thread managing the specific entry may be updated to the initial entry time setting value.

In addition, in the above-described configuration, one entry is created for each user ID, and a thread is created for each managed object entry. When an entry update message is received, entries are written to the user ID information included in the entry update message and the binding table. Compares (updates) the entry in the binding table with the matching user ID if there is a matching user ID, and compares the received entry if there is no matching user ID. The new entry may be generated in the binding table according to the update message information.

In addition, in the above-described configuration, the entry update message may be received periodically from the terminal or may be received in response to the case in which the control unit transmits an entry update message transmission request to the terminal.

In addition, the IP sharing apparatus having a binding table entry management function using the multi-thread according to the present invention includes a binding table manager for generating and managing a binding table, and user information and terminal information connected to a terminal installed in a terminal in a home network. An entry manager for creating and managing an entry in the binding table, a thread manager for managing a maintenance time of the entry, and a thread for deleting the entry when the entry retention time expires, and a terminal in the home network. It includes a transmitting and receiving unit for performing the transmission and reception of the entry, the entry is generated for each user connected to the terminal, and includes an entry retention time information that can be updated, the thread is created for each managed object entry to manage each generated entry The thread is holding the entry When the counting by the retention time of the managed entry expiry may be characterized in that for deleting the entries managed.

Also, in the above configuration, the thread retrieves the entry retention time and stores it in the storage as a counting variable of the thread, and counts the value stored as the counting variable to delete the managed entry when the counting variable value reaches a predetermined entry retention end value. If the transceiver receives the binding table update message from the terminal to which the specific user is connected, the entry manager updates the entry holding time of the entry including the specific user information in the binding table to a predetermined initial value, and the thread binds. When the entry retention time of the table has been updated to a predetermined initial value, the updated entry retention time may be stored as a counting variable, and the entry retention time may be counted again.

Also, in the above-described configuration, the counting performed by the thread is to decrease the value stored in the counting variable by a predetermined amount every time a certain time elapses, and the thread is to reduce the value stored in the counting variable by the predetermined size. Each time, the entry retention time stored in the binding table may be reduced by a predetermined size.

In addition, in the above configuration, the data in the binding table includes at least one entry, and the entry includes a user ID, a service ID, an IP address of a terminal to which the user is connected, a MAC address of a terminal to which the user is connected, and an entry holding time. It can be characterized by.

According to the present invention, a multi-threaded entry in a binding table that stores location information, ID information, and service information of a user who is receiving a multimedia service while moving in a home network is managed by creating a multi-thread to manage the entry retention time of the binding table. This prevents table overflow.

In addition, if an overflow of the binding table occurs, a normal entry may be deleted and abnormally disconnected multimedia services may occur.However, even if a user moves frequently in a home network by preventing an entry overflow, It has the effect of providing a stable and seamless multimedia streaming service, and as a result, it realizes the mobility of multimedia service within the home network. It is effective to be provided.

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

1 is a detailed configuration diagram of a relationship between a service mobility support server agent and a binding table according to an embodiment of the present invention.

As shown in FIG. 1, a program module installed in a system for providing service mobility in a home network includes a service mobility support terminal agent 101 and a service mobility support server agent 102, each of which is a terminal of a home network. Is installed on the router. The service mobility support server agent 102 generates and manages a binding table. The service mobility support server agent 102 stores and manages information such as location information, ID information, service information, etc. of a user transferred from the service mobility support terminal agent.

The control functions in which the service mobility support server agent program is installed in the IP router and operate include a binding table manager for generating and managing a binding table, an entry including user information and terminal information connected to a terminal agent program installed in a terminal in a home network. It is performed through the entry management unit for creating and managing the entry in the binding table, and the thread management unit for managing and maintaining the entry of the entry to create a thread (thread) for deleting the entry when the entry retention time expires.

It also includes a control unit for transmitting and receiving the data transmission and reception with the terminal in the home network. For convenience, the service mobility support server agent performs a function performed by the binding table manager, the entry manager, the thread manager, and the transceiver controller.

2 is an operation diagram illustrating a thread's operation of an operation state change of a binding table according to an exemplary embodiment of the present invention.

When the user first connects to the service mobility support terminal agent, the service mobility support server agent adds 201 a new entry for storing the user's location information and ID information to the binding table. As an entry is added to the binding table, a thread 204 is created to manage the retention time of the entry.

Entries added to the binding table include entry duration items along with information needed for service mobility. Each time a binding table entry is added, it creates a thread that manages the retention time for that entry, and counts the remaining maintenance time at regular intervals. Each thread stores the remaining retention time of each managed entry as a counting variable value and subtracts it at regular intervals. The thread operates as many threads as the number of entries in the binding table, and when the remaining retention time of the entry counting in each thread expires, that is, when the counting variable value reaches a predetermined end value, the managed entry is deleted. The running thread itself is also removed. At this time, the counting variable value can be subtracted from the initial setting value by a predetermined size whenever a predetermined time elapses, and a predetermined end value (entry holding end value) set in advance can be set. Preferably, the counting variable is decremented by 1 every 1 second. If the counting variable becomes 0, the entry retention end value, the managed entry managed by the thread can be deleted and the thread can be terminated. have. Retrieve and update binding table entries at regular intervals while the thread is running normally.

The service mobility support terminal agent sends a binding table entry update message to the IP router on which the service mobility support server agent is installed, and the received IP router searches for the corresponding entry in the binding table and updates the entry retention time of the entry to the initial setting. (202). This initial value is a value that can be appropriately selected to keep the multimedia service stable, ensuring a minimum entry retention time. This initial setting value may vary depending on the user mobility of the home network and the network situation. For example, when the speed of adding new user entries is increased, the initial setting value that guarantees minimum entry retention time is changed to a smaller value to facilitate the deletion of unnecessary entries, thereby reducing the possibility of a binding table overflow, and the new user. If the entry addition speed becomes relatively slow, the minimum retention time of the entry can be increased by changing the initial setting value that guarantees the minimum entry retention time to a larger value.

On the other hand, when the entry retention time of a specific entry in the binding table is updated to the initial setting value, the counting variable value of the thread 204 managing the updated entry is also updated to the initial setting value.

This operation allows each thread to manage the entry retention time of its own managed entry, and remains constant unless the counting variable value of the thread becomes the entry retention end value or the managed entry is deleted.

On the other hand, if the user terminates the access to the service mobility support terminal agent normally, the service mobility support terminal sends the connection termination message to the IP router, and the service mobility support server agent accesses the binding table and binds the corresponding user ID. Delete the table entry. When an entry is deleted, the thread managing that entry is also removed.

The thread 204 managing the entry holding time of the binding table is created each time an entry is added, and as many threads as the number of the binding table entries are created and maintained.

The entry update message is transmitted by the service mobility support agent to the IP router periodically or in response to the terminal receiving an entry update message transmission request controlled by the service mobility support server agent and transmitted through the transceiver. You can also

3 is a flowchart illustrating an operation of a thread according to adding a binding table entry according to an embodiment of the present invention.

When a user who wants to receive a multimedia service in the home network initially connects, a new entry is added to the binding table (S310). When the entry is added, a thread for managing the maintenance time of the entry is generated (S320), and the thread performs an operation for entry management (S330). The thread operation for maintaining an entry will be described in detail with reference to FIG. 5. When the entry maintenance time of a managed entry expires according to the operation of the thread, the thread attempts to delete the entry, checks whether the entry has been deleted by referring to the binding table (S340), and checks that the entry has not been deleted. After the first thread is created, the operation is repeated, and if the entry is normally deleted as a result of the check, the thread is terminated (S350).

4 is a state diagram illustrating an operation of controlling an entry of a binding table according to a change in an operating state of a thread according to an embodiment of the present invention.

In the initial state of thread creation (401), it retrieves the time1 (407) value (entry holding time) initially set in the corresponding binding table entry that it wants to manage, and stores it in the time2 (406) value (counting variable value) of the thread. do.

Thereafter, the thread enters the progress state 402 to perform the expression 404 of "Time2 = Time2 -1". The above formula is preferably performed at 1 second intervals. However, it is not necessary to subtract the value of Time2 by a certain amount at regular intervals, so it is not necessary to subtract by 1, and the thread can be operated until the value of Time2 is increased from 0 until it is equal to the initial value of the entry retention time. .

The value of Time2 (406) that changes due to the thread's operation updates the Time1 (407) value of the corresponding binding table entry each time the formula (404) is executed, and searches for the Time1 (407) value in the entry to start the entry retention time. Set to Thread 2's Time2 value only when the value is updated again. This process is executed until the thread's Time2 (406) value expires (Time2 = 0).

  When the thread's Time2 (406) value expires, it enters the expiration state (403) and the thread issues a delete command for the corresponding binding table entry that it was managing. This occurs when the binding table entry update message from the service mobility support terminal agent to which the user is connected is no longer sent to the service mobility support server agent. That is, when the user terminates the connection abnormally without notifying the service connection termination normally, this is a case where the normal entry deletion process is not performed by the service mobility server agent. In order to prevent overflow of the binding table due to an increase in unnecessary entries due to such abnormal termination, it is necessary to manage the retention time of the entry.

FIG. 5 is a flowchart illustrating a detailed operation of a thread according to an embodiment of the present invention and sequentially expressing a state diagram of FIG. 4.

The initial thread is created and the created thread searches for the entry's retention time (Time1) to set the retention time of the entry it manages to the variable value (Time2) to be counted in the thread. The thread sets the initial setting value to the counting variable value (Time2) of the thread only when the first entry is created and when the retention time of the retrieved entry is updated to the entry retention time initial setting value (S510). After the delay for 1 second (S520), the thread executes the expression "Time2 = Time2 -1" (S530), and updates the value of Time2, which is a result value, to the entry time (Time1) of the entry (S540). It checks whether the counting variable Time2 has expired every one cycle of the thread's operation (S550). If it has not expired, the above operation is repeated and the entry managed by the thread is deleted (S560).

1 is a detailed configuration diagram of a relationship between a service mobility support server agent and a binding table according to an embodiment of the present invention.

2 is an operation diagram illustrating a thread's operation of an operation state change of a binding table according to an exemplary embodiment of the present invention.

3 is a flowchart illustrating an operation of a thread according to adding a binding table entry according to an embodiment of the present invention.

4 is a state diagram illustrating an operation of controlling an entry of a binding table according to a change in an operating state of a thread according to an embodiment of the present invention.

FIG. 5 is a flowchart illustrating a detailed operation of a thread according to an embodiment of the present invention and sequentially expressing a state diagram of FIG. 4.

Claims (9)

(A) receiving an entry update message from a terminal in the home network; (B) generating or updating an entry of a binding table according to the information included in the entry update message; (C) creating a thread managing the created entry each time a new entry is created in the binding table; And And (d) managing a maintenance time of an entry of the binding table by using the thread. The method of claim 1, wherein step (d) Searching for a management target entry of the thread in the binding table using the thread, extracting entry retention time data of the management target entry, and determining whether the thread is set or updated to a predetermined initial setting value; (D-2) storing the entry holding time data as a counting variable value when the entry holding time data is set or updated to an initial setting value; Subtracting a counting variable value stored in the storage unit by a predetermined size after a predetermined time and storing the subtracted counting variable value as updated entry holding time data in a management target entry of the binding table (d-3) ; And Steps (d-1) to (d-3) are repeated until the counting variable value reaches a predetermined entry retention end value, and the counting variable value is determined by the iteration. And (d-4) deleting the management target entry and deleting the thread managing the management target entry. The method of claim 1, wherein step (d) The thread receives an entry holding time initial setting value of the management target entry and stores it as a counting variable value, and repeatedly counts the counting variable value by a predetermined size for each elapse of a predetermined time to maintain the preset counting value. When the end value is reached, the management target entry is deleted. And upon receiving an entry update message for a specific entry, updating a counting variable value of a thread managing the specific entry to an initial entry time setting value. The method according to claim 2 or 3, The entry is created one for each user ID, the thread is created for each managed entry, In the step (b), when the entry update message is received, the user ID information included in the entry update message is compared with the user IDs of entries previously created in the binding table. Stable entry management of an IP router, characterized by updating an entry of a binding table having a matching user ID, and creating a new entry in the binding table according to the received entry update message information when a matching user ID does not exist. Way. The method of claim 4, wherein The entry update message is periodically received from the terminal, or a stable entry management method of the IP router, characterized in that received in response to the case in which the control unit transmits an entry update message transmission request to the terminal. A binding table manager for generating and managing a binding table; An entry manager configured to generate and manage an entry in the binding table, the entry including user information and terminal information connected to a terminal installed in a terminal in a home network; A thread manager for managing a maintenance time of the entry to generate and manage a thread for deleting the entry when the entry maintenance time expires; And Including a transceiver for transmitting and receiving data with the terminal in the home network, The entry includes entry retention time information that is generated and updatable for each user accessing the terminal, and the thread is generated for each managed entry to manage each generated entry, and the thread is an entry retention time. And sharing the management target entry when the maintenance time of the management target entry expires by counting the IP sharing device. The method of claim 6, The thread retrieves the entry holding time and stores the counting variable of the thread in a storage unit, and counts a value stored as the counting variable to delete a managed entry when a counting variable value reaches a predetermined entry holding end value. When the transceiver receives a binding table update message from a terminal connected to a specific user, the entry manager updates the entry holding time of an entry including the specific user information of the binding table to a predetermined initial value, and the thread In the home network, characterized in that if the entry retention time of the binding table has been updated to a predetermined initial value, the updated entry retention time is stored as the counting variable and counted again. IP sharing device with stable entry management. The method of claim 7, wherein The counting performed by the thread is to reduce the value stored in the counting variable by a predetermined amount every time a predetermined time elapses, and the thread is configured to bind the value whenever the value stored in the counting variable is reduced by the predetermined size. An IP sharing apparatus having stable entry management function in a home network, characterized by reducing the entry retention time stored in a table by the predetermined size. The method of claim 8, The data of the binding table includes at least one entry, wherein the entry includes a user ID, a service ID, an IP address of a terminal to which the user is connected, a MAC address of a terminal to which the user is connected, and an entry holding time. IP sharing device with stable entry management in the home network.

Images