WCDMA RAN12.0 Version Feature 20091230 B 1.0

www.huawei.com

Security Level: Internal Use

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

RAN12 Version Feature

Introduction

Wireless Product Service Department– WRAN Team

ISSUE1.0

2009-05

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2

Upon completion this course, you will be able to:

Know RAN12 version objectives and roadmap;

Master new features and implementation schemes of

RNC/NodeB in RAN12 version


《 BSC6900 V9R012C00 Release Notes 》《 BSC6800 V1R012C00 Release Notes 》《 NodeB V200R012C00 Release Notes 》《 RAN12 Feature Sales Guide 》《 RAN12 PDCP Report Materials 》


Chapter 1 Version Introduction

Chapter 2 Feature Description


RAN Version Roadmap

• In RAN12.0, the key features are HSPA+Ph2, IC and FDE which

improve UL/DL broadband capability, enhance in green energy,

maintenance efficiency, user experience, transmission scheme and

emergency communication.

• RAN12.0 mainly include soft features and only new base band ASIC

board is necessary when IC feature is used.

HSDPA Phase4

HSUPA Phase2

MBMS Phase2

CCPIC

RNC resource pool

HSPA+ Phase1

VoIP phaseI

RNC backup

Green Energy

IP transmission

enhancement

CS over HSPA+

HSPA+ Phase2

Advanced Receiver

IC

Green Energy

enhancement

OAM enhancement

EOS enhancement

2009.12-2010.3 2009Q1 2008Q2

RAN 12.0 RAN 11.0 RAN 10.0

HSPA+ Phase3

SON

FA

2010-2011

RAN 13.0


RAN12 Version Objectives

New Feature

HSPA+Phase2 IC FDE DC 64QAM+MIMO

HSPA+ high-speed Service

Mobility management between UMTS and LTE

Data service QoS management

Improve broadband capability and use experience for customer network

Decrease TCO of customer

Enhance product competition capability

Improve maintenance efficiency and reduce maintenance costs

ProfitNew Solution


Products Description

Items Description

Products BSC 6800V100R012/

BSC6900V900R012、 DBS3900/BTS3900/BTS3900A/BTS390

0L V200R012、 DBS3800/BTS3812E/BTS3812A V100R012

Protocol

Version3GPP R8 (2009.3)， back compatible with R7、 R6、 R5、R4 and R99

Main Feature Inherit the RAN11 function and the new features as follow:

1. UMTS LTE mutual operation

2. HSPA+ Phase2—— IC

3. HSPA+ Phase2—— 64QAM+MIMO

4. HSPA+ Phase2—— UL L2 enhancement

5. HSPA+ Phase2—— UL 16QAM

6. HSPA+ Phase2—— DC-HSDPA

7. FDE


Chapter 1 Version Introduction

Chapter 2 Feature Description


Mobility Management Between UMTS and LTE in Phase 1

Description With the mobility management between UMTS and LTE, in phase 1:A UE can hand over to or reselect a UMTS network from a LTE network.A UE in the idle state can reselect a LTE network from a UMTS network.The procedure in which the UE reselects a UMTS network from a LTE network is the same as the procedure in which the UE reselects a UMTS network from a GSM network. Therefore, the RNC supports a UE to reselect a UMTS network from a LTE network by nature.

Improvement The UMTS network broadcasts the system information related to LTE so that a UE in the idle state will reselect a LTE cell in preference.PS services can be handed over from LTE to UMTS.

Implementation Broadcast of system informationThe RNC supports system information block 19. LTE frequency information is broadcast through the system information block 19 to notify UEs of the priority and reselection quality threshold of the adjacent LTE frequency. Based on the information, a UE in the idle state can reselect the LTE network.Handover of PS service from LTE to UMTSAfter receiving a PS handover request from the LTE network, the RNC allocates resources to the requesting UE and instructs the core network to initiate the handover. In this way, the UE can hand over from the LTE network to the UMTS network, without interrupting the PS service.


HSUPA Uplink Interference Cancellation

Description HSUPA UL Interference Cancellation (IC) is performed to cancel the interference caused by the UL high rate EDPDCH data to improve the demodulation signal-to-noise ratio (SNR) and thus to increase the UL system capacity of the network.

Improvement The introduction of the IC technology significantly improves the UL capacity of the UMTS. In certain scenarios, the gain of the IC technology is significant. For example, if the system needs to support a small number of HSUPA users with high throughput and a large number of HSUPA users with low throughput, the IC is required to cancel the uplink interference brought by HSUPA users with high throughput. Without the IC technology, the high UL interference may be generated from the high speed HSUPA users. In such a case, if the rate of the original high rate HSUPA users must be guaranteed, the number of low speed users, for example, VoIP users must be limited. Otherwise, the original high speed HSUPA users may be affected, the speed of services may decrease to the minimum

Implementation

The IC technology supports different categories of HSUPA users, including UEs of categories 1 to 7. The principle of the IC technology is that the receiver of the NodeB demodulates the HSUPA data on the UL EDPDCH and reconstructs the baseband data based on the demodulated data and received baseband data. The NodeB then demodulates the reconstructed baseband data. For the reconstructed baseband data, the interference from the reconstructed EDPDCH data is eliminated and the colored noise in the cell caused by the self-interference feature of the UMTS is reduced. Therefore, the SNR of the reconstructed data is improved.


DC-HSDPA

Description When Dual Carrier-HSDPA (DC-HSDPA) is enabled, the downlink connections can be established simultaneously between the UE and two inter-frequency co-coverage cells that are configured with consecutive frequencies and controlled by the NodeB. The two cells can schedule the UE simultaneously, thus increasing the downlink peak throughput of the UE. When the UE is located at the edge of a cell, the gain of its downlink peak throughput becomes greater.

Improvement The DC-HSDPA helps to increase the throughputs of a single UE and a cell.

Increasing the throughput of a single UE

Owing to the application of DC-HSDPA, the throughputs of the UE at both the

center and edge of the cell are doubled. If the DC-HSDPA is used together

with 64QAM, the throughput of the UE at the center of a cell can reach 42

Mbit/s theoretically.

Increasing the throughput of a cell

Owing to the application of DC-HSDPA, the total throughputs of the two inter-

frequency co-coverage cells are increased by 5% to 10%. The gain of the

throughput is inversely proportional to the number of the UEs in a cell.


DC-HSDPA（ Dual Cell - HSDPA）Implementation

The RNC checks whether the UE and cells support DC-HSDPA. When DC-HSDPA is required, the RNC configures two radio links to the NodeB by using the Iub signaling RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and RADIO LINK RECONFIGURATION PREPARE and the RNC configures two radio links to the UE by using Uu signaling RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, ACTIVE SET UPDATE, PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, CELL UPDATE CONFIRM. Then, the downlink connections between the UE and two inter-frequency co-coverage cells can be established so that DC-HSDPA can be applied.

Cell A

UL DPCH

UL E-DPCCH/E-DPDCH

DL DPCH(F-DPCH)

UL HS-DPCCH

Cell B

Supplementary Carrier DL HS-SCCH/HS-PDSCH

Anchor Carrier DL HS-SCCH/HS-PDSCH


TCP Accelerator Enhancement

Description In RAN11.0, the Downlink TCP accelerator feature is implemented,

which helps optimize the downlink data transmission.

Based on RAN11.0, the Uplink TCP accelerator feature in RAN12.0

helps accelerate the slow start and recovery of uplink data

transmission through the spilt ACK technique. In this way, the impact

of packet loss on the uplink TCP data transmission is reduced.

Improvement The slow start and recovery of uplink packet transmission at the UE is

accelerated.

The performance of uplink TCP data transmission is improved, and

thus the user experience is also improved.

Implementation The TCP accelerator processes TCP/IP packets with the following

technologies:

Uplink TCP packet sorting.

Downlink split ACK for accelerating slow start and packet transmission at

the UE.

This feature in RAN12.0 is controlled by license as it is in RAN11.0.


Uplink Layer 2 Enhancement

Description With the uplink layer 2 enhancement feature enabled, the data of a flexible Protocol Data

Unit (PDU) size can be transmitted according to the radio transmission environment on the

Uu interface.

When the UE is at the edge of a cell, the data of a small PDU size is transmitted to prevent

the increase of bit error rate (BER) caused by the limited power, so that the data

transmission efficiency is improved.

When the UE is in the center of the cell, the data of a large PDU size is transmitted to meet

the requirement for high data rate and realize the higher data transmission efficiency, so

that the throughput of the system is improved.

Improvement The uplink layer 2 enhancement feature can effectively improve the throughput of a single

user and the throughput of the cell.

Throughput of a single user

When the UE is in the center of the cell, the data of a great PDU size is transmitted on the

radio link layer to meet the requirement for high rate. When the UE is at the edge of the cell,

the data of a small PDU size is transmitted on the radio link layer to reduce the BER caused

by the limited power. In this manner, the throughput of a single user is improved.

Throughput of the cell

The data of different PDU sizes is transmitted in accordance with the data transmission

capability on the Uu interface when the UE is at different locations of a cell. In this way, the

resources on the Uu interface can be utilized optimally and the throughput of the cell can be

improved.


Uplink Layer 2 Enhancement

Implementation

The RNC obtains the information about whether the UE and cell support the

uplink layer 2 enhancement function. If the function can be enabled, the RNC

configures the NodeB through the signaling messages RADIO LINK SETUP

REQUEST, RADIO LINK ADDITION REQUEST, and RADIO LINK

RECONFIGURATION PREPARE on the Iub/Iur interface so that the NodeB

supports uplink layer 2 enhancement. Moreover, the RNC configures the UE

through the signaling messages RADIO BEARER SETUP and RADIO

BEARER RECONFIGURATION on the Uu interface so that the UE supports

uplink layer 2 enhancement. In this manner, the data of an optimal PDU size

is transmitted on the radio link.


UL 16QAM

Description A higher order modulation is introduced based on the Release 7 HSUPA, that is,

the uplink modulation is upgraded from QPSK to 16QAM.

Improvement The throughput of a single user and the throughput of a cell can be improved

through 16QAM.

Throughput of a single user

The uplink throughput of a single user can reach 11 Mbit/s when the channel

quality is good.

Throughput of a cell

The throughput of a cell is increased by 35% to 50%.

Implementation The RNC obtains the information about whether the UE and cell support UL 16QAM. If

the RNC determines that the current service requires UL 16QAM, it sends the

information about the configuration of UL 16QAM to the NodeB through the signaling

RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and RADIO

LINK RECONFIGURATION PREPARE over the Iub interface, and to the UE through

the signaling RADIO BEARER SETUP, TRANSPORT CHANNEL

RECONFIGURATION, ACTIVE SET UPDATE, PHYSICAL CHANNEL

RECONFIGURATION, RADIO BEARER RECONFIGURATION, and CELL UPDATE

CONFIRM over the Uu interface.


64QAM+MIMO

Description Due to the limited UE capability, 64QAM cannot be used with MIMO together, according to the R7

protocol. With the further development of UEs, the HS-DSCH with categories 19 and 20 is

supported,

according to the R8 protocol. In this case, 64QAM can be used with MIMO simultaneously, thus

improving the downlink peak rate for each user.

Improvement The 64QAM+MIMO helps to increase the peak throughputs of a single UE.

The downlink peak rate for each user can reach 21 Mbit/s when only 64QAM is used.

The downlink peak rate for each user can reach 28 Mbit/s when only MIMO is used.

With the application of 64QAM+MIMO, the peak rate for each user is greatly increased, up to

42 Mbit/s theoretically.

Implementation Depending on whether the UE or the cell supports 64QAM+MIMO, the RNC determines whether to

allow 64QAM+MIMO for the ongoing service. If the feature is allowed, the RNC sends the HS-DSCH

category and configuration data for MIMO and 64QAM to the NodeB through the following messages

over the Iub interface: RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and

RADIO LINK RECONFIGURATION PREPARE. Then, the NodeB determines whether to apply

64QAM+MIMO. After the NodeB informs the RNC of the application of 64QAM+MIMO, the RNC

sends configuration data for MIMO and 64QAM to the UE through the following messages over the

Uu interface: RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, ACTIVE

SET UPDATE 、 PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER

RECONFIGURATION, RADIO BEARER RELEASE, and CELL UPDATE CONFIRM. In addition, the

downlink enhanced L2 function is applied together.


Fast Dormancy

Description According to CR 25.331_CR3483R2, after the UE that supports fast dormancy

finishes transmitting data, the UE will send the RNC a message, indicating that the

data transmission is complete. On receiving the message, the RNC releases the

Radio Resource Control (RRC) connection and the UE enters the idle state. In this

way, power and network resources are saved.

Improvement The UE enters low-power mode immediately. Thus, the battery power of the UE is

saved and the network resource utilization is improved.

Implementation 1. The RNC sends SYSTEM INFORMATION (Type 1) that carries T323 to the UE,

informing the UE to enable fast dormancy. After the UE checks that no PS data

is transmitted, it sends to the RNC the SIGNALLING CONNECTION RELEASE

INDICATION message with the cause value "UE Requested PS Data session

end." On receiving the message, the RNC releases the call, and the UE enters

low-power mode.

UE RNC

SYSTEM INFORMATION (Type 1 T323)

SIGNALLING CONNECTION RELEASE INDICATION

(UE Requested PS Data session end)

RRC CONNECTION RELEASE


Fast Dormancy

Implementation 2. In the process of relocation, the RNC sends to the UE the UTRAN

MOBILITY INFORMATION message that carries T323 if T323 is valid.

UE TRNC SRNC CN

SRNC迁移准备和迁移执行过程

UTRAN MOBILITY INFORMATION CONFIRM

UTRAN MOBILITY INFORMATION (T323)


Adjustment of CS Voice over HSUPA TTI

Description The CS Voice over HSUPA TTI is dynamically adjusted from 2 ms to 10 ms.

Improvement For the UE handling CS Voice over HSUPA at the cell edge, the TTI is adjusted from

2 ms to 10 ms. Thus, a wider coverage can be provided, QoS can be ensured, and

call drops can be avoided.

Implementation A parameter DRA_VOICE_TTI_RECFG_SWITCH is added to control whether the

TTI for CS Voice over HSUPA can be dynamically adjusted.

1. Measurement delivery

For the CS Voice over 2 ms HSUPA TTI, the RNC sends a message to the UE,

requesting the measurement of the UE transmit power.

2. Measurement release

When the current service is not CS Voice over 2 ms HSUPA TTI, the RNC releases

the measurement of the UE transmit power.

3. Handling of the measurement report

On receiving the event 6A concerning the transmit power from the UE, the RNC

triggers the adjustment of TTI for CS Voice over HSUPA from 2 ms to 10 ms.


Enhanced Multiband Management

Description In a multiband network, the cells that operate on different frequency bands have different coverage

areas. Call drops are likely to occur if a blind handover is performed for the UE between these

cells.

The handover success rate can be increased if handover decisions are made according to the

signal quality measurement result.In a single-band network, the cells that operate at different

layers

have discontinuous coverage areas. Similar to the situations in a multiband network, call drops are

likely to occur in a single-band network if a blind handover is performed for the UE between the

cells at different layers. The handover success rate can also be increased if handover decisions

are

made according to the signal quality measurement result.When a measurement-based handover is

required for traffic steering or load sharing, signal quality measurement should be performed and

then handover decision can be made.

Improvement With this feature, traffic steering or load sharing can be implemented between inter-frequency cells

based on the measurement result, thus increasing the resource utilization while ensuring the

handover success rate. This feature is applicable to the following types of network structure:

1.The cells operating on different frequency bands have different coverage areas, and the

coverage

areas of the cells at different layers may overlap each other.

2. The cells operating on different frequency bands have different coverage areas, and the

coverage areas may be discontinuous.

3. The cells operating on the same frequency band but at different layers may have discontinuous

coverage areas.


Enhanced Multiband Management

Implementation

Traffic steering based on measurement result:

Each cell is configured with the priorities for each type of service (R99 RT, R99 NRT,

HSPA, and others). After the RAB setup (RAB modification or RAB reconfiguration) is

complete or the UE moves, the RNC determines whether a cell with a higher priority

exists according to the UE capability, cell capability, RNC switch, license configuration,

and inter-frequency neighboring cell configuration. If such a cell exists, the RNC

notifies the UE to perform inter-frequency signal quality measurement. Based on the

measurement result reported by the UE, the RNC moves the UE to the highest-priority

cell whose signal quality meets the requirements.

Load sharing based on measurement result:

After the RAB is set up, load reshuffling (LDR) may trigger a load-based inter-

frequency handover. The target cell is selected on the basis of the quality

measurement of cells. Only the cell that meets the quality requirement is selected.

This avoids signal quality deterioration or call drops after the UE is handed over to the

target cell.


Quality Improvement for Subscribed Service

Description This feature enables the adjustment of Service Priority Identification (SPI) of

downlink services by identifying the IP data flow, and thus to adjust the user

scheduling priority. The services that the operator requires most, for example, the

HTTP service or the service of a server specified by the operator, can be

preferentially scheduled to ensure the bandwidth for the services. Moreover, the

scheduling priority of the free-of-charge services that demand large amount of

bandwidth can be lowered so that the bandwidth for the services can be used by

other services of high priorities.

Improvement When the Uu resources are limited, the resources are preferentially allocated to the

services of high priorities, for example, HTTP service or the service of a server

specified by the operator. In this manner, the user experience can be improved and

the operator can provide various services for subscribers.

Implementation The triplet of source IP address, source port number, and protocol type of the

downlink IP packet is parsed to determine whether the IP packet is the IP data flow

that is specified by the operator. If yes, the user scheduling priority is adjusted in

accordance with the triplet configured by the operator.


DPU board replacement not disrupting ongoing services

Description With the introduction of this feature, ongoing services on the dedicated channel are not

disrupted at the RNC side when user plane boards (DPUb/DPUe boards) need to be

replaced. The DPUb/DPUe board needs to be replaced when it is faulty or the DSP on

the board is faulty. In this case, this board can be inhibited through the related MML

command, and then new service establishment request is not handled on this board. In

addition, the established common channels are re-established through other

DPUb/DPUe boards.

Improvement With this feature,

The maintenance personnel can replace a faulty DPUb/DPUe board in time, but

not at midnight when traffic is low.

The ongoing services handled on the faulty board can be free from being

disrupted.


DPU board replacement not disrupting ongoing services

Implementation 1. When the faulty DPUb/DPUe board is inhibited logically, new services are

established through other DPUb/DPUe board. The dedicated channel services

handled by the faulty DPUb/DPUe board, however, are not affected.

2. When the faulty DPUb/DPUe board is inhibited logically, the established common

channels are re-established through other DPUb/DPUe boards. In this process, the

common channel services handled by the faulty DPUb/DPUe board are released. If

the remaining resources on other DPUb/DPUe boards are insufficient to re-establish

all the common channels for the faulty board, only some common channels are re-

established.

3. The maintenance personnel can use the MML command DSP UDSPRESOURCE

to query the real-time data, such as the number of CS users, total number of users,

number of cells, and cell IDs. In this way, the maintenance personnel can replace

the faulty DPUb/DPUe board when the services carried on the board is low, thus

reducing the impact on services.


Single IP address for the NodeB

Description The IP addresses of the NodeB consist of the control plane IP address, user plane IP address, and NodeB OM IP address. Currently, typical application is that the control plane IP address and user plane IP address are configured to use the same port IP address. The OM IP address and user plane IP address should be assigned with two different IP addresses belonging to different IP subnets. Therefore, operators need to plan two sets of IP addresses and routing rules during network deployment. With the introduction of single IP address for the NodeB, the traffic channel and OM channel are enabled to share one IP address.

Improvement With the introduction of single IP address for the NodeB, the traffic channel and OM channel are enabled to share one IP address. In this way, more IP address resources are saved and IP route configuration is simplified when IP transport is adopted.

Implementation

1.When a BTS3900/BTS3900A/DBS3900 is configured with one WMPT and the WMPT provides one or more IP ports, the OM IP address can be the same as one of the port IP addresses. When using redundancy configuration for OM channels, the two OM IP addresses can be the same as those of the two ports provided by the WMPT.2.When a BTS3900/BTS3900A/DBS3900 is configured with one WMPT and multiple UTRPs and the WMPT or UTRP provides one or more IP ports, the OM IP address of the NodeB can be the same as one of the port IP addresses. When using redundancy configuration for OM channels, the two OM IP addresses can be the same as those of the two IP ports provided by the WMPT. The two OM IP addresses are not allowed to be the same as those of two IP ports provided by the UTRP.3.A BTS3900/BTS3900A/DBS3900 is configured with multiple ports (E1/T1/Ethernet), and the ports can be combined as one IP interface through Ethernet Trunk and MLPPP. If the IP port is located on the WMPT, the OM IP address can be the same as that of the combined IP port.


Management and monitoring of the solar equipment

Description The solar power system supplies the power produced by solar array to the load. The surplus power is stored in the batteries. The solar power system runs under the control of the solar controller.

Improvement This feature improves the operability and maintainability of the NodeB and solar equipment, which enables a much greener NodeB.

Implementation 1 、 The solar controller, like the traditional power monitoring device, is managed as the PMU. The configuration, maintenance, and status monitoring of the solar controller are performed through the 485 serial port by the NodeB.2 、 The ADD PMU command is used to add the solar controller to the NodeB configurations. The commands for the PMU are used to configure and maintain the solar controller.


HSUPA Uplink Frequency Domain Balancing

Description With the HSUPA uplink frequency domain balancing feature, the NodeB uplink receiver balances the spectrum in the frequency domain of the HSUPA E-DPDCH and reduces the inter-path interference of the E-DPDCH.

Improvement The uplink inter-path interference of HSUPA users is reduced, thus helping to enhance a higher peak data rate for HSUPA users.

Implementation The NodeB uplink receiver balances the spectrum in the frequency domain of the HSUPA E-DPDCH and reduces the inter-path interference of the E-DPDCH.


Improvement of Small-Traffic Service Delay Experience

Description The services with small traffic (such as HTTP or Gaming) are distinguished from all the services carried by the HSPA channels. More resources are allocated to such services with small traffic, thus enhancing the delay experience.

Improvement Users can obtain better delay experience when using bursty small-traffic services.

Implementation The bursty data packet size is set according to the user priority. For services whose total data amount does not exceed the defined value are identified as small-traffic services. The resources are preferentially allocated to small-traffic services in HSPA scheduling and flow control, thus optimizing the delay.


2x 2 MIMO

Description 2 x 2 Multiple Input Multiple Output (MIMO) uses two transmit antennas at the NodeB to transmit orthogonal (parallel) data streams to the two receive antennas at the UEs.

Improvement Using two antennas and additional signal processing at the receiver and the transmitter, 2 x 2 MIMO can increase the system capacity and double user data rates without using additional bandwidth. 2 x 2 MIMO adopts different modes in the 3GPP protocols, with QPSK and 16QAM in R7, and later with 64QAM in R8. With dual-stream dual-antenna mode and16QAM modulation, the peak data rate per user is doubled to 28 Mbit/s and also the average throughput of the system is enhanced.

Implementation The 3GPP R7 protocols define the categories of the UEs that support MIMO, and add the information elements (IEs) that support MIMO in the reporting of local cell capability. The RNC determines whether the RL between the NodeB and the UE supports MIMO according to the local cell capability and UE capability reported by the NodeB. If the RL supports MIMO, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use MIMO according to the following aspects:Channel Quality Indicator (CQI) reported by the UEPrecoding Control Indication (PCI)HS-PDSCH code resources and power resources of the NodeB


IP-Based Automatic Address Identification of the NodeB Description In IP mode, Huawei NodeBs have two types of automatic address identification: DHCP

and DHCP+AACP. In practical usage, the RAN system enables different automatic address identification types for different scenarios.The DHCP+AACP type is the enhancement of the NodeB automatic address identification feature.The difference between DHCP and DHCP+AACP is that: In DHCP+AACP mode, one NodeB provides DHCP relay functions for other NodeBs; in DHCP mode, the transmission device in the RAN is required to provide DHCP relay functions for the NodeB.For the IP RAN, not all the networks can provide the network devices with the relay functions. Therefore, the Huawei RAN system introduces DHCP+AACP for such networks.DHCP+AACP is applicable to only the Ethernet transmission.

Improvement

The automatic address identification of the NodeB is implemented when the network devices do not support the DHCP relay functions.

Implementation

When the network devices do not support the DHCP relay function, Huawei RAN system remotely assigns a temporary IP address to a NodeB in the network through the AACP server and sends the AACP detection packet to the subnetwork of the NodeB. Then, one of the NodeBs obtains the AACP detection packet through the ARP mechanism. The temporary IP address is used to communicate with the DHCP server to obtain a formal IP address for the NodeB. When the formal IP address is set, the NodeB can be configured as the DHCP relay of this sub-network, thus helping other NodeBs in the sub-network to perform automatic identification through the DHCP mechanism.

Thank You

www.huawei.com

Date post:	08-Nov-2014
Category:	Documents
Upload:	asojuma
View:	28 times
Download:	1 times

WCDMA RAN12.0 Version Feature 20091230 B 1.0

Documents