Method and apparatus for traffic probing
US-2024430168-A1 · Dec 26, 2024 · US
US9686344B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9686344-B2 |
| Application number | US-201514594705-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 12, 2015 |
| Priority date | Jul 12, 2012 |
| Publication date | Jun 20, 2017 |
| Grant date | Jun 20, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for implementing cross-domain jump includes: a second domain name server obtaining a cross-domain jump request of jumping from a first domain name to a second domain name sent by a browser, the request including a cross-domain user identifier corresponding to a first identifier of a user in the first domain name; the second domain name server obtaining a second identifier of the user in the second domain name corresponding to the user identifier, and generating a login state of the user in the second domain name according to the second identifier. The second domain name server recognizes identity of the user according to the second identifier, so that user does not need to log in while still maintaining the login state. Therefore, operation convenience of the user is improved. Further, a browser, a first domain name server and a second domain name server are provided.
Opening claim text (preview).
What is claimed is: 1. A method for implementing a cross-domain jump, comprising the following steps: obtaining, by a second domain name server, a cross-domain jump request of jumping from a first domain name to a second domain name sent by a browser, the cross-domain jump request comprising a cross-domain user identifier corresponding to a first identifier of a user in the first domain name; obtaining, by the second domain name server, a second identifier of the user in the second domain name corresponding to the cross-domain user identifier, and generating a user login state of the user in the second domain name according to the second identifier; and generating, by a first domain name server or the browser, the cross-domain user identifier according to the second domain name and the first identifier, comprising: finding, by the first domain name server or the browser, a registered identifier corresponding to the second domain name and a second domain name key corresponding to the second domain name, and combining the registered identifier with the first identifier to obtain a combined identifier; and encrypting, by the first domain name server or the browser, the combined identifier according to the second domain name key to generate the cross-domain user identifier. 2. The method for implementing the cross-domain jump of claim 1 , wherein before the step of obtaining, by the second domain name server, the cross-domain jump request of jumping from a first domain name to a second domain name sent by the browser, the method further comprises: obtaining, by the first domain name server, the request of jumping from the first domain name to the second domain name, the request comprising the second domain name and the first identifier of the user in the first domain name; and returning the cross-domain user identifier to the browser. 3. The method for implementing the cross-domain jump of claim 1 , wherein before the step of obtaining, by the second domain name server, the cross-domain jump request of jumping from the first domain name to the second domain name sent by the browser, the method further comprises: obtaining, by the browser, the request of jumping from the first domain name to the second domain name; generating, by the browser, the cross-domain jump request according to the cross-domain user identifier and the second domain name and sending the cross-domain jump request to the second domain name server. 4. The method for implementing cross-domain jump of claim 1 , wherein the step of obtaining, by the second domain name server, the second identifier of the user in the second domain name corresponding to the cross-domain user identifier comprises: extracting the cross-domain user identifier from the cross-domain jump request, decrypting the cross-domain user identifier to obtain a decrypted cross-domain user identifier, checking legality of the decrypted cross-domain user identifier and finding the second identifier of the user in the second domain name corresponding to the decrypted cross-domain user identifier. 5. The method for implementing cross-domain jump of claim 1 , further comprising: returning, by the second domain name server, web page sources corresponding to the cross-domain jump request and a user identify information corresponding to the second identifier to the browser; displaying, by the browser, a web page corresponding to the web page sources, and displaying the user identity information corresponding to the second identifier in the web page. 6. A first domain name server computing device, comprising: a storage device storing: a first receiving module configured to receive a second domain name and a first identifier of a user in a first domain name sent by a browser; a cross-domain identifier generating module configured to generate a cross-domain user identifier according to the second domain name and the first identifier, the cross-domain user identifier corresponding to a second identifier of the user in the second domain name; find a registered identifier corresponding to the second domain name and a second domain name key corresponding to the second domain name; combine the registered identifier with the first identifier to obtain a combined identifier; and encrypt the combined identifier according to the second domain name key to generate the cross-domain user identifier; and a first sending module configured to send the cross-domain user identifier to the browser. 7. A second domain name server computing device, comprising: a storage device storing: a second receiving module configured to receive a cross-domain jump request of jumping from a first domain name to a second domain name sent by a browser, the cross-domain jump request comprising a cross-domain user identifier corresponding to a first identifier of a user in the first domain name; a second identifier obtaining module configured to obtain a second identifier of the user in the second domain name corresponding to the cross-domain user identifier; and a login state generating module configured to generate a user login state of the user in the second domain name according to the second identifier, wherein the cross-domain user identifier is generated by encrypting a combined identifier according to a second domain name key corresponding to the second domain name, and the combined identifier is generated by combining a registered identifier corresponding to the second domain name with the first identifier. 8. The second domain name server computing device of claim 7 , wherein the second identifier obtaining module is configured to extract the cross-domain user identifier from the cross-domain jump request, decrypt the cross-domain user identifier to obtain a decrypted cross-domain user identifier, check legality of the decrypted cross-domain user identifier and find the second identifier of the user in the second domain name corresponding to the decrypted cross-domain user identifier. 9. The second domain name server computing device of claim 7 , further comprising: an information returning module configured to return web page sources corresponding to the cross-domain jump request and a user identity information corresponding to the second identifier to the browser.
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
Physics · mapped topic
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
providing single-sign-on or federations · CPC title
of access to content, e.g. by caching · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.