Session identifier for a communication session

US10862863B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10862863-B2
Application numberUS-201816017992-A
CountryUS
Kind codeB2
Filing dateJun 25, 2018
Priority dateJun 25, 2015
Publication dateDec 8, 2020
Grant dateDec 8, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques for a session identifier for a communication session are described. According to various implementations, a session identifier that is usable for initiating a communication session is allocated prior to the communication session being initiated. The session identifier can then be activated to enable the session identifier to be used for routing data packets of a communication session.

First claim

Opening claim text (preview).

What is claimed is: 1. A system comprising: one or more processors; and one or more computer-readable storage media storing instructions that are executable by the one or more processors to perform operations including: receiving an allocation request from a first device, the allocation request including a network address of the first device; determining, for the allocation request, a session identifier associated with the network address of the first device, said determining occurring prior to an initiation of a communication session involving the first device; communicating a response to the first device including the session identifier; receiving an activation request including the session identifier and a transport address for the first device; activating the session identifier by associating the session identifier with the transport address; receiving, from a second device and as part of the communication session, a data packet that includes the session identifier; and communicating the data packet to the transport address for the first device. 2. A system as described in claim 1 , wherein the allocation request includes a service quality attribute, and wherein the operations further include determining a port identifier based on the service quality attribute, wherein the response to the first device further includes the port identifier. 3. A system as described in claim 1 , wherein the allocation request includes a modality type, and wherein the operations further include determining a port identifier based on the modality type, wherein the response to the first device further includes the port identifier. 4. A system as described in claim 1 , wherein the operations further include: determining a port to be allocated for the session identifier, and including a port identifier for the port with the response to the first device; and causing data packets of the communication session to be multiplexed over the port with data packets of a different communication session. 5. A system as described in claim 1 , wherein the system comprises a server, and wherein the response to the first device further includes a network address of the server. 6. A system as described in claim 1 , wherein the operations further comprise, prior to communicating the response, validating that the allocation request is associated with a valid user identifier. 7. A system as described in claim 1 , wherein the operations further comprise, prior to communicating the response, validating that the allocation request does not exceed a cap on a number of session identifiers allocated to a particular user identifier. 8. A system as described in claim 1 , wherein the operations further comprise, subsequent to said communicating the response to the first device, maintaining the session identifier in an inactive state until said receiving the activation request. 9. A method comprising: receiving an allocation request from a first device, the allocation request including a network address of the first device; determining, for the allocation request, a session identifier associated with the network address of the first device, said determining occurring prior to an initiation of a communication session involving the first device; communicating a response to the first device including the session identifier; receiving an activation request including the session identifier and a transport address for the first device; activating the session identifier by associating the session identifier with the transport address; receiving, from a second device and as part of the communication session, a data packet that includes the session identifier; and communicating the data packet to the transport address for the first device. 10. A method as recited in claim 9 , wherein the allocation request includes a service quality attribute, and wherein the method further comprises determining a port identifier based on the service quality attribute, wherein the response to the first device further includes the port identifier. 11. A method as recited in claim 9 , wherein the allocation request includes a modality type, and wherein the method further comprises determining a port identifier based on the modality type, wherein the response to the first device further includes the port identifier. 12. A method as recited in claim 9 , further comprising: determining a port to be allocated for the session identifier, and including a port identifier for the port with the response to the first device; and causing data packets of the communication session to be multiplexed over the port with data packets of a different communication session. 13. A method as recited in claim 9 , wherein the allocation request includes a modality type, and wherein the method further comprises: determining a port identifier for a port based on the modality type, wherein the response to the first device further includes the port identifier; and causing data packets of the modality type from the communication session to be multiplexed over the port with data packets of the modality type from a different communication session. 14. A method as recited in claim 9 , further comprising, prior to communicating the response, validating that the allocation request does not exceed a cap on a number of session identifiers allocated to a particular user identifier. 15. A method as recited in claim 9 , further comprising, subsequent to said communicating the response to the first device, maintaining the session identifier in an inactive state until said receiving the activation request. 16. One or more computer-readable storage devices storing instructions that are executable to perform operations comprising: receiving an allocation request from a first device, the allocation request including a network address of the first device; determining, for the allocation request, a session identifier associated with the network address of the first device, said determining occurring prior to an initiation of a communication session involving the first device; communicating a response to the first device including the session identifier; receiving an activation request including the session identifier and a transport address for the first device; activating the session identifier by associating the session identifier with the transport address; receiving, from a second device and as part of the communication session, a data packet that includes the session identifier; and communicating the data packet to the transport address for the first device. 17. One or more computer-readable storage devices as described in claim 16 , wherein the allocation request includes a service quality attribute, and wherein the operations further comprise determining a port identifier based on the service quality attribute, wherein the response to the first device further includes the port identifier. 18. One or more computer-readable storage devices as described in claim 16 , wherein the allocation request includes a modality type, and wherein the operations further comprise determining a port identifier based on the modality type, wherein the response to the first device further includes the port identifier. 19. One or more computer-readable storage devices as described in claim 16 , wherein the operations further comprise: determining a port to be allocated for the session identifier, and including a port identifier for the port with the response to the first device; and causing data packets of the communication session to b

Assignees

Inventors

Classifications

  • Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports · CPC title

  • Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title

  • Network streaming of media packets · CPC title

  • Session establishment or de-establishment · CPC title

  • over a relay server, e.g. traversal using relay for network address translation [TURN] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10862863B2 cover?
Techniques for a session identifier for a communication session are described. According to various implementations, a session identifier that is usable for initiating a communication session is allocated prior to the communication session being initiated. The session identifier can then be activated to enable the session identifier to be used for routing data packets of a communication session.
Who is the assignee on this patent?
Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification H04L65/1069. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Dec 08 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).