Você está na página 1de 15

LTE Network Monitor Mode

Specification v1.01
Femto Forum Technical Document

Document number:
Date issued:
Document Type:

FF_Tech_003_v1.01
12-10-2010
Document for public distribution

Legal Notice
Permitted Use of this document
You are permitted to download, use and distribute copies of this document provided that:
(a) you must only use and distribute this document in its entirety without amendment, deletion or
addition of any legal notice, text, graphics or other content; and
(b) you must not make this document available for download on any publically accessible bulletin
board, website, ftp site or file sharing service.
Disclaimer
This document is provided on an as is basis without guarantees, representations, conditions or
warranties as to its accuracy or completeness or that it is free from error. To the extent permitted by
law, the Femto Forum Ltd and the contributors to this document exclude all representations,
conditions, warranties and other terms which might otherwise be implied by statute, common law or
the law of equity.
Patents
It is possible that use of the technical matter published in this document may require the permission
of the proprietor of one or more patents. You are entirely response for identifying and where
necessary obtaining a licence under such patents should you choose to use any such technical
matter. The Femto Forum Ltd has no responsibility in this regard and shall not be liable for any loss
or damage suffered in relation to an infringement of any third party patent as a result of such use.
Copyright
This document is subject to copyright owned by the Femto Forum Ltd and/or licensed to the Femto
Forum Ltd by its contributing members. You may use and distribute this document free of charge
provided that you comply with the provisions set out in this notice. Other than this limited licence,
you are not granted any further right, interest or title in this document and the Femto Forum Ltd
and/or its contributing members shall at all times remain the sole owner(s) of the copyright in this
document.
Trade Marks
The Femto Forum logo and other logo, trade and service marks contained in this document are the
property of the Femto Forum Ltd and, where applicable, other third parties. You are not permitted
to use or reproduce these marks without the prior written consent of the Femto Forum Ltd or where
applicable the third party owner.

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 2

Table of Contents

1
Table of Contents ............................................................................................................................... 3
2
Document Handling ........................................................................................................................... 4
3
Scope .................................................................................................................................................. 4
4
Interface Overview ............................................................................................................................. 4
5
Functionality Grouping....................................................................................................................... 5
6
Interface Definition ............................................................................................................................ 5
6.1.1
NMM_RSSI_MEAS_REQ Parameters .................................................... 6
6.1.2
NMM_RSSI_MEAS_IND parameters .................................................... 6
6.1.3
NMM_RSSI_MEAS_CNF Parameters .................................................... 6
6.1.4
NMM_STOP_RSSI_MEAS_REQ Parameters ........................................... 6
6.1.5
NMM_CELL_SEARCH_REQ Parameters................................................. 7
6.1.6
NMM_CELL_SEARCH_IND Parameters ................................................. 7
6.1.7
NMM_CELL_SEARCH_CNF Parameters ................................................. 8
6.1.8
NMM_STOP_CELL_SEARCH_REQ Parameters ....................................... 9
6.1.9
NMM_PBCH_CONFIG_REQ Parameters ................................................ 9
6.1.10 NMM_PBCH_CONFIG_CNF Parameters ................................................ 9
6.1.11 NMM_PBCH_DATA_IND Parameters .................................................... 9
6.1.12 NMM_STOP_PBCH_REQ Parameters .................................................. 10
6.1.13 NMM_SIB1_CONFIG_REQ Parameters ............................................... 10
6.1.14 NMM_SIB1_CONFIG_CNF Paramerers ............................................... 10
6.1.15 NMM_BCCH_CONFIG_REQ Parameters .............................................. 10
6.1.16 NMM_BCCH_CONFIG_CNF Parameters .............................................. 11
6.1.17 NMM_BCCH_DATA_IND Parameters .................................................. 11
6.1.18 NMM_STOP_BCCH_REQ Parameters.................................................. 11
7
Parameters ....................................................................................................................................... 12
7.1
CellFoundElement........................................................................................................................ 12
7.2
BcchDataElement......................................................................................................................... 12
7.3
VendorSpecificListElement .......................................................................................................... 12
8
Constants ......................................................................................................................................... 12
9
Scenarios .......................................................................................................................................... 14
9.1
Cell Search ................................................................................................................................... 14
9.2
System Information reading ........................................................................................................ 15
10
References........................................................................................................................................ 15
11
Revision History................................................................................................................................ 15

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 3

Document Handling

This interface specification is planned for public distribution. The inputs by Members are handled
according to paragraph C in the IPR and Confidentiality Policy, with the exception to paragraph C.2.ii that
this document can be distributed publicly once the interface specification has been accepted during the
WG2 plenary meeting.

Scope

This document specifies the Network Monitor Mode (NMM) module for LTE. Support for 3G and 2G is
not in the scope of this document. The goal of this interface specification is to allow a femto cell to support
cell RF self configuration and interference management according to the requirements in [4], which amongst
others include:
carrier and cell id selection
DL TX power setting
UE TX power setting
frequency reference

Interface Overview

The NMM is part of the PHY. The NMM can be accessed through the FAPI. NMM is part of the interface
P4 as shown in Figure 1.
Performance requirements are assumed to be aligned with [2].
Protocol Subsystem (P)

RRM for Rev2+


PDCP/RLC/
MAC

CSC

M1

Scheduler

Network Side
Stacks
Security Layer

auth/encr

OS kernel

OAM

PHY
mode
ctl

Service Discovery

P1

P2

P3

P4

P8

Diag

Serial Port
auth/encr

NWL ctl
&
results

Service Discovery
GPS config/
control

GPIO

GPS
position

P5

main
datapath

P6

SNOW/AES
co-processor
(air-interface
ciphering)

4G PHY

P7

main
datapath
NWL
radio

2G 3G 4G NWL
Ethernet MAC

GPS signal
processing

on-chip peripherals

DSP Subsystem
baseband processor

Figure 1 LTE FAPI overview

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 4

Functionality Grouping

The different functions defined in this interface have different requirements regarding the scope of PHY
implementation needed for NMM. In order to allow for most flexibility the provider of the NMM module
should specify which functional groups are supported by its NMM module. The groupings are defined as
follows:
1. RSSI, RSRP, SYNC, PBCH (requires PHY SYNC,PBCH)
2. BCCH reading (requires complete PHY PDCCH and PDSCH chain incl. turbo decoder)
If the second group is supported the first one is automatically included.

Interface Definition

Primitive name

Reference

Description

NMM_RSSI_MEAS_REQ

6.1.1

Triggers RSSI measurements in the


requested band. Optionally a list of
carriers can be configured.

NMM_RSSI_MEAS_IND

6.1.2

Returns the measurement on a carrier.

NMM_RSSI_MEAS_CNF

6.1.3

Indicates the end of the measurements.

NMM_STOP_RSSI_MEAS_REQ

6.1.4

Stops the RSSI measurements.

NMM_CELL_SEARCH_REQ

6.1.5

Triggers the search for cells on the


specified carrier. Optionally a list of cells
can be specified.

NMM_CELL_SEARCH_IND

6.1.6

Returns a found cell.

NMM_CELL_SEARCH_CNF

6.1.7

Indicates the end of the cell search.

NMM_STOP_CELL_SEARCH_REQ

6.1.8

Stops the cell search.

NMM_PBCH_CONFIG_REQ

6.1.9

Triggers reading of the PBCH.

NMM_PBCH_CONFIG_CNF

6.1.10

Confirms the PBCH configuration.

NMM_PBCH_DATA_IND

6.1.11

Returns the data read from PBCH. For


each NMM_PBCH_CONFIG_REQ zero or
one NMM_PBCH_DATA_IND are
received.

NMM_STOP_PBCH_REQ

6.1.12

Stop PBCH reading.

NMM_SIB1_CONFIG_REQ

6.1.13

Requests SIB1 reading on EARFCN and PCI


configured with last
NMM_PBCH_CONFIG_REQ.

NMM_SIB1_CONFIG_CNF

6.1.14

Confirm SIB1 configuration.

NMM_BCCH_CONFIG_REQ

6.1.15

Requests reading of the BCCH other than


SIB1 reading on EARFCN and PCI
configured with last
NMM_PBCH_CONFIG_REQ.

NMM_BCCH_CONFIG_CNF

6.1.16

Confirm BCCH configuration.

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 5

NMM_BCCH_DATA_IND

6.1.17

Returns the data read from BCCH


including SIB1.

NMM_STOP_BCCH_REQ

6.1.18

Stop BCCH and/or SIB1 reading.

6.1.1 NMM_RSSI_MEAS_REQ Parameters


Elements

Value

Type

Description

freqBandIndicator

1..64

uint8_t

measurementPeriod

1..255

uint8_t

nr_earfcnList

0.. MAX_CARRIER_LIST

uint8_t

earfcnList
[MAX_CARRIER_LIST]
nr_vendorSpecificList
vendorSpecificList

0..65535

array of uint16_t

0..MAX_VENDOR_LIST

uint8_t
A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

The E-UTRA band for which the carrierList


applies. See [1] table 5.5-1
The length of time the NMM measure RSSI
over. In 10ms radio frames.
The number of carriers which should be
measured. In case no carrier (value 0) is
specified all carriers in the band shall be
measured.
The list of carriers to be measured. See
[1].
The number of elements in the next array.
Contains vendor specific configuration.

6.1.2 NMM_RSSI_MEAS_IND parameters


Elements

Value

Type

Description

rssi
earfcn
nr_vendorSpecificList
vendorSpecificList

0..128 (-144..-16)
0..65535
0..MAX_VENDOR_LIST

uint8_t
uint16_t
uint8_t
A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

The measured RSSI in dBm in steps of 1dB.


The carrier measured. See [1].
The number of elements in the next array.
Contains vendor specific configuration.

6.1.3 NMM_RSSI_MEAS_CNF Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next array.

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

Contains vendor specific configuration.

vendorSpecificList

6.1.4 NMM_STOP_RSSI_MEAS_REQ Parameters


2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 6

Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array.

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

Contains vendor specific configuration.

vendorSpecificList

6.1.5 NMM_CELL_SEARCH_REQ Parameters


Elements

Value

Type

Description

earfcn

1..65535

uint16_t

exhaustiveSearch

TRUE, FALSE

bool

nr_pciList

0..MAX_PCI_LIST

uint8_t

pciList[MAX_PCI_LIST]

0..503

array of uint16_t

measBandwidth

6,15,25,50,75,100

uint8_t

measurementPeriod

1..255

uint8_t

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The earfcn for which cells should be


measured.
NMM should try to find all cells on the
carrier.
The number of cells in the pciList. If 0 all
cells on the carrier should be found.
Otherwise, depending on
exhaustiveSearch flag, only the given
pciList is searched or the pciList is used
for indicating a priority list.
The list of cells which should be
searched.
The number of resource blocks which
should be used for measuring RSRP. See
[3].
The length of time the NMM measure
RSSI over. In 10ms radio frames.
The number of elements in the next
array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.6 NMM_CELL_SEARCH_IND Parameters


Elements

Value

Type

Description

nr_cellFoundList

0..MAX_CELL_FOUND_LIST

uint8_t

cellFoundList[MAX_C
ELL_FOUND_LIST]
nr_vendorSpecificList
vendorSpecificList

Array of CellFoundElement
see 7.1
0..MAX_VENDOR_LIST

array of struct

The number of cells indicated in this


message.
The cell information from the NMM.

uint8_t
A variable-length
array of variable-

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

The number of elements in the next array.


Contains vendor specific configuration.

page 7

length
VendorSpecificLis
tElement see 7.3

6.1.7 NMM_CELL_SEARCH_CNF Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 8

6.1.8 NMM_STOP_CELL_SEARCH_REQ Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.9 NMM_PBCH_CONFIG_REQ Parameters


Elements

Value

Type

Description

pci

0..503

uint16_t

earfcn

0..65535

uint16_t

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The physical cell identity of the cell


which the NMM should read the PBCH.
The EARFCN for the cell which the
NMM should read the PBCH.
The number of elements in the next
array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.10 NMM_PBCH_CONFIG_CNF Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.11 NMM_PBCH_DATA_IND Parameters


Elements

Value

Type

Description

pci

0..503

uint16_t

cause

MIB_OK, MIB_FAILED

enum

numTx

1,2,4

uint8_t

sfn

0..1023

uint16_t

The physical cell identity of the cell


which the NMM synchronized to.
Indicates if MIB reading was successful
or not. In case reading failed the next
parameters are invalid.
The number of transmit antennas of the
cell.
The system frame number of the cell.

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 9

phichDuration
phichResource
dl_SystemBandwidth
nr_vendorSpecificList

normal, extended
one_sixth, one_half,
one, two
6,15,25,50,75,100
0..MAX_VENDOR_LIST

vendorSpecificList

enum
enum

The PHICH duration of the cell.


The PHICH resource size of the cell.

uint8_t
uint8_t

DL transmission bandwidth in RBs.


The number of elements in the next
array.
Contains vendor specific configuration.

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.12 NMM_STOP_PBCH_REQ Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.13 NMM_SIB1_CONFIG_REQ Parameters


Elements

Value

Type

Description

retryCount

1..8

uint8_t

nr_vendorSpecificList
vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t
A variable-length
array of variablelength
VendorSpecificLis
tElement see 7.3

The number of periods for which decoding


of a SIB1 should be retried.
The number of elements in the next array
Contains vendor specific configuration.

6.1.14 NMM_SIB1_CONFIG_CNF Paramerers


Elements

Value

Type

Description

nr_vendorSpecificList
vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t
A variable-length
array of variablelength
VendorSpecificLis
tElement see 7.3

The number of elements in the next array.


Contains vendor specific configuration.

6.1.15 NMM_BCCH_CONFIG_REQ Parameters

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 10

Elements

Value

Type

Description

nr_ siPeriodicityList
siPeriodicityList
[MAX_SI_LIST]
siWindow
retryCount

0..MAX_SI_LIST
80, 160, 320, 640, 1280,
2560, 5120
1,2,5,10,15,20,40
1..8

uint8_t
array of
u_int16_t
uint8_t
uint8_t

The number of SIs to read.


The SI periodicity of all requested SIs.

nr_vendorSpecificList
vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t
A variable-length
array of variablelength
VendorSpecificLis
tElement see 7.3

The SI window.
The number of siWindows for which
decoding of a SI should be retried. The
retiries are counted per siPeriodicity.
The number of elements in the next array.
Contains vendor specific configuration.

6.1.16 NMM_BCCH_CONFIG_CNF Parameters


Elements

Value

Type

Description

nr_vendorSpecificList

0..MAX_VENDOR_LIST

uint8_t

The number of elements in the next


array.
Contains vendor specific configuration.

vendorSpecificList

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.17 NMM_BCCH_DATA_IND Parameters


Elements

Value

Type

Description

nr_bcchDataList

0..MAX_BCCH_DATA_LIST

uint8_t

bcchDataList[MAX_BCCH_DATA_LIST]

Array of
BcchDataElement. see 7.2
0..MAX_VENDOR_LIST

array of struct

The number of
BCCHs in this
message .
The list of decoded
BCCH information.
The number of
elements in the next
array
Contains vendor
specific
configuration.

nr_vendorSpecificList

vendorSpecificList

uint8_t

A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

6.1.18 NMM_STOP_BCCH_REQ Parameters


Elements

Value

Type

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

Description

page 11

nr_vendorSpecificList

0..MAX_VENDOR_LIST

vendorSpecificList

7
7.1

uint8_t
A variable-length array of
variable-length
VendorSpecificListElement
see 7.3

The number of elements in the next


array.
Contains vendor specific configuration.

Parameters
CellFoundElement

Elements

Value

Type

Description

rsrp
pci

0..128 (-144..-16)
0..503

uint8_t
uint16_t

The measured RSRP value in dBm. See [3].


The physical cell identity of the cell which
the NMM synchronized to.

7.2

BcchDataElement

Elements

Value

Type

Description

len
sfn
sf
data[MAX_BCCH_SIZ
E]

0..MAX_BCCH_SIZE
0..1023
0..9

uint16_t
uint16_t
uint8_t
uint8_t

The length of the BCCH payload.


The radio frame the data was received on.
The subframe the data was received on.
The BCCH payload. The payload is mapped
according to 36.212 (Byte 0, bit 8 is
mapped to a0).

Type

Description

uint32_t
uint32_t
struct

Indicating the type of the value.


The length of the actual value.
The actual value which will be set

7.3

VendorSpecificListElement

Elements

Value

type
length
value

Constants
Elements

Value

MAX_CARRIER_LIST

100

MAX_PCI_LIST

50

MAX_SI_LIST

32

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 12

MAX_BCCH_SIZE

2048

MAX_CELL_FOUND_LIST

16

MAX_BCCH_DATA_LIST

32

MAX_VENDOR_LIST

16

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 13

Scenarios

9.1

Cell Search
RRM

NMM
NMM_RSSI_MEAS_REQ
setup RFfor band

loop
setup RF for carrier

measure RSSI
NMM_RSSI_MEAS_IND

last carrier has


been measured
NMM_RSSI_MEAS_CNF

NMM_CELL_SEARCH_REQ

loop
acquire sync
NMM_CELL_SEARCH_IND

measure RSRP

last cell has been


measured
NMM_CELL_SEARCH_CNF

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 14

9.2

System Information reading


RRM

NMM
NMM_PBCH_CONFIG_REQ
NMM_PBCH_CONFIG_CNF
read MIB from
PBCH

NMM_PBCH_DATA_IND
NMM_STOP_PBCH_REQ
NMM_SIB1_CONFIG_REQ
NMM_SIB1_CONFIG_CNF
NMM_BCCH_DATA_IND

NMM_BCCH_CONFIG_REQ

read SIB1 from


BCCH

NMM_BCCH_CONFIG_CNF
loop
NMM_BCCH_DATA_IND

read SIx from


BCCH

NMM_BCCH_STOP_REQ

10 References
[1] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio
transmission and reception, v8.5.1, March 200.
[2] 3GPP TS 36.133: Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of
radio resource management, v8.5.0, March 2009.
[3] 3GPP TS 36.214: http://www.3gpp.org/ftp/Specs/html-info/36214.htmEvolved Universal Terrestrial
Radio Access (E-UTRA); Physical layer - Measurements, v8.6.0, March 2009.
[4] A. Maida, Femto Network Monitor Mode Receiver performance & RF Self Configuration
Algorithms, UbiquiSys Ltd, v5

11 Revision History
Version

Description

1.01

Prepared for public release

2010 The Femto Forum, Doc. No. FF_Tech_003_v1.01

page 15

Você também pode gostar