Lightweight internet protocol encapsulation (LIPE) scheme for multimedia traffic transport
First Claim
Patent Images
1. A method for use in a packet server, the method comprising the steps of:
- receiving a number of incoming data packets;
formatting a multiplexing header for each incoming data packet, wherein the formatted multiplexing header includes a user identifier field, a length indicator field, a more packets field, a class of service field, and a sequence number field; and
multiplexing the formatted multiplexing headers and their associated incoming data packets into a single transport session.
11 Assignments
0 Petitions
Accused Products
Abstract
A packet encapsulation scheme for multiplexing application sessions—Lightweight IP Encapsulation (LIPE)—is described. An LIPE packet comprises at least one multiplexing header (NH) and associated multimedia data packet (MDP). The LIPE packet uses UDP/IP as transport. An MH field further comprises a 16-bit a user identifier (UID) field, an 11 bit length indicator (LNG) field, a 1 bit “more” (M) field and an optional payload type/class of service (PT/CoS) field comprising 8 bits.
-
Citations
19 Claims
-
1. A method for use in a packet server, the method comprising the steps of:
-
receiving a number of incoming data packets; formatting a multiplexing header for each incoming data packet, wherein the formatted multiplexing header includes a user identifier field, a length indicator field, a more packets field, a class of service field, and a sequence number field; and multiplexing the formatted multiplexing headers and their associated incoming data packets into a single transport session. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method for use in a packet server, the method comprising the steps of:
-
receiving a number of incoming data streams from a plurality of users; formatting the incoming data packets into user datagram (UDP)/Internet Protocol (IP) packets such that each UDP/IP packet encapsulates at least a UDP header, an IP header and a formatted multiplexing header, wherein the formatted multiplexing header portion includes information for identifying an application associated with the payload, a user identifier field, a length indicator field, a more packets field, and a class of service field, where the more packets field is used to indicate the association of more than one data packet for the application. - View Dependent Claims (9, 10)
-
-
11. A method for use in a packet server, the method comprising the steps of:
-
receiving a number of incoming LIPE packets associated with at least one of different applications and a plurality of users; and formatting each of the incoming LIPE packets into user datagram (UDP)/Internet Protocol (IP) packets such that each UDP/IP packet encapsulates at least a UDP header, an IP header, a formatted multiplexing header and a payload portion, wherein the formatted multiplexing header portion includes information for identifying the different applications, a user identifier field, a length indicator field, a more packets field, and a class of service field, where the more packets field is used to indicate the association of more than one data packet for an application. - View Dependent Claims (12, 13)
-
-
14. An improved apparatus for transporting packets, the improved apparatus comprising:
-
a reception unit adapted to receive a number of incoming data packets; an analysis unit adapted to analyze multiplexing header information associated with each incoming data packet; a formatting unit adapted to format a multiplexing header for each incoming data packet utilizing the analyzed multiplexing header information; wherein the formatted multiplexing header includes a user identifier field, and length indicator field, a more packets field, a class of service field and a sequence number field, wherein the more packets field is used to indicate the use of more than one multiplexing header and associated data packet for transporting incoming data packets; and a modulator unit adapted to multiplex the incoming data packets into a single transport session. - View Dependent Claims (15, 16, 17, 18, 19)
-
Specification