8/12/2019 48002-900

1/18

3GPP

3GPP TS 48.002 V9.0.0 (2009-12)Technical Specification

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

ase Station S!ste" # Mo$ile#ser%ices Switchin& 'entre(SS # MS') interface;

*nterface principles(Release +)

GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS

R

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

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

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

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

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

2/18

3GPP

$eywordsGSM, radio

3GPP

Postal address

3GPP support office address

650 Route des u!io"es - So#$ia %&ti#o"is

Va"'o&&e - R%*+Te". 33 4 92 94 42 00 a 33 4 93 65 4/ 16

%nternet

$tt#.3##.or

Copyright Notification

&o part may be reproduced e'cept as authoried by written permission.

The copyriht and the foreoin restriction e'tend to reproduction in all media.

*++,- 3GPP Oraniational Partners (/%0- T%!- 11!- 2T!%- TT- TT1).

ll rihts reserved.

MT!4 is a Trade Mar" of 2T!% reistered for the benefit of its members

3GPP4 is a Trade Mar" of 2T!% reistered for the benefit of its Members and of the 3GPP Oraniational Partners

5T24 is a Trade Mar" of 2T!% currently bein reistered for the benefit of its Members and of the 3GPPOraniational Partners

G!M6 and the G!M loo are reistered and owned by the G!M ssociation

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

3/18

*o&te&ts

1ontents....................................................................................................................................................3

7oreword...................................................................................................................................................8

9 !cope......................................................................................................................................................:

* /eferences..............................................................................................................................................;

3 =.9 Terrestrial channel manaement............................................................................................................................>=.9.9 Terrestrial channel allocation..............................................................................................................................>

=.9.* 0loc"in of terrestrial channels..........................................................................................................................,=.* /adio channel manaement...................................................................................................................................,

=.*.9 1hannel confiuration manaement...................................................................................................................,

=.*.* /adio T1? manaement.....................................................................................................................................,=.*.*.9 /adio channel allocation..................................................................................................................................,=.*.*.* T1? radio lin" supervision............................................................................................................................ ..,

=.*.*.3 7re@uency hoppin manaement.....................................................................................................................,=.*.*.= %dle channel observation..................................................................................................................................,

=.*.*.8 T1? power control........................................................................................................................................9+

=.*.*.: T1? channel release......................................................................................................................................9+=.*.3 011? 111? manaement...............................................................................................................................9+

=.*.3.9 !chedulin of 011? and 111? messaes...................................................................................................9+

=.*.=

8/12/2019 48002-900

4/18

: Multiple'in of common and dedicated control channels....................................................................9=

; 1lasses of sinallin messaes.............................................................................................................9=

> !upport of services and features other than speech..............................................................................9=>.9 .* !upplementary services........................................................................................................................................9=

, %nterface structures...............................................................................................................................9=

9+ Operation and maintenance................................................................................................................98

Annex A (informative):

Remote Moi!e S"it#$in% Unit (RMSU)&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&'.9 %ntroduction.........................................................................................................................................................9:.* 7unctions provided by the /M!.......................................................................................................................9:

.3 General re@uirements..........................................................................................................................................9:

Annex B:

(voi)&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&'*

Annex C (informative):C$an%e +i,tor-&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&'.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

5/18

oreord

This Technical !pecification has been produced by the 3 rdGeneration Partnership Project (3GPP).

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

Dersion '.y.

whereC

' the first diitC

9 presented to T!G for informationE

* presented to T!G for approvalE

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

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

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

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

6/18

1 S!o#e

The present document ives the principles on which the detailed interface specifications in the rest of the 3GPP T!=>.+'' series of Technical !pecifications are based.

The set of fi'ed e@uipment accessed from the M!1 throuh one particular instance of the interface will be later referredto as a 0ase !tation !ystem (0!!). 0!! ensures the coverae of n cells- where n can be 9 or more.

The function of a 0!! may be further subdivided into a control function- performed by one 0ase !tation 1ontroller(0!1) and a transceivin function- performed by FnF 0ase Transceiver !tation e@uipments (0T!)- one for each cell.

?owever- the study of such a split is outside the scope of the =>.+'' series of Technical !pecifications- where the 0!!

will be considered as a whole.

The 0!!BM!1 interface defined in the 3GPP T! => series of Technical !pecifications is desined to support a widerane of possible architectures on both sides. 1haracteristics li"e location of the transcodersArate adaptation to the M!!

or inside the 0!! (either physically interated into the transceivers or very near to the M!1) or the use of traffic orsinallin concentration at either side are left to the operators choice. nne' to the present document contains

uidance information concernin the use of remote mobile switchin units- which for the purposes of the present

document are considered as part of the M!1.

The 0!!BM!1 interface is commonly called HB%nterfaceI. %t is subdivided into the 1ontrol Plane (sinallin) and theser Plane (traffic). Throuhout this document the term HM!1I is used to reflect both planes of the Mobile 1ore

&etwor"- althouh in some architecture the Mobile 1ore &etwor" is split into M!1B!erver (M!1B!) and MediaGateway (MGJ).

8/12/2019 48002-900

7/18

2 Reere&!es

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

/eferences are either specific (identified by date of publication- edition number- version number- etc.) ornonBspecific.

7or a specific reference- subse@uent revisions do not apply.

7or a nonBspecific reference- the latest version applies. %n the case of a reference to a 3GPP document (includin

a G!M document)- a nonBspecific reference implicitly refers to the latest version of that document in the sameRelease as the present document.

L9 3GPP T! *9.,+8C FDocabulary for 3GPP !pecificationsF.

L* 3GPP T! *3.++,C F?andover proceduresF.

L3 3GPP T! *3.,9+C F1ircuit switched data bearer servicesF.

L= 3GPP T! =3.+*+C F!ecurity related networ" functionsF.

L8 3GPP T! ==.+9>C FMobile radio interface layer 3 specificationE /adio /esource 1ontrol ProtocolF.

L: 3GPP T! =>.++9C 0ase !tation !ystem B Mobile services !witchin 1entre (0!! B M!1)interfaceE General aspectsF.

L; Doid.

L> 3GPP T! =>.++:C F!inalin transport specification mechanism for the 0ase !tation !ubsystem NMobileBservices !witchin 1entre (0!! B M!1) interfaceF.

L, 3GPP T! =>.++>C FMobileBservices !witchin 1entre N 0ase !tation !ystem (M!1B0!!)

interfaceE 5ayer 3 specificationF.

L9+ Doid.

L99 Doid.

L9* Doid.

L93 Doid.

L9= Doid.

L98 Doid.

L9: Doid.

L9; Doid.

L9> 3GPP T! 8*.++9C F1ommon aspects of G!M &etwor" Manaement (&M)F.

L9, 3GPP T! *3.*3:C F %ntraBdomain connection of /adio ccess &etwor" (/&) nodes to multiple

1ore &etwor" (1&) nodes F.

3 ei&itio&s a&d a''reiatio&s

bbreviations used in the present document are listed in 3GPP T! *9.,+8.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

8/18

4 u&!tio&a" diisio& 'etee& ase Statio& S7ste(SS) a&d MS*

Ta$le , 4unctional split

*te"5Task SS MS'6MG7618R698R

Terrestria" *$a&&e" Ma&aee&t!$a&&e" a""o!atio& '"o!:i& i&di!atio&

Radio !$a&&e" a&aee&tRadio !$a&&e" !o&iuratio&a&aee&t re;ue&!7 $o##i& a&aee&t id"e !$a&&e" o'seratio& #oer !o&tro"

T*< a&aee&t!$a&&e" a""o!atio& (!$oi!e) "i&: su#erisio& !$a&&e" re"ease (=&o:ed '7 MS*)

**i #roided? MS* i&oredi&ter&a" ('etee& !e""s) >i #roided? MS* i&oredeter&a" re!o&itio& radio reaso& eter&a" re!o&itio& trai! reaso&

de!isio& ee!utio&

Mo'i"it7 Ma&aee&taut$e&ti!atio& "o!atio& u#dati& #ai&

R #ai& (s!$edu"i&) *a"" !o&tro"

@ser data e&!r7#tio& Ae7 a&d #eritteda"orit$s ro MS*

Si&a""i& e"ee&t e&!r7#tio& Ae7 a&d #eritteda"orit$s ro MS*

S (%S ode Se"e!tio& u&!tio&)

4.1 Terrestria" !$a&&e" a&aee&t

4.1.1 Terrestria" !$a&&e" a""o!atio&Terrestrial channel allocation will be handled in the followin manner.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

9/18

%n case of T.++>.

5ocal bloc"in of terrestrial channels on the side allocatin the circuits may be supported and will result in theconcerned channels not bein chosen- no information need flow across the interface in these cases.

0loc"in for %PBlin"s is not e'plicitly needed- because no fi'ed relation between both endpoints of an %P lin" e'ists.

4.2 Radio !$a&&e" a&aee&t

4.2.1 *$a&&e" !o&iuratio& a&aee&t

The channel confiuration manaement will be controlled between 0!! and maintenance centre- the M!1 holdin no

direct data concernin the allocation of radio timeslots etc.

4.2.2 Radio T*< a&aee&t

4.2.2.1 Radio !$a&&e" a""o!atio&

The 0!! shall choose the radio channel to be used on the appropriate cell- based on information received from the

M!1- which defines the radio channel type- speech codec type (if necessary)- channel codin and all other parametersrelevant to definin channel type. The chosen radio channel shall be connected to the terrestrial channel in order to

support the call. This connection mechanism is not further defined in these Technical !pecifications- e'cept theneotiation of the B%nterface Type (T.++>.

4.2.2.2 T*< radio "i&: su#erisio&

/adio lin" supervision of dedicated radio resources shall be the responsibility of the 0!!. %f communication with themobile is lost then the 0!! can re@uest that the call be cleared.

4.2.2.3 re;ue&!7 $o##i& a&aee&t

7re@uency hoppin manaement shall be performed by the 0!!. That is the 0!! shall store and transmit all hoppinparameters for the cell(s) that it controls- the hoppin shall be performed such that it is not visible on the 0!!AM!1

interface.

4.2.2.4 =d"e !$a&&e" o'seratio&

The @uality of idle radio channels shall be measured by the 0!! and a condensed form of the information passed bac"

to the M!1.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

10/18

4.2.2.5 T*< #oer !o&tro"

ll power control functions shall be performed between M! and 0!!. &o real time power control commands shall besent across the 0!!AM!1 interface.

4.2.2.6 T*< !$a&&e" re"ease

The release of a dedicated resource is primarily controlled by the M!1. ?owever for radio propaation reasons the 0!!can re@uest of the M!1 that a call be released. The necessary protocols are defined in 3GPP T! =>.++>.

4.2.3 **< ***< a&aee&t

ll 011? data shall be either stored at or derived locally by the 0!!.

111? random accesses shall be controlled autonomously by the 0!!- pain messaes shall be received from the

M!1 via the 0!!AM!1 interface.

4.2.3.1 S!$edu"i& o **< a&d ***< essaes

The schedulin for all 011? and 111? messaes shall be performed by the 0!!.

4.2.4 **< Ma&aee&t

4.2.4.1 **< "i&: su#erisio&

/adio lin" supervision of dedicated radio resources shall be the responsibility of the 0!!. %f communication with themobile is lost then the 0!! can re@uest that the call be cleared.

4.2.4.2 **< !$a&&e" re"ease

The release of a dedicated resource is primarily controlled by the M!1. ?owever for radio propaation reasons the 0!!can re@uest of the M!1 that a call be released. The necessary protocols are defined in 3GPP T! =>.++>.

4.2.4.3 **< #oer !o&tro"

ll power control functions shall be performed between M! and 0!!. &o real time power control commands shall be

sent across the 0!!AM!1 interface.

4.2.4.4 Radio *$a&&e" %""o!atio&

The 0!! shall choose the .

4.4 *$a&&e" !odi& de!odi&

The encodin decodin and interleavin shall be performed by the 0!!. The type of channel codin and interleavin is

derived from the information in the assinment messae from the M!1.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

11/18

4.5 Tra&s!odi&rate ada#tatio&

.++>).

4.8.2 =&ter&a" $a&doer 'etee& !e""s

%ntraB0!! ?andover between cells on the same 0!! can be supported within a 0!!. Multi cell 0!!s would normally be

e'pected to support internal inter cell handover- however it is optional that they do so.

%ntraB0!! handover may be performed autonomously by the 0!! as lon as neither the B%nterface Type is chaned

(e.. from T.++>).

%f the %ntraB0!! handover needs a modification of the B%nterface Type (e.. a chane from T

8/12/2019 48002-900

12/18

4.8.3 +ter&a" $a&doer

This type of handover includes interB0!! handover as discussed in 3GPP T! =>.++> and interBM!1 handover asdiscussed in 3GPP T! *3.++,. %n all e'ternal handover cases the M!1 is involved.

4.8.3.1 Re!o&itio& t$at a $a&doer is re;uired or a radio reaso&

The 0!! shall be able to enerate an indication that a handover is re@uired to the M!1 usin the protocols defined in

3GPP T! =>.++>.

&o additional uidance is iven in the 3GPP T! =>.+'' series concernin the alorithm within the 0!! that enerateseither an internal handover- or an indication to the M!1 that an e'ternal handover is re@uired.

4.8.3.2 Re!o&itio& t$at a $a&doer is re;uired or a trai! reaso&

The 0!! shall be able to enerate an indication to the M!1 that a handover is re@uired for traffic reason (e.. directedretry) usin the protocols defined in 3GPP T! =>.++>.

Jithin a multi 0!! area only the M!1 has a perspective of the overall traffic loadin. The M!1 may therefore

oriinate inter 0!! traffic handovers due to traffic reasons.

4.8.3.3 e!isio& o Taret *e""

The choice of the taret cell in an e'ternal traffic handover shall be made by the M!1- based on information receivedfrom the 0!!.

4.8.3.4 +e!utio&

?avin received an indication from a 0!! that an e'ternal handover is re@uired- the decision of when and whether ane'ternal handover should ta"e place shall be made by the M!1.

4.9 Mo'i"it7 a&aee&t

ll transactions concernin mobility manaement (as specified in 3GPP T! ==.+9>) shall ta"e place transparently

between the M! and M!1AD5/A?5/- usin the protocols described in Technical !pecifications 3GPP T! =>.++> and3GPP T! =>.++:. The only e'ception to this rule is that of pain which is scheduled by the 0!! on the appropriate

cell.

4.10 *a"" !o&tro"

1all control will be the responsibility of the M!1A?5/AD5/.

4.11 Se!urit7 eatures

%nformation on security aspects are found in 3GPP T! =3.+*+. The 0!!AM!1 interface supports all of the re@uiredinterchane of encryption "eys.

4.11.1 @ser data !o&ide&tia"it7

2ncryption and decryption of user data (e.. speech) ta"es place within the mobile station and within the 0!!. %n orderto decryptAencrypt user data the encryption device used for the call must be loaded with the relevant "ey and alorithm.

The "ey and the permitted alorithms are supplied by the M!1.

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

13/18

4.11.2 @ser ide&tit7 !o&ide&tia"it7

This feature is supported by usin a TM!% rather than an %M!%- over the radio path. The translation between TM!% and%M!% is performed at the M!1 and within the mobile. 0oth TM!% and %M!% are carried transparently by the 0!!BM!1

interface as far as possible.

4.11.3 Si&a""i& i&oratio& !o&ide&tia"it7

s for user data.

4.11.4 %ut$e&ti!atio& o users

uthentication is carried out at the mobile and at the M!1AD5/A?5/. The M!1 to 0!! interface is re@uired totransport the necessary challene and response messaes.

4.12 G"o'a" Tet Te"e#$o&7

%nterwor"in between cellular te't telephone modem (1TM) and te't telephony standards (e.. D.9>) used in e'ternalnetwor"s can be performed by the 0!!. %t can also be performed by separate entities in the core networ".

4.13 %S ode Se"e!tio& u&!tio&

The optional &! &ode !election 7unction (&&!7) enables the 0!1 to initially assin a M!1 to serve a M! andsubse@uently setup a sinallin connection to the assined M!1.

The method by which the 0!1 initially assins a M!1 is implementation dependent.

The &! &ode !election 7unction is needed when the feature %ntraBdomain connection of /adio ccess &etwor"

(/&) nodes to multiple 1ore &etwor" (1&) nodes is used.

The &&!7 is described in detail in L9,.

5 Tra&s!oderrate ada#ter i&teratio&

5.1 TM 'ased %-=&tera!e

The speech transcoder and the data rate adaptor will be functionally interated into the 0!!. %t is not considered to be a

stand alone piece of e@uipment. The control of the transcoder or rate adaptor will therefore ta"e place directly via the0!!- an e'plicit control interface between 0!! and transcoder and rate adaptor will not be defined.

8/12/2019 48002-900

14/18

6 Mu"ti#"ei& o !oo& a&d dedi!ated !o&tro"!$a&&e"s

1ommon and dedicated control channels will be used for the same call on the radio path. These control channels will be

multiple'ed onto one or more common sinallin channel(s) between the 0!! and M!1. This multiple'in functionwill reside at the 0!!.

%t should be noted therefore that the data lin"s across the air interface are terminated at the 0!!.

ll schedulin of messaes via the air interface is controlled by the base station- flow control is therefore re@uired from0!! to M!1 to prevent overload of the transmission buffers- this is further detailed in Technical !pecifications 3GPP

T! =>.++> and 3GPP T! =>.++:.

/ *"asses o si&a""i& essaes

The sinals between 0!! and M!1 are classified under three headinsC

i) 4T%P 8essa2es ------6SS%P 8essa2esii) 6SS 8a&a2e8e&t---+iii) 6SS BCM

Jhere .++>.

5ayer 3 call control messaes will as far as possible pass transparently throuh the 0!!. The discrimination between0!!MP and .++:.

8 Su##ort o seri!es a&d eatures ot$er t$a& s#ee!$

8.1 ata seri!es

%n order to ensure that the re@uirements of 3GPP T! *3.,9+ are met- the support of data services will entail thefollowin ; actions bein ta"enC

i) the speech coder bein deactivated in the mobileE

ii) a rate adaptation function bein activated in the mobileEiii) an appropriate channel codin bein activated in the mobile radio subsystemE

iv) an appropriate channel coder bein activated in the 0!!Ev) a rate adaptation function bein activated in the 0!!E

vi) any echo control in the M!1 bein byBpassed or disabledEvii) an appropriate networ" interwor"in function bein invo"ed.

The M!1 to 0!! interface will support all necessary sinallin for this to be achieved.

8.2 Su##"ee&tar7 seri!es

ll sinallin concerned with supplementary services is passed transparently throuh the 0!! via the

8/12/2019 48002-900

15/18

10 B#eratio& a&d ai&te&a&!e

Operation and maintenance information is re@uired to flow between the 0!! and O M functions. The 0!! to M!1interface provides for this type of information see 3GPP T! 8*.++9.

6SS-S=4+ MS*-S=4+%-=T+R(%*+

To ot$er #ro!esses1it$i& t$e 6SS

6SS%P

4T%P6SSM%P

4istri'utio&(u&!tio&

6SSBM%P

S * * P

M T P

P

8/12/2019 48002-900

16/18

%&&e % (i&oratie)Reote Mo'i"e Sit!$i& @&it (RMS@)

%.1 =&trodu!tio&

0etween the M!1 and some of the 0!! sites served by this M!1 - it may be advantaeous to include a line

concentrator- an /M!. The main purpose of introducin this unit is to reduce the number of terrestrial circuits needed

between 0!! site and M!1s (sinallin and traffic circuits). The benefits of introducin an /M! will depend onC

B relative costs of the transmission plant for the particular administrationsE

B the costs involved in operatin the /M!E

B the comple'ity of the /M!- i.e. if it allows interwor"in with the %!

8/12/2019 48002-900

17/18

%&&e (oid)

3GPP

Release + 3GPP TS ,-.//0 1+././ (0//+#20)

8/12/2019 48002-900

18/18

%&&e * (i&oratie)*$a&e