DATA TYPE ENCODING FOR MEDIA INDEPENDENT HANDOVER

• US 20090047959A1
• Filed: 05/12/2008
• Published: 02/19/2009
• Est. Priority Date: 05/11/2007
• Status: Active Grant

• Current Assignee: Four Batons Wireless LLC (Two Gold Capital LLC)
• Original Assignee: Telcordia Technologies Incorporated (Telefonaktiebolaget LM Ericsson), Toshiba America Electronic Components Incorporated (Toshiba Corporation)
• Inventors: Taniuchi, Kenichi, Das, Subir, Oba, Yoshihiro, Tauil, Miriam, Cheng, Yuu-Heng Alice
• Granted Patent: US 9,526,040 B2
• Time in Patent Office: Days
• US Class Current: 455/436
• CPC Class Codes: H04W 36/0011 for data sessions of end-to-end connection
• CPC Class Codes: H04W 36/0019 adapted for mobile IP [MIP]
• CPC Class Codes: H04W 36/005 involving radio access media independent information, e.g. MIH [Media independent Hand-off]
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

A method of employing an encoding scheme for media independent handover, comprising: having at least some data type carry only required information to determine the end of data without a length value

Claims

1. A method of employing an encoding scheme for media independent handover, comprising:

having at least some data type carry only required information to determine the end of data without a length value.

2. The method of claim 1, wherein type is defined to determine length.

3. The method of claim 1, wherein said data types are carried in message exchanges between nodes performing an 802.21 media independent handover.

4. The method of claim 3, wherein said data types are used to define IEs.

5. The method of claim 4, further including transmitting said IEs from a mobile node.

6. The method of claim 3, wherein said data types are used to define TLVs.

7. The method of claim 4, further including transmitting said TLVs from a mobile node.

8. The method of claim 3, wherein said data types are used to define primitives.

9. The method of claim 8, wherein said primitives are transmitted between different layers of a protocol stack within the same node.

10. The method of claim 1, further including employing a binary encoding rule when the data types are carried in MIH protocol messages.

11. The method of claim 10, further including employing the following binary encoding rule related to a SEQUENCE data type:

DATATYPE1,DATATYPE2,[, . . . ] are encoded in the order of appearance, where each data type is encoded using the encoding rule for the data type.

12. The method of claim 10, further including employing the following binary encoding rule related to a CHOICE data type:

a one-octet selector field, followed by a variable length Value field, wherein the selector value determines the data type, and wherein if Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2,[, . . . ] is selected, and the Value field is encoded using the encoding the rule for the selected data type.

13. The method of claim 10, further including employing the following binary encoding rule related to a BITMAP data type:

each bit of a BITMAP(N) value [N=8*i, i=1, 2, . . . ] is encoded as an N/8-octet value in order of significance.

14. The method of claim 10, further including employing the following binary encoding rule related to a INTEGER data type:

each octet of an INTEGER(N) value [N=1, 2, . . . ] is encoded in network-byte order into an N-octet field.

15. The method of claim 10, further including employing the following binary encoding rule related to a CHAR data type:

each character is encoded in order of appearance where each bit of each character is encoded in order of significance.

16. The method of claim 10, further including employing the following binary encoding rule related to a UNSIGNED INTEGER data type:

each octet of an UNSIGNED_INT(N) value [N=1, 2, . . . ] is encoded in network-byte order into an N-octet field.

17. The method of claim 10, further including employing the following encoding is for a LIST(DATATYPE) data type:

a variable length Length field is followed by a variable length Value field, where the Length field value is in terms of number of list elements in the list.

18. The method of claim 17, further including that the format of the Length field is defined as follows:

if the actual number of list elements in the Value field is less than or equal to 127, then;

the Length field shall occupy one octet

the MSB of the Length field shall be set to 0, and

the other 7 bits of the Length field shall be used to indicate the actual length of the Value field in the number of list elements, and

if the number of list elements of the Value field is exactly 128, then;

the Length field shall occupy one octet

the MSB of the Length field shall be set to the value ‘

1’

, and

the other seven bits of the Length field shall all be set to the value ‘

0’

, and

if the number of list elements of the Value field is more than 127, then;

the Length field shall occupy more than one octet

the MSB of the first octet of the Length field shall be set to 1

the other 7 bits of the first octet of the Length field shall be used to indicate the number of additional octets of the Length field, and

the value of the remaining octets of the Length field,

when added to 128, shall be used to indicate the actual length of the Value field in number of list elements.

20. The method of claim 10, wherein at a top level, the order can be anything, while inside the top level, ordering restrictions are imposed.

19. A method, comprising:

having messages carry TLVs in which inside the TLVs, the data is encoded without using TLV style encoding.

21. A method of encoding a TLV data structure within an I.E.E.E. 802.21 message without values for at least one of Type, Length and Value.