KR100598966B1 - Method and apparatus for managing handoff among network access servers - Google Patents

Abstract

The present invention stores the first session information corresponding to the user terminal when the first terminal information update request is received from the first data service apparatus connected to the first user terminal PPP, and the second user terminal PPP connected to the second user terminal. When the second terminal information update request is received from the data service device, it is determined whether session information corresponding to the second terminal identification information exists and if the corresponding first session information exists, the first IP address and the second IP address. The present invention relates to a method and an apparatus for managing handoff between data service apparatuses that transmit a session end message to a first data service apparatus when it is determined that they are inconsistent with each other. Handoff management between data service devices using a handoff management device combined with Network Access Server Make it quick.

Handoff, Session, User Terminal, NAS

Description

Method and apparatus for managing handoff among network access servers             

1 is a diagram illustrating a connection relationship between data service devices for performing handoff according to an embodiment of the present invention.

2 is a detailed block diagram of a data communication service system for performing handoff between PDSNs according to an embodiment of the present invention.

3 is a data flow diagram for performing an inter-PDSN handoff for a user terminal in an active state according to an embodiment of the present invention.

4 is a data flow diagram illustrating a session termination procedure of an existing PDSN according to an embodiment of the present invention.

5 is a data flow diagram for performing an inter-PDSN handoff for a user terminal in a Dormant state according to another preferred embodiment of the present invention.

6 is a data flow diagram illustrating a session termination procedure of an existing PDSN according to another preferred embodiment of the present invention.

<Description of Symbols for Main Parts of Drawings>

120: data service device

130, 260: handoff management device

220a: first PCF

220b: second PCF

230a: first PDSN

230b: second PDSN

240: AAA Server

250: billing processing device

The present invention relates to a method and apparatus for managing handoffs between data service devices, and more particularly, to manage handoffs between data service devices capable of quickly processing handoffs between data service devices and suppressing unnecessary waste of radio resources. A method and apparatus are provided.

Handoff means that a particular state is maintained while the interface is changed from one entity to another.

Conventionally, handoff between packet control functions (PCF: Packet Control Function (PCF)) has been performed by a Packet Data Serving Node (PDSN), which is an upper system. The conventional handoff procedure between PDSNs is briefly described as follows.

If a user terminal that is in an active state / dormant state in a jurisdiction of a certain packet data serving node (PDSN) moves to a jurisdiction of another PDSN, the user terminal is connected to a new PDSN and a new session. Set Session and get a new IP address.

The PDSN, which has previously established a session with the user terminal, deletes the session with the user terminal upon expiration of a preset PPP inactivity timer. In general, the expiration of the PPP inactivity timer is monitored by the PDLP's MLP board, and the PPP call is stopped when the PPP inactivity timer expires. That is, the MLP board is a user terminal at each stage of PPP negotiation (Link Control Protocol (LCP), Password Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP), IP Control Protocol (IPCP), and Compression Control Protocol (CCP)). After sending a specific message, the timer must be registered to handle the situation when there is no response.If the call is opened after PPP negotiation, set the PPP Inactivity timer to stop the PPP call if there is no data sent and received by that time. To perform the function.

As described above, the conventional PDSN handoff method in which the PPP inactivity timer operates by itself and terminates the session when the timer expires has a problem in that an unnecessary session is left in the existing PDSN until the PPP inactivity timer of the existing PDSN expires. Therefore, until the session is terminated, the existing PDSN will perform paging to transmit the packet to the user terminal when the packet is transmitted to the IP address assigned to the user terminal, resulting in unnecessary waste of radio resources. .

In addition, when the network is implemented to provide wireless data service in the always-on state, the PPP inactivity timer may be variously changed according to the circumstances of the network. May take up memory. This can result in reduced performance and session capacity due to inefficient memory management.

Accordingly, an object of the present invention to solve the above-described problem is to perform handoff between data service devices using a handoff management device combined with various data service devices (NASs) existing in various networks. It is to provide a method and apparatus for managing handoff between data service devices to enable rapid processing.

Another object of the present invention is to provide a method and apparatus for managing handoff between data service devices, which can minimize radio resource waste through fast handoff between data service devices.

It is still another object of the present invention to provide a method and apparatus for managing handoff between data service apparatuses which enables efficient memory management and session capacity management by quickly terminating unnecessary sessions of any data service apparatus.

In order to achieve the above object, according to an aspect of the present invention, in the handoff management device combined with a plurality of data service device in the method for managing handoff between data service devices according to the change of the position of the user terminal, Receiving a first terminal information update request from a first data service apparatus PPP connected to a user terminal, wherein the first terminal information update request includes first terminal identification information corresponding to the first user terminal and the first terminal information update request; A first IP address of the data service device; Storing first session information corresponding to the user terminal by using the first terminal information update request; Receiving a second terminal information update request from a second data service apparatus connected to a second user terminal in a PPP connection, wherein the second terminal information update request includes second terminal identification information corresponding to the second user terminal; A second IP address of a second data service device; Determining whether session information corresponding to the second terminal identification information exists; Determining whether the first IP address and the second IP address match when the first session information corresponding to the second terminal identification information exists; And transmitting a session termination message to the first data service device when the first IP address and the second IP address do not coincide with each other. A system, apparatus, and recording medium are provided for enabling the performance of a handoff management method between data service apparatuses. In this case, second session information corresponding to the second terminal information update request may be stored before, simultaneously with, or after the transmission of the session termination message.

The method for managing handoff between the data service devices may include receiving a third terminal information update request from the first data service device that has terminated the session with the first user terminal, wherein the third terminal information update request is at least The first terminal identification information and information indicating an end of the session with the first user terminal; And deleting the first session information by using the third terminal information update request.

The method for managing handoff between the data service devices may further include terminal session information for enabling the first terminal information update request and the second terminal information update request to use a wireless data service, respectively. If the second IP address is matched, the method may further include updating the stored first session information by using the terminal session information included in the second terminal information update request.

The determining of whether the first IP address and the second IP address coincide further includes: the first terminal information update request further includes a third IP address of the first lower device corresponding to the first data service device; If the second terminal information update request further includes a fourth IP address of the second lower device corresponding to the second data service device, the first session information corresponding to the second terminal identification information exists. Determining whether the first IP address matches the second IP address; When the first IP address and the second IP address match, determining whether the third IP address and the fourth IP address match; And transmitting a session termination message to the first lower device when the third IP address and the fourth IP address do not match. In this case, each of the first lower device and the second lower device may be at least one of a packet control function unit (PCF) and a packet switching device (SGSN).

The method for managing handoff between the data service devices may further include terminal session information for enabling the first terminal information update request and the second terminal information update request to respectively use a wireless data service. If the fourth IP address matches, the method may further include updating the stored first session information by using the terminal session information for using the wireless data service included in the second terminal information update request.

The first terminal information update request and the second terminal information update request each include operation state information of the first user terminal and the second user terminal, and the operation state information is an active state or an idle state. (Dormant State) may be at least one.

The first data service device and the second data service device may be at least one of a packet data serving node (PDSN), a network interworking device (IWF), and a packet gateway switching device (GGSN) included in a homogeneous or heterogeneous network, respectively. Can be.

The terminal identification information may be subscriber identity information (IMSI: International Mobile Subscriber Identity).

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

1 is a diagram illustrating a connection relationship between data service devices for performing handoff according to an embodiment of the present invention.

Referring to FIG. 1, a data communication service system according to the present invention includes a plurality of PCFs 110a, 110b, 113a, and 113b, a plurality of MSCs 116a and 116b, and a plurality of packet switching devices (SGSNs). (Hereinafter referred to as SGSN) 119a and 119b, a plurality of data service devices 120 and a handoff management device 130.

The data service devices 120 include a plurality of PDSNs 123a and 123b, an Interworking Function (IWF) 126, a Gateway GPRS Support Node (GGSN) 129, and the like. Can be. Of course, in addition to any device that can perform a packet data transmission and reception service through a wireless communication network it is obvious that the same can be applied without any limitation.

Each data service device 123a, 123b, 126 or 129 may be combined with any number of PCFs 110a, 113b, MSCs 116a, 116b or SGSNs 119a, 119b. In FIG. 1, a data service device is combined with two PCFs, MSCs, or SGSNs, respectively, to provide a wireless data service to a user. However, the number of PCFs or SGSNs that can be combined with a data service device is a data communication service. Depending on the configuration of the system, it can be applied differently. Of course, the configuration of the data service apparatus that may be included in the data communication service system may also be different from that of FIG. 1.

Each of the PCFs 110a, 110b, 113a, 113b, the plurality of MSCs 116a, 116b, SGSNs 119a, 119b, PDSNs 123a, 123b, IWF 126, and GGSN 129 shown in FIG. Functions and uses are obvious to those skilled in the art, and thus descriptions thereof will be omitted.

The handoff management device 130 may include a user terminal (eg, a mobile communication terminal, a personal digital assistant (PDA), a laptop computer, or the like) that is currently receiving a wireless data service. Device management information (eg, an International Mobile Subscriber Identity (IMSI)) and an IP address assigned to the user terminal by the data service device 123a, 123b, 126, or 129. The device instructs to perform handoff between data service devices when the jurisdiction between data service devices is changed. Specific operation of the handoff management device 130 will be easily understood through the following description. However, the following description will focus on the case where a handoff is performed between the first PDSN 123a and the second PDSN 123b for convenience of description. Of course, it is obvious that the same or similar method can be applied not only in case of handoff between PDSNs, but also when handoff between heterogeneous networks is required.

2 is a detailed configuration diagram of a data communication service system for performing a handoff between PDSNs according to a preferred embodiment of the present invention, and FIG. 3 is a user in an active state according to a preferred embodiment of the present invention. 4 is a data flow diagram for performing handoff between PDSNs for a terminal, and FIG. 4 is a data flow diagram illustrating a session termination procedure of an existing PDSN according to an embodiment of the present invention.

Referring to FIG. 2, the data communication service system includes two or more base transceiver stations (BTSs), two or more base station controllers (BSC / PCFs, hereinafter referred to as first PCF 220a and second PCF 220b), A plurality of PDSNs (assuming the case includes two PDSNs called a first PDSN 230a and a second PDSN 230b), an exchanger (MSC), a visitor location register (VLR), a home location register ( Home Location Register (HLR), Interworking Function (IWF), Home Agent (HA), AAA Server (Authentication, Authorization and Accounting Server) 240, Billing Processing Unit 250, Handoff Management Device 260 and the like. Functions and uses of each component shown in FIG. 2 are obvious to those skilled in the art, and thus descriptions thereof will be omitted.

Hereinafter, when the user terminal 210 moves from the jurisdiction of the first PDSN 230a to the jurisdiction of the second PDSN 230b, the handoff management apparatus 260 may move the first PDSN 230a and the second PDSN. A method of performing handoff between 230b will be described with reference to FIGS. 3 to 4.

Referring to FIG. 3, when a user terminal 210 moves to a jurisdiction of the second PDSN 230b with a session established with the first PDSN 230a in the jurisdiction of the first PDSN 230a, the second PCF ( When the original message is transmitted to the second PDSN 230b in step 310, the second PCF 220b sends an RP registration request message to the second PDSN 230b in step 220b. ).

The second PDSN 230b registers terminal information (eg, IMSI) and session information of the user terminal 210, and then transmits an RP Registration Reply message to the second PCF 220b in step 315. do.

In case of authentication and intelligent network of the user terminal 210, the second PDSN 230b sends a subscriber detail information request (SubsInfo Request) including the outgoing subscriber number information of the intelligent network subscriber to the AAA server 240 to receive WIN_CALL_ID information. Transmit (step 320) and receive a subscriber detail information response (SubsInfo Response) from the AAA server 240 (step 325). The subscriber details response received through step 325 includes a Virtual Private Network (VPN) field, an AUTH field, a Service Identification Code (WIN), a PRICE_PLAN field, a WIN_CALL_ID field, a Switched Virtual Connection (TYPE) _TYPE field, a USBL_TIME field, and a USBL_PACKET field. It may include. Of course, the configuration of the subscriber details response may be configured in various ways. Here, the VPN field may indicate whether to register a virtual private network service, the AUTH field may indicate whether to register an authentication service, and the service identification code may indicate a field that indicates an intelligent network service code. The PRICE_PLAN field may indicate a discounted / undiscounted area when an initial call is set up for an intelligent network service subscriber, the WIN_CALL_ID field may indicate an ID for identifying an intelligent network subscriber, and the SVC_TYPE field may indicate a detailed intelligent network type. The USBL_TIME field may be a field indicating the amount of available time of the intelligent network prepaid subscriber, and the USBL_PACKET field may be a field indicating the amount of available data of the intelligent network prepaid subscriber.

When the second PDSN receives a message indicating that the authentication succeeds from the AAA server 240, the PPD is configured between the user terminals 210 in step 330.

After the second PDSN 230b allocates a new IP address to the user terminal 210, the charging processing apparatus 250 starts to charge the user for using the wireless data service of the user terminal 210 in step 335. Send Account Request (Start). The second PDSN 230b receives the charging start response message from the charging processing device 250.

Thereafter, the second PDSN 230b updates the information to the handoff management device 260 to change the state of the user terminal 210 (eg, NAS IP address registration, PCF IP address registration, session related information update, etc.). Send a request (Update Request (Active)). The information update request may include terminal information (eg, IMSI), NAS (Network Access Server) IP address, PCF IP address, etc. of the user terminal 210. The second PDSN 230b receives the state change response of the user terminal 210 from the handoff management device 260.

In operation 335, the handoff management apparatus 260 determines whether a corresponding session exists using the terminal information (eg, IMSI) as a key value, and if the session exists, receives it from the second PDSN 230b. It is determined whether a NAS IP address is different from a stored NAS IP address (eg, a NAS IP address assigned by the first PDSN 230a) corresponding to an existing session. If there is a mismatch between the NAS IP address received from the second PDSN 230b and the previously stored NAS IP address, it is recognized as a handoff between the PDSNs, and the flow proceeds to step 360 where the first PDSN 230a receives the corresponding user terminal 210. ) And end the session you have set up. A detailed operation process of step 360 will be described in detail with reference to FIG. 4 below. Of course, step 350 may be performed after step 355 and step 360 are completed. In addition, although not shown in FIG. 3, when the NAS IP address received from the second PDSN 230b and the previously stored NAS IP address match, data related to the existing session may be updated with new information. In addition, although not shown in FIG. 3, when the newly received NAS IP address and the previously stored NAS IP address match, it is determined whether the newly received PCF IP address matches the stored PCF IP address corresponding to the existing session. It may further comprise a step. If each PCF IP address matches, only session related information (eg, terminal session information for using a wireless data service) may be updated with new information. If each PCF IP address is different, the same PDSN may be updated. It is located within the jurisdiction of the PCF, but different PCFs providing data services may perform handoff procedures between PCFs. Since the handoff procedure between PCFs can be processed by applying a concept similar to the handoff procedure between PDSNs, the following description will focus on the handoff procedure between PDSNs. However, in the case of handoff between PCFs, the handoff management device 260 may update only session related information, and the session termination operation may be performed by a corresponding PDSN. That is, in the case of a handoff between PDSNs, the handoff management device 260 performs a session termination work, but in the case of a handoff between PCFs, the corresponding PDSN may perform a session termination work according to the handoff.

Referring to FIG. 4, in operation 410, the first PDSN 230a determines whether a session termination request is received from the handoff management device 260. That is, when the handoff management device 260 recognizes that it is a handoff between PDSNs (see step 355 of FIG. 3), the handoff management apparatus 260 sends a request to the first PDSN to terminate the session established between the first PDSN 230a and the user terminal 210. Send a session termination request (eg, Qualification Directive (PDSN Handoff), QuD (197, InterPDSN Handoff), etc.). The session termination request may include terminal information (eg, IMSI), an accounting session ID, and the like.

If a session termination request is received, in step 425 the first PDSN 230a sends an RP registration update request to the first PCF 220a and in step 430 a response from the first PCF 220a RP Registration Ack).

Thereafter, in step 435, the first PDSN 230a receives an RP registration request (Active Stop, Lifetime = 0) from the first PCF 220a, and in step 440, the first PDSN 230a receives the RP registration request. Send an RP Registration Reply.

The first PDSN 230a transmits an accounting request to the accounting processing unit 250 for accounting for the wireless data service used by the user while the RP session is connected at step 445, and at step 450. The charging processing response is received from the charging processing apparatus 250.

In addition, when the first PDSN 230a transmits an information update request (Update Request (Idle)) to the handoff management device 260 for state management of the user terminal 210 in step 455, the handoff management device 260 ) Transmits the information update response to the first PDSN 230a in step 460 and deletes the session corresponding to the terminal information. Of course, the information update response may be transmitted to the first PDSN 230a after the deletion of the session.

As such, the first PDSN 230a may include a session termination request (for example, terminal information (eg, IMSI), accounting session ID, etc.) received from the handoff management device 260. After finding the corresponding session using any information included in the key as a key value, the session is in an active state, so the PPP is terminated by using the LCP termination request, and the first request is performed by using the RP registration update request. It is to request the PCF 220a to terminate the RP session. Here, the active state is a state in which both a session and a connection are established between the user terminal 210 and the PDSN, and the user terminal 210 also means a state in which the PDSN and the PPP are configured. Thereafter, the first PCF 220a terminates the RP session by the RP registration update request, and the first PDSN 230a transmits a billing clearance request to the billing processing device 250 for billing clearance, and the user terminal 210. Transmits an information update request to the handoff management device 260 for state management. The handoff management device 260 deletes the session when both the terminal information of the information update request and the PCF IP address match.

5 is a data flow diagram for performing handoff between PDSNs for a user terminal in a Dormant state according to another exemplary embodiment of the present invention, and FIG. 6 is a diagram illustrating an existing PDSN according to another preferred embodiment of the present invention. A data flow diagram illustrating a session termination procedure.

5 and 6, the inter-PDSN handoff for the idle user terminal shown in FIGS. 5 and 6 is similar to the system configuration of FIG. 2 described above, in which the user of the second PDSN 230b is located in the jurisdiction of the first PDSN 230a. It shows the inter-PDSN handoff procedure when moving to the jurisdiction. In addition, since the PPP connection and charging step, step 345 and step 350 of FIG. 5 are the same or very similar to the steps 305 to 350 of FIG. 3 described above, description thereof will be omitted in order to avoid redundant description. . This is because, even if the user terminal 210 exists in the Dormant state, when a change occurs in the jurisdiction area between PDSNs, the new PDSN performs a PPP connection to manage the user terminal 210. . In addition, the information update request of steps 345 and 350 is referred to as a first information update request (1st Update Request (Active)) to distinguish it from the information update request transmitted in step 530 of FIG. 5.

Referring to FIG. 5, the user terminal 210 receives a new IP address from the second PDSN 230b through a PPP access procedure with the second PDSN 230b in step 505, and then a dormant state. In order to transition, the connection cancellation request (Release Order) is transmitted to the second PCF 220b. That is, since the user terminal 210 was in a Dormant state at the time of moving from the jurisdiction of the first PDSN 230a to the jurisdiction of the second PDSN 230b, the user terminal 210 received an IP address or the like from the second PDSN 230b. After the system is allocated, it transitions back to the Dormant State. Dormant state refers to a state in which a common channel is connected to a wireless section and PPP remains in a wired section, and a user terminal 210 using a wireless data service by releasing a traffic channel between the base station and the user terminal 210. Remains in a waiting state.

The second PCF 220b receives from the user terminal 210 in step 510 and terminates the traffic channel between the user terminal 210 and the PCF (ie, base station) in step 515. Of course, in the process of terminating the traffic channel between the user terminal 210 and the base station, the traffic channel termination may be performed by the user terminal 210 by transmitting a traffic channel request signal from the base station to the user terminal 210.

Thereafter, the second PCF 220b transmits a charging end request (R-P Registration Request (Active Stop, 1800)) to terminate the charging process of the charging processing device 250 to the second PDSN 230b in step 515. In step 520, a response message (RP Registration Reply) is received from the second PDSN 230b. This is because the state of the user terminal 210 is a dormant state and the traffic channel is terminated between base stations. This is because no billing factor occurs because no packet is sent or received.

In operation 525, the second PDSN 230b transmits an accounting request to the accounting processing apparatus 250 for accounting. In operation 530, the second PDSN 230b receives the accounting termination response from the accounting processing apparatus 250.

Thereafter, the second PDSN 230b transmits a second information update request (2nd Update Request (Dormant)) to the handoff management device 260 to change the state of the user terminal 210 in step 535, and in step 540. The second information update response is received from the handoff management device 260. As described above, the distinction between the first (1st) and the second (2nd) is for convenience of description only and does not have a special meaning. The information update request may include terminal information (eg, IMSI) of the user terminal 210, a NAS IP address assigned by the second PDSN 230b, a PCF IP address, and the like.

The handoff management device 260 determines whether there is a corresponding session using the terminal information (eg, IMSI) as a key value in step 545, and if the session exists, receives it from the second PDSN 230b. It is determined whether a NAS IP address is different from a stored NAS IP address (eg, a NAS IP address assigned by the first PDSN 230a) corresponding to an existing session. If there is a mismatch between the NAS IP address received from the second PDSN 230b and the previously stored NAS IP address, it is recognized as a handoff between the PDSNs, and the flow proceeds to step 550 where the first PDSN 230a receives the corresponding user terminal 210. ) And end the session you have set up. A detailed operation process of step 550 will be described in detail with reference to FIG. 6 below. Of course, step 540 may be performed after step 545 and step 550 are completed. In addition, although not shown in FIG. 5, when the NAS IP address received from the second PDSN 230b and the previously stored NAS IP address match, data related to the existing session may be updated with new information. In addition, although not shown in FIG. 5, when the newly received NAS IP address matches the previously stored NAS IP address, it is determined whether the newly received PCF IP address matches the stored PCF IP address corresponding to the existing session. It may further comprise a step. If each PCF IP address matches, only session-related information can be updated with new information. If each PCF IP address is different, the PCFs that provide data services are located within the jurisdiction of the same PDSN. Therefore, handoff procedure between PCFs can be performed. Since the handoff procedure between PCFs can be processed by applying a concept similar to the handoff procedure between PDSNs, the following description will focus on the handoff procedure between PDSNs. However, in the case of handoff between PCFs, the handoff management device 260 may update only session related information, and the session termination operation may be performed by a corresponding PDSN. That is, in the case of a handoff between PDSNs, the handoff management device 260 performs a session termination work. In the case of a handoff between PCFs, a corresponding PDSN may perform a session termination work according to the handoff.

Referring to FIG. 6, the first PDSN 230a determines whether a session termination request is received from the handoff management device 260 in step 610. That is, when the handoff management device 260 recognizes that it is a handoff between PDSNs (see step 540 of FIG. 5), the handoff management apparatus 260 sends a request to the first PDSN to terminate the session established between the first PDSN 230a and the user terminal 210. Send a session termination request (eg, Qualification Directive (PDSN Handoff), etc.). The session termination request may include terminal information (eg, IMSI), an accounting session ID, and the like.

When the session termination request is received, the first PDSN 230a sends a message to the first PCF 220a to delete the RP session with the user terminal 210 and the mobile node (MN) table corresponding to the terminal information in step 615. The RP Registration Request is transmitted, and in step 620, a response (RP Registration Ack) is received from the first PCF 220a.

Thereafter, in step 625, the first PDSN 230a receives an RP registration request (RP registration request (Active Stop, Lifetime = 0)) from the first PCF 220a, and in step 630, the first PDSN 230a receives the RP registration request. Send an RP Registration Reply.

When the first PDSN 230a transmits an information update request (Update Request (Idle)) to the handoff management device 260 to manage the state of the user terminal 210 in step 635, the handoff management device 260 transmits the information to the handoff management device 260. In step 640, an information update response is transmitted to the first PDSN 230a, and the session corresponding to the terminal information (eg, IMSI) is deleted. Of course, the information update response may be transmitted to the first PDSN 230a after the deletion of the session.

As described above, the method and apparatus for managing handoff between data service apparatuses according to the present invention is a data service apparatus using a handoff management apparatus combined with various data service apparatuses (NAS: Network Access Server) existing in various networks. Handoff of the liver can be handled quickly.

In addition, the present invention can minimize the radio resource waste through the handoff between the data service devices.

In addition, the present invention enables efficient memory management and session capacity management by quickly terminating unnecessary sessions of any data service device.                     

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 (12)

In the handoff management device combined with a plurality of data service devices, A method for managing handoff between data service devices according to a change in position of a user terminal, Receiving a first terminal information update request from a first data service apparatus connected to a first user terminal in a PPP connection, wherein the first terminal information update request comprises: first terminal identification information corresponding to the first user terminal; A first IP address of the first data service device; Storing first session information corresponding to the user terminal by using the first terminal information update request; Receiving a second terminal information update request from a second data service apparatus connected to a second user terminal in a PPP connection, wherein the second terminal information update request includes second terminal identification information corresponding to the second user terminal; A second IP address of a second data service device; Determining whether session information corresponding to the second terminal identification information exists; Determining whether the first IP address and the second IP address match when the first session information corresponding to the second terminal identification information exists; And Transmitting a session termination message to the first data service device when the first IP address and the second IP address do not match. Including but not limited to: Storing second session information corresponding to the second terminal information update request before, concurrent with or after the transmission of the session termination message; Handoff management method between the data service device, characterized in that. The method of claim 1, Receiving a third terminal information update request from the first data service apparatus that has terminated the session with the first user terminal, wherein the third terminal information update request comprises at least the first terminal identification information and the first terminal; Information indicative of the end of the session with the user terminal; And Deleting the first session information by using the third terminal information update request Handoff management method between the data service device further comprising. The method of claim 1, The first terminal information update request and the second terminal information update request further include terminal session information for enabling the use of a wireless data service, respectively, when the first IP address and the second IP address match, the Updating the stored first session information by using terminal session information included in a second terminal information update request. Handoff management method between the data service device further comprising. The method of claim 1, Determining whether the first IP address and the second IP address match, The first terminal information update request further includes a third IP address of the first lower device corresponding to the first data service apparatus, and the second terminal information update request is the second corresponding to the second data service apparatus. If further includes a fourth IP address of the lower device, Determining whether the first IP address and the second IP address match when the first session information corresponding to the second terminal identification information exists; When the first IP address and the second IP address match, determining whether the third IP address and the fourth IP address match; And If the third IP address and the fourth IP address do not match, transmitting a session termination message to the first lower device. Including but not limited to: The first lower device and the second lower device are at least one of a packet control function (PCF) and a packet switching device (SGSN), respectively. Handoff management method between the data service device, characterized in that. The method of claim 4, wherein The first terminal information update request and the second terminal information update request each further include terminal session information for enabling the use of a wireless data service, and when the third IP address and the fourth IP address match, the Updating the stored first session information by using terminal session information for using a wireless data service included in a second terminal information update request. Handoff management method between the data service device further comprising. The method of claim 1, The first terminal information update request and the second terminal information update request each include operation state information of the first user terminal and the second user terminal. The operation state information may be at least one of an active state and a dormant state. Handoff management method between the data service device, characterized in that. The method of claim 1, The first data service device and the second data service device are at least one of a packet data serving node (PDSN), a network interworking device (IWF), and a packet gateway switching device (GGSN) included in a homogeneous or heterogeneous network, respectively. that Handoff management method between the data service device, characterized in that. The method of claim 1, Terminal identification information is an International Mobile Subscriber Identity (IMSI) Handoff management method between the data service device, characterized in that. A handoff management apparatus coupled to a plurality of data service apparatuses for managing handoff between data service apparatuses according to a change in position of a user terminal, Receiving unit for receiving the first terminal information update request from the first data service apparatus PPP connected to the first user terminal, and the second terminal information update request from the second data service apparatus PPP connected to the second user terminal The first terminal information update request includes first terminal identification information corresponding to the first user terminal and a first IP address of the first data service device, and the second terminal information update request is performed by the second user. Second terminal identification information corresponding to a terminal, the second IP address of the second data service device; A storage unit which stores first session information corresponding to the user terminal by using the first terminal information update request; A session information determination unit determining whether there is session information corresponding to the second terminal identification information; An IP address determination unit determining whether the first IP address and the second IP address match when the first session information corresponding to the second terminal identification information exists; And A transmission unit for transmitting a session termination message to the first data service device when the first IP address and the second IP address do not match Including but not limited to: The storage unit stores second session information corresponding to the second terminal information update request before, simultaneously with, or after the transmission of the session termination message; Handoff management device, characterized in that. The method of claim 9, If the receiving unit further receives a third terminal information update request from the first data service device that terminated the session with the first user terminal, A session information deletion unit for deleting the first session information by using the third terminal information update request Include more, The third terminal information update request includes at least the first terminal identification information and information indicating the end of the session with the first user terminal; Handoff management device, characterized in that. The method of claim 9, The first terminal information update request and the second terminal information update request further include terminal session information for enabling the use of a wireless data service, respectively, when the first IP address and the second IP address match, the An update processor for updating the stored first session information by using terminal session information included in a second terminal information update request; Handoff management device further comprising. In the recording medium that can be read by the server apparatus, a program of instructions that can be executed in the server apparatus is tangibly implemented to perform a handoff management method between data service apparatuses. Receiving a first terminal information update request from a first data service apparatus connected to a first user terminal in a PPP connection, wherein the first terminal information update request comprises: first terminal identification information corresponding to the first user terminal; A first IP address of the first data service device; Storing first session information corresponding to the user terminal by using the first terminal information update request; Receiving a second terminal information update request from a second data service apparatus connected to a second user terminal in a PPP connection, wherein the second terminal information update request includes second terminal identification information corresponding to the second user terminal; A second IP address of a second data service device; Determining whether session information corresponding to the second terminal identification information exists; Determining whether the first IP address and the second IP address match when the first session information corresponding to the second terminal identification information exists; And Transmitting a session termination message to the first data service device when the first IP address and the second IP address do not match. Run the Storing second session information corresponding to the second terminal information update request before, concurrent with or after the transmission of the session termination message; Recording medium recording a program characterized in that.

Images