Multiplexing different types of data sequences

• US 20040062276A1
• Filed: 09/30/2002
• Published: 04/01/2004
• Est. Priority Date: 09/30/2002
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: ArrayComm LLC (Ygomi LLC)
• Inventors: Uhlik, Christopher R., Chrabieh, Rabih, Dahlby, Douglas C.
• Granted Patent: US 7,352,774 B2
• Time in Patent Office: Days
• US Class Current: 370/474
• CPC Class Codes: H04L 1/0083 Formatting with frames or packets; Protocol or part of protocol for error control
• CPC Class Codes: H04L 1/18 Automatic repetition systems, e.g. Van Duuren systems
• CPC Class Codes: H04L 2001/0098 Unequal error protection
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04W 72/569 of the traffic information

Abstract

According to an embodiment of the invention, a method and apparatus are described for data bit sequences. According to an embodiment of the invention, a header is inserted in a data burst. One or more high priority messages of a first type are optionally inserted in the data burst starting after the header. One or more messages of a second type are optionally inserted into the data burst starting at an end of the data burst. One or more low priority messages of the first type are optionally inserted in the data.

Claims

1. A method comprising:

inserting a header in a data burst;

optionally inserting one or more high priority messages of a first type in the data burst starting after the header;

optionally inserting one or more messages of a second type into the data burst starting at an end of the data burst; and

optionally inserting one or more low priority messages of the first type in the data burst.

2. The method of claim 1, wherein the low priority messages of the first type are inserted in the data burst starting after the header and the high priority messages of the first type, if any.

3. The method of claim 1, wherein high priority messages of the first type and low priority messages of the first type are mixed together in the data burst.

4. The method of claim 1, further comprising transmitting the data burst over a transmission channel.

5. The method of claim 4, wherein the transmission channel comprises a timeslot and a frequency.

6. The method of claim 1, wherein the first type of message comprises unacknowledged mode traffic data.

7. The method of claim 6, wherein the first type of message comprises data traffic for which there is no automatic repeat request retransmission strategy.

8. The method of claim 1, wherein the second type of message comprises acknowledged mode traffic data.

9. The method of claim 8, wherein the second type of data comprises data traffic for which there is an automatic repeat request retransmission strategy.

10. The method of claim 1, wherein unallocated space in the data burst is filled with no operation codes.

11. The method of claim 1, wherein unallocated space in the data burst is filled with a no operation code and one or more random data bits.

12. The method of claim 1, wherein the one or more messages of the second type include a delineating code to indicate a beginning of messages of the second type.

13. The method of claim 1, wherein the header includes a type field.

14. The method of claim 13, wherein the type field indicates whether the message includes messages of the first type.

15. The method of claim 14, wherein the type field comprises two bits of data.

16. A method comprising:

reading a type field in a header of a data burst;

if the type field indicates that the data burst includes messages of a first type;

setting a bit position to the beginning of the messages of the first type;

examining each bit in the messages of the first type until a pre-defined message of the first type is matched;

resetting the bit position to a position after a matched pre-defined message, and

if the delineating code is matched, recovering the messages of a second type; and

if the type field indicates that the data burst does not include messages of the first type, recovering messages of the second type.

17. The method of claim 16, wherein the transmission channel comprises a timeslot and a frequency.

18. The method of claim 16, wherein the first type of message comprises unacknowledged mode traffic data.

19. The method of claim 18, wherein the first type of message comprises data traffic for which there is no automatic repeat request retransmission strategy.

20. The method of claim 16, wherein the second type of message comprises acknowledged mode traffic data.

21. The method of claim 20, wherein the second type of data comprises data traffic for which there is an automatic repeat request retransmission strategy.

22. The method of claim 16, wherein unallocated space in the data burst is filled with no operation codes.

23. The method of claim 16, wherein unallocated space in the data burst is filled with a no operation code and one or more random data bits.

24. The method of claim 16, wherein the one or more messages of the second type include a delineating code to indicate a beginning of messages of the second type.

25. A method comprising:

placing a header code in a data burst;

if there are one or more high priority messages of a first type to be transmitted in the data burst;

placing the high priority messages of the first type in the data burst, and

reserving space in the data burst for a delineating code, the delineating code indicating the beginning of messages of a second type;

if there are one or more messages of the second type to be transmitted in the data burst;

placing the messages of the second type in the data burst, and

if high priority messages of the first type have been inserted in the data burst, adding the delineating code to the beginning of the messages of the second type; and

if there are low priority messages of the second type to be transmitted in the data burst;

if messages of the second type have been inserted and a delineating code has not already been added, reserving space in the data burst for the delineating code,

inserting the low priority messages of the second type in the data burst, and

if messages of the first type and messages of the second type have been inserted in the data burst and a delineating code has not been added, adding the delineating code to the beginning of the messages of the first type.

26. The method of claim 25, wherein each message of the first type may be identified by parsing the data burst sequentially.

27. The method of claim 26, wherein each message of the first type forms a prefix code of arbitrary length.

28. The method of claim 25, wherein high priority messages of the first type are placed in the data burst after the header.

29. The method of claim 28, wherein messages of the second type are placed in the data burst beginning at an end of the data burst.

30. The method of claim 29, wherein:

if the data burst includes high priority messages of the first type, low priority messages of the first type follow the high priority messages of the first type; and

if the data burst does not include high priority messages of the first type, low priority messages of the first type follow the header.

31. The method of claim 28, wherein high priority messages of the first type and low priority messages of the first type are mixed together in the data burst.

32. The method of claim 25, further comprising inserting no operation codes in remaining available space of the data burst after messages have been inserted in the data burst.

33. The method of claim 25, further comprising inserting a no operation code and one or more random data bits in remaining available space of the data burst after messages have been inserted in the data burst.

34. The method of claim 25, further comprising transmitting the data burst over a single communication channel.

35. The method of claim 34, wherein the communication channel comprises a timeslot-frequency pair.

36. The method of claim 25, wherein the header comprises a type code.

37. The method of claim 36, wherein the type code indicates the types of messages that are included in the data burst.

38. The method of claim 37, further comprising recovering the messages included in the data burst.

39. The method of claim 38, wherein recovering the messages included in the data burst comprises:

if the type code indicates that messages of the first type are included in the data burst;

parsing the data burst sequentially to identify each message of the first type, and

after the messages of the first type have been recovered, recovering messages of the second type; and

if the type code indicates that messages of the first type are not included in the data burst, recovering the messages of the second type.

40. A signal comprising:

a header placed at a beginning of the signal;

one or more high priority messages of a first type placed after the header;

one or more messages of a second type placed at the end of the signal; and

one or more low priority messages of the first type placed after the one or more high priority messages of the first type.

41. The signal of claim 40, further comprising one or more no operation codes placed between the one or more low priority messages of the first type and the one or more messages of the second type.

42. The signal of claim 40, further comprising a no operation code and random data bits placed between the one or more low priority messages of the first type and the one or more messages of the second type.

43. The signal of claim 40, wherein the messages of the second type include a delineating code.

44. The signal of claim 40, wherein the header comprises a type field to indicate what types of messages are included in the signal.

45. The signal of claim 40, wherein each message of the first type is a predefined message.

46. The signal of claim 45, wherein each message of the first type forms a prefix code.

47. The signal of claim 46, wherein messages of the first type are of varying length.

48. The signal of claim 40, wherein each message of the first type comprises unacknowledged mode data.

49. The signal of claim 48, wherein each message of the second type comprises acknowledged mode data.

50. A radio unit comprising:

a processor to assemble a data burst, the data burst having;

a header placed at a beginning of the data burst,

one or more high priority messages of a first type placed after the header,

one or more messages of a second type placed at the end of the signal,

and one or more low priority messages of the first type placed after the header; and

a transmitter to send the data burst assembled by the processor.

51. The radio unit of claim 50, wherein the one more low priority messages of the first type are placed after the one or high priority messages of the first type.

52. The radio unit of claim 50, wherein the one more low priority messages of the first type are mixed with the one or high priority messages of the first type.

53. The radio unit of claim 50, wherein the first type of message comprises unacknowledged mode traffic data.

54. The radio unit of claim 53, wherein the first type of message comprises data traffic for which there is no automatic repeat request retransmission strategy.

55. The radio unit of claim 50, wherein the second type of message comprises acknowledged mode traffic data.

56. The radio unit of claim 55, wherein the second type of data comprises data traffic for which there is an automatic repeat request retransmission strategy.

57. The radio unit of claim 50, wherein unallocated space in the data burst is filled with no operation codes.

58. The radio unit of claim 50, wherein unallocated space in the data burst is filled with a no operation code and random data bits.

59. The radio unit of claim 50, wherein the one or more messages of the second type include a delineating code to indicate a beginning of messages of the second type.

60. The radio unit of claim 59, wherein the header includes a type field.

61. The radio unit of claim 60, wherein the type field indicates whether the message includes messages of the first type.

62. A data burst comprising:

a header placed at a beginning of the burst, the header indicating the types of messages in the burst;

a high priority message of a first type after the header;

a message of a second type at the end of the burst; and

a low priority message of the first type after the high priority message of the first type and before the message of the second type.

63. The data burst of claim 62, further comprising one or more no operation codes placed between the one or more low priority messages of the first type and the one or more messages of the second type.

64. The data burst of claim 62, further comprising a no operation code and one or more random data bits placed between the one or more low priority messages of the first type and the one or more messages of the second type.

65. The data burst of claim 62, wherein the messages of the second type include a delineating code.

66. The data burst of claim 62, wherein the header comprises a type field to indicate what types of messages are included in the signal.

67. The data burst of claim 62, wherein each message of the first type is a predefined message.

68. The data burst of claim 67, wherein each message of the first type forms a prefix code.

69. The data burst of claim 68, wherein messages of the first type are of varying length.

70. The data burst of claim 62, wherein each message of the first type comprises unacknowledged mode data.

71. The data burst of claim 70, wherein each message of the second type comprises acknowledged mode data.

72. A communications system comprising;

means for multiplexing one or messages comprising unacknowledged mode data and one or more messages comprising acknowledged mode data into a data burst;

means for transmitting the data burst over a communications channel;

means for receiving the data burst; and

means for recovering the one or more messages comprising unacknowledged mode data and the one or more messages comprising acknowledged mode data from the data burst.