Gtld domain name registries rdap architecture
US-2018083781-A1 · Mar 22, 2018 · US
US10320694B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10320694-B2 |
| Application number | US-201715586368-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 4, 2017 |
| Priority date | May 4, 2017 |
| Publication date | Jun 11, 2019 |
| Grant date | Jun 11, 2019 |
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.
An originating User Services Platform (USP) endpoint segments a payload representing a USP message into smaller segments (also referred to as “fragments” or “chunks”) for transmission of the payload through intermediate proxies having different message size constraints. Upon receipt, a receiving USP endpoint reassembles the smaller segments to recover the payload representing the USP message.
Opening claim text (preview).
What is claimed is: 1. An electronic device comprising: a memory storing computer-readable instructions; and one or more processors coupled to the memory, the one or more processors configured to execute the computer-readable instructions to process a User Services Platform message to generate a plurality of payload records, segment a payload record among the plurality of payload records to generate a plurality of payload record segments, generate a sequence of User Services Platform records including the plurality of payload record segments, a User Services Platform record in the sequence of User Services Platform records including (i) at least one payload record segment from among the plurality of payload record segments, (ii) a payload segmentation and reassembly state, and (iii) a payload record segmentation and reassembly state, set the payload segmentation and reassembly state for the User Services Platform record to one of begin, in-process or complete based on a position of the User Services Platform record in the sequence of User Services Platform records, and set the payload record segmentation and reassembly state for the User Services Platform record to one of begin, in-process or complete based on whether the User Services Platform record contains an initial one of the plurality of payload record segments, a final one of the plurality of payload record segments, or a payload record segment between the initial and final ones of the plurality of payload record segments; and a transceiver coupled to the one or more processors, the transceiver configured to transmit the sequence of User Services Platform records. 2. The electronic device of claim 1 , wherein a size of the User Services Platform record is based on a size of a non-payload portion of the User Services Platform record and a maximum transmission unit associated with a Message Transfer Protocol used to transmit the sequence of User Services Platform records. 3. The electronic device of claim 1 , wherein the payload segmentation and reassembly state indicates a state of segmentation of the User Services Platform message when the User Services Platform record was generated, and the payload record segmentation and reassembly state indicates a state of segmentation of the payload record when the User Services Platform record was generated. 4. The electronic device of claim 3 , wherein the User Services Platform record includes a Transport Layer Security entity. 5. The electronic device of claim 1 , wherein the User Services Platform record includes a single payload record segment, the single payload record segment corresponding to a single payload record representing the User Services Platform message. 6. The electronic device of claim 1 , wherein the User Services Platform message is one of unencrypted or encrypted with Concise Binary Object Representation (CBOR) Object Signing and Encryption (COSE). 7. The electronic device of claim 1 , wherein the User Services Platform message is one of unencrypted or encrypted with Concise Binary Object Representation (CBOR) Object Signing and Encryption (COSE). 8. The electronic device of claim 1 , wherein the User Services Platform record in the sequence of User Services Platform records further includes a session identifier indicating a session context for the sequence of User Service Platform records; a User Services Platform record sequence identifier; and an expected sequence identifier indicating a next sequence identifier expected to be received at the electronic device. 9. An electronic device, comprising: a transceiver configured to receive a sequence of a plurality of User Services Platform records, each User Services Platform record in the sequence of a plurality of User Services Platform records including (1) at least one payload record segment from among a plurality of payload record segments, the at least one payload record segment representing at least a portion of a User Services Platform message, (ii) a payload segmentation and reassembly state, and (iii) a payload record segmentation and reassembly state; wherein the payload segmentation and reassembly state is set to one of begin, in-process or complete based on a position of the User Services Platform record in the sequence of a plurality of User Services Platform records, and the payload record segmentation and reassembly state is set to one of begin, in-process or complete based on whether the User Services Platform record contains an initial one of the plurality of payload record segments, a final one of the plurality of payload record segments, or a payload record segment between the initial and final ones of the plurality of payload record segments, and one or more processors coupled to the transceiver, the one or more processors configured to execute computer-readable instructions to buffer received User Services Platform records in the sequence of a plurality of User Services Platform records, and recover the User Services Platform message by reassembling payload record segments included in the received User Services Platform records in the sequence of a plurality of User Services Platform records in response to receiving a User Services Platform record in the sequence of a plurality of User Services Platform records including a payload record segmentation and reassembly state set to complete. 10. The electronic device of claim 9 , wherein the payload segmentation and reassembly state included in a first User Services Platform record in the sequence of a plurality of User Services Platform records indicates a state of segmentation of the User Services Platform message when the first User Services Platform record was generated, and the payload record segmentation and reassembly state included in the first User Services Platform record indicates a state of segmentation of a payload record when the first User Services Platform record was generated. 11. The electronic device of claim 10 , wherein each User Services Platform record in the sequence of a plurality of User Services Platform records includes a Transport Layer Security entity. 12. The electronic device of claim 9 , wherein at least a first User Services Platform record in the sequence of a plurality of User Services Platform records includes a single payload record segment corresponding to a single payload record representing the User Services Platform message. 13. The electronic device of claim 9 , wherein each User Services Platform record further includes a session identifier indicating a session context for the sequence of a plurality of User Service Platform records; a User Services Platform record sequence identifier; and an expected sequence identifier indicating a next sequence identifier expected to be received at an electronic device from which the sequence of a plurality of User Services Platform records were transmitted.
by determining packet size, e.g. maximum transfer unit [MTU] · CPC title
specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title
based on packet size, e.g. shortest packet first · CPC title
Electricity · mapped topic
Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.