Nothing Special   »   [go: up one dir, main page]

WO2006024216A1 - Procede pour mettre en oeuvre la certification et systemes correspondants - Google Patents

Procede pour mettre en oeuvre la certification et systemes correspondants Download PDF

Info

Publication number
WO2006024216A1
WO2006024216A1 PCT/CN2005/001157 CN2005001157W WO2006024216A1 WO 2006024216 A1 WO2006024216 A1 WO 2006024216A1 CN 2005001157 W CN2005001157 W CN 2005001157W WO 2006024216 A1 WO2006024216 A1 WO 2006024216A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
authentication
identifier
application server
authentication center
Prior art date
Application number
PCT/CN2005/001157
Other languages
English (en)
Chinese (zh)
Inventor
Long Luo
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006024216A1 publication Critical patent/WO2006024216A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates

Definitions

  • the present invention relates to the field of network security, and in particular to a method and system for implementing authentication. Background of the invention
  • the Internet has become a popular communication method.
  • the servers in the network are often subjected to malicious attacks by illegal users through the client, resulting in a large amount of data loss and damage in the server.
  • a method for implementing authentication, setting a client authentication center comprising the following steps:
  • the client sends the authentication identifier to the client authentication center;
  • the client will access the request. Send to the client authentication center;
  • A2 The client authentication center generates an authentication parameter, and then carries the generated authentication parameter in the client authentication request and sends the authentication parameter to the client;
  • the client obtains the authentication identifier according to the authentication parameter carried in the client authentication request.
  • the method further includes: setting a keystore including a plurality of keys, and storing the set keystore in a client authentication center and each client software, wherein different keys are correspondingly different in the keystore Key serial number;
  • step A2 the step of generating the authentication parameter by the client authentication center includes: the client authentication center selects a key from the keystore saved by itself, and obtains the key sequence number corresponding to the selected key, and then generates a key. a random number, and an encryption algorithm selected by itself; the authentication parameter includes a key sequence number, a random number, and an encryption algorithm;
  • the method further includes: setting a private key corresponding to the client authentication center in the client authentication center, and setting a public key corresponding to the client authentication center in each client software; in step A2, the client authentication
  • the step of generating a random number by the center further includes: the client authentication center signatures the generated random number by using the set private key;
  • the random number included in the authentication parameter is a signed random number
  • the secret is a client software version identifier used by the client to use the software
  • step B the step of the client authentication center determining whether the authentication is successful by determining whether the decrypted secret is legal or not includes: determining, by the client authentication center, whether the client with the same client software version identifier as the decrypted client is saved. End software version identifier, if yes, the authentication is successful.
  • the client software version identifier includes: a client software version serial number, or a client software version serial number and a issuing company identifier.
  • the different client software includes not
  • the client authentication center is connected to an application server;
  • the step A includes: the client sends the authentication identifier to the application server, and the application server sends the authentication identifier to the client authentication center.
  • the method further includes: pre-storing the user name and password of the registered user in the application server; the client sends the user name and password input by the user to the application server, and the application server determines whether the user name and password are the same as the received user name and password. Username and password. If yes, the authentication is successful. Otherwise, the authentication fails.
  • the method further includes: setting a trigger authentication policy in the application server;
  • the step A further includes: the application server determining, according to the set trigger authentication policy Whether the client authentication process should be performed currently, and if so, the step of transmitting the authentication identifier to the client authentication center is continued, otherwise, the current process is ended.
  • the triggering authentication policy includes: whether the number of consecutively receiving the same client access request exceeds the set number of times threshold, or, periodically detecting, or randomly detecting, or, unconditionally detecting, or detecting a specific service, or, Billing detection.
  • the triggering authentication policy is whether the number of consecutively receiving the same client access request exceeds the set threshold value
  • the step of determining, by the application server, whether the client authentication process should be performed currently includes: determining, by the application server, whether the number of times the client access request has been continuously received exceeds a preset threshold value, and if yes, determining that the current response should be Perform the client authentication process.
  • the method further includes: setting a correspondence between different authentication identifiers and different user identifiers in the client authentication center;
  • the step A further includes: the client acquiring the user identifier input by the user, and obtaining the obtained The extracted user ID is sent to the client authentication center;
  • the step B further includes: the client authentication center authenticating the client according to whether the received authentication identifier and the user identifier meet the set correspondence relationship.
  • the user identifier is a mobile phone number or a user name of the user.
  • the client accesses the visited area
  • the step A includes: the client sends the authentication identifier to the client authentication center of the visited area, and the client authentication center of the visiting area sends the authentication identifier to the client authentication center of the home zone;
  • the client authentication center is a client authentication center of the client home zone.
  • a system for implementing authentication comprising a client, an application server, and a client authentication center, wherein the application server is connected to the client and the client authentication center respectively.
  • the client authentication center sends the client authentication request to the application server, receives the authentication identifier sent by the application server, and then authenticates the client according to the received authentication identifier;
  • the application server sends a client authentication request from the client authentication center to the client, and sends the authentication identifier from the client to the client authentication center;
  • the client obtains the authentication identifier after receiving the client authentication request from the application server, and sends the obtained authentication identifier to the application server.
  • the client authentication center is a separate network entity
  • the client authentication center and the application server are connected through a customized Ca interface.
  • the client authentication center and the existing entities in the network are combined into one physical entity.
  • the existing entities in the network are home location registers or application servers.
  • the present invention has the following advantages:
  • the operator assigns different client software version identifiers to different client softwares, and
  • the authentication process is performed according to the client software version identifier, and the client software version identifier is difficult to be obtained by the illegal user. Therefore, the security and reliability of the authentication are greatly improved, and the malicious user is prevented from establishing a connection with the server. Attack, standardizing the network order.
  • the CCC in addition to authenticating the client, the CCC further authenticates the user identity and authenticates successfully if both the client and the user are authenticated. Therefore, the security and reliability of authentication are further improved through the two-factor authentication process.
  • the key information of the client software that is, the client software version identifier, can be grasped, and the client software can be uniformly upgraded and charged, and the user behavior can be easily regulated and managed.
  • Figure 1 is a schematic view showing the structure of the system of the present invention.
  • FIG. 2 is a flow chart of authenticating a client in an embodiment of the present invention.
  • the present invention proposes a new method and system for implementing authentication.
  • the core idea of the method is: setting a client authentication center; the client sends the authentication identifier to the client authentication center; the client authentication center The client is authenticated according to the received authentication identifier.
  • the authentication identifier is information that uniquely identifies the client, for example, encrypting the client software version identifier previously allocated for the software used by the client as the authentication identifier.
  • the core idea of the present invention is to authenticate the client, that is, to verify the legality of the client software used by the client. Moreover, in order to further ensure the security of the authentication process, it may further include authenticating the identity of the user.
  • the trigger authentication policy may be preset.
  • the AS receives the access request sent by the client, the AS does not immediately instruct the client authentication center to perform the authentication process, but firstly according to the set trigger.
  • the authentication policy determines whether the subsequent authentication process should be performed on the client. If it is determined that the subsequent process of authenticating the client should be performed, the process of instructing the client authentication center to perform authentication is continued.
  • FIG. 1 is a schematic view showing the structure of the system of the present invention.
  • the system of the present invention includes: a client, an AS, and a Client Certification Center (CCC).
  • the CCC may be a separate network entity set up by the present invention, or may be combined with an existing entity in the network into a physical entity.
  • the CCC may be combined with a Home Location Register (HLR) or an AS as a network entity.
  • HLR Home Location Register
  • AS Serving Authentication Service
  • 2 is a flow chart of authenticating a client in an embodiment of the present invention. .
  • FIG. 1 and FIG. 2 applying the system of the present invention, the process of implementing the authentication by the method of the present invention specifically includes the following steps:
  • Step 201 Allocate different client software version identifiers for each different client software in advance, and save each of the allocated client software version identifiers in the CCC.
  • the client software version identifier includes a client software version serial number, and may further include information such as a company logo.
  • Step 202 Pre-set a keystore including a plurality of keys, and save the set keystore in the CCC.
  • Step 203 Pre-storing each of the allocated client software version identifiers in the corresponding client software, and storing the keystores in each client software separately.
  • Step 204 Set a trigger authentication policy in the AS in advance.
  • the triggering authentication policy may be set according to the actual service requirement.
  • the triggered authentication policy may be: whether the number of consecutively receiving the same client access request exceeds the set number of times threshold, and/or the periodicity set by the operator. Detection, random detection, unconditional detection, detection of specific services, billing detection, etc.
  • steps 201 to 204 are a series of initial setting processes performed by the present invention to implement the subsequent actual authentication process.
  • ⁇ may further set a private key corresponding to the CCC in the CCC, and set a public key corresponding to the CCC in each client software, for verifying the identity of the CCC in the subsequent authentication process. .
  • Step 205 The client sends an access request carrying the identifier of the client software version to the AS.
  • Step 206 The AS obtains the client software version identifier from the received access request, and then determines whether the current client should be authenticated according to the acquired client software version identifier and the triggering authentication policy. If yes, step 207 is performed. Otherwise, perform the existing process of allowing the client to access and establish a connection, ending the current process.
  • the process of determining whether the current client should be authenticated may be: For example, if the preset trigger authentication policy is that the number of consecutively receiving the same client access request exceeds the set number of times threshold, the AS determines the current Whether the number of times the access request carrying the acquired client software version identifier has been continuously received exceeds the preset number of times, and if so, it is considered that the current client should be authenticated; for example, a preset trigger authentication policy For the periodic detection set by the operator, the AS determines whether it is currently in the period of periodic detection. If yes, it considers that the current client should be authenticated.
  • Step 207 The AS sends the obtained client software version identifier in the client authentication indication to the CCC through the Ca interface.
  • Step 208 The CCC selects a key from its saved keystore, generates a random number, and then uses the key number of the selected key in the keystore, the generated random number, and an encryption algorithm saved by itself.
  • the bearer is sent to the AS through the Ca interface in the client authentication request.
  • the CCC may further sign the generated random number using the set private key, and carry the signed random number in the client.
  • the random number carried in the client authentication request in this step may be a signed random number.
  • Step 209 The AS sends the received client authentication request to the client.
  • Step 210 The client obtains the key sequence number from the received client authentication request, and the Number of machines and encryption algorithms.
  • the client after receiving the client authentication request, the client obtains the signed random number from the client, and the client further uses the client.
  • the public key corresponding to the CCC set in itself is used to verify the signed random number. If the verification result is a CCC signature, the client can confirm that the random number is sent by the CCC, that is, the random number is considered to be legal. The subsequent authentication process is continued. Otherwise, the random number is not sent by the CCC. If the random number is considered illegal, the current authentication process is terminated.
  • Step 211 The client searches for the corresponding key from the stored keystore according to the obtained key sequence number, and then performs the secret in itself according to the found key, the obtained random number, and the encryption algorithm. Encryption, and then the encrypted secret is carried in the client authentication response message and sent to the AS.
  • the secret is selected from the client software version identifier. For example, if the client software version identifier includes the client software version serial number and the issuing company information, the client may select the client software version serial number as the secret for encryption.
  • Step 212 The AS sends the received client authentication response message to the ccc through the Ca interface.
  • Step 213 After receiving the client authentication response, the CCC obtains the encrypted secret therefrom, and then uses the key selected in step 208, the generated random number, and the decryption algorithm saved in itself to obtain the encrypted encrypted information.
  • the secret is decrypted, and then it is judged whether the decrypted secret is legal. If yes, step 214 is performed; otherwise, step 215 is performed.
  • the CCC determines whether the decrypted secret is legal by judging whether or not the same secret as the decrypted secret is stored in itself. For example, in step 211, the client selects the client software version serial number as the secret for encryption. In this step, the CCC decrypted secret is the client software version serial number of the client, and the CCC determines whether it is in the client. Has The decrypted client software version serial number is saved, and if so, the decrypted secret is considered legal.
  • Step 214 The CCC sends a client authentication success message to the AS through the Ca interface, and the AS notifies the client that the authentication is successful, performs a subsequent service connection process, and ends the current process.
  • the operator can also establish a corresponding relationship between the client software and the user in advance, that is, the operator can pre-agreed the user identifier with the user, and set different client software version identifiers in the CCC.
  • the client software version identifier includes a client software version serial number, and may further include information such as a company identifier, where the user identifier is an identifier that can uniquely prove the identity of the user, such as a mobile phone number or a user name of the user. Wait.
  • the method further includes: determining whether there is a correspondence between the current client software version identifier and the user identifier, and the specific implementation process can be seen in FIG. 3, including the following steps:
  • Steps 301 to 307 are the same as all descriptions of steps 201 to 207.
  • Step 308 The CCC selects a key from its saved keystore, generates a random number, and then serializes the selected key in the keystore, the generated random number, the encryption algorithm saved by itself, and The user identification information is required to be carried in the client authentication request and sent to the AS through the Ca interface.
  • the CCC may further sign the generated random number using the set private key, and carry the signed random number in the client.
  • the random number carried in the client authentication request in this step may be a signed random number.
  • Step 309 The AS sends the received client authentication request to the client.
  • Step 310 The client obtains the key sequence number from the received client authentication request, and the The number of machines and the encryption algorithm are provided, and the user identification information is provided according to the requirements carried in the client authentication request to prompt the user to input the user identifier, and obtain the user identifier input by the user.
  • the client after receiving the client authentication request, the client obtains the signed random number from the client, and the client further uses the client.
  • the public key corresponding to the CCC set in itself is used to verify the signed random number. If the verification result is a CCC signature, the client can confirm that the random number is sent by the CCC, that is, the random number is considered to be legal. The subsequent authentication process is continued. Otherwise, the random number is not sent by the CCC. If the random number is considered illegal, the current authentication process is terminated.
  • Step 311 The client searches for the corresponding key from the stored keystore according to the obtained key sequence number, and then performs the secret in itself according to the found key, the obtained random number, and the encryption algorithm. encryption.
  • Step 312 The client sends the encrypted secret and the obtained user identifier to the AS in the client authentication response message.
  • the secret is selected from the client software version identifier.
  • the client software version identifier includes the client software version serial number and the issuing company information, and the client can select the client software version serial number as the secret for encryption.
  • Step 313 The AS sends the received client authentication response message to the ccc through the Ca interface.
  • Step 314 After receiving the client authentication response, the CCC obtains the encrypted secret and the user identifier, and then uses the key selected in step 308, the generated random number, and the decryption algorithm saved in itself to obtain the acquired The encrypted secret is decrypted, and then it is judged whether the decrypted secret is legal. If yes, step 316 is performed; otherwise, step 315 is performed.
  • the CCC determines whether the decrypted secret is legal by judging whether or not the same secret as the decrypted secret is stored in itself. For example, in step 312, the client selects a guest.
  • the client software version serial number is encrypted as a secret.
  • the secret of the CCC decryption is the client software version serial number of the client, and the CCC determines whether the decrypted client software has been saved in the client software. The version serial number, if any, considers the decrypted secret to be legal.
  • Step 315 The CCC sends a client authentication failure message to the AS through the Ca interface, and the AS notifies the client that the authentication fails, denies the client access, and ends the current process.
  • Step 316 The CCC determines whether there is a preset correspondence between the decrypted secret and the acquired user identifier. If yes, step 317 is performed; otherwise, the process returns to step 315.
  • Step 317 The CCC sends a client authentication success message to the AS through the Ca interface, and the AS notifies the client that the authentication is successful, and performs a subsequent service connection process.
  • the client after receiving the client authentication request sent by the client authentication center, the client sends the encrypted password as the authentication identifier, that is, the encrypted client software version identifier to the encrypted client software version identifier.
  • the client may also actively send the authentication identifier to the AS in the access request, and the AS sends the authentication identifier to the client authentication center.
  • the principle is the same as that of the above embodiment.
  • the authentication process of the present invention may further include a currently existing process of authenticating the user identity by the AS.
  • the specific implementation can be implemented in multiple ways.
  • the user name and the secret of the registered user are saved in the application server in advance; when the authentication is performed, the client sends the user name and password input by the user to the AS, and the AS judges itself. Whether the user name and password with the same username and password are saved. If yes, the authentication of the current user is considered successful. Otherwise, the authentication fails.
  • the process of authenticating the user identity in the present invention may be performed after the client authentication is successful, or may be performed before the client is authenticated.
  • both the wired network and the mobile network can be divided into two types: the client accessing the home zone and the visiting zone.
  • the foregoing process describes the process of implementing authentication when the client accesses the home zone.
  • the process of implementing the authentication by the present invention is the same as the above process.
  • All the messages between the AS and the CCC need to be forwarded through the CCC (VCCC) of the visited area. That is, when the AS receives the access request sent by the client, it sends the client authentication indication to the VCCC.
  • the VCCC forwards the client authentication indication to the CCC of the client home zone according to the client software version identifier carried in the client authentication indication, and forwards the client authentication response sent by the VCCC to the CCC of the client home zone.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Procédé pour mettre en oeuvre la certification et systèmes correspondants. Le système comprend un client, un serveur d'applications et un centre de certification client (CCC). Le procédé consiste en ce que le client envoie un identificateur de certification au CCC via le serveur d'applications et que le CCC octroie un certificat au client selon l'identificateur de certification reçue. La présente invention permet d'améliorer sensiblement la sécurité et la fiabilité; elle permet aux fournisseurs de contrôler les informations clé du logiciel client. Elle facilite également la mise à jour et la facturation du logiciel client ainsi que l'uniformisation et la gestion du comportement des clients.
PCT/CN2005/001157 2004-07-29 2005-07-29 Procede pour mettre en oeuvre la certification et systemes correspondants WO2006024216A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2004100703130A CN100499453C (zh) 2004-07-29 2004-07-29 一种客户端认证的方法
CN200410070313.0 2004-07-29

Publications (1)

Publication Number Publication Date
WO2006024216A1 true WO2006024216A1 (fr) 2006-03-09

Family

ID=35927668

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001157 WO2006024216A1 (fr) 2004-07-29 2005-07-29 Procede pour mettre en oeuvre la certification et systemes correspondants

Country Status (2)

Country Link
CN (1) CN100499453C (fr)
WO (1) WO2006024216A1 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101192926B (zh) * 2006-11-28 2011-03-30 北京握奇数据系统有限公司 帐号保护的方法及系统
JP2008181228A (ja) * 2007-01-23 2008-08-07 Sony Corp 管理システムおよび管理方法、端末装置、管理サーバ、並びにプログラム
CN101127744B (zh) * 2007-09-29 2010-10-13 杭州华三通信技术有限公司 对非法客户端进行隔离提示的方法和系统以及网关设备
US20100241861A1 (en) * 2007-12-05 2010-09-23 Tetsuro Yoshimoto Dhcp client server system, dhcp client device and dhcp server device
CN101860521B (zh) * 2009-04-13 2013-05-08 中国联合网络通信集团有限公司 认证处理方法及系统
CN101998575B (zh) * 2009-08-24 2013-04-24 华为技术有限公司 一种接入控制的方法、装置和系统
CN102202040B (zh) * 2010-03-26 2014-06-04 联想(北京)有限公司 一种对客户端进行认证方法及装置
CN103795692B (zh) * 2012-10-31 2017-11-21 中国电信股份有限公司 开放授权方法、系统与认证授权服务器
TWI529537B (zh) * 2013-06-04 2016-04-11 晨星半導體股份有限公司 具有移動高畫質連接埠之顯示器及其信號處理方法
CN103327489B (zh) * 2013-06-28 2017-04-05 宇龙计算机通信科技(深圳)有限公司 认证的方法和系统
US10033720B2 (en) * 2014-05-28 2018-07-24 Futurewei Technologies, Inc. Method and system for creating a certificate to authenticate a user identity
CN113886848A (zh) * 2021-09-23 2022-01-04 深圳优地科技有限公司 信息验证方法、装置、机器人及存储介质
CN114826570A (zh) * 2022-03-30 2022-07-29 微位（深圳）网络科技有限公司 证书获取方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020073322A1 (en) * 2000-12-07 2002-06-13 Dong-Gook Park Countermeasure against denial-of-service attack on authentication protocols using public key encryption
WO2003050995A1 (fr) * 2001-12-07 2003-06-19 Qualcomm Incorporated Authentification d'un reseau de communication hybride
CN1444362A (zh) * 2002-03-08 2003-09-24 华为技术有限公司 无线局域网加密密钥的分发方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020073322A1 (en) * 2000-12-07 2002-06-13 Dong-Gook Park Countermeasure against denial-of-service attack on authentication protocols using public key encryption
WO2003050995A1 (fr) * 2001-12-07 2003-06-19 Qualcomm Incorporated Authentification d'un reseau de communication hybride
CN1444362A (zh) * 2002-03-08 2003-09-24 华为技术有限公司 无线局域网加密密钥的分发方法

Also Published As

Publication number Publication date
CN100499453C (zh) 2009-06-10
CN1728636A (zh) 2006-02-01

Similar Documents

Publication Publication Date Title
WO2006024216A1 (fr) Procede pour mettre en oeuvre la certification et systemes correspondants
US9531681B2 (en) Method for the authentication of applications
US8024488B2 (en) Methods and apparatus to validate configuration of computerized devices
JP4674044B2 (ja) クライアントが許可を検証できるキー管理プロトコルを設けるためのシステムおよび方法
JP6033291B2 (ja) サービスアクセス認証方法およびシステム
EP3850510B1 (fr) Inscription de dispositif d'infrastructure
CN102299930B (zh) 一种保障客户端软件安全的方法
WO2019085531A1 (fr) Procédé et dispositif d'authentification de connexion de réseau
KR100350316B1 (ko) 에이에이에이 서버에 과부하 방지를 위한 접근요청 메시지처리 방법
WO2012037897A1 (fr) Procédé, système et dispositif d'association et d'utilisation d'une carte à mémoire numérique sécurisée
JP2016533694A (ja) ユーザアイデンティティ認証方法、端末及びサーバ
CN109525565B (zh) 一种针对短信拦截攻击的防御方法及系统
KR101531662B1 (ko) 사용자 단말과 서버간 상호 인증 방법 및 시스템
KR20090054774A (ko) 분산 네트워크 환경에서의 통합 보안 관리 방법
WO2006026925A1 (fr) Procede d'etablissement de la cle d'authentification
US20050144459A1 (en) Network security system and method
WO2013004104A1 (fr) Procédé et système de signature unique
JP5185926B2 (ja) アンチ・エミュレーション機構を備えた、サービスを提供する装置、システム及び方法
KR20070009490A (ko) 아이피 주소 기반 사용자 인증 시스템 및 방법
WO2012000313A1 (fr) Procédé et système de certification de passerelle de rattachement
JP7043480B2 (ja) 情報処理システムと、その制御方法とプログラム
KR20130046781A (ko) 무선 네트워크 접속 인증 방법 및 그 시스템
CN109818903B (zh) 数据传输方法、系统、装置和计算机可读存储介质
CN110225011B (zh) 用户节点的认证方法、设备及计算机可读存储介质
WO2005046119A1 (fr) Procede d'etablissement d'association entre l'identification d'une transaction de session et l'entite d'application de reseau

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase