nodeb application part

An introduction to Node B Application Part (NBAP)

Tusharadri SarkarAricentMarch 13, 2013

1March 13, 2013 Tusharadri Sarkar

Iub Interface and NBAP Functions of NBAP NBAP Procedures NBAP Common Procedures NBAP Dedicated Procedures Questions and Answers

Agenda

2Tusharadri Sarkar

Iub Interface and NBAP

Iub Interface : RNC and NodeB

Iub interface connects NodeB and RNC of UTRAN The NBAP protocol stack used for NBAP signaling is shown above


Iub Interface : RNC and NodeB

NBAP protocol stack is supported on both ATM and IP


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


Presenter

Presentation Notes

Cell Configuration Management: This function gives the CRNC the possibility to manage the cell configuration information in a Node B. Common Transport Channel Management: This function gives the CRNC the possibility to manage configuration of Common Transport Channels in a Node B. System Information Management: This function gives the CRNC the ability to manage the scheduling of System Information to be broadcast in a cell. Resource Event Management: This function gives the Node B the ability to inform the CRNC about the status of Node B resources. Configuration Alignment: This function gives the CRNC and the Node B the possibility to verify and enforce that both nodes have the same information on the configuration of the radio resources. Measurements on Common Resources: This function allows the CRNC to initiate measurements on common resources in the Node B. The function also allows the Node B to report the result of the measurements. Radio Link Management: This function allows the CRNC to manage radio links using dedicated resources in a Node B. Radio Link Supervision: This function allows the CRNC to report failures and restorations of a Radio Link. Compressed Mode Control [FDD]: This function allows the CRNC to control the usage of compressed mode in a Node B. Measurements on Dedicated Resources: This function allows the CRNC to initiate measurements on dedicated resources in the Node B. The function also allows the Node B to report the result of the measurements. DL Power Drifting Correction [FDD]: This function allows the CRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links. Reporting of General Error Situations: This function allows reporting of general error situations, for which function specific error messages have not been defined.

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.


NBAP Procedures

NBAP ProceduresSome 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


Presenter

Presentation Notes

Node B Communication Context: The Node B Communication Context contains the necessary information for the Node B for communication with a specific UE. The Node B Communication Context is created by the Radio Link Setup procedure and deleted by the Radio Link Deletion procedure when deleting the last Radio Link within the Node B Communication Context. The Node B Communication Context is identified by the Node B Communication Context ID.

NBAP ProceduresSome 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.433V11.3.0 (2012-12) for the comprehensive list of all Class 1 and Class 2 elementary procedures


Presenter

Presentation Notes

NBAP common procedures are procedures that request initiation of a Node B Communication Context for a specific UE in Node B or are not related to a specific UE. NBAP common procedures also incorporate logical O&M (TS 25.401) procedures. NBAP dedicated procedures are procedures that are related to a specific Node B Communication Context in Node B. This Node B Communication Context is identified by a Node B Communication Context identity. Class 1 Elementary Procedures are procedures with a response (Success or Failure) Class 2 Elementary Procedures are procedures without a response (Assumed to be successful always).

NBAP ProceduresElements of NBAP Communication

NBAP Message : Information Elements (IEs)– Presence (M, O, C)– Criticality (YES, GLOBAL, EACH, none)– Range– Assigned Criticality (10.3.2)

The NBAP Header– Message Type and Procedure Code– Message Discriminator– Transaction ID

Abstract Syntax (ASN.1)– NBAP ASN.1 definition - ITU-T Rec. X.680 and ITU-T Rec. X.681– NBAP ASN.1 Basic Packed Encoding Rules (variant) - ITU T Rec. X.691

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


Presenter

Presentation Notes


NBAP Message : Protocol Error Handling

Transfer Syntax Error– Value range– List of elements – Mandatory IE– Order

Abstract Syntax Error: Actual Criticality Information is handled here– Reject IE– Ignore IE and Notify Sender– Ignore IE

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


Presenter

Presentation Notes

Class 1: Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: -Protocol Causes: 1.Semantic Error 2.Message not compatible with receiver state Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the ERROR INDICATION procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error. Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. Class 2: Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the ERROR INDICATION procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error.

NBAP ProceduresA quick look at UMTS Channels and their mapping


Presenter

Presentation Notes

Logical Channels: 1.1. Control Channels (UL/DL) 1.1.1. Broadcast Control Channel (BCCH), Downlink (DL) 1.1.2. Paging Control Channel (PCCH), DL 1.1.3. Dedicated Control Channel (DCCH), UL/DL 1.1.4. Common Control Channel (CCCH), UL/DL 1.2. Traffic Channels (UL/DL) 1.2.1. Dedicated Traffic Channel (DTCH), UL/DL 1.2.2. Common Traffic Channel (CTCH), Unidirectional (one to many) 2. Transport Channels: 2.1. Dedicated Transport Channel (DCH), UL/DL, mapped to DCCH and DTCH 2.2. Broadcast Channel (BCH), DL, mapped to BCCH 2.3. Forward Access Channel (FACH), DL, mapped to BCCH, CCCH, CTCH, DCCH and DTCH 2.4. Paging Channel (PCH), DL, mapped to PCCH 2.5. Random Access Channel (RACH), UL, mapped to CCCH, DCCH and DTCH 2.6. Uplink Common Packet Channel (CPCH), UL, mapped to DCCH and DTCH 2.7. Downlink Shared Channel (DSCH), DL, mapped to DCCH and DTCH 3. Physical Channels: 3.1. Primary Common Control Physical Channel (P-CCPCH), mapped to BCH 3.2. Secondary Common Control Physical Channel (S-CCPCH), mapped to FACH, PCH 3.3. Physical Random Access Channel (PRACH), mapped to RACH 3.4. Dedicated Physical Data Channel (DPDCH), mapped to DCH 3.5. Dedicated Physical Control Channel (DPCCH), mapped to DCH 3.6. Physical Downlink Shared Channel (PDSCH), mapped to DSCH 3.7. Physical Common Packet Channel (PCPCH), mapped to CPCH 3.8. Synchronisation Channel (SCH) 3.9. Common Pilot Channel (CPICH) 3.10. Acquisition Indicator Channel (AICH) 3.11. Paging Indication Channel (PICH) 3.12. CPCH Status Indication Channel (CSICH) 3.13. Collision Detection/Channel Assignment Indication Channel (CD/CA-ICH)

NBAP ProceduresA quick look at UMTS Channels and their mapping (DL)


NBAP ProceduresA quick look at UMTS Channels and their mapping (UL)


NBAP ProceduresA quick look at a typical Node B Initialization

18

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 FP-

Sync. for RACH, FACH and PCH

System Information UpdateRequest - SIB 5

Update Resources and Unblock Cell

System Information UpdateRequest - SIB 3

March 13, 2013 Tusharadri Sarkar

NBAP Common Procedures

NBAP Common Procedures The main NBAP Common procedures are as follows

– Function: Configuration Alignment Audit Required Audit Reset

– Function: Cell Configuration Cell Setup Cell Reconfiguration Cell Deletion

– Function: Common Transport Channel Handling Common Transport Channel Setup Common Transport Channel Reconfiguration Common Transport Channel Deletion

– Function: Radio Link Management Radio Link Setup


NBAP Common Procedures The main NBAP Common procedures are as follows

– Function: System Information Management System Information Update (SIB)

– Function: Resource Event Management Resource Status Indication

– Function: Measurement on Common Resources Common Measurement Initiation Common Measurement Reporting Common Measurement Termination Common Measurement Failure


Configuration Alignment

NBAP Common ProceduresAudit Required

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

23

CRNC Node B

AUDIT REQUIRED INDICATION


Presenter

Presentation Notes

8.2.6

NBAP Common ProceduresAudit

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

Successful Outcome: AUDIT RESPONSE IE: End Of Audit Sequence Indicator– end of audit sequence, not end of audit sequence

24

CRNC Node B

AUDIT REQUEST

AUDIT RESPONSE


Presenter

Presentation Notes

8.2.7 If the Start Of Audit Sequence Indicator IE in the AUDIT REQUEST message is set to "start of audit sequence" a new audit sequence is started, any ongoing audit sequence shall be aborted and the Node B shall provide (part of the) audit information. If the Start Of Audit Sequence Indicator IE is set to "not start of audit sequence", the Node B shall provide (part of) the remaining audit information not already provided during this audit sequence. If the information provided in the AUDIT RESPONSE message completes the audit sequence, the Node B shall set the End Of Audit Sequence Indicator IE in the AUDIT RESPONSE message to "End of Audit Sequence". If not all audit information has been provided yet as part of the ongoing audit sequence, the Node B shall set the End Of Audit Sequence Indicator IE in the AUDIT RESPONSE message to "Not End of Audit Sequence".


AUDIT RESPONSE: Important Node B information are–Cell Information C-ID Configuration Generation ID Resource Operational State Availability Status Local Cell ID

–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)


Presenter

Presentation Notes

9.1.17 The full list of IEs in AUDIT Response Message


AUDIT RESPONSE: Important Node B information are

– Local Cell Information (for each local cell) Maximum and Minimum DL Power Capability Minimum Spreading Factor HSDPA Capability E-DCH Capability MIMO Capability

– Local Cell Group Information

–Power Local Cell Group Information Power Local Cell Group ID Maximum DL Power Capability


Presenter

Presentation Notes

9.1.17 The full list of IEs in AUDIT Response Message


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

27

CRNC Node B

AUDIT REQUEST

AUDIT FAILURE


Presenter

Presentation Notes

9.2.1.6 The complete list of all possible ‘Cause’ values

NBAP Common ProceduresReset

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

Successful Outcome: RESET RESPONSE

28

CRNC

RESET RESPONSE

RESET REQUESTNode B CRNC

RESET RESPONSE

RESET REQUESTNode B


Presenter

Presentation Notes

8.2.19 If the Reset Indicator IE is set to "Communication Context", the Node B shall remove all the indicated Node B Communication Contexts (identified by a Node B Communication Context ID or a CRNC Communication Context ID IE) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC. If the Reset Indicator IE is set to "Communication Control Port", the Node B shall remove all the Node B Communication Contexts controlled via the indicated Communication Control Port(s) and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC. If the Reset Indicator IE is set to "Node B", the Node B shall remove all the Node B Communication Contexts within the Node B and all the radio resources allocated for these Node B Communication Contexts. The Node B shall also initiate release of the user plane transport bearers that were involved in these Contexts. After clearing all related resources, the Node B shall return the RESET RESPONSE message to the CRNC.

Cell Configuration

CRNC Node B

CELL SETUPRESPONSE

CELL SETUP REQUEST

NBAP Common ProceduresCell Setup

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


Presenter

Presentation Notes

8.2.12

CRNC Node B

CELL SETUP FAILURE

CELL SETUP REQUEST

NBAP Common ProceduresCell Setup

Successful Outcome: CELL SETUP RESONSE What will Node B Store? IE: Configuration Generation ID Which channels exists when a cell is successfully configured?

P-CPICH, S-CPICH, P-SCH, S-SCH, P-CCPCH and BCH

31

• Unsuccessful Outcome: CELL SETUP FAILURE• IE Configuration Generation ID is unchanged in Node B• Cell state: Not Existing. Appropriate Cause is sent to CRNC


Presenter

Presentation Notes

8.2.12 Radio Network Layer Cause: -S-CPICH not supported -Requested Tx Diversity Mode not supported -Power level not supported -Node B Resources unavailable -IPDL not supported -[FDD - S-CPICH power offset support not available] Miscellaneous Cause: -O&M Intervention -Control processing overload -HW failure

CRNC Node B

CELL RECONFIGURATION REQUEST

CELL RECONFIGURATION RESPONSE

NBAP Common ProceduresCell Reconfiguration

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


Presenter

Presentation Notes

8.2.13

NBAP Common ProceduresCell Reconfiguration

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

33

CRNC Node B

CELL RECONFIGURATION REQUEST

CELL RECONFIGURATION FAILURE


Presenter

Presentation Notes

8.2.13 Radio Network Layer Cause: -Power level not supported -Node B Resources unavailable -IPDL not supported -[FDD - S-CPICH power offset support not available] -[FDD - Requested Configuration Not Supported] Miscellaneous Cause: -O&M Intervention -Control processing overload -HW failure

NBAP Common ProceduresCell Deletion

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

Successful Outcome: CELL DELETION RESPONSE

34

CRNC Node B

CELL DELETION RESPONSE

CELL DELETION REQUEST


Presenter

Presentation Notes

8.2.14 Upon reception, the Node B shall remove the cell and any remaining common and dedicated channels within the cell. The states for the cell and the deleted common channels shall be set to Not Existing (TS 25.430 [6]). The Node B shall remove all Radio Links from the Cell and all Node B Communication Contexts that as a result do not have a Radio Link. The Node B shall also initiate release of the user plane transport bearers for the removed common and dedicated channels except the case that there is at least one FACH channel in this cell using the same transport bearer existing in other cell(s) in the Node B. In this case, the Node B shall remove the cell and any remaining common and dedicated channels within the cell but keep the common transport bearer which is used by the remaining common transport channel(s) in other cell(s).

Common Transport Channel Handling

NBAP Common ProceduresCommon Transport Channel Setup

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]

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 [FDD] related to that PRACH

36

CRNC Node B

COMMON TRANSPORT CHANNEL SETUPREQUEST

COMMON TRANSPORT CHANNEL SETUPRESPONSE


Presenter

Presentation Notes

8.2.1


IE: Secondary CCPCH– Common Physical Channel ID– DL Scrambling Code– Channelization Code Number– Secondary CCPCH Slot Format

IE: FACH Parameter– Common Transport Channel ID– Max FACH Power– IE: PCH Parameter Common Transport Channel ID PCH Power IE: PICH Parameter Common Physical Channel ID Channelization Code Number PICH Power


Presenter

Presentation Notes

8.2.1


IE: PRACH– Common Physical Channel ID– Scrambling Code Number– Preamble Signature & Preamble Threshold– Allowed Slot Format– IE: RACH Parameter Common Transport Channel ID Transport Format Set

– IE: AICH Parameter Common Physical Channel ID Channelization Code Number AICH Power

Binding ID and Transport Layer Address can also be provided by CRNC incase of IP backhaul


Presenter

Presentation Notes

8.2.1 Refer to 9.1.3. for the complete IE set of Common Transport Channel Setup Request message


Successful Outcome: COMMON TRANSPORT CHANNEL SETUP RESPONSE

Node B stores Configuration Generation ID IE: Common Transport Channel Information Response For each configured common transport channel (FACHs, PCH

and RACH), Node B notifies back CRNC with this IE which includes– Common Transport Channel ID– Binding ID– Transport Layer Address

Common Transport and Physical Channel state: Enabled Common Physical Channels now exists in the Uu Interface


Presenter

Presentation Notes

8.2.1 Refer to 9.1.4. for the complete IE set of Common Transport Channel Setup Response message and 9.2.1.14A. for Common Transport Channel Information Response IE.


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

40

COMMON TRANSPORT CHANNEL SETUPREQUEST

CRNC Node B

COMMON TRANSPORT CHANNEL SETUPFAILURE


Presenter

Presentation Notes

8.2.1 Radio Network Layer Cause: -Cell not available -Power level not supported -Node B Resources unavailable -Requested Tx Diversity Mode not supported -UL SF not supported -DL SF not supported -Common Transport Channel Type not supported -MICH not supported Transport Layer Cause: -Transport Resources Unavailable Miscellaneous Cause: -O&M Intervention -Control processing overload -HW failure

NBAP Common ProceduresCommon Transport Channel Reconfiguration

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

42

CRNC Node B

COMMON TRANSPORT CHANNELRECONFIGURATION REQUEST

COMMON TRANSPORT CHANNELRECONFIGURATION RESPONSE


Presenter

Presentation Notes

8.2.2

NBAP Common ProceduresCommon Transport Channel Reconfiguration

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

43

CRNC Node B

COMMON TRANSPORT CHANNELRECONFIGURATION REQUEST

COMMON TRANSPORT CHANNELRECONFIGURATION FAILURE


Presenter

Presentation Notes

8.2.2 Radio Network Layer Cause: -Cell not available -Power level not supported -Node B Resources unavailable Transport Layer Cause: -Transport Resources Unavailable Miscellaneous Cause: -O&M Intervention -Control processing overload -HW failure

NBAP Common ProceduresCommon Transport Channel Deletion

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 If PRACH, Node B deletes The PRACH, the RACH and the AICH [FDD] supported by that

PRACH

44

CRNC Node B

COMMON TRANSPORT CHANNELDELETION REQUEST

COMMON TRANSPORT CHANNELDELETION RESPONSE


Presenter

Presentation Notes

8.2.3

NBAP Common ProceduresCommon Transport Channel Deletion

Successful Outcome: COMMON TRANSPORT CHANNEL DELETION RESPONSE

State of the deleted channels: Non Existing Node B stores new Configuration Generation ID


Presenter

Presentation Notes

8.2.3

Radio Link Management

NBAP Common ProceduresRadio Link Setup

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)

47

CRNC Node B

RADIO LINK SETUP REQUEST

RADIO LINK SETUP RESPONSE


Presenter

Presentation Notes

8.2.17


IE: CRNC Communication Context ID IE: UL DPCH information

– UL Scrambling Code, UL SIR Target IE: DL DPCH Information

– DL DPCH Slot Format IE: DCH Information

– DCH FDD Information DCH Specific Info (one or more)

IE: RL Information (one or more)– RL ID, C-ID, First RLS Indicator, Delayed Activation– Initial DL Transmission Power– Maximum and Minimum DL Power

IE: E-DPCH Information– HARQ Info for E-DCH

IE: UE Aggregate Maximum Bit Rate (Optional)


Presenter

Presentation Notes

8.2.17 9.2.2.4DDCH FDD Information If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK SETUP REQUEST message, the NodeB shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. 9.1.36. Complete List of IEs supported by Radio Link Setup Request


Transport Channel Handling: DCHs – Multiple DCH Specific Info – a set of coordinated DCHs– Uplink or Downlink DCH? IE: Unidirectional DCH Indicator

Transport Channel Handling: HS-DSCH– Requested HS-PDSCH is setup on serving HS-DSCH– Which RL to set the HS-PDSCH on? IE: HS-PDSCH RL ID

Successful Outcome: RADIO LINK SETUP RESPONSE– Node B now continuously attempts UL sync on the Uu interface– IE: RL Information Response: Node B populates RL ID, RL Set ID Received Total Wideband Power (RTWP) DCH Information Response


Presenter

Presentation Notes

8.2.17 If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs, then the Node B shall treat the DCHs in the DCH Information IE as a set of co-ordinated DCHs. The Node B shall include these DCHs in the new configuration only if it can include all of them in the new configuration. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Uplink DCH only", the Node B shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to "Downlink DCH only", the Node B shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. Response Message: If the RLs are successfully established, the Node B shall and respond with a RADIO LINK SETUP RESPONSE message. After sending the RADIO LINK SETUP RESPONSE message the Node B shall continuously attempt to obtain UL synchronization on the Uu interface. For each RL for which the Delayed Activation IE is not included in the RADIO LINK SETUP REQUEST message, the Node B shall: -[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].] -[TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].] For each RL for which the Delayed Activation IE is included in the RADIO LINK SETUP REQUEST message, the Node B shall: -if the Delayed Activation IE indicates "Separate Indication": -not start any DL transmission for the concerned RL on the Uu interface; -if the Delayed Activation IE indicates "CFN": -[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.] -[TDD - start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]


Unsuccessful Outcome: RADIO LINK SETUP FAILURE– IE: Unsuccessful RL Information Response – Node B populates RL ID and Cause

– IE: Successful RL Information Response – Node B populates RL ID, RL Set ID Received Total Wideband Power (RTWP) DCH Information Response

50

CRNC Node B

RADIO LINK SETUP REQUEST

RADIO LINK SETUP FAILURE


Presenter

Presentation Notes

8.2.17 Radio Network Layer Cause: -Combining not supported -Combining Resources not available -Requested Tx Diversity Mode not supported -Number of DL codes not supported -Number of UL codes not supported -UL SF not supported -DL SF not supported -Dedicated Transport Channel Type not supported -Downlink Shared Channel Type not supported -Uplink Shared Channel Type not supported -CM not supported -[FDD - DPC mode change not supported] -Delayed Activation not supported -F-DPCH not supported -[FDD - Continuous Packet Connectivity DTX-DRX operation not available] -[FDD - Continuous Packet Connectivity UE DTX Cycle not available] -[FDD - MIMO not available] -E-DCH MAC-d PDU Size Format not available -[FDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD - Multi Cell operation not available.] -[1.28Mcps TDD- MIMO not available] -[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD - TX diversity for MIMO UE on DL Control Channels not available] -[FDD – Single Stream MIMO not available] -[FDD - Multi Cell operation with MIMO not available] -[FDD - Multi Cell operation with Single Stream MIMO not available] -[FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available] -[FDD - Multi Cell E-DCH operation not available] -[FDD – Frequency Specific Compressed mode operation not available] -[FDD - UL CLTD operation not available] -[FDD - MIMO with four transmit antennas not available] -[FDD - Dual Stream MIMO with four transmit antennas not available] -[FDD – Multiflow operation not available] -[FDD - SixtyfourQAM UL operation not available] -[FDD – UL MIMO operation not available] -[FDD – UL MIMO and SixteenQAM operation not available] -[FDD – UL MIMO and SixtyfourQAM operation not available] Transport Layer Cause: -Transport Resources Unavailable Miscellaneous Cause: -O&M Intervention -Control processing overload -HW failure

System Information Management

NBAP Common ProceduresSystem Information Update

Initiating Message: SYSTEM INFORMATION UPDATE REQUEST

Enables Node B to apply The correct scheduling Appropriate contents in the System Information Segment of BCCH

When to update BCCH? IE: BCCH Modification Time (Optional) Update BCCH at the time instance starting from the SFN value

52

SYSTEM INFORMATION UPDATE RESPONSE

CRNC Node B

SYSTEM INFORMATION UPDATE REQUEST


Presenter

Presentation Notes

8.2.16 SFN mod IB_SG_REP = IB_SG_POS


Which information to update? IE: MIB/SB/SIB Information Priority: MIB > SB/SIB Operations Information Block Addition Information Block Deletion Information Block Update

MIB contains: PLMN Identity References to other SIBs

SB contains: Scheduling information of number of SIBs

SIB contains: Specific system information


Presenter

Presentation Notes

8.2.16 MIB – Master Information Block SIB 1 i) Cell Access Related Information - PLMN Identity List, PLMN Identity, TA Code, Cell identity & Cell Status ii) Cell Selection Information - Minimum Receiver Level iii) Scheduling Information - SI message type & Periodicity, SIB mapping Info, SI Window length SIB 2 i) Access Barring Information - Access Probability factor, Access Class Baring List, Access Class Baring Time ii) Semi static Common Channel Configuration - Random Access Parameter, PRACH Configuration iii) UL frequency Information - UL EARFCN, UL Bandwidth, additional emmission SIB 3 Information/Parameters for intra-frequency cell reselections SIB 4 Information on intra-frequency neighboring cells SIB 5 Information on inter-frequency neighboring cells SIB 6 Information for reselection to UMTS (UTRAN) cells SIB 7 Information for reselection to GSM (GERAN) cells SIB 8 Information for reselection to CDMA2000 systems SIB 9 Home eNodeB name – for future LTE femtocell applications SIB 10 + 11 ETWS (Earthquake and Tsunami Warning System) information SIB 12 Commercial Mobile Alerting System (CMAS) information.


Examples of some SIBs SIB 1 PLMN ID list, Cell ID, Cell status, Scheduling info, SIB mapping SIB 3 Information/Parameters for intra-frequency cell reselections SIB 5 Information on inter-frequency neighboring cells SIB 10 + 11 ETWS

Successful Outcome: SYSTEM INFORMATIO UPDATE RESPONSE

54

SYSTEM INFORMATION UPDATE FAILURE

CRNC Node B

SYSTEM INFORMATION UPDATE REQUEST

Unsuccessful Outcome: SYSTEM INFORMATIO UPDATE FAILURE

Node B discards all changes

Appropriate Cause is sent to CRNC


Presenter

Presentation Notes

8.2.16 Radio Network Layer Cause: -SIB Origination in Node B not Supported Miscellaneous Cause: -Hardware failure -Control Processing overload -O&M Intervention

Resource Event Management

NBAP Common ProceduresResource Status Indication

Message: RESOURCE STATUS INDICATION When to update CRNC?

– A Local Cell came up at Node B (Existing)– A Local Cell is to be deleted at Node B (Not Existing)– A Local Cell changed its capabilities and/or its resource operational state– Capabilities of a Local Cell have changed– Common physical and/or transport channels have changed their

capabilities– A Communication Control Port changes its resource operational state– A Local Cell Group has changed its capability

56

CRNC Node B

RESOURCE STATUS INDICATION


Presenter

Presentation Notes

8.2.15

Measurement On Common Resources

NBAP Common ProceduresCommon Measurement Initiation

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

58

CRNC Node B

COMMON MEASUREMENT INITIATIONREQUEST

COMMON MEASUREMENT INITIATIONRESPONSE


Presenter

Presentation Notes

8.2.8


Node B initiates Common Measurement Reporting Procedure How to report the measurement? IE: Report Characteristics

– On Demand– Periodic ( IE: Report Periodicity )– Event A: above threshold and stays for hysteresis time– Event B: below threshold and stays for hysteresis time– Event C: rises by threshold amount within requested time– Event D: falls by threshold amount within requested time– Event E: start when A, wait for B and then terminate– Event F: start when B, wait for A and then terminate

Successful Outcome: COMMON MEASUREMENT INITIATION RESPONSE

Node B uses the same Measurement ID as provided in request


Presenter

Presentation Notes

8.2.8 3 Assisting IEs in Report Characteristics are: Measurement Threshold 1 (2 optional) Measurement Hysteresis Time Report Periodicity If the Report Characteristics IE is set to "On Demand" and if the SFN IE is not provided, the Node B shall return the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [25]).


Unsuccessful Outcome: COMMON MEASUREMENT INITIATION FAILURE

Node B uses the same Measurement ID as provided in request Appropriate Cause is sent to CRNC

60

CRNC Node B

COMMON MEASUREMENT INITIATIONREQUEST

COMMON MEASUREMENTINITIATION FAILURE


Presenter

Presentation Notes

8.2.8 Radio Network Layer Cause: -Measurement not supported for the object. -Measurement Temporarily not Available

CRNC Node B

COMMON MEASUREMENT REPORT

NBAP Common ProceduresCommon Measurement Reporting

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)

IE: Measurement Recovery Report Indicator (optional)– Node B indicated Measurement Available to CRNC when achieved

measurement accuracy fulfills the requested measurement accuracy


Presenter

Presentation Notes

8.2.9

NBAP Common ProceduresCommon Measurement Termination

Message: COMMON MEASUREMENT TERMINATION REQUEST

Node B terminates reporting of common measurements corresponding to the received Measurement ID

62

CRNC Node B

COMMON MEASUREMENT TERMINATIONREQUEST


Presenter

Presentation Notes

8.2.10

NBAP Common ProceduresCommon Measurement Failure

Message: COMMON MEASUREMENT FAILURE INDICATION Reason: A previously requested measurement can no longer be

reported Node B locally terminates the indicated measurement

63

CRNC Node B

COMMON MEASUREMENT FAILUREINDICATION


Presenter

Presentation Notes

8.2.11

NBAP Dedicated Procedures

NBAP Dedicated Procedures The main NBAP Dedicated procedures are as follows

– Function: Radio Link Management Radio Link Addition Synchronized / Unsynchronized Radio Link Reconfiguration Radio Link Deletion

– Function: Radio Link Supervision Radio Link Failure Radio Link Restoration

– Function: Downlink Power Control [FDD]

– Function: Measurement on Dedicated Resources Dedicated Measurement Initiation Dedicated Measurement Reporting Dedicated Measurement Termination Dedicated Measurement Failure


Radio Link Management

NBAP Dedicated ProceduresRadio Link Addition

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 Similarity with RADIO LINK SETUP REQUEST IE: RL Information (parameters of the new RLs to be setup)

67

CRNC Node B

RADIO LINK ADDITION REQUEST

RADIO LINK ADDITION RESPONSE


Presenter

Presentation Notes

8.3.1


Radio Link Handling: Diversity Combination Control– Should Node B combine the new RL with existing RL?– IE: Diversity Control Field (values: May, Must, Must Not)

Radio Link Handling: DL Power Control– What is the transmission power in each DL DPCH?– IE: Initial DL Transmission Power

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


Presenter

Presentation Notes

8.3.1 If all requested RLs are successfully added, the Node B shall respond with a RADIO LINK ADDITION RESPONSE message. After sending the RADIO LINK ADDITION RESPONSE message, the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface. For each RL for which the Delayed Activation IE is not included in the RADIO LINK ADDITION REQUEST message, the Node B shall: -[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].] -[TDD - start transmission on the new RL immediately as specified in TS 25.427 [16].] For each RL for which the Delayed Activation IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall: -if the Delayed Activation IE indicates "Separate Indication": -not start any DL transmission for the concerned RL on the Uu interface; -if the Delayed Activation IE indicates "CFN": -[FDD - start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.] -[TDD - start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]


Unsuccessful Outcome: RADIO LINK ADDITION FAILURE Establishment of at least one of the Radio Links unsuccessful Appropriate Cause is sent to CRNC

69

CRNC Node B

RADIO LINK ADDITION REQUEST

RADIO LINK ADDITION FAILURE


Presenter

Presentation Notes

8.3.1 Radio Network Layer Cause -Combining not supported -Combining Resources not available -Requested Tx Diversity Mode not supported -UL SF not supported -DL SF not supported -Reconfiguration CFN not elapsed -CM not supported -[FDD - DPC Mode change not supported] -Delayed Activation not supported -[FDD - Continuous Packet Connectivity DTX-DRX operation not available] -[FDD - Continuous Packet Connectivity UE DTX Cycle not available] -[FDD - MIMO not available] -[FDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD - Multi Cell operation not available.] -[1.28Mcps TDD- MIMO not available] -[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD - TX diversity for MIMO UE on DL Control Channels not available] -[FDD – Single Stream MIMO not available] -[FDD - Multi Cell operation with MIMO not available.] -[FDD - Multi Cell operation with Single Stream MIMO not available.] -[FDD - Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available] -[FDD - Multi Cell E-DCH operation not available] -[FDD – Frequency Specific Compressed mode operation not available] -[FDD - UL CLTD operation not available] -[FDD - MIMO with four transmit antennas not available] -[FDD - Dual Stream MIMO with four transmit antennas not available] -[FDD – Multiflow operation not available] -[FDD - SixtyfourQAM UL operation not available] -[FDD – UL MIMO operation not available] -[FDD – UL MIMO and SixteenQAM operation not available] -[FDD – UL MIMO and SixtyfourQAM operation not available] Transport Layer Cause -Transport Resources Unavailable Miscellaneous Cause -O&M Intervention -Control processing overload -HW failure

Quiz

Is the Dedicated Radio Link Setup a NBAP Common procedure or a NBAP Dedicated procedure?

70

Note: There is a Common NBAP Channel as well as a Dedicated NBAP Channel


Presenter

Presentation Notes

On the Iub interface, establishment of the first dedicated RL is considered as a NBAP common procedure i.e. all the signaling messages are exchanged via the Node B Control Ports. After the first RL is established the Node B will have a ‘Node B Communication Context’ for the UE identified by the ‘Node B Communication Context ID’. So, further procedures related to that UE will be part of NBAP dedicated procedures i.e. all the signaling messages are exchanged via the Node B Communication Control Ports.

CRNC Node B

RADIO LINK RECONFIGURATION PREPARE

RADIO LINK RECONFIGURATION READY

NBAP Dedicated ProceduresSynchronized Radio Link Reconfiguration

CRNC requests new configuration of RL(s) related to an existing Node B Communication Context

Reconfiguration happens in two steps Reconfiguration Prepare Reconfiguration Commit

Initiating Message: RADIO LINK RECONFIGURATION PREPARE

Handling DCHs IE: DCHs to Modify (1..m) IE: DCHs to Add (1..m) IE: DCHs to Delete (1..m)


Presenter

Presentation Notes

8.3.2


DL Power Control IE: DL Reference Power

Handling Physical Channels IE: UL DPCH Information (new Uplink Scrambling Code, UL SIR target) IE: DL DPCH Information (new DL DPCH Power, DL DPCH Slot Format)

Signaling Bearer Management IE: Signaling Bearer Request Indicator (Node B allocates new

Communication Control Port) HS-DSCH Setup and HS-DCSH Modification IE: HS-DSCH Information(O) and HS-DSCH Information To

Modify(O) Handling Radio Links IE: RL Information (O)


Presenter

Presentation Notes

8.3.2 Signaling bearer rearrangement: If the RADIO LINK RECONFIGURATION PREPARE message includes the Signaling Bearer Request Indicator IE the Node B shall allocate a new Communication Control Port for the control of the Node B Communication Context and include the Target Communication Control Port ID IE in the RADIO LINK RECONFIGURATION READY message.


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


Presenter

Presentation Notes

8.3.2


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

The Prepared Reconfiguration is removed from Node B

74

CRNC Node B

RADIO LINK RECONFIGURATION COMMIT


Presenter

Presentation Notes

8.3.3

NBAP Dedicated ProceduresUnsynchronized Radio Link Reconfiguration

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

75

CRNC Node B

RADIO LINK RECONFIGURATION REQUEST

RADIO LINK RECONFIGURATION RESPONSE


Presenter

Presentation Notes

8.3.5


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


Presenter

Presentation Notes

8.3.5


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

77

CRNC Node B

RADIO LINK RECONFIGURATION REQUEST

RADIO LINK RECONFIGURATION FAILURE


Presenter

Presentation Notes

8.3.5 Radio Network Layer Cause -CM not supported -[FDD - Continuous Packet Connectivity DTX-DRX operation not available] -[FDD - Continuous Packet Connectivity UE DTX Cycle not available] -[FDD - MIMO not available] -E-DCH MAC-d PDU Size Format not available -[FDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD - Multi Cell operation not available.] -[1.28Mcps TDD - MIMO not available] -[1.28Mcps TDD - SixtyfourQAM DL and MIMO Combined not available] -[FDD – Single Stream MIMO not available] -[FDD - Multi Cell operation with MIMO not available] -[FDD - Multi Cell operation with Single Stream MIMO not available] -[FDD - Multi Cell E-DCH operation not available] -[FDD - UL CLTD operation not available] -[FDD - MIMO with four transmit antennas not available] -[FDD - Dual Stream MIMO with four transmit antennas not available] -[FDD – Multiflow operation not available] -[FDD - SixtyfourQAM UL operation not available] -[FDD – UL MIMO operation not available] -[FDD – UL MIMO and SixteenQAM operation not available] -[FDD – UL MIMO and SixtyfourQAM operation not available] Transport Layer Cause -Transport Resources Unavailable Miscellaneous Cause -O&M Intervention -Control processing overload -HW failure

NBAP Dedicated ProceduresRadio Link Deletion

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

78

CRNC Node B

RADIO LINK DELETION REQUEST

RADIO LINK DELETION RESPONSE


Presenter

Presentation Notes

8.3.6

Radio Link Supervision

NBAP Dedicated ProceduresRadio Link Failure

Message: RADIO LINK FAILURE INDICATION Reason: One or more established RLs have failed IE: RL Information One or more individual Radio Link(s) failed

IE: RL Information Set One or more Radio Link Set(s) failed

RL failure might cause loss of UL sync as well Appropriate Cause is sent to CRNC

80

CRNC Node B

RADIO LINK FAILURE INDICATION


Presenter

Presentation Notes

8.3.12 Radio Network Layer Causes: -Synchronization Failure -Invalid CM settings Transport Layer Causes: -Transport Resources Unavailable Miscellaneous Causes: -Control Processing Overload -HW Failure -O&M Intervention -Not enough user plane processing resources

NBAP Dedicated ProceduresRadio Link Restoration

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

IE: RL Information Set One or more Radio Link Set(s) re-established

This is triggered when UL synchronization detection algorithm finishes successfully and indicates that UL sync exists

81

CRNC Node B

RADIO LINK RESTORE INDICATION


Presenter

Presentation Notes

8.3.13 Please refer to TS 25.214 [10] and TS 25.224 [21] for UL synchronization algorithm.

Radio Link Establishment ProcedureComplete Picture


Presenter

Presentation Notes

8.3.13 Please refer to TS 25.214 [10] and TS 25.224 [21] for UL synchronization algorithm.

Downlink Power Control

NBAP Dedicated ProceduresDownlink Power Control [FDD]

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

IE: Inner Loop DL PC Status (optional) Values: Active / Inactive

84

CRNC Node B

DL POWER CONTROL REQUEST


Presenter

Presentation Notes

8.3.7 The Power Adjustment Type IE defines the characteristic of the power adjustment. If the value of the Power Adjustment Type IE is "Common", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Common". As long as the Power Balancing Adjustment Type of the Node B Communication Context is set to "Common", the Node B shall perform the power adjustment (see below) for all existing and future radio links associated with the context identified by the Node B Communication Context ID IE and use a common DL reference power level. If the value of the Power Adjustment Type IE is "Individual", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "Individual". The Node B shall perform the power adjustment (see below) for all radio links addressed in the message using the given DL Reference Powers per RL. If the Power Balancing Adjustment Type of the Node B Communication Context was set to "Common" before this message was received, power balancing on all radio links not addressed by the DL POWER CONTROL REQUEST message shall remain to be executed in accordance with the existing power balancing parameters which are now considered RL individual parameters. Power balancing will not be started on future radio links without a specific request. If the value of the Power Adjustment Type IE is "None", the Power Balancing Adjustment Type of the Node B Communication Context shall be set to "None" and the Node B shall suspend on going power adjustments for all radio links for the Node B Communication Context. If the Inner Loop DL PC Status IE is present and set to "Active", the Node B shall activate inner loop DL power control for all radio links for the Node B Communication Context. If the Inner Loop DL PC Status IE is present and set to "Inactive", the Node B shall deactivate inner loop DL power control for all radio links for the Node B Communication Context according to ref. TS 25.214 [10].

Measurement On Dedicated Resources

NBAP Dedicated ProceduresDedicated Measurement Initiation

Message: DEDICATED MEASUREMENT INITIATION REQUEST Which dedicated resources to perform the measurement on? IE: Node B Communication Context ID

How to keep track? IE: Measurement ID

What to measure? IE: Dedicated Measurement Object Type IE: Node B Communication Context ID

86

CRNC Node B

DEDICATED MEASUREMENT INITIATIONREQUEST

DEDICATED MEASUREMENT INITIATIONRESPONSE


Presenter

Presentation Notes

8.3.8 The Dedicated Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1 except when the Node B Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC". If the Node B Communication Context ID IE in the DEDICATED MEASUREMENT INITIATION REQUEST message is set to the reserved value "All NBCC", the Dedicated Measurement Initiation procedure may be initiated by the CRNC at any time when the Node B Communication Context exists.


Dedicated Measurement Object Type can be– RL: All indicated Radio Links (IE: RL Information)– RLS: All indicated Radio Link Sets (IE: RL Set Information)– ALL RL: All current and future Radio Links within the Node B

Communication Context– ALL RLS: All current and future Radio Link Sets within the Node B

Communication Context

Special case: ALL NBCC– If Node B Communication Context ID is set to ALL NBCC then

measurement is applied on all current and future Node B Communication Contexts controlled via the Communication Control Port on which the request is received


Presenter

Presentation Notes

8.3.8


Node B initiates Dedicated Measurement Reporting procedure How to report? IE: Reporting Characteristics Values are similar to the Common Measurement Reporting procedure

(On Demand, Periodic, A, B, C, D. E, F)

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


Presenter

Presentation Notes

8.3.8


Unsuccessful Outcome: DEDICATED MEASUREMENT INITIATION FAILURE

Node B uses the Measurement ID as received in request Appropriate Cause is sent to CRNC

89

CRNC Node B

DEDICATED MEASUREMENT INITIATIONREQUEST

DEDICATED MEASUREMENT INITIATIONFAILURE


Presenter

Presentation Notes

8.3.8 Radio Network Layer cause -Measurement not supported for the object -Measurement Temporarily not Available Miscellaneous Cause -O&M Intervention -Control processing overload -HW failure

NBAP Dedicated ProceduresDedicated Measurement Reporting

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

90

CRNC Node B

DEDICATED MEASUREMENT REPORT


Presenter

Presentation Notes

8.3.9

NBAP Dedicated ProceduresDedicated Measurement Termination

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

91

CRNC Node B

DEDICATED MEASUREMENTTERMINATION REQUEST


Presenter

Presentation Notes

8.3.10

NBAP Dedicated ProceduresDedicated Measurement Failure

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

92

CRNC Node B

DEDICATED MEASUREMENT FAILUREINDICATION


Presenter

Presentation Notes

8.3.11

Questions and Answers

Thank You

nodeb application part

Documents

radio resources

status of node b resources

node b application

dedicated resources

radio links

nbap elementary procedures

cell configuration information

nodeb nbap protocol