LANEscape Inter Access Point Protocol (LIAPP) Specification v0.3 Draft

1.     Introduction.. 3

2.     General description.. 3

2.1.      Relationships between services. 3

2.2.      Connection service. 4

2.3.      service. 4

3.     Frame formats. 5

3.1.      General frame format. 5

3.1.1.       Protocol Id field. 5

3.1.2.       Control field. 5

3.1.3.       Length field. 5

3.1.4.       Frame Id field. 5

3.1.5.       Frame body. 6

3.1.6.       FCS field. 6

3.2.      Format of individual frame types. 6

3.2.1.       Browse Request frame format 7

3.2.2.       Browse Response frame format 7

3.2.3.       Inquiry Request frame format 7

3.2.4.       Inquiry Response frame format 8

3.2.5.       Configuration Request frame format 8

3.2.6.       Configuration Response frame format 8

3.2.7.       Connection frame format 8

3.2.8.       File Open Request frame format 9

3.2.9.       File Open Response frame format 9

3.2.10.     File Close Request frame format 10

3.2.11.     File Close Response frame format 10

3.2.12.     File Write Request frame format 10

3.2.13.     File Write Response frame format 10

3.2.14.     File Read Request frame format 11

3.2.15.     File Read Response frame format 11

3.2.16.     User Defined Request frame format 11

3.2.17.     User Defined Response frame format 12

3.3.      Frame body components. 12

3.3.1.       User Id field. 12

3.3.2.       Status Code field. 12

3.3.3.       Manufacturer element 13

3.3.4.       Product Name element 13

3.3.5.       Model Name element 13

3.3.6.       Element IDs. 13

4.     Routines and Variables. 14

4.1.      Support routines provided by the LIAPP. 14

4.2.      Support routines provided by Utility Interface. 14

4.3.      Variables provided by LIAPP. 14

4.4.      Variables provided by Utility Interface. 15

Tables

Table 1 Frames permitted in states. 3

Table 2 LIAPP general frame format 5

Table 3 LIAPP control field. 5

Table 4 Frame Id descriptions. 5

Table 5 Frame body of Browse Request 7

Table 6 Frame body of Browse Response. 7

Table 7 Frame body of Inquiry Request 7

Table 8 Frame body of Inquiry Response. 8

Table 9 Frame body of Configuration Request 8

Table 10 Frame body of Configuration Response. 8

Table 11 Frame body of Connect Request 8

Table 12 Presence of user name information. 9

Table 13 Frame body of File Open Request 9

Table 14 Frame body of File Open Response. 9

Table 15 Frame body of File Close Request 10

Table 16 Frame body of File Close Response. 10

Table 16 Frame body of File Write Request 10

Table 16 Frame body of File Write Response. 10

Table 16 Frame body of File Read Request 11

Table 16 Frame body of File Read Response. 11

Table 17 Status Codes. 12

Table 18 Manufacturer element format 13

Table 19 Element ID field description. 13

Table 20 Element class description. 13

1.    Introduction

The LANEscape Inter Access Point Protocol (LIAPP) is developed on top of Utility Interface.

2.    General description

2.1.      Relationships between services

The relationships between these server state variables and services are given by

In State 1, only Class 1 frames are allowed. In State 2, either Class 1 or Class 2 frames are allowed.

Table 1 Frames permitted in states

The frame classes are defined as follows:

a)          Class 1 frames (permitted from within States 1, 2)
1)   Browse Request/Response
2)   Connection: Successful connection enables a station to exchange Class 2 frames.
     Unsuccessful connection leaves the STA in State 1.
3)   Disconnection: Disconnection notification when in State 2 changes the station’s state to State 1.

b)          Class 2 frames (allowed from within States 2, 3, and 4)
1)   Inquiry Request/Response
2)   Configuration Request/Response
If a station A receives a Class 2 frame from station B within State 1, the station A shall send a Disconnection frame to station B.

2.2.      Connection service

2.3.       service

3.    Frame formats

3.1.      General frame format

Table 2 LIAPP general frame format

3.1.1.         Protocol Id field

The Protocol Id field in a LIAPP frame should be 0xF557. The stations will ignore the frame with invalid Protocol Id value.

3.1.2.         Control field

Table 3 LIAPP control field

3.1.3.         Length field

The Length field contains the number of bytes of Sequence, Frame Id, Frame body and CRC16 field.

3.1.4.         Frame Id field

Table 4 Frame Id descriptions

3.1.5.         Frame body

The length of Frame body field can be arbitrary value but limited by the value of global variable LIAPP_MAXFRAMESIZE. The value of global variable LIAPP_MAXFRAMESIZE defines the maximum frame size of a LIAPP frame. The value of LIAPP_MAXFRAMESIZE can be preset by issuing InitLIAPP routine.

3.1.6.         FCS field

The Sequence, Frame Id and Frame body fields should be protected with a CCITT CRC-16 FCS (frame check sequence). The CCITT CRC-16 FCS shall be the remainder generated by the modulo 2 division of the fields by the polynomial:

The CRC16 bits are preset to all zeros. The protected bits shall be processed in transmit order.

3.2.      Format of individual frame types

3.2.1.         Browse Request frame format

The frame body of Browse Request contains the information shown in following table:

Table 5 Frame body of Browse Request