Contents

1   Introduction

This document covers scheduled procedures in Ericsson™ Dynamic Activation (EDA), as it is used in User Data Consolidation (UDC) R1. The procedures and operations described in this document are available though Dynamic Activation Command Line Interface (CLI). How to use the CLI is covered in Generic CLI Interface Specification, Reference [1].

1.1   Purpose and Scope

The purpose of this document is to educate users on how to set up scheduled procedures in Dynamic Activation. This document also supplies specifications for all procedures that can be scheduled.

1.2   Target Group

The target groups for this document are as follows:

• System Administrators

1.3   Typographic Conventions

Typographic conventions are described in Library Overview, Reference [2].

In addition, this document uses the following to indicate operations:

1.4   Prerequisites

The following are prerequisites to using this document:

• Knowledge about the Dynamic Activation CLI; refer to the document Generic CLI Interface Specification, Reference [1].

2   Scheduling Procedures

This section covers how to schedule procedures. The procedures are then automatically executed at the specified times.

Note:  

Only one procedure of each procedure type can exist.

2.1   Initiate Scheduled Procedure (PGSPI)

The operation PGSPI initiates a scheduled procedure in Dynamic Activation.

2.1.1   PGSPI Request

Command Description:

                         �                                                                    �
PGSPI:PROCEDURE=procedure�,STARTDATE=startdate,TIME=time,[INTERVAL=interval,STOPDATE=stopdate]�;
                         �                                                                    �

If only PROCEDURE is specified, the procedure starts executing within a minute from the order. The procedure is, in this case, not scheduled to run again.

When the PGSPI command is executed, the cache file is created.

The name of cache file is location_cache.xml when PROCEDURE=LOCATION and mmelocation_cache.xml when PROCEDURE=MMELOCATION.

The location of the cache file is /var/dve/cache/.

The following table explains the attributes that can be used in a PGSPI request.

(1)  The INTERVAL parameter is only valid if it is used together with STOPDATE parameter.

(2)  If the procedure is still running when the next start is scheduled, the procedure is not started. The schedule will try to start the procedure again after another interval.

2.2   Print Scheduled Procedure (PGSPP)

The operation PGSPP prints a scheduled procedure in Dynamic Activation.

2.2.1   PGSPP Request

Command Description:

PGSPP:PROCEDURE=procedure;

The following table explains the attributes that can be used in a PGSPP request.

2.2.2   PGSPP Result

The PGSPP command gives a response including the attributes listed in Table 3. The following is an example of a PGSPP response:

72 ORDERED PGSPP

72 ID=LOCATION StartDate=20090101 Time=01:00 StopDate=20\
090101 Interval=100 Host=node1 Running=false

72 COMPLETED

Note:  

The Interval and Stopdate attributes is always printed, regardless if they have been initiated or not. The default value for the Interval attribute is 100 ms and the default value for the Stopdate attribute is the same value as set for the Startdate attribute.

(1)  The INTERVAL parameter is only valid if it is used together with STOPDATE parameter.

(2)  If the procedure is still running when the next start is scheduled, the procedure is not started. The schedule will try to start the procedure again after another interval.

2.3   Change Scheduled Procedure (PGSPC)

The operation PGSPC changes a scheduled procedure in Dynamic Activation.

2.3.1   PGSPC Request

Command Description:

PGSPC:PROCEDURE=procedure[,STARTDATE=date][,TIME=time][,STOPDATE=date][,INTERVAL=interval];

The following table explains the attributes that can be used in a PGSPC request.

(1)  If the procedure is still running when the next start is scheduled, the procedure is not started. The schedule will try to start the procedure again after another interval.

2.4   End Scheduled Procedure (PGSPE)

The operation PGSPE ends a scheduled procedure in Dynamic Activation.

Note:  

If a procedure is running, it is not ended. Only the scheduling is deleted.

2.4.1   PGSPE Request

Command Description:

PGSPE:PROCEDURE=procedure;

The following table explains the attributes that can be used in a PGSPE request.

3   Operations and Procedure Types

This section covers operations connected to procedures that can be scheduled for regular execution. The following procedures are supported:

• Print Mobile Subscriber Location Survey (HESPLSP), which uses the result of the procedure LOCATION.
• Print Mobile Subscriber Location Survey (HSSPMLP), which uses the result of the procedure MMELOCATION.

3.1   LOCATION and HESPLSP

HESPLSP returns the number of subscribers for each Visitor Location Register (VLR) or Serving GPRS Support Node (SGSN) address matching the ADDS and GPRS criteria.

The operation HESPLSP fetches data from the latest completed PGSPI:PROCEDURE=LOCATION search.

The PGSPI command with the procedure LOCATION fetches data from the CUDB. The data, that is stored in Dynamic Activation, can take a long time to fetch.

Note:  

The PGSPI command with PROCEDURE=LOCATION is to be run before the HESPLSP operation is executed. If not, the operation HESPLSP fails with fault message NO VLR/SGSN CACHE FILE FOUND

3.1.1   HESPLSP Request

Command Description:

             �    �
             �adds�
HESPLSP:ADDS=�    �[,GPRS][,CHAR][,OCSI][,RID=rid...];
             �ALL �
             �    �

The following table explains the attributes that can be used in a HESPLSP request.

3.1.2   HESPLSP Result File Schema

The following is the result file schema for HESPLSP:

<xsd:element name="MobileSubscriberLocationSurveyData">
	<xsd:complexType>
		<xsd:sequence>
			<xsd:choice minOccurs="0">
				<xsd:element name="VLRAddress" maxOccurs="unbounded">
					<xsd:complexType>
						<xsd:sequence>
							<xsd:element name="vlraddr" type="xsd:string" />
							<xsd:element name="nsub" type="xsd:integer" />
							<xsd:element name="char" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
							<xsd:element name="rid" type="xsd:integer" minOccurs="0" maxOccurs="unbounded" />
						</xsd:sequence>
					</xsd:complexType>
				</xsd:element>
				<xsd:element name="SGSNNumber" maxOccurs="unbounded">
					<xsd:complexType> 
						<xsd:sequence>
							<xsd:element name="sgsnnum" type="xsd:string" />
							<xsd:element name="nsub" type="xsd:integer" />
							<xsd:element name="char" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
							<xsd:element name="rid" type="xsd:integer" minOccurs="0" maxOccurs="unbounded" />
						</xsd:sequence>
					</xsd:complexType>
				</xsd:element>
			</xsd:choice>
			<xsd:element name="OCSI" minOccurs="0">
				<xsd:complexType> 
					<xsd:sequence>
						<xsd:element name="nsub" type="xsd:integer" />
					</xsd:sequence>
				</xsd:complexType>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
</xsd:element>

The following table covers the attributes that can be received in a HESPLSP response.

3.2   MMELOCATION and HSSPMLP

HSSPMLP returns the number of subscribers for each Mobility Management Entity (MME) address matching the ADDS criteria and the corresponding realm of the MME.

The operation HSSPMLP fetches data from the latest completed PGSPI:PROCEDURE=MMELOCATION search.

The PGSPI command with the procedure MMELOCATION fetches data from the CUDB. The data, that is stored in Dynamic Activation, can take a long time to fetch.

Note:  

The PGSPI command with PROCEDURE=MMELOCATION is to be run before the HSSPMLP operation is executed. If not, the operation HSSPMLP fails with fault message NO MME CACHE FILE FOUND.

3.2.1   HSSPMLP Request

Command Description:

             �    �
             �adds�
HSSPMLP:ADDS=�    �;
             �ALL �
             �    �

The following table explains the attributes that can be used in a HSSPMLP request.

3.2.2   HSSPMLP Result File Schema

The following is the result file schema for HSSPMLP:

<xsd:element name="MobilityManagementEntityLocationData">
	<xsd:complexType>
		<xsd:sequence>
			<xsd:choice minOccurs="0">
				<xsd:element name="MMEAddress" maxOccurs="unbounded">
					<xsd:complexType>
						<xsd:sequence>
							<xsd:element name="mmeaddr" type="xsd:string" />
							<xsd:element name="mmerealm" type="xsd:string" />
							<xsd:element name="nsub" type="xsd:integer" />
						</xsd:sequence>
					</xsd:complexType>
				</xsd:element>
			</xsd:choice>
		</xsd:sequence>
	</xsd:complexType>
</xsd:element>

The following table covers the attributes that can be received in a HSSPMLP response.

4   Faults or Errors

The CLI error codes can appear both directly in the prompt, and in the result files. Besides the generic and common error codes, the CLI commands can also return some more specific error codes.

4.1   General CLI Errors

The following table covers UDC HLR Activation Interface error codes. They can appear in any CLI responses.

4.2   Command Mapped Errors

This section covers UDC HLR/AUC Activation Interface errors that are mapped towards certain commands. The commands listed in this section can be assumed to be stopping, unless "(not stopping)" is stated. They are listed in the following table along with the commands that can return them.

4.3   HLR Errors

This section covers HLR errors that can be sent through UDC HLR/AUC Activation Interface. The error codes can only appear in certain commands. The commands listed in this section can be assumed to be stopping, unless "(not stopping)" is stated. The following table lists the HLR error codes for CLI.

Reference List