MME Administration Guide, StarOS Release 21.6

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

MME Administration Guide, StarOS Release 21.6

Chapter Title

Dedicated Core Networks on MME

PDF - Complete Book (11.15 MB) PDF - This Chapter (1.73 MB)
View with Adobe Reader on a variety of devices

Results

Updated:: January 25, 2018

Chapter: Dedicated Core Networks on MME

Feature Summary and Revision History
Feature Description
- Overview
- External Interfaces
How It Works
Configuring DECOR on MME
Monitoring and Troubleshooting
- Show Commands and/or Outputs
- Bulk Statistics

Dedicated Core Networks on MME

Important:

Enhancements to the Dedicated Core Networks feature in release 21.6 are not fully qualified and are available only for testing purposes. For more information, contact your Cisco Account representative. For the list of enhancements in release 21.6, refer to the Feature Summary and Revision History.

This chapter describes the Dedicated Core Networks feature in the following sections:

Feature Summary and Revision History
Feature Description
How It Works
Configuring DECOR on MME
Monitoring and Troubleshooting

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area	MME
Applicable Platform(s)	ASR 5500 VPC-DI VPC-SI
Feature Default	Enabled - Configuration Required
Related Changes in This Release	Not Applicable
Related Documentation	Command Line Interface Reference MME Administration Guide Statistics and Counters Reference

Table 1 Revision History
Revision Details	Release
Enhancements to the DECOR feature in release 21.6 are not fully qualified and are available only for testing purposes. The DECOR feature is enhanced to support: DNS based MMEGI selection DCN-ID IE in Attach/TAU Accept and GUTI Reallocation Command message towards UE DCN-ID IE in INITIAL UE MESSAGE from eNodeB HSS initiated DCN reselection Network sharing with same MMEGI for different PLMNs Network sharing with different MMEGIs for different PLMNs Served DCNs Items IE in S1 Setup Response and MME Configuration Update messages towards eNodeBs	21.6
First introduced.	21.4

Feature Description

Dedicated Core Networks (DCNs) allows an operator to deploy one or more dedicated core network within a PLMN, with each core network dedicated for specific type of subscriber. The specific dedicated core network that serves a UE is selected based on subscription information and operator configuration, without requiring the UEs to be modified.

Dedicated Core Networks (DCNs) can either provide specific characteristics and functions to the UE or subscriber, or isolate them to a UE or subscriber. For example, Machine-to-Machine (M2M) subscribers, subscribers belonging to a specific enterprise or separate administrative domain, and so on.

This feature aims to route and maintain UEs in their respective DCNs.

Overview
External Interfaces

Overview

DCNs enable operators to deploy multiple core networks consisting of one or more MME/SGSN and optionally one or more S-GW/P-GW/PCRF.

If a network deploys a DCN selection based on both LAPI indication and subscription information (MME/SGSN), then DCN selection based on the subscription information provided by MME/SGSN overrides the selection based on the LAPI-indication by RAN.

A new optional subscription information parameter, UE Usage Type, stored in the HSS, is used by the serving network to select the DCNs that must serve the UE. The operator can configure DCNs and it's serving UE Usage Type as required. Multiple UE Usage Types can be served by the same DCN. The HSS provides the UE Usage Type value in the subscription information of the UE to the MME/SGSN/MSC. The serving network chooses the DCN based on the operator configured (UE Usage Type to DCN) mapping, other locally configured operator's policies, and the UE related context information available at the serving network.

Note

One UE subscription can be associated only with a single UE Usage Type, which describes its characteristics and functions.

External Interfaces

The following components are enhanced to support the DECOR feature on the MME:

DNS
S6a (HSS) Interface
GTPv2 (MME or S4-SGSN)

DNS

S-GW or P-GW Selection

To perform S-GW or P-GW selection from DCNs serving UE Usage Type, the existing service parameters of the SNAPTR records are enhanced by appending the character string "+ue-<ue usage type>" to the "app-protocol" name identifying the UE usage type(s) for which the record applies.

For example: S-GW service parameter — x-3gpp-sgw:x-s11+ue-1.10.20 will represent the S-GW which is part of a DCN serving UE usage types 1, 10, and 20.

For example: P-GW service parameter — x-3gpp-pgw:x-s5-gtp+ue-1.10.20:x-s8-gtp+ue-1.10.20 will represent the P-GW which is part of a DCN serving UE usage types 1, 10, and 20.

MMEGI Retrieval

MME uses local configuration for MMEGI corresponding to the UE Usage Type and DNS SNAPTR procedures.

The configuration options for static (local) or DNS or both are provided under decor-profile. If both options are enabled, then DNS is given preference. When DNS lookup fails, static (local) value is used as fallback.

To retrieve the MMEGI identifying the DCN serving a particular UE usage type, the SNAPTR procedure uses the Application-Unique String set to the TAI FQDN. The existing service parameters are enhanced by appending the character string "+ue-<ue usage type>" to the "app-protocol" name identifying the UE usage type for which the discovery and selection procedures are performed.

For example: MME will discover the MMEGI for a particular UE usage type by using the "Service Parameters" of "x-3gpp-mme:x-s10+ue-<ue usage type>". The service parameters are enhanced to identify the UE usage type(s) for which the record applies. The MMEGI will be provisioned in the host name of the records and MMEGI will be retrieved from the host name.

MME or S4-SGSN Selection

To perform MME/S4-SGSN selection from the same DCN during handovers, the existing service parameters are enhanced by appending the character string "+ue-<ue usage type>" to the "app-protocol" name identifying the UE usage type.

If the MME fails to find a candidate list for the specific UE Usage Type, it falls back to the legacy DNS selection procedure.

For example:

For an MME to find a candidate set of target MMEs — "x-3gpp-mme:x-s10+ue-<ue usage type>"

For an MME to find a candidate set of target SGSNs — "x-3gpp-sgsn:x-s3+ue-<ue usage type>"

Note

I-RAT handover between MME and Gn-SGSN is not supported in this release.

S6a (HSS) Interface

To request the UE Usage Type from HSS, MME sets the "Send UE Usage Type" flag in the AIR-Flags AVP, in the AIR command.

The AIR-Flag is set only if the decor s6a ue-usage-type CLI command is enabled under MME-service or Call-Control-Profile.

HSS may include the UE-Usage-Type AVP in the AIA response command in the case of DIAMETER_SUCCESS result code. MME will store the UE Usage Type in the UE context for this result code.

GTPv2 (MME or S4-SGSN)

MME supports the UE Usage Type IE in Identification Response, Forward Relocation Request, and Context Response Messages. If the subscribed UE Usage Type is available, it will be set to the available value, otherwise the MME encodes the length field of this IE with 0.

Similarly, MME will parse and store the UE Usage Type value when received from the peer node.

How It Works

MME obtains the UE Usage type and determines the MMEGI that serves the corresponding DCN.

The MME then compares this MMEGI with its own MMEGI to perform a reroute or process further. In case of reroute, the request message is redirected to the appropriate MME. Refer to the ATTACH and TAU Procedure call flow for more information.

The following deployment scenarios are supported when DECOR is enabled on the MME:

Initial request is sent by RAN (eNodeB) when sufficient information is not available to select a specific DCN.
MME can be deployed as a part of DCN to serve one or more UE Usage Types.
MME can be deployed as part of a Common Core Network (CCN) or Default Core Network, to serve UE Usage Types for which specific DCN is not available.

Note

An MME can service initial RAN requests and also be a part of a DCN or a CCN. However, a particular MME service can only belong to one DCN or CCN within a PLMN domain.

The Dedicated Core Network implements the following functionalities on the MME:

NAS Message Redirection
ATTACH and TAU Procedures
UE Usage Type support on S6a and GTPv2 interfaces
SGW/PGW DNS selection procedures with UE Usage Type
MME/SGSN selection procedures with UE Usage Type during handovers
Roaming
Network Sharing
DNS based MMEGI selection
DCN ID Support
HSS initiated DCN reselection

Flows
Roaming
Network Sharing
Limitations
Supported Standards

Flows

This section describes the following call flows related to the DECOR feature.

NAS Message Redirection Procedure
Attach or TAU Procedure
HSS initiated Dedicated Core Network Reselection

NAS Message Redirection Procedure
ATTACH and TAU Procedure
HSS Initiated Dedicated Core Network Reselection
UE assisted Dedicated Core Network Selection

NAS Message Redirection Procedure

Reroute NAS message is used to reroute a UE from one CN node to another CN node during Attach, TAU, or RAU procedure. This is also used by the MME/SGSN or HSS initiated Dedicated Core Network Reselection procedure.

When the first MME determines the UE Usage Type, it fetches the DCN configuration serving the UE and the corresponding MMEGI (from configuration or DNS). If the MME’s MMEGI is not the same as the MMEGI of the DCN, MME moves the UE to another MME using the NAS messaging redirection procedure.

The following call flow illustrates the NAS Message Redirection procedure:

Figure 1. NAS Message Redirection Procedure

Step	Description
1	The first new MME sends a Reroute NAS Message Request to eNodeB including UE Usage Type and MMEGI among other parameters.
2	RAN selects a new MME based on MMEGI. If no valid MME can be obtained from MMEGI, it selects MME from the CCN or forwards to the same first MME.
3	The second new MME determines from the MMEGI field if the incoming request is a re-routed NAS request or not. Now, if the received MMEGI belongs to the second MME, the call is serviced, else the call is rejected. No further rerouting is performed. If the UE Usage Type is received by the second MME, it is used for S-GW/P-GW selection.

Step

Description

The first new MME sends a Reroute NAS Message Request to eNodeB including UE Usage Type and MMEGI among other parameters.

RAN selects a new MME based on MMEGI. If no valid MME can be obtained from MMEGI, it selects MME from the CCN or forwards to the same first MME.

The second new MME determines from the MMEGI field if the incoming request is a re-routed NAS request or not. Now, if the received MMEGI belongs to the second MME, the call is serviced, else the call is rejected. No further rerouting is performed.

If the UE Usage Type is received by the second MME, it is used for S-GW/P-GW selection.

ATTACH and TAU Procedure

The following figure illustrates a detailed flow of the ATTACH and TAU procedure.

Figure 2. ATTACH and TAU Procedure

Step	Description
1	In the RRC Connection Complete message transferring the NAS Request message, the UE provides the DCN-ID, if available. If the UE has a PLMN specific DCN-ID. the UE provides this value and if no PLMN specific DCN-ID exists, then the pre-provisioned default standardized DCN-ID will be provided, if pre-provisioned in the UE. The RAN node selects a DCN and a serving MME/SGSN within the network of the selected core network operator based on the DCN-ID and configuration in the RAN node. The NAS Request message is sent to the selected node. The DCN-ID is provided by the RAN to the MME/SGSN together with the NAS Request message.
2	The first new MME does not receive the MMEGI from eNodeB. The MME determines the UE Usage Type as follows: It may receive the UE Usage Type from the old MME in the Identification or Context Response message. It may determine from the locally available UE context information. It may determine from the local configuration. It sends an AIR message to the HSS requesting the UE Usage Type by adding the parameter "Send UE Usage Type" flag in the message.
3	When UE Usage Type is available, and if the MME has to send an AIR message to the HSS to fetch authentication vectors, the “Send UE Usage Type” flag is not set in the AIR message.
4	The first new MME determines to handle the UE: When there is a configured DCN and the first new MME belongs to the MMEGI serving the DCN. It will continue with the call flow. The MME/SGSN sends the DCN-ID, if available, for the new DCN to the UE in the NAS Accept message. The UE updates its stored DCN-ID parameter for the serving PLMN if DCN-ID for serving PLMN is changed.
5	The first new MME determines to reject the UE: When UE Usage Type is available, but without a matching DCN. The NAS message is rejected with parameters (For example: backoff timer), such that the UE does not immediately re-initiate the NAS procedure.
6	The first new MME determines to reroute the UE: When there is a configured DCN and first new MME does not belong to the MMEGI. The first new MME sends a Context Acknowledge message with cause code indicating that the procedure is not successful. The old MME/SGSN will continue as if Context Request was never received. First new MME performs the NAS redirection procedure and the request may be routed by RAN to a second new MME.
7	The second new MME determines to handle the UE or reject it; the MME does not perform another re-route. The process of handling the UE or rejecting the UE is similar to the procedure used in the case of the first new MME. The second new MME does not fetch UE Usage Type from the HSS. It receives either from the RAN node or the old MME.

HSS Initiated Dedicated Core Network Reselection

This procedure is used by the HSS to update (add, modify, or delete) the UE Usage Type subscription parameter in the serving node. This procedure may result in change of serving node of the UE.

The following call flow illustrates the HSS Initiated DCN Reselection procedure.

Figure 3. HSS Initiated Dedicated Core Network Reselection Procedure

Step	Description
1	The HSS sends an Insert Subscriber Data Request (IMSI, Subscription Data) message to the MME. The Subscription Data includes the UE Usage Type information.
2	The MME updates the stored Subscription Data and acknowledges the Insert Subscriber Data Request message by returning an Insert Subscriber Data Answer (IMSI) message to the HSS. The procedure ends if the MME/SGSN continues to serve the UE.
As per this callflow, one of the following steps occur: Steps 3 through 6 occur in case the UE is already in connected mode or UE enters connected mode by initiating data transfer. Step 7 occurs in case the UE is in idle mode and performs a TAU/RAU procedure. Important: Paging is not supported in this release. If the UE is in idle mode, MME waits until the UE becomes active.
3	The UE initiates NAS connection establishment either by uplink data or by sending a TAU/RAU Request.
4	The MME triggers the GUTI re-allocation procedure and includes a non-broadcast TAI.
5	The MME releases RAN resources and UE is moved to idle mode.
6	The non-broadcast TAI triggers the UE to immediately start the TAU procedure. The MME receives the TAU Request message.
7	The UE performs a TAU request. The MME receives the TAU Request message
8	The MME triggers the NAS Message redirection procedure to redirect the UE if: the UE Usage Type for the UE has been added or modified and if it is not served by the MME the UE Usage Type has been withdrawn from the HSS subscription data and subscriptions without UE Usage Type are not served by the MME

UE assisted Dedicated Core Network Selection

The UE assisted Dedicated Core Network Selection feature reduces the need for DECOR reroute by using DCN-ID sent from the UE and DCN-ID used by RAN to select the correct DCN.

The DCN-ID will be assigned to the UE by the serving PLMN and is stored in the UE per PLMN-ID. Both standardized and operator specific values for DCN-ID are acceptable. The UE will use the PLMN specific DCN-ID whenever it is stored for the target PLMN.
The HPLMN may provision the UE with a single default standardized DCN-ID that will be used by the UE only if the UE has no PLMN specific DCN-ID of the target PLMN. When a UE configuration is changed with a new default standardized DCN-ID, the UE will delete all stored PLMN specific DCN-IDs.
The UE provides the DCN-ID to RAN at registration to a new location in the network, that is, in Attach, TAU, and RAU procedures.
RAN selects the serving node MME based on the DCN-ID provided by UE and configuration in RAN. For E-UTRAN, the eNodeB is conveyed with DCNs supported by the MME during setup of the S1 connection in S1 Setup Response.

Roaming

MME in the visited PLMN provides an operator policy that allows to serve a UE whose home PLMN does not support DCNs. MME also provides operator policies that support the UE Usage Type parameter received from the HPLMN HSS.

Network Sharing

MME supports DCN selection based on the selected PLMN information received from the UE.

Limitations

The DECOR feature has the following limitations:

Only one MMEGI can be configured per DCN.
DCN deployments as part of a PLMN is not supported. The ability to configure DCN for a set of TAI/TAC is not supported.
UE-Usage lookup from HSS during handovers/S3-S10 based Attach is not supported (Explicit AIR, UE moving from non-DCN network to DCN network).
MME initiated DCN re-selection is not supported.
DIAMETER_AUTHENTICATION_DATA_UNAVAILABLE result code is not supported.
HSS initiated UE usage type withdrawal is not supported. Only change in UE usage type is supported.
DCNs can be deployed partially or heterogeneously.
- Handover from service area where DCN is not used to an area where DCN is supported. In this case, MME does not receive UE Usage Type.
  
  In this release, MME is treated as if UE does not have UE Usage Type.
- The target MME or SGSN obtains the UE Usage Type information from the HSS during the subsequent TAU or RAU procedure. If the target MME/SGSN determines that the S-GW does not support the UE Usage Type, the target MME/SGSN must trigger the S-GW relocation as part of the handover procedures.
  
  In this release, S-GW relocation is not supported.

Supported Standards

The DECOR feature complies with the following standards:

3GPP 23.401 Release 13.11.0 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access
3GPP 23.401 Release 14.5.0 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access
3GPP 29.272 Release 13.10.0 - Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol
3GPP 29.272 Release 14.6.0 - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Diameter applications; 3GPP specific codes and identifiers
3GPP 29.274 Release 13.10.0 - Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3
3GPP 29.274 Release 14.5.0 - Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3
3GPP 29.303 Release 13.5.0 - Domain Name System Procedures; Stage 3
3GPP 29.303 Release 14.3.0 - Universal Mobile Telecommunications System (UMTS); LTE; Domain Name System Procedures; Stage 3

Configuring DECOR on MME

This section describes the configuration of Dedicated Core Networks on the MME.

The DECOR supports the following configurations:

DCN profile with
- UE-Usage-Type
- Static MMEGI
- DNS lookup for MMEGI
- PLMN
- DCN-ID
- Relative Capacity for the served DCN
Associate DCNs to a specific RAT Type
Associate multiple DCN profiles (to designate dedicated or default core network) to MME service
Request UE-Usage-Type from HSS on S6a interface
UE-Usage-Type per IMSI/IMEI range
Non-broadcast TAI

The DECOR feature includes the following configurations:

Configuring DCN Profile
Associating a DECOR Profile
Configuring UE Usage Type over S6a Interface under MME Service
Configuring UE Usage Type over S6a Interface under Call Control Profile
Configuring UE Usage Type under Call Control Profile
Configuring Non-Broadcast TAI

Configuring Decor Profile
Associating a DECOR Profile
Configuring UE Usage Type over S6a Interface under MME Service
Configuring UE Usage Type over S6a Interface under Call Control Profile
Configuring UE Usage Type under Call Control Profile
Configuring Non-Broadcast TAI

Configuring Decor Profile

Important:

Enhancements to the DECOR feature in release 21.6 are not fully qualified and are available only for testing purposes. For more information, contact your Cisco Account representative.

Use the following configuration to create and configure a DECOR profile specifying the MMEGI hosting the DCN and the associated UE usage type using that DCN.

configure
   [ no ] decor-profile profile_name [ -noconfirm ]
      dcn-id dcn_id
      [ no ] mmegi { mmegi_value | dns }
      plmn-id mcc mcc_id mnc mnc_id
      served-dcn [ relative-capacity capacity ]
      [ no ] ue-usage-types num_ue_usage_types
      no { dcn-id | plmn-id | served-dcn }
      end

Notes:

decor-profile profile_name: Configures the Dedicated Core Network as deployed by operator. A decor-profile without any ue-usage-types configuration is treated as a Common Core Network. profile_name must be an alphanumeric string of 1 through 63 characters.

Entering the decor-profile profile_name command results in the following prompt and changes to the Decor Profile Configuration mode:
```
[context_name]host_name(config-decor-profile-<profile_name>)#
```
dcn-id dcn_id: Configures the DCN identifier for the specified decor-profile. dcn_id is an integer from 0 to 65535.
mmegi mmegi_value [ dns ]: Identifies the MME Group Identifier (MMEGI) of the configured DCN. mmegi_value is an integer from 32768 to 65535.

dns: Enables DNS for MMEGI retrieval using UE Usage Type.
plmn-id mcc mcc_id mnc mnc_id: Configures the PLMN identifier for the specified decor profile. This supports network sharing with different MMEGIs for different PLMNs.

mcc mcc_id: Configures the mobile country code (MCC) for the specified decor profile. mcc_id is a 3-digit number between 000 to 999.

mnc mnc_id: Configures the mobile network code (MNC) for the specified decor profile. mnc_id is a 2- or 3-digit number between 00 to 999.
served-dcn [ relative-capacity capacity ]: Configures the MME that is serving the DCN and its relative capacity. These values are sent by MME to eNodeB during S1 Setup Response to indicate DCN-IDs served by the MME and their relative capacity.

relative-capacity capacity: Set the relative capacity of this DCN. capacity must be an integer from 0 to 255. The default relative-capacity is 255.
ue-usage-types num_ue_usage_types: Specifies the number of UE Usage Types in the dedicated core network. num_ue_usage_types is an integer from 0 to 255.

A maximum number of 20 UE Usage Types are supported per DCN.
no: Removes the specified DECOR parameters from the Global Configuration.

Associating a DECOR Profile

Use the following configuration to associate a DECOR profile with an MME service.

configure
   context context_name
      mme-service service_name
         [ associate | remove ] decor-profile profile_name [ access-type { all | eutran | nb-iot } ]
         end

Notes:

associate: Associates a DECOR profile with an MME service.
remove: Removes the specified DECOR profile from the configuration.
decor-profile profile_name: Specifies the DECOR profile that is associated with the MME Service.
access-type: Allows you to configure the type of network access — E-UTRAN, NB-IoT, or both.
- all : Specifies allows all access types.
- eutran: Specifies the access type as E-UTRAN.
- nb-iot: Specifies the access-type as NB-IoT.

Configuring UE Usage Type over S6a Interface under MME Service

Use the following configuration to advertise or request UE Usage Type over S6a interface.

configure
   context context_name
      mme-service service_name
         [ no ] decor s6a ue-usage-type
         end

Notes:

decor: Specifies the dedicated core network configuration.
s6a: Configures the S6a interface.
ue-usage-type: Specifies the UE Usage Type that needs to be sent in the Authentication-Information-Request message over S6a interface.
no: Disables the specified configuration.

Configuring UE Usage Type over S6a Interface under Call Control Profile

Use the following configuration to disable UE Usage Type requests over the S6a interface.

configure
   call-control-profile profile_name
      decor s6a ue-usage-type [ suppress ]
      remove decor s6a ue-usage-type
      end

Notes:

decor: Specifies a dedicated core network configuration.
s6a: Enables the DECOR S6a configuration.
ue-usage-type: Request UE usage type in S6a Authentication-Information-Request message.
suppress: Suppresses sending the UE usage type in S6a Authentication-Information-Request message.
remove: Removes the DECOR configuration.
The configuration under call-control-profile overrides the MME service configuration.

Configuring UE Usage Type under Call Control Profile

Use the following configuration to locally configure UE Usage Types for UEs matching the Call Control Profile criteria.

configure
   call-control-profile profile_name
      decor ue-usage-type usage_type_value
      remove decor ue-usage-type
      end

Notes:

decor: Specifies a dedicated core network configuration.
ue-usage-type usage_type_value: Configures a UE Usage Type locally. usage_type_value must be an integer from 0 to 255.
remove: Removes the specified configuration.

Configuring Non-Broadcast TAI

Important:

Enhancements to the DECOR feature in release 21.6 are not fully qualified and are available only for testing purposes. For more information, contact your Cisco Account representative.

Use the following configuration to configure non-broadcast TAI.

MME supports HSS Initiated Dedicated Core Network Reselection in this release. When HSS sends ISDR with different UE-Usage-Type value other than what is already used by the subscriber and MME decides to move that UE to a new DCN, MME will send the GUTI Reallocation command with unchanged GUTI and non-broadcast TAI.

configure
   contextcontext_name
      mme-service service_name
         tai non-broadcast mcc mcc_id mnc mnc_id tac tac_id
         no tai non-broadcast
         end

Notes:

tai non-broadcast mcc mcc_id mnc mnc_id tac tac_id: Specifies the Tracking Area Identity (TAI) which is not assigned to any area.

mcc mcc_id: Configures the mobile country code (MCC) for the specified decor profile. mcc_id is a 3-digit number between 000 to 999.

mnc mnc_id: Configures the mobile network code (MNC) for the specified decor profile. mnc_id is a 2- or 3-digit number between 00 to 999.

tac tac_id: Configures the tracking area code (TAC) for the specified decor profile. tac_id is an integer from 0 to 65535.
no: Deletes the specified configuration.

Monitoring and Troubleshooting

Important:

Enhancements to the DECOR feature in release 21.6 are not fully qualified and are available only for testing purposes. For more information, contact your Cisco Account representative.

This section provides information on the show commands available to support DECOR on MME.

Show Commands and/or Outputs
Bulk Statistics

Show Commands and/or Outputs

This section provides information regarding show commands and/or their outputs in support of the DECOR feature.

show decor-profile full all
show mme-service name <mme_svc_name>
show mme-service session full all
show mme-service statistics decor decor-profile <decor_profile_name>
show mme-service statistics decor
show mme-service statistics
show mme-service statistics recovered-values

show decor-profile full all

The following fields are added to the output of this command:

Decor Profile Name
UE Usage Types
MMEGI
DNS
DCN Id
PLMN Id
Serving DCN
- Relative capacity

show mme-service name <mme_svc_name>

The following field is added to the output of this command:

Non-Broadcast TAI — Displays the configured values for MCC, MNC, and TAC.

show mme-service session full all

The output of this command includes the following DECOR information:

DECOR Information:
- UE Usage type
- DCN Id

show mme-service statistics decor decor-profile <decor_profile_name>

This show command displays the DECOR statistics for a specified DECOR profile. The DECOR profile level statistics are pegged only if a DECOR profile is configured.

The output of this command includes the following new fields in support of the DECOR feature:

Decor Statistics
- Attached Calls
- Initial Requests
  - ATTACH
    - Accepts
    - Reroutes
    - Rejects
- TAU
  - Accepts
  - Reroutes
  - Rejects
- Rerouted Requests
  - ATTACH
    - Accepts
    - Rejects
  - TAU
    - Accepts
    - Rejects
- UE-Usage-Type Source
  - HSS
  - UE Context
  - Peer MME
  - Peer SGSN
  - Config
  - eNB
- GUTI Reallocation Cmd due to UE-Usage-Type Change
  - Attempted
  - Success
  - Failures
- ISDR UE-Usage-Type Change
- MMEGI Selection
  - DNS
  - Local
  - Failure
- Node Selection
  - SGW DNS
    - Common
    - Dedicated
  - SGW Local Config
    - Common
  - PGW DNS
    - Common
    - Dedicated
  - PGW Local Config
    - Common
  - MME DNS
    - Common
    - Dedicated
  - MME Local Config
    - Common
  - SGSN DNS
    - Common
    - Dedicated
  - SGSN Local Config
    - Common

show mme-service statistics decor

The output of this command includes the following new fields in support of the DECOR feature:

Decor Statistics
- Attached Calls
- Initial Requests
  - ATTACH
    - Accepts
    - Reroutes
    - Rejects
  - TAU
    - Accepts
    - Reroutes
    - Rejects
- Rerouted Requests
  - ATTACH
    - Accepts
    - Rejects
  - TAU
    - Accepts
    - Rejects
- UE-Usage-Type Source
  - HSS
  - UE Context
  - Peer MME
  - Peer SGSN
  - Config
  - eNodeB
- GUTI Reallocation Cmd due to UE-Usage-Type Change
  - Attempted
  - Success
  - Failures
- ISDR UE-Usage-Type Change
- MMEGI Selection
  - DNS
  - Local
  - Failure
- Node Selection
  - SGW DNS
    - Common
    - Dedicated
  - SGW Local Config
    - Common
  - PGW DNS
    - Common
    - Dedicated
  - PGW Local Config
    - Common
  - MME DNS
    - Common
    - Dedicated
  - MME Local Config
    - Common
  - SGSN DNS
    - Common
    - Dedicated
  - SGSN Local Config
    - Common

show mme-service statistics

The output of this command includes the following DECOR statistics are displayed at an MME Service level:

S1AP Statistics
- Reroute NAS Requests
Decor Statistics
- Attached Calls
- Initial Requests
  - ATTACH
    - Accepts
    - Reroutes
    - Rejects
  - TAU
    - Accepts
    - Reroutes
    - Rejects
- Rerouted Requests
  - ATTACH
    - Accepts
    - Rejects
  - TAU
    - Accepts
    - Rejects
- UE-Usage-Type Source
  - HSS
  - UE Context
  - Peer MME
  - Peer SGSN
  - Config
  - eNodeB
- GUTI Reallocation Cmd due to UE-Usage-Type Change
  - Attempted
  - Success
  - Failures
- ISDR UE-Usage-Type Change
- MMEGI Selection
  - DNS
  - Local
  - Failure
- Node Selection
  - SGW DNS
    - Common
    - Dedicated
  - SGW Local Config
    - Common
  - PGW DNS
    - Common
    - Dedicated
  - PGW Local Config
    - Common
  - MME DNS
    - Common
    - Dedicated
  - MME Local Config
    - Common
  - SGSN DNS
    - Common
    - Dedicated
  - SGSN Local Config
    - Common

show mme-service statistics recovered-values

The following new fields are added to the output of this command:

Decor Statistics:

Initial Requests
- ATTACH
  - Accepts
  - Reroutes
  - Rejects
- TAU
  - Accepts
  - Reroutes
  - Rejects
Rerouted Requests
- ATTACH
  - Accepts
  - Rejects
- TAU
  - Accepts
  - Rejects

Bulk Statistics

The following bulk statistics are added in the MME schema to support the DECOR feature:

Bulk Statistics	Description
mme-decor-attached-subscriber	Indicates the number of MME sessions attached that have an associated UE usage type.
mme-decor-initial-attach-req-accept	Indicates the total number of Initial Attach Requests accepted by the MME, which functions as a DCN.
mme-decor-initial-attach-req-reroute	Indicates the total number of Initial Attach Requests which are rerouted by the MME, which functions as a DCN.
mme-decor-initial-attach-req-reject	Indicates the total number of Initial Attach Rejects due to No Reroute data and not handled by the MME, which functions as a DCN.
mme-decor-reroute-attach-req-accept	Indicates the total number of Rerouted Attach Requests which are accepted by the MME, which functions as a DCN.
mme-decor-reroute-attach-req-reject	Indicates the total number of Rerouted Attach Requests which are rejected by the MME, which functions as a DCN.
mme-decor-initial-tau-req-accept	Indicates the total number of Initial TAU Requests accepted by the MME, which functions as a DCN.
mme-decor-initial-tau-req-reroute	Indicates the total number of Initial TAU Requests which are rerouted by the MME, which functions as a DCN.
mme-decor-initial-tau-req-reject	Indicates the total number of Initial TAU Rejects due to No Reroute data and not handled by the MME, which functions as a DCN.
mme-decor-reroute-tau-req-accept	Indicates the total number of Rerouted TAU Requests which are accepted by the MME, which functions as a DCN.
mme-decor-reroute-tau-req-reject	Indicates the total number of Rerouted TAU Requests which are rejected by the MME, which functions as a DCN.
mme-decor-ue-usage-type-src-hss	Indicates the number of MME subscriber sessions, where UE usage type was obtained from HSS/AUC.
mme-decor-ue-usage-type-src-ue-ctxt	Indicates the number of MME subscriber sessions, where UE usage type was obtained from MME DB record.
mme-decor-ue-usage-type-src-peer-mme	Indicates the number of MME subscriber sessions, where UE usage type was obtained from peer MME as part of handover.
mme-decor-ue-usage-type-src-peer-sgsn	Indicates the number of MME subscriber sessions, where UE usage type was obtained from peer SGSN as part of handover.
mme-decor-ue-usage-type-src-cfg	Indicates the number of MME subscriber sessions, where UE usage type was obtained from local configuration.
mme-decor-ue-usage-type-src-enb	Indicates the number of MME subscriber sessions, where UE usage type was obtained from the eNodeB, in the S1 message as part of reroute.
mme-decor-sgw-sel-dns-common	Indicates the number of times S-GW DNS selection procedures were performed with DNS RR excluding UE usage type. This counter increments only when the DNS RR with UE usage type is absent.
mme-decor-sgw-sel-dns-dedicated	Indicates the number of times S-GW DNS selection procedures were performed with DNS RR including UE usage type parameter(s). This counter increments only when the DNS RR with UE usage type is present.
mme-decor-sgw-sel-local-cfg-common	Indicates the number of times S-GW selection procedures were performed with locally configured S-GW address, without considering the UE usage type.
mme-decor-pgw-sel-dns-common	Indicates the number of times PGW DNS selection procedures were performed with DNS RR excluding UE usage type. This counter increments only when the DNS RR with UE usage type is absent.
mme-decor-pgw-sel-dns-dedicated	Indicates the number of times S-GW DNS selection procedures were performed with DNS RR including UE usage type parameter(s). This counter increments only when the DNS RR with UE usage type is present.
mme-decor-pgw-sel-local-cfg-common	Indicates the number of times P-GW selection procedures were performed with locally configured P-GW address without considering the UE usage type.
mme-decor-mme-sel-dns-common	Indicates the number of times MME DNS selection procedures were performed with DNS RR excluding UE usage type. This counter increments only when the DNS RR with UE usage type is absent.
mme-decor-mme-sel-dns-dedicated	Indicates the number of times MME DNS selection procedures were performed with DNS RR including UE usage type parameter(s). This counter increments only when the DNS RR with UE usage type is present.
mme-decor-mme-sel-local-cfg-common	Indicates the number of times MME selection procedures were performed with locally configured MME address without considering the UE usage type.
mme-decor-sgsn-sel-dns-common	Indicates the number of times SGSN DNS selection procedures were performed with DNS RR excluding UE usage type. This counter increments only when the DNS RR with UE usage type is absent.
mme-decor-sgsn-sel-dns-dedicated	Indicates the number of times SGSN DNS selection procedures were performed with DNS RR including UE usage type parameter(s). This counter increments only when the DNS RR with UE usage type is present.
mme-decor-sgsn-sel-local-cfg-common	Indicates the number of times SGSN selection procedures were performed with locally configured SGSN address without considering the UE usage type.
s1ap-transdata-reroutenasreq	Indicates the number of S1 Reroute NAS Request Message sent by MME.
mme-decor-mmegi-sel-dns	Indicates the total number of times MMEGI is selected through DNS from a dedicated pool (DNS records having UE Usage Type which is matching).
mme-decor-mmegi-sel-local-cfg	Indicates the total number of times MMEGI is selected from local configuration.
mme-decor-mmegi-sel-fail	Indicates the total number of times MMEGI is selected from failure.
mme-decor-guti-reallocation-attempted	This proprietary counter tracks the number of GUTI Reallocation procedures attempted due to UE-Usage-Type Change from HSS through ISDR OR after connected mode handover and UE-Usage-Type not served by the MME (NAS GUTI Reallocation Command message was sent by MME).
mme-decor-guti-reallocation-success	Tracks the number of GUTI Reallocation procedures successful.
mme-decor-guti-reallocation-failures	Tracks the number of GUTI Reallocation procedure failures.
mme-decor-isdr-ue-usage-type-change	Tracks the number of ISDR Messages received with different UE-Usage-Type from the HSS.
recovered-mme-decor-initial-attach-req-accept	Indicates the total number of Initial Attach Requests accepted by the MME, which functions as a DCN.
recovered-mme-decor-initial-attach-req-reroute	Indicates the total number of Initial Attach Requests which are rerouted by the MME, which functions as a DCN.
recovered-mme-decor-initial-attach-req-reject	Indicates the total number of Initial Attach Rejects without the reroute data and that are not handled by the MME, which functions as a DCN.
recovered-mme-decor-reroute-attach-req-accept	Indicates the total number of Rerouted Attach Requests which are accepted by the MME, which functions as a DCN.
recovered-mme-decor-reroute-attach-req-reject	Indicates the total number of Rerouted Attach Requests which are rejected by the MME, which functions as a DCN.
recovered-mme-decor-initial-tau-req-accept	Indicates the total number of Initial TAU Reuquests accepted by the MME, which functions as a DCN.
recovered-mme-decor-initial-tau-req-reroute	Indicates the total number of Initial TAU Reuquests which are rerouted by the MME, which functions as a DCN.
recovered-mme-decor-initial-tau-req-reject	Indicates the total number of Initial TAU Rejects due to No Reroute data and not handled by the MME, which functions as a DCN.
recovered-mme-decor-reroute-tau-req-accept	Indicates the total number of Rerouted TAU Requests which are accepted by the MME, which functions as a DCN.
recovered-mme-decor-reroute-tau-req-accept	Indicates the total number of Rerouted TAU Requests which are rejected by the MME, which functions as a DCN.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)