Spid Lte 490

LTE490 Subscriber profile ID selective
neighbor cell list

Tor Leif Aarland
Ice
Oslo, November 2016
For internal use

1 © Nokia Siemens Networks
Feature overview (2,4)
NEI: LTE490 Subscriber profile ID selective neighbor cell list
Inter-RAT HO to operator B WCDMA layer is based on defined • Features gives oprator possibility to
SPID B and Mobility Profile B defined for operator B differentiate behaviour of UE for mobility
procedures depending on Subscriber
Profile ID (SPID) and has influence on
which target frequencies the UE has to
Common operator A and B LTE measure
layer
• In order to configure feature operator has
to define:
Not shared operator B WCDMA layer – Subscriber profile ID (SPID) for UE in
Core Network - HSS
(Home Subscriber Server )
Not shared operator A WCDMA layer – Mobility Profiles in eNB database
(default profile is mandatory)
– Mapping list
Inter-RAT HO to operator A WCDMA layer is based on defined SPID A
and Mobility Profile A defined for operator A
EXAMPLE
• Operators A & B are using common LTE network but own WCDMA networks
• Configuration example:
– UEs of operator A have assigned SPID A, and UEs of operator B have assigned SPID B;
– Mobility Profile instance A can be used by operator A, and Mobility Profile instance B is for operator B configurations
– Both Mobility Profile A & B can have same values for LTE frequencies list and similar Redirection targets for LTE
– Mobility Profile A has WCDMA frequencies used by operator A and Mobility Profile B has WCDMA frequencies used by
operator B
– On LNCEL level SPID A is mapped to Mobility Profile A and SPID B is mapped to Mobility Profile B
For internal use

2 © Nokia Siemens Networks LTE490 / Paweł Cebula / July 2011
• Functionality is activated for the whole eNodeB and it is optional

• Feature does not have influence on mobility alghoritms and threholds
• Mapping list between SPIDs and Mobility Profiles there is in eNB database on
LNCEL level
• Mobility Profiles are defined on LNBTS level and consist list of target frequencies
for a given mobility type and for mobility based on redirection also priority
parameter
• Multiple SPID values can be specified for one specific Mobility Profile
• Configuration must allows to uniquely choose Mobility Profile for a given SPID
value
For internal use

• eNB receives SPID value assigned to UE in INITIAL CONTEXT SETUP message

or in HANDOVER REQUIRED in case incoming handover
• eNB stores SPID value to be used for the UE in mobility procedures
• During HO, SPID value of UE is forwarded to the target via HANDOVER
REQUEST message
• Feature has inpact on:

– measurement configuration for an UE (Initial Context Setup)
– measurement re-configuration for an UE (handovers)
– choosing redirect target (RRC connection release with redirect due to change
in radio conditions or Emergency calls or CF Fallback to UTRAN or GERAN)
For internal use

Configuration guidelines (1,7)
• Feature can be enable by setting
corresponding O&M flag on BTS level
(actSelMobPrf parameter)
• In order to configure feature new
objects have to be created on the
LTBTS level by operator:
– MOC MODPR: MObility Default
PRofile (mandatory)
– MOC MOPR: MObility PRofile
(optional, maximum 8)
• Under MODPR operator has posibility to
create up to 6 MODREDs (MObility
Default profile for REDirection) which
contains the redirect target info
• Under MOPR operator has posibility to
create up to 6 MOREDs (MObility
profile for REDirection) which contains
the redirect target info
New created MOCs
For internal use

• Operator has to define mapping

between User Profiles to
Subscriber Profile IDs list –
moPrMappingList, configured
list there is in LNCEL MOC
Defined mapping list –

LNCEL MOC
For internal use

• Default Mobility Profile (MODPR) consit of:
– Flag for Automatic Adaptation to Frequency Layers of all Neighbour Cells
– optional Frequency Layer List for LTE Inter Frequency Mobility.
– optional Frequency Layer List for Packet Switched Handover to WCDMA target cells
– optional list of Reference Frequencies for Network Assisted Cell Change to GERAN
(band indicator and ARFCN value)
• MODRED consit of:
– Redirection Priority for Circuit Switched Fallback with Redirection
– Redirection Priority for Emergency Call
– Redirection Priority for UE Context Release
– RAT for Redirection:
▪ eUTRA frequency
▪ or UTRA frequency
▪ or GERAN ARFCN values list and GERAN band indicator
For internal use

• Mobility Profile (MOPR) consit of:
– optional Frequency Layer List for LTE Inter Frequency Mobility
– optional Frequency Layer List for Packet Switched Handover to WCDMA target cells
– optional list of Reference Frequencies for Network Assisted Cell Change to GERAN
(Each list element shall consist of band indicator and ARFCN value)
• MORED consit of:
– Redirection Priority for Circuit Switched Fallback with Redirection
– Redirection Priority for Emergency Call
– Redirection Priority for UE Context Release
– RAT for Redirection
▪ eUTRA frequency
▪ or UTRA frequency
▪ or GERAN ARFCN values list and GERAN band indicator
For internal use

• In order to activate feature default profile must be defined
• Default Profile (MOC MODPR) is used in case when SPID value mapping for an
UE is not available or SPID for an UE is not available
• Modification of O&M definitions of Mobility Profiles and mapping to SPID values
can be done online, but new configuration is valid only for new UEs
• Mobility Profile update has influence only for new calls
• Deletion of a Mobility Profile is rejected if it is still assigned to an SPID value
For internal use

• In case of Default Mobility Profile (MOC MODR) there is the option "autoAdapt"
which can be set to "true" or „false”
• If flag is set to „true” Default Profile contains all frequencies in LNADJL, LNADJW
and LNADJG configured at eNB
• If this flag is set to "false" operator has to define list of frequencies in MOC
MODPR and redirect targets in MOC MODRED
For internal use

• If "autoAdapt" flag is "False" and no target frequency info and/or redirect target
info are defined:
– measurement configuration in this case will not be done for an UE for which an
SPID is not available or no matching SPID could be found at eNB
– no redirection will be possible
• If during configuration Default Profile MOC and/or User Profile MOC instances
along with mapping between User Profiles to Susbcriber Profile Ids has been
received by eNB but the LTE490 feature flag has not been enabled.
– eNB shall store the received configuration but apply this LTE490 O&M
configuration data only when the feature flag has been enabled
For internal use

Counters (1,1)
• Feature offers 8 new PM counters to report average number of active

users per cell per mobility profile
• 1 PM counter to report average number of active users per cell for Default
Profile.
• If feature is disabled only the existing counter for number of active users
per cell is updated
For internal use


Spid Lte 490

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Spid Lte 490

Încărcat de

Drepturi de autor:

Formate disponibile

LTE490 Subscriber profile ID selective

neighbor cell list

For internal use

For internal use

• Functionality is activated for the whole eNodeB and it is optional

For internal use

• eNB receives SPID value assigned to UE in INITIAL CONTEXT SETUP message

• Feature has inpact on:

For internal use

For internal use

• Operator has to define mapping

Defined mapping list –

For internal use

For internal use

For internal use

For internal use

For internal use

For internal use

• Feature offers 8 new PM counters to report average number of active

For internal use

S-ar putea să vă placă și