Академический Документы
Профессиональный Документы
Культура Документы
Tusharadri Sarkar
Agenda
Iub Interface and NBAP Functions of NBAP NBAP Procedures NBAP Common Procedures NBAP Dedicated Procedures Questions and Answers
Tusharadri Sarkar
Iub interface connects NodeB and RNC of UTRAN The NBAP protocol stack used for NBAP signaling is shown above
Tusharadri Sarkar
Tusharadri Sarkar
Functions of NBAP
Functions of NBAP
Cell Configuration Management Common Transport Channel Management System Information Management Resource Event Management Configuration Alignment Measurement on Common Resources Radio Link Management Radio Link Supervision Compressed Mode Control Measurement on Dedicated Resources DL Power Drifting Correction Reporting of General Error Situation
March 13, 2013 Tusharadri Sarkar 7
Functions of NBAP
Please refer to Section 7, Table 1 of 3GPP TS 25.433 V11.3.0 (2012-12) for the exhaustive mapping between NBAP Functions and NBAP Elementary procedures.
Tusharadri Sarkar
NBAP Procedures
NBAP Procedures
Some Useful Definitions
CRNC Communication Context Contains necessary information for CRNC for communication with a specific UE CRNC Communication Context ID Node B Communication Context Contains necessary information for the Node B for communication with a specific UE Radio Link Setup and Radio Link Deletion Procedures Node B Communication Context ID Unless explicitly indicated in the procedure description, at any instance in time one protocol peer shall have a maximum of one ongoing dedicated NBAP procedure related to a certain Node B Communication Context
Tusharadri Sarkar
10
NBAP Procedures
Some Useful Definitions
All NBAP Elementary Procedures are divided into TWO Types NBAP Common Procedures NBAP Dedicated Procedures Also, based on the response types, all Elementary Procedures are divided into TWO classes Class 1 Elementary Procedures Class 2 Elementary Procedures Please refer to Section 8, Table 2 and Table 3 of 3GPP TS 25.433 V11.3.0 (2012-12) for the comprehensive list of all Class 1 and Class 2 elementary procedures
Tusharadri Sarkar
11
NBAP Procedures
Elements of NBAP Communication
NBAP Message : Information Elements (IEs)
Presence (M, O, C) Criticality (YES, GLOBAL, EACH, none) Range Assigned Criticality (10.3.2)
Please refer to Section 9 3GPP TS 25.433 V11.3.0 (2012-12) for the comprehensive list of all NBAP Messages and corresponding IEs
Tusharadri Sarkar
12
NBAP Procedures
Elements of NBAP Communication
NBAP Message : Protocol Error Handling Transfer Syntax Error
Value range List of elements Mandatory IE Order
Logical Error
How to handle in Class1 and Class 2 Elementary Procedures? The Error Indication Procedure
Please refer to Section 10 3GPP TS 25.433 V11.3.0 (2012-12) for the Handling of Unknown, Unforeseen and Erroneous Protocol Data
March 13, 2013 Tusharadri Sarkar 13
NBAP Procedures
Elements of NBAP Communication
Tusharadri Sarkar
14
NBAP Procedures
A quick look at UMTS Channels and their mapping
Tusharadri Sarkar
15
NBAP Procedures
A quick look at UMTS Channels and their mapping (DL)
Tusharadri Sarkar
16
NBAP Procedures
A quick look at UMTS Channels and their mapping (UL)
Tusharadri Sarkar
17
NBAP Procedures
A quick look at a typical Node B Initialization
Node B RNC
Audit Request Procedure CellSetup Procedure System Information Update Procedure Common Transport Setup Procedures for PRACH, AICH, S-CCPCH, FACH, PCH and RACH + ALCAP and FPSync. for RACH, FACH and PCH
System Information Update Request - SIB 5 Update Resources and Unblock Cell System Information Update Request - SIB 3
Tusharadri Sarkar
18
Tusharadri Sarkar
21
Configuration Alignment
Node B
Message: AUDIT REQUIRED INDICATION Node B requests CRNC to perform audit on logical resources Possible Cause: misalignment of state or configuration information CRNC initiates Audit procedure upon receiving this message
Tusharadri Sarkar
23
Node B
AUDIT RESPONSE
Initiating message: AUDIT REQUEST CRNC may use an audit sequence (more than one Audit proc.) IE: Start Of Audit Sequence Indicator
start of audit sequence, not start of audit sequence
Tusharadri Sarkar
24
Secondary CPICH Secondary CCPCH FACH, PRACH, RACH and AICH Information HS-DSCH and E-DCH Resource Information Communication Control Port Information (for each communication port)
Tusharadri Sarkar
25
Tusharadri Sarkar
26
Node B
AUDIT FAILURE
Unsuccessful Outcome: AUDIT FAILURE Node B unable to perform audit on configuration and status of logical resources IE: Cause
Appropriate Cause is sent to CRNC
Tusharadri Sarkar
27
Node B CRNC
RESET REQUEST RESET RESPONSE
Node B
Initiating Message: RESET REQUEST Align the resources of Node B and CRNC in the event of an abnormal failure IE: Reset Indicator
Communication Context Communication Control Port Node B
Tusharadri Sarkar
28
Cell Configuration
Initiating Message: CELL SETUP REQUEST Which Cell to Setup? IE: C-ID What Resources to be used? IE: Local Cell ID Important IEs for a Serving Cell
URFCN, Maximum Transmission Power, Primary Scrambling Code Synchronization Configuration, Closed Loop Timing Adjustment Mode Primary SCH, Secondary SCH Information Primary CPICH, Secondary CPICH, Primary CCPCH, BCH Information
March 13, 2013 Tusharadri Sarkar 30
Unsuccessful Outcome: CELL SETUP FAILURE IE Configuration Generation ID is unchanged in Node B Cell state: Not Existing. Appropriate Cause is sent to CRNC
March 13, 2013 Tusharadri Sarkar 31
Initiating Message: CELL RECONFIGURATION REQUEST Node B reconfigures the parameters mentioned in the request
Primary and Secondary SCH Power P-CPICH and S-CPICH Power BCH Power (from Primary CCPCH Information) Time Slot Configuration and Synchronization Information Maximum Transmission Power
Successful Outcome: CELL RECONFIGURATION RESPONSE Node B stores new Configuration Generation ID
March 13, 2013 Tusharadri Sarkar 32
Unsuccessful Outcome: CELL RECONFIGURATION FAILURE Node B failed to reconfigures at least one parameters Old configuration is retained Node B keeps old Configuration Generation ID Appropriate Cause is sent to CRNC
Tusharadri Sarkar
33
Initiating Message: CELL DELETION REQUEST Node B removes the cell mentioned by C-ID What will be deleted from the Cell?
All Common and Dedicated Channels All Radio Links All Node B Communication Contexts having no more RLs All user plane transport bearers corresponding to the removed common and dedicated channels
Initiating Message: COMMON TRANSPORT CHANNEL SETUP RQUEST CRNC establishes the necessary resources in Node B regarding
S-CCPCH, FACH, PCH, PICH, PRACH, RACH, AICH[FDD]
Tusharadri Sarkar
36
Binding ID and Transport Layer Address can also be provided by CRNC incase of IP backhaul
Tusharadri Sarkar
38
Common Transport and Physical Channel state: Enabled Common Physical Channels now exists in the Uu Interface
Tusharadri Sarkar
39
COMMON TRANSPORT CHANNEL SETUP REQUEST COMMON TRANSPORT CHANNEL SETUP FAILURE
Unsuccessful Outcome: COMMON TRANSPORT CHANNEL SETUP FAILURE Node B rejects configuration of all channels State of the channels remains same as before Appropriate Cause is sent to CRNC
Tusharadri Sarkar
40
Tusharadri Sarkar
41
Node B
Initiating Message: COMMON TRANSPORT CHANNEL RECONFIGURATION RQUEST One request message can configure only one of the combinations
One S-CCPCH, FACHs, PCH and PICH related to that S-CCPCH One PRACH, one RACH and one AICH related to that PRAC
Successful Outcome: COMMON TRANSPORT CHANNEL RECONFIGURATION RESPONSE Node B stores the new Configuration Generation ID
March 13, 2013 Tusharadri Sarkar 42
Node B
Unsuccessful Outcome: COMMON TRANSPORT CHANNEL RECONFIGURATION FAILURE Node B rejects reconfiguration of all the channels State of the channels remains same as before Appropriate Cause is sent to CRNC
Tusharadri Sarkar
43
Node B
Initiating Message: COMMON TRANSPORT CHANNEL DELETION RQUEST Which one to delete? IE: COMMON PHYSICAL CHANNEL ID If Secondary CCPCH, Node B deletes
The S-CCPCH, all FACHs, the PCH supported by that FACH and the PICH supported by that PCH
Successful Outcome: COMMON TRANSPORT CHANNEL DELETION RESPONSE State of the deleted channels: Non Existing Node B stores new Configuration Generation ID
Tusharadri Sarkar
45
Node B
Initiating Message: RADIO LINK SETUP REQUEST It establishes the first Radio Link (RL) for a UE and achieves synchronization in the user plane What channels are established?
One or more DCHs on all RLs One HS-DSCH (per Cell) in one RL (Optional) One E-DCH on one or more RLs (Optional)
Tusharadri Sarkar
47
Tusharadri Sarkar
49
Node B
Tusharadri Sarkar
50
Tusharadri Sarkar
52
MIB contains:
PLMN Identity References to other SIBs
SB contains:
Scheduling information of number of SIBs
SIB contains:
Specific system information
March 13, 2013 Tusharadri Sarkar 53
Unsuccessful Outcome: SYSTEM INFORMATIO UPDATE FAILURE Node B discards all changes Appropriate Cause is sent to CRNC
March 13, 2013 Tusharadri Sarkar 54
Node B
Initiating Message: COMMON MEASUREMENT INITIATION REQUEST How to Keep Track? IE: Measurement ID and IE: C-ID What to measure? IE: Common Measurement Type Typical measurement requests
SFN-SFN Observed Time Difference Received Total Wideband Power for Cell Portion Transmitted Carrier Power for Cell Portion HS-DSCH required Power for Cell Portion
March 13, 2013 Tusharadri Sarkar 58
Successful Outcome: COMMON MEASUREMENT INITIATION RESPONSE Node B uses the same Measurement ID as provided in request
March 13, 2013 Tusharadri Sarkar 59
Unsuccessful Outcome: COMMON MEASUREMENT INITIATION FAILURE Node B uses the same Measurement ID as provided in request Appropriate Cause is sent to CRNC
Tusharadri Sarkar
60
Message: COMMON MEASUREMENT REPORT Initiated by Node B when requested measurement criteria are met IE: Common Measurement Object Type
Cell RACH
IE: Measurement ID as provided in measurement initiation request IE: Common Measurement Value Information
Measurement available/not available (measurement accuracy fulfillment)
Message: COMMON MEASUREMENT TERMINATION REQUEST Node B terminates reporting of common measurements corresponding to the received Measurement ID
Tusharadri Sarkar
62
Node B
Message: COMMON MEASUREMENT FAILURE INDICATION Reason: A previously requested measurement can no longer be reported Node B locally terminates the indicated measurement
Tusharadri Sarkar
63
Node B
Initiating Message: RADIO LINK ADDITION REQUEST Request for additional RLs for the UE when the Node B Communication Context already exists Difference with RADIO LINK SETUP REQUEST
IE: Node B Communication Context ID in place of IE: CRNC Communication Context ID
Tusharadri Sarkar
67
Successful Outcome: RADIO LINK ADDITION RESPONSE Node B continuously attempts UL sync on the Uu interface Should Node B start transmission on the DL DPDCH(s) on the new RL?
IE: Delayed Activation (values: Separate Indication, CFN, none) IE: Activation CFN
Tusharadri Sarkar
68
Node B
Unsuccessful Outcome: RADIO LINK ADDITION FAILURE Establishment of at least one of the Radio Links unsuccessful Appropriate Cause is sent to CRNC
Tusharadri Sarkar
69
Quiz
Is the Dedicated Radio Link Setup a NBAP Common procedure or a NBAP Dedicated procedure?
CRNC requests new configuration of RL(s) related to an existing Node B Communication Context Reconfiguration happens in two steps
Reconfiguration Prepare Reconfiguration Commit
Tusharadri Sarkar
72
Successful Outcome: RADIO LINK RECONFIGURATION READY Node B successfully reserved all the necessary resources for reconfiguration of RLs requested by CRNC A Prepared Reconfiguration now exists in Node B
Tusharadri Sarkar
73
Message: RADIO LINK RECONFIGURATION COMMIT CRNC orders Node B to switch to the new configuration for RL(s) When to switch? IE: CFN (M) and IE: Fast Reconfiguration (O)
Fast Reconfiguration present: Node B switches to new configuration at the next coming CFN equal to the CFN requested by CRNC Fast Reconfiguration absent: Node B switches to new configuration as soon as it detects that UE has started using the new configuration i.e. UE already started using the new UL Scrambling code
Tusharadri Sarkar
74
Initiating Message: RADIO LINK RECONFIGURATION REQUEST When there is no need to synchronize the time of switching e.g. reconfiguration of Packet Switched Connections The functions are similar to Synchronized Radio Link Reconfiguration Preparation i.e.
DCH addition, DCH modification and DCH deletion HS-DSCH Setup and HS-DSCH modification Handling Physical Channels and Radio Links Signaling Bearer Management and DL Power Control
March 13, 2013 Tusharadri Sarkar 75
Successful Outcome: RADIO LINK RECONFIGURATION RESPONSE Node B has successfully allocated the required resources, and changed to the new configuration For each new transport channel being added or modified Node B send a Transport Layer Address and a Binding ID to CRNC
Tusharadri Sarkar
76
Unsuccessful Outcome: RADIO LINK RECONFIGURATION FAILURE Node B failed to allocate the necessary resources for all the new DCHs of one set of coordinated DCHs requested to be setup Appropriate Cause is sent to CRNC
Tusharadri Sarkar
77
Node B
Initiating Message: RADIO LINK DELETION REQUEST CRNC orders to release one or more resources established Radio Links towards a UE Which RL(s) to be deleted?
RL(s) uniquely identified by RL ID, Node B Communication Context ID and CRNC Communication Context ID
Successful Outcome: RADIO LINK DELETION RESPONSE After RL(s) deletion Node B will start UL sync for remaining RLs
Tusharadri Sarkar
78
Message: RADIO LINK FAILURE INDICATION Reason: One or more established RLs have failed IE: RL Information
One or more individual Radio Link(s) failed
RL failure might cause loss of UL sync as well Appropriate Cause is sent to CRNC
Tusharadri Sarkar
80
Message: RADIO LINK RESTORE INDICATION Reason: Node B achieved or re-achieved UL sync of one or more established Radio Links or Radio Link Sets on the Uu Interface IE: RL Information
One or more individual Radio Link(s) re-established
This is triggered when UL synchronization detection algorithm finishes successfully and indicates that UL sync exists
March 13, 2013 Tusharadri Sarkar 81
Tusharadri Sarkar
82
Node B
Message: DL POWER CONTROL REQUEST CRNC wants to control DL transmission power of one or more RLs for any existing Node B Communication Context IE: Power Adjustment Type
Values: Common / Individual / None
Tusharadri Sarkar
84
Message: DEDICATED MEASUREMENT INITIATION REQUEST Which dedicated resources to perform the measurement on?
IE: Node B Communication Context ID
What to measure?
IE: Dedicated Measurement Object Type IE: Node B Communication Context ID
March 13, 2013 Tusharadri Sarkar 86
Tusharadri Sarkar
87
Dedicated measurement can not be initiated if there exists a Prepared Reconfiguration, except it is a ALL NBCC case
Successful Outcome: DEDICATED MEASUREMENT INITIATION RESPONSE Node B uses the same Measurement ID as received in request
Tusharadri Sarkar
88
Unsuccessful Outcome: DEDICATED MEASUREMENT INITIATION FAILURE Node B uses the Measurement ID as received in request Appropriate Cause is sent to CRNC
Tusharadri Sarkar
89
Message: DEDICATED MEASUREMENT REPORT Initiated by Node B when requested measurement criteria are met IE: Dedicated Measurement Object Type
RL / ALL RL RLS / ALL RLS
IE: Measurement ID as provided in measurement initiation request IE: Dedicated Measurement Value Information IE: Measurement Recovery Report Indicator
March 13, 2013 Tusharadri Sarkar 90
Node B
Message: DEDICATED MEASUREMENT TERMINATION REQUEST Node B terminates reporting of dedicated measurements corresponding to the received Measurement ID IE Dedicated Measurement Termination can not be initiated if there exists a Prepared Reconfiguration, except the ALL NBCC case
Tusharadri Sarkar
91
Message: DEDICATED MEASUREMENT FAILURE INDICATIN Reason: A previously requested dedicated measurement can no longer be reported Once Node B has sent RADIO LINK SETUP RESPONSE it can initiates Dedicated Measurement Failure procedure at any time If the measurement was started with Node B Communication Context ID set to ALL NBCC and Node B initiates Dedicated Measurement Failure procedure then the CRNC Communication Context ID is set to ALL CRNCCC
March 13, 2013 Tusharadri Sarkar 92
Thank You