WO2014008858A1 - 实现跨域跳转的方法以及浏览器、域名服务器 - Google Patents

实现跨域跳转的方法以及浏览器、域名服务器 Download PDF

Info

Publication number
WO2014008858A1
WO2014008858A1 PCT/CN2013/079124 CN2013079124W WO2014008858A1 WO 2014008858 A1 WO2014008858 A1 WO 2014008858A1 CN 2013079124 W CN2013079124 W CN 2013079124W WO 2014008858 A1 WO2014008858 A1 WO 2014008858A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
domain name
cross
user
identifier
Prior art date
Application number
PCT/CN2013/079124
Other languages
English (en)
French (fr)
Inventor
罗茂政
杨雍
毛宇
王明慧
王志豪
郑闫强
卢寅
张志东
Original Assignee
腾讯科技（深圳）有限公司
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 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP13817388.5A priority Critical patent/EP2874074B1/en
Priority to RU2015104540/08A priority patent/RU2595931C1/ru
Publication of WO2014008858A1 publication Critical patent/WO2014008858A1/zh
Priority to US14/594,705 priority patent/US9686344B2/en

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
    • 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

Definitions

  • the present invention relates to network technologies, and in particular, to a method for implementing cross-domain hopping, a browser, a first domain name server, and a second domain name server.
  • Domain Name is the name of a computer or group of computers on the Internet consisting of a series of dot-separated names used to identify the computer's electronic orientation (sometimes referred to as geographic location) during data transmission. Each website corresponds to a unique domain name. Switching between different websites can be called cross-domain jump. For example, clicking a link on another website in a website is a cross-domain jump.
  • a method for implementing a cross-domain jump includes the following steps:
  • the second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes a cross corresponding to the first identity identifier of the user in the first domain name.
  • Domain user ID
  • the second domain name server obtains the second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name, and generates the user login state of the user in the second domain name according to the second identity identifier.
  • a browser that includes:
  • the request obtaining module is configured to obtain a request for jumping from the first domain name to the second domain name;
  • a browser sending module configured to send the second domain name and the first identity identifier of the user in the first domain name to the first domain name server;
  • a browser receiving module configured to receive, by the first domain name server, a cross-domain user identifier generated according to the second domain name and the first identity identifier, where the cross-domain user identifier and the second identity identifier of the user in the second domain name Corresponding;
  • the browser sending module is further configured to send a cross-domain jump request from the first domain name to the second domain name to the second domain name server, where the cross-domain jump request includes the cross-domain user identifier.
  • the browser After obtaining the request for jumping from the first domain name to the second domain name, the browser receives the cross-domain user identifier generated according to the second domain name and the first identity identifier from the first domain name server, and includes the cross-domain user identifier.
  • the cross-domain jump request is sent to the second domain name server, and the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name. Therefore, the user login status cannot be maintained, and the user login status can be maintained.
  • the user After the cross-domain jump, the user operates at the terminal time, which saves power, especially for a mobile terminal with limited power, which can extend the battery life.
  • a first domain name server comprising:
  • a first receiving module configured to receive a second domain name sent by the browser and a first identity identifier of the user in the first domain name
  • a cross-domain identifier generating module configured to generate a cross-domain user identifier according to the second domain name and the first identity identifier, where the cross-domain user identifier corresponds to a second identity identifier of the user in the second domain name;
  • the first sending module is configured to send the cross-domain user identifier to the browser.
  • the first domain name server After receiving the second domain name sent by the browser and the first identity identifier of the user in the first domain name, the first domain name server generates a cross-domain user identifier according to the second domain name and the first identity identifier, and generates the cross-domain user.
  • the identifier corresponds to the second identity identifier of the user in the second domain name, and sends the cross-domain user identifier to the browser, so that when the browser requests the webpage resource from the second domain name, the identifier may be identified in the second domain name.
  • the cross-domain user identifier of the second identity identifier is sent to the second domain name browser, and the user login status cannot be maintained without requiring the user to log in to the second domain name.
  • a second domain name server comprising:
  • a second receiving module configured to receive a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes the first identity identifier in the first domain name with the user Corresponding cross-domain user ID;
  • a second identity identifier obtaining module configured to generate a second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name
  • the login status generating module is configured to generate a user login status of the user in the second domain name according to the second identity identifier.
  • the cross-domain hop request received by the browser includes the cross-domain user identifier, and generates the second identity identifier of the user in the second domain name according to the cross-domain user identifier, and identifies the user identity according to the second identity.
  • the user does not need to log in to the second domain name, and the user's login status can still be maintained.
  • the method for implementing the cross-domain hopping, the cross-domain hop request corresponding to the first identity identifier of the user in the first domain name, and the second domain name The server may generate the second identity identifier of the user in the second domain name according to the cross-domain user identifier, and identify the identity of the user according to the second identity identifier, so that the user does not need to re-start when jumping from the first domain name to the second domain name.
  • the user can still be logged in, reducing the time for the user to operate in the terminal after the cross-domain jump, and saving power, especially for a mobile terminal with limited power, which can extend the battery life.
  • FIG. 1 is a schematic flowchart of a method for implementing cross-domain hopping in an embodiment
  • FIG. 2 is a schematic flowchart of a method for implementing cross-domain hopping in another embodiment
  • FIG. 3 is a schematic flowchart of a method for implementing cross-domain hopping in still another embodiment
  • FIG. 4 is a flowchart of a method for implementing a cross-domain jump in an embodiment
  • FIG. 5 is a schematic structural diagram of a browser in an embodiment
  • FIG. 6 is a schematic structural diagram of a first domain name server in an embodiment
  • FIG. 7 is a schematic structural diagram of a second domain name server in an embodiment
  • FIG. 8 is a schematic structural diagram of a second domain name server in another embodiment
  • FIG. 9 is a schematic structural diagram of a system for implementing cross-domain hopping in an embodiment
  • FIG. 10 is a schematic structural diagram of a browser in another embodiment
  • FIG. 11 is a schematic structural diagram of a browser in still another embodiment
  • FIG. 12 is a schematic structural diagram of a system for implementing cross-domain jump in another embodiment.
  • a method for implementing a cross-domain jump includes the following steps:
  • Step S102 The second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes a first identity identifier corresponding to the user in the first domain name.
  • Cross-domain user ID The second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes a first identity identifier corresponding to the user in the first domain name.
  • a request to jump from the first domain name to the second domain name will be triggered.
  • the cross-domain user identifier corresponding to the first identity identifier of the user in the first domain name may be obtained, and a cross-domain jump request including the cross-domain user identifier is generated, and the cross-domain jump request is sent to the Second domain name server.
  • the first identity of the user in the first domain name is the user name or user account entered by the user to log in to the first domain name or the identification number assigned to the user after the user logs in to the first domain name.
  • Step S104 The second domain name server acquires a second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name, and generates a user login state of the user in the second domain domain according to the second identity identifier.
  • the second domain name server may parse the cross-domain jump request according to a preset manner, extract the cross-domain user identifier from the cross-domain jump request, decrypt the cross-domain user identifier, and obtain the decryption. After the cross-domain user identifier, the validity of the decrypted cross-domain user identifier is checked, and the second identity identifier of the user corresponding to the decrypted cross-domain user identifier in the second domain name is searched.
  • a legal cross-domain user identity may be pre-stored.
  • the second domain name server may search for the decrypted cross-domain user identifier in the pre-stored legal cross-domain user identifier. If the search succeeds, the decrypted cross-domain user identifier is legal. If the search fails, the decrypted cross is obtained. The domain user ID is not legal. Further, in an embodiment, the user login status of the second identity identifier may be marked as already logged in in the user login status database of the second domain name.
  • a method for implementing cross-domain hopping includes the following steps:
  • Step S202 The first domain name server obtains a request for the browser to jump from the first domain name to the second domain name, where the request includes the second domain name and the first identity identifier of the user in the first domain name.
  • the method for implementing the cross-domain jump further includes the following steps: the browser acquires a login request of the user to the first domain name, where the login request includes the first identity identifier of the user in the first domain name. (such as user name or user account) and user password; the browser sends the login request to the first domain name server; the first domain name server verifies the login request, and sends the verification result to the browser; if the browser receives the verification result And generating a file for saving the logged-in user information of the first domain name and writing the first identity identifier in the file, and further saving the file to the preset directory.
  • the logged in user information of the first domain name can be used to identify the identity of the user operating on the web page of the first domain name.
  • the browser reads the user in the first domain name from the file in the preset directory for saving the logged-in user information of the first domain name.
  • the first identity identifier further generates a request to jump from the first domain name to the second domain name including the second domain name and the first identity identifier, and sends the request to the first domain name server.
  • Step S204 The first domain name server generates a cross-domain user identifier according to the second domain name and the first identity identifier, and returns the cross-domain user identifier to the browser.
  • the specific process of the first domain name server generating the cross-domain user identifier according to the second domain name and the first identity identifier is: the first domain name server searches for the registration identifier and the second domain name key corresponding to the second domain name, and The registration identifier is combined with the first identity identifier. Further, the first domain name server encrypts the combined identifier according to the second domain name key to generate a cross-domain user identifier.
  • the second domain name may be registered in the first domain name in advance, and the first domain name server may pre-store the registration identifier of the second domain name (which may be referred to as appid) and the second domain name key of the second domain name (may be called appkey ).
  • the first domain name server may send the cross-domain user identifier to the browser, and the browser generates a cross-domain jump request including the cross-domain user identifier and the second domain name. Further, the browser sends a cross-domain jump request to the second domain name server.
  • the second domain name server may generate a cross-domain jump request including the cross-domain user ID and the second domain name, and send the cross-domain jump request to the browser. Further, the browser forwards the cross-domain jump request to the second domain name server.
  • Step S206 The second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes the first identity identifier corresponding to the user in the first domain name.
  • Cross-domain user ID The second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes the first identity identifier corresponding to the user in the first domain name.
  • Step S208 The second domain name server obtains the second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name, and generates the user login status of the user in the second domain name according to the second identity identifier.
  • a method for implementing a cross-domain jump includes the following steps:
  • Step S302 The browser acquires a request for jumping from the first domain name to the second domain name, and generates a cross-domain user identifier according to the second domain name and the first identity identifier.
  • the specific process for the browser to generate the cross-domain user identifier according to the second domain name and the first identity identifier is: the browser searches for the registration identifier and the second domain name key corresponding to the second domain name, and the registration identifier and the An identity identifier is combined; the browser encrypts the combined identifier according to the second domain name key to generate a cross-domain user identifier.
  • the first domain name server may embed the registration identifier and the second domain name key of the second domain name included in the webpage resource in the webpage resource. And embedding a program for generating a cross-domain user identifier according to the second domain name and the first identity identifier in the webpage resource, and delivering the webpage resource to the browser.
  • the browser may execute a program that generates a cross-domain user identifier according to the second domain name and the first identity identifier in the pre-embedded webpage resource, and obtains cross-domain User ID.
  • Step S304 The browser generates a cross-domain jump request according to the cross-domain user identifier and the second domain name, and sends the cross-domain jump request to the second domain name server.
  • the browser may generate a cross-domain jump request that includes a cross-domain user identifier and a second domain name to jump from the first domain name to the second domain name, and send the cross-domain jump request to the second domain name server.
  • Step S306 the second domain name server obtains a cross-domain jump request sent by the browser to jump from the first domain name to the second domain name, where the cross-domain jump request includes the first identity identifier corresponding to the user in the first domain name.
  • Cross-domain user ID the cross-domain user ID
  • Step S308 the second domain name server obtains the second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name, and generates the user login state of the user in the second domain name according to the second identity identifier.
  • the method for implementing the cross-domain jump further includes the following steps: the second domain name server returns the webpage resource corresponding to the cross-domain jump request and the user identity information corresponding to the second identity identifier to the browser; The device displays the webpage corresponding to the webpage resource, and displays the user identity information corresponding to the second identity identifier in the webpage.
  • the browser may display user identity information corresponding to the second identity, such as a user name or a user nickname, in the corresponding location of the webpage, to indicate that the user has logged in to the second domain name.
  • user identity information corresponding to the second identity, such as a user name or a user nickname, in the corresponding location of the webpage, to indicate that the user has logged in to the second domain name.
  • the method for implementing cross-domain hopping further includes the step of: the browser storing the second identity identifier in a file in the preset directory for saving the logged-in user information of the second domain name.
  • the browser may encrypt the second identity identifier according to a preset format. Further, the encrypted second identity identifier may be saved in a file in the preset directory for saving the logged-in user information of the second domain name. The logged in user information of the second domain name can be used to identify the identity of the user operating on the second domain name web page.
  • the browser sends a login request to log in to the first domain name server to the first domain name server.
  • the first domain name server verifies the login request, and returns the information of the user's login request verification and the webpage resource of the first domain name to the user browser.
  • the browser obtains a request for the user to jump from the first domain name to the second domain name, obtains the first identity identifier of the user in the first domain name, and sends a processing request including the second domain name and the first identity identifier to the first domain name. server.
  • the first domain name server receives the processing request, generates the cross-domain user identifier of the user according to the second domain name and the first identity identifier, and generates a cross-domain hopping from the first domain name to the second domain name including the cross-domain user identifier. Transfer request to send a cross-domain jump request to the browser.
  • the browser sends a cross-domain jump request to the second domain name server.
  • the second domain name server resolves the cross-domain jump request, extracts the cross-domain user identifier, generates the second identity identifier of the user in the second domain name according to the cross-domain user identifier, and generates the user in the second domain name according to the second identity identifier.
  • the user login status further obtains the webpage resource corresponding to the second domain name.
  • the second domain name server sends the webpage resource corresponding to the cross-domain jump request and the second identity identifier to the browser.
  • a browser 10 includes a request acquisition module 102, a browser sending module 104, and a browser receiving module 106, wherein:
  • the request obtaining module 102 is configured to obtain a request to jump from the first domain name to the second domain name.
  • the browser sending module 104 is configured to send the second domain name and the first identity identifier of the user in the first domain name to the first domain name server.
  • the first identity of the user in the first domain name is the user name or user account entered by the user to log in to the first domain name or the identification number assigned to the user after the user logs in to the first domain name.
  • the browser 10 obtains a login request of the first domain name by the user, where the login request includes a first identity (such as a user name or a user account) and a user password of the user in the first domain name; the browser 10
  • the login request is sent to the first domain name server; the first domain name server verifies the login request, and sends the verification result to the browser 10; if the browser 10 receives the verification result, generates the logged-in user for saving the first domain name.
  • the file of the information is written into the first identity in the file, and the file is further saved to the default directory.
  • the logged in user information of the first domain name can be used to identify the identity of the user operating on the web page of the first domain name.
  • the browser 10 reads the user in the first domain name from the file of the logged-in user information for saving the first domain name in the preset directory.
  • the first identity identifier, and further, the second domain name and the read first identity identifier are sent to the first domain name server.
  • the browser receiving module 106 is configured to receive, by the first domain name server, a cross-domain user identifier generated according to the second domain name and the first identity identifier, where the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name.
  • the second domain name server may send the generated cross-domain user identifier to the browser 10 according to the cross-domain user identifier generated by the second domain name and the first identity identifier.
  • the browser sending module 104 is further configured to send a cross-domain jump request from the first domain name to the second domain name to the second domain name server, where the cross-domain jump request includes the cross-domain user identifier.
  • the browser 10 further includes a cross-domain request generation module (not shown) for generating a cross-domain jump request according to the cross-domain user identification and the second domain name.
  • the cross-domain request generation module may generate a cross-domain jump request that includes a cross-domain user identifier and a second domain name to jump from the first domain name to the second domain name.
  • the browser receiving module 106 is further configured to receive the webpage resource and the second identity corresponding user identity information corresponding to the cross-domain jump request sent by the second domain name server.
  • the browser 10 further includes a display module (not shown) for displaying a webpage corresponding to the webpage resource, and displaying the user identity information corresponding to the second identity in the webpage.
  • the display module may display user identity information corresponding to the second identity, such as a user name or a user nickname, in the corresponding location of the webpage, to indicate that the user has logged in to the second domain name.
  • user identity information corresponding to the second identity, such as a user name or a user nickname, in the corresponding location of the webpage, to indicate that the user has logged in to the second domain name.
  • the browser 10 further includes an identity saving module (not shown) for saving the second identity to a file in the preset directory for saving the logged-in user information of the second domain.
  • the identity saving module may encrypt the second identity identifier according to a preset format. Further, the encrypted second identity identifier may be saved to a file in the preset directory for saving the logged-in user information of the second domain name. in. The logged in user information of the second domain name can be used to identify the identity of the user operating on the second domain name web page.
  • the browser 10 After obtaining the request for jumping from the first domain name to the second domain name, the browser 10 receives the cross-domain user identifier generated according to the second domain name and the first identity identifier from the first domain name server, and includes the cross-domain user identifier.
  • the cross-domain jump request is sent to the second domain name server, and the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name. Therefore, the user login status can still be maintained without re-login.
  • the time for the user to operate in the terminal after the cross-domain jump is reduced, and the power is saved, especially for a mobile terminal with limited power, which can improve the battery life.
  • a first domain name server 20 includes a first receiving module 202, a cross-domain identity generating module 204, and a first sending module 206, where:
  • the first receiving module 202 is configured to receive a second domain name sent by the browser and a first identity identifier of the user in the first domain name.
  • the cross-domain identity generation module 204 is configured to generate, according to the second domain name and the first identity identifier, a cross-domain user identifier, where the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name.
  • the cross-domain identifier generating module 204 is configured to search for a registration identifier and a second domain name key corresponding to the second domain name, and combine the registration identifier and the first identity identifier, and combine the second domain name key pair according to the second domain name.
  • the identity is encrypted and a cross-domain user ID is generated.
  • the second domain name may be registered in the first domain name in advance, and the first domain name server 20 may pre-store the registration identifier of the second domain name (which may be referred to as appid) and the second domain name key of the second domain name (which may be referred to as Appkey).
  • appid the registration identifier of the second domain name
  • Appkey the second domain name key of the second domain name
  • the first sending module 206 is configured to send the cross-domain user identifier to the browser.
  • the first domain name 20 further includes a cross-domain request generation module (not shown) for generating a cross-domain jump request including the cross-domain user identifier and the second domain name.
  • the first sending module 206 is configured to send a cross-domain jump request to the browser.
  • the first domain name server 20 After receiving the second domain name sent by the browser and the first identity identifier of the user in the first domain name, the first domain name server 20 generates a cross-domain user identifier according to the second domain name and the first identity identifier, and generates the cross-domain
  • the user identifier corresponds to the second identity identifier of the user in the second domain name
  • the cross-domain user identifier is sent to the browser, so that the browser can identify the user in the second domain name when requesting the webpage resource from the second domain name.
  • the cross-domain user identifier of the second identity is sent to the second domain browser, and the user is not required to log in to the second domain name, and the login state of the user can still be maintained.
  • a second domain name server 30 includes a second receiving module 302, a second identity acquiring module 304, and a login state generating module 306, where:
  • the second receiving module 302 is configured to receive a cross-domain hopping request that is sent by the browser to the second domain name, where the cross-domain hopping request includes the first identities corresponding to the user in the first domain name.
  • Cross-domain user ID is configured to be received from the browser to the second domain name.
  • the second identity identifier obtaining module 304 is configured to acquire a second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name.
  • the second identity identifier obtaining module 304 may parse the cross-domain jump request according to a preset manner, extract the cross-domain user identifier from the cross-domain jump request, and decrypt the cross-domain user identifier to obtain the decryption. After the cross-domain user identifier, the validity of the decrypted cross-domain user identifier is checked, and the second identity identifier of the user corresponding to the decrypted cross-domain user identifier in the second domain name is searched.
  • the second domain name server may pre-store the legal cross-domain user identifier, and the second identity identifier obtaining module 304 may search the decrypted cross-domain user identifier in the pre-stored legal cross-domain user identifier. If successful, the decrypted cross-domain user ID is legal. If the search fails, the decrypted cross-domain user ID is invalid.
  • the login status generating module 306 is configured to generate a user login status of the user in the second domain name according to the second identity identifier.
  • the login status generation module 306 can mark the user login status of the second identity in the user login status database of the second domain name as already logged in.
  • the second domain name server 30 further includes:
  • the information returning module 308 is configured to return the webpage resource corresponding to the cross-domain jump request and the user identity information corresponding to the second identity identifier to the browser.
  • the second domain name server 30 includes a cross-domain user identifier received from the browser, and generates a second identity identifier of the user in the second domain name according to the cross-domain user identifier, and identifies the user according to the second identity. Identity, you do not need to log in to the second domain name, you can still keep the user's login status.
  • a system for implementing a cross-domain jump includes the browser 10, the first domain name server 20, and the second domain name server 30 in any of the above embodiments, and the browser 10 includes the same as shown in FIG.
  • the first domain name server 20 includes a first receiving module 202, a cross-domain identification generating module 204, and a first sending module 206, as shown in FIG.
  • the domain name server includes a second receiving module 302, a second identity acquiring module 304, and a login state generating module 306 as shown in FIG. 7, wherein:
  • the request obtaining module 102 is configured to obtain a request to jump from the first domain name to the second domain name.
  • the browser sending module 104 is configured to send the second domain name and the first identity identifier of the user in the first domain name to the first domain name server 20.
  • the first receiving module 202 is configured to receive the second domain name sent by the browser 10 and the first identity identifier of the user in the first domain name.
  • the cross-domain identifier generating module 204 is configured to generate a cross-domain user identifier according to the second domain name and the first identity identifier.
  • the first sending module 206 is configured to send the cross-domain user identifier to the browser 10.
  • the browser receiving module 106 is configured to receive the cross-domain user identifier sent by the first domain name server 20.
  • the browser sending module 104 is further configured to send a cross-domain jump request from the first domain name to the second domain name to the second domain name server 30, where the cross-domain jump request includes a cross-domain user identifier.
  • the second receiving module 302 is configured to receive a cross-domain jump request sent by the browser 10 to jump from the first domain name to the second domain name.
  • the second identity identifier obtaining module 304 is configured to acquire a second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name.
  • the login status generating module 306 is configured to generate a user login status of the user in the second domain name according to the second identity identifier.
  • a browser 40 includes a request acquisition unit 402, a cross-domain identification generation unit 404, and a browser transmission unit 406, where:
  • the request obtaining unit 402 is configured to obtain a request to jump from the first domain name to the second domain name.
  • the cross-domain identifier generating unit 404 is configured to generate a cross-domain user identifier according to the second domain name and the first identity identifier of the user in the first domain name, where the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name.
  • the cross-domain identifier generating unit 404 is configured to search for the registration identifier and the second domain name key corresponding to the second domain name, and combine the registration identifier and the first identity identifier, and combine the second domain name key pair according to the second domain name.
  • the identity is encrypted and a cross-domain user ID is generated.
  • the first domain name server may embed the registration identifier and the second domain name key of the second domain name included in the webpage resource in the webpage resource. And embedding a program for generating a cross-domain user identifier according to the second domain name and the first identity identifier in the webpage resource, and delivering the webpage resource to the browser.
  • the cross-domain identifier generating unit 404 may execute a program that may be embedded in the webpage resource and generate a cross-domain user identifier according to the second domain name and the first identity identifier, and generate a cross. Domain user ID.
  • the browser sending unit 406 is configured to send a cross-domain jump request from the first domain name to the second domain name to the second domain name server, where the cross-domain jump request includes the cross-domain user identifier.
  • the browser 40 further includes:
  • the browser receiving unit 408 is configured to receive a webpage resource corresponding to the cross-domain jump request sent by the second domain name server and user identity information corresponding to the second identity identifier.
  • the browser 40 further includes a display module (not shown) for displaying a webpage corresponding to the webpage resource, and displaying the user identity information corresponding to the second identity in the webpage.
  • the browser 40 obtains the cross-domain user identifier generated according to the second domain name and the first identity identifier after the request to jump from the first domain name to the second domain name, and the cross-domain jump request that includes the cross-domain user identifier Sent to the second domain name server, and the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name. Therefore, the user login status can be maintained without re-login, and the cross-domain jump is reduced. After the user operates at the terminal, the power is saved, especially for a mobile terminal with limited power, which can improve the battery life.
  • a system for implementing a cross-domain jump includes the browser 40 and the second domain name server 30 in any of the above embodiments, and the browser 40 includes the same as shown in FIG.
  • the second domain name server includes a second receiving module 302, a second identity acquiring module 304, and a login state generating module 306, as shown in FIG. :
  • the request obtaining unit 402 is configured to obtain a request to jump from the first domain name to the second domain name.
  • the cross-domain identifier generating unit 404 is configured to generate a cross-domain user identifier according to the second domain name and the first identity identifier of the user in the first domain name, where the cross-domain user identifier corresponds to the second identity identifier of the user in the second domain name.
  • the browser sending unit 406 is configured to send a cross-domain jump request from the first domain name to the second domain name to the second domain name server 20, where the cross-domain jump request includes a cross-domain user identifier.
  • the second receiving module 302 is configured to receive a cross-domain jump request sent by the browser 40 to jump from the first domain name to the second domain name.
  • the second identity identifier obtaining module 304 is configured to acquire a second identity identifier of the user corresponding to the cross-domain user identifier in the second domain name.
  • the login status generating module 306 is configured to generate a user login status of the user in the second domain name according to the second identity identifier.
  • the method and system for implementing the cross-domain hopping, the cross-domain hop request corresponding to the first identity identifier of the user in the first domain name may generate the second identity identifier of the user in the second domain name according to the cross-domain user identifier, and identify the identity of the user according to the second identity identifier, so that the user does not need to jump from the first domain name to the second domain name. If you log in again, you can still keep the user's login status, reduce the time that the user operates in the terminal after the cross-domain jump, and save power, especially for mobile terminals with limited power, which can improve the battery life.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种实现跨域跳转的方法，包括以下步骤：第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，所述跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识；第二域名服务器获取与所述跨域用户标识对应的用户在第二域名中的第二身份标识，根据所述第二身份标识生成用户在第二域名中的用户登录状态。上述方法中第二域名服务器可根据跨域用户标识生成用户在第二域名中的第二身份标识，并根据第二身份标识辨识出用户的身份，从而用户在从第一域名跳转到第二域名时不需要再重新登录，依然可保持用户登录状态，因此提高了用户的操作便利性。此外，还提供一种浏览器、第一域名服务器和第二域名服务器。

Description

实现跨域跳转的方法以及浏览器、域名服务器
【技术领域】
本发明涉及网络技术，特别地涉及一种实现跨域跳转的方法、浏览器、第一域名服务器、第二域名服务器。
【背景技术】
域名（Domain Name），是由一串用点分隔的名字组成的Internet上某一台计算机或计算机组的名称，用于在数据传输时标识计算机的电子方位（有时也指地理位置）。每一个网站都对应唯一的一个域名，在不同网站之间的切换访问则可称为跨域跳转，例如，点击一个网站中另一个网站的链接即为跨域跳转。
当用户登录某一域名的网站后，点击该网站上的链接跳转到其他域名的网站时，传统的实现跨域跳转的方法中，其他域名的网站不能识别到用户的登录信息，因此跳转到其他域名的网站后并不能保持用户的登录状态。用户只能在其他域名的网站上重新输入登录信息（例如输入帐号和密码）才能登录进入该网站。因此，传统的实现跨域跳转的方法中，不同域名的网站不能保持用户的登录状态，给用户操作带来不便，用户必须在终端上进行多次操作才能实现跨域跳转后才能保持用户的状态，这必要会增加用户在终端上的操作时间，从而导致终端的耗电量增加，特别是对于电量有限的移动终端来说，会缩短续航时间。
【发明内容】
基于此，有必要提供一种在不同网站之间进行跨域跳转时可保持用户登录状态的实现跨域跳转的方法。
一种实现跨域跳转的方法，包括以下步骤：
第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，所述跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识；
第二域名服务器获取与所述跨域用户标识对应的用户在第二域名中的第二身份标识，根据所述第二身份标识生成用户在第二域名中的用户登录状态。
基于此，有必要提供一种在不同网站之间进行跨域跳转时可保持用户登录状态的实现跨域跳转的浏览器。
一种浏览器，包括：
请求获取模块，用于获取从第一域名跳转到第二域名的请求；
浏览器发送模块，用于将所述第二域名和用户在第一域名中的第一身份标识发送至第一域名服务器；
浏览器接收模块，用于接收第一域名服务器发送的根据所述第二域名和第一身份标识生成的跨域用户标识，所述跨域用户标识与用户在第二域名中的第二身份标识相对应；
所述浏览器发送模块还用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器，所述跨域跳转请求中包含所述跨域用户标识。
上述浏览器，获取到从第一域名跳转至第二域名的请求后，从第一域名服务器接收根据第二域名和第一身份标识生成的跨域用户标识，并且将包含跨域用户标识的跨域跳转请求发送至第二域名服务器，而该跨域用户标识又与用户在第二域名中的第二身份标识相对应，因此，不需要再重新登录，依然可保持用户登录状态，减少了跨域跳转后用户在终端操作的时间，节省了电量，特别是对电量有限的移动终端来说，能延长续航时间。
基于此，有必要提供一种可实现从第一域名跳转到第二域名时可保持用户登录状态的第一域名服务器。
一种第一域名服务器，包括：
第一接收模块，用于接收浏览器发送的第二域名和用户在第一域名中的第一身份标识；
跨域标识生成模块，用于根据所述第二域名和第一身份标识生成跨域用户标识，所述跨域用户标识与用户在所述第二域名中的第二身份标识相对应；
第一发送模块，用于将所述跨域用户标识发送至所述浏览器。
上述第一域名服务器，接收到浏览器发送的第二域名和用户在第一域名中的第一身份标识后，根据第二域名和第一身份标识生成跨域用户标识，且生成的跨域用户标识与用户在第二域名中的第二身份标识相对应，并将跨域用户标识发送至浏览器，使得浏览器在向第二域名请求网页资源时，可将标识用户在第二域名中的第二身份标识的跨域用户标识发送给第二域名浏览器，不需要用户登录第二域名，依然可保持用户的登录状态。
基于此，有必要提供一种可实现从第一域名跳转到第二域名时可保持用户登录状态的第二域名服务器。
一种第二域名服务器，包括：
第二接收模块，用于接收浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，所述跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识；
第二身份标识获取模块，用于生成与所述跨域用户标识对应的用户在第二域名中的第二身份标识；
登录状态生成模块，用于根据所述第二身份标识生成用户在第二域名中的用户登录状态。
上述第二域名服务器，从浏览器接收的跨域跳转请求中包含了跨域用户标识，并根据跨域用户标识生成用户在第二域名中的第二身份标识，根据第二身份辨识用户身份，不需要用户登录第二域名，依然可保持用户的登录状态。
上述实现跨域跳转的方法，从第一域名跳转到第二域名的跨域跳转请求中包含了与用户在第一域名中的第一身份标识对应的跨域用户标识，第二域名服务器可根据跨域用户标识生成用户在第二域名中的第二身份标识，并根据第二身份标识辨识出用户的身份，从而用户在从第一域名跳转到第二域名时不需要再重新登录，依然可保持用户登录状态，减少了跨域跳转后用户在终端操作的时间，节省了电量，特别是对电量有限的移动终端来说，能延长续航时间。
【附图说明】
图1为一个实施例中的实现跨域跳转的方法的流程示意图；
图2为另一实施例中的实现跨域跳转的方法的流程示意图；
图3为又一实施例中的实现跨域跳转的方法的流程示意图；
图4为一个实施例中的实现跨域跳转的方法的工作流程图；
图5为一个实施例中的浏览器的结构示意图；
图6为一个实施例中的第一域名服务器的结构示意图；
图7为一个实施例中的第二域名服务器的结构示意图；
图8为另一实施例中的第二域名服务器的结构示意图；
图9为一个实施例中的实现跨域跳转的系统的结构示意图；
图10为另一实施例中的浏览器的结构示意图；
图11为又一实施例中的浏览器的结构示意图；
图12为另一实施例中的实现跨域跳转的系统的结构示意图。
【具体实施方式】
如图1所示，在一个实施例中，一种实现跨域跳转的方法，包括以下步骤：
步骤S102，第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识。
在一个实施例中，在第一域名的网页中的第二域名的链接被点击后，将触发从第一域名跳转到第二域名的请求。获取到该请求后，可获取与用户在第一域名中的第一身份标识对应的跨域用户标识，并生成包含跨域用户标识的跨域跳转请求，将该跨域跳转请求发送到第二域名服务器。
在一个实施例中，用户在第一域名中的第一身份标识为用户登录第一域名输入的用户名称或用户账号或用户登录第一域名后为用户分配的标识号等。
步骤S104，第二域名服务器获取与跨域用户标识对应的用户在第二域名中的第二身份标识，根据第二身份标识生成用户在第二域名中的用户登录状态。
具体的，在一个实施例中，第二域名服务器可按照预设的方式解析跨域跳转请求，从跨域跳转请求中提取出跨域用户标识，将跨域用户标识进行解密，得到解密后的跨域用户标识，检查解密后的跨域用户标识的合法性，并查找与解密后的跨域用户标识对应的用户在第二域名中的第二身份标识。
在一个实施例中，可预先存储合法的跨域用户标识。第二域名服务器可在预先存储的合法的跨域用户标识中查找解密后的跨域用户标识，若查找成功，则解密后的跨域用户标识是合法的，若查找失败，则解密后的跨域用户标识是不合法的。进一步的，在一个实施例中，可在第二域名的用户登录状态数据库中标记第二身份标识的用户登录状态为已经登录。
如图2所示，在一个实施例中，一种实现跨域跳转的方法，包括以下步骤：
步骤S202，第一域名服务器获取浏览器发送的从第一域名跳转到第二域名的请求，该请求中包含第二域名和用户在第一域名中的第一身份标识。
在一个实施例中，在步骤S202之前，上述实现跨域跳转的方法还包括步骤：浏览器获取用户对第一域名的登录请求，登录请求中包含用户在第一域名中的第一身份标识（如用户名称或用户账号）和用户密码；浏览器将登录请求发送给第一域名服务器；第一域名服务器验证登录请求，并将验证结果发送给浏览器；若浏览器接收到验证通过的结果，则生成用于保存第一域名的已登录用户信息的文件并在文件中写入第一身份标识，进一步将该文件保存至预设目录下。第一域名的已登录用户信息可用于辨识在第一域名的网页上进行操作的用户的身份。
进一步的，当在第一域名的网页中的第二域名的链接被点击后，浏览器从预设目录下用于保存第一域名的已登录用户信息的文件中读取用户在第一域名中的第一身份标识，进一步的生成包含第二域名和第一身份标识的从第一域名跳转到第二域名的请求，将该请求发送至第一域名服务器。
步骤S204，第一域名服务器根据第二域名和第一身份标识生成跨域用户标识，将跨域用户标识返回至浏览器。
在一个实施例中，第一域名服务器根据第二域名和第一身份标识生成跨域用户标识的具体过程为：第一域名服务器查找与第二域名对应的注册标识和第二域名密钥，将注册标识和第一身份标识进行组合，进一步的，第一域名服务器根据第二域名密钥对组合后的标识进行加密处理，生成跨域用户标识。
具体的，第二域名可预先在第一域名中进行注册，第一域名服务器可预先存储第二域名的注册标识（可称为appid）以及第二域名的第二域名密钥（可称为appkey）。
进一步的，第一域名服务器可将跨域用户标识发送给浏览器，浏览器生成包含跨域用户标识和第二域名的跨域跳转请求。进一步的，浏览器将跨域跳转请求发送给第二域名服务器。在另一个实施例中，第二域名服务器可生成包含跨域用户标识和第二域名的跨域跳转请求，并将跨域跳转请求发送给浏览器。进一步的，浏览器将跨域跳转请求转发给第二域名服务器。
步骤S206，第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识。
步骤S208，第二域名服务器获取与跨域用户标识对应的用户在第二域名中的第二身份标识，根据第二身份标识生成用户在第二域名中的用户登录状态。
如图3所示，在一个实施例中，一种实现跨域跳转的方法，包括以下步骤：
步骤S302，浏览器获取从第一域名跳转到第二域名的请求，根据第二域名和第一身份标识生成跨域用户标识。
在一个实施例中，浏览器根据第二域名和第一身份标识生成跨域用户标识的具体过程为：浏览器查找与第二域名对应的注册标识和第二域名密钥，将注册标识和第一身份标识进行组合；浏览器根据第二域名密钥对组合后的标识进行加密处理，生成跨域用户标识。
具体的，在一个实施例中，在浏览器向第一域名服务器请求网页资源时，第一域名服务器即可在网页资源中嵌入网页资源中包含的第二域名的注册标识和第二域名密钥，并在网页资源中嵌入根据第二域名和第一身份标识生成跨域用户标识的程序，将网页资源下发给浏览器。
进一步的，当第一域名网页中的第二域名的链接被点击后，浏览器可执行预先嵌入网页资源中的可根据第二域名和第一身份标识生成跨域用户标识的程序，得到跨域用户标识。
步骤S304，浏览器根据跨域用户标识和第二域名生成跨域跳转请求，将跨域跳转请求发送给第二域名服务器。
具体的，浏览器可生成包含跨域用户标识和第二域名的从第一域名跳转到第二域名的跨域跳转请求，将跨域跳转请求发送给第二域名服务器。
步骤S306，第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识。
步骤S308，第二域名服务器获取与跨域用户标识对应的用户在第二域名中的第二身份标识，根据第二身份标识生成用户在第二域名中的用户登录状态。
在一个实施例中，上述实现跨域跳转的方法还包括步骤：第二域名服务器将与跨域跳转请求对应的网页资源和与第二身份标识对应的用户身份信息返回至浏览器；浏览器显示网页资源对应的网页，并在网页中显示与第二身份标识对应的用户身份信息。
具体的，浏览器可在网页的相应位置显示与第二身份标识对应的用户身份信息，例如用户名称或用户昵称等，以表示用户已经登录第二域名。
在一个实施例中，上述实现跨域跳转的方法还包括步骤：浏览器存储第二身份标识至预设目录下用于保存第二域名的已登录用户信息的文件中。
具体的，浏览器可按照预设的格式加密第二身份标识，进一步的，可将加密后的第二身份标识保存至预设目录下用于保存第二域名的已登录用户信息的文件中。第二域名的已登录用户信息可用于辨识在第二域名网页上进行操作的用户的身份。
下面用一个具体的场景实例来说明上述实现跨域跳转的方法。如图4所示：
（1）浏览器发送登录第一域名的登录请求至第一域名服务器。
（2）第一域名服务器验证登录请求，向用户浏览器返回用户的登录请求验证通过的信息以及第一域名的网页资源。
（3）浏览器获取用户从第一域名跳转到第二域名的请求，获取用户在第一域名中的第一身份标识，发送包含第二域名以及第一身份标识的处理请求至第一域名服务器。
（4）第一域名服务器接收处理请求，根据第二域名和第一身份标识生成用户的跨域用户标识，并生成包含跨域用户标识的从第一域名跳转到第二域名的跨域跳转请求，将跨域跳转请求发送至浏览器。
（5）浏览器将跨域跳转请求发送至第二域名服务器。
（6）第二域名服务器解析跨域跳转请求，提取跨域用户标识，根据跨域用户标识生成用户在第二域名中的第二身份标识，根据第二身份标识生成用户在第二域名中的用户登录状态，进一步获取第二域名对应的网页资源。
（7）第二域名服务器将与跨域跳转请求对应的网页资源以及第二身份标识发送给浏览器。
如图5所示，在一个实施例中，一种浏览器10，包括请求获取模块102、浏览器发送模块104和浏览器接收模块106，其中：
请求获取模块102用于获取从第一域名跳转到第二域名的请求。
在一个实施例中，在第一域名的网页中的第二域名的链接被点击后，将触发从第一域名跳转到第二域名的请求。
浏览器发送模块104用于将第二域名和用户在第一域名中的第一身份标识发送至第一域名服务器。
在一个实施例中，用户在第一域名中的第一身份标识为用户登录第一域名输入的用户名称或用户账号或用户登录第一域名后为用户分配的标识号等。
在一个实施例中，浏览器10获取用户对第一域名的登录请求，登录请求中包含用户在第一域名中的第一身份标识（如用户名称或用户账号）和用户密码；浏览器10将登录请求发送给第一域名服务器；第一域名服务器验证登录请求，并将验证结果发送给浏览器10；若浏览器10接收到验证通过的结果，则生成用于保存第一域名的已登录用户信息的文件并在文件中写入第一身份标识，进一步将该文件保存至预设目录下。第一域名的已登录用户信息可用于辨识在第一域名的网页上进行操作的用户的身份。
进一步的，当在第一域名的网页中的第二域名的链接被点击后，浏览器10从预设目录下用于保存第一域名的已登录用户信息的文件中读取用户在第一域名中的第一身份标识，进一步的，将第二域名和读取的第一身份标识发送至第一域名服务器。
浏览器接收模块106用于接收第一域名服务器发送的根据第二域名和第一身份标识生成的跨域用户标识，该跨域用户标识与用户在第二域名中的第二身份标识相对应。
具体的，第二域名服务器可根据第二域名和第一身份标识生成的跨域用户标识，并将生成的跨域用户标识发送给浏览器10。
浏览器发送模块104还用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器，该跨域跳转请求中包含跨域用户标识。
在一个实施例中，浏览器10还包括跨域请求生成模块（图中未示出），用于根据跨域用户标识和第二域名生成跨域跳转请求。具体的，跨域请求生成模块可生成包含跨域用户标识和第二域名的从第一域名跳转到第二域名的跨域跳转请求。
在一个实施例中，浏览器接收模块106还用于接收第二域名服务器发送的与跨域跳转请求对应的网页资源和第二身份标识对应用户身份信息。
在一个实施例中，浏览器10还包括显示模块（图中未示出），用于显示网页资源对应的网页，并在网页中显示与第二身份标识对应的用户身份信息。
具体的，显示模块可在网页的相应位置显示与第二身份标识对应的用户身份信息，例如用户名称或用户昵称等，以表示用户已经登录第二域名。
在一个实施例中，浏览器10还包括身份标识保存模块（图中未示出），用于保存第二身份标识至预设目录下用于保存第二域名的已登录用户信息的文件中。
具体的，身份标识保存模块可按照预设的格式加密第二身份标识，进一步的，可将加密后的第二身份标识保存至预设目录下用于保存第二域名的已登录用户信息的文件中。第二域名的已登录用户信息可用于辨识在第二域名网页上进行操作的用户的身份。
上述浏览器10，获取到从第一域名跳转至第二域名的请求后，从第一域名服务器接收根据第二域名和第一身份标识生成的跨域用户标识，并且将包含跨域用户标识的跨域跳转请求发送至第二域名服务器，而该跨域用户标识又与用户在第二域名中的第二身份标识相对应，因此，不需要再重新登录，依然可保持用户登录状态，减少了跨域跳转后用户在终端操作的时间，节省了电量，特别是对电量有限的移动终端来说，能提高续航时间。
如图6所示，在一个实施例中，一种第一域名服务器20，包括第一接收模块202、跨域标识生成模块204和第一发送模块206，其中：
第一接收模块202用于接收浏览器发送的第二域名和用户在第一域名中的第一身份标识。
跨域标识生成模块204用于根据第二域名和第一身份标识生成跨域用户标识，该跨域用户标识与用户在第二域名中的第二身份标识相对应。
在一个实施例中，跨域标识生成模块204用于查找与第二域名对应的注册标识和第二域名密钥，将注册标识和第一身份标识进行组合，根据第二域名密钥对组合后的标识进行加密处理，生成跨域用户标识。
具体的，第二域名可预先在第一域名中进行注册，第一域名服务器20可预先存储第二域名的注册标识（可称为appid）以及第二域名的第二域名密钥（可称为appkey）。
第一发送模块206用于将跨域用户标识发送至浏览器。
在另一个实施例中，第一域名20还包括跨域请求生成模块（图中未示出），用于生成包含跨域用户标识和第二域名的跨域跳转请求。本实施例中，第一发送模块206用于将跨域跳转请求发送至浏览器。
上述第一域名服务器20，接收到浏览器发送的第二域名和用户在第一域名中的第一身份标识后，根据第二域名和第一身份标识生成跨域用户标识，且生成的跨域用户标识与用户在第二域名中的第二身份标识相对应，并将跨域用户标识发送至浏览器，使得浏览器在向第二域名请求网页资源时，可将标识用户在第二域名中的第二身份标识的跨域用户标识发送给第二域名浏览器，不需要用户登录第二域名，依然可保持用户的登录状态。
如图7所示，在一个实施例中，一种第二域名服务器30，包括第二接收模块302、第二身份标识获取模块304和登录状态生成模块306，其中：
第二接收模块302用于接收浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，该跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识。
第二身份标识获取模块304用于获取与跨域用户标识对应的用户在第二域名中的第二身份标识。
在一个实施例中，第二身份标识获取模块304可按照预设的方式解析跨域跳转请求，从跨域跳转请求中提取出跨域用户标识，将跨域用户标识进行解密，得到解密后的跨域用户标识，检查解密后的跨域用户标识的合法性，并查找与解密后的跨域用户标识对应的用户在第二域名中的第二身份标识。
在一个实施例中，第二域名服务器可预先存储合法的跨域用户标识，第二身份标识获取模块304可在预先存储的合法的跨域用户标识中查找解密后的跨域用户标识，若查找成功，则解密后的跨域用户标识是合法的，若查找失败，则解密后的跨域用户标识是不合法的。
登录状态生成模块306用于根据第二身份标识生成用户在第二域名中的用户登录状态。
在一个实施例中，登录状态生成模块306可在第二域名的用户登录状态数据库中标记第二身份标识的用户登录状态为已经登录。
如图8所示，在一个实施例中，第二域名服务器30还包括：
信息返回模块308，用于将与跨域跳转请求对应的网页资源和与第二身份标识对应的用户身份信息返回至浏览器。
上述第二域名服务器30，从浏览器接收的跨域跳转请求中包含了跨域用户标识，并根据跨域用户标识生成用户在第二域名中的第二身份标识，根据第二身份辨识用户身份，不需要用户登录第二域名，依然可保持用户的登录状态。
如图9所示，一种实现跨域跳转的系统，包括上述任一实施例中的浏览器10、第一域名服务器20和第二域名服务器30，浏览器10包括如图5所示的请求获取模块102、浏览器发送模块104和浏览器接收模块106，第一域名服务器20包括如图6所示的第一接收模块202、跨域标识生成模块204和第一发送模块206，第二域名服务器包括如图7所示的第二接收模块302、第二身份标识获取模块304和登录状态生成模块306，其中：
请求获取模块102，用于获取从第一域名跳转到第二域名的请求。
浏览器发送模块104，用于将第二域名和用户在第一域名中的第一身份标识发送至第一域名服务器20。
第一接收模块202，用于接收浏览器10发送的第二域名和用户在第一域名中的第一身份标识。
跨域标识生成模块204，用于根据第二域名和第一身份标识生成跨域用户标识。
第一发送模块206，用于将跨域用户标识发送至浏览器10。
浏览器接收模块106，用于接收第一域名服务器20发送的跨域用户标识。
浏览器发送模块104还用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器30，该跨域跳转请求中包含跨域用户标识。
第二接收模块302，用于接收浏览器10发送的从第一域名跳转到第二域名的跨域跳转请求。
第二身份标识获取模块304，用于获取与跨域用户标识对应的用户在第二域名中的第二身份标识。
登录状态生成模块306，用于根据第二身份标识生成用户在第二域名中的用户登录状态。
如图10所示，在一个实施例中，一种浏览器40，包括请求获取单元402、跨域标识生成单元404和浏览器发送单元406，其中：
请求获取单元402，用于获取从第一域名跳转到第二域名的请求。
跨域标识生成单元404，用于根据第二域名和用户在第一域名中的第一身份标识生成跨域用户标识，该跨域用户标识与用户在第二域名中的第二身份标识相对应。
在一个实施例中，跨域标识生成单元404用于查找与第二域名对应的注册标识和第二域名密钥，将注册标识和第一身份标识进行组合，根据第二域名密钥对组合后的标识进行加密处理，生成跨域用户标识。
具体的，在一个实施例中，在浏览器向第一域名服务器请求网页资源时，第一域名服务器即可在网页资源中嵌入网页资源中包含的第二域名的注册标识和第二域名密钥，并在网页资源中嵌入根据第二域名和第一身份标识生成跨域用户标识的程序，将网页资源下发给浏览器。当第一域名网页中的第二域名的链接被点击后，跨域标识生成单元404可执行预先嵌入网页资源中的可根据第二域名和第一身份标识生成跨域用户标识的程序，生成跨域用户标识。
浏览器发送单元406，用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器，该跨域跳转请求中包含跨域用户标识。
如图11所示，在一个实施例中，浏览器40还包括：
浏览器接收单元408，用于接收第二域名服务器发送的与跨域跳转请求对应的网页资源和与第二身份标识对应的用户身份信息。
在一个实施例中，浏览器40还包括显示模块（图中未示出），用于显示网页资源对应的网页，并在网页中显示与第二身份标识对应的用户身份信息。
上述浏览器40，获取到从第一域名跳转至第二域名的请求后，根据第二域名和第一身份标识生成的跨域用户标识，并且将包含跨域用户标识的跨域跳转请求发送至第二域名服务器，而该跨域用户标识又与用户在第二域名中的第二身份标识相对应，因此，不需要再重新登录，依然可保持用户登录状态，减少了跨域跳转后用户在终端操作的时间，节省了电量，特别是对电量有限的移动终端来说，能提高续航时间。
如图12所示，在一个实施例中，一种实现跨域跳转的系统，包括上述任一实施例中的浏览器40和第二域名服务器30，浏览器40包括如图10所示的请求获取单元402、跨域标识生成单元404和浏览器发送单元406，第二域名服务器包括如图7所示的第二接收模块302、第二身份标识获取模块304和登录状态生成模块306，其中：
请求获取单元402，用于获取从第一域名跳转到第二域名的请求。
跨域标识生成单元404，用于根据第二域名和用户在第一域名中的第一身份标识生成跨域用户标识，该跨域用户标识与用户在第二域名中的第二身份标识相对应。
浏览器发送单元406，用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器20，跨域跳转请求中包含跨域用户标识。
第二接收模块302，用于接收浏览器40发送的从第一域名跳转到第二域名的跨域跳转请求。
第二身份标识获取模块304，用于获取与跨域用户标识对应的用户在第二域名中的第二身份标识。
登录状态生成模块306，用于根据第二身份标识生成用户在第二域名中的用户登录状态。
上述实现跨域跳转的方法和系统，从第一域名跳转到第二域名的跨域跳转请求中包含了与用户在第一域名中的第一身份标识对应的跨域用户标识，第二域名服务器可根据跨域用户标识生成用户在第二域名中的第二身份标识，并根据第二身份标识辨识出用户的身份，从而用户在从第一域名跳转到第二域名时不需要再重新登录，依然可保持用户登录状态，减少了跨域跳转后用户在终端操作的时间，节省了电量，特别是对电量有限的移动终端来说，能提高续航时间。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory，ROM）或随机存储记忆体（Random Access Memory，RAM）等。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。

Claims (17)

  1. 一种实现跨域跳转的方法，包括以下步骤：
    第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，所述跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识；
    第二域名服务器获取与所述跨域用户标识对应的用户在第二域名中的第二身份标识，根据所述第二身份标识生成用户在第二域名中的用户登录状态。
  2. 根据权利要求1所述的实现跨域跳转的方法，其特征在于，在所述第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求之前，所述方法还包括：
    第一域名服务器获取浏览器发送的从第一域名跳转到第二域名的请求，所述请求中包含第二域名和所述用户在第一域名中的第一身份标识；
    第一域名服务器根据所述第二域名和第一身份标识生成所述跨域用户标识，将所述跨域用户标识返回至浏览器。
  3. 根据权利要求2所述的实现跨域跳转的方法，其特征在于，所述第一域名服务器根据所述第二域名和第一身份标识生成所述跨域用户标识的步骤为：
    所述第一域名服务器查找与所述第二域名对应的注册标识和第二域名密钥，将所述注册标识和第一身份标识进行组合；
    所述第一域名服务器根据所述第二域名密钥对所述组合后的标识进行加密处理，生成所述跨域用户标识。
  4. 根据权利要求1所述的实现跨域跳转的方法，其特征在于，在所述第二域名服务器获取浏览器发送的从第一域名跳转到第二域名的跨域跳转请求的步骤之前，所述方法还包括：
    浏览器获取从第一域名跳转到第二域名的请求，根据所述第二域名和所述第一身份标识生成所述跨域用户标识；
    所述浏览器根据所述跨域用户标识和第二域名生成所述跨域跳转请求，将所述跨域跳转请求发送给第二域名服务器。
  5. 根据权利要求4所述的实现跨域跳转的方法，其特征在于，所述浏览器根据所述第二域名和第一身份标识生成所述跨域用户标识的步骤为：
    所述浏览器查找与所述第二域名对应的注册标识和第二域名密钥，将所述注册标识和第一身份标识进行组合；
    所述浏览器根据所述第二域名密钥对所述组合后的标识进行加密处理，生成所述跨域用户标识。
  6. 根据权利要求3或5所述的实现跨域跳转的方法，其特征在于，所述第二域名服务器获取与所述跨域用户标识对应的用户在第二域名中的第二身份标识的步骤为：
    从所述跨域跳转请求中提取出所述跨域用户标识，将所述跨域用户标识进行解密，得到解密后的跨域用户标识，检查解密后的跨域用户标识的合法性，并查找与解密后的跨域用户标识对应的所述用户在第二域名中的第二身份标识。
  7. 根据权利要求1所述的实现跨域跳转的方法，其特征在于，所述方法还包括：
    第二域名服务器将与所述跨域跳转请求对应的网页资源和与所述第二身份标识对应的用户身份信息返回至浏览器；
    所述浏览器显示所述网页资源对应的网页，并在所述网页中显示与所述第二身份标识对应的用户身份信息。
  8. 一种浏览器，其特征在于，包括：
    请求获取模块，用于获取从第一域名跳转到第二域名的请求；
    浏览器发送模块，用于将所述第二域名和用户在第一域名中的第一身份标识发送至第一域名服务器；
    浏览器接收模块，用于接收第一域名服务器发送的根据所述第二域名和第一身份标识生成的跨域用户标识，所述跨域用户标识与用户在第二域名中的第二身份标识相对应；
    所述浏览器发送模块还用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器，所述跨域跳转请求中包含所述跨域用户标识。
  9. 根据权利要求8所述的浏览器，其特征在于，所述浏览器还包括：
    显示模块，用于接收所述第二域名服务器返回的与所述跨域跳转请求对应的网页资源和与所述第二身份标识对应的用户身份信息，显示所述网页资源对应的网页，并在所述网页中显示与所述用户身份信息。
  10. 一种第一域名服务器，其特征在于，包括：
    第一接收模块，用于接收浏览器发送的第二域名和用户在第一域名中的第一身份标识；
    跨域标识生成模块，用于根据所述第二域名和第一身份标识生成跨域用户标识，所述跨域用户标识与用户在第二域名中的第二身份标识相对应；
    第一发送模块，用于将所述跨域用户标识发送至所述浏览器。
  11. 根据权利要求10所述的第一域名服务器，其特征在于，所述跨域标识生成模块用于查找与所述第二域名对应的注册标识和第二域名密钥，将所述注册标识和第一身份标识进行组合，根据所述第二域名密钥对所述组合后的标识进行加密处理，生成所述跨域用户标识。
  12. 一种第二域名服务器，其特征在于，包括：
    第二接收模块，用于接收浏览器发送的从第一域名跳转到第二域名的跨域跳转请求，所述跨域跳转请求中包含与用户在第一域名中的第一身份标识对应的跨域用户标识；
    第二身份标识获取模块，用于生成与所述跨域用户标识对应的用户在第二域名中的第二身份标识；
    登录状态生成模块，用于根据所述第二身份标识生成用户在第二域名中的用户登录状态。
  13. 根据权利要求12所述的第二域名服务器，其特征在于，所述第二身份标识获取模块用于从所述跨域跳转请求中提取出所述跨域用户标识，将所述跨域用户标识进行解密，得到解密后的跨域用户标识，检查解密后的跨域用户标识的合法性，并查找与解密后的跨域用户标识对应的用户在第二域名中的第二身份标识。
  14. 根据权利要求12或13所述的第二域名服务器，其特征在于，还包括：
    信息返回模块，用于将与所述跨域跳转请求对应的网页资源和与所述第二身份标识对应的用户身份信息返回至浏览器。
  15. 一种浏览器，其特征在于，包括：
    请求获取单元，用于获取从第一域名跳转到第二域名的请求；
    跨域标识生成单元，用于根据所述第二域名和用户在第一域名中的第一身份标识生成跨域用户标识，所述跨域用户标识与用户在第二域名中的第二身份标识相对应；
    浏览器发送单元，用于发送从第一域名跳转到第二域名的跨域跳转请求至第二域名服务器，所述跨域跳转请求中包含所述跨域用户标识。
  16. 根据权利要求15所述的浏览器，其特征在于，所述跨域标识生成单元用于查找与所述第二域名对应的注册标识和第二域名密钥，将所述注册标识和第一身份标识进行组合，根据所述第二域名密钥对所述组合后的标识进行加密处理，生成所述跨域用户标识。
  17. 根据权利要求15所述的浏览器，其特征在于，所述浏览器还包括：
    显示单元，用于接收所述第二域名服务器返回的与所述跨域跳转请求对应的网页资源和与所述第二身份标识对应的用户身份信息，显示所述网页资源对应的网页，并在所述网页中显示与所述用户身份信息。
PCT/CN2013/079124 2012-07-12 2013-07-10 实现跨域跳转的方法以及浏览器、域名服务器 WO2014008858A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP13817388.5A EP2874074B1 (en) 2012-07-12 2013-07-10 Method for implementing cross-domain jump, browser, and domain name server
RU2015104540/08A RU2595931C1 (ru) 2012-07-12 2013-07-10 Способ осуществления междоменного перехода, браузер и сервер доменных имен
US14/594,705 US9686344B2 (en) 2012-07-12 2015-01-12 Method for implementing cross-domain jump, browser, and domain name server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210241298.6A CN103546432B (zh) 2012-07-12 2012-07-12 实现跨域跳转的方法和系统以及浏览器、域名服务器
CN201210241298.6 2012-07-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/594,705 Continuation US9686344B2 (en) 2012-07-12 2015-01-12 Method for implementing cross-domain jump, browser, and domain name server

Publications (1)

Publication Number Publication Date
WO2014008858A1 true WO2014008858A1 (zh) 2014-01-16

Family

ID=49915417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/079124 WO2014008858A1 (zh) 2012-07-12 2013-07-10 实现跨域跳转的方法以及浏览器、域名服务器

Country Status (5)

Country Link
US (1) US9686344B2 (zh)
EP (1) EP2874074B1 (zh)
CN (1) CN103546432B (zh)
RU (1) RU2595931C1 (zh)
WO (1) WO2014008858A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9503501B2 (en) * 2012-09-17 2016-11-22 Salesforce.Com, Inc. Cross domain in-browser proxy
CN105472052B (zh) * 2014-09-03 2019-12-31 阿里巴巴集团控股有限公司 一种跨域服务器的登录方法和系统
CN105610855A (zh) * 2016-01-21 2016-05-25 北京京东尚科信息技术有限公司 一种跨域系统登录验证的方法和装置
CN107196892B (zh) * 2016-03-15 2020-03-06 阿里巴巴集团控股有限公司 一种网站登录方法和装置
CN107306296A (zh) * 2016-04-17 2017-10-31 王正伟 域名替代使用方法
CN105897746A (zh) * 2016-05-26 2016-08-24 深圳市金立通信设备有限公司 一种跨网站登录方法、终端及网站服务器
CN106060189B (zh) * 2016-07-08 2019-03-29 厦门纳网科技股份有限公司 一种分布式域名注册系统
CN106973037B (zh) * 2017-02-16 2018-09-04 咪咕视讯科技有限公司 一种控制数据传输的方法及系统
CN108574709B (zh) * 2017-03-10 2021-09-07 北京京东尚科信息技术有限公司 跨域操作的实现方法和装置
CN108632209A (zh) * 2017-03-20 2018-10-09 北京京东尚科信息技术有限公司 用于处理信息的系统、方法和装置
CN107909330B (zh) * 2017-08-31 2020-10-09 平安科技（深圳）有限公司 工作流数据处理方法、装置、存储介质和计算机设备
US10992612B2 (en) * 2018-11-12 2021-04-27 Salesforce.Com, Inc. Contact information extraction and identification
CN109918146A (zh) * 2019-02-02 2019-06-21 北京字节跳动网络技术有限公司 页面生成方法和装置
CN111931088B (zh) * 2020-10-13 2021-01-26 北京拓课网络科技有限公司 一种网页链接处理方法、装置和电子设备
CN112511491B (zh) * 2020-10-30 2022-12-06 福建福诺移动通信技术有限公司 一种在前后端分离模式下结合消息队列的单点登入方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003296277A (ja) * 2002-03-29 2003-10-17 Fuji Xerox Co Ltd ネットワーク装置、認証サーバ、ネットワークシステム、認証方法
CN101075875A (zh) * 2007-06-14 2007-11-21 中国电信股份有限公司 在门户/系统之间实现单点登录的方法及其系统
GB2452283A (en) * 2007-08-30 2009-03-04 Clickstream Technologies Plc Establishing a common ID in first and second domain
CN101540734A (zh) * 2008-03-21 2009-09-23 阿里巴巴集团控股有限公司 一种跨域名Cookie访问方法、系统及设备
CN100586066C (zh) * 2006-06-26 2010-01-27 北京金山软件有限公司 一种实现单点登录的系统及方法
US20110302631A1 (en) * 2010-06-07 2011-12-08 Salesforce.Com, Inc. Systems and methods for logging into an application on a second domain from a first domain in a multi-tenant database system environment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6119234A (en) * 1997-06-27 2000-09-12 Sun Microsystems, Inc. Method and apparatus for client-host communication over a computer network
US6629246B1 (en) * 1999-04-28 2003-09-30 Sun Microsystems, Inc. Single sign-on for a network system that includes multiple separately-controlled restricted access resources
CA2346231A1 (en) * 2000-05-08 2001-11-08 Internet Number Corporation Method and system for accessing information on a network using message aliasing functions having shadow callback functions
WO2002039237A2 (en) * 2000-11-09 2002-05-16 International Business Machines Corporation Method and system for web-based cross-domain single-sign-on authentication
CN1647070A (zh) * 2001-06-22 2005-07-27 诺萨·欧莫贵 用于知识检索、管理、交付和表示的系统和方法
US6993596B2 (en) * 2001-12-19 2006-01-31 International Business Machines Corporation System and method for user enrollment in an e-community
CN1855814A (zh) * 2005-04-29 2006-11-01 中国科学院计算机网络信息中心 一种安全的统一身份认证方案
CN1835438B (zh) * 2006-03-22 2011-07-27 阿里巴巴集团控股有限公司 一种在网站间实现单次登录的方法及网站
RU2413278C1 (ru) * 2009-05-27 2011-02-27 Общество с ограниченной ответственностью "МэйлАдмин" Способ отбора информации в сети интернет и использования этой информации в разделяемом веб-сайте и компьютерный сервер для реализации этого способа

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003296277A (ja) * 2002-03-29 2003-10-17 Fuji Xerox Co Ltd ネットワーク装置、認証サーバ、ネットワークシステム、認証方法
CN100586066C (zh) * 2006-06-26 2010-01-27 北京金山软件有限公司 一种实现单点登录的系统及方法
CN101075875A (zh) * 2007-06-14 2007-11-21 中国电信股份有限公司 在门户/系统之间实现单点登录的方法及其系统
GB2452283A (en) * 2007-08-30 2009-03-04 Clickstream Technologies Plc Establishing a common ID in first and second domain
CN101540734A (zh) * 2008-03-21 2009-09-23 阿里巴巴集团控股有限公司 一种跨域名Cookie访问方法、系统及设备
US20110302631A1 (en) * 2010-06-07 2011-12-08 Salesforce.Com, Inc. Systems and methods for logging into an application on a second domain from a first domain in a multi-tenant database system environment

Also Published As

Publication number Publication date
EP2874074A4 (en) 2016-03-09
EP2874074A1 (en) 2015-05-20
CN103546432B (zh) 2015-12-16
US20150127943A1 (en) 2015-05-07
RU2595931C1 (ru) 2016-08-27
CN103546432A (zh) 2014-01-29
EP2874074B1 (en) 2019-02-27
US9686344B2 (en) 2017-06-20

Similar Documents

Publication Publication Date Title
WO2014008858A1 (zh) 实现跨域跳转的方法以及浏览器、域名服务器
WO2016169410A1 (zh) 登录方法、服务器和登录系统
WO2020147383A1 (zh) 基于区块链系统的流程审批方法、装置、系统及非易失性存储介质
WO2019024126A1 (zh) 基于区块链的知识管理方法、终端及服务器
WO2020224246A1 (zh) 基于区块链的数据管理方法、装置、设备和存储介质
WO2019174090A1 (zh) 截屏文件分享的控制方法、装置、设备和计算机存储介质
WO2013159639A1 (zh) 显示微博话题的方法、终端、服务器、系统及存储介质
WO2013189230A1 (zh) 一种通过移动终端实现云搜索的方法
WO2020220413A1 (zh) 个人信息的零知识证明方法、系统及存储介质
WO2017071363A1 (zh) 密码的共享方法、密码的共享系统及终端设备
WO2018090481A1 (zh) 用于移动终端应用程序的数字证书验证方法及系统
WO2016101441A1 (zh) 一种进行文件同步的方法及系统
WO2020253120A1 (zh) 网页注册方法、系统、设备和计算机存储介质
WO2022102930A1 (ko) 브라우저 기반 보안 pin 인증을 이용한 did 시스템 및 그것의 제어방법
WO2015018243A1 (zh) 一种基于iOS设备的网页拦截方法和设备
WO2018233352A1 (zh) 数据传输方法、装置、终端以及计算机可读存储介质
WO2020186775A1 (zh) 业务数据提供方法、装置、设备及计算机可读存储介质
WO2013075613A1 (zh) 网络服务提供方法及装置
WO2021072881A1 (zh) 基于对象存储的请求处理方法、装置、设备及存储介质
WO2020141660A1 (en) Electronic apparatus managing data based on block chain and method for managing data
WO2015199271A1 (en) Method and system for sharing files over p2p
WO2020062644A1 (zh) Json劫持漏洞的检测方法、装置、设备及存储介质
WO2017111483A1 (ko) 생체 정보 기반 인증 장치, 이와 연동하는 제어 서버 및 어플리케이션 서버, 그리고 이들의 동작 방법
WO2017016272A1 (zh) 一种虚拟资源数据的处理方法、装置及系统
WO2012149717A1 (zh) 基于tcm或tpm的license动态管理方法、装置及系统

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: 13817388

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013817388

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2015104540

Country of ref document: RU

Kind code of ref document: A