KR100939570B1 - VoIP system for proceessing XCAP data and CPL data and method thereof - Google Patents

Abstract

The present invention relates to a VoIP system and method for integrating XCAP data and CPL data. The present invention receives and stores mixed XCAP / CPL mixing data based on XML from a user terminal, and separates the XCAP / CPL mixing data into XCAP data and CPL data based on XML and provides the corresponding data upon external request. Register and maintain the presence data, which is the online status information of each user terminal registered as a subscriber, to inform the user of the presence information of the corresponding user, and identify the XCAP data registered by the subscriber in conjunction with the mixing data processor. And a presence server for determining whether to provide information about a specific person, and a call of a caller terminal to a called terminal according to a SIP-based call connection request, and interworking with the mixing data processor to grasp CPL data registered by the corresponding subscriber. SIP server to determine call processing command for a specific person Include. Accordingly, the present invention integrates XCAP data and CPL data processing to maximize the efficiency of the system operation and to reduce the system construction cost and management cost.

CPL Script, XCAP, SIP, Presence

Description

VoIP system for proceessing XCAP data and CPL data and method

The present invention relates to a Voice over Internet Protocol (VoIP) system and method having a presence service. In particular, the present invention provides a VoIP system for integrating and managing XCAP (XML configuration Access Protocol) data generated on the user side for presence service and CPL (Call Processing Language) data which is call processing information registered on the user side for VoIP calls; It is about a method.

As Internet telephony service has been spotlighted as a marketable technology centering on VoIP, IETF's SIP, a signaling protocol for VoIP service, has attracted attention as a replacement technology for ITU-T's H.323. VoIP service is being provided through VoIP system.

SIP is a signaling protocol for establishing and tearing down sessions in an IP network, and is becoming the standard for VoIP services that locate and connect end users to multi-party voice and video conferencing.

On the other hand, in the voice communication that emphasizes real-time, the absence of the other party brings the inconvenience that the user must re-send a number of times. Therefore, in order to increase the success rate of the call, the necessity of the service to confirm the presence and location of the other party has emerged. As a result, a presence service has been developed to provide a VoIP system or an instant messaging system (e.g. Nate On, MSN Messenger, Birdie, birdie, etc.).

Presence service is a service to receive the presence information of a specific user who is away from the Internet. The presence service is used to provide information on whether the user is in real time communication, what services are available, what the user is currently doing, and how he is feeling. Provides a variety of information. The presence service determines whether to provide the presence information with reference to an access right policy (eg, friend registration, friend rejection, display rejection, etc.) to the user presence information registered by the user when providing the user's presence information to the washer. At this time, the information on the access right policy is registered in the system using XCAP (XML Configuration Access Protocol) standard technology.

In addition, a CPL (Call Processing Language) engine for VoIP services has been developed and applied to VoIP systems. CPL is a language for describing call processing based on the IETF standard. It is a language for controlling and describing Internet telephony services used in SIP and H.323. Based on XML, CPL follows the characteristics of XML and allows the user to register call processing instructions (eg call forwarding, rejection, call waiting, etc.), and the CPL engine handles call processing according to these user's call processing instructions. To perform.

Therefore, the user confirms the presence information of the other party to be called through the VoIP system and makes a call, and also allows a call from another person to be processed according to a call processing instruction registered by the user.

However, for the presence service, the current online access information of the user must be registered through the XCAP server of the VoIP system, and the CPL script of the user must be registered through the CPL server of the VoIP system for the CPL service.

That is, in SIP-based VoIP system, XCAP-based presence service registers user setting information for a specific application service in XCAP server, and allows XCAP client to manage information registered in XCAP server, and XCAP client is deployed in presence server. do. And in SIP-based VoIP system, user's call processing command (CPL script) is processed in CPL server which is different from XCAP server, and CPL client controls and manages CPL server, and CPL client is in charge of SIP session processing. It is built on a proxy server.

The current communication system construction is proceeding in order to solve the user's desires at a low cost as soon as possible, as part of the integration of the system is being studied.

As a result, in a situation where the processing of XCAP data and CPL data based on XML is separately performed in a SIP-based VoIP system, a system or method for integrating and processing XCAP data and CPL data is required.

An object of the present invention is to provide a VoIP system and method for integrating and processing the presence XCAP data and call processing CPL data generated on the same user side in the same path.

According to one aspect for achieving the above technical problem, the present invention provides a VoIP system for integrating XCAP data and CPL data. The VoIP system receives and stores mixed XCAP / CPL mixing data based on XML from a user terminal, and separates the corresponding data by separating the XCAP / CPL mixing data into XCAP data and CPL data based on XML upon external request. Provides the mixing data processing unit and the presence information, which is the online status information of each user terminal registered as a subscriber, to notify a user who wants the presence information of the corresponding user, and the XCAP data registered by the subscriber in association with the mixing data processing unit. Presence server to determine whether to provide information on a specific person, and SIP-based call connection request to the terminal of the caller terminal to the destination terminal, while interlocking with the mixing data processing unit to grasp the CPL data registered by the subscriber SIP to determine the call processing command for a specific person Include a server.

In addition, according to another feature for achieving the above technical problem, the present invention provides a method for integrating XCAP data and CPL data. The method generates first XCAP data according to a user input in a first user terminal, generates first CPL data according to another input of the user, and then mixes the first XCAP data and the CPL data. In the case of creating and transmitting XCAP / CPL mixing data, a first step of receiving and storing the XCAP / CPL mixing data transmitted from the first user terminal in a first storage, the first user terminal from a second user terminal. When the event for requesting the presence information of the event occurs, the XCAP / CPL mixing data of the first user terminal stored in the first storage is extracted, and then the CPL data portion is extracted from the extracted XCAP / CPL mixing data. A second step of providing and making CPL data; and when a call connection request event from the second user terminal to the first user terminal occurs, the first store. Stored and a third step of making available the XCAP claim 1 wherein the data in the missing part of the data portion of the CPL 1 was extracted XCAP / CPL mixing data of the user terminal, the XCAP / CPL mixing data extracted.

According to an embodiment of the present invention, the present invention provides the XCAP data containing the access policy for the user's presence information for the specific person designated by the user, and the CPL data including the call processing command according to the call connection request for the specific person specified by the user. It is possible to provide a SIP-based VoIP system that integrates and processes.

As a result, the present invention integrates XCAP data and CPL data processing to maximize the efficiency of system operation and reduce system construction and management costs.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding other components unless specifically stated otherwise. In addition, the terms “… unit”, “… unit”, “module”, etc. described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software. have.

Now, a VoIP system and method for integrating XCAP data and CPL data according to an embodiment of the present invention will be described with reference to FIGS. 1 to 3.

Prior to the description, since the VoIP system of the present invention is based on SIP, the configuration of the SIP system in the VoIP system of the present invention will be briefly described. Since the SIP system configuration of the present invention described below belongs to the technical scope of the main governor, in the following description, the SIP system configuration of the unnecessary part is omitted in the description for the present invention.

SIP systems that handle SIP calls generally include a user agent (UA), a proxy server, a redirect server, a location server, and a registrar.

The UA is a part that operates on the user terminal side. The UA operates in a client format (UAC, User Agent Client) when sending an access request message, and in a server format (UAS) when receiving and processing an access request message. It works. The UA establishes a direct connection with another UA or establishes a connection with another UA with the help of proxy / redirect servers, and stores and manages call state.

The proxy server delivers the connection request message received from the UA to a proxy or redirect server in another domain or to the UA in the corresponding domain and maintains information for billing.

The registrar receives the registration request message from the UA and stores it in a system providing a location server using a protocol other than SIP. (The location server provides this information to the proxy or redirect server so that the connection request can be delivered well.) The location server is not a SIP UA but a DB that registers the user's location.

The redirect server does not send the connection request message directly to other UAs or proxy servers, but rather to inform the UA or proxy server that sent the connection request message the address of the UA or proxy server to which they should resend the connection request message. do.

A VoIP system according to an embodiment of the present invention will now be described with reference to FIG. 1. 1 is a schematic block diagram of a VoIP system according to an embodiment of the present invention.

As shown in FIG. 1, the VoIP system according to an exemplary embodiment of the present invention includes a presence server 100, a mixing data processor 200, a SIP server 300, and a user terminal 1.

The user terminal 1 is a generic term for SIP terminals equipped with UAC and UAS. In FIG. 1, only the first user terminal 10 and the second user terminal 20 are illustrated to facilitate the description of the present invention. The first and second user terminals 10 and 20 perform a first function of notifying a current online access state through XCAP data and a second function of notifying a call processing command designated by a user through CPL data. In this case, when the first and second user terminals 10 and 20 need to simultaneously generate the XCAP data and the CPL data and transmit them to the mixing data processor 200, the first and second user terminals 10 and 20 may mix or mix the XCAP data and the CPL data. And a third function of transmitting one data to the mixing data processing unit 200.

Here, the mixing of the XCAP data and the CPL data uses that the XCAP data and the CPL data are commonly based on XML, and a detailed mixing method of the XCAP data and the CPL data will be described in detail with reference to FIG. 2.

The presence server 100 enables the instant communication service by registering / maintaining the current location of the user who is online and informing the users of the desired information. That is, the presence server 100 receives and processes a user request such as a presence service subscription, a presence service request, presence information reception / provision, and presence member registration. The presence server 100 interlocks with the mixing data processing unit 200 to determine whether the service is provided by identifying the presence information authority policy set by the corresponding user, that is, the XCAP information registered by the user.

The mixing data processing unit 200 receives and stores CPL data (eg, a call processing command script of a subscriber), XCAP data, or mixing data mixed with CPL data and XCAP data received from each user terminal 10 or 11. do. The mixing data processor 200 interoperates with the presence server 100 and the SIP server 300, and provides information requested by the presence server 100 or the SIP server 300. In this case, if the information requested by the presence server 100 or the SIP server 300 is mixing data, the mixing data processing unit 200 extracts only the request data (XCAP data or CPL data) from the mixing data and provides them to the corresponding server. Has

The SIP server 300 corresponds to the above-described proxy server, and includes a module for performing a CPL operation.

Hereinafter, the user terminal and the mixing data processor described with reference to FIG. 1 will be described in more detail with reference to FIG. 2. 2 is a diagram illustrating a main configuration of a VoIP system according to an embodiment of the present invention.

As shown in FIG. 2, the user terminal 1 includes a SIP User Agent (UA) 11, a CPL client 12, an XCAP client 13, and an XML mixing unit 14.

The SIP UA 11 is a part that operates on the actual user terminal side. The SIP UA 11 operates in a client format (UAC, User Agent Client) when transmitting an access request message, and in a server format (UAS, User, when receiving and processing an access request message). Agent Server). The client type (UAC) is the caller's SIP application, and the server type (UAS) is the callee's SIP application.

The CPL client 12 allows a user to generate a CPL script for call processing instructions (eg, call forwarding, call rejection, call waiting, etc.), and outputs the CPL script thus generated as CPL data1. The CPL script is written in XML.

The XCAP client 13 allows the user to generate XCAP information about the access policy to presence information (eg, friend registration, friend rejection, refusal to display presence information, etc.), and outputs the generated XCAP information as XCAP data1. do. At this time, XCAP information is written in XML.

Here, the CPL client 12 and the XCAP client 13 are linked to each other, so that the setting information (publishing permission / rejection, etc.) for the presence information for the specific user and the CPL script can be registered simultaneously by the user.

Therefore, when the XCAP data and the CPL data are generated in conjunction with the user terminal, the user terminal mixes the XCAP data and the CPL data and registers the two data at once in the mixing data processing unit 200. Of course, it is possible to prevent the XCAP data and the CPL data from interworking or to generate only one of the XCAP data and the CPL data (for example, changing information on specific registration data). In this case, the user terminal may register only one generated data in the mixing data processor 200.

The XML mixing unit 14 performs an interface with the mixing data processing unit 200, and when the CPL data1 is received from the CPL client 12 or the XCAP data1 is received from the XCAP client 13, the CPL is mixed with the mixing data processing unit 200. Send data or XCAP data respectively. In particular, when the XML mixing unit 14 receives the CPL data1 and the XCAP data1 from the CPL client 12 and the XCAP crite 13 at the same time, after mixing the received CPL data1 and the XCAP data1 to create the XCAP / CPL mixing data. The XCAP / CPL mixing data is transmitted to the mixing data processor 200.

In this case, data mixing between CPL data1 and XCAP data1 uses CPL data1 and XCAP data1 based on XML. Specifically, data mixing between CPL data1 and XCAP data1 maps the tag part in which the call processing instruction is described in CPL data1 to the <tuple> element of XCAP data1, and the CPL part included in XCAP data1 is grouped using the new defined name. .

Here, an example of a data mixing method between CPL data1 and XCAP data1 will be described.

First, identification information of the first user terminal 10 is called dest@example.com, and identification information of the second user terminal 20 is called src@example.com. And XCAP data1 relates to the first user approving the presentation of the presence information for the second user (i.e., registering as a friend), and CPL data1 to receive a call received from the second user. It's about a call processing command to receive a 0000 mobile phone.

Therefore, the source of XCAP data1 is represented as an XML document as follows.

Here, ghsdf is identification information of a server or a device that processes the presence service.

Also, the source of CPL data1 is represented as an XML document as follows.

The source of XCAP / CPL mixing data in which CPL data1 and XCAP data1 are mixed is represented as an XML document as follows.

Looking at the source of the XCAP / CPL mixing data, the CPL part included in XCAP data1 is a part between <incoming> and </ incoming>, and the <incoming> and <location> tags are mapped to the <tuple> element of XCAP data1. And other tags, including <address-switch>, are grouped under the grouping name "ghsdf". Here, the grouping name is used as "ghsdf" which is identification information of the device or server that provides the presence service. However, the grouping name may be any name defined by the designer.

2, the mixing data processor 100 may include a mixing data receiver 210, a mixing data storage unit 220, an XML separation unit 230, a CPL processor 241, and an XCAP processor 242. It includes.

The mixing data receiving unit 210 is an XML interface and receives data (eg, CPL data, XCAP data, XCAP / CPL mixing data) transmitted from the XML mixing unit 14 and stores the data in the mixing data storage unit 220. At this time, the stored data is stored in match with the identification information of the user terminal.

The mixing data storage unit 220 stores the CPL data, the XCAP data, and the XCAP / CPL data received from the mixing data receiver 210 for each user. The mixing data storage unit 220 may be located in the mixing data processing unit 200, but may exist as a separate database server.

The XML separating unit 230 extracts the corresponding data from the mixing data storage unit 220 according to a request of the CPL processing unit 241 or the XCAP processing unit 242, and the corresponding data to be extracted is mixed data into XCAP / CPL mixing data. When stored in the storage unit 220, the XCAP / CPL mixing data is separated into XCAP data and CPL data, and then the corresponding data is extracted. Here, data separation performed by the XML separator 230 is performed by a process opposite to mixing the XCAP data and the CPL data.

For example, the XML separator 230 creates CPL data2 as the CPL portion grouped by a specific name in the XCAP / CPL mixing data, and creates the XCAP data2 as the remaining portion missing the CPL portion. Here, CPL data2 may be the same as or different from CPL data1, but at least includes the same call processing command as CPL data1. In addition, XCAP data2 may be the same as or different from XCAP data1, but at least contains the same presence information access policy as XCAP data1.

The CPL processing unit 241 interfaces with the SIP server 300, and controls the XML separation unit 230 in response to a CPL script request of a specific user from the SIP server 300 to obtain the corresponding CPL data to the SIP server 300. To provide. As a result, the CPL processing unit 241 serves as a CPL server that provides information corresponding to the CPL data request of the SIP server 300, and the SIP server 300 is equipped with a CPL client program serving as a CPL client. It is.

The XCAP processing unit 242 interfaces with the presence server 100, and controls the XML separation unit 230 in response to the presence information access policy of the specific user from the presence server 100 to obtain the corresponding XCAP data and the presence server 100 To provide. Eventually, the XCAP processing unit 242 serves as an XCAP server providing information corresponding to the call processing command script request of the presence server 100, and at this time, the presence server 100 serves as an XCAP client program. This is mounted.

Hereinafter, a method of integrating XCAP data and CPL data according to an embodiment of the present invention will be described with reference to FIG. 3. 3 is a data flow diagram illustrating a method of integrating XCAP data and CPL data according to an embodiment of the present invention. 2 illustrates a case where a call is requested to a first user terminal from a second user terminal 20 confirming the presence of the first user terminal 10.

As shown in FIG. 3, the first user terminal 10 transmits a SUBSCRIBER winfo message for notifying the subscriber requesting his presence status to the presence server 100 (S301).

The presence server 100 then analyzes the SUBSCRIBER message sent from the first user terminal 10 and determines whether to allow the message according to its own policy, and generates an appropriate response message to the first user terminal 10. To pass. If the request message is allowed, the presence server 100 transmits all the subscriber information requesting the status information of the first user terminal 10 that is managed through the NOTIFY message (not shown).

In this state, when the second user terminal 20 transmits a SUBSCRIBER presence message to the presence server 100 in order to obtain the presence information of the first user terminal 10 (S302), the presence server 100 receives a second message. The user terminal 20 transmits information indicating that the user terminal 10 has requested the state information to the first user terminal 10 through the NOTIFY winfo message (S303).

When the first user terminal 10 receives the NOTIFY winfo message requesting its own status information, the first user terminal 10 confirms the information of the second user terminal 20 requesting the status information to the first user, and the second user from the first user. You are asked to give or deny status information about. At this time, the input of the permission or rejection of providing status information for the second user is made through the XCAP client 13, and is provided to the XML mixing unit 14 as XML-based XCAP data (S304).

If in parallel with step S304, the first user calls through a CPL client 12 a call processing command for the second user, e.g., a call processing specifying that the call received from the second user is forwarded to a specific cellular phone. If a command is input, this call processing command is provided to the XML mixing unit 14 as CPL data (S305).

When the CPL data and the XCAP data are provided to the XML mixing unit 14 as described above, the XML mixing unit 14 mixes the CPL data and the XCAP data based on XML to create the XCAP / CPL mixing data (S306), and the XCAP / CPL mixing. The data is provided to the mixing data processor 200 (S307).

On the other hand, when the XML mixing unit 14 receives only one type of data, that is, data of one of the CPL data or the XCAP data, the XML mixing unit 14 directly provides the mixing data processing unit 200 without mixing the same.

The mixing data processing unit 200 matches the data provided by the XML mixing unit 14 with the identification information of the user and stores the data in the mixing data storage unit 220.

In the meantime, when the first user terminal 10 provides the presence server 100 with its own state information (that is, the presence information) as a PUBLISH presence message (S308), the presence server 100 receives the first user terminal ( In response to receiving the state information of 10), a message inquiring whether the information is provided to the mixing data processor 200 to determine whether the state information of the first user terminal 10 may be transmitted to the second user terminal 10. It is transmitted (S309).

As the received query contents are related to the XCAP data, the XCAP processing unit 242 of the mixing data processing unit 200 provides the received query contents to the XML separation unit 230 through the XCAP interface (S310).

Then, the XML separating unit 230 extracts XCAP data for the second user registered by the first user from the information stored in the mixing data storage unit 220. In this case, the XCAP data is mixed with the CPL data. The XCAP data is separated from the XCAP / CPL mixing data (S311).

The XML separating unit 230 provides the separated XCAP data to the XCAP processing unit 242, and the XCAP processing unit 242 provides the XCAP data to the presence server 100 (S312).

The presence server 100 confirms permission to provide status information to the second user through the received XCAP data, and then includes the status information received from the first user in the NOTIFY presence message corresponding to the SUBCRIBER presence message. Provided to the terminal 20 (S313).

Accordingly, the second user terminal 20 receiving the NOTIFY presence message checks and displays the online state of the first user terminal 10 so that the second user can know that the first user is currently online.

In this state, if the second user makes a call connection request to the first user terminal 10, a call connection request message (INVITE message) is received by the SIP server 300 (S314).

The SIP server 300 identifies the person requesting the call connection (the second user terminal) and the person to call the call (the first user terminal) in the received call connection request message, and checks whether there is a CPL script registered by the first user. In order to query the mixing data processing unit 200 whether there is a CPL script of the first user (S315).

As the received query contents are related to the CPL script, the CPL processing unit 241 of the mixing data processing unit 200 provides the received query contents to the XML separation unit 230 through the CPL interface (S316).

Then, the XML separating unit 230 extracts the CPL data registered by the first user from the information stored in the mixing data storage unit 220. At this time, when the CPL data is mixed with the XCAP data, the corresponding XCAP / CPL mixing data. In step S317, the CPL data is separated.

The XML separating unit 230 provides the CPL data thus obtained to the CPL processing unit 241, and the CPL processing unit 241 provides the CPL data to the SIP server 300 (S318).

When the SIP server 300 receives the CPL data registered by the first user, the SIP server 300 recognizes a call processing instruction for forwarding the call received from the second user to the mobile phone through the CPL data, and accordingly the first user calls the call. Call the registered mobile phone (S319).

The embodiments of the present invention described above are not implemented only through the apparatus and the method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. Implementation may be easily implemented by those skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a schematic block diagram of a VoIP system according to an embodiment of the present invention.

2 is a diagram illustrating a main configuration of a VoIP system according to an embodiment of the present invention.

3 is a data flow diagram illustrating a method of integrating XCAP data and CPL data according to an embodiment of the present invention.

Claims (10)

Mixing data processing unit that receives and stores the mixed XCAP / CPL mixing data based on XML from the user terminal, and separates the XCAP / CPL mixing data into XCAP data and CPL data based on XML upon external request and provides the corresponding data. ; Register and maintain the presence information, which is the online status information of each user terminal registered as a subscriber, to inform the user of the presence information of the user, and interlock with the mixing data processing unit to identify the XCAP data registered by the subscriber and information on a specific person. Presence server to determine whether to provide; And In response to the SIP-based call connection request, the caller of the caller terminal to the destination terminal, but in conjunction with the mixing data processing unit to identify the CPL data registered by the subscriber, and includes a SIP server for determining a call processing command for a specific person doing, VoIP system that integrates XCAP and CPL data. The method of claim 1, The mixing data processor, Mixing data receiving unit for receiving the XCAP / CPL mixing data from the user terminal as an XML interface, A mixing data storage unit for storing the XCAP / CPL mixing data received in the mixing data receiving unit according to identification information of a user; A CPL processing unit which interfaces with the SIP server to obtain CPL data of a specific user requested by the SIP server and provide the CPL data to the SIP server; An XCAP processing unit which interfaces with the presence server and obtains XCAP data of a specific user requested by the presence server and provides the same to the presence server; In response to a request of the CPL processing unit or the XCAP processing unit, an XML separation unit for extracting the XCAP / CPL mixing data of a specific user stored in the mixing data storage unit, separating the extracted XCAP / CPL mixing data to provide the corresponding data VoIP system that integrates XCAP and CPL data. The method of claim 2, The mixing data receiver receives the XCAP / CPL mixing data having a form in which a portion between <incoming> and </ incoming> of the CPL data is included in the XCAP data, In this case, the XCAP / CPL mixing data maps the <incoming> and <location> tags of the CPL data to the <tuple> element of the XCAP data, and puts the grouping names set in the remaining tags including the <address-switch> in common and the XCAP is mixed. VoIP system that integrates XCAP and CPL data to differentiate data. The method of claim 3, The CPL processing unit, Extract the grouped portion from the XCAP / CPL mixing data, remove the grouping name from the extracted grouped portion, and make the CPL data containing the contents of the grouped portion and provide the XCAP data and the CPL data to the SIP server. Integrated VoIP system. The method according to claim 3 or 4, And the XCAP processing unit integrally processes the XCAP data and the CPL data provided to the presence server by creating the XCAP data in a portion other than the grouped portion of the XCAP / CPL mixing data. An XCAP / which generates first XCAP data according to a user input in a first user terminal, generates first CPL data according to another input of the user, and then mixes the first XCAP data and the first CPL data When creating and sending CPL mixing data, A first step of receiving and storing the XCAP / CPL mixing data transmitted from the first user terminal in a first storage; When a request event for presence information of the first user terminal is generated from a second user terminal, after extracting the XCAP / CPL mixing data of the first user terminal stored in the first storage, the extracted XCAP / CPL mixing data A second step of extracting a CPL data portion from the first CPL data and providing the first CPL data; And When a call connection request event from the second user terminal to the first user terminal occurs, the XCAP / CPL mixing data of the first user terminal stored in the first storage is extracted and then extracted from the extracted XCAP / CPL mixing data. And a third step of creating and providing the first XCAP data with a portion missing the CPL data portion. How to integrate XCAP data with CPL data. The method of claim 6, And the XCAP / CPL mixing data is a form in which a portion between <incoming> and </ incoming> of the first CPL data is included in the first XCAP data. The method of claim 7, wherein The XCAP / CPL mixing data maps the <incoming> and <location> tags of the first CPL data to the <tuple> element of the first XCAP data and uses the grouping name set in the remaining tags, including <address-switch>. A method of integrating XCAP data and CPL data that commonly puts it apart from XCAP data. The method of claim 8, The second step extracts the grouped portion from the XCAP / CPL mixing data, removes the grouping name from the extracted grouped portion, and makes the first CPL data and the CPL data containing the contents of the grouped portion. How to consolidate data. The method according to claim 8 or 9, The third step is a method for integrating and processing the XCAP data and the CPL data to make the first XCAP data in a portion of the XCAP / CPL mixing data except the grouped portion.

Images