KR100790107B1 - Object management apparatus and method in communication system - Google Patents

Abstract

In the object management method in the mobile communication system having a database for storing the ID of the object generated for the originating and receiving signal processing corresponding to the identification information of the mobile subscriber in accordance with the present invention, the session object for call processing Is generated, the generated session object searches for the database and checks whether a session object exists for specific subscriber identification information, and if the object corresponding to the identification information does not exist in the database. Recording a user's ID and performing a call processing; if there is an object corresponding to the identification information, comparing the ID of the searched object with its own ID and performing the call processing if the same is identical; Recall the message to be processed if the ID of the searched object and its ID is different Delivering to the retrieved object; and removing the session object after delivering the message to be processed.

Object, UMTS, GGSN, Management, Session IP, Packet

Description

OBJECT MANAGEMENT APPARATUS AND METHOD IN COMMUNICATION SYSTEM}             

1 is a diagram schematically illustrating a conventional UMTS system.

2 is a view showing a detailed configuration of a GGSN according to an embodiment of the present invention.

3 is a diagram illustrating an incoming call processing procedure of a GGSN according to an embodiment of the present invention.

The present invention relates to a communication system, and more particularly, to an apparatus and a method for managing a session object created for call processing.

In general, a mobile communication system generally refers to a system for providing voice, data, and the like through a wireless network. Such a mobile communication system has various implementations for services such as voice and data, and typical examples thereof are circuit switching networks and packet switching networks.

Currently, 3G (3rd Generation) mobile communication systems are standardized into two types, UMTS system of 3Gpp and cdma2000 system of 3GPP2. In both systems, the circuit mode domain has almost the same function as the network structure and the element system configuration, but the packet mode domain has many differences in the network structure and the element system configuration (particularly, the core network portion). The following description will be made taking UMTS system as an example.

1 is a diagram schematically illustrating a conventional UMTS system.

Referring to FIG. 1, a mobile-service switching center (MSC) 100 is responsible for mobility management and voice call processing for a circuit mode service subscriber. The VLR (Visited Location Register) configured like the MSC100 is a database that temporarily stores all information on mobile terminals in the region managed by the MSC100. The data related to the Home Location Register (HLR) is always kept the same. .

The Serving GPRS Support Node (SGSN) 110 is a serving node of a general packet radio service (GPRS) that directly provides packet services to the mobile terminal 140. The SGSN 110 sets a mobility management context for a packet mode of the mobile terminal 140. The packet mode data service management of 140 is performed. In addition, the GGSN 120 establishes a PDP context and delivers a service data unit (SDU) using GTP (GPRS Tunneling Protocol) tunneling.

The Gateway GPRS Support Node (GGSN) 120 is a GPRS gateway node that is directly connected to a packet data network or the Internet. The Gateway GPRS Support Node (GGSN) 120 has tunneling and Internet Protocol (IP) routing functions by maintaining routing information to the SGSN 110. The routing information is used to tunnel the SDU to the SGSN 110 currently supporting the packet mode service of the mobile terminal 140 and obtain the location information of the mobile terminal 110 from the HLR. The main functions of the GGSN 120 are IP address allocation and management, mobile point-to-point protocol (PPP) generation, termination and relay, and screening functions for the mobile terminal 140 for connection services to an IMT 2000 ISP or another Internet service provider (ISP). Etc.

RNS 130 is composed of Node B and RNC. The Node B performs radio signal transmission and reception, radio channel encoding and decoding, signal strength and quality measurement (uplink), baseband signal processing, diversity, radio resource management, and self maintenance. The RNC (Radio Network Controller) performs functions such as matching with Node B, inter-cell handover processing, call control, etc., and accessing an IMX (IMT-2000 Multimedia eXchange) with an external access signal link and a bearer channel connection channel and The RNC controls several Node Bs.

The mobile station (MS) 140 may be composed of a mobile terminal (MT) serving as an IMT-2000 wireless modem and a terminal equipment (TE) supporting application services. It is standardized for compatibility with Universal Service Identification Module cards.

On the other hand, the HLR is an essential device for a database that stores subscriber parameters and position information for all mobile terminals registered in the own IMT-2000 network and management, IMT-2000 service. The HLR registers important data such as access capability, basic service, and additional service of the mobile terminal 140 and performs a routing function to the called subscriber. An EIR (Equipment Identity Register) is a database that manages ID management of the mobile terminal 140 and is used to check "valid" for the mobile terminal.

In the configuration as shown in FIG. 1, the packet call processing of the GGSN 120 may be largely classified into an outgoing call process and an incoming call process. The outgoing call processing is started while the calling subscriber tries to make a call, and the incoming call processing is carried out by a packet transmitted by any other party through a packet network (or Internet network). Platform) and starts by notifying a packet service session object (PS Session Object).

At this time, the call signal processing is whether or not "Common IH" (hereinafter referred to as a first process) will generate a PS session object that performs the packet call processing, or to an existing object. Determine whether to perform packet call processing. On the other hand, the incoming call processing "TIF IH (hereinafter referred to as the second process) whether or not to create a PS Session Object that performs the packet call processing, or whether to make the packet call processing to the existing object created The following Table 1 shows the session ID management table of the "TIF IH." The "TIF IH" accesses the management table as shown in Table 1 below to create a new session object or an existing object. Determines whether to perform packet call processing.

TP Context Id IH Id Session Id One One 2 ... .... .... ... ... ....

In the related art, the " TIF ", which is a generating subject of a packet session object that performs an incoming call processing and the " Common IH " IH "exists in different processors and there is no way to share information about PS session objects created by each other. Therefore, although the "Common IH" may allow the PS session object created to perform the outgoing call processing, the incoming call processing may be performed, but a new PS session object for the incoming call processing is generated. That is, there is a problem that unnecessary objects are created.

Therefore, an object of the present invention, in the mobile communication system, even if the subjects that create objects (objects) exist in different processors and cannot share information about the objects created by each other, additionally create unnecessary objects To provide an object management apparatus and method for using an object that has already been created without.

In order to achieve the above object, an apparatus for managing an object created for call processing in a mobile communication system may match an object ID of an object created for outgoing and incoming call processing with identification information of a mobile subscriber. A database for managing, a call signal processing process for generating a specific object upon request of a call signal processing, and a call object processing processor generated by the call signal processing processor, and whether or not a session object is generated for identification information of a specific mobile subscriber through the database; And a session object for retrieving and recording its ID in the database and performing a call processing when the object corresponding to the mobile subscriber does not exist.

In order to achieve the above object, the object management method in the mobile communication system having a database for storing the ID of the object generated for the originating and receiving signal processing corresponding to the identification information of the mobile subscriber, the session for call processing A process of creating an object, a process of checking, by the created session object, whether the session object exists with respect to specific mobile subscriber identification information, and if the object corresponding to the identification information does not exist Recording the ID of the user and performing call processing; and if the object corresponding to the identification information exists, comparing the ID of the searched object with its own ID to perform the call processing; If the ID of the searched object and its ID is different, a message to be processed And delivering to the retrieved object, and removing the session object after delivering the message to be processed.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, if it is determined that the detailed description of the related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

Hereinafter, the present invention provides a PS Session Object that performs packet call processing in a Gateway GPRS Support Node (GGSN) 120, which is a packet service domain of a GSM Packet Radio Service (GPRS). Next, a method of determining whether to create a new object to perform packet call processing or to make an existing object to perform packet call processing will be described.

In particular, the present invention adds a database (DB: Database) for managing only the session ID (Session Id) as shown in Table 2 below to the GGSN (hereinafter referred to as "gateway node"), and the database as shown in Table 2 It is characterized in that to prevent the objects are created by overlapping.

IMSI Packet Data Protocol (PDP) Address IF Id Session Id 1234567890 165.213.238.138 One 2 ... ... ... ... .... .... .... ... .... .... ... ....

2 shows a detailed configuration of the gateway node 120 in the detailed configuration of the GGSN according to an embodiment of the present invention. Reference numerals 200 to 250 denote communication protocol layers for packet call processing. Since these protocol layers are already known, the detailed description is omitted and the description is as follows.

Referring to FIG. 2, an interface handler (IH) 280 serves as an interface between each subsystem of the GGSN. The packet session (PS) 260 is an object created to perform packet call processing. The session database 270 stores the PS object ID. TCAP corresponding to the reference numeral 230 is an application part for transaction execution of a user part in a No. 7 signaling system. SCCP corresponding to 200 is a part for controlling signaling connection of a user part in a No. 7 signaling system. No. 7 corresponding to the reference numeral 200 sets up a signal line separate from the call line to quickly and accurately establish and release the call line and transfer data required between stations. The PS 260 transmits and receives a GTP protocol message related to activation, deactivation, and change of a PS object with the SGSN system through the GTP-C 240. The MIP + 250 performs a function of transmitting and receiving a mobile IP related message. The PS 260 transmits and receives a 3GPP 29.002 protocol message through an HLR and a MAP corresponding to the reference numeral 230. The PS 260 transmits and receives commands related to activating, deactivating, and changing a packet data context through a GGSN transport platform and a TIF 290. Here, reference numerals 260 to 290 denote processes for packet call processing.

Packet call processing of the GGSN can be classified into call processing and incoming call processing. Since the embodiment according to the present invention is equally applied to the call signal processing and the incoming call processing, the following description will only describe the incoming call processing.

Figure 2 shows a detailed configuration of the GGSN according to an embodiment of the present invention, Figure 3 shows an incoming signal processing procedure of the GGSN according to an embodiment of the present invention.

2 and 3, the incoming call processing process (TIF IH) checks whether an incoming call is received in step 301. If the incoming call is received, the processor proceeds to step 303, otherwise proceeds to step 319 to perform the corresponding function. On the other hand, the incoming call processing process generates a PS Session Object (PS Session Object) for the incoming call processing in step 303. In step 305, the PS session object searches for a session ID management table as shown in Table 2 using an IMSI (International Mobile Subscriber Identity) as a key. In operation 307, the PS session object checks whether the PS session object exists in the session ID management table corresponding to a specific IMSI.

If the PS session object does not exist in the session ID management table, the PS session object proceeds to step 321 and records the generated ID of the PS session object in the session ID management table. In operation 317, the PS session object performs normal packet call processing.

On the other hand, if the PS session object exists in the session ID management table, the PS session object proceeds to step 311 to retrieve the PS session object ID retrieved from the session ID management table (RETRIEVE). In operation 311, the PS session object checks whether the ID (own ID) of the PS session object is the same as the retrieved PS session object ID. If the two IDs are the same, the PS session object proceeds to step 317 to perform normal packet call treatment.                     

On the other hand, if the two IDs are different, the PS session object proceeds to step 313 and passes the received message to the PS session object retrieved from the database (DB). In this case, when the two IDs are different, the PS session object is already created for the call signaling, and the PS session object generated by the TIF checks whether the PS session object is generated for a specific IMSI. Therefore, the incoming call processing process deactivates the created unnecessary PS session object in step 315. In step 317, the normal packet call processing is performed through the PS session object recovered from the database.

As described above, in order to perform the call signal processing, the PS Session object generated with the Common IF checks whether the PS Session Object is generated using the IMSI as a key. At this time, if the PS Session object does not exist, the current PS Session object Id is written to the DB, and packet call processing is continued. Similarly, in order to perform the incoming call processing, the PS session object generated by TIF IH also checks whether a PS session object is created, records the PS Session object Id, and continues packet call processing using IMSI as a key. .

If the PS Session object Id is retrieved from the database, it can be processed as follows. First, if the PS session object Id retrieved from the DB and the current PS Session object Id are the same, the PS Session Object can perform normal packet call processing. Second, if the PS Session object Id retrieved from the DB and the current PS Session object ID are different, the PS Session object created by TIF is created after the PS Session object has already been created to perform the signaling. This is the case that PS session object is created for a specific IMSI. In this case, since TIF IH generates an unnecessary PS Session Object for any IMSI, the received message is tossed to a PS Session object retrieved from the DB, and an unnecessary PS Session object generated by TIF IH. Deactivate.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

As described above, the present invention checks the legitimacy of an object created for a specific process, tossing control to an appropriate object in the case of unnecessary objects, and deactivating the created object. Therefore, unnecessary object creation can be suppressed.

Claims (4)

An apparatus for managing an object created for call processing in a mobile communication system, A database for managing an ID of an object generated for processing an incoming call and a receiving call with identification information of a mobile subscriber; A call signal processing process of generating a specific object when a call signal processing request is made; The call origination processor generates the session object for the identification information of the specific mobile subscriber through the database, and if the object corresponding to the mobile subscriber does not exist, the user's ID is entered in the database. A session object for recording and performing call processing. The method of claim 1, And if the object corresponding to the identification information exists, the session object compares the ID of the searched object with its own ID and performs the call processing if the same. The method of claim 1, If there is an object corresponding to the identification information, the session object compares the ID of the searched object with its own ID and delivers a message to be processed to the searched object if it is different, and the session object is removed. Device. In the object management method in a mobile communication system having a database for storing the ID of the object generated for processing the incoming and outgoing signals corresponding to the identification information of the mobile subscriber, Creating a session object for call processing; Checking, by the created session object, whether the session object exists with respect to specific subscriber identification information by searching the database; If there is no object corresponding to the identification information, recording its ID in the database and performing a call processing; If there is an object corresponding to the identification information, comparing the ID of the searched object with its own ID and performing the call processing if it is the same; Transmitting a message to be processed to the searched object when the searched object's ID and the user's ID are different from each other; And removing the session object after delivering the message to be processed.

Images