Beruflich Dokumente
Kultur Dokumente
GENERAL INFORMATION
28 February, 2003
Page 1 /51
Interfaces to MSC/VLR
GMSC EIR F-I/f C-I/f MAP MSC/VLR VLR MSC E-I/f MAP MAP D-I/f MAP MSC/VLR MSC G-I/f VLR MAP VLR MSC/VLR MSC
HLR
Iu-I/f
Gs-I/f RNS RNC Iur-I/f RNC RANAP SGSN BSSAP+
Node B
Node B
BTS
28 February, 2003
Page 2 /51
28 February, 2003
Page 3 /51
28 February, 2003
Page 4 /51
MSC Functions
Terrestrial channel allocation Blocking of terrestrial channels TCH channel release DCCH channel release Channel coding decoding Interworking function (data calls) Traffic measurements Handover Mobility management Call control Encryption
28 February, 2003
Page 5 /51
DTAP Direct Transfer Application Part DTAP BSSMAP + BSSMAP BSS Management Application Part = Distribution Function BSSAP BSS Application Part
SCCP
Network
MS
MSC/VLR
DTAP/NAS
SMS Message
BSS/RNS
Initial MS/UE message BSSMAP RANAP
28 February, 2003
Page 7 /51
28 February, 2003
Page 8 /51
MTP
E1 links: CCITT Recommendations Q.701, Q.702, Q.703, Q.704, and Q.707 T1 links: ANSI Specifications T1.111 with stated exceptions
28 February, 2003
Page 9 /51
SCCP
E1 links: CCITT Recommendations Q.711, Q.712, Q.713, and Q.714 T1 links: ANSI Specifications T1.112.1-4 with stated exceptions Not used SCCP functions: error detection, receipt confirmation, flow control
28 February, 2003
Page 10 /51
28 February, 2003
Page 11 /51
ADDRESSING
SSN + SPC or SSN only No global title is used
28 February, 2003
Page 12 /51
28 February, 2003
Page 13 /51
GENERAL
Specifies Layer 3 procedures used on BSS-MSC interface for control of GSM services Call control and mobility management messages and procedures (DTAP) are described in GSM TS 04.08/3GPP TS 24.008 BSSMAP
28 February, 2003
Page 14 /51
MAIN PARTS
BSSMAP procedures Message formats and coding Signalling element coding Signalling diagrams
28 February, 2003
Page 15 /51
BSSMAP PROCEDURES
General information Successful/unsuccessful operation Abnormal conditions
28 February, 2003
Page 16 /51
28 February, 2003
Page 17 /51
28 February, 2003
Page 18 /51
SIGNALLING DIAGRAMS
Sequence diagrams for the BSSMAP procedures Related to an unique procedure
28 February, 2003
Page 19 /51
MSC/VLR
Cipher Mode Command Cipher Mode Complete Cipher Mode Reject BSC MSC/VLR
Classmark Request
Classmark Update Clear Command Clear Complete
Handover Performed
Handover Required Handover Required Reject Handover Request Handover Request Acknowledge BSC Handover Command Handover Detect Handover Complete Handover Failure
System Management Transfer Project 28 February, 2003
MSC/VLR
Page 22 /51
Perform Location Request Perform Location Response MSC/VLR BSC MSC Invoke Trace Trace Invocation SAPI n Reject
System Management Transfer Project 28 February, 2003
Page 23 /51
CM Service Accept
CM Service Reject CM Service Abort BSC MS Identity Request Identity Response Location Updating Accept Location Updating Reject IMSI Detach Indication TMSI Reallocation Command TMSI Reallocation Complete
MSC/VLR
28 February, 2003
Page 24 /51
/// BSSAP
28 February, 2003
Page 25 /51
28 February, 2003
Page 26 /51
A/Iu-Interface, Section R: UMTS to GSM Inter-System Handover Procedures A/Iu-Interface, Section S: GSM to UMTS Inter-System Handover Procedures
28 February, 2003
Page 28 /51
28 February, 2003
Page 30 /51
28 February, 2003
Page 31 /51
ERROR HANDLING
In case of inconsistent message length between delivered message length according to SCCP and BSSAP header message length, the BSSAP header message length has higher priority Messages with faulty BSSAP header are ignored. Messages are ignored if they are not consistent with the Signalling Type (CL, CO), with the direction, or with the recipients state Not recognized or not implemented messages are ignored. The information elements are classified into conditional, essential, non-essential, and transparent types:
28 February, 2003
Page 32 /51
Messages containing an unrecognisable or unexpected IE before the last essential IEs are rejected with the cause 'Invalid message' if a reject message exists. If no reject message exists the message is ignored Messages containing an unrecognisable IE or unexpected IE, after the last essential IEs have been received, are accepted Messages with a missing essential information element are rejected with the cause 'Invalid message' if a reject message exists. If no reject message exists the message is ignored Messages with a missing non-essential IE are accepted
28 February, 2003
Page 33 /51
If the MSC/VLR receives a message and diagnoses a missing conditional IE or an unexpected conditional IE or when it receives a message containing at least one syntactically incorrect conditional and non-transparent IE which is required to be present, then the message will be rejected with the cause 'Invalid Message' if a reject message exists. If no reject message exists the message is ignored Messages that have an essential and non-transparent IE with field having an incorrect value are rejected if applied with the cause 'Invalid message'. If no reject message exists, the message is ignored Messages that have a non-essential IE with fields having incorrect value are accepted. IE is ignored Transparent IEs are not checked
28 February, 2003
Page 34 /51
28 February, 2003
Page 35 /51
The administration of BSC data includes the following commands Definition of BSC Change of BSC capabilities Connection of alternative route to a BSC Disconnection of alternative route from a BSC Removal of BSC Printing of BSC data
28 February, 2003
Page 36 /51
28 February, 2003
Page 37 /51
FUNCTION DESCRIPTIONS
A-Interface Line Terminal Functions
The A-interface line terminal functions allow the seizure and release of an A-interface line (device) towards a BSS. The function also takes care of the administration of A-interface lines The A-interface line terminal functions handle BSSAP messages, concerning A-interface lines (block, unblock, circuit group block, circuit group unblock, reset circuit, unequipped circuit) The type of signaling used for the A-interface is ITU-T or ANSI signaling for the SCCP and Message Transfer Part (MTP)layers The A-interface line terminal functions take care of the handling of transmission concerning A-interface lines (A-law or U-law idle pattern sending, 24-channel(T1) or 32-channel(E1) Pulse Code Modulation (PCM) Interface or SDH/STM-1 interface)
System Management Transfer Project 28 February, 2003 Page 38 /51
Administration of BSCs
Administration of BSCs is a part of the administration of Base Station subsystem data in MSC/VLR Server
Administration of Cells
The administration of the cells is performed by means of seven commands, if the Location Area (LA) administration is supported, and four commands, if the LA administration is not supported. The LA administration involves the definition of a LA before the definition of the cells to be connected to it, and removal of a LA after all cells are removed from this LA
MM Connection Management
The MM connection management function establishes, maintains and releases internal links between the upper layer (CM) and the lower layer (RR), after a first transaction has been established. It distributes messages and signals coming from the link in both directions, to the proper user function
MM Traffic
Takes part for instance packing and unpacking of MM messages
BLOCKS
DIPST (Digital Path Supervision and Test)
The Function block DIPST contains functions for Digital Path (DIP) administration and maintenance, as well as hardware and clock reference administration
28 February, 2003
Page 43 /51
28 February, 2003
Page 44 /51
MRRM complex (Mobile Telephony Radio Resources Management, /MRRM, MRRMASG, MRRMHO/)
MRRM supervises the establishment and the release of the signaling connections between the MSC/VLR server and the BSC, and handles the messages At the reception of the messages, MRRM checks and distributes the different messages to the appropriate user function. The transparent messages (DTAP) are forwarded to the block MMM. The BSSMAP messages, received from MSCCO in connectionoriented mode or from MSCCL in connectionless mode are distributed to the appropriate function on RR level which will initiate the unpacking of the message and take the appropriate action In the connection oriented mode, MRRM receives the sending signals from the upper layer for DTAP messages or from MRRMH for BSSMAP messages and forwards them to MSCCO.
28 February, 2003
Page 45 /51
-In the connectionless mode at message sending stage, MRRM does not act -The block is also involved in several BSSMAP procedures during the assignment of a terrestrial line, the BSC recording initiation process, the ciphering process, the handover and the global reset.
28 February, 2003
Page 46 /51
MRRRSMH (Mobile Telephony Radio Resources Regional Satellite Application Message Handler)
The function block MRRRSMH is responsible for the analysis, packing and unpacking of Regional Satellite application specific Ies included in RR layer messages
28 February, 2003
Page 47 /51
28 February, 2003
Page 48 /51
Remote A-interface
Introduced in MSC R10
28 February, 2003
Page 49 /51
Site
TSC/ GMSC Server GCP
TDM: BSS
BTS BSC
MGW SGW
MGW SGW
28 February, 2003
Page 50 /51
28 February, 2003
Page 51 /51