GSM協(xié)議棧設計結構英文.doc

GSM 協(xié)議棧設計結構1 Architecture of GSM2 CC2.1 SummaryIn GSM protocol, both SS protocol and CC protocol are sub-protocol of CM protocol. The CC entity uses box to communicate with API, MM and RR. Each CC entity shall communicate with the correspondent peer entity using its own MM connection.2.2 Object Model DiagramIn CC module, different CC context needs interwork with others, so all CC context are organized in a queue. Every CC context will manage a call.2.3 Objects DescriptionThe functions of CC entity as following:Call establishment procedures;Call clearing procedures;Call information phase procedures;Miscellaneous procedures.DTMF manage;User notification;In call Modify manage;CRSS function manage.2.4 CC State ChartFSM stateCC stateDescribeU0CC_U0No call existsU01CC_U01MM Connection pending, This state exists for a mobile originating call, when the mobile station requests the establishment of a MM connection.U1CC_U1CC has send SETUP CC_U3CC has received CALL PROCEEDINGCC_U4CC has received ALERTU6CC_U6MS has received SETUPU8CC_U8MS has sent CONNECT.U9CC_U9MS has sent CALL CONFIRMU9CC_U7MS has sent ALERTINGU10CC_U26MO modifying.CC_U27MT modifying.CC_U10The call active, refer U26, U27, REESET.REESETMM connection is disconnected and just reestablishing, the CC U10.U11CC_U11This state exists when the mobile station has requested the network to clear the end-to-end connection (if any) and is waiting for a response.U12CC_U12This state exists when the mobile station has received an invitation to disconnect because the network has disconnected the end-to-end connection (if any).U19CC_U19This state exists when the MS has requested the network to release and is waiting for a response.GENEDifferent CC state will do same respond to message will deal in virtual FSM state GENE.Call states at the mobile station side of the interfaceThe states which may exist on the mobile station side of the radio interface are defined in this clause.NOTE:States U0.1, U0.2, U0.3, U0.4, U0.5, U0.6, U26, and U27 are GSM specific. All other states are ITU-T defined.U0000000NullNo call existsU0.1000010MM Connection pendingThis state exists for a mobile originating call, when the mobile station requests the establishment of a MM connectionU1000001Call initiatedThis state exists for a mobile originating call, when the MS requests call establishment from the networkU3000011Mobile originating call proceedingThis state exists for a mobile originating call when the mobile station has received acknowledgement that the network has received all call information necessary to effect call establishment.U4000100Call deliveredThis state exists for a mobile originating call, when the calling mobile station has received an indication that remote user alerting has been initiatedU6000110Call presentthis state exists for a mobile terminating call when the mobile station has received a call establishment request but has not yet responded.U7000111Call receivedThis state exists for a mobile terminating call when the mobile station has indicated alerting but has not yet answeredU8001000Connect RequestThis state exists for a mobile terminating call, when the mobile station has answered the call and is waiting to be awarded the callU9001001Mobile terminating call confirmedThis state exists for a mobile terminating call when the mobile station has sent acknowledgement that the mobile station has received all call information necessary to effect call establishmentU10001010ActiveThis state exists for a mobile terminating call when the MS has answered the call. This state exists for a mobile originating call when the MS has received an indication that the remote user has answered the callU11001011Disconnect requestThis state exists when the mobile station has requested the network to clear the end-to-end connection (if any) and is waiting for a response.U12001100Disconnect indicationThis state exists when the mobile station has received an invitation to disconnect because the network has disconnected the end-to-end connection (if any).U19010011Release requestThis state exists when the MS has requested the network to release and is waiting for a response.U26011010Mobile originating modifyThis state exists when the mobile station has sent a request to the network for a new mode but has not yet received an answer.U27011011Mobile terminating modifyThis state exists when the mobile station has received a request from the network for a new mode and has not yet sent a response to this request.3 SS3.1 SummaryIn GSM protocol, SS protocol is a sub-protocol of CM protocol. The SS entity uses box to communicate with API and MM. Each SS entity shall communicate with the correspondent peer entity using its own MM connection.3.2 Object Model DiagramAPISS11nnMMIn MS, different SS entity needs know other SS entities, so all SS entities are organized in a queue, Every SS entity describes in protocol is mapped to a SS context.3.3 Objects DescriptionThe functions of SS entity as following:SS Interrogate for Line ID,CF,CB,CW;CF register, Erasure;CF,CB Activate, Deactivate;CB Password Registe;USSD manage.4 SMS4.1 SummaryNote:In GSM mode, SM_CL use MM entity to comminute, In GPRS mode, use MMP.SMS_CB will performed by CB module.4.2 Object Model Diagram4.3 Objects DescriptionSMS module will perform the function of SM RL and SM RL, it combine the SMS entity and GSMS entity.A SMR entity communicates with A SMR entity in the SMC, give the SM_TL capability to exchange SM_TL message. SMC entity is in CM sublayer, carrying SMR data.SM_TL：SMS sending and MEMORY AVAILABLE notify, SMS receiving and STATUS REPORT receiving, alphabet supporting, saving message to SIM and reading message from SIM, contact SMS.5 MMAbbreviationArfcn The absolute RF channel numberCMConnection ManagementCKSNCiphering Key Sequence NumberFSMFinite State MachineGPRSGeneral Packet Radio ServiceIMSIInternational Mobile Subscriber IdentityKcCiphering keyLACLocation Area CodeLAILocation Area Identity LANLocal Area NetworkLLCLow Layer CompatibilityMMMobile ManagementMMCCircuit Switch MMMMPPacket Switch MMOSIOpen System InterconnectionRRRadio Resource ManagementSIMSubscriber Identity ModuleTMSITemporary Mobile Subscriber Identity5.1 SummaryMobile management sublayer locate in Level 3 of protocol stack, and middle of Level 3。The main function of the Mobility Management sublayer is to support the mobility of user terminals, such as informing the network of its present location and providing user identity confidentiality.A further function of the MM sublayer is to provide connection management services to the different entities of the upper Connection Management (CM) sublayer.All the MM procedures described in this clause can only be performed if a RR connection has been established between the MS and the network. Else, the MM sublayer has to initiate the establishment of a RR connection.In Figure 2.1.1 An overview of the MM sublayer protocol architecture in GSM/GPRS protocol is given. Figure 2.1.15.2 Object Model DiagramMM sublayer includes two objects MMC and MMP. MM sublayer is a entity. The contacts between MM entity and other entity are followed in Figure 2.2.1 Figure 2.2.15.3 Objects DescriptionThe object MMC fulfills the following procedure:1)MM common procedures:Initiated by the network:-TMSI reallocation procedure;-authentication procedure;-identification procedure;-MM information procedure;-abort procedure.Initiated by the mobile station:-IMSI detach procedure.ii)MM specific procedures:-normal location updating procedure;-periodic updating procedure;-IMSI attach procedure.iii)MM connection management procedures:These procedures are used to establish, maintain and release a MM connection between the mobile station and the network, over which an entity of the upper CM layer can exchange information with its peer. A MM connection establishment can only be performed if no MM specific procedure is running. More than one MM connection may be active at the same time.5.4 state chartMMC Finite State Machine is made of 7 state。MMC_GENE State deals with some message that need to be treated with whereas dont treated with in 6 normal state.6 normal state is :MMC_NULL initiative state. power on，MM stand in the state。MMC_IDLE idle state，MM start all procedure in the state。MMC_WRRC state that wait the RR connection response. MMC_WNKR state that wait the network response message.MMC_CNTD MM connected。No less than one connection have been established.MMC_WNKC state that wait the network command.6 RR6.1 RRISXRSystem eXecutive Real timeFSMFinite State MachineRRD Radio Resource Dedicated modeRRI Radio Resource Idle modeRRI_P Radio Resource Idle mode PLMN SelectionRRI_C Radio Resource Idle mode Cell SelectionL1Layer 1 of GSM/GPRS systemMMMobile ManagementLAPLink Access Protocol6.1.1 SummaryRRI module is part of Radio Resource Manage, main function is responsible for PLMN selection, Cell selection, Cell reselection, all System Message received and Measurement Report sent. It s positioning in GSM protocol stack as below:Figure 1 RRIs location in stack22 / 226.1.2 Object Model DiagramThe RRI have two objects, which implement different functions with independent finite state machine. The relationship between two objects (RRI_C and RRI_P) and the other extern objects displays in the figure below.Figure 1 RRIs OMD6.1.3 Objects DescriptionThe object RRI_P completes the following functions: Automatic and manual PLMN selection. Select designated PLMN. PLMN reselection procedure. PLMN selection mode setting. Report available PLMN list.The object RRI_C completes the following functions: Normal cell selection. Normal reselection. Neighbour cell synchronization procedure. Plmn scan procedure. Cell changed in connected mode. Acquisition of system information on BCCH and PBCCH. Received system information on DCCH. Measurements control and reporting. Forwarding of paging information to MM layer. Sending quality report.6.1.4 State chartrri_PNULL: Init State Wiat for a Start Command.rri_PWCS: Wait for a Cell from CSel. Psel has sent a Search to Csel and is waiting for it.rri_PCAMP: PSel is camped on a the selected Plmn.rri_PLTD: Limited Service state.rri_PNSVC: No service is detected sleep with a awake timer.rri_PCONN: In Connected Mode some restriction for MMI fucntion apply.rri_CNULL: Initial State. Can only receive a request fron PSel to start search a Plmn.rri_CRSSI: RSSI measurements are requested and Result is Waited ( for initial Cell selection).rri_CSYNCHR: Wait for a possible Synchro on a Cell. L1 will report the first possible synchro when found.rri_CSVERIF: Wait for receiveing All Sysinfo for Selecting a Cell.rri_CRVERIF: Wait for receiveing All Sysinfo for reselectiong a Cell.rri_CCAMPED: Camped on a Main Cell (can be on Any cell ie Emergency only).rri_CRESEL: Current serving Cell is not suitable any more. Wait for other cell information to be able to switch Cell.rri_CCONN: MS has engaged a circuit swicth connexion. Reselection is prohibited here.rri_CENDCO: MS has Terminated the circuit swicth connexion. Trys to select the Cell on witch we last werein Connected.6.2 RRD6.2.1 SummaryIn the GSM/GPRS stack, RRD is under MM , and up LAP and L1. RRD provides MM with services of RR connection establishment , management and data transmitting. RRD is short for RR in dedicated mode .RRD communicates with MM , LAP and L1 with mailboxes Fig below describes RRD s position in stack RRD in stack6.2.2 Object Model DiagramIn practice , RRD module is mapped as one RRD instance. See RRD OMD Fig 2 below.OMD of RRD6.2.3 Object DescriptionRRD procedures provide the following services:：1. establishment/release of multiframe mode on data link layer connections;2. transfer of messages on any data link layer connection;3. indication of temporary unavailability of transmission (suspension, resuming);4. indication of loss of RR connection5. handover to maintain the RR connection;6. setting/change of the transmission mode on the physical channels, including change of type of channel, change of the coding/decoding/transcoding mode and setting of ciphering;7. release of an RR connection.6.2.4 State chartWe have a state machine for RRD GSM module，and this RRD state machine has 6 state, as follows：(1) RRD_VOID： RRDs state when no connection is started or established.In this state RRD can only process a request to establish a connection(2) RRD_ACCI： RRD is accessing the PCCCH channel and waits for a channel allocation by the network(3) RRD_WCNI： RRD is waiting for the establishment of the lower layers on the initial connection(4) RRD_COND：The connection is established(5) RRD_WCNN：RRD is waiting for the establishment of the lower layers on the new connection(6) RRD_WRLS：RRD is waiting for the release of the lower layers7 LAPABM Asynchronous Balanced ModeAGCH Access Grant ChannelBCCH Broadcast Control ChannelDCCH Dedicated Control ChannelDLCI Data Link Connection IdentifierDLL Data Link LayerFACCH Fast Associated DCCHFSM Finite State MachineLAPDm Link Access Procedures on the Dm ChannelPCH Paging ChannelRR Radio Resource REQ RequestRES ResponseSACCH Slow Associated DCCHSAPI Service Access Point IdentifierSDCCH Stand-alone DCCHUA Unnumbered AcknowledgementUI Unnumbered Information7.1 SummaryIn GSM/GPRS stack, LAP is under RR, up L1, providing reliable data transmitting for layer 3 on dedicated channels.LAP has two operation modes: unacknowledged operation using UI frame, and acknowledged operation using multi frame.LAP communicates with RR by mailbox; LAP send messages to L1 by shared queues or pointers. L1 send messages to LAP by mailbox.LAPs position in the stack is as follows:Figure 1 LAP in stack7.2 Object Model DiagramLAP module is mapped into one object when realization, and it has two instances, SAPI0 and SAPI3. LAPs object model diagram is as follows.Figure 2 LAPs OMD7.3 Objects DescriptionLAPDm includes functions for:a)the provision of one or more data link connections on a Dm channel. Discrimination between the data link connections is by means of a data link connection identifier (DLCI);b)allowing recognition of frame types;c)allowing layer 3 message units to be passed transparently between layer 3 entities;d)sequence control, to maintain the sequential order of frames across a data link connections;e)detection of format and operational errors on a data link;.f)flow control; andg)contention resolution when establishing a data link after an access request has been made on the RACH.1. 在移動臺和基站之間為L3傳遞信息。2. 在確認操作模式下，為確認信息傳輸建立邏輯數據鏈路連接，分為沖突解決建鏈和正常建鏈。3. 在非確認操作模式下，提供無編號信息幀的傳遞功能。4. 提供Dm信道上一個或者多個邏輯鏈路連接，這些連接由DLCI來區(qū)分（DLCI包括SAPI和信道類型）5. 為收到的L3的消息提供分段功能，為收到的L1的消息提供重組功能。6. 為確認的信息幀I幀的傳遞提供序列控制。接收信息出現(xiàn)序列錯誤時，通知對等實體重發(fā)。收到對等實體的拒絕幀后提供重發(fā)機制。7. 在信道改變之前，可將業(yè)務掛起；切換成功后，在新信道上重建數據鏈路，并恢復業(yè)務；在信道切換失敗后，在老信道上重建數據鏈路，并恢復業(yè)務。8. 檢測L2邏輯鏈路上的收到的幀格式。7.4 State chartLAP module has a state machine, it has two instances, sapi0 and sapi3. LAP state machine has 8 states as follows：1. LAP_IDLE：LAPDm is in idle state, no connection established.2. LAP_ESTAB_SABM_SENT：A establish SABM has been sent, the LAPDm is waiting for the answer.3. LAP_MFE：The LAPDm is in multi-frame operation.4. LAP_SUSPENDED：The LAPDm is suspended. For sapi0 instance only.5. LAP_RESUME_SABM_SENT：A resume SABM has been sent, the LAPDm is waiting for the answer. For sapi0 instance only.6. LAP_RECONNECT_SABM_SENT：A reconnect SABM has been sent, the LAPDm is waiting for the answer. For sapi0 instance only.7. LAP_TIMER_RECOVERY：The LAPDm is in timer recovery, waiting for ACK for I frame.8. LAP_RELEASE_DISC_SENT：A release DISC has been sent, the LAPDm is waiting for the answer. For sapi0 instance only.9. LAP_GENE: LAPDm Generic state which can handle received message LAP_UNIT_DATA_REQ, LAP_RX_UI_FRAME, LAP_LOCAL_RELEASE_REQ, L1_TX_IND.7.4.1 State chart for lap sapi07.4.2 State chart for lap sapi38 L1CAGCH Access Grant ChannelBCCH Broadcast Control ChannelBTS Base Transceiver StationFACCH Fast Associated DCCHLAP Link Access Procedures NCH Notification ChannelPAGCH Packet Access Grant ChannelPCH Paging ChannelPDTCH Packet Data Traffic ChannelsPNCH Packet Notification ChannelPPCH Packet Paging ChannelPRACH Packet Random Access ChannelRACH Random Access ChannelRR Radio Resource SACCH Slow Associated DCCHSAPI Service Access Point IdentifierSDCCH Stand-alone DCCHTA Timing AdvanceTCH/F full rate traffic channelTCH/AFS adaptive full rate traffic channel for speechTCH/EFS enhanced full rate traffic channel for speechTCH/FS full rate traffic channel for speechTCH/H half rate traffic channelTCH/AHS adaptive half rate traffic channel for speechTCH/HS half rate traffic channel for speechTCH/F9.6 full rate traffic channel for 9.6kbit/s user dataTCH/F4.8 full rate traffic channel for 4.8kbit/s user dataTCH/H4.8 half rate traffic channel for 4.8kbit/s user data