KR20050120221A - System and method for furnishing the user agent profile using cache memory - Google Patents

Abstract

The present invention relates to a mobile communication terminal information (UA (User Agent) Profile) providing system and method therefor, the mobile communication terminal information periodically updated in the memory of the web server cached to the mobile according to the information request from the outside In order to provide a mobile communication terminal information providing system and a method using memory caching for transmitting communication terminal information, in the mobile communication terminal information providing system, and stores the mobile terminal information (UA) profile A terminal information database; A web application server for periodically monitoring the update history of the mobile communication terminal information stored in the terminal information database and notifying the fact that the terminal information has been updated; And periodically caching the corresponding mobile communication terminal information stored in the terminal information database as the web application server notifies the terminal information update, and the cached mobile communication in response to a request for transmitting terminal information from a content provider server. And a terminal information providing server for querying the corresponding mobile communication terminal information in the terminal information and transmitting the terminal information inquiry result to the content provider server.

Description

System and method for providing mobile communication terminal information using memory caching {System and method for furnishing the user agent profile using cache memory}

The present invention relates to a system and method for providing a mobile terminal information (UA) user profile, and more particularly, to request information from the outside by caching periodically updated mobile terminal information in a memory of a web server. The present invention relates to a mobile communication terminal information providing system using memory caching and a method for transmitting the corresponding mobile communication terminal information.

Recently, various additional services have been provided to users through mobile communication terminals due to the development of mobile communication technology. For example, a music gift service that presents music to a friend to play music on the other party's mobile terminal, a My Bell service that downloads a specific ringtone and outputs the specified ringtone on the mobile terminal when a call comes in, and receives from the other party. A picture friend service for changing the expression of a character on a background screen of a mobile communication terminal according to a phrase of a short message, and a multimedia messaging service for sending a multimedia message with an image file attached to the counterpart mobile communication terminal.

In the above service, the content provider or mobile service provider responds to the service request of the customer, and the mobile terminal or counterpart mobile terminal information (UA) profile (eg, resolution / pixel number of the LCD, Music playback function, Internet communication function, manufacturer, etc.) (hereinafter referred to as "terminal information") is determined to transmit content suitable for the corresponding mobile communication terminal.

For example, when a user selects a ringtone of 64 poly and presents it to the other party, the content provider determines whether the mobile terminal of the other party can output the ringtone of 64 poly. Then, the content provider transmits the ringtone to the other party's mobile terminal if the mobile terminal supports 64 Poles. If the mobile terminal does not support 64 poly, the content provider is suitable for the support function of the other mobile terminal. Induce them to choose a ringtone.

The terminal information providing system provides mobile terminal information in response to a request for information from a content provider in a three-tier structure of a web, a web, a database, and a database.

That is, the content provider requests a specific mobile terminal information inquiry by accessing the mobile terminal information providing server through the web, and the mobile terminal information providing server extracts the corresponding mobile terminal information from the database accordingly. To send.

However, in the conventional method as described above, the mobile communication terminal information providing server is unable to provide the mobile communication terminal information quickly and stably in response to various information requests from numerous content providers.

That is, the mobile terminal information providing server searches the database every time according to the individual requests of numerous content providers and processes the mobile terminal information (e.g., converts the data format to the supported data format of the content provider). Because it is sent to the corresponding content provider, it is impossible to respond quickly to each content provider's request, and accordingly, the access time and cumulative number of company accesses of the content provider waiting for the response are increased. There is a problem that the load is increased.

On the other hand, in the conventional method as described above, when a user newly joins (opens) a mobile communication provider through a mobile communication terminal, the mobile communication terminal information provided by the manufacturer of the mobile communication terminal is used as the mobile communication terminal information of the subscriber. Register at

Table 1 below shows mobile communication terminal information provided by a manufacturer of a mobile communication terminal.

Type meaning Sample Remarks A Wireless Operator (Prefix) 011: SKT017: STI016: KTF018: HSP019: LGT010: 010IRM: IXX 010: Used for the number integration station IRM: The upper 2 digits of the 10 digits are written after the letter "I" B Service method WAP: 1SK WEB: 2 Stinger: 3IS-95C WAP: 4EV-DO WAP: 5WCDMA WAP: 6 Wireless Internet service method, set to 4 if IS-95C terminal is synchronized to 95C network. Set to 5 if EV-DO terminal is synchronized to EV-DO network and connected to WAP. C Terminal type IS-95A Cellular Phone: 1PDA: 2Smart Phone: 3VMT Terminal: 4IS-95C Cellular Phone: 5EV-DO Terminal: 6WCDMA Terminal: 7 DD Handset manufacturer Samsung: SS Hyundai: HDLG: LGSKTT: SK Hanwha: HH Motorola: MT Nokia: NO EE Terminal type by company LG WEBER865: 00SK IM1000: 01HD Mate: 02 Maximum number of device models by company: 99 FF Browser type AU system: 00Ericsson: 01 Nokia: 02 Telson: 03 Infraware: 15 Maximum number of browsers: 99 types NGB is displayed as 1X if the terminal is added NGB Download Descriptor is displayed as 2X If the terminal receives download through WAM and interface with WiPI 1.2 or higher, 3X is indicated as 3X .. .. .. ..

By the way, the conventional method as described above does not vary the mobile communication terminal information provided by the manufacturer of the mobile communication terminal, and is limited to only a specific function of the mobile communication terminal, so that various service requirements of the content provider, that is, the user It is not possible to provide the corresponding mobile communication terminal information.

In addition, in the above-described conventional method, since the information registered at the time of opening the mobile communication terminal is maintained as it is, the corresponding mobile communication terminal information is changed (for example, the Internet function is changed according to program loading). , Hardware upgrades, etc.), but the changes are not registered in the database.

Therefore, by providing a variety of information on the mobile terminal, the content provider can provide the user with content that meets the various service requirements of the customer, and the user and the relevant parties continuously update the updated information of the mobile terminal There is an urgent need for technology that will enable it.

The present invention has been proposed to solve the above problems and to meet the above demands. The mobile communication terminal is calibrated by periodically updating the mobile communication terminal information in the memory of the web server and requesting information from the outside. It is an object of the present invention to provide a mobile communication terminal information providing system and method using memory caching for transmitting information.

According to an aspect of the present invention, there is provided a mobile communication terminal information providing system, comprising: a terminal information database storing mobile communication terminal information (UA) profile; A web application server for periodically monitoring the update history of the mobile communication terminal information stored in the terminal information database and notifying the fact that the terminal information has been updated; And periodically caching the corresponding mobile communication terminal information stored in the terminal information database as the web application server notifies the terminal information update, and the cached mobile communication in response to a request for transmitting terminal information from a content provider server. And a terminal information providing server for querying the corresponding mobile communication terminal information in the terminal information and transmitting the terminal information inquiry result to the content provider server.

On the other hand, the method of the present invention, in the method for providing mobile communication terminal information, the mobile communication terminal information (UA (User Agent) Profile) stored in the terminal information database in accordance with the periodic notification of the terminal information update from the web application server First caching periodically); A second step of querying corresponding mobile communication terminal information among the mobile communication terminal information cached in the first step according to a request for transmitting terminal information from a content provider; And a third step of transmitting the terminal information inquiry result in the second step to the content provider.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

1 is a configuration diagram of an embodiment of a mobile communication terminal information providing system using memory caching according to the present invention.

As shown in FIG. 1, the content provider server 100 includes a web connection unit (HTTP client) 10, an authentication / encryption unit 11, and an XML parser 12. ), A Customer Profile Request (13), a Terminal Information Request (UA Profile Request) 14, and a Contents Application (Contents Provider Application) 15.

The terminal information providing server 200 includes a web server 20, an authentication checker 21, a document generator 22, and a terminal information inquiry unit. An RDF (Resource Description Format) Server 23, a terminal information cache storage unit (Cache DB) 24, and a cache updater 25 are included.

The web application server 300 includes an update notifier 30, a configurator 31, a customer profile manager 32, and a terminal information manager. Profile Manager) 33 and various applications (Web-Application) (34).

In addition, the mobile terminal information (UA Profile) is registered and stored in the terminal information database 400.

In addition, the mobile communication service provider server 500 includes an update agent 50 and a terminal information copy storage unit 51.

In the present invention, the mobile communication terminal information providing system is composed of a three-layer structure of the terminal information providing server 200, the web application server 300 and the terminal information database 400, but the terminal is stored in the terminal information database 400 The information is cached in the terminal information cache storage unit 24 of the terminal information providing server 200, and the web application server 300 is configured in response to a terminal information request from the outside (particularly, the content provider server 100) through the web. It directly retrieves this cached terminal information and provides it to the content provider.

In addition, the update notification unit 30 of the web application server 300 periodically monitors the update information of the terminal information stored in the terminal information database 400, the terminal of the terminal information providing server 200 in accordance with the terminal information update The terminal information cached in the information cache storage unit 24 is continuously updated so that the latest terminal information is provided to the content provider.

In addition, the terminal information registered in the terminal information database 400 is diversified and provided to the content provider so that the content provider can provide services that meet various requirements of the user.

In addition, the terminal information is stored in the terminal information database 400 in the form of a resource description format (RDF) file of a Uniform Resource Identifier (URI) method so that the terminal information can be easily queried and changed.

The web connection unit 10 of the content provider server 100 is connected to the terminal information providing server 200 and the data related to the terminal information request and the terminal information response (eg, terminal information request message, terminal information inquiry result, etc.). Send and receive. At this time, the web connection unit 10 of the content provider server 100 is connected to the terminal information providing server 200 through the company ID and password given from the terminal information providing server 200 side.

The authentication / encryption unit 11 of the content provider server 100 checks whether the customer information request of the customer information requesting unit 13 and the terminal information request of the terminal information requesting unit 14 are suitable (the ID of the corresponding customer and Password check) to authenticate and encrypt the information request message to be transmitted to the terminal information providing server 200 side.

The document analyzing unit 12 of the content provider server 100 interprets the terminal information inquiry result in the XML form received from the terminal information providing server 200 to be read by the content application 15.

The customer information requesting unit 13 of the content provider server 100 determines a URI of the corresponding customer information according to the customer information request of the content application 15 and transmits the URI to the terminal information providing server 200. Ask.

The terminal information request unit 14 of the content provider server 100 determines the URI of the corresponding mobile communication terminal information according to the terminal information request of the content application 15 to be transmitted to the terminal information providing server 200. Requests terminal information.

The content application 15 of the content provider server 100 responds to a request of a user of the mobile communication terminal connected to the content provider server 100 (for example, music selection to be presented to the other party's mobile communication terminal). Perform a known function of providing content.

The web connection unit 20 of the terminal information providing server 200 is connected to the content provider server 100 to receive data related to the terminal information request and the terminal information response (eg, terminal information request message, terminal information inquiry result, etc.). Send and receive.

When the company authentication unit 21 of the terminal information providing server 200 receives the customer information request and the terminal information request from the content provider server 100, the ID and password of the content provider server 100 may be examined. Verify the rights of the content provider. At this time, the company authentication unit 21 preferably decrypts the encrypted terminal information request message and then performs an authentication process.

The document generation unit 22 of the terminal information providing server 200 uses the terminal information inquiry unit 23 to display an inquiry result for the customer information request and the terminal information request from the content provider server 100 in the form of XML. Create a document.

The terminal information inquiry unit 23 of the terminal information providing server 200 uses the corresponding URI as a parameter according to the customer information request and the terminal information request from the content provider server 100 and the terminal information cache storage unit 24. Search for the information in.

The terminal information inquiry unit 23 displays web server information according to a standard specification (RDF method) defined in "W3C CC / PP (Composite Capability / Preference Profiles: Structures and Vocabularies Recommendation)". Regardless of the size, it is preferable that the web server information can be transmitted to each mobile communication terminal (web surfing) according to the screen size and processing power of each mobile communication terminal.

In the terminal information cache storage unit 24 of the terminal information providing server 200, the terminal information stored in the terminal information database 400 is cached by the cache updater 25. The terminal information cache storage unit 24 is preferably implemented as a disk cache using a portion of a cache memory or a main memory device which is a dedicated fast storage device.

The cache updater 25 of the terminal information providing server 200 receives terminal information update facts from the update notification unit 30 of the web application server 300. The terminal information is updated in the terminal information database 400. To the terminal information cache storage unit 24 to be cached. At this time, the update notification unit 30 notifies the cache updater 25 of the terminal information history updated in the terminal information database 400, and accordingly, the terminal information database ( In step 400, the terminal information is updated and cached in the terminal information cache storage 24.

The update notification unit 30 of the web application server 300 monitors the terminal information database 400 periodically (for example, at intervals of 10 seconds, etc.), and as the terminal information is added or changed, the terminal information providing server 200 And the fact that the terminal information update to the mobile communication server 500. At this time, the update notification unit 30 also transmits the updated terminal information, so that the corresponding component can recognize the updated terminal information.

The environment setting unit 31 of the web application server 300 sets various environments necessary for performing the function of the update notification unit 30 (eg, monitoring period of the terminal information database 400, and setting of a transmission data type when notifying update facts). Etc.)

The customer information manager 32 of the web application server 300 includes information (eg, name, address, fee) of a customer who owns the mobile communication terminal 10 (particularly, a customer who subscribes to the mobile communication service provider through the mobile communication terminal). Billing related information, mobile communication terminal number, etc.), and issues a web ID and password to the corresponding customer to map the mobile communication terminal information stored in the ID and terminal information database 400.

In addition, the customer information management unit 32 provides a known additional service (for example, change of a plan, personal information, home call setting, etc.) to a customer connected to the terminal information providing server 200 through the web.

The terminal information manager 33 of the web application server 300 provides the mobile communication terminal information stored in the terminal information database 400 to a customer accessing the terminal information providing server 200 through the web. At this time, the terminal information manager 33 inquires the terminal information stored in the terminal information database 400 using the MDN and the client's web ID as parameters according to the terminal information request of the customer.

Various applications 34 of the web application server 300 refer to mobile communication terminal information stored in the terminal information database 400 to provide customers and / or contents connected to the terminal information providing server 200 through the web. To the company, the customer complaint processing function 34a, the additional service code management function 34b, the terminal information management function 34c, the content provider authority management 34d, the test number management function 34e, and various data statistics functions ( 34f) and the like.

The terminal information database 400 stores mobile communication terminal information (UA) and content provider information.

The mobile communication terminal information is the personal information of the customer and the information of the mobile communication terminal opened by the update agent 50 when the user newly subscribes to the mobile communication service provider or converts from another mobile communication service provider through the mobile communication terminal. Is obtained and stored in the terminal information database 400.

In addition, the mobile terminal information, the user changes the hardware platform (HardwarePlatform) of the mobile terminal through the mobile carrier, content provider and terminal manufacturer (e.g., change the connection method of the Bluetooth module), software functions (SoftwarePlatform) (e.g. Java platform change, video player upgrade, voice / video codec patch, etc.), network function (NetworkCharacteristics) (e.g. infrared (IrDA) communication method change (i.e. IrOBEX / 1.1 settings), Security program installations), change browser functionality (BrowserUA) (e.g., Internet browser patches, Java applet upgrades, etc.), and swap functionality (WapCharacteristics) (e.g., change the Digital Right Managemnet (DRM) preferences (i.e., MP3 files) Playing days, etc.), WmlScriptLibraries patches, etc.), changing push features (PushCharacteristics) (e.g., changing the format of pushable data (i.e. setting text / html), etc.) Changes in multimedia message functionality (MmsCharacteristics) (e.g., support data format change of multimedia messages (e.g. video / mpeg_4), etc. Information related to the changed mobile communication terminal is obtained by the update agent 50 and stored in the terminal information database 400.

That is, as the mobile communication terminal information stored in the terminal information database 400 is changed (for example, a mobile service provider providing service change, terminal H / W, S / W function upgrade, etc.), the corresponding mobile communication terminal or / and mobile The update agent 50 of the service provider server 500 may change the corresponding terminal information of the terminal information database 400.

At this time, the mobile communication terminal information stored in the terminal information database 400 is authorized by the subscriber or / and the administrator of the mobile operator side, such as addition, change, deletion, etc. URI (store location path) of the terminal information Can be accessed and updated.

Mobile communication terminal information registered by the URI method will be described in detail with reference to FIGS. 2A to 2H.

Meanwhile, the content provider information is stored in the terminal information database 400 when the content provider subscribes to the mobile communication provider and the information of the corresponding content provider is obtained.

The update agent 50 of the mobile communication service provider server 500 receives the terminal information update facts from the update notification unit 30 of the web application server 300. The terminal information is updated in the terminal information database 400. Copy and update the terminal information copy storage unit 51 and store it.

The copy of the terminal information stored in the terminal information database 400 by the update agent 50 is stored in the terminal information copy storage unit 51 of the mobile service provider server 500.

2A to 2H are conceptual model diagrams of mobile communication terminal information used in the present invention.

In the present invention, the mobile communication terminal information defined in the "OMA UA Profile" standard specification and the "W3C CC / PP" standard specification is categorized into eight components, and each category component is the RDF model. Describe.

FIG. 2A shows an item related to a hardware function (HardwarePlatform), FIG. 2B shows an item related to a software function (SoftwarePlatform), and FIG. 2C shows an item related to a network function (NetworkCharacteristics), and FIG. 2D FIG. 2E illustrates an item related to a browser function (BrowserUA), FIG. 2E illustrates an item related to a swap function (WapCharacteristics), and FIG. 2F illustrates an item related to a push function (PushCharacteristics) of a mobile communication terminal. FIG. 2G illustrates an item related to a multimedia message function (MmsCharacteristics), and FIG. 2H illustrates an item related to a mobile service provider service function (SvcCharacteristics).

Namespace Alias (Prefixes) described in each component shown in FIGS. 2A to 2H are as follows.

xmlns: rdf = “http://www.w3.org/1999/02/22-rdf-syntax-ns#”

xmlns: rdfs = “http://www.w3.org/2000/01/rdf-schema#”

-xmlns: prf = “http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#”

-xmlns: mms = “http://www.wapforum.org/profiles/MMS/ccppschema-20010111#”

-xmlns: prfext = “http://mobileinternet.nate.com/tech/rdf/profiles/UAPROF/ccppschema-20030811#”

xmlns: ccpp = “http://www.w3.org/2002/11/08-ccpp-schema#”

As shown in FIGS. 2A to 2H, "rdf: Bag" and "rdf: Seq" are expressed in an abbreviated form for convenience of description, but the full URI_Ref of the URI is shown. It is preferable to express as.

The mobile communication terminal information illustrated in FIGS. 2A to 2H is implemented in the form of an RDF file and stored in the terminal information database 400. Hereinafter, the contents of the RDF file in which the mobile communication terminal information of the model name "SCH-V330" released by "Samsung Electronics Co., Ltd." is registered will be described.

<? xml version = "1.0" encoding = "UTF-8"?>

-<rdf: RDF xmlns: ccpp = "http://www.w3.org/2002/11/08-ccpp-schema#" xmlns: mms = "http://www.wapforum.org/profiles/MMS/ ccppschema-20010111 # "xmlns: prf =" http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226# "xmlns: prfext =" http://mobileinternet.nate.com/tech/rdf/ profiles / UAPROF / ccppschema-20030811 # "xmlns: rdf =" http://www.w3.org/1999/02/22-rdf-syntax-ns# "xmlns: rdfs =" http: //www.w3. org / 2000/01 / rdf-schema # ">

-<rdf: Description rdf: ID = "02717">

<prf: component>

-<rdf: Description ID = "HardwarePlatform">

<rdf: type rdf: resource = "http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#HardwarePlatform" />

<prf: BitsPerPixel> 18 </ prf: BitsPerPixel>

<prf: Model> SCH-V330 Upgrade </ prf: Model>

<prf: ScreenSize> 176x192 </ prf: ScreenSize>

<prf: ScreenSizeChar> 22x10 </ prf: ScreenSizeChar>

<prf: Vendor> Samsung </ prf: Vendor>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "SoftwarePlatform">

<rdf: type rdf: resource = "http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#SoftwarePlatform" />

<prf: CcppAccept>

-<rdf: Bag>

<rdf: li> application / jvm; </ rdf: li>

<rdf: li> image / jpg; size = 128x96 </ rdf: li>

<rdf: li> player / vnd.skt.gnex; ver = 2 </ rdf: li>

<rdf: li> video / skm; ver = 2.3 </ rdf: li>

<rdf: li> image / vnd.skt.sis; ver = P10 </ rdf: li>

<rdf: li> audio / vnd.skt.poly; ver = 30 </ rdf: li>

<rdf: li> application / x-mm-tcm; ver = 1 </ rdf: li>

</ rdf: Bag>

</ prf: CcppAccept>

<prf: SoftwareNumber> 11 </ prf: SoftwareNumber>

<prfext: SoftwareScreenSize> 176x178 </ prfext: SoftwareScreenSize>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "BrowserUA">

<rdf: type rdf: resource = "http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#BrowserUA" />

<prf: BrowserName> AU </ prf: BrowserName>

<prf: BrowserVersion> 1.0 </ prf: BrowserVersion>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "NetworkCharacteristics">

<rdf: type rdf: resource = "http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#NetworkCharacteristics" />

-<prf: SupportedBearers>

-<rdf: Bag>

<rdf: li> CDMA2000-1X-EVDO_CDMA_PACKET </ rdf: li>

<rdf: li> IS-95_CDMA_SMS </ rdf: li>

<rdf: li> CDMA2000-1X_CDMA_PACKET </ rdf: li>

<rdf: li> IS-95B_CDMA_PACKET </ rdf: li>

<rdf: li> IS-95_CDMA_CSD </ rdf: li>

<rdf: li> IS-95_CDMA_PACKET </ rdf: li>

<rdf: li> IS-95A_CDMA_PACKET </ rdf: li>

</ rdf: Bag>

</ prf: SupportedBearers>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "WapCharacteristics">

<rdf: type rdf: resource = "http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20030226#WapCharacteristics" />

<prf: WapScreenSize> 176x160 </ prf: WapScreenSize>

-<prf: WmlScriptLibraries>

-<rdf: Bag>

<rdf: li> CryptoEx </ rdf: li>

<rdf: li> URL </ rdf: li>

<rdf: li> String </ rdf: li>

<rdf: li> Dialogs </ rdf: li>

<rdf: li> Float </ rdf: li>

<rdf: li> Lang </ rdf: li>

<rdf: li> PSTOR </ rdf: li>

</ rdf: Bag>

</ prf: WmlScriptLibraries>

<prf: WmlScriptVersion>

-<rdf: Bag>

<rdf: li> 1.2 </ rdf: li>

<rdf: li> 1.2.10 </ rdf: li>

</ rdf: Bag>

</ prf: WmlScriptVersion>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "MmsCharacteristics">

<rdf: type rdf: resource = "http://www.wapforum.org/profiles/MMS/ccppschema-20010111#MmsCharacteristics" />

<prfext: MmsVersion>

-<rdf: Bag>

<rdf: li> 1.5 </ rdf: li>

</ rdf: Bag>

</ prfext: MmsVersion>

</ rdf: Description>

</ prf: component>

<prf: component>

-<rdf: Description ID = "SvcCharacteristics">

<rdf: type rdf: resource = "http://mobileinternet.nate.com/tech/rdf/profiles/UAPROF/ccppschema-20030811#SvcCharacteristics" />

-<prfext: Supported-Services>

-<rdf: Bag>

<rdf: li rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#CI" />

<rdf: li rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#CellBroadcast" />

<rdf: li rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#Lettering" />

<rdf: li rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#NATEDrive" />

<rdf: li rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#SKAD" />

</ rdf: Bag>

</ prfext: Supported-Services>

-<rdf: Description rdf: resource = "http://mobileinternet.nate.com/rdf/service-name#SKAD">

<rdf: type rdf: resource = "http://mobileinternet.nate.com/tech/rdf/profiles/UAPROF/ccppschema-20030811#SvcProfile" />

<prfext: Svc-Version>

-<rdf: Bag>

<rdf: li> 1.02 </ rdf: li>

</ rdf: Bag>

</ prfext: Svc-Version>

</ rdf: Description>

</ rdf: Description>

</ prf: component>

</ rdf: Description>

</ rdf: RDF>

3 is a flow chart of an embodiment of a mobile terminal information providing process using memory caching according to the present invention.

First, the terminal information providing server 200 requests the terminal information database 400 to transmit terminal information (or content provider information) (S300). At this time, the terminal information providing server 200 requests the terminal information database 400 to accept the terminal information inquiry or read the terminal information (or content provider information) or the terminal information (or content provider information). ) Can also send a transmission request message. In this case, the mobile communication terminal information is the personal information of the corresponding customer and opened by the update agent 50 when the user newly subscribes to the mobile communication provider through the mobile communication terminal or switches from another mobile communication provider. Information is obtained and stored in the terminal information database 400. Meanwhile, the content provider information is stored in the terminal information database 400 when the content provider subscribes to the mobile communication provider and the information of the corresponding content provider is obtained.

Then, the terminal information database 400 transmits all of the terminal information (or content provider information) previously stored to the terminal information providing server 200 (S301). At this time, the terminal information database 400 transmits all the information of the record unit previously stored to the terminal information providing server 200.

Then, the terminal information providing server 200 caches all the information received in the terminal information cache storage unit 24 (S302).

Thereafter, the terminal information providing server 200 waits for the terminal information request and the customer information request from the content provider server 100 to be received, and the web application server 200 is periodically stored in the terminal information database 400. The terminal information (or content provider information) update history is monitored (S303). Here, the terminal information stored in the terminal information database 400 is updated by the outside (particularly, the party on the mobile communication provider side and / or the user on the mobile communication terminal side).

Then, the terminal information previously stored in the terminal information database 400 is updated (S304).

Then, the web application server 300 checks the terminal information update history (S305).

Then, the web application server 300 notifies the terminal information providing server 200 of the terminal information update (S306). At this time, the web application server 300 transmits the newly added or modified record unit information together with the terminal information update notification message so that the terminal information providing server 200 can recognize the details of the terminal information. On the other hand, it will be readily understood by those skilled in the art that not only the terminal information but also the content provider information is updated and thus notified.

Then, the terminal information providing server 200 requests the updated terminal information transmission to the terminal information database 400 (S307).

Then, the terminal information database 400 transmits the terminal information to the terminal information providing server 200 (S308).

Then, the terminal information providing server 200 updates and caches the terminal information received in the terminal information cache storage unit 24 (S309). Here, it will be readily understood by those skilled in the art that a process of continuously updating and caching the terminal information updated in the terminal information database 400 to the terminal information cache storage unit 24 is continuously performed.

Meanwhile, the terminal information providing server 200 waits for the terminal information request and the customer information request from the content provider server 100 to be received after the "S302" process, and the terminal information is provided from the content provider server 100. It is required (S310). At this time, the content provider needs information of the other party's mobile terminal in order to provide content about a mobile terminal user's request (eg, music selections to be presented to the other party's mobile terminal, etc.). The server 100 performs a process of requesting the terminal information providing server 200 to transmit information of the corresponding mobile communication terminal.

Then, the content provider server 100 transmits the company ID and password and the URI of the corresponding mobile communication terminal information (S311), and requests the terminal information providing server 200 to transmit the corresponding terminal information. At this time, the content provider server 100 transmits a terminal information request message including a company ID and password and the URI of the corresponding mobile communication terminal information to the terminal information providing server 200.

Then, the terminal information providing server 200 receives the terminal information request message and determines the header information of the message (S312). In this case, the terminal information providing server 200 notifies the content provider server 100 of the header information error if there is an error in the determined header information (for example, a message format is inappropriate or the number of parameters is insufficient). If there is no error in the information, proceed with the content provider certification process.

Then, the terminal information providing server 200 authenticates the content provider by checking the company ID and password included in the terminal information request message (S313). At this time, the terminal information providing server 200 notifies the content provider server 100 that the authentication failed when the content provider authentication fails (for example, non-registered company ID, company ID and password mismatch, etc.), and the content provider. If the authentication is successful, the terminal information inquiry process is performed. In addition, during the content provider certification process, the authority to check the content provider may be checked so that only the information corresponding thereto may be viewed.

Then, the terminal information providing server 200 queries the terminal information from the terminal information cache storage unit 24 (S314). In this case, the terminal information providing server 200 notifies the content provider server 100 of the absence of terminal information if the terminal information does not exist in the terminal information cache storage unit 24.

Thereafter, the terminal information providing server 200 generates an XML document corresponding to the terminal information inquiry result (S315).

Then, the terminal information providing server 200 transmits the terminal information search result in the form of XML document to the content provider server 100 (S316).

Then, the content provider server 100 analyzes the XML document to confirm the terminal information (S317). Thereafter, the content provider server 100 performs a known content providing function by referring to the checked information of the mobile communication terminal.

While the content of the present invention has been described by way of examples, the embodiments of the present invention are merely illustrative of the present invention and should not be construed as limiting the scope of the present invention. Those skilled in the art to which the present invention pertains may modify or alter the present invention in various forms within the principles and scope described in the claims herein.

The present invention as described above, by periodically caching the updated mobile communication terminal information and transmits the mobile communication terminal information according to the information request from the outside, it is possible to improve the speed of inquiring the mobile communication terminal information, accordingly There is an effect that can quickly and reliably respond to a request for information transmission of a mobile terminal from a provider.

In addition, the present invention provides the content provider with various mobile communication terminal information of the customer as well as the mobile communication terminal information provided by the manufacturer of the mobile communication terminal, the content provider provides content that meets various service requirements to the user. It is effective to provide.

In addition, the present invention, so that the user or / and the related party can update the updated information of the mobile communication terminal through the RDF file registered by the URI method so that the changes of the mobile communication terminal can be continuously registered. It is effective.

1 is a configuration diagram of an embodiment of a mobile communication terminal information providing system using memory caching according to the present invention.

2A to 2H are conceptual models of mobile communication terminal information used in the present invention.

3 is a flow chart of an embodiment of a mobile terminal information providing process using memory caching according to the present invention.

* Explanation of symbols on the main parts of the drawing

100: content provider server 200: terminal information providing server

300: web application server 400: terminal information database

500: mobile communication service provider server 20: web connection unit

21: company certification unit 22: document generation unit

23: terminal information inquiry unit 24: terminal information cache storage unit

26: cache updater 30: update notification unit

Claims (16)

In the mobile communication terminal information providing system, A terminal information database storing mobile communication terminal information (UA) profile; A web application server for periodically monitoring the update history of the mobile communication terminal information stored in the terminal information database and notifying the fact that the terminal information has been updated; And As the web application server notifies the terminal information update, the mobile terminal periodically caches the corresponding mobile communication terminal information stored in the terminal information database, and the cached mobile communication terminal in response to a request for transmitting terminal information from a content provider server. Terminal information providing server for transmitting the terminal information inquiry result to the content provider server by inquiring the corresponding mobile communication terminal information from the information Mobile communication terminal information providing system using memory caching comprising a. The method of claim 1, The terminal information providing server, The mobile communication terminal information stored in the terminal information database is cached in the terminal information caching storage means, and when the terminal information update is notified from the web application server, the updated mobile communication terminal information is updated in the terminal information caching storage means. Cache updating means for caching the cache; The terminal information caching storage means for storing mobile communication terminal information by the cache updating means; Web connection means connected to the content provider server for transmitting and receiving the terminal information request-related data and the terminal information query result related data; Company authentication means for authenticating a specific content provider that has requested terminal information from the web connection means; Terminal information inquiry means for querying mobile communication terminal information stored in the terminal information caching storage means to generate a corresponding terminal information inquiry result when the terminal information transmission request is received from the content provider server authenticated by the company authentication means. ; And Document generation means for generating a document corresponding to the terminal information inquiry result by the terminal information inquiry means; Mobile communication terminal information providing system using memory caching comprising a. The method of claim 2, The company authentication means, And a content provider ID and password included in the terminal information request message received by the web connection unit to authenticate the inquiry authority of the corresponding content provider. The method of claim 2, The terminal information inquiry means, The terminal information caching is stored using the URI of the mobile communication terminal information included in the terminal information request message received by the web connection means as a request for transmission of terminal information from the content provider server authenticated by the company authentication means. A mobile communication terminal information providing system using memory caching, characterized in that the means for inquiring the corresponding mobile communication terminal information. The method of claim 1, The web application server, The controller periodically monitors whether the mobile communication terminal information stored in the terminal information database is added or changed according to an input signal from an external source, and updates the terminal information when the specific mobile communication terminal information is added or changed, and updates the terminal information. Update monitoring / notifying means for notifying the terminal information providing server of the details; And Environment setting means for setting various environments required to perform the function of the update monitoring / notification means Mobile communication terminal information providing system using memory caching comprising a. The method of claim 1, The content provider server, When the terminal information is required, memory caching, characterized in that for transmitting the terminal information transmission request message including the company ID and password granted from the terminal information providing server and the URI of the corresponding mobile communication terminal information to the terminal information providing server. Mobile communication terminal information providing system using. The method according to any one of claims 1 to 6, The mobile terminal information, Items related to hardware functions (HardwarePlatform), items related to software functions (SoftwarePlatform), items related to network functions (NetworkCharacteristics), items related to browser functions (BrowserUA), items related to swap functions (WapCharacteristics), push functions (PushCharacteristics) And information relating to an item related to a multimedia message function (MmsCharacteristics) and an item related to a mobile service provider providing service function (SvcCharacteristics). The method of claim 7, wherein The mobile terminal information, Mobile communication terminal information providing system using memory caching, characterized in that the information in the form of Resource Description Format (RDF) file registered in the URI (Uniform Resource Identifier) method in the terminal information database. In the mobile communication terminal information providing method, A first step of periodically caching mobile communication terminal information (UA) stored in a terminal information database according to periodic notification of terminal information update from a web application server; A second step of querying corresponding mobile communication terminal information among the mobile communication terminal information cached in the first step according to a request for transmitting terminal information from a content provider; And A third step of transmitting the terminal information inquiry result in the second step to the content provider; Mobile communication terminal information providing method using memory caching comprising a. The method of claim 9, The first step is, Requesting transmission of terminal information to the terminal information database and receiving and caching terminal information accordingly; Periodically receiving notification of terminal information update from the web application server; And Requesting transmission of the updated terminal information to the terminal information database, receiving and updating corresponding terminal information according to caching; Mobile communication terminal information providing method using memory caching comprising a. The method of claim 9, In the third step, And generating an XML document corresponding to the terminal information inquiry result in the second step and transmitting the generated XML document to the content provider. The method of claim 9, In the second step, The mobile communication terminal information cached in the first step by using the URI of the mobile communication terminal information included in the terminal information request message received from the content provider side in response to the request for transmitting the terminal information from the content provider side. The mobile terminal information providing method using memory caching, characterized in that for querying the corresponding mobile terminal information. The method of claim 12, The terminal information request message is a mobile terminal information providing method using a memory caching, characterized in that the message including the ID and password of the content provider and the URI of the specific mobile communication terminal information. The method according to any one of claims 9 to 13, The mobile terminal information, Items related to hardware functions (HardwarePlatform), items related to software functions (SoftwarePlatform), items related to network functions (NetworkCharacteristics), items related to browser functions (BrowserUA), items related to swap functions (WapCharacteristics), push functions (PushCharacteristics) And information related to a multimedia message function (MmsCharacteristics) and an item related to a mobile service provider providing service function (SvcCharacteristics). The method of claim 14, The mobile terminal information, Mobile information terminal information providing method using memory caching, characterized in that the information in the form of Resource Description Format (RDF) file registered in the URI (Uniform Resource Identifier) method in the terminal information database. To the terminal information providing server connected to the IP network, A first step of periodically caching mobile communication terminal information (UA) stored in a terminal information database according to periodic notification of terminal information update from a web application server; A second step of querying corresponding mobile communication terminal information among the mobile communication terminal information cached in the first step according to a request for transmitting terminal information from a content provider; And A third step of transmitting the terminal information inquiry result in the second step to the content provider; A computer-readable recording medium having recorded thereon a program for realizing this.