WO2007064071A2

WO2007064071A2 - System for providing subscriber manageable profile service, method of registration, and offer thereof

Info

Publication number: WO2007064071A2
Application number: PCT/KR2006/002918
Authority: WO
Inventors: Don-Sung Oh; Dae-Sik Kim; Myung-Sik Yoo; Pil-Jung Jung; Hyun-Joo Lee
Original assignee: Electronics And Telecommunications Research Institute
Priority date: 2005-12-01
Filing date: 2006-07-25
Publication date: 2007-06-07
Also published as: WO2007064071A3; KR100649675B1

Abstract

According to the present invention, the subscriber manageable profile service providing system (300) includes a profile database (310), a registration manager (320), a first profile manager (340), and a second profile manager (350). The profile database stores (310) a user's profile. The registration manager (320) performs service registration and updates registration information for the user (100). The first profile manager (340) receives profile request information from a service provider server (200) that has been requested to provide services from the user (100), analyzes the profile request information, and provides the corresponding profile to the service provider server (200). The second profile manager (350) writes the registration information transmitted from the registration manager (320) and the updated registration information as profiles, and stores the profiles in the profile database (310). In addition, the second profile manager (350) extracts the corresponding profile from the profile database (310) based on a result of the analysis of the first profile manager (340), and transmits the extracted profile to the first profile manager (340).

Description

SYSTEM FOR PROVIDING SUBSCRIBER MANAGEABLE PROFILE SERVICE, METHOD OF REGISTRATION, AND

OFFER THEREOF

Technical Field

[1] The present invention relates to a subscriber manageable profile service providing system and a method thereof, and more particularly, it relates to a system for integrally and independently managing user profiles from each service provider server in a different service provider server network, and a method thereof. Background Art

[2] Conventionally, profiles are managed by each service provider server.

[3] Therefore, a user has to register for each service provider server in order to use services of the service provider server. In addition, the user has to select services that are unilaterally provided by a service provider server.

[4] In addition, since the service provider server can provide services only to a registered user, many and unspecified persons are not able to use the services.

[5] Therefore, the conventional profile management technique is incapable of satisfying various users' needs and of managing various services and massive data in the next- generation communication network.

[6] As a prior art related to the profile management technology, Korean Patent No.

2000-24416 (entitled "Method and apparatus for providing the profile service in IMT- 2000 mobile communication system," filed on May 8, 2000) has been disclosed. This prior art relates to a method for verifying identity of a subscriber anytime and anywhere by using a profile service system server that resides on an IMT-2000 network, and an apparatus using the same.

[7] According to the previously described Korean Patent No. 20000-24416, a profile request of an IMT-2000 subscriber is stored in a database after the IMT-2000 subscriber registers with a profile service provider server. When there is a profile request from the IMT-2000DeletedTextssubscriber, the corresponding profile information is extracted from the database and then provided to the IMT-subscriber.

[8] In addition, there have been disclosed various prior arts which are related to the profile management techniques, such as a profile writing-related technology, a profile classification-related technique, a profile collection-related technology, a profile transmission-related technology, and a technology related to an efficient use of profiles, etc.

[9] However, a profile is still managed by each service provider server according to the prior arts.

[10] The above information disclosed in this Background section is only for enhancement of understanding of the background of the invention and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art.

Disclosure of Invention Technical Problem

[11] The present invention has been made in an effort to provide a profile managing system for storing subscriber profiles received through a registration process from a subscriber, and integrally and independently managing profiles from each service provider server rather than managing profiles for each service provider server.

[12] In addition, the present invention provides a system for converting a requested profile into an appropriate form for the corresponding service provider when the service provider server requests the profile, and a method thereof.

[13] Further, the present invention provides a system for writing and storing a service preference profile based on a service preference of a user or service usage information provided from a service provider server service and utilizing the service preference profile as a profile of the user. Technical Solution

[14] An exemplary subscriber manageable profile service providing system according to an embodiment of the present invention includes a profile database, a registration manager, a first profile manager, and a second profile manager. The profile database stores a user's profile. The registration manager performs service registration and updates registration information for the user. The first profile manager receives profile request information from a service provider server that has been requested to provide services by the user, analyzes the profile request information, and provides the corresponding profile to the service provider server. The second profile manager writes the registration information transmitted from the registration manager and the updated registration information as profiles, and stores the profiles in the profile database. In addition, the second profile manager extracts the corresponding profile from the profile database based on a result of the analysis of the first profile manager, and transmits the extracted profile to the first profile manager.

[15] A subscriber manageable profile service registration method according to an another embodiment of the present invention includes (a) receiving service request information from a user; (b) determining whether the service request information is a new registration request or a registration information update request; (c) when the new registration is requested, requesting and receiving registration information from the user; (d) when the registration information update is requested, requesting and receiving information to be updated from the user; and (e) writing the registration information received in (c) and the updated information received in (d) as profiles and storing the profiles.

[16] Another exemplary subscriber manageable profile service providing method according to another embodiment of the present invention includes (a) receiving service request information from a service provider server that provides service requested from a user; (b) analyzing the received service request information and extracting the corresponding profile; (c) converting the extracted profile into an appropriate form for the service provider server; and (d) providing the converted profile to the service provider server.

[17] Herein, between (a) and (b), the method may further include (i) determining whether the service request information is a profile request or a service preference information offer; (ii) when the service preference information is offered, writing the service preference information as a profile and storing it; and (iii) when the profile is requested, determining whether to offer a profile service and the form of the requested profile.

[18] In addition, between (a) and (b) or after (iii), the method may further includes (i) analyzing a user's service preference based on the service request information and writing the analysis result as a profile, and (ii) storing the service preference profile. Advantageous Effects

[19] According to the present invention, profiles can be managed integrally and independently from a service provider server so that massive profile data in the next generation communication can be efficiently managed. In addition, profiles are provided to the service provider server within a range that the corresponding user has allowed in order to secure user profiles.

[20] In addition, the user is served with optimal services without regarding whether the user registers with a specific service provider server to thereby provide services that satisfy user's various needs and characteristics. Further, user's satisfaction can also be increased by providing services that meet the user's preference, and therefore purchasing desire will be increased to thereby bring profits to the service provider. Brief Description of the Drawings

[21] FIG. 1 is a schematic view of a subscriber manageable profile service according to an exemplary embodiment of the present invention.

[22] FIG. 2 is a schematic diagram of a subscriber manageable profile service providing system according to an exemplary embodiment of the present invention.

[23] FIG. 3 is a detailed diagram of a first profile manager according to the exemplary embodiment of the present invention.

[24] FlG. 4 is a detailed diagram of a registration manager according to the exemplary embodiment of the present invention.

[25] FlG. 5 is a detailed diagram of a second profile manager according to the exemplary embodiment of the present invention.

[26] FlG. 6 is a flowchart showing a registration process for a subscriber manageable profile service according to the exemplary embodiment of the present invention.

[27] FlG. 7 is a flowchart showing a process for providing the subscriber manageable service according to the exemplary embodiment of the present invention.

[28] FlG. 8 is a flowchart showing a process for providing the subscriber manageable service according to another exemplary embodiment of the present invention.

[29] FlG. 9 is a flowchart showing a process for collecting service preference information according to an exemplary embodiment of the present invention. Best Mode for Carrying Out the Invention

[30] An exemplary embodiment of the present invention will hereinafter be described in detail with reference to the accompanying drawings.

[31] In the following detailed description, only certain exemplary embodiments of the present invention have been shown and described, simply by way of illustration. 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. The drawings and description are to be regarded as illustrative in nature and not restrictive, and like reference numerals designate like elements throughout the specification.

[32] Throughout this specification and the claims which follow, unless explicitly described to the contrary, the word "comprise" or variations such as "comprises" or "comprising" will be understood to imply the inclusion of stated elements but not the exclusion of any other elements. In addition, throughout this specification and the claims which follow, a module means a unit that performs a specific function or operation, and can be realized by hardware or software, or a combination of both.

[33] A subscriber manageable profile service providing system, and a service registration process and a service providing method for realization thereof will now be described in more detail with reference to the accompanying drawings.

[34] FlG. 1 is a schematic view of a subscriber manageable profile service according to an exemplary embodiment of the present invention.

[35] As shown in FlG. 1, the subscriber manageable profile service conceptually includes a user 100, a service provider 200, and a profile service providing system 300.

[36] The user 100 registers with the profile service providing system 300 and uses services provided by all service providers 200, which are interconnected with the profile service providing system 300.

[37] When providing services upon a request of the user 100, or providing push services, the service provider 200 requests the profile service providing system 300 to provide a subscriber profile. The service provider 200 may also request the profile service providing system 300 to provide subscriber profiles for other occasions.

[38] The profile service providing system 300 manages a profile of the registered user

100, and stores various profiles in a profile database 310. Upon a profile request from the service provider 200, the profile service providing system 300 provides the service provider 200 with a profile in an appropriate form for the corresponding provider. The profile service providing system 300 can access a profile only within a range that is allowed by the user 100.

[39] As described, instead of using an existing database for integrating profiles which have been individually managed by each service provider 200, the profile service providing system 300 individually establishes a profile database 310 for each profile provided from the user 100 according to the subscriber manageable profile service. In addition, the service provider 200 utilizes a profile stored in the profile database 310 for a service providing process (e.g., user authorization process) upon a request from the user 100.

[40] Therefore, after registering with the profile service providing system 300 through a registration process, the user 100 can use various next-generation communication services such as Internet services, mobile communication services, financial management services, and health-related services through a simple process.

[41] That is, according to the concept of the subscriber manageable profile service in the present exemplary embodiment of the present invention, inefficiency of the conventional system has been improved for integral management of subscriber profiles required for a subscriber authorization process which is a prerequisite process for access of various services. The subscriber manageable profile service also provides profiles in an appropriate form for each service provider to thereby offer various services to the user and provide a new profile management technology for integrating and managing a massive amount of profile data.

[42] A configuration of a profile service providing system to which the concept of the subscriber manageable profile service is applied will now be described in more detail.

[43] FlG. 2 is a configuration diagram of a subscriber manageable profile service providing system according to an exemplary embodiment of the present invention, and particularly, a configuration of the profile service providing system 300 of FlG. 1 is illustrated in detail therein.

[44] As shown in FlG. 2, the profile service providing system 300 includes a profile database 310, a registration manager 320, an interface unit 330, a first profile manager 340, and a second profile manager 350.

[45] The profile database 310 is used for providing services of each service provider

200, and stores a profile provided from a user 100 that is registered with the profile service providing system 300. At this time, the profile database 310 stores profiles written in various forms such as a terminal profile, a preference profile, a service profile, and a network profile.

[46] The registration manager 320 performs various registration-related processes such as a profile service registration process and a registration information update process for the user 100.

[47] The interface unit 330 communicates with a server at the service provider 200.

[48] The first profile manager 340 manages the entire operation of the profile service providing system 300. That is, the first profile manager 340 receives service request information through the interface unit 330. The first profile manager 340 analyzes the profile request information and determines whether the service provider server 200 offers services, the form of the requested profile, and whether service preference information is provided. Then the first profile manager 340 transmits the corresponding profile to the service provider server 200 through the interface unit 330.

[49] The second profile manager 350 stores registration information, update information, and service preference information as profiles, and converts the stored profiles into an appropriate form for the service provider server 200 that has requested the profile. That is, the second profile manager 350 writes the registration information or the update information transmitted from the registration manager 320 or the service preference information transmitted from the first profile manager 340 as profiles, and stores the written profiles in the profile database 310. In addition, the second profile manager 350 extracts the corresponding profile from the profile database 310 according to the analysis result of the first profile manager 340, and converts the extracted profile into an appropriate form for the service provider server 200 that has requested the profile and then transmits the converted profile to the first profile manager 340.

[50] FlG. 3 shows a detailed configuration of the first profile manager 340 according to an exemplary embodiment of the present invention, and it shows a correlation between the first profile manager 340, the interface unit 330, and the second profile manager 350.

[51] As shown in FlG. 3, the first profile manager 340 includes a profile request analysis module 342 and a profile providing module 344.

[52] The profile request analysis module 342 analyzes service request information received through the interface unit 330. That is, the profile request analysis module 342 determines whether the service request information requests a profile or offers a service preference. In addition, the profile request analysis module 342 determines whether the service provider server 200 that has transmitted the service request information offers services, and determines the type or form of a requested profile when the service request information is a profile request.

[53] Then, the profile request analysis module 342 re-writes the analysis result in a form that can be converted by the second profile manager 350 and transmits the re-written result to the second profile manager 350. When the service request information is a profile request, the profile request analysis module 342 acknowledges a service preference by analyzing the service request information and transmits the service preference to the second profile manager 350.

[54] The profile providing module 344 receives a profile from the second profile manager 350 and outputs the received profile to the interface unit 330.

[55] FlG. 4 is a detailed configuration diagram of the registration manager 320 according to an exemplary embodiment of the present invention, and it shows a correlation between the registration manager 320 and the second profile manager 350.

[56] As shown in FlG. 4, the registration manager 320 performs a registration process for the user 100 who wants to register with the profile providing service, and updates registration information of the user 100. At this time, the registration manager 320 can receive a registration request from the user 100 through various networks such as a mobile communication network and the Internet, etc. Such a registration manager 320 includes a registration classification module 322 and a registration form providing module 324.

[57] The registration classification module 322 classifies the registration request of the user 100 into a new registration request and a registration information update request. The new registration request is classified into profile management classes, for example, A class, B class, and C class. The A class manages all service-related profiles. The B class manages all the service-related profiles, excluding finance-related service profiles. The C class manages profiles only related to mobile communication- related service profiles. Meanwhile, when the registration information update is requested, the registration classification module 322 authorizes the user 100 to modify or delete registration information.

[58] The registration form providing module 324 provides the user 100 with a registration form appropriate for the registration classified by the registration classification module 322. The registration information of the user 100 is written in accordance with the registration form and output to the second profile manager 350. Then the registration information is written as a profile and stored in the profile database 310. At this time, the profile may be converted into a form that is appropriate for each service provider server and then stored. Therefore, the user 100 who has requested the registration form needs to fill in the form once with registration information of the user 100.

[59] FlG. 5 is a detailed configuration diagram of the second profile manager 350 according to the exemplary embodiment of the present invention, and it shows a correlation between the registration manager 320 and the second profile manager 350.

[60] As shown in FlG. 5, the second profile manager 350 includes a profile writing module 352, a profile storing module 354, and a profile converting module 356.

[61] The profile writing module 352 writes the registration information or updated registration information provided from the registration manager 340 as a profile. It also writes a user's service preference information that has been provided from the first profile manager 340 as a profile. Further, the profile writing module 352 writes service preference information that the first profile manager 340 has acknowledged on the basis of service request information as a profile.

[62] The profile storing module 354 stores a profile written by the profile writing module 352 in the profile database 310.

[63] The profile converting module 356 extracts the corresponding profile from the profile database 310 based on an analysis result of the profile request information transmitted from the first profile manager 340, and converts the profile into an appropriate form for the service provider 200 that has requested the profile. Herein, the conversion means converting the profile to a form that can be read out by the service providing server 200 that has requested the profile, and the converted profile is called an adapted profile. At this time, the profile converting module 356 outputs the adapted profile to the first profile manager 340. Then, the first profile manager 340 provides the adapted profile to the service provider 200 that has requested the profile through the interface unit 330.

[64] With the above-described configuration, a method for realizing a subscriber profile service will now be described in accordance with a registration process, a profile service providing process, and a service preference collection process.

[65] FlG. 6 is a flowchart of a subscriber manageable profile service registration process according to an exemplary embodiment of the present invention.

[66] As shown in FlG. 6, the registration manager 320 in the registration-waiting state receives service request information from the user 100 in step SlOl.

[67] Then the service request information is analyzed to determine whether the request represents a new registration request or a registration information update request in step S 103.

[68] When the service request information is determined to be the new registration request as a result of the determination of S 103 in step S 105, the new registration request is classified into a user-desired registration class in step S 107. At this time, the registration request is classified in accordance with the profile management classes that have been previously mentioned when describing the registration classification module 322 of FlG. 4. That is, the registration request may be classified into a class for managing all the service-related profiles, a class for managing all the service-related profiles with exclusion of financial service-related profiles, and a class for managing mobile communication service-related profiles.

[69] Then the user 100 is provided with the corresponding registration form according to the registration class into which the registration request was classified in the step S 107, in step S 109. At this time, a category for setting an information disclosure level is included in the registration form provided to the user 100 so that the user 100 can set a disclosure level of registration information so as to protect privacy and security.

[70] Then the registration information written properly in accordance with the registration form that was provided in step S 109 is transmitted from the user 100 in step Sill.

[71] When the request is determined to be a registration information update request as a result of the determination of S 103 in step S 113 , a registration form containing registration information that has been provided by an existing user 100 is provided in step Sl 15. At this time, the existing user 100 is authorized to modify or delete the registration information in the registration form.

[72] Subsequently, updated registration information is transmitted from the user 100 in step S 117.

[73] The registration information received in the step Sill or the updated registration information received in the step Sl 17 is written as a profile in step Sl 19.

[74] The written profile is stored in the profile database 310 in step S 121.

[75] FlG. 7 is a flowchart of a subscriber manageable profile service providing process according to an exemplary embodiment of the present invention.

[76] As shown in FlG. 7, the profile service providing system 300 in the profile- request-waiting-state receives service request information from the service provider server 200 in step S201. At this time, the profile request may be formed of a service identifier (ID), a subscriber ID, and a profile request provider ID.

[77] Then, the service request information is analyzed to determine whether the service provider server 200 offers services and to determine the form of the requested profile in step S203.

[78] Based on the analysis result of the step S203, the corresponding profile is extracted from the profile database 310 in step S205.

[79] The profile that is extracted in the step S205 is converted into an appropriate form for the service provider server 200 that has requested the profile in step S207.

[80] The profile that is converted in the step S209 is provided to the service provider server 200 in step S209.

[81] FlG. 8 is a flowchart of a process for providing a subscriber manageable profile service according to another exemplary embodiment of the present invention, and it is checked whether the service provider server 200 provides service preference information of the user in the flowchart.

[82] As shown in FlG. 8, the profile service providing system 300 receives service request information in step S301.

[83] The received service request information is analyzed to determine whether it provides service preference information or requests a profile in step S303.

[84] When the request is determined to be the profile request as a result of the determination of the step S303 in step S305, whether to offer a profile service and the form of the requested profile are determined in step S307.

[85] Then, the corresponding profile is searched and extracted from the profile database

310 based on the result of the determination of the step S307. The extracted profile is converted into an appropriate form for the service provider server 200 that has requested the profile. Then the converted profile is provided to the service provider server 200 in step S309.

[86] When the result of the determination of the step S303 shows that the service preference information is provided in step S311, the service preference information is written as a profile in step S313.

[87] Then, the written service preference profile is stored in the profile database in step

S315.

[88] FlG. 9 is a flowchart of a service preference information collection process according to an exemplary embodiment of the present invention. According to the exemplary embodiment of the present invention, the user 100 does not directly provide a service preference, and therefore the service preference can be collected through the service provider server 200 or other methods. Such a service collection process is illustrated in FlG. 9.

[89] As shown in FlG. 9, the service request information transmitted from the service provider server 200 in the step S401 is analyzed in step S403. At this time, the service request information is analyzed to determine whether the service preference information is provided or a profile is requested.

[90] When it is determined to be the service preference information as a result of the determination of the step S403 in step S405, the service preference information is written as a profile in step S411.

[91] When the result of the determination of the step S403 shows that the profile is requested in step S407, a service preference is analyzed on the basis of the service request information in step S409. When analyzing the service preference, service types of the service provider that has requested the subscriber profile and the number of profile requests may be used. The service preference may be accumulated, and it can be further accumulated as accumulation of the service preference increases.

[92] Then the service preference analyzed in step S409 is written as a profile in step

S411.

[93] The service preference profile written in step S411 is stored in the profile database

310 in step S413.

[94] The above-described exemplary embodiment of the present invention may be realized by an apparatus and a method, but it may also be realized by a program that realizes functions corresponding to configurations of the exemplary embodiment or a recording medium that records the program. Such a realization can be easily performed by a person skilled in the art.

[95] While this invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

[1] A subscriber manageable profile service providing system comprising: a profile database for storing a user's profile; a registration manager for performing service registration and registration information update for the user; a first profile manager for receiving profile request information from a service provider server that has been requested to provide services from the user, analyzing the profile request information, and providing the corresponding profile to the service provider server; and a second profile manager for writing registration information transmitted from the registration manager and updated registration information as profiles and storing the profiles in the profile database, extracting the corresponding profile from the profile database based on a result of the analysis of the first profile manager, and transmitting the extracted profile to the first profile manager.

[2] The subscriber manageable profile service providing system of claim 1, wherein the first profile manager comprises: a profile request analysis module for determining whether the service provider server provides services, the form of the requested profile, and whether service preference information is provided, analyzing a service preference based on the service request information when service request information is determined to be a profile request, and transmitting the determination and analysis results to the second profile manager; and a profile providing module for providing the profile transmitted from the second profile manager to the service provider server.

[3] The subscriber manageable profile service providing system of claim 2, wherein the profile request analysis module analyzes a service identifier (ID), a subscriber ID, and a requested-service provider ID included in the profile request information.

[4] The subscriber manageable profile service providing system of claim 1, wherein the registration manager comprises: a registration classification module for determining whether a service request from the user is a new registration request or a registration information update request, and classifying profile management classes in accordance with the type of profile when the new registration is requested; and a registration form providing module for providing the user with an appropriate registration form according to the registration classification of the registration classification module.

[5] The subscriber manageable profile service providing system of claim 4, wherein the registration classification module classifies profile management classes into an entire service-related profile, the entire service-related profile with exclusion of finance services, and a mobile service-related profile according to the type of profile.

[6] The subscriber manageable profile service providing system of claim 4, wherein the registration form provided by the registration form providing module comprises a category for setting a disclosure level of registration information.

[7] The subscriber manageable profile service providing system of claim 2, wherein the second profile manager comprises: a profile writing module for writing registration information and registration update information transmitted from the registration manager and service preference information transmitted from the first profile manager as profiles; a profile storing module for storing the profiles written by the profile writing module in the profile database; and a profile converting module for extracting the corresponding profile from the profile database based on the analysis result of the first profile manager, converting the extracted profile into an appropriate form for the service provider server, and transmitting the converted profile to the first profile manager.

[8] A subscriber manageable profile service registration method comprising:

(a) receiving service request information from a user;

(b) determining whether the service request information is a new registration request or a registration information update request;

(c) when the new registration is requested, requesting and receiving registration information from the user;

(d) when the registration information update is requested, requesting and receiving information to be updated from the user; and

(e) writing the registration information received in (c) and the update information received in (d) as profiles and storing the profiles.

[9] The method of claim 8, wherein (c) comprises:

(i) classifying registration into profile management classes classified in accordance with the type of profile;

(ii) providing the user with an appropriate registration form for the registration classification; and

(iii) receiving the registration information written in accordance with the registration form from the user. [10] The method of claim 9, wherein the profile management classes classified in (i) are classified into an entire subscriber profile management class, an entire subscriber profile management class with exclusion of finance-related profile, and a mobile communication subscriber profile management class. [11] The method of claim 9, wherein, in (ii), the registration form comprises a category for setting a disclosure level of a subscriber's profile. [12] The method of claim 8, wherein (d) comprises: providing the user with a registration form containing registration information of the user; and receiving a registration form containing update information modified or deleted by the user from the user. [13] A subscriber manageable profile service providing method comprising:

(a) receiving service request information from a service provider server that provides services requested from a user;

(b) analyzing the received service request information and extracting the corresponding profile;

(c) converting the extracted profile into an appropriate form for the service provider server; and

(d) providing the converted profile to the service provider server. [14] The method of claim 13, between (a) and (b), further comprising:

(i) determining whether the service request information is a profile request or a service preference information offer;

(ii) when the service preference information is offered, writing the service preference information as a profile and storing it; and

(iii) when the profile is requested, determining whether to offer a profile service and the form of the requested profile. [15] The method of claim 13 or claim 14, between (a) and (b), or after (iii), further comprising:

(i) analyzing a user's service preference based on the service request information and writing the analysis result as a profile; and

(ii) storing the service preference profile. [16] The method of claim 15, wherein, in (i), a service type of a service provider server that has requested a user's profile and the number of profile requests are used when analyzing the service preference. [17] The method of claim 13, wherein, in (a), the service request information includes a service identifier (ID), a subscriber ID, and a requested- service provider server

ID.