WO2013079037A1 - 一种允许用户访问的方法、客户端、服务器以及系统 - Google Patents

一种允许用户访问的方法、客户端、服务器以及系统 Download PDF

Info

Publication number
WO2013079037A1
WO2013079037A1 PCT/CN2012/085772 CN2012085772W WO2013079037A1 WO 2013079037 A1 WO2013079037 A1 WO 2013079037A1 CN 2012085772 W CN2012085772 W CN 2012085772W WO 2013079037 A1 WO2013079037 A1 WO 2013079037A1
Authority
WO
WIPO (PCT)
Prior art keywords
identification code
user
server
type
client
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/085772
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
瞿超
万巍
雷超
李小磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Peking University Founder Group Co Ltd
Beijing Founder Apabi Technology Co Ltd
Original Assignee
Peking University Founder Group Co Ltd
Beijing Founder Apabi Technology 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 Peking University Founder Group Co Ltd, Beijing Founder Apabi Technology Co Ltd filed Critical Peking University Founder Group Co Ltd
Priority to KR1020137031873A priority Critical patent/KR20140035382A/ko
Priority to EP12852657.1A priority patent/EP2787707A4/en
Priority to JP2014536108A priority patent/JP2014534515A/ja
Priority to US14/118,161 priority patent/US20140298428A1/en
Publication of WO2013079037A1 publication Critical patent/WO2013079037A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/08—Network architectures or network communication protocols for network security for authentication of entities
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • 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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles

Definitions

  • the present invention relates to the field of computer application technologies, and in particular, to a method, a client, a server, and a system for allowing a user to access. Background technique
  • the Web operating system is an indispensable application in the process of using the Internet.
  • the Web operating system mainly provides the following two methods to enable users to access the server:
  • the first type the user accesses the server through a browser provided by the Web operating system on the client side, that is, a normal PC;
  • API Application Programming Interface
  • the server Whether the user accesses the server through the above access mode on the ordinary PC or on the mobile device, the server must authenticate and judge the user identity and usage rights.
  • the user's identity and the usage rights of the related functions that the user can use are statically authenticated to ensure that the user information in different application scenarios is synchronized and shared. Judging whether the user has the right to use a certain function based on the result of the authentication.
  • static authentication is only performed when the user logs in, and in the process of the user accessing the server, it is impossible to determine whether the user has the right to use certain applications, that is, it is impossible to judge whether the user is in the process of accessing the user. Allow users to continue accessing the server. Summary of the invention
  • the embodiment of the invention provides a method for allowing a user to access, which is used to solve the problem that the user is allowed to continue to access during the process of the user accessing the server.
  • a method of allowing user access comprising:
  • the server receives the type identification code and/or the service identification code and the user identity information sent by the client, where the client generates a type identification code and/or a service identification code corresponding to the application for each application accessed by the login user.
  • the type identification code is used to identify the type to which the application belongs; the service identification code is used to uniquely identify an application;
  • the server determines, according to the user identity information, the number of the type identification code and/or the type identification code received by the login user, and determines whether the login user is allowed to access according to the determination result.
  • a system that allows a user to access comprising:
  • a server configured to receive a type identifier code and/or a service identifier code sent by the client, and user identity information; determining, according to the user identity information, the type identifier code and/or the type received by the login user The number of the identification code is determined according to the determination result whether the login user is allowed to access; the type identification code is used to identify the type of the application; the service identification code is used to uniquely identify an application;
  • the client is configured to generate, for each application accessed by the login user, a type identification code and/or a service identification code corresponding to the application.
  • a client, the client includes:
  • a generating unit configured to generate, for each application accessed by the logged-in user, a type identification code and/or a service identification code corresponding to the application; the type identification code is used to identify a type to which the application belongs; The identification code is used to uniquely identify an application;
  • a sending unit configured to send the type identifier code and/or the service identifier code generated by the generating unit and the user identity information to the server.
  • a server comprising:
  • a receiving unit configured to receive a type identifier code and/or a service identifier code sent by the client, and user identity information; the type identifier code is used to identify a type to which the application belongs; and the service identifier code is used to uniquely identify an application;
  • the determining unit is configured to determine, according to the user identity information, the number of the type identification code and/or the type identification code received by the login user, and determine, according to the determination result, whether the login user is allowed to access.
  • the method can solve the problem of determining whether to allow the user to continue access during the user's access to the server.
  • FIG. 1 is a schematic flowchart of a method for allowing a user to access according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a first method for allowing a user to access according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a third method for allowing user access according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a system for allowing user access according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a client according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a server according to an embodiment of the present invention. detailed description
  • An embodiment of the present invention provides a method for allowing a user to access, according to the number of types of applications accessed by the user and/or the number of applications accessed by the user during the user access to the server, Allow the user to continue accessing the server; as shown in Figure 1, specific The process is as follows:
  • Step 11 The server receives the type identifier code and/or the service identifier code sent by the client, and the user identity information of the login user, where the client generates a type identifier code corresponding to the application for each application accessed by the login user. And/or a service identification code; the type identification code is used to identify a type to which the application belongs; and the service identification code is used to uniquely identify an application;
  • Step 12 The server determines, according to the user identity information, the number of the type identifier code and/or the type identifier code received by the login user, and determines, according to the determination result, whether the login user is allowed to access. .
  • step 12 it is determined whether the login user is allowed to access according to the determination result: determining whether the total number of the type identification codes received by the user is greater than a preset number of types, when the determination is not greater than Allowing the user to access; or determining whether the total number of the service identification codes received by the user is greater than a total number of services set in advance, and allowing the user to access when determining not to be greater than; or Whether the sum of the number of the service identification code and the type identification code received by the user is greater than a preset total number of accesses, and allowing the user to access when the determination is not greater than.
  • the method further includes: the client retaining one of the plurality of identical type identification codes generated.
  • the method further includes: the client generating account information for the logged-in user; the account information is used to identify the user identity;
  • the specific content of the execution is: the client sends the generated type identification code and/or service identification code, account information, and user identity information to the server;
  • the client sends the generated type identification code and/or service identification code and account information to the server, and according to the server,
  • the user identity information before determining the number of the type identifier code and/or the type identifier code received by the login user, further includes: determining, by the server, the received account information according to a preset login condition Whether it is valid; at this time, the determination process is performed when it is determined that the account information is valid;
  • the server determines that the user can continue to access the application, according to the type identifier code received to the user and / or service identification code and account information generation token, determine the validity period of the token; and send the token to the client; when the user logs in to the server again at other times, send a command to the server while accessing the server Card,
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the first embodiment of the present invention provides a first method for allowing user access, as shown in FIG. 2, the specific process is as follows:
  • Step 201 The client allocates a type identification code for each application accessed by the login user and the user identity information of the login user.
  • the type identifier code used by the login user for the user is used to identify the type of the application.
  • Step 202 The client sends the generated type identification code and the user identity information to the server.
  • Step 203 The server determines, according to the user identity information, whether the total number of type identification codes received by the user is greater than a preset number of types. If the determination is not greater than, go to step 204, otherwise the user is prohibited from continuing to access;
  • Step 204 allowing the user to continue to access
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the second embodiment of the present invention provides a second method for allowing user access, as shown in FIG. 3, the specific process is as follows:
  • Step 301 The client allocates a service identification code and user identity information of the login user for each application accessed by the login user.
  • the service identification code is used to uniquely identify an application; ;
  • Step 302 The client sends the generated service identification code and user identity information to the server.
  • Step 303 The server determines, according to the user identity information, the service identifier received by the user. Whether the total number of codes is greater than the total number of services set in advance, and when it is determined not to be greater than, the process proceeds to step 304; otherwise, the user is prohibited from continuing to access;
  • Step 304 allowing the user to continue to access
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the third embodiment of the present invention provides a third method for allowing user access, as shown in FIG. 4, the specific process is as follows:
  • Step 401 The client allocates a service identification code and a type identification code for each application accessed by the login user, and the user identity information of the login user; the login user is referred to as the user;
  • Step 402 The client sends the generated service identification code, type identification code, and user identity information to the server.
  • Step 403 The server determines, according to the user identity information, whether the total number of service identification codes received by the user is greater than a preset total number of services. If the determination is not greater than, the process proceeds to step 404; otherwise, the user is prohibited from continuing to access; Alternatively, the server determines whether the total number of the received type identification codes is greater than a preset number of types. If the determination is not greater than, the process proceeds to step 404; otherwise, the user is prohibited from continuing to access; or the server determines the received type identification code. Whether the sum of the number of the service identification codes is greater than the number of accesses, and when the determination is not greater than, the process proceeds to step 404; otherwise, the user is prohibited from continuing to access;
  • Step 404 allowing the user to access
  • the client may also generate an account information for the login user in step 201, step 301 or step 401; then in step 202, step 302 or step 402, The client also needs to send the account information to the server together; after step 202, step 302 or step 402, before step 203, step 303 or step 403, the server further includes, according to the account information, after the server receives the account information. Determining whether the login user corresponding to the account information has the right to access, and when determining the right, proceeding to step 203, step 303 or step 403; otherwise, determining that the user does not have access, that is, prohibiting the user from continuing to access;
  • the client may retain one of the plurality of identical type identification codes generated; in step 202 or step 402, the client sends the simplified type identification code to the server.
  • the server performs the legality verification operation on the user each time.
  • the server may Generate a token according to the account information, the type identification code, and the service identification code, and set an expiration date for the token; and send the generated token to the client; when the user accesses the server again, the client directly connects with the user The corresponding token is sent to the server, and the server determines that the client has the right to access based on the token.
  • the server When the user voluntarily quits the server or the token expires, the server considers that the user is not eligible for access; when the server does not allow the user to access, it may also send a forbidden access token to the client;
  • the number of different types, the number of different accesses, and the total number of different services may be set according to different account information, and the number of types, the number of accesses, and the total number of services may also be set. Set to the same;
  • the client assigns a type identification code to the application, as shown in the following method:
  • all the accessed applications can be assigned the same type identification code; when the user accesses the server through the client's API interface, each application accessed is assigned a different type identifier. code;
  • the client allocates a service identification code for the application, and the method is as follows:
  • a service identifier different from other applications is generated for each application; when the user accesses the server through the client's PC browser, each time a new server is established with the server The session state connection, that is, the generation of a service identifier.
  • an embodiment of the present invention provides a system for allowing a user to access, and the system includes:
  • the server 52 is configured to receive a type identifier code and/or a service identifier code sent by the client, and user identity information of the login user, and determine, according to the user identity information, the type identifier code received by the login user and/or Or the number of the type identification code, determining whether the login user is allowed to access according to the determination result; the type identification code is used to identify the type to which the application belongs; and the service identification code is used to uniquely identify an application;
  • the client 51 is configured to generate, for each application accessed by the login user, a type identification code and/or a service identification code corresponding to the application.
  • the client 51 is also used to:
  • the client 51 is also used to:
  • Generating account information for the login user sending the generated type identification code and/or service identification code and the account information to the server 52; the account information is used to identify the user identity;
  • the server 52 is also used to:
  • Determining whether the account information is valid according to a preset login condition when determining that the account information is valid, the server determines, according to the user identity information, the type identification code received by the login user and/or Or the number of the type identification code.
  • the server 52 is also used to:
  • the embodiment of the present invention further provides a client, where the client includes: a generating unit 61, configured to generate, for each application accessed by the login user, a type identification code corresponding to the application.
  • the service identification code is used to identify the type of the application; the service identification code is used to uniquely identify an application;
  • the sending unit 63 is configured to send the type identification code and/or the service identification code generated by the generating unit 61 and the user identity information to the server.
  • the client also includes:
  • a retaining unit 62 configured to use, for the plurality of identical type identification codes generated by the generating unit 61, Keep one of them.
  • the generating unit 61 is further configured to: generate account information for the login user; the account information is used to identify the user identity;
  • the sending unit 63 is specifically configured to send the type identification code and/or the service identification code and the account information generated by the generating unit 61 to the server.
  • the embodiment of the present invention further provides a server, where the server includes: a receiving unit 71, configured to receive a type identifier code and/or a service identifier code sent by a client, and user identity information of a login user;
  • the type identification code is used to identify the type to which the application belongs;
  • the service identification code is used to uniquely identify an application;
  • the determining unit 73 is configured to determine the number of the type identification code and/or the type identification code received by the login user, and determine, according to the determination result, whether the login user is allowed to access.
  • the receiving unit 71 is further configured to: receive account information generated by the client for the login user; and the account information is used to identify the identity of the login user;
  • the server further includes:
  • the account determining unit 72 is configured to determine whether the account information is valid according to a preset login condition
  • the determining unit 73 is specifically configured to: when the account determining unit 72 determines that the account information is valid, determine the received type identification code and/or service identification code.
  • the server 52 further includes:
  • a first generating unit 74 configured to generate a token according to the type identifier code and/or the service identifier code and the account information received by the receiving unit 71, determine an expiration date of the token, and send the token to Client.
  • the method provided by the embodiment of the present invention in the process of the user accessing the server, according to the number of types of applications accessed by the user and/or the total number of applications accessed, or the accessed application.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • a computer-usable storage medium including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
PCT/CN2012/085772 2011-12-01 2012-12-03 一种允许用户访问的方法、客户端、服务器以及系统 Ceased WO2013079037A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020137031873A KR20140035382A (ko) 2011-12-01 2012-12-03 사용자 액세스를 허용하는 방법, 클라이언트, 서버 및 시스템
EP12852657.1A EP2787707A4 (en) 2011-12-01 2012-12-03 PROCESS FOR ENABLING USER ACCESS, CLIENT, SERVER AND SYSTEM
JP2014536108A JP2014534515A (ja) 2011-12-01 2012-12-03 ユーザーのアクセス許可の方法、システム、クライアントおよびサーバ
US14/118,161 US20140298428A1 (en) 2011-12-01 2012-12-03 Method for allowing user access, client, server, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110393869.3 2011-12-01
CN201110393869.3A CN103139182B (zh) 2011-12-01 2011-12-01 一种允许用户访问的方法、客户端、服务器以及系统

Publications (1)

Publication Number Publication Date
WO2013079037A1 true WO2013079037A1 (zh) 2013-06-06

Family

ID=48498492

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/085772 Ceased WO2013079037A1 (zh) 2011-12-01 2012-12-03 一种允许用户访问的方法、客户端、服务器以及系统

Country Status (6)

Country Link
US (1) US20140298428A1 (enExample)
EP (1) EP2787707A4 (enExample)
JP (1) JP2014534515A (enExample)
KR (1) KR20140035382A (enExample)
CN (1) CN103139182B (enExample)
WO (1) WO2013079037A1 (enExample)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016530767A (ja) * 2013-07-08 2016-09-29 コンヴィーダ ワイヤレス， エルエルシー Ｉｍｓｉレスデバイスからｅｐｃへの接続

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6123539B2 (ja) * 2013-07-18 2017-05-10 大日本印刷株式会社 識別子生成装置、識別子生成方法、及び識別子生成プログラム
CN104468495B (zh) * 2013-09-25 2018-03-06 北大方正集团有限公司 一种电子资源借阅控制的方法和系统
KR102311331B1 (ko) * 2014-11-20 2021-10-13 에스케이플래닛 주식회사 데이터저장장치 및 그 동작 방법
KR101684278B1 (ko) * 2015-10-30 2016-12-08 주식회사 컨시어지소프트 응용프로그램 제어 장치를 이용한 응용프로그램 제어 방법
US9554279B1 (en) * 2015-11-12 2017-01-24 Finjan Mobile, Inc. Authorized areas of authentication
US11290425B2 (en) * 2016-02-01 2022-03-29 Airwatch Llc Configuring network security based on device management characteristics
CN106992972B (zh) * 2017-03-15 2018-09-04 咪咕数字传媒有限公司 一种接入方法及装置
CN108092951B (zh) * 2017-11-08 2021-08-27 腾讯科技(成都)有限公司 客户端登录方法和装置、存储介质及电子装置
CN109787852A (zh) * 2017-11-15 2019-05-21 小草数语（北京）科技有限公司 账号有效性检测方法、装置及其设备
CN111181977B (zh) * 2019-12-31 2021-06-04 瑞庭网络技术（上海）有限公司 一种登录方法、装置、电子设备及介质
CN111600900B (zh) * 2020-05-26 2022-09-02 牛津(海南)区块链研究院有限公司 基于区块链的单点登录方法、服务端及系统
CN115868144A (zh) * 2020-06-29 2023-03-28 伊鲁米纳公司 经由安全发现框架的临时云提供商凭据

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309233A (zh) * 2008-06-04 2008-11-19 腾讯科技（深圳）有限公司 实现即时通讯tcp连接复用的方法
CN101631120A (zh) * 2009-08-20 2010-01-20 中兴通讯股份有限公司 应用服务器和媒体资源分配方法
CN101674293A (zh) * 2008-09-11 2010-03-17 阿里巴巴集团控股有限公司 一种分布式应用中处理非正常请求的方法及系统
CN102045331A (zh) * 2009-10-22 2011-05-04 成都市华为赛门铁克科技有限公司 查询请求报文处理方法、装置及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5260999A (en) * 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
JPH08263283A (ja) * 1995-03-24 1996-10-11 Ricoh Co Ltd ソフトウェア管理システム
US7437550B2 (en) * 1999-12-02 2008-10-14 Ponoi Corp. System for providing session-based network privacy, private, persistent storage, and discretionary access control for sharing private data
US20020116649A1 (en) * 2001-02-21 2002-08-22 Kenji Goshima Authentication system and authentication method
CN101166173B (zh) * 2006-10-20 2012-03-28 北京直真节点技术开发有限公司 一种单点登录系统、装置及方法
WO2008060300A1 (en) * 2006-11-16 2008-05-22 Dynomedia, Inc. Systems and methods for distributed digital rights management
US8583915B1 (en) * 2007-05-31 2013-11-12 Bby Solutions, Inc. Security and authentication systems and methods for personalized portable devices and associated systems
US20130014141A1 (en) * 2011-07-06 2013-01-10 Manish Bhatia Audience Atmospherics Monitoring Platform Apparatuses and Systems
US8868915B2 (en) * 2010-12-06 2014-10-21 Verizon Patent And Licensing Inc. Secure authentication for client application access to protected resources

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101309233A (zh) * 2008-06-04 2008-11-19 腾讯科技（深圳）有限公司 实现即时通讯tcp连接复用的方法
CN101674293A (zh) * 2008-09-11 2010-03-17 阿里巴巴集团控股有限公司 一种分布式应用中处理非正常请求的方法及系统
CN101631120A (zh) * 2009-08-20 2010-01-20 中兴通讯股份有限公司 应用服务器和媒体资源分配方法
CN102045331A (zh) * 2009-10-22 2011-05-04 成都市华为赛门铁克科技有限公司 查询请求报文处理方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2787707A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016530767A (ja) * 2013-07-08 2016-09-29 コンヴィーダ ワイヤレス， エルエルシー Ｉｍｓｉレスデバイスからｅｐｃへの接続
JP2017143539A (ja) * 2013-07-08 2017-08-17 コンヴィーダ ワイヤレス， エルエルシー Ｉｍｓｉレスデバイスからｅｐｃへの接続
US9930613B2 (en) 2013-07-08 2018-03-27 Convida Wireless, Llc Connecting IMSI-less devices to the EPC
US10812461B2 (en) 2013-07-08 2020-10-20 Convida Wireless, Llc Connecting IMSI-less devices to the EPC
US11973746B2 (en) 2013-07-08 2024-04-30 Interdigital Patent Holdings, Inc. Connecting IMSI-less devices to the EPC

Also Published As

Publication number Publication date
KR20140035382A (ko) 2014-03-21
EP2787707A1 (en) 2014-10-08
JP2014534515A (ja) 2014-12-18
US20140298428A1 (en) 2014-10-02
CN103139182A (zh) 2013-06-05
CN103139182B (zh) 2016-04-06
EP2787707A4 (en) 2015-07-29

Similar Documents

Publication Publication Date Title
WO2013079037A1 (zh) 一种允许用户访问的方法、客户端、服务器以及系统
TWI792320B (zh) 判定認證能力之查詢系統、方法及非暫態機器可讀媒體
CN102761549B (zh) 资源共享的处理方法和系统以及业务平台
US8925053B1 (en) Internet-accessible service for dynamic authentication and continuous assertion of trust level in identities
JP5570610B2 (ja) 遠隔ユーザ・セッションのためのシングル・サインオン
JP2014534515A5 (enExample)
CN104917727B (zh) 一种帐户鉴权的方法、系统及装置
WO2013097588A1 (zh) 应用程序登录方法、装置和移动终端
CN109600337B (zh) 资源处理方法、装置、系统及计算机可读介质
KR20180053701A (ko) 로컬 디바이스 인증
CN111800377B (zh) 一种基于安全多方计算的移动终端身份认证系统
CN103188344A (zh) 一种安全调用rest api的方法
CN110730174A (zh) 一种网络访问控制方法、装置、设备及介质
WO2018161807A1 (zh) 用户身份校验方法及装置
CN105554004A (zh) 一种混合云计算环境中容器服务的认证系统和方法
KR20150036371A (ko) 클라우드 서버를 위한 바우처 인가
CN106331003B (zh) 一种云桌面上应用门户系统的访问方法及装置
US20170279798A1 (en) Multi-factor authentication system and method
CN103095666B (zh) 第三方应用处理方法及装置
CN107862198A (zh) 一种访问验证方法、系统及客户端
TW201638822A (zh) 進程的身份認證方法和裝置
CN110069909A (zh) 一种免密登录第三方系统的方法及装置
CN113765655A (zh) 访问控制方法、装置、设备及存储介质
US10264455B1 (en) Short-range cross-device authorization
CN117411660A (zh) 资源授权方法、装置、存储介质及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12852657

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14118161

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2012852657

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20137031873

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2014536108

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE