3gpp 0406-821

8/19/2019 3GPP 0406-821

1/57

3GPP TS 04.06 V8.2.1 (2002-05)Technical Specification

3rd Generation Partnership Project;Technical Specification Group GSM/EDGE Radio Access

Networ;Mo!ile Station " #ase Station S$ste% &MS " #SS' interface;

Data (in &D(' la$er specification&Release )***'

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP Oranisational Partners and shall not be implemented.

This !pecification is provided for future development wor" within 3GPP only. The Oranisational Partners accept no liability for any use of this

!pecification.!pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Oranisational Partners# Publications Offices.

8/19/2019 3GPP 0406-821

2/573GPP

$eywordsGSM

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sopi! "#tipolisV!l$o##e - %R"&'

Tel. *33 4 +2 +4 42 00 %!, *33 4 +3 65 4 16

%nternet

ttp///.3pp.o

Copyright Notification

&o part may be reproduced e'cept as authoried by written permission.The copyriht and the foreoin restriction e'tend to reproduction in

all media.

*++*, 3GPP Oraniational Partners (-%/, 01T!, 2T!%, T, TT-,TT0).-ll rihts reserved.

3GPP TS +,-+. 0-1-) &1++1"+2'1Release )***

8/19/2019 3GPP 0406-821

3/57

'o#te#ts

4oreword..........................................................................................................................................................

+ !cope......................................................................................................................................................+. eferences.................................................................................................................................................................+.* -bbreviations............................................................................................................................................................

General.................................................................................................................................................... Options......................................................................................................................................................................

* 4rame structure for peer5to5peer communication....................................................................................*. General......................................................................................................................................................................*.* 4rame delimitation and fill bits...............................................................................................................................*.3 -ddress field............................................................................................................................................................

*.6 0ontrol field............................................................................................................................................................*.7 8enth indicator field..............................................................................................................................................*.7a !hort 8* header type .......................................................................................................................................*.9 %nformation field......................................................................................................................................................*.: Transparency...........................................................................................................................................................*.; 4ormat convention...................................................................................................................................................

*.;. &umberin convention......................................................................................................................................*.;.* Order of bit transmission...................................................................................................................................*.;.3 4ield mappin convention.................................................................................................................................

3 2lements of procedures and formats of fields for nac"nowleded operation variables and parameters......................................................................................

3.9 8enth indicator field format..................................................................................................................................3.: 8enth indicator field variables...............................................................................................................................3.:. 8enth indicator field e'tension bit (28)..........................................................................................................3.:.* More data bit (M)..............................................................................................................................................3.:.3 8enth indicator (8)...........................................................................................................................................3.; 0ommands and responses.......................................................................................................................................

3.;. %nformation (%) commands.................................................................................................................................3.;.* !et asynchronous balanced mode (!-/M) command......................................................................................3.;.3 %) command..........................................................................................................3.;.7 eceive ready () command=response............................................................................................................3.;.9 eject (2A) command=response.......................................................................................................................

3.;.: eceive not ready (&) command=response...................................................................................................

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'3Release )***

8/19/2019 3GPP 0406-821

4/57

3.;.; >nnumbered ac"nowledement (>-) response................................................................................................3.;.B

8/19/2019 3GPP 0406-821

5/57

7.6.3.3.* Procedure after returnin to the old channel (M! only)..............................................................................7.6.6 Termination of multiple frame operation...........................................................................................................7.6.6. General...............................................................................................................................................................7.6.6.* &ormal release procedure..................................................................................................................................

7.6.6.3 Procedure on e'piry of timer T*++ for normal release......................................................................................7.6.6.6 8ocal end release procedure..............................................................................................................................

7.6.7 %dle state.............................................................................................................................................................7.6.9 0ollision of unnumbered commands and responses..........................................................................................7.6.9. %dentical transmitted and received commands...................................................................................................7.6.9.* nsolicited

8/19/2019 3GPP 0406-821

6/57

G.* Parameter errors in the address field.......................................................................................................................G.*. >nallocated !-P%..............................................................................................................................................G.*.* 1ron value of the 0= bit................................................................................................................................G.*.3 2- bit set to +.................................................................................................................................................

G.3 Parameter errors in the control field........................................................................................................................G.3. !upervisory frames............................................................................................................................................

G.3.* >nnumbered frames..........................................................................................................................................G.6 Parameter errors in the lenth indicator field..........................................................................................................G.6. 28 bit error.........................................................................................................................................................G.6.* %nformation frames............................................................................................................................................

G.6.3 !upervisory frames............................................................................................................................................G.6.6 % frames.................................................................................................................................

Annex H (informative): Change Reuest Histor!...............................................................................

%oe/odThis Technical !pecification has been produced by the 3rd Generation Partnership Project (3GPP).

The present document specifies or references procedures used on the /ase !tation !ystem (/!!) to !ervin GP!!upport &ode (!G!&) interface for control of G!M pac"et data services within the diital cellular telecommunicationssystem (Phase *I).

The contents of the present document are subject to continuin wor" within the T!G and may chane followin formalT!G approval. !hould the T!G modify the contents of the present document, it will be re5released by the T!G with anidentifyin chane of release date and an increase in version number as followsF

@ersion '.y.

whereF

' the first diitF

presented to T!G for informationJ

* presented to T!G for approvalJ

3 or reater indicates T!G approved document under chane control.

y the second diit is incremented for all chanes of substance, i.e. technical enhancements, corrections,updates, etc.

the third diit is incremented when editorial only chanes have been incorporated in the document.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'.Release )***

8/19/2019 3GPP 0406-821

7/57

0 Scope

The present document defines a data lin" layer protocol to be used for sinallin, and possibly also for otherapplications, on the M!5/! interface.

0.1 Reee#ces

The followin documents contain provisions which, throuh reference in this te't, constitute provisions of the presentdocument.

• eferences are either specific (identified by date of publication, edition number, version number, etc.) or

non5specific.

• 4or a specific reference, subse?uent revisions do not apply.

• 4or a non5specific reference, the latest version applies. %n the case of a reference to a 3GPP document (includin

a G!M document), a non5specific reference implicitly refers to the latest version of that document in the same Release as the present document .

KL 3GPP T! +.+6F -bbreviations and acronyms.

K*L 3GPP T! +6.+F Mobile !tation 5 /ase !tation !ystem (M! 5 /!!) interfaceJ General aspects and principles.

K3L 3GPP T! +6.+3F Mobile !tation 5 /ase !tation !ystem (M! 5 /!!) interface 0hannel structures

and access capabilities.

K6L 3GPP T! +6.+6F 8ayer General re?uirements.

K7L 3GPP T! +6.+7F

8/19/2019 3GPP 0406-821

8/57

&OT2 F The term

8/19/2019 3GPP 0406-821

9/57

5 4ormat - is used on % frames transmitted by the networ" on !-00CJ

5 format / is applied in all other cases.

5 4ormat /bis is used only on /00C, P0C, &0C, and -G0C.

5 %n addition there is a 4ormat 0 for transmission of random access sinals.

4ormat 0 frames are described in anne' -. 4ormat -, /, /bis, /ter and /6 frames are described in the remainder of the present document.

it 0 . 2 , 3 1 )ctet &o

)

4 Address field 4

5ontrol field 6)

61

4 (en7th indicator field 4

n

n6)

4 8ill !its 4

N1+)6n

8or%at t$pe A

8i7ure )/3GPP TS +,-+. &sheet ) of 3'4 General fra%e for%ats

it 0 . 2 , 3 1 )ctet &o

)

4 Address field 4

5ontrol field 6)

61

4 (en7th indicator field 4n

n6)

4 9nfor%ation field 4

N

N6)

4 8ill !its 4

N1+)6n

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'*Release )***

8/19/2019 3GPP 0406-821

10/57

8or%at t$pe #

it 0 . 2 , 3 1 )ctet &o

1

9nfor%ation field

N1+)

8or%at t$pe #!is

8i7ure )/3GPP TS +,-+. &sheet 1 of 3'4 General fra%e for%ats

it 0 . 2 , 3 1 )

ctet &o)

4 Address field 4

5ontrol field 6)

61

4 9nfor%ation field 4

N1+) 66)

8or%at t$pe #,

it 0 . 2 , 3 1 )ctet &o

sot L2 e!det7pe 1

)

1

4 9nfor%ation field 44 4

N1+)

8or%at t$pe #ter

8i7ure )/3GPP TS +,-+. &sheet 3 of 3'4 General fra%e for%ats

The parameter &*+ is the ma'imum number of octets which are partially or entirely available for the information fieldof a frame. %t depends on the type of channel and the format, see subclause 7.;.3.

2.2 %!e deliit!tio# !#d ill $its

4rame delimitation is provided by the physical layerF

5 in format type -, / and /6 frames at the beinnin of the frame for determinin the start of the first octet in the

address field,in format type /ter frames for determinin the start of the octet containin the short 8* headertype (which is also the first octet used for the information field), and in format type /bis frames for

determinin the start of the first octet for the information fieldJ

5 at the end of the frame for determinin the last bit of the frame.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2')+Release )***

8/19/2019 3GPP 0406-821

11/57

The end of the useful part of the frame, i.e. the end of the lenth indicator field in type - frames and the end ofthe information field in type / frames, is determined by a lenth indicator contained in the lenth indicator field.The useful part of a /bis frames ta"es all &*+ octets of that frame. The useful part of a /ter frame ta"es all &*+ octets of that frame e'cept those bits of octet which contain the short 8* header type . The useful part

of a /6 frame ta"es all &*+ octets of that frame e'cept those octets which contain the address field and thecontrol field.

%f a frame contains a lenth indicator has a value less than &*+, the frame contains fill bits. Octets containinfill bits shall ta"e the binary value ++++, when sent by the networ". Octets containin fill bits shall ta"e

the value ++++ or , when sent by the mobile station.

&OT2F The value ++++ is chosen due to the modulation and interleavin scheme used in the G!M system.

2.3 "ddess ield

The address field may consist of a variable number of octets. Cowever, for applications on control channels the fieldconsists of only one octet. The address field identifies the !-P for which a command frame is intended and the !-P

transmittin a response frame. The format of the address field is defined in subclause 3.*.

2.4 'o#tol ield

The control field consists of one octet. The format of the control field is defined in subclause 3.6.

2.5 Le#t i#dic!to ield

The lenth indicator field may consist of a variable number of octets. Cowever, for applications on control channels thefield consists of only one octet. The format of the field is defined in subclause 3.9.

2.5! Sot L2 e!de t7pe 1

The short 8* header type consists of two bits. %ts contents are defined in subclause 3.6a.

2.6 #o!tio# ield

The information field of a frame, when present, has the position in the frame defined in *..

The ma'imum number of octets in the information field (&*+) is defined in subclause 7.;.3.

2. T!#sp!e#c7

/ecause of the frame delimitation techni?ue used (see subclause *.*), the frame can include any possible se?uence of bits without the need for additional transparency mechanisms.

2.8 %o!t co#e#tio#

2.8.1 &u$ei# co#e#tio#

The basic convention used in this Technical !pecification is illustrated in fiure *. The bits are rouped into octets.

The bits of an octet are shown horiontally and are numbered from to ;. Multiple octets are shown vertically and arenumbered from to n.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'))Release )***

8/19/2019 3GPP 0406-821

12/57

#it 0 . 2 , 3 1 ):ctet no

1

2

9

9

#

8i7ure 1/3GPP TS +,-+.4 8or%at conention

2.8.2 de o $it t!#sissio#

The order of bit transmission is defined in 3GPP T! +6.+6.

2.8.3 %ield !ppi# co#e#tio#

1hen a field is contained within a sinle octet, the lowest bit number of the field represents the lowest order value.

1hen a field spans more than one octet, the order of bit values within each octet proressively decreases as the octetnumber increases. %n that part of the field contained in a iven octet the lowest bit number represents the lowest ordervalue.

4or e'ample, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bitnumber within the octet. 4iure 3 illustrates a field that spans from bit (, 3) to bit (*, :). The hih order bit of the fieldis mapped on bit (, 3) and the low order bit is mapped on bit (*, :).

#it 0 . 2 , 3 1 )

4 3 2 1st octet ield2 2 2

1 0 2#d octet ield2 2

8i7ure 3/3GPP TS +,-+.4 8ield %appin7 conention

3 lee#ts o pocedues !#d o!ts o ields o:!t! Li#; L!7e pee-to-pee cou#ic!tio#

3.1 Ge#e!l

The elements of procedures define the commands and responses that are used on the data lin" connections carried on

the

8/19/2019 3GPP 0406-821

13/57

5 and the 8in" Protocol !tio#

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2')3Release )***

8/19/2019 3GPP 0406-821

14/57

3.4 'o#tol ield o!ts

The control field identifies the type of frame, which will be either a command or a response. The control field will

contain se?uence numbers, where applicable.

Three types of control field formats are specifiedF numbered information transfer (% format), supervisory functions (!format), and unnumbered information transfer and control functions (> format). The control field formats for 8-P format shall be used to provide additional data lin" control functions and unac"nowleded information transfer.

This format does not contain se?uence numbers. %t does include a P=4 bit that may be set to + or .

Ta!le 3/3GPP TS +,-+.4 5ontrol field for%at

5ontrol field !its 0 . 2 , 3 1 )

o!t &(R) P &(S) 0

S o!t &(R) P% S S 0 1

? o!t ? ? ? P% ? ? 1 1

&(!) Transmitter send se?uence number.

&() Transmitter receive se?uence number.

! !upervisory function bit.

> >nnumbered function bit.

P=4 Poll bit, when issued as a command, final bit, when issued as a response.

4or definition of values for supervisory function bits and unnumbered function bits, see table 6.

3.4! Sot L2 e!de t7pe 1

The short 8* header type field is used in format /ter frames, see subclause *.. %t consists of * bits, both shall ta"evalue +.

&OT2F %ntroduction of further short 8* header types (loner than * bits, settin bit * to and bit to +) is forfurther study.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'),Release )***

8/19/2019 3GPP 0406-821

15/57

The short 8* header type implicitly defines a >% command frame belonin to !-P%H+, with lenth &*+. -ll other parameters of a 8* frame header are irrelevant.

3.5 'o#tol ield p!!etes !#d !ssoci!ted st!te !i!$les

The various parameters associated with the control field formats are described in this clause. The codin of the bitswithin these parameters is such that the lowest numbered bit within the parameter field is the least sinificant bit.

3.5.1 Poll%i#!l $it

-ll frames contain P=4, the Poll=4inal bit. The Poll=4inal (P=4) bit serves a function in both command frames andresponse frames. %n command frames the P=4 bit is referred to as the P bit. %n response frames it is referred to as the 4 bit.

The P bit set to is used by a data lin" layer entity to create (poll) a response frame from the peer data lin" layer

entity. The 4 bit set to is used by a data lin" layer entity to indicate the response frame transmitted as a result of asolicitin (poll) command.

The use of the P=4 bit is described in clause 7.

3.5.2 Multiple !e ope!tio# - !i!$les !#d se@ue#ce #u$es

3.5.2.1 Modulus

2ach % frame is se?uentially numbered by a se?uence number which may have the value + throuh :.

-rithmetics actin on variables which are related to such se?uence numbers (i.e. &(!), &(), @(!), @(), @(-)J seefollowin subclauses) operate modulo ;.

&OT2F Modulo ; operation on neative numbers is performed by addin multiples of ; to the neative numberuntil the result becomes nonneative. Then common modulo ; operation is applied.

3.5.2.2 Se#d st!te !i!$le V(S)

2ach point5to5point data lin" connection endpoint shall have an associated send state variable (@(!)) when usin

% frame commands. The send state variable denotes the se?uence number of the ne't in5se?uence % frame to betransmitted.

The send state variable can ta"e on the value + throuh :.

The value of the send state variable shall be incremented by with each successive % frame transmission, and shall not

e'ceed @(-) by more than the ma'imum number of outstandin % frames " (The window sie " is defined insubclause 7.;.6.). The value of " may be in the rane of HN"HN:.

3.5.2.3 "c;#o/lede st!te !i!$le V(")

2ach point5to5point data lin" connection endpoint shall have an associated ac"nowlede state variable (@(-)) whenusin % frame commands and supervisory frame commands=responses.

The ac"nowlede state variable identifies the last frame that has been ac"nowleded by its peer (@(-) 5 e?uals the &(!) of the last ac"nowleded % frame). The ac"nowlede state variable can ta"e on the value + throuh :. The value ofthe ac"nowlede state variable shall be updated by the valid &() values received from its peer (see 3.7.*.9). - valid

&() value is one that is in the rane @(-)HN&()HN@(!).

&OT2F These ine?ualities shall be interpreted in the followin wayF &() is called valid, if and only if (&()5@(-)) mod ; NH (@(!)5@(-)) mod ;.4urthermore, from subclause 3.7.*.*., it is obvious that (@(!)5@(-)) mod ; NH ".

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2')2Release )***

8/19/2019 3GPP 0406-821

16/57

3.5.2.4 Se#d se@ue#ce #u$e &(S)

Only % frames contain &(!), the send se?uence number of transmitted % frames. -t the time that an in5se?uence % frameis desinated for transmission, the value of &(!) is set e?ual to the value of the send state variable @(!).

3.5.2.5 Receie st!te !i!$le V(R)

2ach point5to5point data lin" connection endpoint shall have an associated receive state variable (@()) when usin% frame commands and supervisory frame commands=responses. The receive state variable denotes the se?uence number of the ne't in5se?uence % frame e'pected to be received. The receive state variable can ta"e on the value + throuh :.

The value of the receive state variable shall be incremented by one with the receipt of an error5free, in5se?uence % frame

whose send se?uence number &(!) e?uals the receive state variable @().

3.5.2.6 Receie se@ue#ce #u$e &(R)

-ll % frames and supervisory frames contain &(), the e'pected send se?uence number of the ne't received % frame.

-t the time that a frame of the above types is desinated for transmission, the value of &() is set e?ual to the current

value of the receive state variable @(). &() indicates that the data lin" layer entity transmittin the &() has correctlyreceived all % frames numbered up to and includin &() 5 .

3.5.2. te p!!etes !#d !i!$les

4or definition and values of parameters and variables such as timer T*++, ma'imum number of retransmissions (&*++),window sie (") and the ma'imum number of octets in an information field (&*+), see subclause 7.;.

3.5.3 ?#!c;#o/leded ope!tio# !i!$les !#d p!!etes

The only parameter defined for unac"nowleded operation is the number of octets (&*+) in the information field of the>% frame. !ee subclause 7.;.3.

3.6 Le#t i#dic!to ield o!t

The format of the lenth indicator field for control channels is shown in fiure 7.

The lenth indicator field e'tension bit, 28, enables e'tension of the field to span more than one octet.

#it 0 . 2 , 3 1 )

L M L

8/19/2019 3GPP 0406-821

17/57

The more data bit, M, is used to indicate sementation of layer 3 messae units on data lin" layer frames. 8ayer 3messaes, which need to be semented, shall only be transported by %5frames.

1hen the M bit is set to , it indicates that the information field of the frame contains only a sement of the layer 3messae unit.

The M bit set to + indicatesF

i) that the information field contains a complete layer 3 messae unit provided that the M bit of the previous frame

was set to +J

ii) that the information field contains the last sement of a layer 3 messae unit if the M bit of the previous framewas set to .

1hen the M bit is set to , the information field shall contain the ma'imum number of octets, &*+, that aninformation frame can contain, see subclause 7.;.3 for the value of &*+.

%n frames other than information (%) frames the M bit shall be set to +.

3..3 Le#t i#dic!to (L)

The lenth indicator consists of 9 bits and is used to indicate the number of octets contained in the information field of>%, !-/M, >- or % frames, i e any value from + to &*+ inclusive.

The 8 H + shall be used in frames not containin an information field.

3.8 'o!#ds !#d espo#ses

The followin commands and responses are used by either the M! or the /! data lin" layer entities and are representedin table 6. 2ach data lin" connection supports the appropriate set of commands and responses for the type of operationdesired (see clause 7).

4or purposes of the 8-P

8/19/2019 3GPP 0406-821

18/57

3.8.1 #o!tio# () co!#ds

The function of the information (%) command is to transfer, across a data lin" connection, se?uentially numbered framescontainin information fields provided by layer 3. This command is used in the multiple frame operation.

Ta!le ,/3GPP TS +,-+.4

5o%%ands and responses " unacnowled7ed and %ultiple fra%e acnowled7ed operation

%o!t 'o!#ds Respo#ses 8 6 5 4 3 2 1

#o!tio#t!#se

(i#o-!tio#)& ( R ) P & ( S ) 0

RR(eceiee!d7)

RR(eceiee!d7)

& ( R ) P% 0 0 0 1

Supeiso7 R&R(eceie

#ot e!d7)

R&R(eceie

#ot e!d7)& ( R ) P% 0 1 0 1

RA

(eBect)

RA

(eBect) & ( R ) P% 1 0 0 1S"M

(set !s7#-co#ous$!l!#ced

ode)

0 0 1 P 1 1 1 1

?##u$eed:M

(disco##ectode)

0 0 0 % 1 1 1 1

? (u#-#u$eed

i#o!tio#) 0 0 0 P 0 0 1 1

:S'

(disco##ect) 0 1 0 P 0 0 1 1?" (u#-

#u$eed!c;#o/-lede)

0 1 1 % 0 0 1 1

3.8.2 Set !s7#co#ous $!l!#ced ode (S"M) co!#d

The !-/M unnumbered command is used to place the addressed user side or networ" side into the modulo ; multipleframe ac"nowleded operation.

-n information field is permitted with the !-/M command only if it is used in the M! to /!! direction in order to

establish a !-P% + data lin" (for contention resolution after havin transmitted a random access frame on the -0C).8ayer 3 will indicate when an information field is to be included (see subclause 7.6. for procedures).

- data lin" layer entity confirms acceptance of a !-/M command by the transmission at the first opportunity of a >-response. >pon acceptance of this command, the data lin" layer entity#s send state variable @(!), ac"nowlede statevariable @(-), and receive state variable @(), are set to +. The transmission of an !-/M command indicates the

clearance of any e'ception condition, in particular a busy condition that was reported by the earlier transmission of an& frame by that same data lin" layer entity.

Previously transmitted % frames that are unac"nowleded when this command is actioned remain unac"nowleded andshall be discarded. %t is the responsibility of a hiher layer (for e'ample, layer 3) to recover from the possible loss of thecontents of such % frames.

&OT2F !-/M frames cannot contain layer 3 messae units which have to be semented.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2')0Release )***

8/19/2019 3GPP 0406-821

19/57

3.8.3 :isco##ect (:S') co!#d

The % unnumbered command shall be used tosend information to its peer without affectin data lin" layer variables. >% command frames do not carry a se?uence

number. Therefore, the >% frame may be lost without notification to the layer 3 entity if a data lin" e'ception occurs

durin transmission of the command.

The re?uest of unac"nowleded information transfer may re?uire short 8* header type . %f the layer * entity does notsupport short 8* header type , it shall report an M

8/19/2019 3GPP 0406-821

20/57

3.8. Receie #ot e!d7 (R&R) co!#despo#se

The receive not ready (&) supervisory frame shall be used by a data lin" layer entity to indicate a busy conditionJthat is, a temporary inability to accept additional incomin % frames. The value of &() in the & frame ac"nowledes

% frames numbered up to and includin &() 5 .

-c"nowledement of subse?uent % frames transmitted before the indication of the peer receiver busy is received, will bemade in subse?uent e'chanes if they arrive after the peer receiver busy condition has been cleared.

%n addition to indicatin the status of a data lin" layer entity, the & command with the P bit set to may be used bythe data lin" layer entity to as" for the status of its peer data lin" layer entity.

&o information field is permitted with the & command= response.

&OT2F The protocol operation used on control channels with !-P%H+ or !-P%H3 shall not utilie the & frame

type and related procedures. Therefore & frames received in those cases can be inored.

3.8.8 ?##u$eed !c;#o/ledee#t (?") espo#se

The >- unnumbered response is used by a data lin" layer entity to ac"nowlede the receipt and acceptance of the modesettin commands (!-/M or - response istransmitted.

-n information field is permitted with the >- response, i e if an !-/M command with an information field is received

and the !-/M is to be ac"nowleded, the >- response to that command shall contain the same information field asreceived in the !-/M command.

The transmission of the >- response indicates the clearance of any busy condition that was reported by the earliertransmission of an & frame by that same data lin" layer entity.

3.8.+ :isco##ected ode (:M) espo#se

The

8/19/2019 3GPP 0406-821

21/57

The primitive eneric names that are defined in the present document areF

4.1.1.1 :L-ST"LSC

The

8/19/2019 3GPP 0406-821

22/57

4.1.1.11 PC-:"T"

The PC52!T primitive type.

4.1.2.3 RSP&S

The 2!PO&!2 primitive type is used by a layer to ac"nowlede receipt, from the ne't lower layer, of the%&

8/19/2019 3GPP 0406-821

23/57

4.1.2.4 '&%RM

The 0O&4%M primitive type is used by the layer providin the re?uested service to confirm that the activity has beencompleted.

4iure 9 illustrates the relationship of the primitive types to the layer 3 and the data lin" layer.

F

L!7e1 3

'o#i15 Re@uest

S"P

:!t!li#;l!7e1

F

Respo#se

S"P

8#dic!tio#

L!7e1 2 pee1-to-pee1 p1otocol

8i7ure ./3GPP TS +,-+.4Relationship of the pri%itie t$pes to the la$er 3 and the data lin la$er

4.1.3 P!!ete dei#itio#

4.1.3.1 Mess!e u#it

The messae unit contains additional layer5to5layer information concernin actions and results associated with re?uests.

%n the case of the &%T

8/19/2019 3GPP 0406-821

24/57

4.1.3.3 Seice "ccess Poi#t

!ince data lin"s on different !-P%s may be multiple'ed, the !-P% parameter is used to indicate the respectiveassociation.

4.1.3.4 Rele!se ode

The release mode parameter is used to enable the data lin" layer to operate in different release modes dependin onwhether the data lin" is to be released in the normal way or that a local end release shall ta"e place on command fromthe layer 3. The values of the parameter areF

5 normalJ

5 local end release.

4.1.3.5 o c!use

This parameters is used by the data lin" layer to report procedure error to layer 3. The followin causes may be

reportedF

5 timer T*++ e'pired (&*++ I) timesF perform abnormal releaseJ

5 re5establishment re?uestJ

5 unsolicited >- responseJ

5 unsolicited

8/19/2019 3GPP 0406-821

25/57

4.1.3.8 Pioit7

This parameter is used by the hiher layers to indicate the priority of a 8ayer 3 messae on !-P% + with multiple frameoperation. The parameter is not applicable to unac"nowleded information transfer or to other !-P%s. The parameterta"es the followin valuesF

5 hihJ5 normalJ

5 low.

The parameter need not be included if the hiher layers do not support the sendin of low priority messaes as definedin 3GPP T! +6.+;. %f the parameter is not included, the data lin" layer shall assume a priority value of normalQ.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'12Release )***

8/19/2019 3GPP 0406-821

26/57

Ta!le 2/3GPP TS +,-+.4 Data (in Serice pri%ities

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'1.Release )***

8/19/2019 3GPP 0406-821

27/57

Generic na%e Para%eters Messa7e

unit

and t$peSAP9 5hannel

t$peError

5auseRelease%ode

Esta!lish%ode

(1header

t$pe

Priorit$ contents

:L-ST"LSC-RE?ST 0 :''C 'oRes

L!7e 3ess!e

0:''C=S"''C &o

3:''C=S"''C &o

:L-ST"LSC-&:'"T& 0 :''C 'oRes

L!7e 3ess!e

0:''C=S"''C &o

3:''C=S"''C &o

:L-ST"LSC-

'&%RM 0 :''C 'oRes

0:''C=S"''C &o

3:''C=S"''C &o

:L-RL"S-RE?ST 0=3

:''C=S"''C !#7

:L-RL"S-&:'"T& 0=3

:''C=S"''C !#7

:L-RL"S-'&%RM 0=3

:''C=S"''C !#7

:L-S?SP&:-RE?ST 0 :''C

:L-S?SP&:-

'&%RM 0 :''C:L-RS?M-

RE?ST 0 :''CL!7e 3pee-to-

pee ess!e

:L-RS?M-'&%RM 0 :''C

:L-R'&&'T-RE?ST 0 :''C

L!7e 3pee-to-

pee ess!e

:L-R'&&'T'&%RM 0 :''C

:L-:"T"-RE?ST

0=3 :''C=S"''C

!#7(S"P 0

o#l7)

L!7e 3

pee-to-pee

ess!e

:L-:"T"-&:'"T& 0=3 :''C=

S"''C

L!7e 3pee-to-

pee ess!e

:L-?&T:"T"-RE?ST

0

''C'''C:''C

S"''C

#o!lL2

e!de sot

L2e!de t7pe 1

L!7e 3pee-to-

pee ess!e

3 :''CS"''C

L!7e 3pee-to-

pee ess!e

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'1Release )***

8/19/2019 3GPP 0406-821

28/57

Generic na%e Para%eters Messa7e

unit


t$peError

5auseRelease%ode

Esta!lish%ode

(1header

t$pe

Priorit$ contents

:L-?&T:"T"-&:'"T& 0

''C'''C:''C

S"''C

L!7e 3pee-to-

pee ess!e

3 :''CS"''C

L!7e 3pee-to-

pee ess!e

M:L-RL"S-RE?ST 0=3 :''C=

S"''C

M:L-RRR-

&:'"T& 0=3 :''C=S"''C

!#7

:L-R"&:M "''SS-RE?ST 0 R"'C

'!##ele@uest

(see3GPP TS

04.08)

0 :''CC!#doe

!ccess(see

3GPP TS04.08)

:L-R"&:M "''SS-&:'"T& 0 R"'C

Re@uesteee#ce

(see3GPP TS

08.58)

0 :''CC!#doe eee#ce

(see3GPP TS

08.58)

:L-R"&:M "''SS-'&%RM 0 R"'C

Re@uesteee#ce

(see3GPP TS

04.08)

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'10Release )***

8/19/2019 3GPP 0406-821

29/57

Ta!le ./3GPP TS +,-+.4 Ph$sical Serice pri%ities used

Generic na%e Para%eters Messa7e unit


t$peError 5ause

Release%ode

Esta"!lish

%ode

contents

PC-:"T"-RE?ST !#7

:!t! li#; pee-to-pee

ess!e

PC-:"T"-&:'"T& !#7

:!t! li#; pee-to-pee

ess!e

PC-R"&:M "''SS-RE?ST R"'C=

:''C

R!#do !ccessd!t! li#;

ess!e u#it

PC-R"&:M "''SS-&:'"T& R"'C=

:''C

R!#do !ccessd!t! li#;

ess!e u#it!#d T:M"

!e #.PC-R"&:M

"''SS- '&%RMR"''C=:''C

T:M" !e#u$e

PC-'&&'T-&:'"T& !#7

PC-R":D-T-S&:-&:'"T. !#7

PC-MPTD-%R"M-RE?ST !#7

&OT2 F Table 7 and table 9 do not contain a complete list of conditional dependencies of service primitive parameters. %f a field is left blan", the respective parameter shall not be used or is not applicable. %f a fieldis mar"ed by any, the respective parameter shall be used and shall be set to a valid value accordin itsspecification.

&OT2 *F %n table 7 and table 9, the term

8/19/2019 3GPP 0406-821

30/57

5 :ei#itio# o te pee-to-pee potocol L"P:

5.1 Ge#e!l

%n the followin clauses, a protocol for use by the data lin" layer on the radio interface is specified, referred to as8-P

8/19/2019 3GPP 0406-821

31/57

5.2 Ge#e!l Potocol Pocedues

5.2.1 ?#!c;#o/leded i#o!tio# t!#se

Ciher layers may as" for unac"nowleded transmission transfer with normal 8* headerJ hiher layers may also as" for

unac"nowleded transmission transfer on !-P% + usin short 8* header type .

1hen a protocol entity receives a valid >% frame, this re?uires no further response to the transmittin entity.

4or unac"nowleded information transfer with normal 8* header, the P=4 bit is not used and shall be set to +.

5.2.2 "c;#o/leded ultiple !e i#o!tio# t!#se

- data lin" layer entity receivin an !-/M, nac"nowleded information is passed to the data lin" layer by layer 3 usin the primitive &%T

2!T. This &%T 2!T specifies whether a short 8* header type is to be used or not.The layer 3 messae unit shall be transmitted in a >% command frame.

8ayer * shall construct a layer * messae unit from the layer 3 messae unit and pass it to layer for transmission usinthe primitive PC5% command frame with a !-P% which is supported by the receiver, the contents of the information field

shall be passed to the layer 3 entity identified by the !-P% usin the data lin" layer to layer 3 primitive &%T% frames received with the lenthindicator set to + shall be inored.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2'3)Release )***

8/19/2019 3GPP 0406-821

32/57

5.4 Pocedues o est!$lise#t !#d ele!se o ultiple !eope!tio#

5.4.1 st!$lise#t o ultiple !e ope!tio#

5.4.1.1 Ge#e!l

These procedures shall be used to establish multiple frame operation between the /! and a desinated M! entity.

8ayer 3 will initiate the establishment procedure after a physical channel supportin this type of operation(see subclause 7.) has been allocated to the M!.

&OT2F %n order to avoid loss of layer 3 information if the !-/M has to be retransmitted because the >-response messae is lost, the data lin" layer should be established when needed by the entity that willsend an % command frame. 4or !-P% + the data lin" is always established by the M!.

Two establishment procedures are specifiedF

5 normal establishment where the !-/M does not contain an information field. 8ayer 3 will indicate a re?uest forthis type of establishment by the use of the 2!T primitive (subclauses 7.6..* and7.6..3)J

5 contention resolution where the !-/M contains an information field. The procedure is always initiated by theM!, i e the !-/M is sent by the M!. 8ayer 3 will indicate a re?uest for this type of establishment by the use ofthe 2!T primitive containin the layer 3 messae unit (subclauses 7.6..6 and 7.6..7).This procedure is only applicable for !-P% +.

e5establishment may be initiated, usin the normal establishment procedure, as a result of the data lin" layer proceduredefined in subclause 7.9.

5.4.1.2 &o!l est!$lise#t pocedues

- data lin" layer entity shall initiate a re?uest for the multiple frame operation to be set by transmittin the !et-synchronous /alanced Mode (!-/M) command with the P bit set to . !ince the 2!T primitive does not contain a layer 3 messae unit, the lenth indicator, 8, is set to +.

-ll e'istin e'ception conditions shall be cleared, the retransmission counter shall be reset, and timer T*++ shall be set

riht before transmittin a frame, when the PC52-nnumbered -c"nowledement (>-) response with the 4 bit set to the same binary value as theP bit in the received !-/M command, the same !-P% value as in the received !-/M command, and with thelenth indicator, 8, set to +J

5 set the send state variable @(!), receive state variable @() and ac"nowlede state variable @(-) to +J

5 enter the multiple5frame5established state and inform the associated layer 3 entity usin the primitive

8/19/2019 3GPP 0406-821

33/57

>pon reception of the >- response with the 4 bit set to , the oriinator of the !-/M command shallF

5 reset timer T*++J

5 set the send state variable @(!), the receive state variable @() and the ac"nowlede state variable @(-) to +J

5 enter the multiple5frame5established state and inform the associated layer 3 entity usin the primitive

- response with the 4 bit set to + shall be inored.

>pon reception of a

8/19/2019 3GPP 0406-821

34/57

5 the lenth indicator, 8, set to the same value as that contained in the !-/M commandJ

5 the same information field as that contained in the !-/M commandJ


5 enter the contention resolution receiver state and inform the layer 3 entity usin the

- response withF

5 the same !-P% value as received in the !-/M commandJ

5 the 4 bit set to the same binary value as the P bit contained in the !-/M commandJ

5 the lenth indicator, 8, set to the same value as that contained in the !-/M commandJ

5 the stored information field.

&OT2 *F This case corresponds to a retransmission of the !-/M command by the M! (see subclause 7.6..7).

&OT2 3F The specification is very different from the normal establishment procedureF in the latter case thereception of a subse?uent !-/M frame triers a re5establishment (see subclause 7.9).

The data lin" layer entity in the /! shall remove the establishment in proress fla and delete the stored information

field whenF

5 an % frame or supervisory frame is received. %f the frame is in se?uence, the data lin" layer entity shall enter themultiple frame established state and process the frame as specified for operation in the multiple frameestablished state. %f the frame is out of se?uence, the /! shall initiate abnormal release usin the procedure of

subclause 7.9J

5 a release re?uest is received from layer 3. %n this case the data lin" layer entity shall enter the idle state if the primitive received is 2!T or the null state if the primitive is M2!T.

The procedure when awaitin ac"nowledement in the M! is as followsF

>pon reception of a >- response containin an information field and with the 4 bit set to , the data lin" layer entityin the M! shall compare the stored information field with the information field received in the >- response. %f the twofields are identical, the data lin" layer entity shallF

5 reset timer T*++J


5 delete the stored information fieldJ

5 enter the multiple5frame5established state and inform the layer 3 entity usin the

8/19/2019 3GPP 0406-821

35/57

&OT2 6F %n fact, there are no foreseen cases in which the networ" will send !-/M,

8/19/2019 3GPP 0406-821

36/57

Ta!le /3GPP TS +,-+.4 Actions taen on response fra%es

Response fra%e Multiple fra%e esta!lished Ti%er recoer$

?" %

8/19/2019 3GPP 0406-821

37/57

5.4.3 Suspe#sio# !#d esuptio# o ultiple !e ope!tio#

5.4.3.1 Ge#e!l

These procedures shall be used in a M! entity to suspend the uplin" multiple frame operation for !-P%H+ durin achane of dedicated channels (dedicated channel assinment or handover procedure on layer 3) and to resume theoperation after the new physical channel has been connected. The purpose of these procedures is to provide amechanism for reliably avoidin messae loss durin a chane of dedicated channels. The procedures are onlydescribed for the case where the window sie is oneJ it should, however, be obvious how to adapt them to larerwindow sies.

-s the procedures may delay the actual channel chane, they shall only be used to protect layer 3 messaes pertaininto !-P%H+. -pplications usin the multiple frame established service on !-P%s other than + are e'pected to cope withmessae loss or duplication autonomously, i.e. on layers above layer *.

/oth layer 3 procedures, dedicated channel assinment and handover, are initiated and controlled by a networ" entity

(/!! or M!0). This entity therefore will suspend the flow of layer 3 messaes towards the M! after the-!!%G&M2&T or C-&% frame is constructed, only one at atime, and placed in a transmit buffer. (%f the layer 3 messae needs to be semented, then this last step will be performedseveral times). The frame is then transmitted.

>pon transmission and after it has been ac"nowleded if it has been an % frame, the transmit buffer is cleared and filledwith the ne't frame. 1hen the contents of the send buffer have been transmitted and ac"nowleded, the send buffer is

cleared and filled with the ne't layer 3 messae from the send ?ueue.

5.4.3.2 Suspe#sio#

- layer 3 entity in the M! shall indicate a re?uest for the suspension of multiple frame operation by use of the

!P2&2!T primitive. The layer * entity, upon receipt of this primitive, shall act as followsF

&o further layer 3 messaes shall be ta"en from the send ?ueue for !-P%H+.

5 %f there is a layer 3 messae in the send buffer which has not yet been transmitted, it shall not be transmitted. Thecontents of the send buffer shall be put bac" to the first position of the send ?ueue. The send and transmit buffers

shall be cleared. - layer 3 messae is considered to be transmitted as soon as its final sement has beentransmitted at least onceJ it need not yet have been ac"nowleded. (This ensures that all sements of a sementedand possibly partly transmitted layer 3 messae will be transmitted on the new channel. Those sements alreadytransmitted and received on the networ" side will be discarded by the networ" upon release of the old channel because the layer 3 messae is not yet complete).

5 %f there is a layer 3 messae in the send buffer, the last sement of which has been transmitted but is not yet fullyac"nowleded, i.e. the frame carryin the last sement of the messae has been transmitted but is not yetac"nowleded, then the contents of the send buffer shall be put bac" to the first position of the send ?ueue andthe send and transmit buffers shall be cleared.

5 The layer * entity shall then return a !P2&

8/19/2019 3GPP 0406-821

38/57

5.4.3.3 Resuptio#

5.4.3.3.1 Pocedue !te c!##el c!#e

This procedure is initiated by the M2 primitive. - data lin" layer entity shall initiate a re?uest for the multipleframe operation by transmittin the !-/M command.

-ll e'istin e'ception conditions shall be cleared and the retransmission counter shall be reset. -ll outstandinpon reception of >- response the data lin" layer shallF

5 reset T*++J

5 set send variable @(!), the receive state variable @() and the ac"nowlede state variable @(-) to +J

5 enter the multiple established stateJ

5 confirm establishment to layer 3 usin pon reception of a >- response the data lin" layer shallF

5 reset T*++J

5 set send state variable @(!), the receive state variable @() and the ac"nowlede state variable @(-) to +J

5 enter the multiple frame established stateJ

5 confirm establishment to layer 3 usin

8/19/2019 3GPP 0406-821

39/57

5.4.4 Tei#!tio# o ultiple !e ope!tio#

5.4.4.1 Ge#e!l

These procedures shall be used to terminate the multiple frame operation between the /! and a desinated M! entity.

- layer 3 entity shall indicate a re?uest for termination of the multiple frame operation by use of the2!T primitive. The 2!T primitive will contain a parameter indicatinwhether normal release or local end release shall ta"e place. %n the first case the data lin" layer will initiate the release procedure of subclause 7.6.6.*. %n the second case the data lin" layer shall follow the procedures of subclause 7.6.6.6.

%f a physical channel is disconnected at the physical layer, layer 3 will re?uest release (i e local end release) by issuinan M2!T primitive. The actions to be ta"en are defined in subclause 7.6.6.6.

-ll frames other than unnumbered frames received durin the release procedure shall be inored.

4or normal release the release procedure implies the discard of any outstandin

8/19/2019 3GPP 0406-821

40/57

5.4.4.4 Loc!l e#d ele!se pocedue

1hen receivin a 2!T primitive from layer 3 with the release mode parameter set to local endrelease, the data lin" layer shall in all statesF

5 return a

8/19/2019 3GPP 0406-821

41/57

5.4.6.2 :iee#t t!#sitted !#d eceied co!#ds

%f the transmitted and received unnumbered commands (!-/M or

8/19/2019 3GPP 0406-821

42/57

5 if the M bit is set to +, concatenate it with previously received frames with the M bit set to , if any, and passthe complete layer 3 messae unit to the layer 3 entity usin the primitive

8/19/2019 3GPP 0406-821

43/57

%f timer T*++ has been reset by the receipt of an %, or & frame, and if there are outstandin % frames stillunac"nowleded, the data lin" layer entity shall set timer T*++. %f timer T*++ then e'pires, the data lin" layer entityshall follow the recovery procedure as defined in subclause 7.7.: with respect to the unac"nowleded % frames.

%f timer T*++ has been reset by the receipt of an 2A frame, the data lin" layer entity shall follow the retransmission procedures in subclause 7.7.6.

5.5.3.2 Receii# supeiso7 co!#d !es /it te P $it set to 1

1hen receivin supervisory command frames with the P bit set to , the followin responses with the 4 bit set to shall be ivenF

5 if the data lin" layer entity is neither in an own receiver busy condition nor in an &(!) se?uence error e'ceptioncondition, the appropriate supervisory response is the responseJ

5 if the data lin" layer entity is not in an own receiver busy condition, but is in an &(!) se?uence error e'ceptioncondition (i e an &(!) se?uence error has been detected but a 2A frame has not yet been transmitted), theappropriate supervisory response is the 2A responseJ

5 if the data lin" layer is in its own receiver busy condition, the appropriate supervisory response is the &

response.

5.5.4 Receii# RA !es

5.5.4.1 Receipt o ! !lid RA !e

On receipt of a valid 2A frame the data lin" layer entity shall act as followsF

i) if it is not in the timer recovery conditionF

5 clear an e'istin peer receiver busy conditionJ

5 set its send state variable @(!) and its ac"nowlede state variable @(-) to the value of the &() contained inthe 2A frame control fieldJ

5 reset timer T*++J

5 if it was an 2A command frame with the P bit set to , transmit an appropriate supervisory frame with the4 bit set to (see subclause 7.7.3.*)J

5 transmit the correspondin % frame as soon as possible as defined in subclause 7.7. ta"in into account theconditions iven in subclause 7.7.6.*J

5 if it was an 2A response frame with the 4 bit set to , notify a protocol violation to layer 3 by means of theM

8/19/2019 3GPP 0406-821

44/57

5 if it was an 2A command frame with the P bit set to , transmit an appropriate supervisory response framewith the 4 bit set to (see subclause 7.7.3.*).

5.5.4.2 T!#sitti# !es

1hen transmittin frames the followin conditions are to be observedF

) if the data lin" layer entity is transmittin a supervisory frame when it receives the 2A frame, it shall completethat transmission before commencin transmission of the re?uested % frameJ

*) if the data lin" layer entity is transmittin an !-/M or - or

8/19/2019 3GPP 0406-821

45/57

5 if the value of the retransmission count variable is e?ual to &*++, it shall initiate the abnormal release proceduredescribed in subclause 7.9. 8ayer 3 shall be notified via the Mpon receipt of the supervisory response with the 4 bit set to , the data lin" layer entity shall reset timer T*++, andF

5 if the response is an or 2A response, the peer receiver busy condition is cleared and the data lin" layer entitymay transmit new % frames or retransmit % frames as defined in subclauses 7.7. or 7.7.6, respectivelyJ or

5 if the response is an & response, the data lin" layer entity receivin the response shall proceed accordin to

subclause 7.7.7, first pararaph.

%f a supervisory command (, & or 2A) with the P bit set to + or , or a supervisory response frame with the 4 bit set to + is received durin the en?uiry process, the data lin" layer entity shallF

5 if the supervisory frame is an or 2A command or response frame with the 4 bit set to +, clear the peer

receiver busy condition and if the supervisory frame was a command with the P bit set to , transmit theappropriate supervisory response (see subclause 7.7.3.*) frame with the 4 bit set to . Cowever, thetransmission or retransmission of % frames shall not be underta"en until the appropriate supervisory responseframe with the 4 bit set to is received or until the e'piry of timer T*++J or

5 if the supervisory frame is an & command or an & response with the P=4 bit set to +, retain the peerreceiver busy condition, and if the supervisory frame received was an & command with the P bit set to ,transmit the appropriate supervisory response (see subclause 7.7.3.*) with the 4 bit set to .

eceivin an !-/M command, the data lin" layer entity shall clear the peer receiver busy condition.

5.5.6 :!t! li#; l!7e o/# eceie $us7 co#ditio#

1hen the data lin" layer entity enters an own receiver busy condition, it shall transmit an & frame at the earliestopportunity. The & frame may be eitherF

5 an & response with the 4 bit set to +J or

5 if this condition is entered when receivin a command frame with the P bit set to , an & response framewith the 4 bit set to J or

5 if this condition is entered on e'piry of timer T*++, an & command with the P bit set to .

-ll received % frames with the P bit set to + shall be discarded, after updatin the ac"nowlede state variable @(-).

-ll received supervisory frames with the P=4 bit set to + shall be processed, includin updatin the ac"nowlede statevariable @(-).

-ll received % frames with the P bit set to shall be discarded, after updatin the ac"nowlede state variable @(-).Cowever, an & response frame with the 4 bit set to shall be transmitted.

-ll received supervisory frames with the P bit set to will be processed includin updatin the ac"nowlede statevariable @(-). -n & response with the 4 bit set to shall be transmitted.

To indicate to the peer data lin" layer entity the clearance of the own receiver busy condition, the data lin" layer entityshall transmit an frame, or, if a previously detected &(!) se?uence error has not yet been reported, an 2A frame

with the &() set to the current value of the receive state variable @().

The transmission of an !-/M command or a >- response (in reply to an !-/M command) also indicates to the peerdata lin" layer entity the clearance of the own receiver busy condition.

5.5. H!iti# !c;#o/ledee#t

The data lin" layer entity shall maintain an internal retransmission count variable.

3GPP

3GPP TS +,-+. 0-1-) &1++1"+2',2Release )***

8/19/2019 3GPP 0406-821

46/57

%f timer T*++ e'pires, the data lin" layer entity shallF

5 if it is not yet in the timer recovery condition, enter the timer recovery condition and set the retransmission count

variable to +J or

5 if it is already in the timer recovery condition, add one to its retransmission count variable.

The data lin" layer entity shall thenF

a) if the value of the retransmission count variable is less than &*++F

5 retransmit the last transmitted % frame (@(!)5) with the P bit set to J or

5 send the appropriate supervision frame, with the P bit set to J

5 set timer T*++ riht before transmittin a frame, when the PC52-

8/19/2019 3GPP 0406-821

47/57

8ow priority data that is not discarded (i.e. previously transmitted but unac"nowleded data and up to &*+ octets ofuntransmitted data) shall be retransmitted if necessary until ac"nowleded by receivin data lin" layer entity.

5.5.8.2 Receie Re@uiee#ts

The receivin data lin" layer entity is not affected by, nor aware of, preemption at a sender.

8/19/2019 3GPP 0406-821

48/57

The data lin" layer shall remain in the same state (i e multiple frame established or timer covery) until the primitive isreceived.

5. ,ceptio# co#ditio# epoti# !#d ecoe7 o ultiple !eope!tio#

2'ception conditions may occur as the result of physical layer errors or data lin" layer procedural errors.

The error recovery procedures which are available to effect recovery followin the detection of an e'ception conditionat the data lin" layer are defined in this clause.

5..1 &(S) se@ue#ce eo

-n &(!) se?uence error e'ception condition occurs in the receiver when a valid % frame is received which contains an &(!) value which is not e?ual to the receive state variable @() at the receiver. The information field of all % frameswhose &(!) does not e?ual the receive state variable @() shall be discarded.

The receiver shall not ac"nowlede (nor increment its receive state variable) the % frame causin the se?uence error, norany % frames which may follow, until an % frame with the correct &(!) is received.

- data lin" layer entity which receives one or more % frames havin se?uence errors but otherwise error5free, orsubse?uent supervisory frames (, & and 2A), shall use the control field information contained in the &() fieldand the P or 4 bit to perform data lin" control functionsJ for e'ample, to receive ac"nowledement of previouslytransmitted % frames and to cause the data lin" layer entity to respond if the P bit is set to . Therefore, a retransmitted

% frame may contain an &() field value and P bit that are updated from, and therefore different from, the onescontained in the oriinally transmitted % frame.

The 2A frame is used by a receivin data lin" layer entity to initiate an e'ception condition recovery (retransmission)followin the detection of an &(!) se?uence error.

Only one 2A e'ception condition for a iven direction of information transfer shall be established at a time.

- data lin" layer entity receivin an 2A command or response shall initiate se?uential transmission (retransmission) of% frames startin with the % frame indicated by the &() contained in the 2A frame.

-n 2A e'ception condition is cleared when the re?uested % frame is receive or when an !-/M or

8/19/2019 3GPP 0406-821

49/57

5 an % frame with the M bit set to and the lenth indicator set to less than &*+ octets (cause % frame withincorrect use of M bit)J

5 a command or response frame with a control field which is not implemented (cause frame not implemented).

&o other action shall be ta"en as a result of such frames, i e information fields shall be discarded and &(!) fields, &()fields and P=4 bits shall be inored.

5..4 &(R) se@ue#ce eo

-n &() se?uence error e'ception condition occurs in the transmitter when a valid supervisory frame or % frame isreceived which contains an invalid &() value.

- valid &() is one that is in the rane @(-)HN&()HN@(!).

&OT2F These ine?ualities shall be interpreted in the followin wayF &() is called valid, if and only if (&()5@(-)) mod ; NH (@(!)5@(-)) mod ;.

The information field contained in an % frame which is correct in se?uence and format but contains an invalid &() shall be delivered to layer 3 by means of the primitive

8/19/2019 3GPP 0406-821

50/57

5.8.1.2 %o S"Ps ote t!# 0 o 3

The value of timer T*++ for data lin"s with !-P%s other than + or 3 is for further study.

5.8.2 M!,iu #u$e o et!#sissio#s (&200)

5.8.2.1 %o S"P

8/19/2019 3GPP 0406-821

51/57

The value of " for other values of !-P% is for further study.

5.8.5 M!,iu #u$e o octets i# ! L!7e 3 ess!e

The number of octets in a 835messae passed to layer * for transmission in ac"nowleded mode shall not e'ceed *7,due to correspondin limits in 3GPP T! +;.79.

The number of octets in a 835messae passed to layer * for transmission in unac"nowleded mode is limited by thema'imum number of octets in the information field of an >%5frame, as defined in subclause 7.;.3.

5.+ S7ste peo!#ce e@uiee#ts

-n implementation of data lin" layer service for !-P%H+ and !-P%H3 consistin of a data lin" layer entity and an entitynecessary for physical transmission on the G!M radio channels, shall have sufficient processin capacity to satisfy thefollowin performance re?uirements. Those re?uirements are to be satisfied by a local implementation without

reference to the (remote) peer implementationF

5 -vailable response delayF

%f a data lin" entity receives a data lin" command frame re?uestin response whose last burst has been physically

transmitted in the T

8/19/2019 3GPP 0406-821

52/57

Ta!le 0/3GPP TS +,-+.4 Perfor%ance Para%eters

S"P T7pe o c!##el "!il!$le Mi#iu M!,iuRespo#se Repetitio# Repetitio#:el!7 :el!7 :el!7Tesp Ti# T!, (&ote 3)

0 S:''C MS 11

SS 32

51 51

0 %"''C%ull !te (&ote 4)

+ 26 3+

0 -%"''C%ull !te + 1 26

0 %"''CC!l !te 10 34 44

3 S:''C MS 11 SS 32

51 51 (&ote 1)

3 S"''C (/it T'C) 2512+ (&ote 2) 312 416 (&ote 2)

@alues iven in this table are measured in units of T

8/19/2019 3GPP 0406-821

53/57

"##e, " (#o!tie)R!#do !ccess pocedues

".1 :esciptio# o te pocedue

".1.1 Pocedue i# te MS

The random access procedure is initiated by layer 3. The data lin" layer will receive the ; bit information content of therandom access burst in a

8/19/2019 3GPP 0406-821

54/57

"##e, G (#o!tie)C!#dli# o !es /it p!!ete eos i# te !ddess=

co#tol !#d le#t i#dic!to ieldsG.1 Ge#e!l

The parameters contained in frames received with parameter errors in the address, control and lenth indicator fieldsshall be inored and an information field shall be discarded.

4or some parameter errors an indication is iven to the mobile manaement entity in an M

8/19/2019 3GPP 0406-821

55/57

is not allowedF

-ctionsF

5 -n M

8/19/2019 3GPP 0406-821

56/57

G.4.5S"M ?" !#d ? !es

%f !-/M, >- or >% frames are received with 8R&*+ or with the M bit set to an M

8/19/2019 3GPP 0406-821

57/57

"##e, C (i#o!tie)'!#e Cisto7

Tdoc 5R Su!ject New er'e!tio# o R++ so/i# V8.0.0 $!sed upo# .0.1 8.0.0

GP-0103++ "0113 See#t!tio#Peeptio# o L'S 8.1.0

GP-020413 "0141 'oectio# o L"P: peo!#ce p!!etes o -%"''C% 8.2.0

- - tis TS c!#ed to te pese#t docue#t. PR cl!use eoed. Ce!de o!ts i# "##e,escoected

8.2.1

3GPP TS +,-+. 0-1-) &1++1"+2'2Release )***

3gpp 0406-821

Documents