3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Networ ; General Pac et Radio Ser!

ice (2011-03) "GPRS#; V10.0.0 $ase Station S%ste& "$SS# ' Technical Specification Ser!in( GPRS Support Node "SGSN# interface; Networ Ser!ice "Release )*#

3GPP TS 48.016

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

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 Or anisational Partners and shall not be implemented. This !pecification is provided for future development wor" within 3GPP only. The Or anisational 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 Or anisational Partners# Publications Offices.

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

,eywords
GSM, radio $MT!% is a Trade Mar" of &T!' re istered for the benefit of its members 3GPP% is a Trade Mar" of &T!' re istered for the benefit of its Members and of the 3GPP Or ani(ational Partners )T&% is a Trade Mar" of &T!' currently bein re istered for the benefit of its Members and of the 3GPP Or ani(ational Partners G!M* and the G!M lo o are re istered and owned by the G!M +ssociation

3GPP Postal address 3GPP support office address

650 Route des Lu io!es - So"#ia $%ti"o!is Va!&o%%e - 'R$()* Te!.+ ,33 4 -2 -4 42 00 'a.+ ,33 4 -3 65 4/ 16

'nternet
#tt"+00111.32"".or2

Copyright Notification -o part may be reproduced e.cept as authori(ed by written permission. The copyri ht and the fore oin restriction e.tend to reproduction in all media.
/ 01223 3GPP Or ani(ational Partners (+4'53 +T'!3 66!+3 &T!'3 TT+3 TT6). +ll ri hts reserved.

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

)o%te%ts
6ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 2 !cope......................................................................................................................................................9 0 4eferences..............................................................................................................................................9 3 :efinitions3 symbols and abbreviations..................................................................................................; 8 -etwor" !ervice eneral description......................................................................................................< 9 &lements for layer=to=layer communication.........................................................................................2> ; !ub=-etwor" !ervice protocol.............................................................................................................01 > -etwor" !ervice 6ontrol protocol........................................................................................................0< < General protocol error handlin ...........................................................................................................38 ? General P:$ definitions and contents.................................................................................................3; 21 General information elements codin .................................................................................................88 22 )ist of system variables......................................................................................................................92

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

'ore1ord
This Technical !pecification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor" within the T!G and may chan e followin formal T!G approval. !hould the T!G modify the contents of the present document3 it will be re=released by the T!G with an identifyin chan e of release date and an increase in version number as follows@ Aersion ..y.( where@ . the first di it@ 2 presented to T!G for informationB 0 presented to T!G for approvalB 3 or reater indicates T!G approved document under chan e control. y the second di it is incremented for all chan es of substance3 i.e. technical enhancements3 corrections3 updates3 etc. ( the third di it is incremented when editorial only chan es have been incorporated in the document.

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

S o"e

The present document specifies the -etwor" !ervice used on the 5ase !tation !ystem (5!!) to !ervin GP4! !upport -ode (!G!-) interface (Gb interface). The protocol stac" on the Gb interface is defined in the sta e 0 Technical !pecification 3GPP T! 83.1;1. The -etwor" !ervice entity provides networ" services to the 5!!GP entity specified in 3GPP T! 8<.12<. The layer 2 of the Gb interface is specified in 3GPP T! 8<.128. 'n the present document3 the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. 5ut only e.ternally observable behaviour resultin from the description is normatively prescribed by the present document. The service primitive model used in the present document is based on the concepts developed in 'T$=T 4ecommendation C.011.

Re3ere% es
4eferences are either specific (identified by date of publication3 edition number3 version number3 etc.) or non=specific. 7or a specific reference3 subseDuent revisions do not apply. 7or a non=specific reference3 the latest version applies. 'n the case of a reference to a 3GPP document (includin a G!M document)3 a non=specific reference implicitly refers to the latest version of that document in the same Release as the present document. E2F E0F E3F E8F E9F E;F E>F E<F E?F E21F E22F 3GPP T4 02.?19@ GAocabulary for 3GPP !pecificationsG. 3GPP T! 00.1;1@ GGeneral Pac"et 4adio !ervice (GP4!)B !ervice descriptionB !ta e 2G. 3GPP T! 03.1;1@ GGeneral Pac"et 4adio !ervice (GP4!)B !ervice descriptionB !ta e 0G. 3GPP T! 8<.128@ GGeneral Pac"et 4adio !ervice (GP4!)B 5ase !tation !ystem (5!!) = !ervin GP4! !upport -ode (!G!-) interfaceB Gb interface )ayer 2G. 3GPP T! 8<.12<@ GGeneral Pac"et 4adio !ervice (GP4!)B 5ase !tation !ystem (5!!) = !ervin GP4! !upport -ode (!G!-)B 5!! GP4! Protocol (5!!GP)G. 747 2.2 (2??;)@ G$ser=to=-etwor" 'mplementation + reement ($-')G. (void). 'T$=T 4ecommendation H.?02 (2??>)@ G'!:- user=networ" interface = :ata lin" layer specificationG. 'T$=T 4ecommendation H.?00 (2??0)@ G'!:- data lin" layer specification for frame mode bearer servicesG. 'T$=T 4ecommendation H.?32 (2??<)@ G'!:- user=networ" interface layer 3 specification for 5asic 6all 6ontrolG. 'T$=T 4ecommendation H.?33 (2??9)@ G:i ital !ubscriber !i nallin !ystem -o. 2 (:!! 2) = !i nallin specifications for frame mode switched and permanent virtual connection control and status monitorin G.

The followin documents contain provisions which3 throu h reference in this te.t3 constitute provisions of the present document.

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

E20F E23F E28F E29F E2;F E2>F E2<F E2?F E01F E02F

'T$=T 4ecommendation '.3>1 (2??2)@ G6on estion mana ement for the '!:- 7rame 4elayin 5earer !erviceG. 'T$=T 4ecommendation C.011 (Ihite 5oo")@ G'nformation technolo y = Open !ystems 'nterconnection = 5asic 4eference Model@ The basic modelG. +-!' T2.;10@ G'!:- = :ata )in" )ayer !i nallin !pecification for +pplication at the $ser=-etwor" 'nterfaceG. +-!' T2.;1; (2??1)@ G7rame 4elayin 5earer !ervice +rchitectural 7ramewor" and !ervice description (4 2??;)G. +-!' T2.;2> (2??2)@ G:i ital !ubscriber !ystem -o. 2 (:!!2) !i nalin !pecification for 7rame 4elay 5earer !ervice (42??>)G. +-!' T2.;2< (2??2)@ G:i ital !ubscriber !ystem -o. 2 (:!!2) 6ore +spects of 7rame 4elay Protocol for $se with 7rame 4elay 5earer !ervice (42??>)G. '&T7 476 >;< (2?<1)@ G$ser :ata ram ProtocolG (!T: ;). '&T7 476 >?2 (2?<2)@ G'nternet ProtocolG (!T: 9). '&T7 476 08;1 (2??<)@ G'nternet Protocol3 Aersion ; ('Pv;) !pecificationG. 3GPP T! 03.03;@ G'ntra=domain connection of 4adio +ccess -etwor" (4+-) nodes to multiple 6ore -etwor" (6-) nodesG.

4e3i%itio%s, s56&o!s a%d a&&re7iatio%s

3.1 4e3i%itio%s
7or the purposes of the present document3 the terms and definitions iven in 3GPP T! 00.1;1 and the followin in apply@ BSSGP Virtual Connection (BVC) end=to=end virtual communication path between remote -etwor" !ervice user entities BSSGP Virtual Connection I!enti"ier (BVCI) identifier of a 5A63 havin end=to=end si nificance across the Gb interface IP en!#oint an endpoint defined by its 'P address and $:P port. +n 'P endpoint can be a data endpoint andJor a si nallin endpoint $ata IP en!#oint an 'P endpoint used for :ata traffic Si%nallin% IP en!#oint an 'P endpoint used for !i nallin traffic $ata tra""ic data traffic for an 'P !ub=-etwor" is defined as -! !:$s for PTP and PTM functional entities (5A6' 2) Si%nallin% tra""ic si nallin traffic for an 'P !ub=-etwor" is defined as -! !:$s for !i nallin functional entities (5A6'K1) and all P:$s for 'P !ub=-etwor" !ervice 6ontrol Full Me&' Connecti(it) any 'Pv8 endpoint in an -!& is capable of communications with any 'Pv8 endpoint in its peer -!&. +lso any 'Pv; endpoint in an -!& is capable of communications with any 'Pv; endpoint in its peer -!& Net*or+ Ser(ice Entit) I!enti"ier (NSEI) identifier of an -! &ntity havin end=to=end si nificance across the Gb interface3 i.e. the peer -!&s on the 5!! side and the !G!- side are identified by the same -!&' value Net*or+ Ser(ice Virtual Connection (NS,VC) end=to=end virtual communication path between -etwor" !ervice peer entities Net*or+ Ser(ice Virtual Connection I!enti"ier (NS,VCI) identifier of an -!=A6 havin end=to=end si nificance across the Gb interface

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

Net*or+ Ser(ice Virtual Lin+ (NS,VL) virtual communication path between the 5!! or the !G!- and the intermediate networ"3 or between the 5!! and the !G!- in case of direct point=to=point confi uration Net*or+ Ser(ice Virtual Lin+ I!enti"ier (NS,VLI) identifier of an -!=A)3 havin local si nificance at the 5!! or !G!Net*or+ Ser(ice Virtual Connection Grou# roups all -!=A6s to ether which provide communication between the same peer -! entities. This roupin has local si nificance at the 5!! or !G!Bloc+e! - un.loc+e! when an -!=A6 can not be used for -! user traffic3 it is bloc"ed. Ihen an -!=A6 can be used for -! user traffic3 it is unbloc"ed $ea! - ali(e when an -!=A6 is able to provide communication between remote -! entities3 it is alive. Ihen it is not able3 it is dead. These states are supervised by means of a test procedure3 as further described in the present document Pool area an area within which an M! may roam without need to chan e the servin !G!-. + pool area is served by one or more !G!-s in parallel. +ll the cells controlled by a 5!6 belon to the same one (or more) pool area(s).

3.2 S56&o!s
7or the purposes of the present document3 the symbols iven in 3GPP T! 03.1;1 apply.

3.3 $&&re7iatio%s
7or the purposes of the present document3 the abbreviations iven in 3GPP T! 02.?19 and the followin apply@ 5&65!!GP 5A6 5A6' 6))M :& 7&674 747 'P 'Pv8 'Pv; ))6 )!P M+6 -! -!&' -!=!+P -!=A6 -!=A6' -!=A) -!=A)' P:$ PTM PTP PA6 4)6 !G!!-! $:P $-' 5ac"ward &.plicit 6on estion -otification 5ase !tation !ystem GP4! Protocol 5!!GP Airtual 6onnection 5!!GP Airtual 6onnection 'dentifier 6onsolidated )in" )ayer Mana ement :iscard &li ibility 7orward &.plicit 6on estion -otification 7rame 4elay 7rame 4elay 7orum 'nternet Protocol 'nternet Protocol version 8 'nternet Protocol version ; )o ical )in" 6ontrol )in" !elector Parameter Medium +ccess 6ontrol -etwor" !ervice -etwor" !ervice &ntity 'dentifier -etwor" !ervice !ervice +ccess Point -etwor" !ervice Airtual 6onnection -etwor" !ervice Airtual 6onnection 'dentifier -etwor" !ervice Airtual )in" -etwor" !ervice Airtual )in" 'dentifier Protocol :ata $nit Point=To=Multipoint Point=To=Point Permanent Airtual 6onnection 4adio )in" 6ontrol !ervin GP4! !upport -ode !ub=-etwor" !ervice $ser :ata ram Protocol $ser=to=-etwor" 'nterface

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

(et1or8 Ser7i e 2e%era! des ri"tio%

4.1 97er7ie1
The position of the -etwor" !ervice within the protocol stac" of the Gb interface is shown in fi ure 8.2.2.
))6 4&)+L 4)6 M+6 5!!GP -! )2 5!!GP -! )2 Gb

5!! (9T*+

!G!-

:SSGP, L1, LL), M$), R*L$;, RL) are outside t#e s o"e o3 t#e "rese%t do u6e%t, re3er to 3GPP TS 43.060 3or 3urt#er detai!s.

3i(ure +-)-)4 Position of the NS within the G5 interface protocol stac The -etwor" !ervice performs the transport of -! !:$s between the !G!- and 5!!. The services provided to the -! user shall be@ = -etwor" !ervice !:$ transfer. The -etwor" !ervice entity shall provide networ" service primitives allowin for transmission and reception of upper layer protocol data units between the 5!! and !G!-. The -! !:$s are transferred in order by the -etwor" !ervice3 but under e.ceptional circumstances order may not be maintained. -etwor" con estion indication. 6on estion recovery control actions may be performed by the !ub=-etwor" !ervice (e. . 7rame 4elay). 6on estion reportin mechanisms available in the !ub=-etwor" !ervice implementation shall be used by the -etwor" !ervice to report con estion. !tatus indication. !tatus indication shall be used to inform the -! user of the -! affectin events e. . chan e in the available transmission capabilities.

The -etwor" !ervice entity is composed of an entity dependent on the intermediate transmission networ" used on the Gb interface3 the !ub=-etwor" !ervice3 and of a control entity independent from that networ"3 the -etwor" !ervice 6ontrol. There is a hierarchical relationship between both entities. This is reflected in fi ure 8.2.0. The detailed communication mechanisms between both entities is an internal matter for the -etwor" !ervice and is not further standardi(ed.

-etwor" !ervice

-etwor" !ervice 6ontrol J -etwor" !ervice 6ontrol protocol

!ub=-etwor" !ervice J !ub=-etwor" !ervice protocol

3i(ure +-)-04 6nternal architecture of the Networ Ser!ice

ETSI

Release )*

3GPP TS +,-*). /)*-*-* "0*))'*3#

The !ub=-etwor" !ervice entity provides a communication service to -etwor" !ervice 6ontrol peer entities. The -etwor" !ervice 6ontrol peer entities use the !ub=-etwor" !ervice for communication with each other. The peer=to= peer communication accross the Gb interface between remote -etwor" !ervice 6ontrol entities is performed over -etwor" !ervice Airtual 6onnections (-!=A6s). +n -!=A6 is a virtual communication path between -etwor" !ervice 6ontrol peer entities. The -etwor" !ervice entity provides a communication service to -! user peer entities@ the peer=to=peer communication between remote -! user entities is performed over 5!!GP Airtual 6onnections (5A6s). + 5A6 is a virtual communication path between -etwor" !ervice user peer entities. + -etwor" !ervice &ntity communicates with only one peer -etwor" !ervice &ntity. +ddressin across the Gb interface is further detailed in the rest of the present document. The -etwor" !ervice 6ontrol entity is responsible for the followin functions@ = = = -! !:$ transmission@ The -! !:$s shall be transmitted on the -!=A6s. The -! !:$s are encapsulated into -etwor" !ervice 6ontrol P:$s which in turn are encapsulated into !ub=-etwor" !ervice P:$s. )oad sharin @ The load sharin function distributes the -! !:$ traffic amon st the available (i.e. unbloc"ed) -!=A6s of a roup. -!=A6 mana ement@ + bloc"in procedure is used by an -! entity to inform an -! peer entity when an -!=A6 becomes unavailable for -! user traffic. +n unbloc"in procedure is used for the reverse operation. + reset procedure is used between peer -! entities in order to set an -!=A6 to a determined state3 after events resultin in possibly inconsistent states of the -!=A6 at both sides of the Gb interface. + test procedure is used to chec" that an -!=A6 is operatin properly between peer -! entities.

4.2 $ddressi%2
The purpose of this sub=clause is to describe the addressin principles on the Gb interface in a eneric way3 i.e. irrespective of the e.act confi uration of the Gb interface and of the e.act nature of the intermediate transmission networ"3 when present. Therefore3 this sub=clause provides an abstract description of the addressin principles. These principles are then applied to real networ"s in sub=clause G!ub=-etwor" !ervice protocolG. 'n this sub=clause3 addressin is considered in the eneral case where an !G!- is connected to several 5!!s via an intermediate transmission networ" and in the specific case where a 5!! is connected to several !G!-s within one or more pool areas3 see 3GPP T! 03.03;. Point=to=point physical connections may also be used3 addressin in this special case can be derived from the eneral case.

4.2.1 (et1or8 Ser7i e Virtua! Li%8 ((S-VL)

+n !G!- and a 5!! may use different physical lin"s for connectin to each other (e. . because of intermediate eDuipment or transmission networ"). &ach physical lin" is locally (i.e. at each side of the Gb interface) identified by means of a physical lin" identifier. The e.act structure of the physical lin" identifier is implementation dependent. &ach physical lin" supports one or more -etwor" !ervice Airtual )in"s (-!=A)s). &ach -!=A) is supported by one physical lin" if the 7rame 4elay !ub=-etwor" is employed. 7or an 'P sub=networ"3 the -!=A) is mapped to an 'P endpoint. The e.act nature of the -!=A) depends on the intermediate networ" used on the Gb interface. 'n the eneral case of an intermediate transmission networ"3 the -!=A) is used to access the intermediate networ". 6ommunication means internal to the intermediate networ" are outside the scope of the present document. The -!=A)s may alternatively be used end=to=end between the 5!! and !G!-3 in case of a point=to=point confi uration on the Gb interface. &ach -!=A) may be identified by means of a -etwor" !ervice Airtual )in" 'dentifier (-!=A)'). The si nificance (i.e. local or end=to=end) and the e.act structure of the -!=A)' depends on the confi uration of the Gb interface and on the intermediate networ" used. 7or e.ample3 in the case of a 7rame 4elay networ"3 the physical lin" is the 74 bearer channel3 the -!=A) is the local lin" (at $-') of the 74 permanent virtual connection (PA6) and the -!=A)' is the association of the 74 :)6' and bearer channel identifier.

ETSI

Release )*

)*

3GPP TS +,-*). /)*-*-* "0*))'*3#

4.2.2 (et1or8 Ser7i e Virtua! )o%%e tio% ((S-V))

'n order to provide end=to=end communication between the 5!! and !G!- irrespective of the e.act confi uration of the Gb interface3 the concept of -etwor" !ervice Airtual 6onnection (-!=A6) is used. The -!=A6s are end=to=end virtual connections between the 5!! and !G!-. 'n the case of a 74 sub=networ"3 at each side of the Gb interface there is a one=to=one correspondence between -!=A6s and -!=A)s. Ihen employin an 'P=sub=networ" one -!=A) may serve several -!=A6s (see fi ure 8.0.0.2).
BSS NSEI/0 SGSN NSEI/0

U$P -IP
A
I NS ,VL

-!=A62 ($:P +J'P23$:P5J'P3)

U$P -IP
B
III NS ,VL

-!=A60 ($:P+J'P23 $:P6J'P3)

U$P -IP
A
II NS ,VL

U$P -IP
-!=A63 ($:P +J'P03 $:P5J'P3) -!=A68 ($:P +J'P03 $:P6J'P3)
C
IV NS ,VL

3i(ure +-0-0-)4 6P su5'networ relationship 5etween NS'/8s and NS'/9s 7or e.ample3 in the case of a 7rame 4elay networ"3 the -!=A6 is the 74 permanent virtual connection (PA6). 7i ure 8.0.0.0 shows the relationship between -!=A6s and -!=A)s for a 7rame 4elay sub=networ". 'n the case of an 'P networ"3 the -!=A6 is iven by a pair of 'P endpoints at the 5!! and !G!-. Ihile 7i ure 8.0.0.2 illustrates a confi uration with only one -!&3 multiples -!& in either the 5!! or !G!- are allowed. +t the 5!!3 the 'P endpoints for each -!& shall not be shared amon -!&s connected to the same !G!-. Mowewer3 an 'P endpoint at the 5!! may serve multiple -!&s when each of the -!&s is connected towards different !G!-s. +t the !G!-3 an 'P endpoint may serve multiple -!&sB (i.e. 'P endpoints may be shared amon -!&s).

end=to=end -!=A6

intermediate transmission networ" !G!-

5!!

-!=A) at the 5!! side

-!=A) at the !G!- side

3i(ure +-0-0-04 3ra&e rela% su5'networ relationship 5etween NS'/8s and NS'/9s

ETSI

Release )*

))

3GPP TS +,-*). /)*-*-* "0*))'*3#

&ach -!=A6 is identified by means of a -etwor" !ervice Airtual 6onnection 'dentifier (-!=A6') havin end=to=end si nificance across the Gb interface. +n -!=A6' uniDuely identifies an -!=A6 within an !G!- and within a 5!!. The establishment of an -!=A6 includes the establishment of physical lin"s3 see 3GPP T! 8<.1283 and of -!=A)s. 'n the case of an 74 sub=networ" -!=A6s and -!=A)s are permanently established by means of administrative procedures3 -!=A6's are allocated by administrative means as well. The mappin of -!=A6's on -!=A)'s and on physical lin" identifiers is held in non=volatile memory. Ihen employin an 'P sub=networ" the -!=A6s and -!=A)s may be established by means of administrative means (static confi uration) or by auto=confi uration procedures (dynamic confi uration).

4.2.3 (et1or8 Ser7i e Virtua! )o%%e tio% Grou"

The -etwor" !ervice Airtual 6onnection Group roups to ether all -!=A6s providin communication between the same peer -! entities. One -!=A6 roup is confi ured between two peer -! entities. This roupin is performed by administrative means. +t each side of the Gb interface3 there is a one=to=one correspondence between a roup of -!= A6s and an -!&'. The -!&' has an end=to=end si nificance across the Gb interface.

4.2.4 :SSGP Virtua! )o%%e tio% (:V))

The -etwor" !ervice provides communication paths between remote -! user entities. These communication paths are called 5!!GP Airtual 6onnections (5A6s). &ach 5A6 is used to transport -! !:$s between -! users. + -etwor" !ervice &ntity provides one or more 5A6s between peer -! user entities. &ach 5A6 is supported by one roup of -!=A6s. &ach roup of -!=A6s supports one or more 5A6s. The -! entity maps between 5A6 and the related -!=A6 roup. &ach 5A6 is identified by means of a 5!!GP Airtual 6onnection 'dentifier (5A6') havin an end=to=end si nificance across the Gb interface. The 5A6' to ether with the -!&' uniDuely identifies a 5A6 within an !G!-. The 5A6' and -!&' are used on the -etwor" !ervice=!ervice +ccess Point (-!=!+P) for layer=to=layer communication.

ETSI

Release )*

)0

3GPP TS +,-*). /)*-*-* "0*))'*3#

4.2.5 <se o3 )o% e"ts o% t#e G& =%ter3a e 1#e% =%tra 4o6ai% )o%%e tio% o3 R$( (odes to Mu!ti"!e )( (odes a""!ies i% t#e :SS
BSS 2 SGSN 2

5A6'K3

-!&'K2

-!=A6 2 -!=A6 0

-!&'K2

5A6'K8 4adio cell 2

4adio cell 0

SGSN 0 5A6'K3

-!&'K0
5A6'K9

-!=A6 3 -!=A6 8

-!&'K0

3i(ure +-0-0-34 :se of G5 8oncepts when 6ntra Do&ain 8onnection of RAN Nodes to Multiple 8N Nodes applies in the $SS 7or a pool area the 5!! sets up several -!&s3 and each of these -!&s oes towards different !G!-s. 'n this way the 5!! have one -!& towards each of the connected !G!-s. +lternatively3 several -!&s in the 5!! are connected towards each of the !G!-s supportin the pool area. One or more -!=A6s are set up between each of the -!&s in the 5!! and the correspondin peer -!&s in the !G!-s. 'n an 'P networ"3 an -!=A6 is identified by a pair of 'P addresses and $:P ports at both the 5!! and the !G!-. 'n a 74 networ"3 the identity of an -!=A6 is uniDue within an -!&'.

4.3 Su&-(et1or8 Ser7i e 3u% tio%s

The !ub=-etwor" !ervice functions of the -etwor" !ervice shall provide access to the intermediate networ" (or to the peer entity in case of direct point=to=point confi uration) by means of -!=A)s and shall provide -!=A6s between -! peer entities. On each -!=A63 data are transferred in order by the !ub=-etwor" !ervice. Ihen the !ub=-etwor" !ervice entity detects that an -!=A6 becomes unavailable (e. . upon failure detection)3 or when the -!=A6 becomes available a ain (e. . after failure recovery)3 the -etwor" !ervice 6ontrol entity shall be informed. 7ailures may occur due to protocol errors3 intermediate transmission networ" failure3 eDuipment or lin" failure or other reasons.

ETSI

Release )*

)3

3GPP TS +,-*). /)*-*-* "0*))'*3#

4.4 Load s#ari%2 3u% tio%

4.4.1 Load S#ari%2 3u% tio% 3or t#e 'ra6e Re!a5 Su&-(et1or8
4.4.1.1 97er7ie1

The load sharin function distributes the -! !:$ traffic amon the unbloc"ed -!=A6s of the same roup on the Gb interface. The use of load sharin also provides to the upper layer seamless service upon failure by re=or ani(in the -! !:$ traffic between the unbloc"ed -!=A6s of the same roup. The re=or ani(ation may disturb the order of transferred -! !:$s. The load sharin function should be implemented in both the 5!! and the !G!-. )oad sharin applies only to -! !:$s3 not to -! si nallin such as -!=A6 mana ement P:$s.

4.4.1.2

Re>uire6e%ts o% !oad s#ari%2 3u% tio%

+ll -! !:$s to be transmitted over the Gb interface are passed to the load sharin function alon with the )in" !elector Parameter ()!P) 3 the 5A6' and the -!&'. )!P and 5A6' are used by the -! entity to select amon st the unbloc"ed -!=A6s within the roup3 addressed by means of the -!&'3 where to send the -! !:$. The mappin between )!P and -!=A6 is based on an implementation dependent function that meets the followin reDuirements@ = = 7or each 5A6 and -!&'3 the -! entity selects the -!=A6 out of the roup based on the )!P. This is an internal matter for the -! entity and it is not subject to further standardi(ation. 7or each 5A6 and -!&'3 -! !:$s with the same )in" !elector Parameter shall be sent on the same -!=A6. Thus3 the load sharin function uarantees that3 for each 5A63 the order of all -! !:$s mar"ed with the same )!P value is preserved. 'n the event of a lin" failure and subseDuent re=or ani(ation of the -! !:$ traffic between the unbloc"ed -!=A6s3 the receiver may et out of order -! !:$s. 7urther actions implemented to prevent this error are outside the scope of the present document. )oad sharin functions at the 5!! and the !G!- are independent. Therefore3 uplin" and downlin" -! !:$s for a subscriber may be transferred over different -!=A6s. + chan e in -!=A6s available for -! user traffic (i.e. one or more -!=A6s become bloc"ed or unbloc"ed) shall result in a re=or ani(ation of the -! !:$ traffic amon st the unbloc"ed -!=A6s of the same roup. 7or a 5A63 when there is no unbloc"ed -!=A6 of the roup left between a 5!! and a !G!-3 the correspondin traffic is discarded by the -! at the sendin side.

= = =

The )in" !elector Parameter is locally used at the 5!! and at the !G!- and shall not be transmitted across the Gb interface.

4.4.2 Load s#ari%2 3u% tio% 3or t#e =P Su&-(et1or8

4.4.2.1 97er7ie1

The load sharin function distributes the -! !:$s and !-! P:$s traffic amon the available 'P endpoints on the Gb interface. The use of load sharin also provides to the upper layer seamless service upon failure by re=ne otiatin the -! !:$ traffic between the remainin 'P endpoints. The re=ne otiation may disturb the order of transferred -! !:$s. The load sharin function shall be implemented in both the 5!! and the !G!-. The load sharin function for the 'P sub=networ" determines the local 'P endpoint locally and the remote 'P endpoint based on wei ht information provided by the peer -!&. &ach -!& shall use an implementation dependent load sharin function to determine the local 'P endpoint associated with all -! !:$ traffic related to an M!. The remote 'P endpoint shall initially be determined by an implementation dependent load sharin function that distributes the traffic in eDual proportion to the relative wei hts assi ned to the peer -!&#s endpoints. These relative wei hts are assi ned by the peer -!& for both si nallin traffic and data traffic and will be referred to as si nallin wei ht and data wei ht respectively. (These relative wei hts are communicated usin the !-!=6O-7'G3 !-!=+::3 and !-!=6M+-G&=I&'GMT P:$s. +lso3 the remote 'P endpoint can be chan ed by the peer -!& via the 4esource :istribution 7unction (refer to sub= clause 8.8a.).

ETSI

Release )*

)+

3GPP TS +,-*). /)*-*-* "0*))'*3#

4.4.2.2

Se!e tio% o3 t#e !o a! =P e%d"oi%t

The )!P is used by an -! entity to select amon st the available local 'P endpoints for the iven -!&'3 from which the -! !:$s are sent. The association between an )!P and a local 'P endpoint is based on an implementation dependent function that meets the followin reDuirements@ = 7or each -!=!:$3 an -! entity selects a local 'P endpoint based on the )!P for sendin the -!=!:$ to the peer -!&. 'f the )!P has not been associated with a local 'P endpoint3 then a local 'P endpoint shall be selected by a method that is implementation dependent. This is an internal matter for the -! entity and it is not subject to further standardisation. Once a local 'P endpoint is selected for the )!P3 the -!& should maintain a lin"a e between the )!P and the local 'P endpoint so that -! !:$s with the same )in" !elector Parameter shall be sent from the same local 'P endpoint. The -!& may disassociate the M! from the last used local 'P endpoint when an M! ma"es a cell chan e. 'f a local 'P endpoint that has been mapped to an )!P is ta"en out of service3 a new local 'P endpoint shall be selected and associated with the )!P. !election of the local 'P endpoint occurs locally at each -!&. 'f there is no available local 'P endpoint3 the correspondin traffic is discarded by the -! at the sendin side.

= = =

The )in" !elector Parameter is locally used at the 5!! and at the !G!- and shall not be transmitted across the Gb interface.

4.4.2.3

Se!e tio% o3 t#e re6ote =P e%d"oi%t

+ remote 'P endpoint is an 'P address and $:P port that the peer -!& has made "nown to the local -!& (e. . usin the 6onfi uration procedure). 'n addition to bein used to select the local 'P endpoint3 the )!P is also used by the -! entity to select amon st the available remote 'P endpoints for the iven -!&'3 to which the -! !:$s are sent. The selection of the remote 'P endpoint for an )!P is initially based on the si nallin wei ht and data wei ht of the remote 'P endpoints. +lso3 the 4esource distribution function can be used by the peer -!& to initially reDuest or subseDuently chan e the remote 'P endpoint selection for an )!P.

4.4.2.3.1

Se!e tio% o3 re6ote =P e%d"oi%t 3or data tra33i

7or each -!=!:$3 an -! entity selects a remote 'P endpoint based on the )!P for sendin the -!=!:$ to the peer -!&. 'f the )!P has not been associated with a remote 'P endpoint3 then a remote 'P endpoint shall be selected for the )!P accordin to the data=wei hts assi ned to the peer -!&#s 'P endpoints. The remote 'P endpoints shall be selected in eDual proportion to the data=wei hts assi ned to the peer -!&#s endpoints. :ata=wei hts are assi ned by the peer -!& and have a value ran e of 1 to 099. + data wei ht of 1 assi ned to an 'P endpoint indicates that the load sharin function shall not initially associate this remote 'P endpoint to an )!P. Mowever3 if an )!P has been previously associated with a remote 'P endpoint3 -! !:$s associated with this )!P shall be sent to this remote 'P endpoint re ardless of its data wei ht3 i.e.3 even when the data wei ht has a value of 1. (This association of )!P to the 'P endpoint with a data wei ht of 1 may have been reDuested by the remote -!& via the 4esource :istribution 7unction.) &.amples of eDual proportion selection@ = = = 'f 'P endpoint (+) has data wei htK9 and endpoint (5) has data wei htK213 then endpoint (5) will be selected for initial association with an )!P twice as often as endpoint (+). 'f 'P endpoint (+) has data wei htK21 and endpoint (5) has data wei htK213 then endpoint (+) and endpoint (5) will be selected for initial association with an )!P on an eDual basis. 'f 'P endpoint (+) has a data wei htK13 then 'P endpoint (+) will not be selected for initial association with an )!P. Mowever3 'P endpoint (+) may be associated with an )!P via the peer -!&#s use of the 4esource :istribution 7unction.

Once a remote 'P endpoint is selected for the )!P3 the -!& should maintain a lin"a e between the )!P and the remote 'P endpoint so that -! !:$s with the same )!P shall be directed to the same remote 'P endpoint. 'f a remote 'P endpoint associated with an )!P is ta"en out of service3 then another remote 'P endpoint shall be selected accordin to

ETSI

Release )*

)1

3GPP TS +,-*). /)*-*-* "0*))'*3#

the data=wei hts assi ned by the peer -!& and associated with the )!P. The association of an )!P to a remote 'P endpoint can be chan ed by the peer -!& usin the 4esource :istribution function (refer to sub=clause 8.8a). The 5!! may disassociate the )!P from the remote 'P endpoint when an M! ma"es a cell chan e or when the M! conte.t is deleted. The !G!- shall associate an M! with the last used remote 'P endpoint as lon as the !G!- has location information for the M! on cell level. The )in" !elector Parameter is locally used at the 5!! and at the !G!- and shall not be transmitted across the Gb interface.

4.4.2.3.2

Se!e tio% o3 re6ote =P e%d"oi%t 3or si2%a!!i%2 tra33i

Out oin 5A6'K1 -!=!:$s3 or !-! P:$s shall be sent to a remote 'P endpoint accordin to the si nallin wei ht assi ned by the peer -!&. The sendin -!& shall distribute these messa es in eDual proportion to the si nallin wei hts assi ned to the peer -!&#s 'P endpoints. The sendin -!& may send the 5A6'K1 -!=!:$s and all !-! P:$s from any 'P endpoint. -OT&@ )oad sharin endpoint selection does not apply to -!=!:$s or !-! P:$s subject to specific conditions stipulated elsewhere in the present specification3 such as !-!=!'N& and !-!=6O-7'G P:$s that need to be sent to an !G!- pre=confi ured endpoint3 or any ac"nowled ement J response that needs to be sent bac" to the endpoint havin ori inated the correspondin reDuest.

&.amples of eDual proportion selection@ = = = 'f 'P endpoint (+) has si nallin wei htK9 and 'P endpoint (5) has si nallin wei htK213 then 'P endpoint (5) will be selected as a si nallin 'P endpoint twice as often as 'P endpoint (+). 'f 'P endpoint (+) has si nallin wei htK21 and 'P endpoint (5) has si nallin wei htK213 then 'P endpoint (+) and 'P endpoint (5) will be selected as a si nallin 'P endpoint on an eDual basis. 'f 'P endpoint (+) has a si nallin wei htK13 then 'P endpoint (+) will not be selected as a si nallin 'P endpoint.

'f there is no available remote 'P endpoint3 the correspondin traffic is discarded by the -! at the sendin side. The )in" !elector Parameter is locally used at the 5!! and at the !G!- and shall not be transmitted across the Gb interface.

4.4a Resour e distri&utio% 3u% tio%

The resource distribution function is only available for data traffic when an 'P sub=networ" is used. This function allows the 5!! or !G!- to e.plicitly chan e the 'P endpoint at which it receives -! !:$s. The 5!! or !G!- may choose not to initiate any reDuest for chan e in 'P endpoints for any M! or M5M! session and rely on the underlyin load sharin function to properly distribute -! user traffic. Mowever3 if the 5!! or !G!- receives a reDuest to chan e the 'P endpoint at which -! !:$s are received for an M! or M5M! session3 then the hi her layers shall be informed of this chan e by an indication in the )in" !elector Parameter. That is3 if the !G!- (5!!) receives a reDuest to chan e the remote 'P endpoint for an M! or M5M! session then subseDuent downlin" (uplin") data for the mobile or M5M! session shall be sent to that remote 'P endpoint indicated by the reDuest. The 4esource :istribution 7unction overrides the )oad !harin function for the selection of the remote 'P endpoint. The 4esource :istribution 7unction overrides the data wei ht of a remote 'P endpoint (i.e. the 4esource :istribution 7unction can reDuest that data be sent to an 'P endpoint that has a data wei htK1).

4.4a.1 Re>uire6e%ts o% resour e distri&utio% 3u% tio%

'n an 'P sub=networ" the 5!! or !G!- may receive an -! !:$ with a reDuest to chan e the remote 'P endpoint. The tri ers for eneratin a reDuest are implementation dependent and are not subject to further standardi(ation. The behaviour on receipt of a reDuest shall meet the followin reDuirements@ = +n -!& may chan e the 'P endpoint at which the -! !:$s for an M! are received by settin the 4=bit field to G2G (4eDuest chan e flow) in the NS SDU Control Bits '& in the ne.t -! !:$ or in an -! !:$ with no data.

ETSI

Release )*

).

3GPP TS +,-*). /)*-*-* "0*))'*3#

-OT&@ = =

The 5!!GP :)=$-'T:+T+ (5!!GP $)=$-'T:+T+) and the 5!!GP $)=M5M!=$-'T:+T+ with an ))6=P:$ )en th 'ndicator set to 1 are iven in 3GPP T! 8<.12<.

+n -!& shall only act on a reDuest for chan e in 'P endpoint if the new 'P endpoint has previously been confi ured and is operational. 7or M5M!3 the resource distribution function is only available at the 5!! side. That is3 it is only the 5!! that can reDuest a chan e of the 'P endpoint to which the -! !:$s for an M5M! session are sent while M5M! data flows are only present in the downlin" direction. $pon receivin a reDuest for chan e in 'P endpoint3 an -!& shall notify the -! user entity of the chan e by an indication in the )in" !elector Parameter (that is3 the 'P endpoint at the peer entity) and direct subseDuent -! !:$s for the iven M! or M5M! session to the new 'P endpoint. The resource distribution functions are independent at the 5!! and the !G!-. That is3 each entity may independently choose the 'P endpoint at which -! !:$s for an M! or M5M! session are received. +n -!& shall obtain the new 'P endpoint from the source 'P endpoint (i.e. in the $:PJ'P header) of the -! !:$ in which the 4eDuest 6han e 7low bit was set. The new 'P &ndpoint is not e.plicitly transmitted over the Gb. The 5!! shall associate an M! with the last used remote 'P endpoint as lon as the M! conte.t e.ist in the 5!! or until the M! ma"es a cell chan e. The !G!- shall associate an M! with the last used remote 'P endpoint as lon as the !G!- has location information for the M! on cell level. The !G!- shall associate an M5M! session with the last used remote 'P endpoint for the duration of the M5M! session.

= = = = =

4.5 (S-V) 6a%a2e6e%t 3u% tio%

The -!=A6 mana ement function is responsible for the bloc"in J unbloc"in 3 reset and test of -!=A6s.

4.5.1 :!o 8i%2 0 u%&!o 8i%2 o3 a% (S-V)

The bloc"in J unbloc"in procedures shall not be used for an 'P !ub=networ". Ihen a condition ma"in an -!=A6 unavailable for -! user traffic is locally detected at the 5!! or at the !G!-3 the -!=A6 shall be mar"ed as bloc"ed by the local -! entity and the remote -! peer entity shall be informed by means of a bloc"in procedure. The remote -! entity shall then mar" the -!=A6 as bloc"ed and shall consider it as unavailable for -! user traffic. + 5!! or !G!- may bloc" an -!=A6 because of@ = = = = = Operation and Maintenance intervention at the Gb interface ma"in the -!=A6 unavailable for -! user trafficB eDuipment failure at a 5!! or an !G!- entityB eDuipment or lin" failure on a 5!! or an !G!- siteB failure in the transit networ"B or other causes.

Ihen the -!=A6 becomes available a ain for -! user traffic3 the -! entity which initiated the bloc"in procedure may inform the remote -! peer entity by means of an unbloc"in procedure. The remote -! entity shall then mar" the -!= A6 as unbloc"ed and shall consider it as available for -! user traffic. The bloc"in J unbloc"in procedures are further detailed in the rest of the present document.

4.5.2 Reset o3 a% (S-V)

The reset procedure shall not be used for an 'P !ub=networ".

ETSI

Release )*

)2

3GPP TS +,-*). /)*-*-* "0*))'*3#

This procedure is used to reset one -!=A6 to a determined state between remote entities. This procedure is performed@ = = = = when a new -!=A6 is set=upB after a processor re=startB after a failure recovery when the state of an -!=A6 must be set to bloc"ed and aliveB or at any local event restorin an e.istin -!=A6 in the dead state or in an undetermined state.

Ihen a reset procedure is initiated3 data in transfer may be lost.

4.5.3 Test o3 a% (S-V)

The test procedure is used to chec" that end=to=end communication e.ists between peer -! entities on a iven -!=A6. Ihen end=to=end communication e.ists3 the -!=A6 is in the GaliveG state3 otherwise it is in the GdeadG state. + dead -!=A6 can not be in the Gunbloc"edG state.

*!e6e%ts 3or !a5er-to-!a5er o66u%i atio%

This sub=clause presents the -etwor" !ervice in a eneric way3 no assumptions are made re ardin the real protocols providin the networ" services.

5.1 Ser7i e "ri6iti7e 6ode!

The service primitive model shown in fi ure 9.2.2 is applicable to both 5!! and !G!-.

-etwor" !ervice user

G!M 1<.2<

-!=!+P

-etwor" !ervice

G!M 1<.2;

3i(ure 1-)-)4 Networ Ser!ice pri&iti!e &odel The networ" services are provided at the -etwor" !ervice=!ervice +ccess Point (-!=!+P).

5.2 Ser7i e "ri6iti7es a%d "ara6eters

The -etwor" !ervice primitives are summari(ed in table 9.0.2. The eneral synta. of the -etwor" !ervice primitives is@ -! = Generic name = Type (Parameters).

ETSI

Release )*

),

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ta5le 1-0-)4 Networ Ser!ice pri&iti!es

Generic na&e <(=T4$T$ Re;uest ? T%pe 6ndication ? Para&eters Response 8onfir& - :V)= a%d (S*= - (S S4< - (S )#a%2e =P e%d"oi%t - Li%8 Se!e tor Para6eter - :V)= a%d (S*= - o%2estio% ause - :V)= a%d (S*= - (S a33e ti%2 ause - tra%s3er a"a&i!it5

)9(G*ST=9( ST$T<S

? ?

5.2.1 Pri6iti7es
5.2.1.1 (S-<(=T4$T$-Re>uest

This primitive is used by the -! user entity to send a -! !:$ to its peer entity via a 5A6. The -! entity sends the -! !:$ in unac"nowled ed mode. The )in" !elector Parameter is used to identify the -! !:$s which must be sent in order relatively to each other. The -!&' is used by the -! entity to select the roup of -!=A6s correspondin to the addressed remote entity. The -! 6han e 'P endpoint is used to reDuest the -! entity to indicate whether a GreDuest chan e flowG or Gconfirm chan e flowG indication needs to be sent to its peer entity.

5.2.1.2

(S-<(=T4$T$-=%di atio%

This primitive is used by the -! entity to provide the -! user entity with a -! !:$ received on a virtual connection. The -! !:$ are received in unac"nowled ed mode. 5A6' to ether with -!&' indicate which 5A6 the -! !:$ was received on. The -! 6han e 'P endpoint is used to indicate to the user of the -! entity whether a GreDuest chan e flowG or Gconfirm chan e flowG indication was received from the peer entity. 'n case a GreDuest chan e flowG is received from the peer entity the )in" !elector Parameter on which the -! !:$ was received is sent to the hi her layer.

5.2.1.3

(S-)9(G*ST=9(-=%di atio%

The -! entity shall be able to detect when a con estion situation starts and ends on an -!=A6. This primitive is used by the -! entity to report to the -! user entity that con estion is detected or that the con estion situation has disappeared. The 5A6' and -!&' of the affected 5A6 and the con estion cause are reported to the -! user entity. Typically3 the cause indicates the direction of transmission affected by the con estion.

5.2.1.4

(S-ST$T<S-=%di atio%

There may be situations where an -!=A6 becomes unavailable for -! user traffic. Ihen this occurs3 the -! user is informed of the de radation of the transfer capacity by means of this primitive includin the Gtransfer capabilityG parameter. Ihen an -!=A6 previously unavailable for -! user traffic becomes available a ain3 the -! user entity is also informed by means of this service primitive3 indicatin the current transfer capability. This primitive may be used in response to an -!=$-'T:+T+=4eDuest primitive which the -! is unable to serve because of e. . -!=A6 failure. This primitive may also be used upon recovery after a failure affectin the -!.

5.2.2 Para6eters
5.2.2.1 (S S4<

The -! !:$s are specified in 3GPP T! 8<.12<. They shall never be inspected by the -etwor" !ervice entity.

ETSI

Release )*

)7

3GPP TS +,-*). /)*-*-* "0*))'*3#

5.2.2.2

Li%8 Se!e tor Para6eter

The )in" !elector Parameter is included in the -!=$-'T:+T+=4eDuest primitive for load sharin purposes as described in sub=clause G4eDuirements on load sharin functionG. The )in" !elector Parameter is included in the -!=$-'T:+T+='ndication primitive and in the -!=$-'T:+T+= 4eDuest primitive for resource distribution purposes as described in sub=clause 8.8a.2. The )in" !elector Parameter shall include a reference to the local 'P endpoint and the remote 'P endpoint for resource distribution purposes if the -! 6han e 'P endpoint parameter has the cause value of GreDuest chan e flowG.

5.2.2.3

:V)= = a%d (S*=

5A6' and -!&' parameters are included in the service primitives to identify the 5A6 for which the service is provided. These parameters are used by the -! entity to multiple. the -! !:$s over the -!=A6s.

5.2.2.4

)o%2estio% ause

The con estion cause shall indicate the affected direction of transmission and may be set to the followin values@ a) con estion detected3 bac"wardB b) end of con estion3 bac"wardB c) con estion detected3 forwardB d) end of con estion3 forward.

5.2.2.5

Tra%s3er a"a&i!it5

This parameter is used to report to the -! user entity the current transfer capacity available for a 5A63 in terms of bandwidth. This parameter may be set to any value from G1G ((ero) to the ma.imum bandwidth provided by the complete set of -!=A6s associated to the 5A6.

5.2.2.6

(S a33e ti%2 ause

This parameter is used to indicate to the -! user entity the reason which caused the -!=!T+T$!='ndication primitive to be used. The cause values are@ -!=A6 failure@ -!=A6 recovery@ -! failure@ -! recovery@ a failure is affectin one or more -!=A6s3 the -! is still available. one or more -!=A6s which were in failure are available a ain. the -! can not provide data transfer services to the -! user. the -! can provide data transfer services a ain.

5.2.2./ (S #a%2e =P e%d"oi%t

The -! chan e 'P endpoint parameter is included in the -!=$-'T:+T+=4eDuest and -!=$-'T:+T+='ndication primitive for resource distribution purposes. This parameter is used in an 'P sub=networ" to indicate to the -! user entity a reDuest for chan e in 'P endpoint or a response to a chan e in 'P endpoint. The cause values are@ 4eDuest chan e flow@ 6onfirm chan e flow@ 4eDuest to chan e the 'P endpoint at which to receive -! !:$s associated with a subscriber or M5M! session. 6onfirmation to a reDuest for chan e of 'P endpoint of -! !:$s associated with a subscriber or M5M! session.

ETSI

Release )*

0*

3GPP TS +,-*). /)*-*-* "0*))'*3#

Su&-(et1or8 Ser7i e "roto o!

6.1 'ra6e Re!a5 su""ort o3 t#e Su&-(et1or8 Ser7i e "roto o!

6.1.1 97er7ie1
The Gb interface may consist of direct point=to=point connections between the 5!! and the !G!-3 or an intermediate 7rame 4elay networ" may be placed between both ends of the Gb interface. Other intermediate eDuipments may be traversed. !everal confi urations are possible3 the detail of which is outside the scope of the present document. 7or the purposes of the present document the followin two types of confi urations have to be considered@ = = Point=to=point physical connections. 'ntermediate 7rame 4elay networ".

'n case of an intermediate 7rame 4elay networ"3 both 5!! and !G!- shall be treated as the user side of the user=to= networ" interface. The networ"=to networ" interface is outside the scope of the present document. Only 7rame 4elay permanent virtual connections (PA6s) shall be used on the Gb interface. Therefore 'T$=T 4ecommendation H.?00 +nne. + or T2.;2< for P6!2?11 and 'T$=T 4ecommendation H.?33 +nne. + or T2.;2> for P6!2?113 permanent virtual connection procedures3 shall be supported. !witched virtual connection procedures in 'T$=T 4ecommendation H.?00 or T2.;2< for P6!2?11 and 'T$=T 4ecommendation H.?33 or T2.;2> for P6!2?11 shall not be supported. 'T$=T 4ecommendation H.?02 or T2.;10 and 'T$=T 4ecommendation H.?32 procedures shall not be applicable. The 7rame 4elay user=to=networ" interface ($-') shall be implemented on the Gb interface accordin to the 747 2.2 a reement3 unless otherwise stated in the present document. !elected options or deviations from 747 2.2 are specified in the rest of this 7rame 4elay chapter. Ihere discrepancies arise between the present document and the above mentioned recommendations3 the present document ta"es precedence. The rest of this 7rame 4elay sub=clause applies only to PA6 usa e. The Gb interface addressin principles shall be applied as follows@ = = = = = The physical lin" is the 7rame 4elay bearer channel. The -!=A) is the local lin" in one end (at $-') of the 7rame 4elay PA6. The -!=A)' is the 7rame 4elay :)6' to ether with the bearer channel identifier. The -!=A6 is the 7rame 4elay PA6. The !ub=-etwor" !ervice entity is the 7rame 4elay entity.

6.1.2 (et1or8 o%3i2uratio%

The Gb interface is a $ser=to=-etwor" ($-') interface3 as defined in 747 2.2. Two confi urations are possible3 either a direct lin" confi uration or PA6(s) via a 7rame 4elay networ". +nne. + shows an e.ample of each type of confi uration. 'n case of point=to=point connections3 the 5!! shall be considered as the user side of the user=to=networ" interface3 the !G!- shall be considered as the networ" side3 see fi ure ;.2.0.2. Gb 5!! (user) 3i(ure .-)-0-)4 Direct lin confi(uration !G!(networ")

ETSI

Release )*

0)

3GPP TS +,-*). /)*-*-* "0*))'*3#

'n case of an intermediate 7rame 4elay networ"3 both 5!! and !G!- shall be treated as the user side of the user=to= networ" interface3 see fi ure ;.2.0.0. The networ"=to networ" interface is outside the scope of the present document.

Gb 5!! (user) 7rame 4elay networ"

Gb !G!(user)

3i(ure .-)-0-04 P/8 !ia a 3ra&e Rela% Networ

6.1.3 Ser7i es e."e ted 3ro6 !a5er 1

'n the conte.t of 7rame 4elay3 the physical lin" is referred to as the bearer channel. The 7rame 4elay protocol shall be run across permanently reserved bearer channels on the Gb interface3 see 3GPP T! 8<.128.

6.1.4 9"tio%s se!e ted 3ro6 'R' 1.1

6.1.4.1 Su""ort o3 4L-)9(TR9L su&-!a5er

-o end=to=end :)=6O-T4O) sub=layer shall be implemented on the Gb interface.

6.1.4.2

'ra6e !e%2t#

The default ma.imum information field si(e of 2 ;11 octets shall be supported on the Gb interface. Ma.imum information field si(es reater than 2 ;11 octets may be a reed to between 7rame 4elay networ" operators and users at subscription time.

6.1.4.3

)o%2estio% o%tro! "ro edures

6on estion control is defined in 747 2.2 and consists of con estion avoidance and con estion recovery mechanisms. 6on estion control on the Gb interface consists of con estion avoidance based on the :& bit and on e.plicit notifications via the 7&6- and 5&6- bits within the address field of the 7rame 4elay frame. 6on estion avoidance based on the 6))M messa e (see 'T$=T 4ecommendation H.?00 sub=clause +.> or T2.;2< for P6!2?11 and 747 2.2 sub=clause 0.0.9) is not reDuired at the 5!! and !G!- sides. -o con estion control mechanism based on implicit con estion detection (see 'T$=T 4ecommendation H.?00 sub= clause +.;.2) or T2.;2< for P6!2?11 is reDuired at the 5!! and !G!- sides.

6.1.4.3.1

4* &it usa2e

The 5!! and the !G!- shall always set the :& bit to 1 ((ero).

6.1.4.3.2

'*)( a%d :*)( &it usa2e

Settin% o" t'e FECN an! BECN .it& The 7&6- and 5&6- bits shall be set to 1 by the 5!! and the !G!-. Reaction u#on recei#t o" FECN or BECN 3ar+e! "ra3e& The reaction of the 5!! and the !G!- upon reception of 7&6- or 5&6- mar"ed frames is implementation dependent.

ETSI

Release )*

00

3GPP TS +,-*). /)*-*-* "0*))'*3#

't is recommended to implement 'T$=T 4ecommendation H.?00 appendi. '.0 or T2.;2< for P6!2?11 procedures or similar procedures3 so that the -! entity can reduce or increase the transmission rate3 dependin on the 7&6- or 5&6bits received. The -! entity shall be able to report the con estion situation to the upper layer. The criteria to be met for con estion bein reported to the upper layer are implementation dependent. The upper layer is e.pected to reduce or increase its transmission rate as appropriate. 't shall be up to the upper layer to perform further appropriate actions e. . flow control with its peer entity3 see 'T$=T 4ecommendation '.3>1 or T2.;1; for P6!2?11.

6.1.4.4

Si2%a!!i%2 "ro edures

'T$=T 4ecommendation 4evised H.?33 anne. + or T2.;2> for P6!2?11 procedures shall be implemented at the 5!! and the !G!- sides as recommended in 747 2.2 sub=clause 0.3. On the Gb interface3 these procedures shall be initiated by the user side of the $-'3 reverse procedures shall not be used. Only periodic pollin shall be used3 asynchronous status messa e needs not to be supported. !witched virtual connection procedures 3 see 747 2.2 sub=clause 0.3.03 shall not be implemented.

6.1.4.5

)0R &it usa2e

The 6J4 bit shall not be used and shall be set to 1 by the sendin entity. 't shall not be chec"ed by the receivin entity.

6.1.5 $&%or6a! o%ditio%s

$pon detection of the unavailability of a PA6 by the 7rame 4elay entity or when a PA6 becomes available a ain3 the -etwor" !ervice 6ontrol entity shall be informed. $navailability cases are described in 4ecommendations 'T$=T 4ecommendation H.?00 or T2.;2< for P6!2?11 and 'T$=T 4ecommendation H.?33 anne. + or T2.;2> for P6!2?11.

6.2 =P Su""ort o3 t#e Su&-(et1or8 Ser7i e Proto o!

6.2.1 97er7ie1
The 'P !ub=-etwor" shall use the 'nternet Protocol ('P) as defined in either 476 >?2 or 476 08;1 and the $ser :ata ram Protocol ($:P) as defined in 476 >;<. The connections between the 5!! and the !G!- may consist of point=to=point connections or of an intermediate 'P networ". !everal confi urations are possible3 the details of which are outside the scope of the present document. 7or the purposes of the present document the followin characteristics have to be considered@ 2) The !ub=-etwor" !ervice (!-!) may be confi ured by administrative means (i.e. static confi uration) or by auto=confi uration procedures (i.e. dynamic confi uration). 'n the case of auto=confi uration the operator shall ensure3 in advance3 that each -!& can fulfil its peer -!& reDuirements (e. . ma.imum number of -!=A6s3 ma.imum number of 'P=endpoints). 0) +dministrative confi uration means the administration of the -!&s# 'P endpoints (includin the !i nallin Iei ht and :ata Iei ht). 3) 'n the case of a point=to=point connection3 the administrative confi uration shall be used. 'n the case of an intermediate 'P networ" connection3 then either the administrative means or the auto=confi uration procedures may be used. 8) The 5!! -!& has no "nowled e of the confi uration of any other 5!! -!&s. 9) The auto=confi uration procedures are used to e.chan e confi uration information between the 5!! and the !G!-. The clientJserver principle applies@ the !G!- is the server3 while the 5!! is a client. The 5!! shall have "nowled e of at least one !G!- 'P endpoint3 referred to as pre=confi ured endpoint hereafter3 to initiate the procedures. The auto=confi uration procedures consist of the followin @

ETSI

Release )*

03

3GPP TS +,-*). /)*-*-* "0*))'*3#

a) +fter start=up the 5!! -!& reports to the peer=!G!- -!& by initiatin the !i(e procedure. b) Then3 the 5!! initiates the 6onfi uration Procedure in which a seDuence of messa es are e.chan ed between the 5!! and the !G!- containin si nallin endpoints3 data endpoints3 and initial wei hts. + pre=confi ured endpoint shall not be used for -!& data or si nallin traffic (with the e.ception of !i(e and 6onfi uration procedures) unless it is confi ured by the !G!- usin the auto=confi uration procedures. ;) + networ" connection as part of the intermediate 'P networ" between the -!&s shall be terminated by the same type of 'P addresses (e. . 'Pv8 or 'Pv;). >) 7or dynamic confi urations the chan e of initially confi ured parameters shall be supported by the +dd procedure3 :elete procedure and 6han eIei ht procedure. <) The !-! messa es (!-! !'N&3 !-! 6O-7'G3 !-! +::3 !-! :&)&T&3 !-! 6M+-G&I&'GMT) servin to support the confi uration3 !i(e3 +dd3 :elete and 6han eIei ht procedures shall only be used in the case of dynamic confi uration.

6.2.1a $&%or6a! )o%ditio%s

'f the 5!! or !G!- -!& receives at a iven 'P endpoint an !-! P:$ containin an un"nown -!&' or an -!&' associated to a different local 'P endpoint3 the 5!! or !G!- -!& may simply discard such !-! P:$ without further action.

6.2.2 =P 'ra26e%tatio%
7ra mentation should be avoided if possible. &.amples of fra mentation drawbac"s are3 e. .@ = = 7ra mentation is inefficient3 since the complete 'P header is duplicated in each fra ment. 'f one fra ment is lost3 the complete pac"et has to be discarded. The reason is that no selective retransmission of fra ments is possible.

Mechanisms used to avoid fra mentation are outside the scope of the present document.

6.2.3 Ser7i es e."e ted 3ro6 !a5er 1 a%d !a5er 2

)ayer one and two are unspecified. -o services are defined in the present document.

6.2.4 Si@e Pro edure

This procedure is initiated by the 5!!. The !i(e procedure shall be performed to@ = = = = 4eset all information maintained by the 5!! -!& and its peer prior to the confi uration procedure. Aerify that the number of -!=A6s that can be supported by the 5!! -!& is reater than or eDual to the number of -!=A6s reDuired for full mesh connectivity to the peer !G!- -!&. Aerify that the number of 'P endpoints indicated by the 5!! -!& can be supported by the !G!- -!&. Aerify the compatibility between the type of 'P addresses ('Pv8J'Pv;) supported by the peer -!&s.

The 5!! -!& shall send an !-!=!'N& P:$ to the !G!- usin any of the pre=confi ured !G!- 'P endpoints (confi urin of any pre=confi ured !G!- 'P endpoints is out of the scope of the present document). The 5!! shall start timer Tsns=prov. The !-!O!'N& P:$ shall contain the followin information elements@ = = = -!&'@ -!& 'dentifier. Ma.imum -umber of -!=A6s@ ma.imum number of -!=A6s the 5!! -!& can support. 4eset 7la @ indicates whether all confi uration information between the 5!! -!& and its peer !G!- -!& shall be cleared prior to a forthcomin initiation of the confi uration procedure by the 5!! -!& (4eset=bit field of the

ETSI

Release )*

0+

3GPP TS +,-*). /)*-*-* "0*))'*3#

Reset Flag '& set to G2G)3 or if the procedure is only initiated to ascertain the ability of the !G!- -!& to support the reDuested capabilities (4eset=bit field of the Reset Flag '& set to G1G). = = -umber of 'P8 &ndpoints@ ma.imum number of 5!! -!& 'Pv8 addresses that the 5!! -!& is allowed to confi ure throu h the forthcomin confi uration procedure andJor -umber of 'P; &ndpoints@ ma.imum number of 5!! -!& 'Pv; addresses that the 5!! -!& is allowed to confi ure throu h the forthcomin confi uration procedure.

$pon receipt of an !-!=!'N& P:$3 the !G!- shall@ = 'f the 4eset=bit field of the Reset Flag '& is set to G2G3 clear all previous operatin information about the 5!! -!& (no operatin information shall be affected in the !G!- if the 4eset=bit field of the Reset Flag '& is set to G1G). !end an !-!=!'N&=+6, P:$ to the source 'P endpoint. The !-!=!'N&=+6, P:$ shall contain the -!&' '&. The !-!=!'N&=+6, P:$ may contain the Cause '& as specified in sub=clause ;.0.8.2.

$pon receipt of an !-!=!'N&=+6, P:$ the 5!! shall@ = = !top timer Tsns=prov. 'f the 4eset=bit field of the Reset Flag '& was set to G2G in the !-!=!'N& P:$ sent by the 5!!3 initiate the confi uration procedure (see sub=clause ;.0.9).

6.2.4.1 $&%or6a! )o%ditio%s

'f the ma.imum number of -!=A6s indicated in the !-!=!'N& P:$ is less than the number of -!=A6s reDuired for full mesh connectivity between the peer -!&s3 the !G!- shall send an !-!=!'N&=+6, P:$ with a cause code G'nvalid number of -!=A6sG. The number of -!=A6s reDuired for full mesh connectivity between peer -!&s is the product of the number of 'Pv8 endpoints supported on each of the peer -!&s plus the product of the number of 'Pv; endpoints supported on each of the peer -!&s. $pon receivin the !-!=!'N&=+6, P:$ with a cause code G'nvalid number of -!=A6sG the 5!! -!& may notify the OPM system and abort the procedure. 'f the !G!- does not support the type of 'P addresses ('Pv8J'Pv;) offered by the 5!!3 the !G!- shall send an !-!= !'N&=+6, P:$ with a cause code G'nvalid number of 'P8 &ndpointsG or G'nvalid number of 'P; &ndpointsG. $pon receivin the !-!=!'N&=+6, P:$ with a cause code G'nvalid number of 'P8 &ndpointsG or G'nvalid number of 'P; &ndpointsG the 5!! -!& may notify the OPM system and abort the procedure. 'f the !G!- does not support the number of 'Pv8 endpoints indicated in the !-!=!'N& P:$3 the !G!- shall send an !-!=!'N&=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG. 'f the !G!- does not support the number of 'Pv; endpoints indicated in the !-!=!'N& P:$3 the !G!- shall send an !-!=!'N&=+6, P:$ with a cause code set to G'nvalid number of 'P; &ndpointsG. $pon receivin the !-!=!'N&=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG or G'nvalid number of 'P; &ndpointsG3 the 5!! -!& may notify the OPM system and abort the procedure. $pon e.piry of timer Tsns=prov the -!& may retry the operation !-!=!'N&=4&T4'&! times. 'f the operation has been attempted !-!=!'N&=4&T4'&! times without ac"nowled ement from the peer -! entity3 then the -! entity may notify the OPM system and abort the procedure. Ihether the -! entity would restart the si(e procedure usin any pre= confi ured !G!- 'P endpoints after abortion is left implementation dependent. 7urther actions are outside the scope of the present document.

6.2.5

)o%3i2uratio% Pro edure

The confi uration procedure is used on the Gb interface to e.chan e confi uration information between an -!& and its peer -!&. To start the confi uration procedure3 the clientJserver principle is used3 with the 5!! as the client. $pon start=upJrestart of a 5!! -!& or followin the detection of a restart of a peer !G!- -!& (e. . by means of the test procedure = see sub=clause >.8b)3 the !i(e procedure with the 4eset=bit field of the Reset Flag '& set to G2G in the !-!= !'N& P:$ shall be performed upon initiation by the 5!! -!& before the confi uration procedure is started.

ETSI

Release )*

01

3GPP TS +,-*). /)*-*-* "0*))'*3#

+fter completion on the 5!! side of the !i(e procedure havin indicated a reset3 the 5!! -!& shall send an !-!= 6O-7'G P:$ to the same pre=confi ured !G!- 'P endpoint used in the !i(e procedure. -OT&@ This does not imply that the !-!=6O-7'G P:$ has to be sent from the same 'P endpoint used in the !i(e procedure.

The 5!! shall start timer Tsns=prov. The !-!=6O-7'G P:$ shall contain the followin information elements@ -!&'@ &nd 7la @ )ist of 'P8 &lements@ )ist of 'P; &lements@ -!& 'dentifier. identifies the last !-!=6O-7'G P:$ sent by the 5!! -!&. one or more 'Pv8 endpoints3 or one or more 'Pv; endpoints.

$pon receipt of an !-!=6O-7'G P:$ sent by the 5!!3 the !G!- shall send an !-!=6O-7'G=+6, P:$ to the source 'P endpoint. $pon receipt of an !-!=6O-7'G=+6, P:$ sent by the !G!-3 the 5!! shall@ = = !top timer Tsns=prov. 4epeat the above !-!=6O-7'G P:$ seDuence to the !G!- if the 5!! has more 'P endpoints to confi ure.

+fter completion on the !G!- side of the !i(e procedure3 the !G!- shall send an !-!=6O-7'G P:$ to the 5!! -!& usin any "nown si nallin 'P endpoints (i.e.3 from information contained within an !-!=6O-7'G P:$ sent by the 5!!). The !G!- shall start timer Tsns=prov. The !-!=6O-7'G P:$ shall contain the followin information elements@ -!&'@ &nd 7la @ )ist of 'P8 &lements@ )ist of 'P; &lements@ -!& 'dentifier. identifies the last !-!=6O-7'G P:$ sent by the !G!- -!&. one or more 'Pv8 endpoints3 or one or more 'Pv; endpoints.

$pon receipt of an !-!=6O-7'G P:$ sent by the !G!-3 the 5!! shall send an !-!=6O-7'G=+6, P:$ to the source 'P endpoint. $pon receipt of an !-!=6O-7'G=+6, P:$ sent by the 5!!3 the !G!- shall@ = = !top timer Tsns=prov. 4epeat the above !-!=6O-7'G P:$ seDuence to the 5!! if the !G!- has more 'P endpoints to confi ure. The !G!- shall start timer Tsns=prov.

-either the !G!- nor the 5!! shall initiate any other procedure before receivin the peer#s end=fla .

6.2.5.1 $&%or6a! )o%ditio%s

$pon receivin an !-!=6O-7'G P:$ with the &=bit field in the End Flag '& set to G2G3 if the total number of 'Pv8 elements sent to the !G!- by the 5!! -!& is reater than the number of 'Pv8 endpoints sent by the 5!! -!& in the !'N& P:$3 the !G!- shall send an !-!=6O-7'G=+6, P:$ with a cause code of G'nvalid number of 'P8 &ndpointsG. The !G!- shall clear all information associated with the peer 5!! -!&. $pon receivin an !-!=6O-7'G=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG the 5!! may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document. The 5!! shall clear all information associated with the peer !G!- -!&. $pon receivin an !-!=6O-7'G P:$ with the &=bit field in the End Flag '& set to G2G3 if the total number of 'Pv; elements sent to the !G!- by the 5!! -!& is reater than the number of 'Pv; endpoints sent by the 5!! -!& in the !'N& P:$3 the !G!- shall send an !-!=6O-7'G=+6, P:$ with a cause code of G'nvalid number of 'P; &ndpointsG. The !G!- shall clear all information associated with the peer 5!! -!&.

ETSI

Release )*

0.

3GPP TS +,-*). /)*-*-* "0*))'*3#

$pon receivin an !-!=6O-7'G=+6, P:$ with a cause code set to G'nvalid number of 'P; &ndpointsG the 5!! may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document. The 5!! shall clear all information associated with the peer !G!- -!&. $pon receivin an !-!=6O-7'G P:$ with the &=bit field in the End Flag '& set to G2G3 if the total number of 'Pv8 elements sent to the 5!! by the !G!- -!& is reater than the number of 'Pv8 endpoints supported by the 5!! -!&3 the 5!! shall send an !-!=6O-7'G=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG and clear all information associated with the peer !G!- -!&. $pon receivin an !-!=6O-7'G P:$ with the &=bit field in the End Flag '& set to G2G3 if the total number of 'Pv; elements sent to the 5!! by the !G!- -!& is reater than the number of 'Pv; endpoints supported by the 5!! -!&3 the 5!! shall send an !-!=6O-7'G=+6, P:$ with a cause code set to G'nvalid number of 'P; &ndpointsG and clear all information associated with the peer !G!- -!&. $pon receivin an !-!=6O-7'G=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG or G'nvalid number of 'P; &ndpointsG the !G!- may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document. The !G!- shall clear all information associated with the peer 5!! -!&. $pon receivin an !-!=6O-7'G P:$ with the &=bit field in the End Flag '& set to G2G3 if the resultin sum of the si nallin wei hts of all the peer 'P endpoints confi ured for this -!& is eDual to (ero or if the resultin sum of the data wei hts of all the peer 'P endpoints confi ured for this -!& is eDual to (ero the -!& shall send an !-!=6O-7'G=+6, P:$ with a cause code of G'nvalid wei htsG. The -!& shall clear all information associated with the peer -!&. $pon receivin an !-!=6O-7'G +6, P:$ with cause code set to G'nvalid wei htsG the -!& shall clear all information associated with the peer -!& and may notify the OPM system. $pon e.piry of timer Tsns=prov the -!& may retry the operation !-!=6O-7'G=4&T4'&! times. 'f the operation has been attempted !-!=6O-7'G=4&T4'&! times without ac"nowled ement from the peer -!&3 then the -!& may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document.

6.2.6

$dd Pro edure

The +dd procedure is used by an -!& to confi ure additional 'P endpoints. To add new 'P endpoints3 the -!& shall send an !-!=+:: P:$ to a peer -!& si nallin endpoint. $pon sendin the !-!=+:: P:$ the -!& shall start timer Tsns=prov. The !-!=+:: P:$ shall contain the followin information elements@ -!&'@ Transaction ':@ )ist of 'P8 &lements@ )ist of 'P; &lements@ -!& 'dentifier. identifies a uniDue transaction within an -!&. one or more 'Pv8 endpoints3 or. one or more 'Pv; endpoints.

$pon receipt of an !-!=+:: P:$ the -!& shall send an !-!=+6, P:$ to the source 'P endpoint from which the !-!=+:: P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=+:: P:$. $pon receipt of an !-!=+6, P:$ the -!& shall stop timer Tsns=prov.

6.2.6.1 $&%or6a! )o%ditio%s

$pon receivin an !-!=+:: P:$3 if the conseDuent number of -!=A6s e.ceeds the ma.imum own supported number of -!=A6s then the -!& shall send an !-!=+6, P:$ with cause code set to G'nvalid number of -!=A6sG. $pon receivin an !-!=+:: P:$3 if the conseDuent number of 'Pv8 endpoints e.ceeds the number of 'Pv8 endpoints supported by the -!&3 the -!& shall send an !-!=+6, P:$ with a cause code set to G'nvalid number of 'P8 &ndpointsG. $pon receivin an !-!=+:: P:$3 if the conseDuent number of 'Pv; endpoints e.ceeds the number of 'Pv; endpoints supported by the -!&3 the -!& shall send an !-!=+6, P:$ with a cause code set to G'nvalid number of 'P; &ndpointsG.

ETSI

Release )*

02

3GPP TS +,-*). /)*-*-* "0*))'*3#

$pon receivin an !-!=+:: P:$ containin an already confi ured 'P endpoint the -!& shall send an !-!=+6, P:$ with the cause code GProtocol error = unspecifiedG. 7or any of the abnormal cases specified above@ = = The whole content of the received !-!=+:: P:$ shall be i nored. The !-!=+6, P:$ shall be sent to the source 'P endpoint from which the !-!=+:: P:$ was sent. The !-!= +6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=+:: P:$.

$pon e.piry of timer Tsns=prov the -!& may retry the operation !-!=+::=4&T4'&! times. 'f the operation has been attempted !-!=+::=4&T4'&! times without ac"nowled ement from the peer -!&3 then the -!& may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document.

6.2./

4e!ete Pro edure

The delete procedure is used by an -!& to remove previously confi ured 'P endpoints from service. To delete 'P endpoints3 the -!& shall send an !-!=:&)&T& P:$ to a peer -!& si nallin endpoint. $pon sendin the !-!=:&)&T& P:$ the -!& shall start timer Tsns=prov. The !-!=:&)&T& P:$ shall contain the followin information elements@ -!&'@ Transaction ':@ 'P +ddress@ )ist of 'P8 &lements@ )ist of 'P; &lements@ -!& 'dentifier. identifies a uniDue transaction within the -!&. all 'P endpoints that use this 'P address shall be deleted or one or more 'Pv8 endpoints3 or one or more 'Pv; endpoints.

$pon receipt of an !-!=:&)&T& P:$ the -!& shall send an !-!=+6, P:$ to the source 'P endpoint from which the !-!=:&)&T& P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=:&)&T& P:$. $pon receipt of an !-!=+6, P:$ the -!& shall stop timer Tsns=prov.

6.2./.1 $&%or6a! )o%ditio%s

$pon receivin an !-!=:&)&T& P:$ containin one or more 'P endpoints that has not been previously confi ured with an !-!=+:: P:$ or an !-!=6O-7'G P:$3 the -!& shall send an !-!=+6, P:$ with a cause code of G$n"nown 'P endpointG to the source 'P endpoint from which the !-!=:&)&T& P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=:&)&T& P:$. The -!& shall also include3 in the !-!=+6, P:$3 all 'Pv8 endpoints in the !-!=:&)&T& P:$ that have not been previously confi ured in the List of IP4 Elements '&3 or all 'Pv; endpoints in the !-!=:&)&T& P:$ that have not been previously confi ured in the List of IP Elements '&. +ll previously confi ured 'P endpoints contained in the !-!=:&)&T& P:$ shall be deleted. $pon receivin an !-!=:&)&T& P:$ containin an 'P address for which no 'P endpoints have been previously confi ured with an !-!=+:: P:$ or an !-!=6O-7'G P:$3 the -!& shall send an !-!=+6, P:$ with a cause code of G$n"nown 'P addressG to the source 'P endpoint from which the !-!=:&)&T& P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=:&)&T& P:$. The -!& shall also include3 in the !-!=+6, P:$3 the 'P address received in the !-!=:&)&T& P:$. $pon e.piry of timer Tsns=prov the -!& may retry the operation !-!=:&)&T&=4&T4'&! times. 'f the operation has been attempted !-!=:&)&T&=4&T4'&! times without ac"nowled ement from the peer -!&3 then the -!& may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document.

6.2.8

)#a%2eAei2#t Pro edure

The 6han eIei ht procedure is used by an -!& to chan e the si nallin wei ht andJor data wei ht of the specified 'P endpoints.

ETSI

Release )*

0,

3GPP TS +,-*). /)*-*-* "0*))'*3#

To chan e the si nallin wei ht andJor data wei ht of an 'P endpoint3 the -!& shall send an !-!=6M+-G&I&'GMT P:$ to a peer -!& si nallin endpoint. $pon sendin the !-!=6M+-G&I&'GMT P:$ the -!& shall start timer Tsns=prov. The !-!=6M+-G&I&'GMT P:$ shall contain the followin information elements@ -!&'@ Transaction ':@ )ist of 'P8 &lements@ )ist of 'P; &lements@ -!& 'dentifier. identifies a uniDue transaction within the -!&. one of more 'Pv8 endpoints3 or one or more 'Pv; endpoints.

$pon receipt of an !-!=6M+-G&I&'GMT P:$ the -!& shall send an !-!=+6, P:$ to the source 'P endpoint from which the !-!=6M+-G&I&'GMT P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=6M+-G&I&'GMT P:$. $pon receipt of an !-!=+6, P:$ the -!& shall stop timer Tsns=prov.

6.2.8.1

$&%or6a! )o%ditio%s

$pon receivin an !-!=6M+-G&I&'GMT P:$3 if the resultin sum of the si nallin wei hts of all the peer 'P endpoints confi ured for this -!& is eDual to (ero or if the resultin sum of the data wei hts of all the peer 'P endpoints confi ured for this -!& is eDual to (ero3 the 5!!J!G!- shall send an !-!=+6, P:$ with a cause code of G'nvalid wei htsG. The whole content of that !-!=6M+-G&I&'GMT P:$ shall be i nored. $pon receivin an !-!=6M+-G&I&'GMT P:$ containin one or more 'P endpoints that has not been previously confi ured with an !-!=+:: P:$ or an !-!=6O-7'G P:$3 the -!& shall send an !-!=+6, P:$ with a cause code of G$n"nown 'P endpointG to the source 'P endpoint from which the !-!=6M+-G&I&'GMT P:$ was sent. The !-!=+6, P:$ shall contain the Transaction ': set to the same value as that in the !-!=6M+-G&I&'GMT P:$. The -!& shall also include3 in the !-!=+6, P:$3 all 'Pv8 endpoints sent in the !-!=6M+-G&I&'GMT P:$ that have not been previously confi ured in the List of IP4 Elements '&3 or all 'Pv; endpoints sent in the !-!= 6M+-G&I&'GMT P:$ that have not been previously confi ured in the List of IP Elements '&. The -!& shall discard the information in the !-!=6M+-G&I&'GMT P:$ associated with all 'P endpoints that have not been previously confi ured. +ll previously confi ured 'P endpoints contained in the !-!=6M+-G&I&'GMT P:$ shall be chan ed. $pon e.piry of timer Tsns=prov the -!& may retry the operation !-!=6M+-G&I&'GMT=4&T4'&! times. 'f the operation has been attempted !-!=6M+-G&I&'GMT=4&T4'&! times without ac"nowled ement from the peer -!&3 then the -!& may notify the OPM system and abort the procedure. 7urther actions are outside the scope of the present document.

(et1or8 Ser7i e )o%tro! "roto o!

/.1 Pro edures 3or t#e tra%s6issio% o3 (S S4<s

-! !:$s are transmitted in unac"nowled ed mode across the Gb interface by means of an -!=$-'T:+T+ P:$. The -!=$-'T:+T+ P:$ is used in both 5!!=to=!G!- and !G!-=to=5!! directions. 7or an 'P sub=networ"3 an -!=$-'T:+T+ P:$ for a PTP 5A6 may indicate a reDuest to chan e the 'P endpoint andJor a response to a chan e in the 'P endpoint. 'f the 5!! or !G!- receives an -!=$-'T:+T+ P:$ for a si nallin 5A6 or a PTM 5A6 then the 5!! or !G!shall i nore the codin of the 6=bit and 4=bit.

/.1.1 $&%or6a! )o%ditio%s

'f the 5!! receives an -!=$-'T:+T+ P:$ includin a 5A6' not associated to the -!=A6 where the P:$ was received3 the 5!! shall return an -!=!T+T$! P:$ on that -!=A63 cause G5A6 un"nown on that -!&G. :ependin on the implementation3 the 5!! may then i nore the 5A6' and treat the rest of the -!=$-'T:+T+ P:$.

ETSI

Release )*

07

3GPP TS +,-*). /)*-*-* "0*))'*3#

/.2 :!o 8i%2 0 u%&!o 8i%2 "ro edures

The 5loc"in J$nbloc"in procedures shall not be used for an 'P !ub=networ". Ihen a 5!! (or !G!-) wishes to bloc" an -!=A6 between a 5!! and !G!-3 the followin shall be performed@ = The transmittin side at the 5!! (or !G!-) shall mar" the -!=A6 as bloc"ed and shall inform the load sharin function. This results in the redistribution of -!=$-':+T+ P:$s to other unbloc"ed -!=A6s of the same roup3 as described in the G)oad sharin functionG sub=clause. The -! user entity shall also be informed of the new transfer capability by means of an -!=!T+T$!='ndication primitive for each affected 5A6. + 5!! (or !G!-) then sends an -!=5)O6, P:$ to the peer entity and starts timer Tns=bloc". The -!=5)O6, P:$ contains the -!=A6' and a 6ause element indicatin the reason for bloc"in (typical cause values@ Transit networ" failure3 OPM intervention3 &Duipment failure). The -!=5)O6, P:$ may be sent in any alive (bloc"ed or unbloc"ed) -!=A6 pertainin to the same roup as the -!=A6 to be bloc"ed3 unless otherwise reDuired for particular cases which may be further described in the rest of the present document. +t the sendin side of the -!=5)O6, P:$3 if no failure has occurred in the receive direction (e. . OPM intervention)3 the ori inator of the -!=5)O6, P:$ shall continue to accept -!=$-'T:+T+ P:$s received on the -!=A6 bein bloc"ed3 until an -!=5)O6,=+6, P:$ is received for this -!=A6. The ori inator of the -!=5)O6, P:$ shall stop to accept -!=$-'T:+T+ P:$s3 if the number of retries of the bloc"in procedures is e.ceeded. $pon 4eceipt of an -!=5)O6, P:$ at an !G!- (or 5!!) the -!=A6 shall be mar"ed as bloc"ed. The !G!(or 5!!) shall immediately inform the load sharin function. The -! user entity shall also be informed of the new transfer capability by means of an -!=!T+T$!='ndication primitive for each affected 5A6. The !G!- (or 5!!) then sends in any alive (bloc"ed or unbloc"ed) -!=A6 of the relevant roup an -!=5)O6,=+6, P:$3 for the bloc"ed -!=A63 to the 5!! (or !G!-). On receipt of an -!=5)O6,=+6, P:$ or -!=5)O6, P:$3 the ori inator of the -!=5)O6, P:$ stops timer Tns=bloc".

The -!=A6 shall remain bloc"ed until an -!=$-5)O6, P:$ is received indicatin that the -!=A6#s state has been chan ed. Ihen a 5!! (or !G!-) wishes to unbloc" an -!=A6 between a 5!! and !G!-3 the followin shall be performed@ = The 5!! (or !G!-) sends an -!=$-5)O6, P:$ to the peer entity and starts timer Tns=bloc". The -!=$-5)O6, P:$ shall be sent on the -!=A6 to be unbloc"ed (the -!=A6 must be alive3 see chec" procedure in sub=clauses GTest of an -!=A6G). The 5!! or !G!- may discard any -!=$-'T:+T+ P:$ received on the concerned -!=A6 until the reception of the -!=$-5)O6,=+6, P:$. 'f an -!=$-5)O6, P:$ is received by an !G!- (or 5!!) for an -!=A6 and the !G!- (or 5!!) is able to unbloc" the -!=A63 the !G!- (or 5!!) shall return an -!=$-5)O6,=+6, P:$ on the -!=A6 where the -!=$-5)O6, P:$ was received3 then the -!=A6 shall be mar"ed as unbloc"ed. The load sharin function shall be informed. The -! user entity shall also be informed of the new transfer capability by means of an -!= !T+T$!='ndication primitive for each affected 5A6. + 5!! (or !G!-) shall stop timer Tns=bloc" on receipt of an -!=$-5)O6,=+6, or -!=$-5)O6, P:$3 shall mar" the -!=A6 as unbloc"ed and shall inform the load sharin function in order to allow transmission of -!=$-'T:+T+ P:$s on this -!=A6. The -! user entity shall also be informed of the new transfer capability by means of an -!=!T+T$!='ndication primitive for each affected 5A6. +n -!=$-5)O6, P:$ received while a 5!! (or !G!-) is waitin for an -!=$-5)O6,=+6, P:$ shall be ac"nowled ed with an -!=$-5)O6,=+6, P:$. 'f an -!=$-5)O6, P:$ is received by an !G!- (or 5!!) and the !G!- (or 5!!) is not able to unbloc" the -!=A63 the -!=A6 shall remain bloc"ed and the -!=A6 bloc"in procedure shall be initiated by returnin an -!=5)O6, P:$ to the 5!! (or !G!-). This -!=5)O6, P:$ shall be sent on the -!=A6 where the -!=$-5)O6, P:$ was received. 'f a 5!! (or !G!-) receives an -!=5)O6, P:$ while waitin for an -!=$-5)O6,=+6, P:$3 it shall stop timer Tns=bloc" and the -!=A6 shall remain bloc"ed. +n -!=5)O6,=+6, P:$ shall be returned. +n indication shall be issued towards the OPM system3 announcin that the unbloc"in of the -!=A6 was not possible at the peer entity. 7urther actions of the OPM system are out of the scope of the present document.

ETSI

Release )*

3*

3GPP TS +,-*). /)*-*-* "0*))'*3#

/.2.1 $&%or6a! )o%ditio%s

'f an -!=5)O6,=+6, P:$ is not received for an -!=5)O6, P:$ within Tns=bloc" seconds3 then the -!=5)O6, P:$ procedure shall be repeated a ma.imum of -!=5)O6,=4&T4'&! attempts. +fter -!=5)O6,=4&T4'&! unsuccessful retry attempts the procedure is stopped and the OPM system is informed that the bloc"in procedure has failed. 7urther actions of the OPM system are out of the scope of the present document. The -!=A6 shall be mar"ed as bloc"ed at the ori inatin side of the bloc"in procedure. 'f an -!=$-5)O6,=+6, P:$ is not received for an -!=$-5)O6, P:$ within Tns=bloc" seconds3 the -!= $-5)O6, P:$ procedure shall be repeated a ma.imum of -!=$-5)O6,=4&T4'&! attempts. +fter -!= $-5)O6,=4&T4'&! unsuccessful retry attempts the procedure is stopped and the OPM system is informed that the unbloc"in procedure has failed. 7urther actions of the OPM system are out of the scope of the present document. The -!=A6 shall be mar"ed as bloc"ed at the ori inatin side of the unbloc"in procedure. 'f an -!=$-'T:+T+ P:$ is received on an -!=A6 that is mar"ed at a 5!! or an !G!- as bloc"ed and no -!=A6 unbloc"in procedure is pendin 3 then an -!=!T+T$! P:$ (6ause value@ -!=A6 bloc"ed) shall be returned to the peer entity. 'f an -!=5)O6, P:$ is received by a 5!! or an !G!- for a bloc"ed -!=A63 an -!=5)O6,=+6, P:$ shall be returned. 'f an -!=$-5)O6, P:$ is received by a 5!! or an !G!- for an unbloc"ed -!=A63 an -!=$-5)O6,=+6, P:$ shall be returned. 'f an une.pected -!=5)O6,=+6, P:$ is received by a 5!! or an !G!- and it is related to an -!=A6 that is locally bloc"ed3 the -!=5)O6,=+6, P:$ is discarded. 'f the -!=5)O6,=+6, P:$ is related to an -!=A6 that is not locally bloc"ed3 then an -!=A6 unbloc"in procedure is initiated. 'f an une.pected -!=$-5)O6,=+6, P:$ is received by a 5!! or an !G!- and it is related to an -!=A6 that is not locally bloc"ed3 the received -!=$-5)O6,=+6, P:$ is discarded. 'f the -!=$-5)O6,=+6, P:$ is related to an -!=A6 that is locally bloc"ed3 then an -!=A6 bloc"in procedure is initiated. 'f the -!=A6' received in an -!=5)O6, or -!=5)O6,=+6, P:$ is un"nown3 then the error shall be reported to the ori inator of the P:$ by means of an -!=!T+T$! P:$ includin the un"nown -!=A6'3 with the 6ause value set to G-!=A6 un"nownG3 the OPM system shall be informed3 then the -!=5)O6, or -!=5)O6,=+6, P:$ shall be i nored. 7urther actions of the OPM system are out of the scope of the present document.

/.3 Reset "ro edure

The reset procedure shall not be used for an 'P !ub=networ". The reset procedure shall be used when a new -!=A6 is set=up between a 5!! and an !G!-3 after processor re=start3 after failure recovery or any local event restorin an e.istin -!=A6 in the dead state or when its state is undetermined between remote -! entities. $pon completion of the reset procedure3 the successfully reset -!=A6 is mar"ed as bloc"ed and alive at both sides of the Gb interface. Ihen a 5!! (or !G!-) wishes to reset an -!=A63 the followin shall be performed@ = The -! entity at the 5!! (or !G!-) informs the -! user entity of the new transfer capability by means of an -!=!T+T$!='ndication primitive for each affected 5A6. The 5!! (or !G!-) then sends an -!=4&!&T P:$ to its peer entity indicatin the -!=A6' and the -!&'. The -!=4&!&T P:$ is sent on the -!=A6 bein reset. The -!=4&!&T P:$ includes a 6ause information element. The sendin entity of the -!=4&!&T P:$ then mar"s the -!=A6 as bloc"ed and dead and starts timer Tns= reset. 4eceipt of an -!=4&!&T P:$ at an !G!- (or 5!!) shall be ac"nowled ed with an -!=4&!&T=+6, P:$ includin the -!=A6' and the -!&'3 provided that the receivin side is able to reset the -!=A6 (i.e. no local condition prevents the receivin side from resettin the -!=A6). The -!=4&!&T=+6, P:$ shall be sent on the -!=A6 bein reset.

= =

ETSI

Release )*

3)

3GPP TS +,-*). /)*-*-* "0*))'*3#

The entity receivin the -!=4&!&T P:$ then mar"s the ac"nowled ed -!=A6 as bloc"ed and alive and informs the -! user entity of the new transfer capability by means of an -!=!T+T$!='ndication primitive for each affected 5A6. The test procedure is then initiated on this -!=A6. Ihen the sendin entity of an -!=4&!&T P:$ receives the -!=4&!&T=+6, P:$3 it stops timer Tns=reset3 mar"s the -!=A6 as bloc"ed and alive and initiates the test procedure on this -!=A6. The ori inator of the -!= 4&!&T P:$ is then responsible for unbloc"in this -!=A6.

'n case of collision between reset procedures initiated at both sides of the Gb interface3 the followin shall apply@ = Ihen an -! entity awaitin an -!=4&!&T=+6, P:$ in response to an -!=4&!&T P:$ receives an -!= 4&!&T P:$3 it shall ac"nowled e it as described above3 and in addition3 it shall treat it as an -!=4&!&T=+6, P:$.

Ihen an -! entity is awaitin an -!=4&!&T=+6, P:$3 any P:$ other than -!=4&!&T or -!=4&!&T=+6, received on one of the -!=A6s bein reset shall be i nored. The reset procedure overrides any other pendin procedure on the affected -!=A6 i.e. other pendin procedures are stopped3 other runnin timers are stopped.

/.3.1 $&%or6a! o%ditio%s

'f the sendin entity of an -!=4&!&T P:$ receives no -!=4&!&T=+6, P:$ before timer Tns=reset e.pires the correspondin -!=A6s shall remain bloc"ed and dead and the entire reset procedure shall be repeated. 'f the reset procedure remains unsuccessful for a period of time established by the operator3 the OPM system shall be informed3 and the reset procedure shall be stopped. 7urther actions of the OPM system are out of the scope of the present document. 'f the -!=A6' received in an -!=4&!&T P:$ is different from the -!=A6' locally associated to this -!=A63 the OPM system shall be informed3 an -!=4&!&T=+6, P:$ shall be returned includin the -!=A6' locally associated to this -!=A63 then the -!=4&!&T P:$ shall be i nored as if not received. 'f the -!&' received in an -!=4&!&T P:$ is different from the -!&' locally associated to this -!=A63 the OPM system shall be informed3 an -!=4&!&T=+6, P:$ shall be returned includin the -!&' locally associated to this -!= A63 then the -!=4&!&T P:$ shall be i nored as if not received. 'f the -!=A6' received in an -!=4&!&T=+6, P:$ is different from the -!=A6' locally associated to this -!=A6 or if the -!&' received in an -!=4&!&T=+6, P:$ is different from the -!&' locally associated to this -!=A63 the OPM system shall be informed3 then the reset procedure shall be stopped. 7urther actions of the OPM system are out of the scope of the present document. 'f an -!=4&!&T=+6, P:$ is received when not e.pected3 it shall be i nored.

/.4 Test "ro edure 3or a 'ra6e Re!a5 Su&-%et1or8

The test procedure shall be used when a 5!! (or !G!-) wishes to chec" that end=to=end communication with its peer entity e.ists on an -!=A6. 5oth sides of the Gb interface may initiate this procedure independently from each other. This procedure shall be initiated upon successful completion of the reset procedure (as specified in sub=clause G4eset procedureG) and shall then be periodically repeated. $pon successful completion of an -!=A6 reset procedure3 a 5!! (or !G!-) shall start timer Tns=test3 then@ = = = $pon Tns=test e.piry3 a 5!! (or !G!-) sends an -!=+)'A& P:$ on the -!=A6 to be chec"ed3 starts timer Tns=alive and waits for an -!=+)'A&=+6, P:$ on this -!=A6. $pon receipt of an -!=+)'A& P:$ on an alive -!=A63 an !G!- (or 5!!) shall return an -!=+)'A&=+6, P:$ on the -!=A6 where the -!=+)'A& P:$ was received. $pon receipt of the -!=+)'A&=+6, P:$ in response to an -!=+)'A& P:$3 the ori inator of the -!=+)'A& P:$3 shall stop timer Tns=alive and shall start a ain timer Tns=test.

ETSI

Release )*

30

3GPP TS +,-*). /)*-*-* "0*))'*3#

The procedure is repeated each time Tns=test e.pires.

/.4.1 $&%or6a! o%ditio%s

'f an -!=+)'A&=+6, P:$ is received when not e.pected3 it shall be i nored. 'f no -!=+)'A&=+6, P:$ is received before Tns=alive e.pires3 the test procedure shall be repeated a ma.imum of -!=+)'A&=4&T4'&! attempts. +fter -!=+)'A&=4&T4'&! unsuccessful retry attempts3 the procedure is stopped3 the -!=A6 is mar"ed as dead and bloc"ed3 the OPM system and the load sharin function are informed3 and an -!=!T+T$!='ndication is sent to the -! user entity. 'f the -!=A6 is not already bloc"ed3 a bloc"in procedure is initiated usin an alive -!=A63 if any. 7urther actions of the OPM system are out of the scope of the present document.

/.4& Test Pro edure 3or a% =P Su&-%et1or8

The test procedure is used on the Gb interface to verify the communications paths between the !G!- and the 5!!. +t least one of the si nallin endpoints of the !G!- shall be tested by the 5!!3 by sendin the -!=+)'A& P:$ on any -!=A6 terminatin at any of the !G!- si nallin endpoints. +n -!& may test any peer -!& 'P endpoint at any time. 't is recommended that all remote 'P endpoints of an -!& (si nallin and data endpoints) are tested periodically3 re ardless of their operational status (operational or non=operational). $pon successful completion of the !i(e and confi uration procedures when confi ured by auto=confi uration procedures3 or upon completion of administrative confi uration3 the -!& shall start timer Tns=test. $pon e.piry of the timer Tns=test the -!& shall@ = = = send an -!=+)'A& P:$ to a peer 'P endpoint. start timer Tns=alive. upon receivin an -!=+)'A&=+6, P:$ from the peer -!& 'P endpoint3 the -!& shall stop timer Tns=alive and shall start a ain timer Tns=test.

The procedure is repeated each time that the Tns=test e.pires. $pon receipt of an -!=+)'A& P:$3 on any confi ured 'P endpoint3 the -!& shall send an -!=+)'A&=+6, P:$ to the source $:PJ'P endpoint of the -!=+)'A& P:$. $pon receipt of an -!=+)'A&=+6, P:$3 on an 'P endpoint mar"ed as non=operational3 the -!& communication path is mar"ed as operational.

/.4&.1 $&%or6a! )o%ditio%s

'f an -!=+)'A&=+6, P:$ is received when not e.pected3 it shall be discarded.

/.4&.1.1

$&%or6a! )o%ditio%s 3or si2%a!!i%2 e%d"oi%ts

'f the -!& timer Tns=alive e.pires3 the test procedure shall be repeated a ma.imum of -!=+)'A&=4&T4'&! times. +fter -!=+)'A&=4&T4'&! unsuccessful attempts the -!& communication path is mar"ed as non=operational. The OPM system and the load sharin function are informed3 and an -!=!T+T$!='ndication is sent to the -! user entity. 'f more than one si nallin endpoint is available at the !G!-3 an -!=!T+T$! P:$ may be sent to the !G!usin one of the available si nallin endpoints of the peer -!&. The -!=!T+T$! includes the two 'P endpoints that comprise the -!=A6 and a cause code G'P test failedG. 7urther actions of the OPM system is out of the scope of the present document. 'f more than one si nallin endpoints are available at the !G!- the test procedure shall continue on one or more of these endpoints. 'f all si nallin $:PJ'P endpoints of a peer !G!- -!& are mar"ed non=operational and if the -!& is confi ured by auto=confi uration procedures3 then the 5!! -!& shall start the !i(e procedure with the 4eset=bit field of the Reset Flag '& set to G2G followed by the confi uration procedure.

ETSI

Release )*

33

3GPP TS +,-*). /)*-*-* "0*))'*3#

'f an !G!- tests 'P endpoints of a peer 5!! -!& and all si nallin 'P endpoints of a peer 5!! -!& are mar"ed non= operational and if the -!& is confi ured by auto=confi uration procedures3 then the !G!- -!& shall not respond to -!=+)'A& messa es from that 5!! -!&. 'f the -!& is confi ured by administrative means3 then the !G!- -!& shall respond to -!=+)'A& messa es from that 5!! -!&. Ihen the !G!- recovers after a restart or a networ" failure and if the -!& is confi ured by auto=confi uration procedures3 it shall not respond on any -!=P:$s until the !i(e and confi uration procedures have been completed successfully.

/.4&.1.2

$&%or6a! )o%ditio%s 3or data e%d"oi%ts

'f the test procedure is bein performed on a data 'P endpoint and timer Tns=alive e.pires3 dependin on the implementation3 the test procedure may be repeated. +fter -!=+)'A&=4&T4'&! unsuccessful retry attempts3 the OPM system and the load sharin function are informed3 and an -!=!T+T$!='ndication is sent to the -! user entity. +n -!= !T+T$! procedure may be initiated towards a si nallin 'P endpoint. The -!=!T+T$! includes the two 'P endpoints that comprise the -!=A6 and a cause code G'P test failedG. 7urther actions of the OPM system is out of the scope of the present document. Ihen an -!=+)'A& fails for a path3 the sendin side is allowed to chan e both the local 'P endpoint and the remote 'P endpoint. Traffic may be processed if received on an 'P endpoint after an unsuccessful test procedure.

/.5 Pro edure 3or error re"orti%2

The reportin of protocol errors to the remote entity is done by means of the -!=!T+T$! P:$3 as further described in the rest of the present document. $pon receipt of an -!=!T+T$! P:$3 the OPM system is informed. 7urther actions of the OPM system are out of the scope of the present document.

/.5.1 $&%or6a! o%ditio%s

'f an error is detected in a received -!=!T+T$! P:$3 then the error shall not be reported to the remote -! entity.

/.6 Resour e 4istri&utio% Pro edure

&ach -! entity is responsible for determinin when to tri er the 4esource :istribution 7unction and to which 'P endpoint resource distribution can occur. This sub=clause only describes the mechanism for informin the peer -! entity the 'P endpoint at which -! user data for an M! or for an M5M! session is to be received. 4ecommended usa e of the 4esource :istribution 7unction for an 'P sub=networ" when 4esource :istribution is to be performed on a data flow concernin an M! can be found in anne. 5. The resource distribution function at an -!& may choose to chan e the 'P endpoint at which it receives -! user data for an M! or M5M! session. To achieve this3 the -! user entity shall notify the load sharin function and subseDuently the -! entity to send an -!=$-'T:+T+ with the 4=bit field set to G2G in the NS SDU Control Bits '& from the new 'P endpoint. -ote@ the 5!! may set the 4=bit field to G2G in the initial P:$ for -! user data for an M!. 'f an -!& has no -! !:$ to send for some period of time3 or if 4esource :istribution is to be performed on a data flow concernin an M5M! session3 then the -!& shall send an -!=$-'T:+T+ P:$ containin a 5!!GP :)=$-'T:+T+ (5!!GP $)= $-'T:+T+) or3 in case of an M5M! session3 a 5!!GP $)=M5M!=$-'T:+T+ with an ))6=P:$ )en th 'ndicator set to 1 (see 3GPP T! 8<.12<). Ihen the -!& receives an -!=$-'T:+T+ P:$ with 4=bit field set to G2G in the NS SDU Control Bits '&3 it shall inform the hi her layers to chan e the destination 'P endpoint for that M! or M5M! session. +ll subseDuent -! !:$s for the same M! or M5M! session shall be sent to this destination. The receivin -!& may optionally send an -!= $-'T:+T+ P:$ with the 6=bit field set to G2G in the NS SDU Control Bits '& to confirm ac"nowled ement of the reDuest to chan e the 'P endpoint.

ETSI

Release )*

3+

3GPP TS +,-*). /)*-*-* "0*))'*3#

The -!& initiatin the 4esource :istribution 7unction for an M! shall not set the 4=bit field to G2G in an -!= $-'T:+T+ P:$ for this M! once it has received an -!=$-'T:+T+ P:$ for the same M!3 irrespective of the 6=bit field value3 at the reDuested 'P endpoint.

/.6.1 $&%or6a! )o%ditio%s

'f a peer -!& continues to send -!=$-'T:+T+ for a iven M! or M5M! session to an 'P endpoint after receipt of a -!=$-'T:+T+ with 4=bit that directs traffic to a different 'P endpoint3 then the action ta"en by the -!& is implementation dependent.. The 5!! maintains the M! conte.t for a subscriber for a finite period of time. Ihen uplin" data is received for a mobile and the 5!! has no M! conte.t with the !G!- preferred 'P endpoint then the 5!! may choose to send the -! user data on one of the 'P endpoints determined by the load sharin function. Mowever3 the !G!- maintains the M! conte.t for as lon as it has location information for the M! on cell level.

Ge%era! "roto o! error #a%d!i%2

This sub=clause is not applicable to the !ub=-etwor" !ervice protocol. The followin GGeneral caseG sub=clause applies unless otherwise stated in the G!pecial casesG sub=clause.

8.1 Ge%era! ase

This sub=clause specifies procedures for the handlin of un"nown3 unforeseen3 and erroneous protocol data by the receivin entity. These procedures are called Gerror handlin proceduresG3 but in addition to providin recovery mechanisms for error situations they define a compatibility mechanism for future e.tensions of the protocol. Most error handlin procedures are mandatory for a 5!! and !G!-. :etailed error handlin procedures are implementation dependent and may vary from P)M- to P)M-. Mowever3 when e.tensions of this protocol are developed3 networ"s shall be assumed to have the error handlin that is indicated in this sub=clause as mandatory (GshallG) and that is indicated as stron ly recommended (GshouldG). 'n this sub=clause the followin terminolo y is used@ = S)ntactical error an '& is defined to be syntactically incorrect in a P:$ if it contains at least one value defined as GreservedG or Greserved for future useG3 or if its value part violates codin rules specified in the relevant protocol specification3 e. . a too short '& (the len th indicator shall be used to determine the boundary of the '&). Mowever3 it is not a syntactical error that an '& specifies in its len th indicator a reater len th than defined in the relevant protocol specificationB and Se3antic error a P:$ is defined to have semantically incorrect contents if it contains information which3 possibly dependent on the state of the receiver3 is in contradiction to the resources of the receiver andJor to the procedural part of the relevant protocol specification.

To allow for the introduction of new functions the followin rules shall be used to determine the actions of a receivin entity when it receives a P:$3 part or all of which it is unable to understand. +s the recipient is unable to tell the difference between a new3 previously unspecified codin and an erroneous codin 3 the recipient also uses the same rules for error handlin . The robustness of a recipient in handlin erroneous P:$s does not rela. the reDuirement that the transmitter shall obey the present document. Mowever3 it is intended that functionality can be radually added to an entity3 and no obstacle to intermediate phase eDuipment is intended.

8.1.1 Prese% e re>uire6e%ts o3 =%3or6atio% *!e6e%ts

There are three different presence reDuirements (M3 63 or O) for an '& within a iven P:$@ = = M (4Man!ator)4) means that the '& shall be included by the sendin side3 and that the receiver dia noses a Gmissin essential '&G error when detectin that the '& is not present. C (4Con!itional4) means@

ETSI

Release )*

31

3GPP TS +,-*). /)*-*-* "0*))'*3#

= =

that inclusion of the '& by the sender depends on conditions specified in the relevant protocol specificationB that there are conditions for the receiver to e.pect that the '& is present andJor conditions for the receiver to e.pect that the '& is not presentB these conditions depend only on the P:$ itself3 and not on the state in which the P:$ was receivedB they are "nown as static conditionsB that the receiver detectin that the '& is not present when sufficient static conditions are fulfilled for its presence3 shall dia nose a Gmissin essential '&G errorB that the receiver detectin that the '& is present when sufficient static conditions are fulfilled for its non=presence3 shall treat the '& as an optional one3 see below.

= = =

O (4O#tional4) means that the receiver shall never dia nose a Gmissin essential '&G error or shall never dia nose an error because it detects that the '& is present or that the '& is not present. There may however be conditions dependin on the states3 resources3 etc. of the receiver to dia nose other errors.

'n addition3 the followin definitions apply@ = E&&ential Ele3ent& These are the conditional (6) elements when the condition for their reception is fulfilled3 plus the mandatory (M) elements. +ny e.ception to this rule is e.plicitly stated in the relevant protocol specification. Non,E&&ential Ele3ent& -on=essential elements are all the information elements that are not defined as essential.

8.1.2 *rro%eous e7e%ts

The followin events shall be re arded as errors by the recipient and shall be treated as specified below. 6ertain types of error shall be reported to the sendin side3 in that case the erroneous P:$ and the error cause shall be returned to the sendin side by means of the appropriate error reportin P:$. The followin rules shall be applied in order of precedence@ 2) a P:$ whose type is non=e.istent or unreco nisable@ the error shall not be reported3 the P:$ shall be i noredB 0) a P:$ not consistent with the recipient#s state@ the error shall be reported with cause GP:$ not compatible with the protocol stateG3 the P:$ shall be i noredB 3) a P:$ sent in the wron direction@ the error shall be reported with cause GProtocol error = unspecifiedG3 the P:$ shall be i noredB 8) a missin essential information element@ the error shall be reported with cause GMissin essential '&G3 the P:$ shall be i noredB 9) syntactical error in an essential '&@ the error shall be reported with cause G'nvalid essential '&G3 the P:$ shall be i nored.

8.1.3 (o%-erro%eous e7e%ts

The followin events shall not be re arded as errors by the recipient@ 2) spare bits with an une.pected value in any information elementB 0) the use of additional octets in any information element with a len th indicator3 that is@ when the indicated len th is reater than defined in the relevant protocol specification (the len th indicatorl shall be used to determine the boundary of the '&)B 3) a missin non=essential information elementB 8) an un"nown information element identifierB 9) any une.pected information elementB and ;) a syntactical error in any non=essential information element.

ETSI

Release )*

3.

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ihen the recipient detects one or more of these events the receivin entity shall i nore the information that it is unable to understand and treat the P:$ on the basis of the information that remains. +dditionally3 when more information elements of a particular type are received than are e.pected3 the last one(s) shall be i nored. 'f3 because information was i nored3 the rest of the P:$ can no lon er be handled then the receivin entity shall report the error to the sendin side by means of the appropriate error reportin P:$ includin the incorrect P:$ received and the cause Gsemantically incorrect P:$G.

8.1.4 9t#er e7e%ts

The followin events should be treated on a case by case basis and the outcome may depend upon the capabilities of the recipient. 2) The recipient may accept P:$s that contain information elements that do not appear to be in the correct seDuence. &lements that occur more than once in a P:$ shall be assumed to have been transmitted in the correct order. 4ecipients that do not accept out of seDuence information elements shall re ard the P:$ as containin une.pected andJor missin information elements and follow the procedures defined in the rest of this GGeneral caseG sub=clause. 0) Ihen any '& with semantically incorrect contents is received3 the receivin entity shall react accordin to the relevant protocol specification. 'f however no such reactions are specified3 the receivin entity shall i nore that '& and treat the rest of the P:$. 'f3 because this '& was i nored3 the rest of the P:$ can no lon er be handled then the receivin entity shall report the error to the sendin side by means of the appropriate error reportin P:$ includin the incorrect P:$ received and the cause Gsemantically incorrect P:$G.

8.2 S"e ia! ases

'n case of conflict between this sub=clause and the above GGeneral caseG sub=clause3 this sub=clause ta"es precedence. 'n case of conflict between this sub=clause and the specific G+bnormal conditionsG sub=clauses in sub=clause G-etwor" !ervice 6ontrol protocolG3 the G+bnormal conditionsG sub=clauses ta"e precedence over this G!pecial casesG sub=clause.

8.2.1 4e7iatio%s 3ro6 t#e BGe%era! aseB su&- !ause

The 6ause information element (see sub=clauses GGeneral P:$ definitions and contentsG and GGeneral information elements codin G) shall be considered as a non=essential information element even when mandatory in a P:$.

8.2.2 *rror re"orti%2

The -!=!T+T$! P:$ shall be used to report error to the remote -! entity3 see sub=clause GProcedure for error reportin G. The -!=!T+T$! P:$ shall never be used to report an error detected in a received -!=!T+T$! P:$.

Ge%era! P4< de3i%itio%s a%d o%te%ts

This sub=clause is not applicable to the !ub=-etwor" !ervice protocol.

-.1 Ge%era! stru ture o3 a P4<

This sub=clause defines the eneral structure of the P:$s on the Gb interface. The eneral P:$ structure is composed of@ a) a P:$ type information elementB and b) other information elements3 as reDuired.

ETSI

Release )*

32

3GPP TS +,-*). /)*-*-* "0*))'*3#

The P:$ type '& occupies the first octet position in the P:$. This eneral structure and the numberin convention used on the Gb interface are illustrated in fi ure ?.2.2. The bits are rouped into octets. The bits of an octet are shown hori(ontally and are numbered from 2 to <. Multiple octets are shown vertically and are numbered from 2 to n. The octets shall be transmitted by increasin order of octet number. Iithin each octet3 the bits shall be transmitted by increasin order of bit number i.e. bit 2 of octet 2 shall be transmitted first3 bit < of octet n shall be transmitted last.
, octet ) octets 0< 3< ---n 2 . 1 + 3 P4< t5"e ot#er i%3or6atio% e!e6e%ts 0 )

3i(ure 7-)-)4 General PD: structure and nu&5erin( con!ention &ach P:$ definition includes a table listin the information elements ('&s) "nown in the P:$ and the order of their appearance in the P:$. $nless specified otherwise in the P:$ descriptions3 a particular information element shall not be present more than once in a iven P:$. +ll information elements that may be repeated are e.plicitly indicated. 7or each information element the table indicates@ a) The name of the information element (which may ive an idea of the semantics of the element). b) Possibly a reference to another G!M Technical !pecification where the information element is described. c) The presence reDuirement indication (M3 63 or O) for the '& as defined in sub=clause GGeneral protocol error handlin G. d) The format (T3 )3 A) of the information element. !ee further description of the type (T)3 len th ()) and A (value) fields in sub=clause GGeneral structure of the information elementsG. e) The len th of the information element (or permissible ran e of len ths)3 in octets3 in the P:$3 where GQG means that the ma.imum len th of the '& is only constrained by the lower layer protocol. This indication is non= normative. The indicated len th includes all the T3 )3 A fields present in the '&. f) !ub=clauses specifyin 3 where appropriate3 conditions for '&s with presence reDuirement 6 or O in the relevant P:$ which to ether with other conditions specified in 3GPP T! 8<.12; define when the information elements shall be included or not3 what non=presence of such '&s means3 and = for '&s with presence reDuirement 6 = the static conditions for presence andJor non=presence of the '&s3 see sub=clause GGeneral protocol error handlin G.

-.2 (et1or8 Ser7i e )o%tro! P4<s

The -etwor" !ervice 6ontrol P:$s are also referred to as -! P:$s in the rest of the present document.

-.2.1 (S-$L=V*
This P:$ is used to test an -!=A6. P:$ type@ :irection@ -!=+)'A& 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-)-)4 NS'A96/E PD: contents
6nfor&ation ele&ent P4< t5"e Reference 10.3./ Presence M 3or&at V 9en(th 1

ETSI

Release )*

3,

3GPP TS +,-*). /)*-*-* "0*))'*3#

-.2.2 (S-$L=V*-$)C
This P:$ ac"nowled es a received -!=+)'A& P:$ and is sent on the -!=A6 where the -!=+)'A& P:$ was received. P:$ type@ :irection@ -!=+)'A&=+6, !G!- to 5!!3 5!! to !G!Ta5le 7-0-0-)4 NS'A96/E'A8= PD: contents
6nfor&ation ele&ent P4< t5"e Reference 10.3./ Presence M 3or&at V 9en(th 1

-.2.3 (S-:L9)C
This P:$ indicates that an -!=A6 shall be bloc"ed at the recipient entity. P:$ type@ :irection@ -!=5)O6, 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-3-)4 NS'$9>8= PD: contents
6nfor&ation ele&ent P4< t5"e )ause (S-V)= Reference 10.3./ 10.3.2 10.3.5 Presence M M M 3or&at V TLV TLV 9en(th 1 3 4

-.2.4 (S-:L9)C-$)C
This P:$ ac"nowled es that an -!=A6 has been bloc"ed for use. P:$ type@ :irection@ -!=5)O6,=+6, !G!- to 5!!3 5!! to !G!Ta5le 7-0-+-)4 NS'$9>8='A8= PD: contents
6nfor&ation ele&ent P4< t5"e (S-V)= Reference 10.3./ 10.3.5 Presence M M 3or&at V TLV 9en(th 1 4

ETSI

Release )*

37

3GPP TS +,-*). /)*-*-* "0*))'*3#

-.2.5 (S-R*S*T
This P:$ indicates that the -! peer entity is tryin to reset one -!=A6. P:$ type@ :irection@ -!=4&!&T 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-1-)4 NS'RESET PD: contents
6nfor&ation ele&ent P4< t5"e )ause (S-V)= (S*= Reference 10.3./ 10.3.2 10.3.5 10.3.6 Presence M M M M 3or&at V TLV TLV TLV 9en(th 1 3 4 4

Typical cause values are@ OPM intervention3 &Duipment failure.

-.2.6 (S-R*S*T-$)C
This P:$ ac"nowled es the reset of the indicated -!=A6. P:$ type@ :irection@ -!=4&!&T=+6, 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-.-)4 NS'RESET'A8= PD: contents
6nfor&ation ele&ent P4< t5"e (S-V)= (S*= Reference 10.3./ 10.3.5 10.3.6 Presence M M M 3or&at V TLV TLV 9en(th 1 4 4

-.2./ (S-ST$T<S
This P:$ is used to report error conditions. P:$ type@ :irection@ -!=!T+T$! !G!- to 5!!3 5!! to !G!Ta5le 7-0-2-)4 NS'STAT:S PD: contents
6nfor&ation ele&ent P4< t5"e )ause (S-V)= (S P4< :V)= List o3 =P4 *!e6e%ts List o3 =P6 *!e6e%ts Reference 10.3./ 10.3.2 10.3.5 10.3.3 10.3.1 10.3.2 10.3.2d Presence M M ) ) ) ) ) 3or&at V TLV TLV TLV TLV TLV TLV 9en(th 1 3 4 3-D 4 10-D 22-D

ETSI

Release )*

+*

3GPP TS +,-*). /)*-*-* "0*))'*3#

-.2./.1

Stati

o%ditio%s 3or (S-V)=

The NS!"CI '& shall be included when the Cause '& is set to one of the followin values@ a) G-!=A6 bloc"edGB b) G-!=A6 un"nownGB and shall not be included otherwise.

-.2./.2

Stati

o%ditio%s 3or (S P4<

The NS PDU '& shall be included if the -!=!T+T$! messa e is sent in response to a received -! P:$ within which an error was detected i.e. when the Cause '& is set to one of the followin values@ a) G!emantically incorrect P:$GB b) GP:$ not compatible with the protocol stateGB c) GProtocol error = unspecifiedGB d) G'nvalid essential '&GB e) GMissin essential '&GB and shall not be included otherwise. This is the whole P:$ received with error. This P:$ may be truncated if it e.ceeds the information carryin capacity of the -!.

-.2./.3

Stati

o%ditio%s 3or :V)=

The B"CI '& shall be included when the Cause '& is set to one of the followin values@ a) G5A6' un"nown on that -!&GB and shall not be included otherwise.

-.2./.4

Stati

o%ditio%s 3or List o3 =P4 *!e6e%ts

The List of IP4 Elements '& shall be included when the Cause '& is set to one of the followin values@ a) G 'P test failedGB and the 'P endpoints of the -!=A6 that failed are 'Pv8 endpoints. The List of IP4 Elements '& shall be the only conditional '& sent in a -!=!T+T$! P:$. The List of IP4 Elements '& shall not be included otherwise.

-.2./.5

Stati

o%ditio%s 3or List o3 =P6 *!e6e%ts

The List of IP Elements '& shall be included when the Cause '& is set to one of the followin values@ a) G 'P test failedGB and the 'P endpoints of the -!=A6 that failed are 'Pv; endpoints. The List of IP Elements '& shall be the only conditional '& sent in a -!=!T+T$! P:$. The List of IP Elements '& shall not be included otherwise.

ETSI

Release )*

+)

3GPP TS +,-*). /)*-*-* "0*))'*3#

-.2.8 (S-<(:L9)C
This P:$ indicates that an -!=A6 shall be unbloc"ed at the recipient entity. P:$ type@ :irection@ -!=$-5)O6, 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-,-)4 NS':N$9>8= PD: contents
6nfor&ation ele&ent P4< t5"e Reference 10.3./ Presence M 3or&at V 9en(th 1

-.2.- (S-<(:L9)C-$)C
This P:$ ac"nowled es that an -!=A6 has been unbloc"ed. P:$ type@ :irection@ -!=$-5)O6,=+6, !G!- to 5!!3 5!! to !G!Ta5le 7-0-7-)4 NS':N$9>8='A8= PD: contents
6nfor&ation ele&ent P4< t5"e Reference 10.3./ Presence M 3or&at V 9en(th 1

-.2.10 (S-<(=T4$T$
This P:$ transfers one -! !:$ between the 5!! and !G!-. P:$ type@ :irection@ -!=$-'T:+T+ 5!! to !G!-3 !G!- to 5!! Ta5le 7-0-)*-)4 NS':N6TDATA PD: contents
6nfor&ation ele&ent P4< t5"e (S S4< )o%tro! :its :V)= (S S4< Reference 10.3./ 10.3.10.3.1 10.3.4 Presence M M M M 3or&at V V V V 9en(th 1 1 2 1-D

The len th of the NS SDU information element shall be derived by the -etwor" !ervice 6ontrol entity from the len th of the complete -!=$-'T:+T+ P:$ provided by the !ub=-etwor" !ervice entity to the -etwor" !ervice 6ontrol entity.

-.3 Su&-(et1or8 Ser7i e )o%tro! P4<s

The !ub=-etwor" !ervice 6ontrol P:$s are also referred to as !-! P:$s in the rest of the present document. The !ub=-etwor" !ervice 6ontrol P:$s are only used in an 'P sub=networ".

-.3.1 S(S-$)C
The !-!=+6, P:$ is used to ac"nowled e the !-!=+:: P:$3 the !-!=:&)&T& P:$3 or the !-!= 6M+-G&I&'GMT P:$.

ETSI

Release )*

+0

3GPP TS +,-*). /)*-*-* "0*))'*3#

P:$ type@ :irection@

!-!=+6, 5!! to !G!-3 !G!- to 5!! Ta5le 7-3-)-)4 SNS'A8= PD: contents

6nfor&ation ele&ent Reference Presence 3or&at 9en(th P4< t5"e 10.3./ M V 1 (S*= 10.3.6 M TLV 4 Tra%sa tio% =4 10.3.10 M V 1 )ause 10.3.2 9 TLV 3 =P $ddress a) 10.3.2& ) TV 6-18 List o3 =P4 *!e6e%ts &) 10.3.2 ) TLV 10-D List o3 =P6 *!e6e%ts &) 10.3.2d ) TLV 22-D a) t#e =P $ddress =* s#a!! o%!5 &e "rese%t i3 t#e B)auseB 7a!ue is set to B<%8%o1% =P addressB. &) o%e or 6ore o3 t#ese o%ditio%a! =*s s#a!! &e "rese%t i3 t#e B)auseB 7a!ue is set to B<%8%o1% =P e%d"oi%tB.

-.3.2 S(S-$44
The !-!=+:: P:$ is used to add additional 'P &ndpoints. P:$ type@ :irection@ !-!=+:: 5!! to !G!-3 !G!- to 5!! Ta5le 7-3-0-)4 SNS'ADD PD: contents
6nfor&ation ele&ent Reference Presence 3or&at P4< t5"e 10.3./ M V (S*= 10.3.6 M TLV Tra%sa tio% =4 10.3.10 M V List o3 =P4 *!e6e%ts a) 10.3.2 ) TLV List o3 =P6 *!e6e%ts a) 10.3.2d ) TLV a) o%e a%d o%!5 o%e o3 t#e o%ditio%a! =*s s#a!! &e "rese%t. 9en(th 1 4 1 10-D 22-D

-.3.3 S(S-)E$(G*A*=GET
The !-!=6M+-G&I&'GMT P:$ is used to chan e the si nallin wei ht andJor data wei ht of an 'P endpoint. P:$ type@ :irection@ !-!=6M+-G&I&'GMT 5!! to !G!-3 !G!- to 5!! Ta5le 7-3-3-)4 SNS'8?ANGE@E6G?T PD: contents
6nfor&ation ele&ent Reference Presence 3or&at P4< t5"e 10.3./ M V (S*= 10.3.6 M TLV Tra%sa tio% =4 10.3.10 M V List o3 =P4 *!e6e%ts a) 10.3.2 ) TLV List o3 =P6 *!e6e%ts a) 10.3.2d ) TLV a) o%e a%d o%!5 o%e o3 t#e o%ditio%a! =*s s#a!! &e "rese%t. 9en(th 1 4 1 10-D 22-D

-.3.4 S(S-)9('=G
The !-!=6O-7'G P:$ is used to confi ure a -!& to a peer -!&. P:$ type@ !-!=6O-7'G

ETSI

Release )*

+3

3GPP TS +,-*). /)*-*-* "0*))'*3#

:irection@

5!! to !G!-3 !G!- to 5!! Ta5le 7-3-+-)4 SNS'8>N36G PD: contents

6nfor&ation ele&ent Reference Presence 3or&at P4< t5"e 10.3./ M V *%d '!a2 10.3.2a M V (S*= 10.3.6 M TLV List o3 =P4 *!e6e%ts a) 10.3.2 ) TLV List o3 =P6 *!e6e%ts a) 10.3.2d ) TLV a) o%e a%d o%!5 o%e o3 t#e o%ditio%a! =*s s#a!! &e "rese%t.

9en(th 1 1 4 10-D 22-D

-.3.5 S(S-)9('=G-$)C
The !-!=6O-7'G=+6, P:$ is used to ac"nowled e an !-!=6O-7'G P:$. The !-!=6O-7'G=+6, P:$ shall be sent to the source 'P &ndpoint of the correspondin !-!=6O-7'G P:$. P:$ type@ :irection@ !-!=6O-7'G=+6, 5!! to !G!-3 !G!- to 5!! Ta5le 7-3-1-)4 SNS'8>N36G'A8= PD: contents
6nfor&ation ele&ent P4< t5"e (S*= )ause Reference 10.3./ 10.3.6 10.3.2 Presence M M 9 3or&at V TLV TLV 9en(th 1 4 3

-.3.6 S(S-4*L*T*
The !-!=:&)&T& P:$ is used to delete previously confi ured 'P &ndpoints. P:$ type@ :irection@ !-!=:&)&T& 5!! to !G!-3 !G!- to 5!! Ta5le 7-3-.-)4 SNS'DE9ETE PD: contents
6nfor&ation ele&ent Reference Presence 3or&at P4< t5"e 10.3./ M V (S*= 10.3.6 M TLV Tra%sa tio% =4 10.3.10 M V =P $ddress a) 10.3.2& ) TV List o3 =P4 *!e6e%ts a) 10.3.2 ) TLV List o3 =P6 *!e6e%ts a) 10.3.2d ) TLV a) o%e a%d o%!5 o%e o3 t#e o%ditio%a! =*s s#a!! &e "rese%t. 9en(th 1 4 1 6-18 10-D 22-D

-.3./ S(S-S=F*
The !-!=!'N& P:$ is used to indicate to the peer -!& the ma.imum number of -!=A6s or a chan e in the -!=A6 capacity. The !-!=!'N& P:$ is used to si nal the restart of a -!& to a peer -!&. P:$ type@ :irection@ !-!=!'N& 5!! to !G!-

ETSI

Release )*

++

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ta5le 7-3-2-)4 SNS'S6AE PD: contents

6nfor&ation ele&ent P4< t5"e Reference 10.3./ Presence M 3or&at V TLV TV TV TV TV 9en(th 1 4 2 3 3 3

(S*= 10.3.6 M Reset '!a2 M Ma.i6u6 (u6&er 10.3.2e M o3 (S-V)s (u6&er o3 =P4 10.3.23 ) *%d"oi%ts a) (u6&er o3 =P6 10.3.22 ) *%d"oi%ts a) a) $t !east o%e o3 t#ese o%ditio%a! =*s s#a!! &e "rese%t.

-.3.8 S(S-S=F*-$)C
The !-!=!'N&=+6, P:$ is used to ac"nowled e an !-!=!'N& P:$. The !-!=!'N&=+6, P:$ shall be sent to the source 'P &ndpoint of the correspondin !-!=!'N& P:$. P:$ type@ :irection@ !-!=!'N&=+6, !G!- to 5!! Ta5le 7-3-,-)4 SNS'S6AE'A8= PD: contents
6nfor&ation ele&ent P4< t5"e (S*= )ause Reference 10.3./ 10.3.6 10.3.2 Presence M M 9 3or&at V TLV TLV 9en(th 1 4 3

10

Ge%era! i%3or6atio% e!e6e%ts odi%2

This sub=clause is not applicable to the !ub=-etwor" !ervice protocol.

10.1 Ge%era! stru ture o3 t#e i%3or6atio% e!e6e%ts

The eneral information element structure is composed of (see fi ure 21.2.2)@ a) an 'nformation &lement 'dentifier (also referred to as the T field)B b) a len th indicator (also referred to as the ) field)B c) the information element value (also referred to as the A field). 'nformation elements have the T)A3 the TA or the A format3 as specified in the relevant protocol specification. The format of any iven information element may depend on the conte.t e. . on the messa e type.
, octet ) octets 0< 0a octet 3 --octet --- n 2 . 1 + 3 0 )

=%3or6atio% *!e6e%t =de%ti3ier (=*=) !e%2t# i%di ator i%3or6atio% e!e6e%t 7a!ue

3i(ure )*-)-)4 6nfor&ation ele&ent structure< T9/ for&at

ETSI

Release )*

+1

3GPP TS +,-*). /)*-*-* "0*))'*3#

, octet ) --octet --- n

i%3or6atio% e!e6e%t 7a!ue

3i(ure )*-)-04 6nfor&ation ele&ent structure< / for&at Ihen a field e.tends over more than one octet3 the order of bit values pro ressively decreases as the octet number increases. The least si nificant bit of the field is represented by the lowest numbered bit of the hi hest numbered octet of the field.

10.1.1 =%3or6atio% *!e6e%t =de%ti3ier

The first octet of an information element havin the T)A format contains the '&' of the information element. 'f this octet does not correspond to an '&' "nown in the P:$3 the receiver shall assume that the ne.t octet is the first octet of the len th indicator field and shall interpret it as described in the G)en th indicatorG sub=clause. This rule allows the receiver to s"ip un"nown information elements and to analyse any followin information elements.

10.1.2 Le%2t# i%di ator

The len th indicator shall be included in all information elements havin the T)A format. 'nformation elements may be variable in len th. The len th indicator is one or two octet lon 3 the second octet may be absent. This field consists of the field e.tension bit3 1J2 e.t3 and the len th of the value field which follows3 e.pressed in octets. The field e.tension bit enables e.tension of the len th indicator to two octets. 5it < of the first octet is reserved for the field e.tension bit. 'f the field e.tension bit is set to 1 ((ero)3 then the second octet of the len th indicator is present. 'f the field e.tension bit is set to 2 (one)3 then the first octet is the final octet of the len th indicator. The len th of the value field of the '& occupies the rest of the bits in the len th indicator.
, octet 0 octet 0a 001 e.t 2 . 1 + !e%2t# !e%2t# 3 0 )

3i(ure )*-)-0-)4 9en(th indicator structure The 5!! or !G!- shall not consider the presence of octet 0a in a received '& as an error when the '& is short enou h for the len th to be coded in octet 0 only.

10.2 =%3or6atio% e!e6e%t des ri"tio%

The descriptions of the information elements are or ani(ed in alphabetical order of the '& name. &ach '& is described in one sub=clause. + fi ure of the sub=clause defines the structure of the '& indicatin @ = = = = the position of the '&'3 when presentB the fields the '& value part is composed ofB the position of the len th indicator3 when presentB possibly octet numbers of the octets that compose the '&.

7inally3 the sub=clause may contain fi ures definin the structure and value ran e of the fields that compose the '& value part.

ETSI

Release )*

+.

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ihere the description of information elements in the present document contains bits defined to be Gspare bitsG3 these bits shall set to (ero by the sendin side3 and their value shall be i nored by the receivin side. The term GdefaultG may be used3 implyin that the value defined shall be used in the absence of any assi nment3 or that this value allows ne otiation of alternative values in between the two peer entities.

10.3 =%3or6atio% e!e6e%ts

The '&' values are indicated in table 21.3.2@ Ta5le )*-3-)4 6E6 codin(
, 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 6E6 codin( . 1 + 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 1 0 0 1 0 0 0 1 0 0 0 1 0 0 0 1 0 ot#er 7a!ues 6nfor&ation ele&ent na&e 0 0 0 1 1 0 0 1 1 0 0 1 1 ) 0 1 0 1 0 1 0 1 0 1 0 1 )ause (S-V)= (S P4< :V)= (S*= List o3 =P4 *!e6e%ts List o3 =P6 *!e6e%ts Ma.i6u6 (u6&er o3 (S-V)s (u6&er o3 =P4 *%d"oi%ts (u6&er o3 =P6 *%d"oi%ts Reset '!a2 =P $ddress reser7ed 3or 3uture use

10.3.1 :V)=
This '& is used for multiple.in 5A6s on -!=A6s.
, octet ) octets 0< 0a octet 3 octet + 2 . 1 + 3 0 )

=*= !e%2t# i%di ator 6ost si2%i3i a%t o tet o3 :V)= !east si2%i3i a%t o tet o3 :V)=

3i(ure )*-3-)-)4 $/86 infor&ation ele&ent

10.3.2 )ause
This '& may be used to indicate to the peer -! entity the reason which tri ered a procedure3 or the reason of an abnormal condition.
, octet ) octets 0< 0a octet 3 2 . 1 + 3 0 )

=*= !e%2t# i%di ator ause 7a!ue

3i(ure )*-3-0-)4 8ause infor&ation ele&ent

ETSI

Release )*

+2

3GPP TS +,-*). /)*-*-* "0*))'*3#

The cause values are indicated in table 21.3.0.2@ Ta5le )*-3-0-)4 8ause !alues
8ause !alue codin( , 2 . 1 + 3 0 ) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 0 1 1 0 0 0 0 1 1 0 0 0 0 0 0 1 1 0 1 0 0 0 0 1 1 1 0 0 0 0 0 1 1 1 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 1 0 0 0 0 1 0 0 1 1 0 0 0 1 0 1 0 0 ot#er 7a!ues 8ause na&e Tra%sit %et1or8 3ai!ure 9GM i%ter7e%tio% *>ui"6e%t 3ai!ure (S-V) &!o 8ed (S-V) u%8%o1% :V)= u%8%o1% o% t#at (S* Se6a%ti a!!5 i% orre t P4< P4< %ot o6"ati&!e 1it# t#e "roto o! state Proto o! error - u%s"e i3ied =%7a!id esse%tia! =* Missi%2 esse%tia! =* =%7a!id %u6&er o3 =P4 *%d"oi%ts =%7a!id %u6&er o3 =P6 *%d"oi%ts =%7a!id %u6&er o3 (S-V)s =%7a!id 1ei2#ts <%8%o1% =P e%d"oi%t <%8%o1% =P address =P test 3ai!ed reser7ed 3or 3uture use

10.3.2a *%d '!a2

This '& is used to indicate last !-!=6O-7'G P:$ to be sent to the peer -! entity. +ll unused bits are spare.
, octet ) 2 . 1 s"are + 3 0 ) *-&it

3i(ure )*-3-0a-)4 End 3la( infor&ation ele&ent The G&=bitG is coded as shown below@ 1 +dditional P:$s will be sent. 2 )ast P:$ sent.

10.3.2& =P $ddress
This '& identifies an 'P address.
, >ctet ) >ctet 0 >ctets 3 'n 2 . + =*= $ddress T5"e $ddress 7a!ue 1 3 0 )

3i(ure )*-3-05-)4 6P Address infor&ation ele&ent Ihere GnG is ; if the +ddress Type is 'Pv8 and GnG is 2< if the +ddress Type is 'Pv;. The G+ddress TypeG is coded as shown in table 21.3.0b.2.

ETSI

Release )*

+,

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ta5le )*-3-05-)4 BAddress T%peB codin(

codin( 0 1 2 Reser7ed Address T%pe Reser7ed =P74 =P76 $!! 7a!ues %ot e."!i it!5 s#o1% are reser7ed 3or 3uture use.

10.3.2

List o3 =P4 *!e6e%ts

, octet ) octet 0< 0a octets 3')* octets C ' "0D,n# 2 . + =*= Le%2t# =%di ator =P4 *!e6e%t 1 =P4 *!e6e%t % 1 3 0 )

This '& identifies a list of 'Pv8 elements.

3i(ure )*-3-0c-)4 9ist of 6P+ Ele&ents infor&ation ele&ent The len th depends on the number of 'P8 &lements@ n. The codin of an 'P8 &lement is@
, octet "ED)#'"ED+# octet "ED1#'"ED.# octet "ED2# octet "ED,# 2 . 1 + 3 =P74 $ddress <4P Port Va!ue Si2%a!!i%2 Aei2#t 4ata Aei2#t 0 )

where . K <i = ; (2 i n).

10.3.2d List o3 =P6 *!e6e%ts

This '& identifies a list of 'Pv; elements.
, octet ) octet 0< 0a octets 3' 00 octets C ' "0D0*n# 2 . 1 + 3 0 )

=*= Le%2t# =%di ator =P6 *!e6e%t 1 =P6 *!e6e%t %

3i(ure )*-3-0d-)4 9ist of 6P. Ele&ents infor&ation ele&ent The len th depends on the number of 'P; &lements@ n . The codin of an 'P; &lement is@
, octet "ED)#'"ED).# octet "ED)2#'"ED),# octet "ED)7# octet "ED0*# 2 . 1 + 3 0 )

=P76 $ddress <4P Port Va!ue Si2%a!!i%2 Aei2#t 4ata Aei2#t

where . K 01i = 2< (2 i n).

10.3.2e Ma.i6u6 (u6&er o3 (S-V)s

This '& identifies the ma.imum number of -!=A6s.

ETSI

Release )* , octet ) octet 0 octet 3 2 . 1

+7 + 3 0

3GPP TS +,-*). /)*-*-* "0*))'*3# )

=*= 6ost si2%i3i a%t o tet o3 Ma.i6u6 (u6&er o3 (S-V)s !east si2%i3i a%t o tet o3 Ma.i6u6 (u6&er o3 (S-V)s

3i(ure )*-3-0e-)4 MaEi&u& Nu&5er of NS'/8s infor&ation ele&ent

10.3.23 (u6&er o3 =P4 *%d"oi%ts

This '& identifies the number of 'Pv8 endpoints.
, octet ) octet 0 octet 3 2 . 1 + 3 0 )

=*= 6ost si2%i3i a%t o tet o3 (u6&er o3 =P4 *%d"oi%ts !east si2%i3i a%t o tet o3 (u6&er o3 =P4 *%d"oi%ts

3i(ure )*-3-0f-)4 Nu&5er of 6P+ Endpoints infor&ation ele&ent

10.3.22 (u6&er o3 =P6 *%d"oi%ts

This '& identifies the number of 'Pv; endpoints.
, octet ) octet 0 octet 3 2 . 1 + 3 0 )

=*= 6ost si2%i3i a%t o tet o3 (u6&er o3 =P6 *%d"oi%ts !east si2%i3i a%t o tet o3 (u6&er o3 =P6 *%d"oi%ts

3i(ure )*-3-0(-)4 Nu&5er of 6P. Endpoints infor&ation ele&ent

10.3.3 (S P4<
This '& is included in the -!=!T+T$! P:$ sent in answer to an erroneous -! P:$. This '& contains the erroneous P:$ received. The erroneous P:$ may be truncated in order to fit in the ma.imum si(e of the -!=!T+T$! P:$.
, octet ) octets 0< 0a octet 3 --octet n 2 . 1 + 3 0 )

=*= !e%2t# i%di ator (S P4<

3i(ure )*-3-3-)4 NS PD: infor&ation ele&ent

10.3.4 (S S4<
This '& contains one and only one -! !:$ transmitted across the Gb interface.
, octet ) --octet n 2 . 1 + 3 0 )

(S S4<

3i(ure )*-3-+-)4 NS SD: infor&ation ele&ent

ETSI

Release )*

1*

3GPP TS +,-*). /)*-*-* "0*))'*3#

'n this G-! !:$G information element3 bit i of octet j is eDual to bit i of octet j of the -! !:$3 as defined in the -! user protocol specification.

10.3.5 (S-V)=
This '& unambi uously identifies one -!=A6 amon st all the -!=A6s used between one !G!- and the connected 5!!s.
, octet ) octets 0< 0a octet 3 octet + 2 . 1 + 3 0 )

=*= !e%2t# i%di ator 6ost si2%i3i a%t o tet o3 (S-V)= !east si2%i3i a%t o tet o3 (S-V)=

3i(ure )*-3-1-)4 NS'/86 infor&ation ele&ent

10.3.6 (S*=
This '& unambi uously identifies one -!&.
, octet ) octets 0< 0a octet 3 octet + 2 . 1 + 3 0 )

=*= !e%2t# i%di ator 6ost si2%i3i a%t o tet o3 (S*= !east si2%i3i a%t o tet o3 (S*=

3i(ure )*-3-.-)4 NSE6 infor&ation ele&ent

10.3./ P4< t5"e

Ta5le )*-3-2-)4 PD: t%pe codin(
, 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 PD: t%pe codin( 2 . 1 + 3 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 0 1 0 0 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 1 0 0 0 0 1 1 0 0 0 0 1 1 1 0 0 0 1 1 1 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 1 0 0 1 0 0 1 ot#er 7a!ues PD: na&e ) 0 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 1 (S-<(=T4$T$ (S-R*S*T (S-R*S*T-$)C (S-:L9)C (S-:L9)C-$)C (S-<(:L9)C (S-<(:L9)C-$)C (S-ST$T<S (S-$L=V* (S-$L=V*-$)C S(S-$)C S(S-$44 S(S-)E$(G*A*=GET S(S-)9('=G S(S-)9('=G-$)C S(S-4*L*T* S(S-S=F* S(S-S=F*-$)C reser7ed 3or 3uture use

10.3./a Reset '!a2

This '& is used to indicate if the peer -! entity shall reset all confi uration information. +ll unused bits are spare.

ETSI

Release )* , octet ) octet 0 2 .

1) 1 =*= S"are + 3 0

3GPP TS +,-*). /)*-*-* "0*))'*3# ) Reset&it

3i(ure )*-3-2a-)4 Reset 3la( infor&ation ele&ent The G4eset=bitG is coded as shown below@ 1 :o not reset. 2 4eset.

10.3.8 (7oid) 10.3.- (S S4< )o%tro! :its

This '& is used to indicate additional information about the -!=!:$ to the user of the -! entity. +ll unused bits are spare.
, octet ) 2 . s"are 1 + 3 0 )-&it ) R-&it

3i(ure )*-3-7-)4 NS SD: 8ontrol $its infor&ation ele&ent The G4=bitG is coded as shown below@ 1 -o reDuest for chan e flowB 2 4eDuest chan e flow. The G6=bitG is coded as shown below@ 1 -o confirmation for chan e flowB 2 6onfirm chan e flow.

10.3.10 Tra%sa tio% =4

This '& provides an identifier for !-! P:$s.
, octet ) 2 . 1 Va!ue + 3 0 )

3i(ure )*-3-)*-)4 Transaction 6D infor&ation ele&ent

11

List o3 s5ste6 7aria&!es

Ta5le ))-)4 S%ste& ti&ers
Ti&er !alue 1s to 120s 1s to 120s 1s to 60s 3s 1s-10s Notes Guards t#e &!o 8i%2 a%d u%&!o 8i%2 "ro edures Guards t#e reset "ro edure Periodi it5 o3 t#e (S-V) test "ro edure Guards t#e (S-V) test "ro edure Guards t#e S(S "ro edures Relation to other ti&ers %o%e %o%e %o%e %o%e %o%e

Ti&er na&e T%s-&!o 8 T%s-reset T%s-test T%s-a!i7e Ts%s-"ro7

ETSI

Release )*

10

3GPP TS +,-*). /)*-*-* "0*))'*3#

Ta5le ))-04 S%ste& counters

8ounter na&e (S-:L9)C-R*TR=*S (S-<(:L9)C-R*TR=*S (S-$L=V*-R*TR=*S S(S-$44-R*TR=*S S(S-)9('=G-R*TR=*S S(S-)E$(G*A*=GET-R*TR=*S S(S-4*L*T*-R*TR=*S S(S-S=F*-R*TR=*S /alue 3 3 10 3 3 3 3 3 re re re re re re re re Notes o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue o66e%ded 7a!ue

ETSI

Release )*

13

3GPP TS +,-*). /)*-*-* "0*))'*3#

$%%e. $ (i%3or6ati7e)+ Re o66e%ded usa2e o3 :V)= a%d (S*=

This anne. recommends a way to use 5A6's and -!&'s3 avoidin hu e and unfle.ible confi uration data at the !G!-. This anne. uses concepts defined in 3GPP T! 8<.12<. The "ey points are@ = = + 5A6' needs not to be uniDue within an !G!-3 a 5A6' is uniDue within an -! &ntity. 5A6' to ether with -!&' uniDuely identify a 5A6 within an !G!- (the lobal identifier within an !G!- is 5A6'R-!&'). 5A6's correspondin to PTP functional entities need not to be statically confi ured at the !G!- side@ no fi.ed3 permanent relationship is reDuired in the !G!- between PTP 5A6's and -!=A6s.

Iith the -!&'3 the !G!- needs not to be updated when a new cell (5A6') is added to a 5!! (-!&'). The pre=confi uration of a cell in the !G!- and the constraint in the number of 5A6s in an !G!- are not needed@ = The !G!- "eeps detailed MM information about an M! while the M! is in the 4&+:L state3 i.e. the !G!"nows the 5A6' and -!&' which can be used to contact the M! for downlin" transmission. The 5A6' and -!&' are passed from -! to 5!!GP and from 5!!GP to the upper layers as a primitive parameter in every uplin" pac"et received by the !G!-. !ubseDuent downlin" ))6 frames to this M! shall be transmitted by the !G!- over the 5A6 identified by this 5A6'R-!&'. +n !G!- in !T+-:5L state will pa e an M! before sendin downlin" traffic. The M! will respond with an ))6 pac"et that will put the MM conte.t in 4&+:L state and will deliver the 5A6' and -!&' to the user of 5!!GP.

7or pa in purposes3 the !G!- only needs to "now the correspondence between each 4outein +rea and one or more -!&'(s) where to send the correspondin pa in messa es. Pa in messa es for a mobile in !T+-:5L state shall always be sent over 5A6'K1 of an -!&' and for a mobile in 4&+:L state the circuit pa e is sent over the PTP 5A6 identified by the 5A6'R-!&'. There may be -!&'(s) where 5A6'K1 is not used.

ETSI

Release )*

1+

3GPP TS +,-*). /)*-*-* "0*))'*3#

$%%e. : (i%3or6ati7e)+ Re o66e%ded usa2e o3 Resour e 4istri&utio% 3or =P

This anne. recommends a way to support resource distribution over the Gb in an 'P sub=networ". 4esource distribution provides a means to control the 'P endpoint at which the -! user traffic for a mobile is received. !ome e.amples of resource distribution over the Gb@ E5a3#le 2 5oth -! entities tri er resource distribution (refer to fi ure 5.2). The 5!! receives an uplin" ))6 P:$ from the mobile and creates a mobile conte.t. -ow the 5!! selects the source 'PJ$:P2 endpoint (internal implementation dependent) and a destination 'PJ$:P 3 endpoint ('P load sharin dependent) on which to send -! !:$s associated with the mobile. The 5!! sends the uplin" -!=$-'T:+T+ (with 4=bit set and the )!P correspondin to the 'P endpoints selected) to the !G!- from 'PJ$:P2 to 'PJ$:P3. On receipt of uplin" -!=$-'T:+T+ for the mobile the !G!- may also choose to chan e the 'P endpoint at which it wishes to receive uplin" -!=$-'T:+T+ for the mobile to 'PJ$:P 8. The !G!responds by sendin a downlin" -!=$-'T:+T+ with 4=bit and 6=bit set to 2 from the 'PJ$:P 8 at to 'PJ$:P2. !ubseDuent uplin" and downlin" -!=$-'T:+T+ for the mobile shall follow the dotted path ('PJ$:P 2 and 'PJ$:P8) throu h the 'P sub=networ". 5!! -!=$-'T:+T+(4=bit) -!=$-'T:+T+(4=bit3 6=bit) !G!-

'PJ$:P2

'PJ$:P3

'PJ$:P0

'PJ$:P8

3i(ure $-)4 EEa&ple ) of 5oth NS entities re;uestin( chan(e flow E5a3#le 0 Only one -! entity tri ers resource distribution (refer to fi ure 5.0). The 5!! sends an uplin" -!=$-'T:+T+ with 4=bit set from 'PJ$:P 2 to 'PJ$:P3 at the !G!-. The !G!- may choose not to tri er resource distribution3 but the !G!- confirms receipt of the GreDuest chan e flowG by sendin the in the ne.t downlin" -!=$-'T:+T+ with 6=bit set to 'PJ$:P 2. !ubseDuent uplin" data transfer for the mobile will follow the dotted paths from 'PJ$:P 2 to 'PJ$:P3 and downlin" data transfer from 'PJ$:P8 to 'PJ$:P2.

ETSI

Release )*

11

3GPP TS +,-*). /)*-*-* "0*))'*3#

5!! -!=$-'T:+T+(4=bit) -!=$-'T:+T+(6=bit)

!G!-

'PJ$:P2

'PJ$:P3

'PJ$:P0

'PJ$:P8

3i(ure $-04 EEa&ple 0 of onl% one NS entit% re;uestin( chan(e flow E5a3#le 1 -! entity tri erin resource distribution without data (refer to fi ure 5.3). The !G!- may wish to receive uplin" data for a mobile at 'PJ$:P 8 and not 'PJ$:P3. The !G!- may not have downlin" data3 in which case the !G!- may send a downlin" -!=$-'T:+T+ (with 4=bit set) containin a 5!!GP :)=$-'T:+T+ with an ))6 P:$ of len th 1. !ubseDuent uplin" data transfer for the mobile will follow the dotted path from 'PJ$:P 2 to 'PJ$:P8 throu h the 'P sub=networ". 5!! -!=$-'T:+T+ !G!-

'PJ$:P2

'PJ$:P3

-!=$-'T:+T+(4=bit3 5!!GP has ))6 with len th K 1) 'PJ$:P0 'PJ$:P8

3i(ure $-34 EEa&ple 3 of NS entit% re;uestin( chan(e flow without data E5a3#le 6 -! entities without any resource distribution function (refer to fi ure 5.8). The 5!! and !G!- may not care which 'P endpoint data arrives at as lon as the reDuirements for the load sharin function are met. 'n this case the paths ta"en by the uplin" and downlin" data are independent.

ETSI

Release )*

1.

3GPP TS +,-*). /)*-*-* "0*))'*3#

5!! -!=$-'T:+T+

!G!-

'PJ$:P2

'PJ$:P3

-!=$-'T:+T+ 'PJ$:P0 'PJ$:P8

3i(ure $-+4 EEa&ple + of NS entit% not re;uestin( chan(e flow

ETSI

Release )*

12

3GPP TS +,-*). /)*-*-* "0*))'*3#

$%%e. ) (i%3or6ati7e)+ )#a%2e Eistor5

Meetin( / Docu&ent Date nu&5er Mar # 2011 8R Re! -

Su5ject/8o&&ent
)reatio% o3 Re!-10 7ersio% &ased o% 7ersio% -.0.0

New !ersion 10.0.0

ETSI