{"search_session":{},"preferences":{"l":"en","queryLanguage":"en"},"patentId":"190-781-885-632-739","frontPageModel":{"patentViewModel":{"ref":{"entityRefId":"190-781-885-632-739","entityRefType":"PATENT"},"entityMetadata":{"linkedIds":{"empty":true},"tags":[],"collections":[{"id":188941,"type":"PATENT","title":"Patentes 20 años","description":"Todas las patentes en los ultimos 20años","access":"OPEN_ACCESS","displayAvatar":true,"attested":false,"itemCount":50000,"tags":[],"user":{"id":356015324,"username":"luis.vargas","firstName":"Luis Miguel","lastName":"Vargas Largo","created":"2020-06-06T12:35:15.000Z","displayName":"Luis Miguel Vargas Largo","accountType":"PERSONAL","isOauthOnly":true},"notes":[],"sharedType":"PUBLISHED","hasLinkedSavedQueries":true,"savedQueries":[],"created":"2021-03-07T15:12:38Z","updated":"2021-03-07T15:12:49Z","lastEventDate":"2021-03-07T15:12:49Z"}],"notes":[],"inventorships":[],"privateCollections":[],"publicCollections":[{"id":188941,"type":"PATENT","title":"Patentes 20 años","description":"Todas las patentes en los ultimos 20años","access":"OPEN_ACCESS","displayAvatar":true,"attested":false,"itemCount":50000,"tags":[],"user":{"id":356015324,"username":"luis.vargas","firstName":"Luis Miguel","lastName":"Vargas Largo","created":"2020-06-06T12:35:15.000Z","displayName":"Luis Miguel Vargas Largo","accountType":"PERSONAL","isOauthOnly":true},"notes":[],"sharedType":"PUBLISHED","hasLinkedSavedQueries":true,"savedQueries":[],"created":"2021-03-07T15:12:38Z","updated":"2021-03-07T15:12:49Z","lastEventDate":"2021-03-07T15:12:49Z"}],"privateNotes":[],"landscapeCollections":[],"landscapeNotes":[]},"document":{"record_lens_id":"190-781-885-632-739","lens_id":["190-781-885-632-739","158-918-721-014-63X"],"doc_key":"EP_1956511_A2_20080813","created":"2016-01-13T10:18:19.317","docdb_id":51142,"lens_internal":{"earliest_lens_id_created_time":"2016-01-13T10:18:19.317","last_modified":"2024-03-26T05:00:36.077","legacy_pub_key":"EP_1956511_A2","has_doc_lang":true,"has_biblio_lang":true,"has_all_title_lang":true,"has_all_abstract_lang":true,"has_all_claims_lang":true,"has_description_lang":true},"jurisdiction":"EP","doc_number":"1956511","kind":"A2","date_published":"2008-08-13","year_published":2008,"ids":["EP_1956511_A2","190-781-885-632-739","158-918-721-014-63X","EP_1956511_A2_20080813","EP","1956511","A2","EP1956511A2","EP1956511","1956511A2"],"lang":"en","publication_type":"PATENT_APPLICATION","application_reference":{"jurisdiction":"EP","doc_number":"08151204","kind":"A","date":"2008-02-08"},"priority_claim":[{"jurisdiction":"JP","doc_number":"2007030564","kind":"A","date":"2007-02-09"}],"priority_claim.source":"DOCDB","earliest_priority_claim_date":"2007-02-09","title":{"de":[{"text":"Verfahren und System zur Authentifizierung einer Funktionslizenz","lang":"de","source":"DOCDB","data_format":"DOCDBA"}],"en":[{"text":"Method and system for function license authentication","lang":"en","source":"DOCDB","data_format":"DOCDBA"}],"fr":[{"text":"Procédé et système d'authentification de licence d'utilisation","lang":"fr","source":"DOCDB","data_format":"DOCDBA"}]},"title_lang":["de","en","fr"],"has_title":true,"applicant":[{"name":"NEC INFRONTIA CORP","residence":"JP","sequence":1,"app_type":"applicant"}],"applicant_count":1,"has_applicant":true,"inventor":[{"name":"NAKAGAWA HIROAKI","residence":"JP","sequence":1},{"name":"NISHIDE NOBUO","residence":"JP","sequence":2}],"inventor_count":2,"has_inventor":true,"agent":[{"name":"Vossius & Partner","address":"Siebertstrasse 4, 81675 München","country":"DE"}],"agent_count":1,"has_agent":true,"owner":[],"owner_count":0,"owner_all":[],"owner_all_count":0,"has_owner":false,"has_examiner":false,"class_ipcr":[{"symbol":"G06F21/10","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":1},{"symbol":"G06F21/12","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":2},{"symbol":"G06F21/14","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":3},{"symbol":"G06F21/33","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":4},{"symbol":"G06F21/44","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":5},{"symbol":"G06Q10/00","version_indicator":"2012-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":6},{"symbol":"G06Q50/00","version_indicator":"2012-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":7},{"symbol":"G06Q50/10","version_indicator":"2012-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-03-06","class_status":"R","class_data_source":"H","generating_office":"JP","sequence":8}],"class_ipcr.later_symbol":["G06F21/10","G06F21/12","G06F21/14","G06F21/33","G06F21/44","G06Q10/00","G06Q50/00","G06Q50/10"],"class_ipcr.inv_symbol":["G06F21/10","G06F21/12","G06F21/14","G06F21/33","G06F21/44","G06Q10/00","G06Q50/00","G06Q50/10"],"class_ipcr.add_symbol":[],"class_ipcr.source":"DOCDB","class_cpc":[{"symbol":"G06F21/6218","version_indicator":"2013-01-01","class_symbol_position":"F","class_value":"I","action_date":"2013-01-01","class_status":"B","class_data_source":"H","generating_office":"EP","sequence":1},{"symbol":"G06F21/629","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2013-01-01","class_status":"B","class_data_source":"H","generating_office":"EP","sequence":2},{"symbol":"G06F21/6218","version_indicator":"2013-01-01","class_symbol_position":"F","class_value":"I","action_date":"2019-08-22","class_status":"B","class_data_source":"H","generating_office":"US","sequence":3},{"symbol":"G06F21/629","version_indicator":"2013-01-01","class_symbol_position":"L","class_value":"I","action_date":"2019-10-11","class_status":"B","class_data_source":"H","generating_office":"US","sequence":4}],"class_cpc_cset":[],"class_cpc.first_symbol":"G06F21/6218","class_cpc.later_symbol":["G06F21/629","G06F21/629"],"class_cpc.inv_symbol":["G06F21/6218","G06F21/629","G06F21/6218","G06F21/629"],"class_cpc.add_symbol":[],"class_cpc.source":"DOCDB","class_national":[],"class_national.later_symbol":[],"reference_cited":[{"patent":{"num":1,"document_id":{"jurisdiction":"JP","doc_number":"2007030564","kind":"A","date":"2007-02-08","name":"AISIN AW CO"},"lens_id":"116-280-901-356-457","category":[],"us_category":[],"cited_phase":"APP","cited_date":"2008-06-17","rel_claims":[],"sequence":1}},{"patent":{"num":2,"document_id":{"jurisdiction":"JP","doc_number":"2004252931","kind":"A","date":"2004-09-09","name":"SONY CORP"},"lens_id":"104-461-629-425-771","category":[],"us_category":[],"cited_phase":"APP","cited_date":"2008-06-17","rel_claims":[],"sequence":2}},{"patent":{"num":3,"document_id":{"jurisdiction":"JP","doc_number":"2006031320","kind":"A","date":"2006-02-02","name":"MATSUSHITA ELECTRIC IND CO LTD"},"lens_id":"013-207-894-034-744","category":[],"us_category":[],"cited_phase":"APP","cited_date":"2008-06-17","rel_claims":[],"sequence":3}},{"patent":{"num":4,"document_id":{"jurisdiction":"JP","doc_number":"2006059164","kind":"A","date":"2006-03-02","name":"FUJITSU SUPPORT & SERVICE KK"},"lens_id":"009-413-623-345-922","category":[],"us_category":[],"cited_phase":"APP","cited_date":"2008-06-17","rel_claims":[],"sequence":4}},{"patent":{"num":5,"document_id":{"jurisdiction":"JP","doc_number":"2006195826","kind":"A","date":"2006-07-27","name":"TOSHIBA TEC KK"},"lens_id":"186-177-801-465-203","category":[],"us_category":[],"cited_phase":"APP","cited_date":"2008-06-17","rel_claims":[],"sequence":5}}],"reference_cited.source":"DOCDB","reference_cited.patent_count":5,"cites_patent":true,"reference_cited.npl_count":0,"reference_cited.npl_resolved_count":0,"cites_npl":false,"cites_resolved_npl":false,"cited_by":{"patent_count":2,"patent":[{"lens_id":"188-926-200-902-04X","document_id":{"jurisdiction":"US","doc_number":"10685095","kind":"B2"}},{"lens_id":"091-174-916-865-161","document_id":{"jurisdiction":"EP","doc_number":"3273376","kind":"A4"}}]},"cited_by_patent":true,"family":{"simple":{"size":6,"id":183842741,"member":[{"lens_id":"055-989-274-227-046","document_id":{"jurisdiction":"JP","doc_number":"2008197795","kind":"A","date":"2008-08-28"}},{"lens_id":"190-781-885-632-739","document_id":{"jurisdiction":"EP","doc_number":"1956511","kind":"A2","date":"2008-08-13"}},{"lens_id":"035-729-044-929-556","document_id":{"jurisdiction":"CA","doc_number":"2619178","kind":"A1","date":"2008-08-09"}},{"lens_id":"126-929-742-298-785","document_id":{"jurisdiction":"EP","doc_number":"1956511","kind":"A3","date":"2009-04-01"}},{"lens_id":"092-106-576-269-997","document_id":{"jurisdiction":"AU","doc_number":"2008200597","kind":"A1","date":"2008-08-28"}},{"lens_id":"132-353-213-184-086","document_id":{"jurisdiction":"US","doc_number":"20080215886","kind":"A1","date":"2008-09-04"}}]},"extended":{"size":6,"id":183841221,"member":[{"lens_id":"035-729-044-929-556","document_id":{"jurisdiction":"CA","doc_number":"2619178","kind":"A1","date":"2008-08-09"}},{"lens_id":"190-781-885-632-739","document_id":{"jurisdiction":"EP","doc_number":"1956511","kind":"A2","date":"2008-08-13"}},{"lens_id":"055-989-274-227-046","document_id":{"jurisdiction":"JP","doc_number":"2008197795","kind":"A","date":"2008-08-28"}},{"lens_id":"126-929-742-298-785","document_id":{"jurisdiction":"EP","doc_number":"1956511","kind":"A3","date":"2009-04-01"}},{"lens_id":"092-106-576-269-997","document_id":{"jurisdiction":"AU","doc_number":"2008200597","kind":"A1","date":"2008-08-28"}},{"lens_id":"132-353-213-184-086","document_id":{"jurisdiction":"US","doc_number":"20080215886","kind":"A1","date":"2008-09-04"}}]}},"has_sequence":false,"legal_status":{"ipr_type":"patent for invention","granted":false,"earliest_filing_date":"2008-02-08","application_expiry_date":"2011-04-21","has_disclaimer":false,"patent_status":"DISCONTINUED","publication_count":2,"has_spc":false,"has_grant_event":false,"has_entry_into_national_phase":false},"abstract":{"en":[{"text":"There is provided a function license authentication method and system capable of preventing the illegal creation of a license key. A function license authentication method comprising: a step in which an authentication server generates a function code based on order in which functions used have been coded; a step in which a user transfers an equipment-specific code to the authentication server; a step in which the authentication server generates a first license key based on the function code and equipment-specific code; a step in which the user inputs the coded order to the equipment; a step in which the user acquires the first license key from the authentication server and inputs the acquired first license key to the equipment; a step in which the equipment generates a function code based on the coded order that has been input thereto and further generates a second license key based on the generated function code and equipment specific code; and a step in which the equipment compares the first and second license keys and determines that authentication is successfully completed when the first and second license keys coincide with each other.\n","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"}]},"abstract_lang":["en"],"has_abstract":true,"claim":{"en":[{"text":"A function license authentication method comprising:\n a step in which an authentication server generates a function code based on order in which functions used have been coded; \n a step in which a user transfers an equipment-specific code to the authentication server; \n a step in which the authentication server generates a first license key based on the function code and equipment-specific code; \n a step in which the user inputs the coded order to the equipment; \n a step in which the user acquires the first license key from the authentication server and inputs the acquired first license key to the equipment; \n a step in which the equipment generates a function code based on the coded order that has been input thereto and further generates a second license key based on the generated function code and equipment-specific code; and \n a step in which the equipment compares the first and second license keys and determines that authentication is successfully completed when the first and second license keys coincide with each other.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"},{"text":"The function license authentication method according to claim 1, wherein \nthe URL of the authentication server is written in an order sheet supplied from a sales company to the user.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"},{"text":"The function license authentication method according to claim 2, wherein \ncoded functions are also written in the order sheet.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"},{"text":"A function license authentication system comprising an authentication server and an equipment, wherein \nthe authentication server generates a function code based on order in which functions used have been coded, \na user transfers an equipment-specific code to the authentication server, \nthe authentication server generates a first license key based on the function code and equipment-specific code, \nthe user inputs the coded order to the equipment, \nthe user acquires the first license key from the authentication server and inputs the acquired first license key to the equipment, \nthe equipment generates a function code based on the coded order that has been input thereto and further generates a second license key based on the generated function code and equipment-specific code, and \nthe equipment compares the first and second license keys and determines that authentication is successfully completed when the first and second license keys coincide with each other.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"},{"text":"The function license authentication system according to claim 4, wherein \nthe URL of the authentication server is written in an order sheet supplied from a sales company to the user.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"},{"text":"The function license authentication system according to claim 5, wherein \ncoded functions are also written in the order sheet.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"}]},"claim_lang":["en"],"has_claim":true,"description":{"en":{"text":"This application is based upon and claims the benefit of priority from Japanese patent application No. 2007-030564, filed on February, 9th, 2007 , the disclosure of which is incorporated herein in its entirety by reference. The present invention relates to a function license authentication method and system for acquiring a license for utilizing a function of an equipment (telephone system, etc.). A conventional issuance procedure of a license key and an authentication procedure performed in an equipment will hereinafter be described. \n\"Function code\", which represents the content of a function of canceling usage restrictions, is used for informing an equipment of the content of a function to be canceled. The \"function code\" is used also in authentication. \n\"Equipment-specific code\", which is a number specific to individual equipments, is assigned to an equipment in a factory at its manufacturing time. The \"equipment-specific code\" needs to be difficult to rewrite after manufacturing in a factory. \n\"License key\" is created based on the \"equipment-specific code\" and \"function code\". An equipment uses the license key\" for confirming whether an input license key has been authenticated or not. \nA conventional authentication operation is performed according to a procedure shown in FIG. 1 .\n (1) A user places an order for a function of an equipment used, function for each client, and number of clients with a sales company (step S901). (2) The sales company registers the order in an authentication server (step S903). (3) The authentication server creates the \"function code\" based on the order (step S904). (4) The sale company acquires the \"function key\" from the authentication server (step S905). (5) The sales company prints the \"function code\", order, and address of the authentication server on a paper (see FIG. 2 ) and sells the functions to the user (step S907). (6) The user uses an equipment being used to read in the \"function-specific code\" (step S909). (7) The user accesses the authentication server and inputs the \"function-specific code\" to the authentication server. (8) The authentication server calculates the \"license key\" from the \"equipment-specific code\" and \"function code\" (step S912). (9) The user acquires the \"license key\" from the authentication server (S913). (10) The user inputs the \"function code\" and \"license key\" to the equipment (step S915). (11) The equipment calculates the \"license key\" from the input \"function code\" and \"equipment-specific code\" stored therein and compares the calculated \"license key\" with the input \"license key\". When both the license keys coincide with each other, the equipment determines that the \"function code\" has successfully been authenticated and activates the function corresponding to the \"function code\" (step S917). The \"function code\", \"equipment-specific code\", and \"license key\" are created/calculated as follows. The \"function code\", which represents the content of a function of canceling usage restrictions, is created as follows. The equipment uses eight functions of a1, a2, a3, a4, a5, a6, a7, and a8, which determine only ON/OFF. Up to 4095 clients can be connected simultaneously in the equipment, and the clients can use four functions of b1, b2, b3, and b4. 8 bits are necessary to represent the ON/OFF of the functions used by the equipment as a bit string. In the case where only the function a is ON, a bit string obtained is 00000001 which is \"01\" when represented as a hexadecimal number. In the case where only the function a1 is OFF and functions a2, a3, a4, a5, a6, a7, and a8 are ON, a bit string obtained is 1111110 which is \"FE\" when represented as a hexadecimal number. In the setting of the client function, the number of clients allowed to use each function is set. In the case where the number of clients allowed to use the function b1 is 0, \"000\" is obtained using the hexadecimal representation and, similarly, in the case where the number of clients allowed to use the function b1 is 4095, \"FFF\" is obtained. Similarly, 3 digits (from \"000\" to \"FFF\") are necessary to represent the function b2 as a hexadecimal number. When all the functions are represented as a hexadecimal number, 2 digits (from \"00\" to \"FF\") are necessary for respective functions a1, a2, a3, a4, a5, a6, a7, and a8, 3 digits (from \"000\" to \"FFF\") are necessary for the function b1 and, similarly, 3 digits (from \"000\" to \"FFF\") are necessary for the functions b2 and b4 respectively. In total, 14 digits (from \"00 000 000 000 000\" to \"FFFFFFFFFFFFFF\") are necessary. If another function b5 for the client is added, 17 digits are necessary. The \"equipment-specific code\" is supplied in the form of a serial number or MAC address. It is assumed here that hexadecimal numbers from 0000 to FFFF are assigned to the \"equipment-specific code\". There are available various creation methods of the \"license key\". Here, as an example, a product of the \"equipment-specific code and \"function code\" is calculated. Assuming that the equipment-specific code is \"ABCD\" and function code is \"030644D2000000\", obtained license key is \"79BFD622A000000\". Thus, different values need to be obtained for the license key in the case where different equipment-specific codes are input, although the function code is the same. The function code and license key are authenticated as follows. The license key is calculated both in the authentication server and equipment. The value of the license key calculated using the same function code and same equipment-specific code according to the same rule (\"multiplication\", in this case) becomes the same. The license key calculated in the authentication server is input to the equipment side. When a comparison result between the value of the license key calculated in the equipment and value of the input license key is the same, i.e., matched, authentication is achieved. In the case where the license key authenticated in one equipment is input to another equipment, a license key calculated in the equipment differs from the input license key since the equipment-specific codes are different, authentication fails. \n[Patent Document 1] JP-A-2004-252931 \n[Patent Document 2] JP-A-2006-031320 \n[Patent Document 3] JP-A-2006-059164 \n[Patent Document 4] JP-A-2006-195826 In a conventional system, the number of functions whose usage restrictions are to be canceled, the number of clients to be managed, and numbers specific to a target equipment are included in the license key issued to a user. Thus, irrespective of whether codes used in the system are encrypted or not, a calculation method of the license key can be estimated and therefore there is a danger that the license key is illegally created. Further, when the number of functions to be managed is large, the number of digits of the issued license key becomes enormous, making input operation of the license key complicated. An object of the present invention is therefore to provide a function license authentication method and system capable of preventing the illegal creation of a license key. In the present invention, the following modifications are made.\n <1> \"Function code\" that has conventionally been written in a function code sheet is not issued but, instead, an order sheet ( FIG. 3 ) only describing order items is issued. \nAlthough the authentication server receives as an input the order from the sales company and creates \"function code\", it does not output the created \"function code\". <2> The user does not input \"function code\" that the user has conventionally input to the equipment. <3> The user inputs the order to the equipment. The equipment does not require input of the \"function code\", but the user inputs the order to the equipment. The equipment activates a function according to the input order. A tentative \"function code\" is created based on the input of the order. \"License key\" is calculated from the tentative \"function code\" and \"equipment-specific code\". Although, in the conventional system, it is necessary to input the \"function code\" supplied from the sales company to the equipment, the input operation of the \"function code\" is unnecessary in the present invention. Since the \"function code\" becomes unnecessary, the \"function code\" cannot illegally be created. Further, since the \"function code\" is not disclosed to the user, it becomes hard to estimate how to calculate the \"license key\" which is calculated from the order and \"equipment-specific code\", making it difficult to illegally create the \"license key\", that is, making it difficult to illegally cancel the usage restrictions on the function. Although, in the method according to the present invention, input operation of the \"order\" is necessary, the operation involves inputting only numerals as specified on the order sheet, which places a less burden on the user as compared to the input operation of \"function code\" which is composed of characters meaninglessly arranged. The invention is further explained with reference to the drawings:\n FIG. 1 is a block diagram showing a configuration of a conventional function license authentication system; FIG. 2 is a view showing an example of a function code sheet issued to a user in a system shown in FIG. 1 ; FIG. 3 is a view showing an example of an order sheet issued to a user in a system shown in FIG. 4 ; FIG. 4 is a block diagram showing a configuration of a function license authentication system according to an embodiment of the present invention; and FIG. 5 is a block diagram showing a configuration of a function license authentication system according to another embodiment of the present invention. There exists an equipment in which usage restrictions are placed on functions of a software and hardware component and the usage restrictions are canceled by using license keys which are available from a sales company. Conventionally, the following conditions are required for creation of the license key. The first condition is that the number specific to the equipment is included in the license key for preventing illegal use of the license key. The second condition is that the content of a function whose usage restrictions are to be canceled is included in the license key. When a license key satisfying the first and second conditions is issued after being subjected to arithmetic processing such as encryption, an equipment to which the license key has been input needs to perform inverse arithmetic processing or needs to use a decryption key. However, when a configuration allowing inverse arithmetic processing is adopted to a system, security of the system is weakened. Further, handling of the decryption key is very complicated. Thus, the present invention provides an authentication method capable of simplifying input operation of the license key and preventing a decrease of security. A preferred embodiment of the present invention will be described below in detail with reference to the accompanying drawings. In a telephone equipment such as a PBX, various functions are provided for the equipment and for each telephone set. The use of these functions is usually restricted. A user places an order for a function of the equipment used and functions provided for each telephone set by the amount corresponding to required telephone sets. A sales company of the telephone equipment needs to allow the user to use the function of the telephone equipment and functions of each telephone set according to the user's order. It is assumed, for example, that the telephone equipment can support up to 4095 telephone sets. It is assumed that a1, a2, a3, a4, a5, a6, a7, and a8 are prepared as a function of the equipment. It is assumed that b1, b2, b3, and b4 are prepared as a function of each of the telephone set. The user and sales company perform the following operation to cancel usage restrictions on the functions. With reference to FIG. 4 , a function license authentication method according to the present invention will be described.\n (1) A user 207 places an order for the functions a1 and a2 and functions b1 by the amount corresponding to 100 telephone sets and function b2 by the amount corresponding to 1234 telephone sets with a sales company 203 (step S101). (2) The sales company 203 registers the order in an authentication server 205 (step S103). (3) An authentication server 205 creates the following \"function code\" based on the order and records it (step S104). The \"function code\" is \"030644D2000000\". (4) The sales company 203 issues an order sheet (see FIG. 3 ) describing the order and address of the authentication server 205 and sells it to the user 207 (step S105). (5) The user 207 uses an equipment (telephone system 201, etc.) being used to read in \"function-specinc code\" (\"ABCD\") (step S107). (6) The user 207 accesses the address written in the order sheet and inputs the \"equipment-specific code\" (\"ABCD\") to the authentication server 205 (step S109). The authentication server 205 calculates \"license key\" (\"79BFD622A000000\") from the \"equipment-specific code\" (\"ABCD\") and \"function code\" (\"030644D2000000\") (step S110). (7) The user 207 acquires the \"license key\" (\"79BFD622A000000\") from the authentication server 205 (step S111). (8) The user 207 inputs the order (a1=1, a2=1, b1=100, b2=1234) to the equipment (telephone system 201, etc.) through a menu window on the equipment (step S113). (9) The user 207 inputs the \"license key\" (\"79BFD622A000000\") to the equipment (telephone system 201, etc.) (step S115). The equipment (telephone system 201, etc.) creates \"function code\" (\"030644D2000000\") based on the order input in (8). Further, the equipment creates \"license key\" (\"79BFD622A000000\") from the \"equipment-specific code\" (\"ABCD\") stored therein and \"function code\" (\"030644D2000000\") created from the order. The equipment then compares the \"license key\" input in (9) and \"license key\" calculated therein. Since the both license keys coincide with each other, the order input in (8) is authenticated, and the equipment activates its function (step S116). The equipment on which usage restrictions of function can be imposed includes a telephone equipment, a server, and the like. The \"function code\" may be represented as a binary number, decimal number, hexadecimal number, ASCII code, or may be encrypted. The \"function code\" may be generated not only from the content of the function but also from a combination of the content of the function and issuance date or random numbers. The calculation method of the \"license key\" includes not only multiplication but also various methods including encryption. Although the \"license key\" describes all digits in the above embodiment, calculated check sum may be used or a part of all the digits may be used for authentication. There is no restriction imposed on the number of functions that can be managed in the present invention. There is available another method obtained by combining conventional method and the present invention. That is, a meaningless value such as random number is written, as the function key, in the function code sheet, and actual authentication is not performed using the value. The \"function code\" and \"order sheet\" may be supplied not only in the form of a paper document but also on E-mail, through a Web site on the Internet. Alternatively, the \"function code\" and \"order sheet\" may automatically be supplied when the equipment accesses the Internet. Although the exemplary embodiments of the present invention have been described in detail, it should be understood that various changes, substitutions and alternatives can be made therein without departing from the sprit and scope of the invention as defined by the appended claims. Further, it is the inventor's intent to retain all equivalents of the claimed invention even if the claims are amended during prosecution.","lang":"en","source":"EPO_FULLTEXT","data_format":"ORIGINAL"}},"description_lang":["en"],"has_description":true,"has_docdb":true,"has_inpadoc":true,"has_full_text":true,"biblio_lang":"en"},"jurisdiction":"EP","collections":[],"usersTags":[],"lensId":"190-781-885-632-739","publicationKey":"EP_1956511_A2","displayKey":"EP 1956511 A2","docAssets":{"lensId":"190-781-885-632-739","pdfUrl":"https://www.lens.org/images/patent/EP/1956511/A2/EP_1956511_A2.pdf","images":[{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000001.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000001.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000002.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000002.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000003.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000003.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000004.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000004.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000005.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000005.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000006.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000006.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000007.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000007.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000008.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000008.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000009.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000009.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000010.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000010.png"},{"thumb":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/10pc/00000011.png","full":"https://s3-us-west-2.amazonaws.com/lens-resource/patent/EP/A2/1956/1956511/image/page/full/00000011.png"}],"fallover":false},"countryName":"EUROPEAN PATENT OFFICE","inventorModel":{"inventors":[{"name":{"value":"NAKAGAWA HIROAKI","valueNormalised":"Nakagawa Hiroaki"},"inventorship":null},{"name":{"value":"NISHIDE NOBUO","valueNormalised":"Nishide Nobuo"},"inventorship":null}],"inventorships":[],"unmatchedInventorships":[],"activeUserHasInventorship":false},"simpleFamilyId":183842741,"citesPatentCount":5,"countrySpec":{"countryName":"EUROPEAN PATENT OFFICE","description":"APPLICATION PUBLISHED WITHOUT Search Report","rule":"","docType":"PATENT_APPLICATION"},"pageTitle":"EP 1956511 A2 - Method and system for function license authentication","documentTitle":"Method and system for function license authentication"},"claims":{"source":"xml_claims","claims":[{"lines":["A function license authentication method comprising:
a step in which an authentication server generates a function code based on order in which functions used have been coded;
a step in which a user transfers an equipment-specific code to the authentication server;
a step in which the authentication server generates a first license key based on the function code and equipment-specific code;
a step in which the user inputs the coded order to the equipment;
a step in which the user acquires the first license key from the authentication server and inputs the acquired first license key to the equipment;
a step in which the equipment generates a function code based on the coded order that has been input thereto and further generates a second license key based on the generated function code and equipment-specific code; and
a step in which the equipment compares the first and second license keys and determines that authentication is successfully completed when the first and second license keys coincide with each other."],"number":1,"annotation":false,"claim":true,"title":false},{"lines":["The function license authentication method according to claim 1, wherein the URL of the authentication server is written in an order sheet supplied from a sales company to the user."],"number":2,"annotation":false,"claim":true,"title":false},{"lines":["The function license authentication method according to claim 2, wherein coded functions are also written in the order sheet."],"number":3,"annotation":false,"claim":true,"title":false},{"lines":["A function license authentication system comprising an authentication server and an equipment, wherein the authentication server generates a function code based on order in which functions used have been coded, a user transfers an equipment-specific code to the authentication server, the authentication server generates a first license key based on the function code and equipment-specific code, the user inputs the coded order to the equipment, the user acquires the first license key from the authentication server and inputs the acquired first license key to the equipment, the equipment generates a function code based on the coded order that has been input thereto and further generates a second license key based on the generated function code and equipment-specific code, and the equipment compares the first and second license keys and determines that authentication is successfully completed when the first and second license keys coincide with each other."],"number":4,"annotation":false,"claim":true,"title":false},{"lines":["The function license authentication system according to claim 4, wherein the URL of the authentication server is written in an order sheet supplied from a sales company to the user."],"number":5,"annotation":false,"claim":true,"title":false},{"lines":["The function license authentication system according to claim 5, wherein coded functions are also written in the order sheet."],"number":6,"annotation":false,"claim":true,"title":false}]}},"filters":{"npl":[],"notNpl":[],"applicant":[],"notApplicant":[],"inventor":[],"notInventor":[],"owner":[],"notOwner":[],"tags":[],"dates":[],"types":[],"notTypes":[],"j":[],"notJ":[],"fj":[],"notFj":[],"classIpcr":[],"notClassIpcr":[],"classNat":[],"notClassNat":[],"classCpc":[],"notClassCpc":[],"so":[],"notSo":[],"sat":[]},"sequenceFilters":{"s":"SEQIDNO","d":"ASCENDING","p":0,"n":10,"sp":[],"si":[],"len":[],"t":[],"loc":[]}}