Links

GitHub

Open HUB

Quick Links

Download

STREAMS

SIGTRAN

SS7

Hardware

SCTP

Related

Package

Manual

FAQ

Library

SDLI Tech Spec

SDTI Tech Spec

SLI Tech Spec

MTPI Tech Spec

TRI Tech Spec

TCI Tech Spec

ISUPI Tech Spec

BICCI Tech Spec

MAPI Tech Spec

CDI Tech Spec

DLPI Tech Spec

NPI Tech Spec

TPI Tech Spec

WAN Tech Spec

LLI Tech Spec

NLI Tech Spec

CHI Tech Spec

MXI Tech Spec

MGI Tech Spec

XCC Tech Spec

XGCP Tech Spec

XMAP Tech Spec

Resources

Packages

Sys Req

Repositories

Download

Mailing Lists

Browse Source

CVS Archive

Bug Reports

Library

Hardware

Vendor Links

Home

Overview

Status

Documentation

Resources

About

News

XMAP Technical Specification

Description: OpenSS7 Project Library XMAP

A PDF version of this document is available here.

XOM Mobile Application Part (XMAP)

XOM Mobile Application Part (XMAP) Specification

About This Manual

This is Edition 1.20110510, last updated 2011-10-28, of The XOM Mobile Application Part (XMAP) Specification, for Version 1.1 release 1.20110510 of the OpenSS7 package.

Preface

Notice

Software in this document and related software is released under the AGPL (see GNU Affero General Public License). Please note, however, that there are different licensing terms for some of the manual package and some of the documentation. Consult permission notices contained in the documentation of those components for more information.

This document is released under the FDL (see GNU Free Documentation License) with no invariant sections, no front-cover texts and no back-cover texts.

Abstract

This document is a Specification containing technical details concerning the implementation of the XOM Mobile Application Part (XMAP) for OpenSS7. It contains recommendations on software architecture as well as platform and system applicability of the XOM Mobile Application Part (XMAP).

This document specifies a XOM Mobile Application Part (XMAP) Specification in support of the OpenSS7 Mobile Application Part (MAP) protocol stacks. It provides abstraction of the Mobile Application Part interface to these components as well as providing a basis for Mobile Application Part control for other Mobile Application Part protocols.

Purpose

The purpose of this document is to provide technical documentation of the XOM Mobile Application Part (XMAP). This document is intended to be included with the OpenSS7 STREAMS software package released by OpenSS7 Corporation. It is intended to assist software developers, maintainers and users of the XOM Mobile Application Part (XMAP) with understanding the software architecture and technical interfaces that are made available in the software package.

Intent

It is the intent of this document that it act as the primary source of information concerning the XOM Mobile Application Part (XMAP). This document is intended to provide information for writers of OpenSS7 XOM Mobile Application Part (XMAP) applications as well as writers of OpenSS7 XOM Mobile Application Part (XMAP) Users.

Audience

The audience for this document is software developers, maintainers and users and integrators of the XOM Mobile Application Part (XMAP). The target audience is developers and users of the OpenSS7 SS7 stack.

Revision History

Take care that you are working with a current version of this documentation: you will not be notified of updates. To ensure that you are working with a current version, check the OpenSS7 Project website for a current version.

A current version of this specification is normally distributed with the OpenSS7 package, openss7-1.1.1.20110510.1

Version Control

Although the author has attempted to ensure that the information in this document is complete and correct, neither the Author nor OpenSS7 Corporation will take any responsibility in it. OpenSS7 Corporation is making this documentation available as a reference point for the industry. While OpenSS7 Corporation believes that these interfaces are well defined in this release of the document, minor changes may be made prior to products conforming to the interfaces being made available. OpenSS7 Corporation reserves the right to revise this software and documentation for any reason, including but not limited to, conformity with standards promulgated by various agencies, utilization of advances in the state of the technical arts, or the reflection of changes in the design of any techniques, or procedures embodied, described, or referred to herein. OpenSS7 Corporation is under no obligation to provide any feature listed herein.

     $Log: xmap.texi,v $
     Revision 1.1.2.3  2011-07-18 19:42:14  brian
     - added documentation
     
     Revision 1.1.2.2  2011-02-07 02:21:48  brian
     - updated manuals
     
     Revision 1.1.2.1  2009-06-21 10:58:46  brian
     - added files to new distro
     

ISO 9000 Compliance

Only the TeX, texinfo, or roff source for this maual is controlled. An opaque (printed, postscript or portable document format) version of this manual is a UNCONTROLLED VERSION.

Disclaimer

OpenSS7 Corporation disclaims all warranties with regard to this documentation including all implied warranties of merchantability, fitness for a particular purpose, non-infrincement, or title; that the contents of the manual are suitable for any purpose, or that the implementation of such contents will not infringe on any third party patents, copyrights, trademarks or other rights. In no event shall OpenSS7 Corporation be liable for any direct, indirect, special or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action or contract, negligence or other tortious action, arising out of or in connection with any use of this documentation or the performance or implementation of the contents thereof.

U.S. Government Restricted Rights

If you are licensing this Software on behalf of the U.S. Government ("Government"), the following provisions apply to you. If the Software is supplied by the Department of Defense ("DoD"), it is classified as "Commercial Computer Software" under paragraph 252.227-7014 of the DoD Supplement to the Federal Aquisition Regulations ("DFARS") (or any successor regulations) and the Government is acquiring only the license rights granded herein (the license rights customarily provided to non-Government users). If the Software is supplied to any unit or agency of the Government other than DoD, it is classified as "Restricted Computer Software" and the Government's rights in the Software are defined in paragraph 52.227-19 of the Federal Acquisition Regulations ("FAR") (or any successor regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplerment to the FAR (or any successor regulations).

Acknowledgements

The OpenSS7 Project was funded in part by:

Thanks to the subscribers to and sponsors of The OpenSS7 Project. Without their support, open software like this would not be possible.

As with most open source projects, this project would not have been possible without the valiant efforts and productive software of the Free Software Foundation, the Linux Kernel Community, and the open source software movement at large.

1 Introduction

1.1 Overview

The XOM Mobile Application Part Application Programming Interface (abbreviated XMAP) defines an Application Program Inteface (API) to mobile application services. It is referred to as the interface throughout this specification.

The interface is designed to offer services that are consistent with, but not limited to, the 3GPP TS 29.002 and ITU-T Recommendation Q.711 standards. These standards were published in 1997 and have been stable for many years.

The interface is also designated to offer services that are consistent with the EIA/TIA ANSI-41D standards for CDMA mobile networks.

All of the above standards are referred to in this document as the Standards.

Access to other mobile application services through the API is not prohibited, but has not been explicitly considered.

The interface is designed to be used and implemented in conjunction with the use and implementation of the general-purpose XOM API (reference XOM).

A brief introduction to Mobile Application Services is given in Introductory Concepts. Following this is an overview of OSI-Abstract-DATA Manipulation OM, which provides the Data Abstraction service as defined in the XOM specification (reference XOM). Then the optional features of this specification are described, and the chapter closes with a list of abbreviations. In all cases the reader should refer to the Standards (reference TCAP, reference GSM MAP), or to the XOM Specification (reference XOM) for further authoritative details.

The structure of the remaining chapters and appendices are described in the Preface.

1.2 Format of the Specification

This specification describes a programming language-independent interface to the Mobile Application Services together with a specific C language binding of that interface. Several conventions are used to identify particular items. The general conventions are described in the Preface, while the C language binding conventions are described in C Language Binding.

1.3 Introductory Concepts

1.3.1 Relationship to MAP Protocols

The interaction between mobile application programs acting in a mobile application entity role are realized through the exchange of mobile application service information. The general communications service for the mobile applications is the Mobile Application Part. MAP defines the following operations:

Service Type

This communication may be accomplished using the ITU-T or ANSI Transaction Capabilities Application Part protocol.

1.3.2 XMAP and the MAP Provider

The XMAP interface provides access to the MAP service provider, which offers all of the facilities defined in the Standards. It also provides facilities such as automatic association management and automatic dialog handling. The interface is designed not to restrict the services offered to those of specific service packages of GSM MAP.

The interface defined in this specification is “symmetrical” in the sense that it can be used to implement mobile application programs acting in any of the MAP producer or consumer roles (e.g, HLR, VLR). The interface supports:

  • a mobile application program acting as a consumer of mobile application services. This is done by submitting service operation requests and receiving service operation responses.
  • a mobile application program acting as a producer of mobile application services. This is done by receiving service operation requests and sending back service operation responses.

The interface provides the ability to send requests on the consumer side and to receive indications on the producer side within a mobile service interaction. Furthermore, if the service is confirmed, the producer will be able to send back responses that will be received as confirmations by the consumer.

1.4 Relationship to GSM and ANSI MAP

The API is essentially based on the abstract services of the GSM MAP and ANSI MAP, but is independent of the underlying communications stack. The API allows the manipulation of ITU-T and ANSI mobile application service information. Thus this API does not preclude and does not force the use of either the GSM MAP protocol or the ANSI MAP protocol.

The XMAP API offers two abstract mobile application service views: the one of GSM and the one of CDMA.

The contents of GSM MAP messages are described in 3GPP TS 29.002. These messages implicitly define GSM MAP services. The mapping between GSM MAP services and various service primitives and parameters of the XMAP API are described below.

The services offered by the XMAP API are a superset of those defined both by GSM MAP and ANSI MAP. The general communication protocol for ANSI MAP is the TCAP as specified in ANSI T1.114/2000. The general communication protocol for GSM MAP is the TCAP as specified in ITU-T Recommendation series Q.771 through Q.775.

The two abstract mobile application views of XMAP (GSM MAP and ANSI MAP) are independent of the underlying protocol. However, the ITU-T view on top of ANSI TCAP requires that an appropriate mapping of GSM MAP services over ANSI TCAP is widely available.

1.5 Relationship to Data Abstraction Services

XMAP is dependent on standard data abstraction services to ensure portability of management software written to the XMAP specification. XMAP functions pass most arguments by reference. The data referenced by these arguments is modelled and manipulated in an object-oriented fashion. Mobile application data abstraction services are provided by the XOM API (reference XOM).

The definitions below introduce the various concepts that are used by Mobile Application data abstraction services.

Syntax
A syntax is the classification and representation of values in OSI-Abstract-Data Manipulation. Examples of syntaxes are Boolean, Integer, Real, String(Octet), String(Object-Identifier) and Object.
Value
A value is a single datum, or piece of information. A value may be as simple as a Boolean value (for example, True), or as complicated as an entire OM object (for example, a Message).
OM Attribute
An OM attribute type is an arbitrary category into which a specification places some values. An OM attribute is an OM Attribute Type, together with an ordered sequence of one or more values. The OM Attribute Type can be thought of as the name of the OM attribute.
OM Object
An OM object is a collection of OM attributes.
OM Class
An OM class is a category of OM objects set out in a specification. It determines the OM attributes that may be present in the OM object, and details the constraints on those OM attributes.
Package
A Package is a set of OM classes that are grouped together by the specification, because tey are functionally related (for example, GSM service package).
Package Closure
A Package-Closure is the set of classes that need to be supported to be able to create all possible instances of all classes defined in the package. Thus an OM Class may be defined to have an OM Attribute whose value is an OM Obejct of an OM Class that is defined in some other package, but within the same Package-Closure.
Workspace
A workspace is allocated storage that contains one or more Package-Closures, together with an implementation of the Mobile Application data abstraction services, that supports all the OM classes of OM objects in the Package-Closures.
Descriptor
A descriptor is a defined data structure that is used to represent an OM Attribute Type and a single value. The structure has three components: a type, a syntax and a value.
Public Object
Public Objects are represented by data structures that are manipulated directly using programming language constructs. Use of Public Objects therefore simplifies programming by this direct access and by enabling objects to be statically defined, when appropriate. Programs can efficiently access public objects.
Private Objects
Private Objects are held in data structures that are private to the service and can only be accessed from programs indirectly using interface functions. They are of particular use for structures that are infrequently manipulated by programs, being passed by reference to the service, which can then manipulate them efficiently. An example of such objects in XMAP is the session object.

1.6 Mandatory and Optional Features

The interface defines an Application Program Interface (API) that application programs can use to access the functionality of the underlying Mobile Application Services. The interface does not define or imply any profile of that service.

Note that nothing in this specification requires that the implementation of the interface or the Mobile Application Services itself actually makes use of TCAP or other parts of the model, just so long as it provides the defined service. Also, the scope of the Mobile Application Services to which an application has access is not determined; it is not restricted to GSM MAP operations.

Some OM attributes are optional: these are marked (Optional Functionality) in the OM class definitions. They are:

  • File-Descriptor in a Session object.

Some items of behaviour of the interface and a number of aspects of the Mobile Application Services provider are implementation-defined. These are:

  • the maximum number of outstanding asynchronous operations
  • whether an asynchronous function call returns before the operation is submitted to the Mobile Application Services provider
  • the text and language of error messages
  • the OM classes permitted as values of the Address and Title argument to interface functions.

The default values of some OM attributes on OM object Session are locally administered.

This API assumes the provision of automatic association management and automatic dialog handling by the MAP provider.

The interface enables negotiation of the use of the various defined features of the MAP provider and those of the interface.

1.7 Packages

The specification defines three Mobile Service packages (Common MAP package, GSM MAP package and ANSI MAP package), Interface Class Definitions. These packages define the OM classes required by the interface functions to perform GSM MAP or ANSI MAP services. The Common MAP package, which also includes the errors defined (see Errors), is mandatory. The GSM MAP package and the ANSI MAP package are optional, but at least one of them must be supported by the implementation. The ITU-T service view and the ANSI service view assume the support of the corresponding GSM MAP or ANSI MAP package by the implementation.

The use of the optional packages is negotiated using the Negotiate() function.

1.8 Terminology

The terms implementation-defined, may, should, undefined, unspecified, and will are used in this document with the meanings ascribed to them in reference XPG4, see also Glossary.

1.9 Abbreviations

API Application Program Interface
ANS.1 Abstract Syntax Notation One
ANSI American National Standards Institute
BER Basic Encoding Rules
GSM Global Services Mobile
ISO International Organisation for Standardisation
ITU-T International Telecommunications Union - Telecom Sector
MAP Mobile Application Part
OM OSI-Abstract-Data Manipulation
OSI Open Systems Interconnect
ROSE Remote Operations Service Element
TCAP Transaction Capabilities Application Part
XMAP XOM Mobile Application Part API
XOM X/Open: OSI-Abstract-Data Manipulation API

2 C Language Binding

This chapter sets out certain characteristics of the C language binding to the interface. The binding specifies C identifiers for all the elements of the interface, so that application programs written in C can access the Mobile Application Services. These elements include function names, typedef names and constants. All of the C identifiers are mechanically derived from the language independent names as explained below. There is a complete list of all the identifiers in C Headers. For ease of use, some of these identifiers are defined in the specification alongside the language-independent name.

A Function() is indicated as shown.

A CONSTANT is in Roman font.

The names of [[ERRORS]] and other return codes are surrounded by square brackets.

The definitions of the C identifiers appear in four headers:

<xom.h>
This header file contains definitions for the associated OM interface.
<xmap.h>
This header file contains common definitions for the access to the Mobile Application Part service (see Interface Functions, and Common MAP Package). A listing of this header file is provided in xmap.h.
<xmap_gsm.h>
This header file contains specific definitions that reflect the Abstract Services of the GSM Mobile Services along with the ASN.1 productions of the related protocol (GSM MAP), See GSM MAP Package. A listing of this header file is provided in xmap_gsm.h.
<xmap_ansi.h>
This header file contains specific definitions that reflect the Abstract Services of the ANSI Mobile Services along with the ASN.1 productions of the related protocol (ANSI MAP), See ANSI MAP Package. A listing of this header file is provided in xmap_ansi.h.
<xmap_gsm_sm.h>
This header file contains specific definitions that reflect the Short Message GSM services along with ASN.1 productions of the related services (GSM MAP Short Message services), See GSM Short Message Service Package. A listing of this header file is provided in xmap_gsm_sm.h.

2.1 C Naming Conventions

The interfaces uses part of the C public namespace for its facilities. All identifiers start with the letters map, MAP or OMAP, and more detail of the conventions used are given in the following table. Note that the interface reserves all identifiers starting with the letters mapP for private (i.e. internal) use by implementations of the interface. It also reserves all identifiers starting with the letters mapX or MAPX for vendor-specific extensions of the interface. Application programmers should not use any identifier starting with these letters.

The OSI-Abstract-Data Manipulation API uses similar, though not identical, naming conventions, that are described in XOM (reference XOM). All its identifiers are prefixes by the letters OM or om.

reserved for implementors mapP
reserved for interface extensions mapX
reserved for interface extensions MAPX
reserved for implementors OMAP

functions map_
error problem values MAP_E_
enumeration tags (except errors) MAP_T_
OM class names MAP_C_
OM value length limits MAP_VL_
OM value number limits MAP_VN_
other constants MAP_

A complete list of all identifiers used (except those beginning mapP, mapX, MAPX or OMAP) is given in C Headers. No implementation of the interface will use any other public identifiers. A public identifier is any name except those reserved in section 4.1.2.1 of the ISO C Standard, and the public namespace is the set of all possible public identifiers.

The C identifiers are derived from the language-independent names used throughput this specification by a purely mechanical process which depends on the kind of name:

  • Interface function names are made entirely lower-case and prefixed by map_. Thus Service-Req() becomes map_service_req().
  • C function parameters are derived from the argument and result names by making them entirely lower-case. In addition, the names of results have _return added as a suffix. Thus the argument Session becomes session, while the result of Result becomes result_return.
  • OM class names are made entirely upper-case and prefixed by MAP_C_. Thus Service-Argument becomes MAP_C_SERVICE_ARGUMENT. Note that the symbolic OM class names are strictly those used in the abstract syntax ASN.1 of the TCAP and MAP with the exception that names containing multiple words are separated by hyphens.
  • Enumeration tags are derived from the name of the corresponding OM type and syntax by prefixing MAP_. The case of letters is left unchanged. Thus Enum(User-reason) befomes MAP_User_reason.
  • Enumeration constants, except erros, are made entirely upper-case and prefixed by MAP_T_. Thus resource-limitation becomes MAP_T_RESOURCE_LIMITATION.
  • The name of an OM attribute is local to its OM class, that measn the same name of an OM attribute may appear in different OM classes, for example, OM attribute application-Context is defined in both OM classes Open-Arg and application-Context-List. Independent-language atribute application-Context appears as MAP_APPLICATION_CONTEXT in C-language. Note that the symbolic OM attribute names are strictly those used in the abstract syntax ASN.1 of the TCAP and MAP with the exception that names containing multiple words are separated with hyphens.
  • Errors are treated as a special case. Constants that are the possible values of the OM attribute Error-Status of a subclass of the OM class Error are made entirely upper-case and prefixed by MAP_E_. Thus invalid-session becomes MAP_E_INVALID_SESSION.
  • The constants in the Value Length and Value Number columns of the OM class definition tables are also assigned identifiers. (They have no names in the language-independent specification.) Where the upper limit in on eof these columns is not “1” (one), it is given a name consisting of the OM attribute name, prefixed by MAP_VL_ for value length, or MAP_VN_ for value numbers.
  • The sequence of octets for each object identifier is also assigned an identifier, for internal use by certain OM macros. These identifiers are all upper case and are prefixed by OMP_O_. See reference XOM for further details on the use of object identifiers.

    Note that hyphens are translated everywhere to underscores.

2.2 Use and Implementation of Interfaces

Each of the following statements applies unless explicitly state otherwise in the detailed descriptions that follow:

If an argument to a function has an invalid value (such as a value outside the domain of the function, or a pointer outside the address space of the program, or a null pointer), the behaviour is undefined.

Any function declared in a header may be implemented as a macro defined in the header, so a library function should not be declared explicitly if its header is included. Any macro definition of a function can be suppressed locally be encoding the name of the function in parentheses, because the name is not then followed by the left parentheses that indicate expansion of a macro function name. For the same syntactic reason, it is permitted to take the address of a library function even if it is also defined as a macro. The use of #undef to remove any macro definition will also ensure that an actual function is referred to. Any invocation of a library function that is implemented as a macro will expand to code that evaluates each of its arguments exactly once, fully protected by parentheses where necessary, so it is generally safe to use arbitrary expressions as arguments. Likewise, those function-like macros described in the following sections may be invoked in an expression anywhere a function with a compatible return type could be called.

2.3 Function Return Values

The return value of a C function is always bound to the result of the language-independent description. Functions return a value of MAP_status, which is an error indication. If and only if the function succeeds, its value will be success, expressed in C by the constant MAP_SUCCESS. If a function returns a status other than this, then it has not updated the return parameters. The value of the status, in this case, is an error as described in Errors. In most cases the integer returned in Status is sufficient for error processing. However, in a few cases additional information is available if desired.

Since C does not provide multiple return values, functions must return all other results by writing into storage passed by the application program. Any argument that is a pointer to such storage has a name ending with _return. For example, the C parameter declaration ‘OM_sint *invoke_id_return’ in the Service-Req() function indicates that the function will return an signed integer Invoke-Id as a result, so the actual argument to the function must be the address of a suitable variable. This notation allows the reader to distinguish between an input parameter that happes to be a pointer, and an output parameter where the <*> is used to simulate the semantics of passing by reference.

2.4 Compilation and Linking

All applications programs that use this interface include the <xom.h> and <xmap.h> headers in that order, and at least one of the <xmap_gsm.h> and <xmap_ansi.h> headers.

3 Description

The interface comprises a number of functions together with many OM classes and OM objects that are used as the arguments and results of the functions. Both the functions and the OM objects are based closely on the Abstract Service that is specified in the Standards (references GSM MAP and ANSI MAP).

The interface models mobile application interactions as service requests made through a number of interface functions, which take a number of input arguments. Each valid request causes an operation within the producer which eventually returns a status and any result of the operation.

All interactions between a Consumer and a Producer belong to a session, which is represented by an OM object passed as the first argument to most interface functions.

The other arguments to the function include a context and various service-specific arguments. The context includes a number of parameters that are common to many functions and that seldom change from operation to operation.

Each of the components of this model is described below, along with other features of the interface such as asynchronous function calls and security.

3.1 Services

As mentioned above, the Standards define Abstract Services that Consumers and Producers use. Each of these Absract Services maps to a single function call with the same name. The services are Service-req and Service-rsp.

These are three functions called Receive(), Wait(), and Abandon() which have no counterpart in the Abstract Service. Receive() is used to receive indications and results of asynchronous operations, and is explained in Interface Functions. Wait() is used to suspend execution until indications are available for specified sessions. Abandon() is used to abandon locally the result of a pending asynchronous operation. Two additional functions Bind()2 and Unbind() are used to open and close a user-session.

There are also other interface specific functions called Get-Assoc-Info(), Get-Last-Error(), Validate-object(), Error-Message(), Initialize(), Shutdown() and Negotiate().

The detailed specifications are given in Interface Functions.

3.1.1 Negotiation Sequence

The interface has an initialize and shutdown sequence that permits the negotiation of optional features. This involves the functions Initialize(), Negotiate(), and Shutdown().

Every application program must first call Initialize(), that returns a workspace. This workspace supports only the standard Common MAP package, See Interface Class Definitions.

The workspace can be extended to support either the GSM MAP or ANSI MAP package or both (see Interface Class Definitions, and any combination of the optional Mobile Application Services packages), or any vendor extensions. Vendor extensions may include additional packages, and may also include additional or modified functionality. All such packages or other extensions are identified by means of OSI Object Identifiers, and the Object Identifiers are supplied to the Negotiate() function to incorporate the extensions into the workspace. Features defined by this specification are described and assigned Object Identifiers in Interface Functions. A feature represents any package or any additional or modified functionality that is subject to negotiation. The Negotiate() function allows some particular features to be made available.

After a workspace with the required features has been negotiated in this way, the application can use the workspace as required. It can create and manipulate OM objects using the OM functions, and can start one or more management sessions using Bind().3 All the sessions on a given workspace share the same features.

Eventually, when it has completed its tasks, terminated all its mobile application sessions using Unbind(), and released all its OM objects using OM-Delete(), the application should ensure that resources associated with the interface are freed by calling Shutdown().

A miscellaneous error arises if an attempt is made to use an unavailable feature. If an instance of a class that is not in an available package is supplied as a function argument, the bad-class error arises.

3.1.2 Names, Addresses and Titles

To address a wide variety of mobile application transport protocols the interface is capable of accepting various forms of object names, system addresses and program or system titles.

  • Name is an “abstract class” that contains various subclass types used to define specific subscribers or systems responsible for producing mobile application services.
  • Address is an “abstract class” that contains various subclass types used to define the specific location to contact a particular consumer or producer of mobile services. For example, the SCCP-Address subclass is typically used to define the location of a producer or consumer.
  • Title is an “abstract class” that contains various subclass types used to define a specific subscriber or system name responsible for producing mobile application services.

All three abstract classes participate in an implementation-specific name resolution scheme. It is assumed that given a Name, an implementation can determine the Title responsible for that Name. It is also assumed that given a Title, an implementation can determine the Address of that Title.4

The producer of an invoked operation may be explicitly designated at the interface boundary using the following precedence rules:

  1. A default Title or Address may be supplied as parameters to a bound “session”. If both are provided, the implementation will verify that the Title resolves to the Address.
  2. If automatic association management is used, a provider Title or Address may be supplied as parameters within the “context” or a specific operation request. If both are provided, the implementation will verify that the Title resolves to the Address. The “context” Title or Address takes precedence over the “session” Title or Address for unassociated session objects.
  3. A consumer address may be supplied as a parameter within the “argument” of a specific operation request. The “argument” Address takes precedence over either the “session” Title or Address or the “context” Title or Address.
  4. If the producer of an invoked operation is not explicitly designated at the interface boundary, the implementation will resolve the Name to the appropriate Title or Address.

3.2 Session

A session identifies to which mobile application entity a particular operation will be sent. It contains some Bind-Arguments, such as the name of the consumer. The session is passed as the first argument to most interface functions.

A session is described by an OM object of OM class Session. It is created, and appropriate parameter values may be set, using the OSI-Abstract-Data Manipulation functions. A mobile application session is then started with Bind()5 and later is terminated with Unbind(). A session with default parameters can be started by passing the constant Default-Session (‘(OM_object)MAP_DEFAULT_SESSION’) as the Session argument to Bind().

Bind() must be called before the Session can be used as an argument to any other function in the interface. After Unbind() has been called, Bind() must be called again if another session is to be started.

The interface supports multiple concurrent sessions, so that an application implemented as a single process, such as a server in a client-server model, can interact with the Mobile Application Services using several identities; and so that a process can interact directly and concurrently with different mobile application services.

Detailed specifications of the OM class Session are given in Interface Class Definitions.

A session can be used either acting as a consumer of mobile application services, or acting as a producer of mobile application services, or both.

A session can be restricted for use only with a designated program called the responder. When the responder is omitted and automatic association management is used, the session can be used to exchange mobile application service information with all processes.

The responder (title and address) parameters of an opened session, if present, specifies the producer of the requested operation. The precedence rules on address and title of the responder are described in Names.

Other OM attributes (vendors' implementation extensions) may be included to specify characteristics of the underlying protocol used.

There are three type of session objects:

3.2.1 AAM Enabled Session

The Session collects together all the information that described a particular management interaction. The parameters that are to control such a session are set up in an instance of this OM class, which is then passed as an argument to Bind().6 This sets the OM attributes that describe the actual characteristics of the session, and starts the session. Such a started session can be passed as the first argument to interface functions.

No attribute of a bound or connected session may be changed. The result of modifying a started session is unspecified.

Finally, Unbind() is used to terminate the session, after which the parameters can be modified and a new session started using the same instance, if required. Multiple concurrent sessions can be run, by using multiple instances of this OM class.

A session allows a requesting program (the requester) to exchange mobile application information with another program designated (the responder) or by default to all programs.

An AAM enabled session thus allows a mobile application entity to access either a portion of the mobile application services (that is, that are accessible via the designated responder) or all mobile application services. In the later case, the producer mobile application entity resolution is performed by the Mobile Application Service provider, according to the mobile application services invoked.

This type of session object can not be used to receive or send ACSE related primitives or operations explicitly. To use ACSE explicitly, see AAM Disabled Session.

3.2.2 AAM Disabled Session

A session object can have Automatic Association Management disabled when it belongs to a workspace that has Automatic Association Management disabled via Negotiate(), which allows the user to explicitly send and receive ACSE operations to build and tear down associations. It gives explicit control over associations to the user. The Mobile Application Service provider does no ACSE operations on behalf of the user.

When the user creates and binds a session object in a workspace with AAM disabled, only the following attributes within the session object can be specified:

  • requestor-Address
  • requestor-Title

The session object is then passed as an argument to Bind(),7 which binds the session. This bound session can only be used to send ACSE related operations an to receive ACSE related primitives. The following can be sent/received using this type of bound session:

  • Receive() (map_receive()/‘MAP_ASSOC_IND’)
  • Receive() (map_receive()/‘MAP_ASSOC_CNF’)
  • Assoc-req() (map_assoc_req())
  • Assoc-rsp() (map_assoc_rsp())

The other attributes that relate to ACSE are specified within an Assoc-Argument or Assoc-Result object that is passed to, or returned from, Assoc-req(), Assoc-rsp(), or Receive().

3.2.3 Associated Session

Once a user has created a bound session that has AAM disabled, an association can be created. An association is represented by an associated or partially associated session object. An associated session is returned as the result of building a new association. The associated session is used, like a bound session, by sending and receiving mobile application dialog handling or service operations. The major difference is that an associated session object can only be used to send and receive operations to, or from, a single remote mobile application entity. After a session is associated, the user can abort the association, which implicitly unbinds the associated, or partially associated, session.

The precedence rules for common parameters within the Session and the Context objects are different for associated session objects. Once a session is in the associated state; the responder-Address and responder-Title cannot be overridden by the context object.

To terminate this type of session, the user should either abort the session, which implicitly unbinds the session. If the user unbinds the associated session prior to aborting the association, the service provider will abort the association.

3.2.4 ADH Enabled Session

The ADH enabled session allows a mobile application entity to invoke and respond to mobile application services requests and indications without regard for dialog handling. The Mobile Application Service provider provides all dialog handling.

This type of session cannot be used to send dialog handling primitives or operations explicitly. To use dialog handling explicitly, see ADH Disabled Session.

3.2.5 ADH Disabled Session

A session object can have Automatic Dialog Handling disabled when it belongs to a workspace that has Automatic Dialog Handling disabled using the Negotiate() function. This allows the user to explicitly send and receive dialog handling operations to establish and tear down dialogs. It gives explicit control over dialogs to the user. The Mobile Application Service provider does no dialog handling operations on behalf of the user.

Once the session object is bound (AAM enabled) or associated (AAM disabled) and has ADH disabled, the session must explicitly issue dialog handling operations for each mobile application service request or response. This bound or associated session can only be used to send dialog handling primitives. The following can be sent/received using this type of bound or associated session:

  • Receive() (map_receive()/‘MAP_OPEN_IND’)
  • Receive() (map_receive()/‘MAP_ACCEPT_CNF’)
  • Receive() (map_receive()/‘MAP_REFUSE_CNF’)
  • Open() (map_open())
  • Accept() (map_accept())
  • Refuse() (map_refuse())

The other attributes that relate to dialog handling are specified within the Open-Argument, Accept-Result or Refuse-Result objects that are passed to, or returned from, Open(), Accept(), Refuse(), or Receive().

3.2.6 Dialog Session

Once a user has created a bound or associated session that has ADH disabled, a dialog can be created. A dialog is represented by a fully formed, or partially formed dialog, session object. A dialog session is returned as the result of building a new dialog. The dialog session is used, like a bound or associated session, by sending and receiving mobile application service operations. The major difference is that a dialog session object can only be used to send and receive operations within a single dialog with a single remote mobile application entity. After a session forms a dialog, the user can close or abort the dialog, which returns the session to the bound or associated state.

The precedence rules for common parameters within the Session and the Context objects are different for dialog session objects. Once a session has formed a dialog, the dialog related arguments, application-Context-Name, cannot be overridden by the context object.

To terminate this type of session, the user should either abort or close the dialog, which implicitly unbind the session. If the user unbinds the dialog session prior to either closing or aborting the dialog, the service provider will first attempt to close the dialog, and if that is rejected, will abort the dialog.

3.3 Context

The context defines the characteristics of the mobile application interaction that are specific to a particular mobile application operation, but are often used unchanged for many operations. Since the parameters are presumed to be relatively static for a given user during a particular mobile application interaction, these arguments are collected into an OM object of OM class Context, which is supplied as the second argument of each mobile application operation. This serves to reduce the number of arguments passed to each function.

The context includes various administrative details, such as the mode defined in the Abstract Service, which affect the processing of each mobile application operation. These include a number of Service Controls and Local Controls that allow control over some aspects of the operation. The Service Controls include mode, responder-Address, and responder-Title. The Local Controls include asynchronous, reply-Limit and time-Limit. Each of these is mapped onto an OM attribute in the Context, and they are detailed in Interface Class Definitions.

The effect is as if they were passed as a group of additional arguments on every function call. The value of each component of the context is determined when the interface function is called, and remains fixed throughout the operation.

The precedence rules on address and title of the responder are described in Names.

Some of the OM attributes in the Context have default values, some of which are locally adminstered. The constant Default-Context (‘MAP_DEFAULT_CONTEXT’) can be pased as the value of the Context argument to the interface functions, and has the same effect as a context OM object created with default values. The context must be a private object, unless it is Default-Context.

Detailed specifications of the OM class Context are given in Interface Class Definitions.

3.4 Function Arguments

The Abstract Service defines specific arguments for each operation. These are mapped onto corresponding arguments to each interface function (which are also called input parameters). Although each service has different arguments, some specific arguments recur in several operations; these are briefly introduced here. As far as the GSM MAP package is concerned, OM classes are defined with a one-to-one mapping to the ASN.1 Abstract Syntax of GSM MAP. Full details of these and all the other arguments are given in the function definitions in Interface Functions, and the OM class definitions in Interface Class Definitions.

All arguments that are OM objects can generally be supplied to the interface functions as public objects (i.e, descriptor lists) or as private objects. Private objects must be created in the workspace that was returned by Initialize(). In some cases, constants can be supplied instead of OM objects.

Note that wherever a function is stated as accepting an instance of a particular OM class as the value of an argument, it will also accept an instance of any subclass of that OM class. For example, the Service-Req function has a parameter argument, which accepts values of OM class Service-Argument. Any of the subclasses of Service-Argument may be supplied as the value of argument.

Rules for interpretation of ‘ANY’ syntax appearing in function arguments are defined in Encoding and Decoding.

3.4.1 Encoding and Decoding

XMAP specifies two alternatives for encoding and decoding of Mobile Application Packages OM-Attribute values of type ‘ANY’, or any OM-Attribute values in a Mobile Application Services package.

  1. The encoding and decoding functionality can be provided internally with the XMAP API, without requiring the application to invoke any encoding or decoding functions. This option allows the application to be free from any knowledge of encoding rules. In this case, the OM class and attribute type and corresponding representation are defined in a mobile application or services package. The XMAP API uses the package definition to attempt encoding or decoding; if automatic decoding fails, an OM String(Encoding) is used.
  2. The application can perform encoding and decoding itself. This option gives the application responsibility and control over the encoding and decoding of OM attributes. In this case, all OM attribute values appear as an OM String(Encoding).

The encoding and decoding alternative to be used is negotiated through the Negotiate() function; See Negotiate.

The XMAP API does not specify the use of OM-Encode or OM-Decode for the OM classes defined in this specification, or in mobile application or services packages used with this specification.

To ensure interoperability, the sender and receiver must follow the same encoding rules when converting between OM syntax and encoded syntax. If an algorithm is used to generate OM packages, then the algorithm must ensure that the generated OM syntax is consistent with the input abstract syntax (that is, the same encoded values must result from applying the encoding rules to either representation). The encoding rules used with the GSM MAP and ANSI MAP packages defined by this specification are ANS.1 BER. This does not imply that other encoding rules cannot be used with other packages defined in the future.

For the API to encode and decode the OM attribute values according to the ASN.1 standard scheme, ASN.1 tagging information must be stored for each OM object and each OM attribute. Thus, the package definitions in the workspace need to incorporate the ASN.1 tagging information for each OM object and each OM attribute definition for all Mobile Application Services packages.

As a minimum, the following requirements apply:

  • All rules specified in ISO/IEC 8825 – Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1) shall be adhered to. Any exceptions or restrictions must be stated.
  • ASN.1 tagging information must be retained for each OM object and each OM attribute in the Mobile Application Services packages.
  • The specified encoding and decoding scheme (and any implementation thereof) should be extensible to accommodate the new encoding rules established subsequent to ISO/IEC 8825.

3.4.2 Argument and Response

Most operations and notifications take an argument to specify the argument of the operation and a response when issuing the response of the operation. These arguments and responses are specified to accept values of OM classes that are consistent with the abstract service view (GSM MAP or ANSI MAP) of the current operation.

The argument for a Service-req() function is represented by an instance of the OM Class GSM-Service-Req-Argument for a GSM MAP operation or an instance of the OM Class ANSI-Service-Req-Argument for an ANSI MAP operation.

The reponse for a Service-rsp() function is represented by an instance of the OM Class GSM-Service-Result, GSM-Linked-Reply-Argument Service-Error or GSM-Service-Reject to represent the possible responses of the GSM service request operation, or an instance of the ANSI-Service-Result, ANSI-Linked-Reply-Argument Service-Error or ANSI-Service-Reject to represent the possible responses of the ANSI service request operation.

3.5 Function Results

All functions return a Status (which is the C function result). Most return an Invoke-ID which identifies the particular invocation. The confirmed operations each return a Result. (The Invoke-ID and Result are returned using pointers that are supplied as arguments of the C function). These three kinds of function results are introduced below.

All OM objects returned by interface functions (results and errors) will be private objects in the workspace associated with the session private object.

3.5.1 Invoke-ID

All interface functions that invoke a mobile application service operation return an Invoke-ID; an integer that identifies the particular invocation of an operation. The Invoke-ID is only relevant for asynchronous confirmed operations and may be used later to receive the Status and Result, or to abandon them. The Invoke-ID is also used to respond to a previously requested confirmed operation. Asynchronous operations are fully described in Synchronous and Asynchronous Operation. The interface functions that can be used to start them are the Service-req() function.

The numerical value of the invoke-Id returned from a call that successfully invoke an asynchronous confirmed operation is guaranteed to be unique amongst all outstanding operations in given session. The value is such as could be returned from TCAP, the Transaction Capabilities Application Part defined in ITU-T Recommendation Q.771 through Q.775. Invoke IDs used by XMAP are not necessarily those that are actually sent via a protocol such as TCAP. Invoke IDs may be mapped or altered by the Mobile Application Service provider.

The value returned for a synchronous operation or an asynchronous non-confirmed operation is unspecified, as is that for a call that fails to invoke an operation.

3.5.2 Result

Functions invoking confirmed mobile application service operations return a result only if they succeed. All errors from these functions are reported in the Status described below, as are errors from all other functions.

The value returned by a function call that invokes an asynchronous operation is unspecified, as is that for a call that fails to invoke an operation. The result of an asynchronous operation is returned by a later call to Receive().

The result of a function invoking a confirmed operation can be composed of a single reply, or of multiple linked replies. In the later case, the term partial result is used to designate one of these linked replies. Only a confirmed Service-req may produce multiple results. Multiple replies to a single mobile application service operation may only occur if the invoker specifies multiple-reply in the functional unit attribute of the Session object.

In asynchronous mode, the partial results can be retrieved one at a time by subsequent calls to Receive(), which each time returns an instance of OM class Linked-Reply-Argument. In synchronous mode, the function returns an instance of OM class Multiple-Reply, which contains a list of sub-objects of OM class Linked-Reply-Argument.

The result (or partial result) of an operation is returned in a private object whose OM class is appropriate to the particular operation. The format of mobile application service operation results is driven both by the Abstract Service and by the need to provide asynchronous execution of functions. To simplify processing of asynchronous results, the result (or partial result) of a single operation is returned in a single OM object (corresponding to the abstract result defined in the Standards). The components of the result (or partial result) of an operation are represented by OM attribute in the operation's result object. All information contained in the Abstract Service result is made available to the application program. The result (partial result) is inspected using the functions provided in the OSI-Abstract-Data Manipulation API.

Only confirmed mobile application service operations produce results, and each type of operation has a specific OM class of OM object for its result. These OM classes are defined in Interface Class Definitions.

The actual OM class of the result can always be a subclass of that named, to allow flexibility for extensions. Thus, the function OM-Instance() should always be used when testing the OM class.

3.5.3 Status

Every interface function returns a Status value, which is either the constant success (‘(MAP_status)0’ or ‘MAP_SUCCESS’) or an error. Function call errors are represented as integer constants and grouped in categories of System, Library and Communications as described in Errors.

Additional error information is available for System and Communications errors via the Get-Last-Error() function call. Additional error information is available for the bad-argument Library error via the Validate-object() function call.

A synchronous call with multiple linked replies is considered successful unless the reply limit or time limit is exceeded. The function returns a Status value equal to success, and the argument Result is an OM object of OM class Multiple-Reply, which contains all the linked replies.

It should be noted that OM object Linked-Reply-Argument may contain an OM attribute that reflects an error.

If the reply limit or time limit is exceeded, the synchronous call fails and returns a status of the appropriate Library error. However, the Result is still considered valid and may contain an OM-Object Multiple-Reply, which contains all the received linked replies. A result of MAP_ABSENT_OBJECT means no replies were received.

In most cases other results of functions are initialized to Null (MAP_ABSENT_OBJECT) if the status does not have the value success. However, the Result is still considered valid and may contain an OM-Object of partial replies. A result of MAP_ABSENT_OBJECT means no replies were received.

3.6 Synchronous and Asynchronous Operation

The asynchronous or synchronous mode of a requested operation is specified at the interface, and determined for each operation by the value of the OM attribute Asynchronous in the Context passed to the interface function. The default value of this OM attribute is false, causing all operations to by synchronous. Support for both synchronous and asynchronous operation is mandatory. There is a limit to the number of pending asynchronous operations; this limit is given by the constant max-outstanding-operations, and has a minimum value of 10.

In synchronous mode, all functions wait until the operation is complete before returning. Thus the thread of control is blocked within the interface after calling a function, and the application can make use of the result immediately after the function returns.

In asynchronous mode, some functions return before the operation is complete. The application is then able to continue with other processing while the operation is being executed by the Mobile Application Service provider, and can then access the result by calling Receive(). An application may initiate several concurrent asynchronous operations on the same session before receiving any of the results, subject to the limit described below. The results are not guaranteed to be returned in any particular order. The functions that can execute asynchronously are the Service-req() function. This corresponds to the mobile application services of the Standards that operate in a confirmed mode. Moreover, only confirmed operations return service results.

An asynchronous function call of a confirmed service returns an Invoke-ID of the operation to the application. The same Invoke-ID will be returned by Receive() on the corresponding result.

An Invoke-ID is also returned by Receive() on an indication of an invoked mobile application service operation. The same Invoke-ID will be used to respond to this operation.

Implementations of the interface are free to return from asynchronous function calls as soon as possible or may wait until the operation has been submitted to the underlying Mobile Application Service provider. The actual policy used is implementation-defined.

Implementations will define a limit to the number of asynchronous operations that may be outstanding at any one time on any one session. An asynchronous operation is outstanding from the time that the function is called until the last reply of the result is returned by Receive(), or the operation is abandoned by Abandon(), or the session is closed by Unbind(). The limit is given by the constant max-outstanding-operations (‘MAP_MAX_OUTSTANDING_OPERATIONS’) and is at least 10 for conforming XMAP implementations. While this number of operations is outstanding, attempts to invoke further asynchronous operations will report a Library-Error (too many operations).

Asynchronous operation calls can be aborted by executing an Abandon() or Unbind() call. In this case, the operation is no longer outstanding and the result will never be returned by further Receive() function calls.

If an error is detected before an asynchronous request is submitted to the Mobile Application Service provider, the function will return immediately and there will be no outstanding operation generated. Other errors are notified later by Receive(), when the result of the outstanding asynchronous confirmed operation is returned. All errors occurring during a synchronous request are reported when the function returns. Full details of error handling are given in Errors.

Where vendors provide suitable system primitives (such as System V poll(2s), or BSD select(2)), applications can obtain a file descriptor from the Session by inspecting the value of the OM attribute File-Descriptor. Applications may use the file descriptor to suspend the process until data is received on the particular file descriptor.

Applications should ensure that there are no outstanding asynchronous operations on a session when Unbind() is called on that session. Once Unbind() has been called there is no way to determine whether any outstanding operations succeed or even whether they were ever sent to the Mobile Application Service provider. Also no errors or results of any kind will be reported to the application. It is strongly recommended that Receive() is called repeatedly until Completion-Flag takes the value nothing.

3.7 Other Features

These features are not part of the interface itself, but are mandatory when specified by the Mobile Application Service provider.

The Mobile Applications are not restricted to those defined by GSM MAP.

All the features listed below are for the most part necessary for ease of use in a mobile application environment. These features are classified as given registered identifiers (Object Identifier). They can be negotiated using the Negotiate() function in the same manner as packages. Other types of information that are critical in servicing an environment that includes implementation from multiple vendors on various machines can also be classified and handled with the Negotiate() function. Features defined by this specification are described and assigned Object Identifiers in Interface Functions.

3.7.1 Automatic Association Management

When the Mobile Application Services provider makes use of association oriented communication services, such as TCAP, the Mobile Application Service provider implementations are assumed to provide automatic handling of the association between mobile application entities, establishing and releasing associations at its discretion. Such management is intended to bring benefits such as reduced communication charges. To allow this flexibility to the implementation, the interface does not specify when communication takes place. Automatic Association Management (AAM) may be enabled or disabled on a per-workspace basis using the Negotiate() function.

3.7.2 Automatic Dialog Handling

When the Mobile Application Services provider makes use of dialog oriented communication services, such as that provided by TCAP, the Mobile Application Service provider implementations are assumed to provide automatic handling of dialogs between mobile application entities, establishing and releasing dialogs at its discretion. Such management is intended to bring benefits such as reduced communication overheads. To allow this flexibility to the implementation, the interface does not specify when communication takes place. Automatic Dialog Handling (ADH) may be enabled or disabled on a per-workspace basis using the Negotiate() function.8

3.7.3 Automatic Performer Resolution

The performer of an invoked operation may be explicitly designated by the responder name and responder address parameters of the bound session used.

However, in the case where the responder is specified as a wildcard, the Mobile Application Service provider may be assumed to provide automatic mobile application service and application context to consumer resolution: to find out the consumer that is in charge of the selected mobile application service specified in the mobile application service operation.

3.7.4 Responder Versatility

Responder versatility is the ability to change the consumer within a same bound-session at each function call. It is useful when the automatic consumer resolution is either not supported by the Mobile Application Service provider or not requested. This applies if the underlying Mobile Application Service provider is connection-less.

3.7.5 Automatic Name to Address Resolution

Mobile Application Service provider implementation may provide automatic resolution between program name and address to find the network address of a mobile application entity from its name using directory or translation services.

3.7.6 Automatic Dispatching to Appropriate Stack

The Mobile Application Services provider implementation may provide a loop back facility if the destination of the operation or notification is local. It also may provide routing of the mobile application services operation to the proper underlying communications stack according to the implied mobile application service and the destination (for example over a ITU-T SCCP stack or an ANSI SCCP stack).

3.8 Function Sequencing

A minimum set of sequencing rules applies when using the interface to exchange mobile application service information between mobile application programs acting as a mobile application entity. These rules need to be respected by mobile application programs to ensure that interface functions are called in the proper sequence and that the state of the interface is not violated, otherwise Library-error status will be returned.9

The general rules to follow are:

  1. Initialize a workspace (‘map_initialize()’)
  2. Negotiate features of the interface (‘map_negotiate()’)
  3. Open one or several sessions (‘map_bind()’)
  4. Perform mobile application service interactions (operations) using the offered interface functions. An interaction is identified by its Invoke-Id.
  5. Close the opened sessions (‘map_unbind()’)
  6. Discard the workspace (‘map_shutdown()’)

Seven states are defined in the interface to cover both interface service operations and mobile application service interactions:

UNINIT
Workspace uninitialized.
INIT
Workspace initialized.
UNBND
Session closed.
BND
Session opened.
IDLE
OUTOP
Outstanding operation requested in a mobile application service interaction.
OPIND
Operation indication received in a mobile application service interaction.

4 Interface Functions

4.1 Abandon()

NAME
Abandon – abandon locally the result of a pending asynchronous operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_abandon(
             OM_private_object  session,
             OM_sint32          invoke_id
     );

DESCRIPTION
This function abandons the result of an outstanding asynchronous function call. The function is no longer outstanding after this function returns, and the result (or the remaining results in case of multiple linked replies) will never be returned by Receive().

Abandon() may, but need not, cause the Mobile Application Service provider to abandon the outstanding asynchronous operation itself (as opposed to simply discarding the result). Note that the specified behaviour is a local mater, and no statement is made about underlying mobile application service operations that may or may not be abandoned.

This function can only be called in synchronous mode.

ARGUMENTS
Session (Object(Session))
The mobile application session in which the confirmed operation was requested. This must be a private object previously returned from Bind().10
Invoke-ID (Integer)
Selects the specific outstanding asynchronous operation submitted via the Session to be terminated. The outstanding operation may be a non-confirmed service. In that case the abandon is without effect. The value of Invoke-ID must be that which was returned by the function call that initiated the asynchronous management operation that is now to be abandoned.

RESULTS
Status (Status)
Indicates whether or not the abandon function succeeded.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-session, bad-procedural-use, miscellaneous, session-terminated.

This function can return a Communications-Error.

Note that the abandon function is successful even if the operation to be abandoned does not exist (any longer) or is not confirmed. The abandon is then without effect.

The function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCE]].

4.2 Abort()

NAME
Abort – Abort Association.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_abort(
             OM_private_object  session,
             OM_private_object  context,
             OM_object          argument
     );

DESCRIPTION
This function is one of a group of dialogue handling functions: Open(), Accept(), Refuse(), Issue(), Close(), Abort(), Receive(), used to manage the MAP dialogue when AAM is disabled on a session. When AAM is enabled on a session, this dialogue handling function is neither necessary nor permitted.

This function is used to abort a mobile application session that is either associated or partially associated. The service is defined as an unconfirmed service: a reply is not expected.

Once an abort is issued, the associated session is implicitly disassociated and unbound. All outstanding requests that pertain to this session are returned with the error session-terminated. This includes any Wait() request on that session.

ARGUMENTS
Session (Object(Session))
The associated (or partially associated) session against which this operation is perfomed. This must be a private object previously returned as part of an Accept-Result or Open-Argument, or returned explicitly from an asynchronously called Open(). This session object must have AAM disabled.
Context (Object(Context))
The management context to be used for this operation. This argument must be a private object. Once a session is connected or partially connected, the precedence rules for common parameters within the Session and the Context objects are different. Once connected, the responder address and responder title cann not be overriden by the Context object. (See also Names.)
Argument (Object(Abort-Argument))
The information supplied as the argument of an Abort operation. (See Abort-Argument.)

RESULTS
As this function is not confirmed, there are no results returned.
ERRORS
This function can return a Communications-Error, or one of the following Library-Errors: bad-argument, bad-class, bad-context, bad-session, miscellaneous, missing-type, session-terminated, reply-limit-exceeded, time-limit-edceeded.

The function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

CORRESPONDENCE
This function corresponds to the MAP-U-ABORT request primitive of 3GPP TS 29.002 Section 7.

4.3 Abort-req()

NAME
Abort-req — abort a mobile application association.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_abort_req(
             OM_private_object   session,
             OM_private_object   context,
             OM_object           response
     );

DESCRIPTION
This function is used to abort a mobile application session that is either associated or partially associated. The service is defined as an unconfirmed service. A reply is not expected.

Once an abort request has been issued, the associated session is implicitly disassociated and unbound. All outstanding requests that pertain to this session are returned with the error session-terminated. This includes any Wait() requests on that session.

ARGUMENTS
Session (Object(Session))
The associated (or partially associated) session against which this operation is performed. This must be a private object previously returned as part of an Assoc-Result or Assoc-Argument, or returned explicitly from an asynchronously called Assoc-req(). This session object must have AAM disabled.
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object.

Once a session is associated or partially associated, the precedence rules for common parameters within the Session and Context objects are different. Once associated, the responder-Address and responder-Title cannot be overridden by the Context object.

Response (Object(Abort-Result))
The information supplied as the response of an Abort operation.

RESULTS
Status (Status)
The value success indicates that the operation was completed.

ERRORS
This function can return a Communications-Error, or one of the following Library-Errors: bad-argument, bad-class, bad-context, bad-session, miscellaneous, missing-type, session-terminated, reply-limit-exceeded, time-limit-exceeded.

This function can also return the error constants [[MP_NO_WORKSPACE]], [[MP_INVALID_SESSION]] or [[MP_INSUFFICIENT_RESOURCES]].

4.4 Accept()

NAME
Accept — accept an indicated mobile application open operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_accept(
             OM_private_object       session,
             OM_private_object       context,
             OM_object               response,
             OM_sint32               dialog_id,
             OM_private_object      *connected_session_return
     );

DESCRIPTION
This function is one of a group of dialogue handling functions: Open(), Accept(), Refuse(), Issue(), Close(), Abort(), Receive(), used to manage the MAP dialogue when AAM is disabled on a session. When AAM is enabled on a session, this dialogue handling function is neither necessary nor permitted.

This function is used to accept a previously indicated Open operation. This function can only be called in syncrhonous mode.

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is to be performed. This must be a private object previously returned from Bind().11
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).
Response (Object(Accept-Result))
The information supplied in acceptance of the previously indicated Open operation. This is an instance of OM class Accept-Result, indicating that the open indication is to be accepted. The user provides negotiated ACSE parameters in this object as input to the service provider. A newly formed dialog object is returned in the Accept-Result object, so this is an in/out parameter to this function. The new Session object represents a fully formed dialog session.
Dialog-ID (Integer)
The Dialog-ID of the requested dialog to which the reply applies. This Dialog-ID must have been returned from a call to Receive() for the corresponding association that is being accepted.

RESULTS
Status (Status)
Indicates whether or not the Accept response was completed.
Connected-Session (Object(Session))
When successful, this function returns a newly connected session object. The returned Session object is in a connected state, and contains the final negotiated ACSE parameters for the new association.

It is not specified whether the association has been formed by the underlying Mobile Application Service provider at the time that this function returns. The underlying Mobile Application Service might wait until a Issue() function call before fully forming the association. Nevertheless, the association is considered to be in the “connected” state from the standpoint of the interface.


ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-result, bad-session, miscellaneous, no-such-operation, not-supported, session-terminated.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

CORRESPONDENCE
This function corresponds to the MAP-OPEN response primitive (with a parameter indicating acceptance) of 3GPP TS 29.002 Section 7.

4.5 Assoc-req()

NAME
Assoc-req — establish mobile application association.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_assoc_req(
             OM_private_object   session,
             OM_private_object   context,
             OM_object           argument,
             OM_private_object  *result_return
     );

DESCRIPTION
This function is used to request the establishment of a mobile application association. The service is defined as a non-confirmed service. No reply is expected.

This operation may only be called in synchronous mode.

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is performed. This must be a private object previously returned from Bind().12 This session must also have AAM (Automatic Association Management) disabled.
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object.
Argument (Object(Assoc-Argument))
The information supplied as an argument of an Assoc operation. This is an Assoc-Argument object with optional ACSE information contained within it. An associated Session object is returned in the Result of this function.

RESULTS
Status (Status)
The value success indicates that the action was completed.
Result (Object(Assoc-Result))
Upon successful completion, when the Assoc-req has been accepted/rejected by the Mobile Application Service provider, one instance of the OM class Assoc-Result Object is returned. This Assoc-Result object either contains information as to why an association was rejected, or contains a Session object in an associated state, and contains the final negotiated ACSE parameters for the new association.

ERRORS
This functoin can return one of the following Library-Errors: bad-argument, bad-class, bad-context, bad-session, miscellaneous, missing-type, session-terminated, reply-limit-exceeded, time-limit-exceeded.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] or [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Assoc-rsp().13

4.6 Assoc-rsp()

NAME
Assoc-rsp — reply to a requested association operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_assoc_rsp(
             OM_private_object   session,
             OM_private_object   context,
             OM_object           response,
             OM_sint32           assoc_id
     );

DESCRIPTION
This function is used to reply to a previously invoked Assoc operation.

This function can only be called in syncrhonous mode.

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is performed. This must be a private object previously returned from Bind().14
Context (Object(Context))
The mobile application context to be used for this operation. This must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).
Response (Object(Assoc-Result))
The information supplied as a response to an Assoc operation. This is one of the following:
  • When an association is accepted, one instance of the OM class Assoc-Result is given as the response. The user provides negotiated ACSE parameters in this object as input to the service provider, and also indicates that the association is to be accepted by setting the assoc-Result attribute to accept. A newly associated session object is returned in the Assoc-Result object, so this is an in/out parameter to this function. The new Session object is in an associated state, and contains the final negotiated ACSE parameters for the new association.
  • When an association is to be rejected, one instance of the OM class Assoc-Result is given as a response. The Assoc-Result should have the assoc-Result attribute set to either reject-permanent or reject-transient. The assoc-Diagnostic can also optionally be set to indicate why the reject has occurred.

Assoc-ID (Integer)
The Assoc-ID of the requested operation to which the reply applies.

RESULTS
Status (Status)
Indicates whether or note the Assoc response was completed.

ERRORS
Ths function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-result, bad-session, miscellaneous, no-such-operation, not-supported, session-terminated.
SEE ALSO
Assoc-req().15

4.7 Bind()

NAME
Bind — open a mobile application session.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_bind(
             OM_object           session,
             OM_workspace        workspace,
             OM_private_object  *bound_session_return
     );

DESCRIPTION
This function opens a mobile application session. It creates a Session OM object describing the session suitable for supplying to other XMAP functions. A session must be opened before any mobile application service interactions can take place.

If the OM attribute requestor-Title is specified, only one unconnected session can be opened with the same value of the OM attribute. There can be multiple connected or partially connected session objects with the same requestor-Title.

To allow for the implementation of automatic association management, it is undefined as to whether Bind() causes any communication with the remote management entity.

ARGUMENTS
Session (Object(Session))
Specifies a program together with other details of the service required. This argument may be either a public object or a private object. The constant Default-Session (‘MAP_DEFAULT_SESSION’) may also be used as the value of this argument, causing a new session to be created with default values for all its OM attributes.
Workspace (Workspace)
Sepcifies the workspace (obtained from a call to Initialize()) which is to be associated with the session. All function results from mobile application operations using this session will be returned as private objects in this workspace. If the Session argument is a private object, it must be a private object in this workspace.

RESULTS
Status (Status)
Indicates whether or not the function completed successfully.
Bound-Session (Object(Session))
Upon successful compltion, contains an instance of a mobile application session that may be used as an argument to other functions (e.g. Service-req()). This will be a new private object if the value of Session was Default-Session or a public object, otherwise, it will be that supplied as an argument. In the later case, the session provided should not be already in use. The function will supply default values for any of the OM attribute that were not present in the Session instance supplied as an argument. It will also set the value of the File-Descriptor OM attribute (the value will be No-Valid-File-Descriptor (‘MAP_NO_VALID_FILE_DESCRIPTOR’) if the functionality is not supported).

When AAM is disabled with Negotiate(), any session bound using Bind() is unconnected and may only be used to receive and send ACSE-related primitives, (i.e. it cannot be used for Mobile Application Service operations).


ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-address, bad-session, bad-title, miscellaneous, not-supported, too-many-sessions.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Unbind(),16 Negotiate().17

4.8 Close()

NAME
Close — terminate a mobile application association.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_close(
             OM_private_object       session,
             OM_private_object       context,
             OM_object               argument
     );

DESCRIPTION
This function is used to request the termination of a mobile application association. The service is defined as an unconfirmed service. No reply is expected.

This operation may only be called in synchronous mode.

ARGUMENTS
Session (Object(Session))
The connected session against which this operation is performed. This must be a private object previously returned as part of an Accept-Result or Open-Argument. This session object must have AAM diabled, and it must be in a connected state.
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object.

Once a session is connected or partially connected, the precedence rules for common parameters within the Session and the Context objects are different. Once connected, the responder address and title cannot be overridden by the Context object.

Argument (Object(Close-Argument))
The information supplied as the argument of a Close operation.

RESULTS
Status (Status)
The value success indicates that the operation was completed.

ERRORS
This function can return a Communications-Error, or one of the following Library-Errors: bad-argument, bad-class, bad-context, bad-session, miscellaneous, missing-type, session-terminated, reply-limit-exceeded, time-limit-exceeded.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Abort().18
CORRESPONDENCE
This function corresponds to the MAP-CLOSE request primitive of 3GPP TS 29.002 Section 7.

4.9 Error-Message()

NAME
Error-Message — return an error message describing a particular error.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     OM_sint map_error_message(
             MAP_status          error,
             OM_sint             length,
             unsigned char      *error_text_return
     );

DESCRIPTION
This function returns an error message string that describes the error. The caller provides a buffer-address and buffer-length argument. The error message is stored in the client's buffer.
ARGUMENTS
Error (Status)
Length
The length of the buffer. The error text buffer is an unsigned character array. This is necessary if the intent is to support NLS (the X/Open Native Language System).

RESULTS
Error-text (String)
A message describing the error. The error message text is terminated by a NUL character.

The error message text will be truncated if the length of the error-text-buffer is less than the length of the error message text.

Length (Integer)
Indicates the length of the returned mesage. If the length parameter is 0 or the *error_text_return parameter is NULL, then the length_return value indicates the amount of buffer space required to host the error message.

ERRORS
This function returns no errors. (A default error message reports faulty arguments or other problems).

4.10 Get-Assoc-Info()

NAME
Get-Assoc-Info — retrieve negotiated association values.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_get_assoc_info(
             OM_private_object       receive_result_or_argument,
             OM_uint                 request_mask,
             OM_uint                 result_mask,
             OM_public_object        *pres_layer_args,
             OM_public_object        *acse_args,
             OM_public_object        *map_assoc_args
     );

DESCRIPTION
This function returns the negotiated association values corresponding to an incoming Result-Or-Argument object previously supplied by Receive(). The caller provides a request_mask to identify which values are to be returned in result objects.

This function may be used with automatic association management enabled or disabled or with automatic dialog handling enabled or disabled. In any case, the values returned are those associated with the underlying association or dialog within which the incoming Result-Or-Argument arrived.

Certain reqeusted values may not be available for the input object (that is, inappropriate for the underlying protocol) and may therefore be absent from the result. The values actually returned are indicated by the function result.

ARGUMENTS
Result-Or-Argument (Object(*))
This object contains an asynchronous response or indication, as previously returned to the user from the Receive() function.
Request-Mask (Integer)
The request-mask indicates which association values should be returned as result objects. The mask is composed of bit values that must be set on (‘1’) to request that the corresponding association value be returned. Association values that can be obtained by calling this function are:
  • presentation-Context-List
  • responder-Address
  • responder-Title
  • application-Context
  • application-Context-List
  • version-List

RESULTS
Result-Mask (Integer)
A mask indicating which association values have been returned as part of the result objects below. This mask has the same structure as the Request-Mask argument. All bits off (‘0’) indicates no values were available for the input object.
Pres-Layer-Args (Object(Presentation-Layer-Args))
Upon completion of this function, this object contains the negotiated values associated with the Result-Or-Argument object. This object is returned only when one of the following Result-Mask bits is set on:
  • MAP_T_PRESENTATION_CONTEXT_LIST
Otherwise, [[MAP_ABSENT_OBJECT]] is returned for this object.
Acse-Args (Object(Acse-Args))
Upon completion of this function, this object contains the negotiated values associated with the Result-Or-Argument object. This object is returned only when one of the following Result-Mask bits is set on:
  • MAP_T_RESPONDER_ADDRESS
  • MAP_T_RESPONDER_TITLE
  • MAP_T_APPLICATION_CONTEXT
Otherwise, [[MAP_ABSENT_OBJECT]] is returned for this object.
Map-Assoc-Args (Object(Map-Assoc-Args))
Upon completion of this function, this object contains the negotiated values associated with the Result-Or-Argument object. This object is returned only when the one of the following Result-Mask bits is set on:
  • MAP_T_APPLICATION_CONTEXT_LIST
  • MAP_T_VERSION_LIST
otherwise, [[MAP_ABSENT_OBJECT]] is returned for this object.

ERRORS
This function can return error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] or [[MAP_INSUFFICIENT_RESOURCES]].

4.11 Get-last-error()

NAME
Get-last-error — retrieve secondary return code of the most recent function call Communications or System error.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_get_last_error(
             OM_workspace        workspace,
             OM_uint32          *additional_return_error
     );

DESCRIPTION
This function is used to return additional error information related to the last function call that returned a status of:
  • [[MAP_E_COMMUNICATIONS_PROBLEM]]
  • [[MAP_E_BROKEN_SESSION]]
  • [[MAP_E_INVALID_CONNECTION_ID]]
  • [[MAP_E_SYSTEM]]
The returned integer value is implementation dependent.

In a multiple thread environment where there are multiple XMAP function calls, additional error information is stored in the workspace of the invoking call on a thread basis. The map_get_last_error call must be invoked from the same thread.

For most XMAP function calls, the Workspace anchor to store additional information is dervied from the ‘bound_session’. For Bind() and Wait(), the workspace parameter on the calls is used.

ARGUMENTS
Workspace (Workspace)
The workspace (obtained from a prior call to Initialize() of the function call that had the status error.

RESULTS
Status (Status)
Indicates whether or not the function call completed.
Additional-Error (Integer)
The secondary integer related to the last function call that returned a Communications or System error.

ERRORS
This function can return error constants [[MAP_NO_WORKSPACE]] or [[MAP_INVALID_SESSION]].

4.12 Initialize()

NAME
Initialize — initialize the interface.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     OM_workspace map_initialize(
             void
     );

DESCRIPTION
This function performs any necessary initialization of the interface and allocates a workspace. It must be called before any other mobile application interface functions are called. It may be called multiple times, in which case each call returns a workspace that is distinct from other workspaces created by Initialize() but not yet deleted by Shutdown().
ARGUMENTS
None.
RESULTS
Workspace (Workspace)
Upon successful completion, contains a handle to a workspace in which OM objects can be created and manipulated. Objects created in this workspace, and only such objects, may be used as arguments to the other management interface functions. This function returns NULL if it fails.

ERRORS
None.
SEE ALSO
Shutdown().19
EXAMPLE
     
     
     OM_workspace workspace;
     
     if ((workspace = map_initialize()) == NULL) {
     	exit(1);
     }

4.13 Issue()

NAME
Issue — issue pending service requests and responses.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_issue(
             OM_private_object       session,
             OM_private_object       context,
             OM_sint32               dialog_id
     );

DESCRIPTION
This function is one of a group of dialogue handling functions: Open(), Accept(), Refuse(), Issue(), Close(), Abort(), Receive(), used to manage MAP dialogues when AAM is disabled on a session. When AAM is enabed on a session, this dialogue hanglin function is neither necessary nor permitted.

This function is used to issue pending mobile application service requests and responses. The function can only be called in synchronous mode.

When an Open(), Accept() or Refuse() function is called, the underlying Mobile Application Service provider might not issue the corresponding TCAP transactions immediately, but may wait for the accumulation of mobile application service requests or responses to combine with the dialogue. The Issue() function tells the underlying Mobile Application Service provider to release pending dialogue handling primitives with the service requests and responses currently accumulated.

One typical order of dialogue handling function calls would be as follows:

  • Bind() — bind the session.
  • Open() — open the dialogue.
  • Service-req() — generate one or more service requests.
  • Issue() – issue pending dialogue handing and accumulated service requests or responses.
  • Service-req() — generate one or more service requests.
  • Close() — close the dialogue (also issuing any pending dialogue handling and accumulated service requests or responses).

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is to be performed. This must be a private object previously reutrned from Bind().20
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).
Dialog-ID (Integer)
The Dialog-ID of the requested dialog to which the reply applies. This Dialog-ID must have been returned from a call to Receive() for the corresponding association for which pending service requests and responses are being issued.

RESULTS
Status (Status)
Indicates whether or not the Issue request was completed.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-result, bad-session, miscellaneous, no-such-operation, not-supported, session-terminated.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

CORRESPONDENCE
This function corresponds to the MAP-DELIM request primitive of 3GPP TS 29.002 Section 7.

4.14 Negotiate()

NAME
Negotiate — negotiate features of the interface and service.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_negotiate(
             MAP_feature         feature_list[],
             OM_workspace        workspace
     );

DESCRIPTION
This function negotiates features of the interface; each feature is represented as an Object Identifier. Several features are defined and registered within this specification. Features may also include mobile application services packages, vendor extensions, and new features defined in future versions of this specification. Features can be negotiated after a workspace has been initialized, and can be renegotiated any time until the workspace is discarded. Note that all sessions on a given workspace share the same features.
ARGUMENTS
Feature-List (Feature-List)
An ordered sequence of features, each represented by an object identifier and a request value. The request value can contain one of the following values: Activate, Deactivate, Query State, and Query Supported.

The sequence is terminated by an object identifier having no components (a length of zero and a value of the data pointer in the C representation). The response value is returned upon completion of the Negotiate invocation.

In the C binding, the Feature-List argument is a single array of structures of type MAP_feature, which is defined as:

          
               #define MAP_ACTIVATE            0
               #define MAP_DEACTIVATE          1
               #define MAP_QUERY_STATE         2
               #define MAP_QUERY_SUPPORTED     3
               
               typedef struct {
                       OM_object_identifier    feature;
                       OM_sint                 request;
                       OM_boolean              response;
               } MAP_feature;
          

The following Features are defined and registered by this specification:

  • Mobile Application Packages
    The GSM Mobile Application package and the ANSI Mobile Application package are specified in Interface Class Definitions. Additional Mobile Application packages may be specified in the future. Note that multiple Mobile Application Packages can be activated within the same workspace.
  • Automatic Association Management
    This feature provides for automatic establishment and release of the underlying protocol associations(s) (if any); refer to Automatic Association Management. The Object-Identifier associated with this feature is ‘{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) common(1) automatic-association-management(1) }’. This Object-Identifier is represented by the constant ‘MAP_AUTOMATIC_ASSOCIATION_MANAGEMENT’. Automatic Association Management is enabled by default.
  • Automatic Dialog Handling This feature provides for automatic establishment and release of the underlying protocol dialog(s) (if any); refer to Automatic Dialog Handling. The Object-Identifier associated with this feature is ‘{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) common(1) automatic-dialog-handling(2) }’. This Object-Identifier is represented by the constant ‘MAP_AUTOMATIC_DIALOG_HANDLING’.
  • Automatic ASN.1 BER Encoding and Decoding
    This feature provides for automatic encoding and decoding of OM class and attribute types using ASN.1 BER;refer to Encoding and Decoding. The Object-Identifier associated with this feature is ‘{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) common(1) automatic-decoding(3) }’. This Object-Identifier is reprsented by the constant ‘MAP_AUTOMATIC_DECODING’. Automatic ASN.1 BER Encoding and Decoding is enabled by default.

Mobile Application Services packages are also negotiated as part of the Feature-List. Mobile Application Services packages may be defined by the OpenSS7 Project, by standards organizations or consortia, by vendors, or by users.

Registered Object Identifiers representing future features and vendor extensions may also be included in the Feature-List for negotiation.

Workspace
The handle to the workspace for which features are negotiated.

RESULTS
Status (Status)
Whether or not the function completed successfully.
Response (Boolean-List)
If the function completed successfully, this result contains an ordered list of Boolean values, with the same number of elements as the Feature-List. The significance of the values is shown as follows:

Request Response Meaning
Activate True Activated
False Cannot activate feature (or the feature is not supported).
Deactivate True Deactivated
False Cannot deactivte feature (or the feature is not supported).
Query-state True Activated
False Deactivated (or the feature is not supported).
Query-supported True Supported
False Not supported
Invalid True Cannot be returned
False Invalid argument
In the C binding, this result is combined with the Feature-List argument as a single array of structures of type MAP_feature as defined above.

ERRORS
This function can return a System-Error or Library-Error “miscellaneous”.

This function does not return a Communications-Error, nor any mobile application errors.

The function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCE]].

EXAMPLE
     
     
     MAP_status status;
     OM_workspace workspace;
     int i;
     
     workspace = map_initialize();
     
     MAP_feature feature_list[] = {
     	{MAP_COMMON_PKG, MAP_ACTIVATE, 0}
     	, {MAP_GSM_PKG, MAP_ACTIVATE, 0}
     	, {MAP_GSM_SM_PKG, MAP_ACTIVATE, 0}
     	, {MAP_GSM_LS_PKG, MAP_ACTIVATE, 0}
     	, {MAP_GSM_IN_PKG, MAP_ACTIVATE, 0}
     	, {MAP_GSM_CH_PKG, MAP_ACTIVATE, 0}
     	, {NULL, 0, 0}
     };
     
     if ((status = map_negotiate(feature_list, workspace)) != MAP_SUCCESS)
     	exit(1);
     
     for (i = 0; i < 6; i++)
     	if (!feature_list[i].response)
     		exit(1);

4.15 Open()

NAME
Open – Request establishment of a Mobile Application Services association (dialogue).
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_open(
             OM_private_object       session,
             OM_private_obect        context,
             OM_object               argument,
             OM_private_object       *result_return,
             OM_sint32               *dialog_id_return
     );

DESCRIPTION
This function is used to request the creation of a mobile application entity association (dialogue). The service is defined as a confirmed service: a reply is expected.

This operation may be called in asynchronous mode. Note that when operating in this mode, results may not only be locally discarded (when Abandon() is used), as may be done with outer asynchronous calls.

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is performed. This must be a private object previously returned from Bind().21 This session must also have ADH (Automatic Dialog Handling) disabled.
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object.
Argument (Object(Assoc-Argument))
The information supplied as the argument of an Assoc operation. This is an Assoc-Argument object with optional ACSE information contained within it. When called asynchronously, a partially connected Session object is returned in the Result of this function.

RESULTS
Status (Status)
If the function is called syncrhonously, the value success indicated that the action was completed. If called asynchronously, it indicates that the operation was initiated.
Result (Object(*))
Upon successful completion of a synchronous call, the results is one of the following:
  • When the Open request has been accepted by the remote peer, one instance of the OM class Accept-Result Object is returned. This Accept-Result object contains a session attribute that returns a Session object for which a dialog has been fully formed. The Accept-Result object also contains the final negotiated dialog parameters for the new dialog.
  • When the Open request has been refused by the remote peer, one instance of the OM class Refuse-Result Object is returned. This Refuse-Result object contains information as to why the dialog was refused. No session attribute is present in this result and no dialog session is formed.
  • When the Open request has been aborted by the remote peer or by the provider, one instance of the OM class Abort-Argument is returned. This Abort-Argument object contains information pertaining to the abort. No session attribute is present in this result and no dialog session is formed.
Upon successful completion of an asynchronous call, a partially formed dialog Session object is returned in the Result.
Note:
The original Session object passed to this function is unaffected and still remains in the bound or associated state. This session object can still be used in additional concurrent Open() or Receive() function calls.

Dialog-ID (Integer)
The returned Dialog-ID of the management operation when used asynchronously.

ERRORS
This function can return one of the following Library-Errors: bad argument, bad-class, bad-context, bad-session, miscellaneous, missing-type, session-terminated, reply-limit-exceeded, time-limit-exceeded.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Abort(),22 Assoc-rsp(), Accept(),23 Refuse().24
CORRESPONDENCE
This function corresponds to the MAP-OPEN request primitive of 3GPP TS 29.002 Section 7.

4.16 Receive()

NAME
Receive — get the argument of an operation or retrieve the (partial) result of an asynchronously executed operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_receive(
             OM_private_object   session,
             OM_sint            *mode_return,
             OM_sint            *primitive_return,
             OM_sint            *completion_flag_return,
             MAP_status         *operation_status_return,
             OM_private_object  *result_or_argument_return,
             OM_sint32          *invoke_or_dialog_id_return
     );

DESCRIPTION
This function is used to retrieve the argument of an invoked operation and to retrieve a partial result (linked reply) or the completed result of a previous asynchronous operation.

The function results include two status indications. One, called Status, indicates that the function call itself was successful; it is always returned. The other, called Operation-Status, is used to return the status of the completed asynchronous operation, and is only returned if there is one.

ARGUMENTS
Session (Object(Session))
The moble application session against which this mobile application operation is performed. This must be a private object previously returned from Bind(),25 or a connected or partially connected session object returned from Open(),26 Accept(),27 or Receive().

RESULTS
Status (Status)
Takes an error value if one of the library errors or system errors listed below occurred during execution of this function. Takes the value success (‘MAP_SUCCESS’) if this function returned successfuly.
Primitive (Integer)
The mobile application service primitives (‘MAP_SERVICE_IND’, ‘MAP_SERVICE_CNF’).

The MAP association service primitives (‘MAP_OPEN_IND’, ‘MAP_ACCEPT_CNF’, ‘MAP_REFUSE_CNF’, ‘MAP_DELIM_IND’, ‘MAP_CLOSE_IND’, ‘MAP_ABORT_IND’, ‘MAP_P_ABORT_IND’).

Determines the operation of this result or argument.

This result is only valid if Completion-Flag has the value completed, incoming or partial.

Mode (Integer)
This indicates the mode of an indication. When confirmed (‘MAP_T_CONFIRMED’) the invoked operation has to be confirmed, a reply is expected. When non-confirmed (‘MAP_T_NON_CONFIRMED’), the requested service is not to be confirmed.

This result is only valid if Completion-Flag has the value incoming.

Completion-Flag (Integer)
This flag indicates the statue of the received data, if any.
completed
(‘MAP_COMPLETED’)
This flag indicates that a final response has been received. For mobile application primitives this may be the confirmation for a service request or the last confirmation of a linked reply. In the latter case, the Result-Or-Argument parameter will be the Absent-Object.
incoming
(‘MAP_INCOMING’)
An indication has been received.
nothing
(‘MAP_NOTHING’)
There are no indications or confirmations to receive. Further, there are no outstanding asynchronous requests.
outstanding
(‘MAP_OUTSTANDING’)
There are no indications or confirmations to receive. There are still outstanding requests, but no confirmations have yet arrived.
parial
(‘MAP_PARTIAL’) A confirmation has been received which is part of a linked reply. This is used for all but the last in a series of linked replies. (See completed, above.)
This result is only valid if Status has the value success. In that case, the validity of the other results is given as follows:

Completed yes(1) no yes yes(1) yes
Incoming yes yes no yes yes
Nothing no no no no no
Outstanding no no no no no
Partial(3) yes(1) no yes yes(1) yes

Operation-Status (Status)
Takes an error value if a communications error occurred during the execution of the asynchronous operation, and success (‘MAP_SUCCESS’) otherwise. The possible error values are listed for each individual operation in the corresponding function description.

This result is only valid if Completion-Flag has the value completed or partial.

Result-or-Argument (Object(*))
This object contians the results of an asynchronous request, or information about an indication. The class of object received is dependent upon the values of the Primitive and Completion-Flag parameters. The following table for the three applicable Completion-Flag values. The actual class returned is dependent on the value of Primitive.
Completion-Flag set to completed:

Service-Result MAP_SERVICE_CNF
Service-Error MAP_SERVICE_CNF
Service-Reject MAP_SERVICE_CNF
Accept-Result MAP_ACCEPT_CNF
Refuse-Result MAP_REFUSE_CNF
Absent-Object All confirmations.
Note that Absent-Object may be returned in two cases:
  1. The confirmation contains no data.
  2. As the terminator of a linked reply list. In this case, the Invoke-or-Dialog-ID parameter can be used to determine which linked reply has been terminated.

Completion-Flag set to incoming:

Service-Argument MAP_SERVICE_IND
Open-Argument MAP_OPEN_IND
Close-Argument MAP_CLOSE_IND
Abort-Argument MAP_ABORT_IND

Completion-Flag set to partial:

Linked-Reply-Argument
For Completion-Flag values of completed or partial, the Result-or-Argument parameter is valid only if the Operation-Status contains the value success. The parameter is not valid for Completion-Flag values of nothing or outstanding.
Invoke-or-Dialog-ID (Integer)
The Invoke-ID or Dialog-ID of the operation whose error, result or argument is being returned.

This result is only valid of the Status has the value success and Completion-Flag has the value completed, partial or incoming.


ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-session, miscellaneous, session-terminated, time-limit-exceeded.

This function does not report any Communication-Errors, in its Status result. (Any such errors related to the completed asynchronous operation is reported in Operation-Status, as described above.)

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

4.17 Refuse()

NAME
Refuse – refuse an indicated association operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_refuse(
             OM_private_object       session,
             OM_private_object       context,
             OM_object               response,
             OM_sint32               dialog_id
     );

DESCRIPTION
This function is one of a group of dialogue handling functions: Open(), Accept(), Refuse(), Issue(), Close(), Abort(), Receive(), used to manage the MAP dialogue when AAM is disabled on a session. When AAM is enabled on a session, this dialogue handling function is neither necessary nor permitted.

This function is used to refuse a previously indicated Open operation. This function can only be called in syncrhonous mode.

ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is to be performed. This must be a private object previously returned from Bind().28
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).
Response (Object(Refuse-Result))
The information supplied in refusal of the previously indicated Open operation. This is an instance of OM class Refuse-Result, indicating that the open indication is to be refused. The user provides alternate ACSE parameters in this object as input to the service provider. The refuse-Reason and diagnostic-Information can be set to indicate why the reject occured.
Dialog-ID (Integer)
The Dialog-ID of the requested dialog to which the reply applies. This Dialog-ID must have been returned from a call to Receive() for the corresponding association that is being accepted.

RESULTS
Status (Status)
Indicates whether or not the Refuse response was completed.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-result, bad-session, miscellaneous, no-such-operation, not-supported, session-terminated.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCES]].

CORRESPONDENCE
This function corresponds to the MAP-OPEN response primitive (with a parameter indicating refusal) of 3GPP TS 29.002 Section 7.

4.18 Release-req()

NAME
Release-req
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_release_req(
     );

DESCRIPTION
ARGUMENTS
RESULTS
ERRORS

4.19 Release-rsp()

NAME
Release-rsp
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_release_rsp(
     );

DESCRIPTION
ARGUMENTS
RESULTS
ERRORS

4.20 Service-req()

NAME
Service-req — request mobile appliction service.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_service_req(
             OM_private_object   session,
             OM_private_object   context,
             OM_object           argument,
             OM_private_object  *result_return,
             OM_sint32          *invoke_id_return
     );

DESCRIPTION
This function is used to request mobile application service.
ARGUMENTS
Session (Object(Session))
The mobile application session against which this operation is performed. THis must be a private object previously returned from Bind().
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).

The service may be requested in a confirmed mode or a non-confirmed mode. In confirmed mode, a reply is expected.

Argument (Object(Service-Argument))
The information supplied as the argument of a mobile application service request is an instance of a subclass of the OM class Service-Argument. Normally, concrete subclasses of this class are defined in Mobile Application Services packages. For example, the MO-Forward-SM-Arg subclass of Service-Argument is defined in the GSM Short Message Services package (see MO-Forward-SM-Arg) and may be used as an argument to this function.

RESULTS
Status (Status)
If the function is called synchronously, the values success indicated that the action was completed. If called asynchronously, it indicates that the operation was initiated.
Result (Object(*))
Upon successful completion of a syncrhonous coall, when the operation was requested in a confirmed mode, the result is one of the following:
  • When the service is requested in a non-confirmed mode, no results are expected and the constant Absent-Object (‘MAP_ABSENT_OBJECT’) is returned as the result.
  • When a confirmed mode services is requested, this is indicated by on instance of the OM class Service-Result, or Service-Error, or when multiple replies are provided, an instance of OM class Multiple-Reply, which contains a set of instances of the OM class Service-Linked-Reply-Argument. Each Service-Linked-Reply-Argument contains exactly one of the following OM attributes:
    • service-Result
    • service-Error
    • processing-Failure

Invoke-ID (Integer)
The Invoke-ID of the initiated mobile application service operation when invoked asynchronously. It is significant in the case of a confirmed mode request only.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-argument, bad-class, bad-context, bad-session, miscellaneous not-supported, session-terminated, reply-limit-exceeded, time-limit-exceeded.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] or [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Abandon(),29 Service-rsp().30
CORRESPONDENCE
This function corresponds to the MAP-XXX request primitive of 3GPP TS 29.002 Section 7.

4.21 Service-rsp()

NAME
Service-rsp — reply to a requested mobile application service operation.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_service_rsp(
             OM_private_object   session,
             OM_private_object   context,
             OM_object           response,
             OM_sint32           invoke_id
     );

DESCRIPTION
This function is used to reply to a previously invoked confirmed mobile application service operation. This function can only be called in synchronous mode.
ARGUMENTS
Session (Object(Session))
The mobile application session against which the operation is performed. This must be a private object previously returned from Bind().
Context (Object(Context))
The mobile application context to be used for this operation. This argument must be a private object or the constant Default-Context (‘MAP_DEFAULT_CONTEXT’).
Response (Object(*))
The information supplied as response to an service operation. The response is one of the following:
  • An instance of a concrete subclass of the OM class Service-Result as the response.
  • An instance of a concrete subclass of the OM class Service-Error as the response, including the problem cause and its associated parameter that may be returned. See Service-Error.
  • An instance of a concrete subclass of the OM class Service-Reject including the problem cause and its associated parameter may be returned: duplicate-invocation, mistyped-argument, resource-limitation, unrecognized-operation.
  • When a service request requires multiple responses, this is indicated by one or more Service-rsp() calls, once for each response, followed by a final “empty” Service-rsp(). Each Service-rsp() call includes a response that contains an instance of a concrete subclass of OM class Service-Linked-Reply-Argument, containing exacly one of the following OM attributes:
    • service-Result
    • service-Error
    • processing-Failure
    The final “empty” Service-rsp() call includes a response that contains only the constant Absent-Object (‘MAP_ABSENT_OBJECT’).
For more details about the OM classes and OM attributes mentioned above, refer to Interface Class Definitions.
Invoke-ID (Integer)
The Invoke-ID of the requested operation to which the reply applies. This is the Invoke-ID that was returned from a call to Receive() that indicated the service request to which this service response corresponds.

RESULTS
Status (Status)
Indicates whether or not the action response was completed.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-context, bad-error, bad-linked-reply, bad-result, bad-session, miscellaneous, no-such-operation, not-supported, session-terminated.

This function can return a Communications-Error.

This function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] or [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Receive(),31 Service-req().32
CORRESPONDENCE
This function corresponds to the MAP-XXX response primitive of 3GPP TS 29.002 Section 7.

4.22 Service-parameter()

NAME
Service-parameter
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_xxx(
     );

DESCRIPTION
ARGUMENTS
RESULTS
ERRORS
CORRESPONDENCE
This function corresponds to the MAP-PARAMETER request primitive of 3GPP TS 29.002 Section 7.

4.23 Shutdown()

NAME
Shutdown — delete a workspace and the associated resources.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_shutdown(
             OM_workspace    workspace
     );

DESCRIPTION
This function deletes a workspace established by Initialize()33 and all the associated resources. It may enable the service to release resources.

All the remaining opened sessions are closed, all the remaining OM objects are deleted, and the workspace is deleted.

No other function may reference the specified workspace after it has been deleted.

ARGUMENTS
Workspace (Workspace)
Specifies the workspace (obtained from a call to Initialize()) which is to be deleted.

RESULTS
Status (Status)
Inidcates whether or not the shutdown function succeeded.

ERRORS
This function can return the error constants [[MAP_NO_WORKSPACE]] or [[MAP_INSUFFICIENT_RESOURCES]].
SEE ALSO
Initialize().34
EXAMPLE
     
     
     OM_workspace workspace;
     MAP_status status;
     
     if ((workspace = map_initialize()) == NULL)
     	exit(1);
     
     /* perform functions within the workspace */
     
     if ((status = map_shutdown(workspace)) != MAP_SUCCESS)
     	exit(1);
     exit(0);

4.24 Unbind()

NAME
Unbind — unbind from a mobile application session.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_unbind(
             OM_private_object   session
     );

DESCRIPTION
This function terminates the given mobile application session, and makes the argument unavailable for use with other interface functions (except Bind()).

Note that this means the results of any outstanding asynchronous operations that were intiiated uinsg the given Session can no longer be received. Any such operations may be terminated prematurely. For this reason it is recommended that all outstanding asynchronous operations are processed using Receive() before Unbind() is called.

The unbound session may be used again as an argument to Bind() possible after modification by the XOM functions (reference XOM). When it is no longer required, it must be deleted using the XOM functions.

The Library-Error “session-terminated” will be returned as the error value to a synchronous function call using the terminated session.

ARGUMENTS
Session (Object(Session))
The management session that is to be unbound. This must be a private object previously returned by Bind(). The value of the File-Descriptor OM attribute will be No-Valid-File-Descriptor (‘MAP_NO_VALID_FILE_DESCRIPTOR’) if the function succeeds. The other OM attributes will be unchanged.

RESULTS
Status (Status)
Takes the value success if Session was unbound, and take an error value if not.

ERRORS
This function can return a System-Error or one of the following Library-Errors: bad-class, bad-session, miscellaneous, session-terminated.

This function does not return a Communications-Error or any mobile application errors.

This function can return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] or [[MAP_INSUFFICIENT_RESOURCES]].

SEE ALSO
Bind().35

4.25 Validate-object()

NAME
Validate-object — analyze OM-Object and return Bad-Argument details if necessary.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_validate_obejct(
             OM_workspace        workspace,
             OM_object           test_object,
             OM_private_object  *bad_argument_return
     );

DESCRIPTION
This function is used to analyze any OM-Object to validate its structure. It may be used as a debug tool prior to issuing other XMAP function calls. It may also be used after XMAP function calls that return [[MAP_E_BAD_ARGUMENT]].

It is not the intention of this function to be able to validate all OM objects in all packages. Its purpose is to validate only those primary OM objects that may be validly passed as arguments to function defined in this specification.

This function is not intended to validate private objects, only client or service generated public objects. When passed a private object, provided that the private object is of a known OM class, success will be returned. That is, the function does not analyze the contents of a private object.

ARGUMENTS
Test-Object (Object(*))
The OM-Object to analyze and validate.
Workspace (Workspace)
Specifies the workspace (obtained from a call to Initialize(), in which Bad-Argument OM object will be created if the return status is [[MAP_E_BAD_ARGUMENT]]. Test-Objects does not need to be from this workspace.

RESULTS
Status (Status)
Indicates whether or not the validation was successful. A value of [[MAP_E_BAD_ARGUMENT]] indicates a validation failure and problem details are in the Bad-Argument parameter.
Bad-Argument (Object(Bad-Argument))
When Status is [[MAP_E_BAD_ARGUMENT]], the result is one instance of the OM class Bad-Argument.

ERRORS
This function can return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INSUFFICIENT_RESOURCES]], [[MAP_E_SYSTEM]] or [[MAP_E_BAD_ARGUMENT]].
EXAMPLE
Following is a ‘C’ binding example of validating a user-generated public object from the GSM MAP Short Message services package:
     
     
     OM_object argument = {
         OM_OID_DESC(OM_CLASS, MAP_C_MO_FORWARD_SM_ARG)
         , {MAP_SM_RP_DA, OM_S_OBJECT, {
             OM_OID_DESC(OM_CLASS, MAP_C_SM_RP_DA)
             , {MAP_IMSI, MAP_S_TBCD_STRING, OM_STRING("\x21\x43\x65\x87")}
             , OM_NULL_DESCRIPTOR
           } }
         , {MAP_SM_RP_OA, OM_S_OBJECT, {
             OM_OID_DESC(OM_CLASS, MAP_C_SM_RP_OA)
             , {MAP_NO_SM_RP_OA, OM_S_NULL, NULL}
             , OM_NULL_DESCRIPTOR
           } }
         , {MAP_SM_RP_UI, OM_S_OCTET_STRING, (OM_string) {data_length, data_pointer} }
         , {MAP_IMSI, MAP_S_TBCD_STRING, OM_STRING("\x21\x43\x65\x87")}
         , OM_NULL_DESCRIPTOR
     };
     MAP_status status;
     OM_private_object bad_argument;
     
     status = map_validate_object(workspace, argument, &bad_argument);
     
     if (status == MAP_E_BAD_ARGUMENT)
         exit(1);

4.26 Wait()

NAME
Wait — wait for the availability of manaement message(s) from one or more bound Sessions.
SYNOPSIS
     #include <xom.h>
     #include <xmap.h>
     
     MAP_status map_wait(
             MAP_waiting_sessions    bound_session_list[],
             OM_workspace            workspace,
             OM_uint32               timeout
     );

DESCRIPTION
This function is used to suspend the caller until a mobile application operation is available for a bound Session. A timeout value specifies the maximum number of milliseconds to suspend before returning when no messages are available. It should be noted that, in a multithreaded environment, Wait() may report the presence of a message that will have been processed by another thread by the time the first thread call Receive() to process it.
ARGUMENTS
Bound_session_list (Bound-Session-List)
An ordered sequence of mobile application sessions to wait upon. The last value must evaluate to NULL.
Workspace (Workspace)
Specifies the workspace (obtained from a call to Initialize(), in which a MAP_status object will be created if the return status is other than [[MAP_SUCCESS]]. Session(s) specified in the bound-session-list do no need to be from this workspace.
Timeout (Integer)
The maximum number of milliseconds to suspend before returning when there are no messages from the list of Session(s). A value of zero specifies an indefinite timeout.

RESULTS
Status (Status)
Indicates whether or not the function completed successfully. A successful completion means that either a message is available from a Session or that the timeout limit has been reached. The Receive() function must be called to determine whether a message is available. (See note in description above.)
Activated (Boolean-List)
If the function was completed successfully, this result is an ordered list of Boolean values, with the same number of elements as the bound-session-list. If true, each value indicates that the corresponding Session has data waiting in queue. If false, each valud indicates that the corresponding Session does not has data waiting in queue.

In the C binding, this result is combined with the bound-session-list argument as a single array of structures of type MAP_waiting_sessions, which is defined as:

          
               typedef struct {
                       OM_private_object   bound_session;
                       OM_boolean          activated;
               } MAP_waiting_sessions;
          

ERRORS
This function can return one of the following Library-Errors: bad-address, bad-session, bad-workspace, miscellaneous, session-terminated.

The function can also return the error constants [[MAP_NO_WORKSPACE]], [[MAP_INVALID_SESSION]] and [[MAP_INSUFFICIENT_RESOURCE]].

SEE ALSO
Initialize(),36 Receive(),37 Bind().38
EXAMPLE
Following is a ‘C’ language binding example of using the Wait() function in conjunction with the Receive() function to process indications or confirmations:
     
     
     MAP_waiting_sessions bound_session_list[] =
         { {session, OM_FALSE} , {NULL,} };
     
     for (;;) {
         if ((status = map_wait(bound_session_list, workspace, 0)) != MAP_SUCCESS)
             exit(1);
         if (bound_session_list[0].activated) {
             OM_sint mode;
             OM_sint primitive;
             OM_sint completion_flag;
             MAP_status operation_status;
             OM_private_object result;
             OM_sint32 received_invoke_id;
     
             if ((status = map_receive(session, &mode, &primitive, &operation_status,
                                 &result, &received_invoke_id)) != MAP_SUCCESS)
                     exit(1);
             /* process received result */
             om_delete(result);
         }
     }

5 Interface Class Definitions

This chapter defines, in alphabetical order, the OM classes that constitute the Common MAP package (COMMON), the GSM Mobile Application package (GSM) and the ANSI Mobile Application package (ANSI). The common errors are defined in the Common MAP package, while the variant specific errors are defined in the GSM MAP and ANSI MAP packages.

The Object-Identifier associated with the Common MAP package is:

{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) common(1) }

This Object-Identifier is represented by the constant Common-Package (‘MAP_COMMON_PKG’).

The Object-Identifier associated with the GSM MAP package is:

{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) gsm(2) }

This Object-Identifier is represented by the constant GSM-Package (‘MAP_GSM_PKG’).

The Object-Identifier associated with the ANSI MAP package is:

{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) ansi(3) }

This Object-Identifier is represented by the constant ANSI-Package (‘MAP_ANSI_PKG’).

The Object-Identifier associated wtih the GSM MAP Short Message Service package is:

{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591) xom-packages(1) xmap(1) gsm(2) sm(22) }

This Object-Identifier is represented by the constant GSM-SM-Package (‘MAP_GSM_SM_PKG’).

The XMAP API may also make use of Mobile Application Services packages. These optional packages define OM classes that are additional to those in the Mobile Application packages, to extend the capabilities of the interface.

The concepts of OSI-Abstract-Data Manipulation are briefly described in Relationship to Data Abstraction Services. The notation is introduced below. Both are fully explained in the XOM Specification (see reference XOM).

Each OM class is described in a separate section, which identifies the OM attributes specific to that OM class. The OM classes are listed in alphabetic order; the OM attributes for each OM class are listed in the order in which they occur in corresponding ASN.1 definitions. The OM attributes that may be found in an instance of an OM class are those OM attributes specific to that OM class and those inherited from each of its super-classes. The OM class-specific OM attributes are defined in a table. The table gives the name of each OM attribute, the syntax of each of its values, any restrictions upon the length (in bits, octets (bytes), or characters) of each value, any restrictions upon the number of values, and the value, if any, the OM-Create() function supplies.

Vendor Extensions

Vendors may provide additional OM attributes in their implementation of particular OM classes and their individual documentation will give details of the specification and usage of these. Extensions must be negotiated through use of the Negotiate() function.

All such OM attributes have default values which lead to the behaviour described in this specification.

5.1 Global Class Hierarchy

This section depicts the hierarchical organization of the OM classes defined in this chapter, and thus shows which OM classes inherit additional OM attributes from their super-classes. Sub-classification is indicated by indentation, and the names of abstract OM classes are rendered in italics. Thus, for example, the concrete class Itut-SCCP-Address is an immediate subclass of the abstract class Address which in turn is an immediate subclass of the abstract class Object. The Create() function applies to all concrete OM classes.

The application is not permitted to create or modify instances of some OM classes, because these OM classes are only returned by the interface and never supplied to it (for example, some subclasses of Error).

5.1.1 Interface Common Objects

  • Object (defined in the XOM Specification: see reference XOM)
    • Abort-Argument
    • Acse-Args
    • Address
    • Assoc-Argument
    • Assoc-Information
    • Assoc-Result
    • Context
    • Extension
      • SNMP-Object-Name
    • Presentation-Context
    • Presentation-Layer-Args
    • Session
    • Title

5.1.2 Interface Common Error Definitions

  • Object (defined in the XOM Specification: see reference XOM)
    • Bad-Argument
    • Error
      • Service-Error
      • Service-Reject

5.1.3 GSM MAP Package Objects

  • Object (defined in the XOM Specification: see reference XOM)

5.1.3.1 GSM SM package Objects
  • Object (defined in the XOM Specification: see reference XOM)

5.1.4 ANSI MAP Package Objects

  • Object (defined in the XOM Specification: see reference XOM)

5.2 Common MAP Package

The Common MAP package introduces some additional OM syntaxes that are derivations of the String(Octet) syntax. These additional OM syntaxes are used to represent digit strings for telephony numbers and SCCP addresses.

5.2.1 String(TBCD)

This OM syntax is indicated in OM Attribute tables as String(TBCD).

In the C binding, the OM Syntax name for String(TBCD) is declared as ‘MAP_S_TBCD_STRING’.

A TBCD string is a Telephony Binary Coded Decimal encoding where digits ‘0’ through ‘9’, ‘*’, ‘#’, ‘a’, ‘b’ and ‘c’ keys are coded ‘0000’ through ‘1001’, ‘1010’, ‘1011’, ‘1100’, ‘1101’ and ‘1110’. The (2n)'th digit is encoded in the n'th octet in bits ‘4321’ and the (2(n-1)+1)'th digit iin bits ‘8765’. Code ‘1111’ is used as a filler when the number of digits is odd.

A Telephony Binary Coded Decimal (TBCD) String is used to represent several digits from ‘0’ through ‘9’, ‘*’, ‘#’, ‘a’, ‘b’, ‘c’, two digits per octet, each digit encoded ‘0000’ to ‘1001’ (‘0’ to ‘9’), ‘1010’ (‘*’), ‘1011’(‘#’), ‘1100’ (‘a’), ‘1101’ (‘b’), ‘1110’ (‘c’); ‘1111’ used as a filler when there is an odd number of digits. Bits ‘8765’ of octet n encodes digit 2n. Bits ‘4321’ of octet n encoding digit 2(n-1)+1.

5.2.2 String(Sccp-Address)

This OM syntax is indicated in OM Attribute tables as String(Sccp-Address).

In the C binding, the OM Syntax name for String(Sccp-Address) is declared as ‘MAP_S_SCCP_ADDRESS_STRING’.

An SCCP Address string is a encoded octet string where the encoding is the encoding of an SCCP address in either ITU-T or ANSI format in accordance with the format specified for the SCCP Called Party Address in ANSI T1.112/2000 Section 3.4 and ITU-T Recommendation Q.713 Section 3.4. This encoding is formatted as follows:

Octet 1
The first octet contains the address indicator, which is always present. The bits of the address indicator are interpreted as follows:
bit 8
0
A ‘0’ in bit 8 indicates that the address is formatted as an ITU-T address.
1
A ‘1’ in bit 8 indicates that the address is formatted as an ANSI address.

bit 7
0
A ‘0’ in bit 7 indicates that SCCP translation is required and routing is based on global title.
1
A ‘1’ in bit 7 indicates that SCCP translation is not required and routing is based on signalling point code and subsystem number.

bits 6543
These bits contain the global title indicator that determines the format of the Global Title.
bit 2
0
A ‘0’ in bit 2 indicates that the address does not contain a signalling point code.
1
A ‘1’ in bit 2 indicates that the address contains a signalling point code.

bit 1
0
A ‘0’ in bit 1 indicates that the address does not contain a subsystem number.
1
A ‘1’ in bit 1 indicates that the address contains a subsystem number.

ITU-T Format
When bit 8 in octet 1 is set to ‘0’, the remainder of the address is formatted according to ITU-T format as follows:
Octet 2a and 2b
Octets 2a and 2b, when present as indicated by the point code indicator (bit 2 in Octet 1), contains the ITU-T formatted signalling point code. Otherwise, octets 2a and 2b are not included. Octet 2a contains the least significant eight bits of the 14-bit signalling point code; octet 2b contains the most significant 6-bits of the signalling point code, aligned to the least significant bit, with the two most significant bits padded to zeroes.
Octet 3
Octet 3, when present as indicated by the subsystem number indicator (bit 1 in Octet 1), contains the ITU-T formatted subsystem number. Otherwise, octet 3 is not included.
Global Title
GTI ‘0000
When the global title indicated is coded ‘0000’, there is no global title octets in the address.
GTI ‘0001
When the global title indicates is coded ‘0001’, the global title octets are formatted as follows:
Octet 4a
Contains the nature of address indicator.
Octet 5a and onwards.
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

GTI ‘0010
When the global title indicates is coded ‘0010’, the global title octets are formatted as follows:
Octet 4a
Contains the translation type.
Octet 5a and onwards
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

GTI ‘0011
When the global title indicates is coded ‘0011’, the global title octets are formatted as follows:
Octet 4a
Contains the translation type.
Octet 4b
Contains the numbering plan and encoding scheme as follows:
bits 8765
Contain the numbering plan.
bits 4321
Contain the encoding scheme.

Octet 5a and onwards
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

GTI ‘0100
When the global title indicates is coded ‘0100’, the global title octets are formatted as follows:
Octet 4a
Contains the translation type.
Octet 4b
Contains the numbering plan and encoding scheme as follows:
bits 8765
Contain the numbering plan.
bits 4321
Contain the encoding scheme.

Octet 4c
Contains the nature of address indicator (with the odd/even indicator unused).
Octet 5a and onwards
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

ANSI Format
When bit 8 in octet 1 is set to ‘1’, the remainder of the address is formatted according to ANSI format as follows:
Octet 2
Octet 2, when present as indicated by the subsystem number indicator (bit 1 in Octet 1), contains the ANSI formatted subsystem number. Otherwise, octet 2 is not included.
Octets 3a, 3b, 3c
Octets 3a, 3b, 3c, when present as indicated by the point code indicator (bit 2 in Octet 1), contains the ANSI formatted signalling point code. Otherwise, octets 3a, 3b and 3c are not included. Octet 3a contains the member component of the signalling point code; 3b the cluster; and 3c the network.
Global Title
GTI ‘0000
When the global title indicated is coded ‘0000’, there is no global title octets in the address.
GTI ‘0001
When the global title indicates is coded ‘0001’, the global title octets are formatted as follows:
Octet 4a
Contains the translation type.
Octet 4b
Contains the numbering plan and encoding scheme as follows:
bits 8765
Contain the numbering plan.
bits 4321
Contain the encoding scheme.

Octet 5a and onwards
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

GTI ‘0010
When the global title indicates is coded ‘0010’, the global title octets are formatted as follows:
Octet 4a
Contains the translation type.
Octet 5a and onwards
Contains the address signals. When BCD encoding is indicated, the address signals are in the format of a String(TBCD).

5.2.3 Abort-Argument

An instance of OM abstract class Abort-Argument represents the base information passed as the Argument argument to the Abort() function (see Abort) or returned from the Receive() function (see Receive) in the Result-Or-Argument result for a user abort indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Abort-Argument (see GSM-Abort-Argument) and ANSI-Abort-Argument.

An instance of this OM class has the OM attributes of its superclasses, Object, Error; it does not define any attributes of its own.

Because abort causes are Mobile Application package specific, this abstract OM class does not define any of the values for the problem or parameter attributes of the Error superclass.

See also Service Error.

5.2.4 Abort-Result

An instance of abstract OM class Abort-Result represents the base information passed as the Argument argument to the Abort-req() function (see Abort-req) or returned from the Receive() function (see Receive) in the Result-Or-Argument result for an association abort indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Abort-Result (see GSM-Abort-Result) and ANSI-Abort-Result.

An isntance of this OM class has the OM attributes of its superclasses, Object, Error; it does not define any attributes of its own.

Because abort result error codes are Mobile Application package specific, this abstract class does not define any of the problem values or parameter syntaxes of the Error superclass.

5.2.5 Accept-Result

An instance of abstract OM class Accept-Result represents the base information passed as the Response argument to the Accept() function (see Accept) or returned from the Receive() function (see Receive) in the Result-Or-Argument result for an accept indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Accept-Result (see GSM-Accept-Result) and ANSI-Accept-Result.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 51.

xmap_tab051.png

Table 51. OM Attributes of OM class Accept-Result

This OM class contains the following class-specific OM attributes:

session
Used to return to the user a fully formed dialog session object. This object may be used for all furture interface calls pertaining to this new dialog.

When this object is received as a Result-Or-Argument result in a call to Receive() (see Receive), the Get-Assoc-Info() function can be used to retrieve additional details concerning the association. See Get-Assoc-Info.

5.2.6 Acse-Args

An instance of OM class Acse-Args identifies ACSE specific arguments that will be used during association establishment to a remote peer entity. These can be specified in the Session object if AAM is enabled, or in the Assoc-Argument or Assoc-Result object if AAM is disabled.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed below:

xmap_tab028.png

Table 28. OM Attributes for a Acse-Args

This OM class contains the following class-specific OM attributes:

The Acse-Args object collects together all the information that is ACSE specific for association establishment.

responder-Address
Indicates the address of the responding program named by responder-Title.
responder-Title
Indicates the name of the program which will be used to service management service requests. It may be a distinguished name (instance of OM class Form1) or a registered name (instance of OM class Form2) which is used in name/network address resolution phase to get the application process title, the application entity qualifier and the presentation address. It may also be the Entity-Name of the responding program.
application-Context
The application context name proposed by the user to be used on the mobile application association. When automatic dialog handling is enabled on the session, the application context will be selected by the Mobile Application Service provider consistent with the Mobile Application Service request or indication. Mobile Application Service packages define a set of application contexts that are applicable to the service package.
security-Context
The security context name proposed by the user to be used on the mobile application association. By default the security context is not present. MObile Application Service packages define a set of security contexts that are applicable to the service package.

5.2.7 Address

An instance of OM class Address represents the address of a particular mobile application entity. It is used to define the sepcific location to contact a particular mobile application entity.

An instance of this OM class has all of the attributes of its superclasses, Object, and additionally the OM attributes listed in Table 30.

xmap_tab030.png

Table 30. OM Attributes of OM class Address

This OM class contains the following class-specific OM attributes:

sccp-Address
The address is respresented using an octet string that contains the encoding of an SCCP address in either ITU-T or ANSI format in accordance with the format specified for the SCCP Called Party Address in ANSI T1.112/2000 Section 3.4 and ITU-T Recommendation Q.713 Section 3.4 (see String(Sccp-Address)) with the following considerations:
  • The encoded address shall have both a signalling point code and a subsystem number in the address.
  • The encoded address shall not have a global title in the address (the global title indicated shall be coded ‘0000’).
  • The encoded address will distinguish between ITU-T format and ANSI format using the network indicator bit as described in ANSI T1.112/2000 Section 3.4.

5.2.8 Application-Context-List

An instance of OM class Application-Context-List represent a list of application context names.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 47.

xmap_tab047.png

Table 47. OM Attributes of OM class Application-Context-List

This OM class contains the following class-specific OM attributes:

application-Context-Name
This attribute is one or more instances of an application context name consisting of an integer syntax or an object-identifier syntax. The integer syntax is only applicable to some Mobile Application packages (e.g. the GSM ANSI service package).

5.2.9 Assoc-Argument

An instance of OM class Assoc-Argument is the information supplied as an argument of an ACSE Associate operation to be performed. This object is passed to Assoc-req() or returned from Receive().

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed below:

xmap_tab029.png

Table 29. OM Attributes of OM class Assoc-Argument

This OM class contains the following class-specific OM attributes:

presentation-Layer-Args
Indicates any presentaiton layer arguments needed during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
acse-Args
Indicates ACSE related arguments that will be used during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
map-Assoc-Args
Indicates MAP related arguments that will be used during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
session
Used to return an associated Session object. This attribute must be empty when Assoc_req() is called, and is supplied as a Result parameter by the Mobile Application Service provider upon return from that call. When the object is returned from Receive(), this attribute is a partially associated Session object. Partially associated session objects can be aborted by calling Abort_req() using the new partially associated session object. Partially associated session objects can become fully associated by calling Assoc_rsp(). To accept or refuse the new association, call Assoc_rsp() using the new partially associated session object that was returned by Receive() for the association indication.

5.2.10 Assoc-Result

An instance of OM class Assoc-Result is the information supplied as a response of an ACSE Associate operation to be performed. This object is passed to Assoc-rsp() or returned from Receive().

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 61.

xmap_tab061.png

Table 61. OM Attributes of OM class Assoc-Result

This OM class contains the following class-specific OM attributes:

presentation-Layer-Args
Indicates any presentation layer arguments needed during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
acse-Args
Indicates ACSE relasted arguments that will be used during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
map-Assoc-Args
Indicates MAP related arguments that will be used during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
session
Used to return to the user an associated session object. This object may be used for all future interface calls pertaining to this new association.

5.2.11 Close-Argument

An instance of OM class Close-Argument represents the base information that is supplied as the Argument argument to the Clsoe() function (see Close) or is returned by the Receive() function (see Receive) in the Result-Or-Argument result for a close indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Close-Argument (see GSM-Close-Argument) and ANSI-Close-Argument.

An instance of this OM class has the OM attributes of its superclasses, Object, it does not define any OM attribtutes of its own.

5.2.12 Context

An instance of OM class Context comprises per operation arguments that are accepted by most of the interface functions.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attribtutes listed below:

xmap_tab023.png

Table 23. OM Attributes of OM class Context

This OM class contains the following class-specific OM attributes:

Common Arguments
extensions

Service Controls
mode

application-Context
responder-Address
responder-Title

Local Controls
asynchronous
reply-Limit
time-Limit

5.2.13 Extension

An instance of OM class Extension represent an extension to ASN.1 syntax. This object is coded using the any syntax. The particular syntax of the extension is dependent upon the object within which an instance of this extension object is contained.

An instance of this OM class has the OM attributes of is superclasses, Object, and additionally the OM attributes listed in Table 45.

xmap_tab045.png

Table 45. OM Attributes of OM class Extension

This OM class contains the following class-specific OM attributes:

extension
This attribute is a syntax that represents the ASN.1 encoding of the extension complete with tags.

5.2.14 Generic-Service-Argument

An instance of OM class Generic-Service-Argument represents a generic service request independent of a defined Mobile Application Services package. This object is used to support service requests that have not been defined in a Mobile Application Services package, or for a Mobile Application Services package that is not supported by the implementation workspace.

An instance of this OM class has the attributes of it is superclasses, Service-Request, and additionally the OM attributes listed in Table 55.

xmap_tab055.png

Table 55. OM Attributes of OM class Generic-Service-Argument

This OM class contains the following class-specific OM attributes:

confirmation
This attribute is a boolean value that specifies whether the operation is performed in the confirmed or unconfirmed mode. When performed in a confirmed mode, a response is expected. When performed in the unconfirmed mode, no response is expected. This attribute determines which TCAP operations class will be used for the underlying invoke operation.
operation
This attribute specifies the ROSE/TCAP operation code associated with the service request as either an integer or an object identifier. Whether an integer or object identifier is used depends upon the underlying ROSE/TCAP provider and may differ depending on the Mobile Application Package in use (e.g. GSM MAP or ANSI MAP).
arguments
This attribute specifies the parameters of the operation invocation as one or more instances of OM class Encoding. This encoding class will be encapsulated in a Parameter Sequence by the underlying ROSE/TCAP provider.

5.2.15 Generic-Service-Result

An instance of OM class Generic-Service-Result represents a generic service response independent of a defined Mobile Application Services package. This object is used to support service responses that have not been defined in a Mobile Application Services package, or for a Mobile Application Services package that is not supported by the implementation workspace.

An instance of this OM class has the attributes of its superclasses, Service-Result, and additionally the OM attributes listed in Table 56.

xmap_tab056.png

Table 56. OM Attributes of OM class Generic-Service-Result

This OM class contains the following class-specific OM attributes:

operation
This attribute specifies the ROSE/TCAP operation code associated with the service request as either an integer or an object identifier. Whether an integer or object identifier is used depends upon the underlying ROSE/TCAP provider and may differ depending on the Mobile Application Package in use (e.g. GSM MAP or ANSI MAP).
response
This attribute specifies the parameters of the operation invocation as one or more instances of OM class Encoding. This encoding class will be encapsulated in a Parameter Sequence by the underlying ROSE/TCAP provider.

5.2.16 Map-Assoc-Args

An instance of OM class Map-Assoc-Args represents the MAP association arguments that are optionally supplied by the Session, Assoc-Argument or Assoc-Result objects and can be interrogated with the Get-Assoc-Info() function.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 60.

xmap_tab060.png

Table 60. OM Attributes of OM class Map-Assoc-Args

This OM class contains the following class-specific OM attributes:

application-Context-List
version-List

5.2.17 Notice-Result

An instance of OM class Notice-Result represents the base information that is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a notice indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Notice-Result (see GSM-Notice-Result) and ANSI-Notice-Result.

An instance of this OM class has the OM attributes of its superclasses, Object. It does not define any OM attributes of its own.

5.2.18 Open-Argument

An instance of OM class Open-Argument represents the base information that is supplied as an argument to the Open() function (see Open) or is returned by the Receive() function (see Receive) for an open indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Open-Argument (see GSM-Open-Argument) and ANSI-Open-Argument.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 32.

xmap_tab032.png

Table 32. OM Attributes of OM abstract class Open-Argument

This OM class contains the following class-specific OM attributes:

responder-Address
Specifies the responder address (the address of the remote mobile application entity) for a bound session object with AAM enabled, this address takes precedence over any responder-Address contained in the Context or Session objects. For an associated session object, the precedence rules are different and the Open-Argument object cannot be used to override the responder-Address contained in the Session object.
responder-Title
Specifies the responder title. This title takes precedence over any responder-Title contained in the Context or Session objects. When not specified by any object, the MAS provider will not include a responder title in the open request.
requesting-Address
The requesting-Address contained in the Open-Argument cannot be used to override the any requesting address contained in the Session object.
requesting-Title
Specifies the requesting title. This title takes precedence over any requesting-Title contained in the Context or Session objects. When not specified by any object, the MAS provider will not include a requesting title.
session
Use to return a partially formed dialog Session object. This attribute must be empty when Open() is called, and is supplied as a Result parameter by the Mobile Application Service provider upon return from that call. The partially formed dialog session can either be aborted with a call to Abort(), or can become a fully formed dialog session with a call to Accept(). To abort the partially formed dialog session, call Abort() using the new partially formed dialog session object. To accept or refuse the new dialog, call Accept() or Refuse() using the session object that received the association indication.

5.2.19 Operation-Argument

5.2.20 Operation-Error

5.2.21 Operation-Reject

5.2.22 Operation-Result

5.2.23 P-Abort-Result

An instance of OM abstract class P-Abort-Result represents the base information returned in the Result-Or-Argument result from the Receive() function (see Receive) for a provider abort indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-P-Abort-Result (see GSM-P-Abort-Result) and ANSI-P-Abort-Result.

An instance of this OM class has the OM attributes of its superclasses, Object, Error; it does not define any OM attributes of its own.

See also Service Error.

5.2.24 Presentation-Context

An instance of OM class Presentation-Context lists the presentation contexts for association establishment.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed below:

xmap_tab026.png

Table 26. OM Attributes of OM class Presentation-Context

This OM class contains the following class-specific OM attributes:

presentation-Id
The integer user identification of the presentation context.
presentation-Abstract
Identifies the abstract syntax. If no value is supplied, by default the abstract syntax name is provided by the Mobile Application package. The GSM MAP package provides a default abstract syntax name of map-DialogueAs, specified by 3GPP TS 29.002, and is supplied by the Mobile Application Service provider. This Object-Identifier is { itu-t(0) identified-organization(4) etsi(0) mobile-domain(0) gsm-Network(1) as-Id(1) map-DialoguePDU(1) version1(1) } and is provided in the C binding as ‘MAP_GSM_DIALOGUE_AS’.

5.2.25 Presentation-Layer-Args

An instance of OM class Presentation-Layer-Args identifies the presentation layer arguments that will be used during association establishment. These can be specified in the session object if AAM is enabled, or in the Assoc-Argument or Assoc-Result object if AAM is disabled.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed below:

xmap_tab025.png

Table 25. OM Attributes of OM class Presentation-Layer-Args

This OM class contains the following class-specific OM attributes:

presentation-Context-List
The list of presentation contexts.

5.2.26 Refuse-Result

An instance of OM class Refuse-Result represents the base information that is supplied as the Response argument to the Refuse() function (see Refuse) or is returned by the Receive function (see Receive) in the Result-Or-Argument result for a refuse indication.

This OM class is an abstract class with several defined concrete subclasses: GSM-Refuse-Result (see GSM-Refuse-Result) and ANSI-Refuse-Result.

An instance of this OM class has the OM attributes of its superclasses, Object, it does not define any OM attributes of its own.

5.2.27 Release-Argument

5.2.28 Release-Result

5.2.29 Service-Argument

An instance of OM class Service-Argument represents the base information that is supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a service indication.

This OM class is an abstract class containing several defined subclasses: GSM-Service-Argument (see GSM-Service-Argument) and ANSI-Service-Argument.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionaly the OM attributes listed in Table 64.

xmap_tab064.png

Table 64. OM Attributes of OM class GSM-Service-Argument

This OM class contains the following class-specific OM attributes:

responder-Address
responder-Title
requesting-Title

5.2.30 Service-Error

An instance of abstract OM class Service-Error represents the base information that is supplied in response to a service operation, supplied as the Argument argument to the Service-rsp() function (see Service-rsp) or is returned as a Result-Or-Argument result by the Receive() function (see Receive) for a service confirmation.

This OM class is an abstract class containing several defined subclasses: GSM-Service-Error (see GSM-Service-Error) and ANSI-Service-Error.

An instance of this OM class has the OM attributes of its superclasses, Object, Error. As the problem values and parameter syntaxes are Mobile Application package specific, this OM class defines no attributes or error values of its own.

See Service Error.

5.2.31 Service-Reject

An instance of abstract OM class Service-Reject represents the base information that is supplied in response to a service operation, supplied as the Argument argument to the Service-rsp() function (see Service-rsp) or is returned as Result-Or-Argument result by the Receive() function (see Receive) for a service confirmation.

This OM class is an abstract class containing several defined subclasses: GSM-Service-Reject (see GSM-Service-Reject) and ANSI-Service-Reject.

An instance of this OM class has the OM attribute of its superclasses, Object, Error. As the problem values and parameter syntaxes are Mobile Application package specific, this OM class defines no attributes or error values of its own.

Note that when Automatic Association Management or Automatic Dialog Handling are enabled on a sesion for which a concrete subclass of the Service-Reject is used as a response, the Service-Reject object also represents the errors that would otherwise be reported using a concrete subclass of Abort-Argument, P-Abort-Result (were ADH to be diabled) or Refuse-Result or Abort-Result (were AAM to be disabled).

Therefore, when ADH is enabled on a session, the problem and parameter attributes of the Error superclass may also contain any of the error values defined for the corresponding Abort-Argument or P-Abort-Result subclasses. When AAM is enabled on a session, the problem and parameter attributes of the Error superclass may also contain any of the error values defined for the corresponding Refuse-Result or Abort-Result subclasses.

See Service Error.

5.2.32 Service-Result

An instance of OM class Service-Result represents the base information that is supplied as an argument to the Service-rsp() function (see Service-rsp) or is returned as a receive result by the Receive() function (see Receive) for a service confirmation.

This OM class is an abstract class containing several defined subclasses: GSM-Service-Result (see GSM-Service-Result) and ANSI-Service-Result.

An instance of this OM class has the OM attributes of its superclasses, Object. As the error codes are Mobile Application package specific, this OM class defines no attributes of its own.

5.2.33 Session

An instance of OM class Session identifies a particular communications link from the application program to the Mobile Application Service provider or to a remote mobile application entity depending upon the state of the session object. Session objects can be created with Automatic Association Management enabled or disabled. If AAM is enabled, then all of the ACSE connection management, needed to deliver a mobile application service operation, is done by the Mobile Application Service provider. If AAM is disabled, the ACSE connection management is done by the user before issuing or receiving Mobile Application Service operations.

The use of and rules for the session object are different depending on whether AAM is enabled or disabled. AAM is specified as part of Negotiate().39

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 24.

xmap_tab024.png

Table 24. OM Attributes of OM class Session

For a description of the three type of Session objects: AAM Enabled Session, AAM Disabled Session and Connected Session, see Session Description.

The OM atributes of a Session are:

requestor-Address
Indicates the address of the requesting program named by requestor-Title. If both the requestor-Address and requestor-Title are not specified, the service provider will supply a default requestor-Address.
requestor-Title
Indicates the name of the requesting program, user of this session. It may be a distinguished name (instance of OM class Form1) or a registerd name (instance of OM class Form2) which is used in name/network address resolution phase to get the application process title, the application entity qualifier and the presentation address. It my also be the entity-name of the requesting program.
role
Indicates the roles acted by the resquestor. The role value is specified by OR-ing none, one, or more of the following values:
performer-role
(‘MAP_T_PERFORMER_ROLE’) Responder and performer of mobile application services operations. Unless this role is set or implied, no indications will be returned by calls to Receive and the Mobile Application Service provider does not need to provide indications to the bound session user.
invoker-role
(‘MAP_T_INVOKER_ROLE’) Requester and Invoker of mobile application services operations. If performer-role is set and invoker-role is clear, the Mobile Application Service provider does not need to honor operation or service requests from the bound session user.
When both role flags are clear, or this attribute is not present in the session, the Mobile Application Service provider may still honor operation and service requests.
file-Descriptor
Indicates the file descriptor associated with the session. The file descriptor may be used by implementors of the Wait() function. The file descriptor may be used in subsequent calls to vendor-specific system facilities to suspend the process (for example, System V poll(2s) or BSD select(2)). Its use for any other purpose is unspecified.

If the implementation does not define any suitable supsension facilities, or if the session is not started, the value is No-Valid-File-Descriptor (‘-1’ or ‘MAP_NO_VALID_FILE_DESCRIPTOR’).

presentation-Layer-Args
Indicates any presentation layer arguments needed during association establishment. If none are supplied, the Mobile Application Service provider will supply defaults if required.
acse-Args
Indicates the ACSE related arguments that will be used during association establishment. If none are supplied, the Mobile Application Service Provider will supply defaults if required.
map-Assoc-Args
Indicates the MAP association related arguments that will be used during association establishment. If not are supplied, the Mobile Application Service Provider will supply defaults if required.

5.2.34 Title

An instance of OM class Title represents the title of a paticular mobile application service entity. It contains various subclass types used to define the specific mobile application process or system name responsible for a mobile application service entity.

An instance of this OM class has all of the attributes of its superclasses, Object, and additionally the OM attributes listed in Table 31.

xmap_tab031.png

Table 31. OM Attributes of OM class Title

This OM class contains the following class-specific OM attributes:

sccp-Title
The title is respresented using an octet string that contains the encoding of an SCCP address in either ITU-T or ANSI format in accordance with the format specified for the SCCP Called Party Address in ANSI T1.112/2000 Section 3.4 and ITU-T Recommendation Q.713 Section 3.4 (see String(Sccp-Address)) with the following considerations:
  • The encoded address may have either a signalling point code or a subsystem number, or both, in the address.
  • The encoded address shall have a global title in the address (the global title indicated shall not be coded ‘0000’).
  • The encoded address will distinguish between ITU-T format and ANSI format using the network indicator bit as described in ANSI T1.112/2000 Section 3.4.

5.3 GSM MAP Package

The GSM MAP package provides specialization of the argument and result objects of the Common MAP package to provide for the services under the GSM MAP as described in 3GPP TS 29.002 Section 7.6. This package is organized as a separate OM package that can be negotiated using the Negotiate() function.40

The Object-Identifier associated with the GSM MAP package is:

{ iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) openss7(29591)
  xom-packages(1) xmap(1) gsm(2) }

This Object-Identifier is represented by the constant GSM-Package (‘MAP_GSM_PKG’). This constant can be used to negotiate support for the package using the Negotiate() function.

GSM MAP package introduces some additional OM syntaxes that are derivations of the String(Octet) syntax. These additional OM syntaxes are used to represent digit strings and telephony numbers. See String(Address).

The following outlines the OM Class Hierarchy for the GSM MAP package:

  • Object (defined in the XOM Specification: see reference XOM)
    • Abort-Argument (defined in MAP-Common-Package)
      • GSM-Abort-Argument
    • Abort-Result (defined in MAP-Common-Package)
      • GSM-Abort-Result
    • Accept-Result (defined in MAP-Common-Package)
      • GSM-Accept-Result
    • Close-Argument (defined in MAP-Common-Package)
      • GSM-Close-Argument
    • Context (defined in MAP-Common-Package)
      • GSM-Context
    • Extension-Container
    • Map-Assoc-Args (defined in MAP-Common-Package)
      • GSM-Map-Assoc-Args
    • Notice-Result (defined in MAP-Common-Package)
      • GSM-Notice-Result
    • Open-Argument (defined in MAP-Common-Package)
      • GSM-Open-Argument
    • P-Abort-Argument (defined in MAP-Common-Package)
      • GSM-P-Abort-Argument
    • PCS-Extensions
    • Private-Extension
    • Private-Extension-List
    • Refuse-Result (defined in MAP-Common-Package)
      • GSM-Refuse-Result
    • Release-Argument (defined in MAP-Common-Package)
      • GSM-Release-Argument
    • Release-Result (defined in MAP-Common-Package)
      • GSM-Release-Result
    • Service-Argument (defined in MAP-Common-Package)
      • GSM-Service-Argument
    • Service-Result (defined in MAP-Common-Package)
      • GSM-Service-Result
    • Specific-Information
    • User-Abort-Choice

5.3.1 String(Address)

This OM syntax is indicated in OM Attribute tables as String(Address).

In the C binding, the OM Syntax name for String(Address) is ‘MAP_S_ADDRESS_STRING’.

This syntax is used to represent a number for addressing purposes. It is composed of a sequence of one or more octets, consisting of:

  • one octet for nature of address and numbering plan indicator;
  • digits of an address encoded as String(TBCD).

The first octet includes a one bit extension indicator, 3-bit nature of address indicator, and 4-bit numbering plan indicator coded as follows:

bit ‘8’:
This bit is an unused extension bit (no extension, coded as zero (‘0’)).
bits ‘765’:
These bits contain the Nature of Address Indicator:

000unknown
001international number
010national significant number
011network specific number
100subscriber number
101reserved
110abbreviated number
111reserved for extension

bits ‘4321’:
These bits contain the Numbering Plan:

0000unknown
0001ISDN/Telephony Number Plan (ITU-T Rec. E.164)
0010spare
0011data numbering plan (ITU-T Rec. X.121)
0100telex numbering plan (ITU-T Rec. F.69)
0101spare
0110land mobile numbering plan (ITU-T Rec. E.212)
0111spare
1000national numbering plan
1001private numbering plan
1010reserved
1011reserved
1100reserved
1101reserved
1110reserved
1111reserved for extension

The following octets representing digits of an address encoded as String(TBCD).

5.3.2 String(Subaddress)

This OM syntax is indicated in OM Attribute tables as String(Subaddress).

In the C binding, the OM Syntax name for String(Subaddress) is ‘MAP_S_SUBADDRESS_STRING’.

This syntax is used to represent a number for addressing purposes. It is used to represent ISDN subaddresses. It is composed of:

  • one octet of type of subaddress and odd/even indicator;
  • twenty octets of subaddress information.

The first octet includes a one bit extension indicator, a 3-bit type of subaddress, and a one bit odd/even indicator, encoded as follows:

bit ‘8

1(no extension)

bits ‘765

000NSAP (X.213/ISO 8348 AD2)
010User Specified
all other values reserved

bit ‘4

0even number of address signals
1odd number of address signals

bits ‘321

000(unused)

The following octets represent the address signals or subaddress information.

The NSAP X.213/ISO8348 AD2 address shall be formatted as specified by octet 4 which contains the Authority and Format Identifier (AFI). The encoding is made according to the “preferred binary encoding” as defined in X.213/ISO 8348 AD2. For the definition of this type of subaddress, see ITU-T Recommendation I.334.

For User-specific subaddress, this field is encoded according to the user specification, subject to a maximum length of 20 octets. When interworking with X.25 networks, BCD coding should be applied.

5.3.3 GSM-Abort-Argument

An instance of OM class GSM-Abort-Argument represents the information that can be supplied as the Argument argument to the Abort() function (see Abort) or is returned by the Receive() function (see Receive) in the Result-Or-Argument result of a user abort indication.

An instance of this OM class has the OM attributes of its superclass, Object, Error, Abort-Argument (see Abort-Argument), and additionally the OM attributes listed in Table 5.

xmap_tab005.png

Table 5. OM Attributes of OM class GSM-Abort-Argument

This OM class contains the following class-specific OM attributes:

problem
user-specific-reason(0)41 (‘MAP_E_PROCEDURE_ERROR’)
Processing of the procedure is terminated due to procedural reasons. The remote MAP Service User has aborted the operation due to a user-specific reason. Indicates that the user abort reason is user specific and no additional information is provided. There is no error parameter associated with this problem code.
resource-limitation-congestion(1) (‘MAP_E_RESOURCE_LIMITATION_CONGESTION’)
The requested user resource is unavailable due to congestion. The remote MAP Service User has aborted the operation due to a resource limitation (such as congestion). Indicates that the user abort reason is related to a resource limitation (e.g. congestion) and no additional information is provided. There is no error parameter associated with this problem code.
resource-unavailable(2) (‘MAP_E_RESOURCE_UNAVAILABLE’)
The requested user resource is unavailable for reasons other than congestion. The remote MAP Serice User has aborted the operation due to the unavailability of a resource (such as system memory). This is either of a short term or long term nature. Indicates that the user abort reason is due to the unavailability of a resource. The reason is further qualified as to the duration of the resource limitation as follows:
short-term-resource-limitation
(‘MAP_E_SHORT_TERM_RESOURCE_LIMITATION’ ‘0’)
long-term-resource-limitation
(‘MAP_E_LONG_TERM_RESOURCE_LIMITATION’ ‘1’)
This further qualification is contained in the error parameter as an Integer value.
application-procedure-cancellation(3) (‘MAP_E_APPLICATION_PROCEDURE_CANCELLATION’)
The procedure is cancelled for reasons detailed in the diagnostic information parameter. The remote MAP Service User has aborted the operation due to application procedure cancellation. The cause of the cancellation is provided. Indicates that the user abort reason is due to the cancellation of a procedure. The reason is futher qualified as to the source of the cancellation as follows:
handover-cancellation
(‘MAP_E_HANDOVER_CANCELLATION’ ‘0’)
radio-channel-release
(‘MAP_E_RADIO_CHANNEL_RELEASE’ ‘1’)
network-path-release
(‘MAP_E_NETWORK_PATH_RELEASE’ ‘2’)
call-release
(‘MAP_E_CALL_RELEASE’ ‘3’)
associated-procedure-failure
(‘MAP_E_ASSOCIATED_PROCEDURE_FAILURE’ ‘4’)
tandem-dialogue-release
(‘MAP_E_TANDEM_DIALOGUE_RELEASE’ ‘5’)
remote-operations-failure
(‘MAP_E_REMOTE_OPERATIONS_FAILURE’ ‘6’)
This further qualification is contained in the error parameter as an Integer value.

parameter
This attribute is an instance of OM class Specific-Information.
specific-Information
This attribute is zero or more instances of OM class Specific-Information. See Specific-Information.

5.3.4 GSM-Abort-Result

5.3.5 GSM-Accept-Result

An instance of OM class GSM-Accept-Result represents the information that is supplied as the Response argument to the Accept() function (see Accept) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for an accept confirmation.

An instance of this OM class has the OM attributes of its superclass, Accept-Result (see Accept-Result), and additionally the OM attributes listed in Table 2.

xmap_tab002.png

Table 2. OM Attributes of OM class GSM-Accept-Result

This OM class contains the following class-specific OM attributes:

specific-Information
This attribute provides user-specific information that is passed transparently between peer mobile application service users as part of dialog establishment. This attribute is an instance of OM class Specific-Information. See Specific-Information.

5.3.6 GSM-Close-Argument

An instance of OM class GSM-Close-Argument represents the information that is supplied as the Argument argument to the Close() function (see Close) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a close indication.

An instance of this OM class has the OM attributes of its superclass, Close-Argument (see Close-Argument), and additionally the OM attributes listed in Table 4.

xmap_tab004.png

Table 4. OM Attributes of OM class GSM-Close-Argument

This OM class contains the following class-specific OM attributes:

release-Method
Specifies the release method for closing the dialogue. When supplied as an argument to the Close() function, this value can be one of the following:
normal-release
(‘MAP_T_NORMAL_RELEASE’) The release is normal (and will result in issuing a MAP-CLOSE dialogue and a TCAP END message).
prearranged-end
(‘MAP_T_PREARRANGED_END’) The release is prearranged (and will not result in either issuing a MAP-CLOSE dialogue nor a TCAP END message).
Note:
When indicated by the Receive() function, this attribute will always contain normal-release.

specific-Information
This attribute provides user-specific information that is passed transparently to the remote peer moble application service user. This attribute is an instance of OM class Specific-Information. See Specific-Information.

5.3.7 GSM-Context

An instance of OM class GSM-Context comprises per operation arguments, including GSM specific arguments, that are accepted by most of the interface functions.

An instance of the OM class has the OM attributes of it superclasses, Context, and additionally the OM attributes listed in Table 65.

xmap_tab065.png

Table 65. OM Attributes of OM class GSM-Context

.

This OM class contains the following class-specific OM attributes:

application-Context
Specifies the application context for the calle to Open(), Refuse() (ADH disabled) or Service-req(), Service-rsp() (ADH enabled). When not specified, the MAS provider will select a default value as required.
destination-Reference
Specifies the destination reference for the call to Open() (ADH disabled) or Service-req() (ADH enabled). When not specified, the MAS provider will select a default value as required.
originating-Reference
Specifies the originating reference for the call to Open() (ADH disabled) or Service-req() (ADH enabled). When not specified, the MAS provider will select a default value as required.
specific-Information
Specifies the specific information as an instance of the OM class Specific-Information (see Specific-Information) to be passed with any dialog handling or service request or response.
For a call to Service-req() or Service-rsp for a fully or paritally formed dialog session, the precedence rules for common attributes in the Context and Session objects are different and the application-Context, destination-Reference and originating-Reference in the GSM-Context object cannot be used to override those contained in the dialog Session object.

5.3.8 GSM-Map-Assoc-Args

An instance of OM class GSM-Map-Assoc-Args represents the additional GSM specific MAP association arguments that are optionally supplied by the Session, Assoc-Argument or Assoc-Result objects and can be interrogated with the Get-Assoc-Info() function.

An instance of this OM class has the OM attributes of its superclasses, Map-Assoc-Args (see Map-Assoc-Args), and additionally the OM attributes listed in Table 62.

xmap_tab062.png

Table 62. OM Attributes of OM class GSM-Map-Assoc-Args

This OM class contains the following class-specific OM attributes:

destination-Reference
This attribute is a destination reference represented as an address string. The rules for supplying destination references is given in 3GPP TS 29.002. This attribute has syntax String(Address). See String(Address).
originating-Reference
This attribute is a originating reference represented as an address string. The rules for supplying originating references is given in 3GPP TS 29.002. This attribute has syntax String(Address). See String(Address).
specific-Information
This attribute is zero or more instances of OM class Specific-Information. See Specific-Information.

5.3.9 GSM-Notice-Result

An instance of OM class GSM-Notice-Result respresents the information that is returned in a Result-Or-Argument result by the Receive() function (see Receive) for a notice indication.

An instance of this OM class has the OM attributes of its superclasses, Notice-Result (see Notice-Result), and additionally the OM attributes listed in Table 7.

xmap_tab007.png

Table 7. OM Attributes of OM class GSM-Notice-Result

This OM class contains the following class-specific OM attributes:

Problem-Diagnostic
abnormal-event-detected-by-peer
(‘MAP_T_ABNORMAL_EVENT_DETECTED_BY_PEER’)
response-rejected-by-the-peer
(‘MAP_T_RESPONSE_REJECTED_BY_THE_PEER’)
abnormal-event-received-from-the-peer
(‘MAP_T_ABNORMAL_EVENT_RECEIVED_FROM_THE_PEER’)
message-cannot-be-delivered-to-the-peer
(‘MAP_T_MESSAGE_CANNOT_BE_DELIVERED_TO_THE_PEER’)

The following values of the problem code of the TC-R-REJECT and TC-U-REJECT primitive are mapped to the values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows:

TC Problem Code MAP Diagnostic
general-problem(0)
unrecognized-component(0) abormal-event-detected-by-the-peer
mistyped-component(1) abormal-event-detected-by-the-peer
badly-structured-component(2) abormal-event-detected-by-the-peer
invoke-problem(1)
duplicate-invoke-id(0)
unrecognized-operation(1)
mistyped-parameter(2)
resource-limitiation(3)
initiating-release(4)
unrecognized-linked-id(5) abormal-event-detected-by-the-peer
linked-response-unexpected(6) response-rejected-by-the-peer
unexpected-linked-operation(7) response-rejected-by-the-peer
return-result-problem(2)
unrecognized-invoke-id(0) response-rejected-by-the-peer
return-result-unexpected(1) response-rejected-by-the-peer
mistyped-parameter(2) response-rejected-by-the-peer
return-error-problem(3)
unrecognized-invoke-id(0) response-rejected-by-the-peer
return-error-unexpected(1) response-rejected-by-the-peer
unrecognized-error(2) response-rejected-by-the-peer
unexpected-error(3) response-rejected-by-the-peer
mistyped-parameter(4) response-rejected-by-the-peer

The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows:

TC Problem Code MAP Diagnostic
general-problem(0) abormal-event-received-from-the-peer
invoke-problem(1)
unrecognized-linked-id(5) abormal-event-received-from-the-peer
return-result-problem(2)
unrecognized-invoke-id(0) abnormal-event-received-from-the-peer
return-error-problem(3)
unrecognized-invoke-id(0) abnormal-event-received-from-the-peer

5.3.10 GSM-Open-Argument

An instance of OM class GSM-Open-Argument represents the information that is supplied as an argument to the Open() function (see Open) or is returned by the Receive() function (see Receive) for an open indication.

An instance of this OM class has the OM attributes of its superclasses, Open-Argument (see Open-Argument), and additionally the OM attributes listed in Table 1.

xmap_tab001.png

Table 1. OM Attributes of OM class GSM-Open-Argument

This OM class contains the following class-specific OM attributes:

application-Context
Specifies the application context for the dialog. When not specified, the MAS will provide a default application context when required.
destination-Reference
This attribute is a destination reference represented as an address string. The rules for supplying destination references is given in 3GPP TS 29.002. This attribute has syntax String(Address). See String(Address).
originating-Reference
This attribute is a originating reference represented as an address string. The rules for supplying originating references is given in 3GPP TS 29.002. This attribute has syntax String(Address). See String(Address).
specific-Information
This attribute is an instance of OM class Specific-Information. See Specific-Information.

5.3.11 GSM-P-Abort-Result

An instance of OM class GSM-P-Abort-Result represents the information that is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a provider abort indication.

An instance of this OM class has the OM attributes of its superclasses, P-Abort-Result (see P-Abort-Result), and additionally the OM attributes listed in Table 6.

xmap_tab006.png

Table 6. OM Attributes of OM class GSM-P-Abort-Result

This OM class contains the following class-specific OM attributes:

This OM class corresponds to the MAP-P-ABORT indication primitive of 3GPP TS 29.002 which contains Provider reason and Source parameters. This indication can result from the receipt of the local MAS provider of a map-providerAbort dialogue PDU or as a result of the receipt of a TC-U-ABORT or TC-P-ABORT indication primitive from the underlying TC provider. A TC-P-ABORT can either be because of an error detected in the dialogue user, or due to receipt of a TR-P-ABORT indication primitive.

provider-Reason
provider-malfunction
(‘MAP_E_PROVIDER_MALFUNCTION’) When the source is MAP, this represents a malfunction at the MAP level at the peer entity. When the source is TC, this represents the TC-P-ABORT reasons: unrecognised-message-type, badly-formatted-transaction-portion, incorrect-transaction-portion or abnormal-dialogue. When the source is NSP, this represents a malfunction at the network service level at the peer entity.
supporting-dialogue-transaction-released
(‘MAP_E_SUPPORTING_DIALOGUE_TRANSACTION_RELEASED’) When the source is TC, this represents the TC-P-ABORT reason unrecognised-transaction-id.
resource-limitation
(‘MAP_E_RESOURCE_LIMITATION’) When the source is MAP, this represents congestion toward the MAP peer service-user. When the source is TC, this represents resource-limitation received in a TC-P-ABORT.
maintenance-activity
(‘MAP_E_MAINTENANCE_ACTIVITY’) When the source is MAP, this represents maintenance activity at the MAP peer service-user. When the source is NSP, this represents maintenance at the network peer service level.
version-incompatibility
(‘MAP_E_VERSION_INCOMPATIBILITY’) When the source is TC, this represents a TC-P-ABORT indicating no-common-dialogue-portion or incorrect-transaction-portion received in the dialogue initated state.
abnormal-map-dialogue
(‘MAP_E_ABNORMAL_MAP_DIALOGUE’) When the source is MAP, this represents a MAP dialogue that is not in accordance with the specified application context.

source
map-problem
(‘MAP_E_MAP_PROBLEM’)
tc-problem
(‘MAP_E_TC_PROBLEM’)
network-service-problem
(‘MAP_E_NETWORK_SERVICE_PROBLEM’)

p-Abort-Reason
This attribute reflects the MAP provider abort reason (this is the information passed by the remote MAP provider in the MAP-P-ABORT dialogue PDU in the AABT APDU) and has one of the following values:
0abnormal-dialogue(0)
(‘MAP_E_ABNORMAL_DIALOGUE’)
1invalid-pdu(1)
(‘MAP_E_INVALID_PDU’)

p-Abort-Cause
This attribute reflects the TC provider abort cause (this is the information passed by the remote TCAP provider in the TCAP P-ABORT PDU) and has one of the following values:
0unrecognized-message-type(0)
(‘MAP_E_UNRECOGNIZED_MESSAGE_TYPE’)
1unrecognized-transaction-id(1)
(‘MAP_E_UNRECOGNIZED_TRANSACTION_ID’)
2badly-formatted-transaction-portion(2)
(‘MAP_E_BADLY_FORMATTED_TRANSACTION_PORTION’)
3incorrect-transaction-portion(3)
(‘MAP_E_INCORRECT_TRANSACTION_PORTION’)
4resource-limitation(4)
(‘MAP_E_RESOURCE_LIMITATION’)

The component sublayer will decide to abort a dialogue and discard any components received if an incorrect dialogue portion (e.g. syntactically incorrect or inopportune) is received or if no common version of the dialogue portion control APDUs can be agreed to. It informs its TC-user via a TC-P-ABORT indication primitive with “P-Abort” in the primtiive set to respectively “abnormal dialogue” or “no common dialogue portion”.

5abnormal-dialogue(5)
(‘MAP_E_ABNORMAL_DIALOGUE’) This is a local value and the numeric value is arbitrarily assigned.
6no-common-dialogue-portion(6)
(‘MAP_E_NO_COMMON_DIALOGUE_PORTION’) This is a local value and the numeric value is arbitrarily assigned.
1281unrecognized-package-type
1282incorrect-trans-portion
1283badly-structured-trans-portion
1284unassigned-responding-trans-id
1285permission-to-release-problem
1286resource-unavailable
1unrecognized-package-type
2incorrect-transaction-portion
3badly-structured-transaction-portion
4unassigned-responding-transaction-id
5permission-to-release-problem
6resource-unavailable
7unrecognized-dialogue-portion-id
8badly-structured-dialogue-portion
9missing-dialogue-portion
10inconsistent-dialogue-portion

report-Cause
Specifies the SCCP return cause resulting in local provider abort. It has one of the following values:
00000000no-translations-for-address-of-such-nature(0)
00000001no-translation-for-this-specific-address(1)
00000010subsystem-congestion(2)
00000011subsystem-failure(3)
00000100unequipped-user(4)
00000101mtp-failuire(5)
00000110network-congestion(6)
00000111sccp-unqualified(7)
00001000error-in-message-transport(8)
00001001error-in-local-processing(9)
00001010destination-cannot-perform-reassembly(10)
00001011sccp-failure(11)
00001100hop-counter-violation(12)
00001101segmentation-not-supported(13)
00001110segmentation-failure(14)

In addition, if the local SCCP provider is an ANSI SCCP provider,42 the SCCP return cause can also contain one of the following values:

11110111message-change-failure(247)
11111000invalid-ins-routing-request(248)
11111001invalid-isni-routing-request(249)
11111010unauthorized-message(250)
11111011message-incompatibility(251)
11111100cannot-perform-isni-constrained-routing(252)
11111101redundant-isni-constrained-routing-information(253)
11111110unable-to-perform-isni-identification(254)

5.3.12 GSM-Refuse-Result

An instance of OM class GSM-Refuse-Result represents the information that is supplied as an argument to the Refuse() function (see Refuse) or is returned by the Receive() function (see Receive).

An instance of this OM class has the OM attributes of its superclasses, Refuse-Result, and additionally the OM attributes listed in Table 3.

xmap_tab003.png

Table 3. OM Attributes of OM class GSM-Refuse-Result

This OM class contains the following class-specific OM attributes:

application-Context
Specifies the highest version alternate application context supported by the refusing mobile application entity when refusal is due to application-context-not-supported.
refuse-Reason
This attribute provides the reason for refusal. Its value can be one of the following:
no-reason-given
(‘MAP_T_NO_REASON_GIVEN’ ‘0’) This reason is transmitted and is provided directly in a received ‘map-refuse’ dialogue PDU.
invalid-destination-reference
(‘MAP_T_INVALID_DESTINATION_REFERENCE’ ‘1’) This reason is transmitted and is provided directly in a received ‘map-refuse’ dialogue PDU.
invalid-originating-reference
(‘MAP_T_INVALID_ORIGINATING_REFERENCE’ ‘2’) This reason is transmitted and is provided directly in a received ‘map-refuse’ dialogue PDU.
encapsulated-AC-not-supported
(‘MAP_T_ENCAPSULATED_AC_NOT_SUPPORTED’ ‘3’) This reason is transmitted and is provided directly in a received ‘map-refuse’ dialogue PDU. This reason is not used in dialogues with an application context different from secureTransportHandling.
transport-protection-not-adequate
(‘MAP_T_TRANSPORT_PROTECTION_NOT_ADEQUATE’ ‘4’) This reason is transmitted and is provided directly in a received ‘map-refuse’ dialogue PDU. This reason is not used in dialogues with an application context different from secureTransportHandling.
remote-node-not-reachable
(‘MAP_T_REMOTE_NODE_NOT_REACHABLE’) This reason is not transmitted and may not be specified as a refuse-Reason when calling Refuse().
application-context-not-supported
This refuse reason is given if a TC-U-ABORT is received by the local Mobile Application Service provider while an open request is pending and the Abort-Reason is “application context not supported”.
potential-version-incompatibility
(‘MAP_T_POTENTIAL_VERSION_INCOMPATIBILITY’) This refuse reason is given if a TC-P-ABORT is received by the local Mobile Application Service provider while an open request is pending and the P-Abort cause is “incorrect-transaction-portion” or “no-common-dialogue-portion”.
secured-transport-not-possible
(‘MAP_T_SECURED_TRANSPORT_NOT_POSSIBLE’) This reason is not transmitted.

specific-Information
This attribute provides user-specific information that is passed transparently between peer mobile application service users as part of dialog establishment. This attribute is an instance of OM class Specific-Information. See Specific-Information.

5.3.13 GSM-Release-Argument

5.3.14 GSM-Release-Result

5.3.15 GSM-Service-Argument

An instance of OM class GSM-Service-Argument represents the information that is supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive).

An instance of this OM class has the OM attributes of its superclasses, Service-Argument, and additionally the OM attributes listed in Table 63.

xmap_tab063.png

Table 63. OM Attributes of OM class GSM-Service-Argument

This OM class contains the following class-specific OM attributes:

application-Context
destination-Reference
originating-Reference
specific-Information
This attribute provides user-specific information that is passed transparently between peer mobile application service users as part of dialog establishment. This attribute is an instance of OM class Specific-Information.

5.3.16 GSM-Service-Error

An instance of concrete OM class GSM-Service-Error represents error information that is supplied as a response to a service operation, supplied as the Argument argument to the Service-rsp() function (see Service-rsp) or is returned as a Result-Or-Argument result by the Receive() function (see Receive) for a GSM service confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Error, Service-Error. It defines no attributes of its own.

problem
The superclass problem attribtue represents the GSM service user-Error. Values for the problem superclass attribute are defined as follows:
  • Reject Errors

    Reject GSM-Service-Error problem values and parameter syntaxes are defined in this GSM MAP package and are described in Reject Errors.

  • Generic Errors

    Generic GSM-Service-Error problem values and parameter syntaxes are defined in this GSM MAP package and are described in Generic Errors.

  • Identification and Numbering Errors

    Identification and Numbering GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Identification and Numbering Errors.

  • Subscription Errors

    Subscription GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Subscription Errors.

  • Handover Errors

    Handover GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Handover Errors.

  • Operation and Maintenance Errors

    Operation and Maintenance GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Operation and Maintenance Errors.

  • Call Handling Errors

    Call Handling GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Call Handling Errors.

  • Any Time Interrogation Errors

    Any Time Interrogation GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Any Time Interrogation Errors.

  • Any Time Information Handling Errors

    Any Time Information Handling GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Any Time Information Handling Errors.

  • Supplementary Service Errors

    Supplementary Service GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Supplementary Service Errors.

  • Short Message Service Errors

    Short Message Service GSM-Service-Error problem values and parameter syntaxes are defined in the GSM MAP Short Message Service services package and are described in Short Message Service Errors.

  • Group Call Errors

    Group Call GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Group Call Errors.

  • Location Service Errors

    Location Service GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Location Service Errors.

  • Mobility Management Errors

    Mobility Management GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Mobility Management Errors.

  • Secure Transport Errors

    Secure Transport GSM-Service-Error problem values and parameter syntaxes are defined in a future GSM MAP services package and are described in Secure Transport Errors.


parameter
The superclasss parameter attribute, which may or may not be present, indicates the additional information available with the service user error. This information is contained in as an Object(Encoding) or is defined by a Mobile Application Services package. See GSM MAP Errors.

5.3.17 GSM-Service-Reject

An instance of concrete OM class GSM-Service-Reject represents error information that is supplied as a response to a service operation, supplied as the Argument argument to the Service-rsp() function (see Service-rsp) or is returned as a Result-Or-Argument result by the Receive() function (see Receive) for a GSM service confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Error, Service-Reject. It defines no attributes of its own.

problem
Values for the problem superclass attribute (see Error) represent provider errors and values are defined as follows:
duplicated-invoke-id
(‘MAP_E_DUPLICATED_INVOKE_ID’)
not-supported-service
(‘MAP_E_NOT_SUPPORTED_SERVICE’)
mistyped-parameter
(‘MAP_E_MISTYPED_PARAMETER’)
resource-limitation
(‘MAP_E_RESOURCE_LIMITATION’)
initiating-release
(‘MAP_E_INITIATING_RELEASE’) That is, the peer has already initiated release of the dialogue and the service has to be released.
unexpected-response-from-the-peer
(‘MAP_E_UNEXPECTED_RESPONSE_FROM_THE_PEER’)
service-completion-failure
(‘MAP_E_SERVICE_COMPLETION_FAILURE’)
no-response-from-the-peer
(‘MAP_E_NO_RESPONSE_FROM_THE_PEER’)
invalid-response-receceived
(‘MAP_E_INVALID_RESPONSE_RECEIVED’)

parameter
The superclasss parameter attribute, which may or may not be present, indicates the additional information available with the service provider error. This information is contained in as an Object(Encoding) or is defined by a Mobile Application Services package.

5.3.18 GSM-Service-Result

An intance of OM class GSM-Service-Result represents the information that is supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a service confirmation.

An instance of this OM class has the OM attributes of its superclasses, Service-Result, GSM-Close-Argument and GSM-Abort-Argument, and additionally the OM attributes listed in Table 59.

xmap_tab059.png

Table 59. OM Attributes of OM class GSM-Service-Result

This OM class contains the following class-specific OM attributes:

specific-Information
This attribute provides user-specific information that is passed transparently between peer mobile application service users as part of dialog establishment. This attribute is an instance of OM class Specific-Information.

5.3.19 GSM Data Types

5.3.19.1 Access-Network-Signal-Info

An instance of OM class Access-Network-Signal-Info represents access network signalling information contained in an an-APDU.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionalyt the OM attributes listed in Table 415.

xmap_tab415.png

Table 415. OM Attributes of OM class Access-Network-Signal-Info

This OM class contains the following class-specific OM attributes:

access-Network-Protocol-Id
An enumeration containing one of the following values:
ts3g-48006
(‘MAP_T_TS3G_48006’ ‘1’)
ts3g-25413
(‘MAP_T_TS3G_25413’ ‘2’)
If the sequence contains this parameter with any other value than the ones listed, the receiver shall ignore the entire AccessNetworkSignalInfo sequence.
signal-Info
LongSignalInfo :;= OCTET STRING (SIZE(1..2560)) The value 2560 represents the maximum number of octets that is available to carry a signle instance of the LongSignalInfo data type using White Book SCCP with the maximum number of segments. It takes into account the octets used by the lower layers of the protocol, and other information elements that may be included in the same component.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.2 Basic-Service-Code

An instance of the OM class Basic-Service-Code provides the specification of a basic mobile service code as a single byte octet string. An instance of this class has all of the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 102.

xmap_tab102.png

Table 102. OM Attributes of OM class Basic-Service-Code

The attributes of the OM class represent a choice and exactly one of the attributes must be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

bearer-Service
BearerServiceCode ::= OCTET STRING (SIZE (1))
teleservice
TeleserviceCode ::= OCTET STRING (SIZE (1))

5.3.19.3 Cell-Global-Id-Or-Service-Area-Id-Or-LAI

An instance of OM class Cell-Global-Id-Or-Service-Area-Id-Or-LAI represents a global cell id, a service area id, or a local area id.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 422.

xmap_tab422.png

Table 422. OM Attributes of OM class Cell-Global-Id-Or-Service-Area-Id-Or-LAI

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

cell-Global-Id-Or-Service-Area-Id-Fixed-Length
CellGlobalIdOrServiceAreaIdFixedLength ::= OCTET STRING (SIZE (7)) Refers to Cell Global Identification or Service Area Identification defined in 3GPP TS 23.003. The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code 3rd digit; bits 8765, mobile network code 2rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octet 4 and 5, Location Area Code according to 3GPP TS 24.008; octet 6 and 7, Cell Identity (CI) value or Service Area Code (SAC) value according to 3GPP TS 23.003.
lai-Fixed-Length
LAIFixedLength ::= OCTET STRING (SIZE (5)) Refers to Location Area Identification in 3GPP TS 23.003. The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code 3rd digit; bits 8765, mobile network code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, Location Area Code according to 3GPP TS 24.008.

5.3.19.4 EMLPP-Info

An instance of OM class EMLPP-Info represents the priority of an EMLPP call.

An instances of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 418.

xmap_tab418.png

Table 418. OM Attributes of OM class EMLPP-Info

This OM class contains the following class-specific OM attributes:

maximum-Entitled-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
default-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.5 Ext-Basic-Service-Code

An instance of the OM class Ext-Basic-Service-Code provides the specification of an extensible basic mobile service code. An instance of this class has all of the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 412.

xmap_tab412.png

Table 412. OM Attributes of OM class Ext-Basic-Service-Code

The attributes of the OM class represent a choice and exactly one of the attributes must be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

ext-Bearer-Service
Ext-BearerServiceCode ::= OCTET STRING (SIZE(1..5)) This type is used to represent the code identifying a single bearer service, a group of bearer services, or all bearer services. The services are defined in 3GPP TS 22.002. The internal structure is defined as follows: octet 1, plmn-specific bearer services, bits 87654321, defined by the HPLMN operator; rest of bearer services, bit 8, 0 (ununsed); bits 7654321, group (bits 7654), and rate, if applicable (bits 321); octets 2-5: reserved for future use. If received the Ext-BearerServiceCode shall be treated according to the exception handling defined for the operation that uses this type. Ext-BearerServiceCode includes all values defined for BearerServiceCode.
ext-Teleservice
Ext-TeleserviceCode ::= OCTET STRING (SIZE(1..5)) This type is used to represent the code identifying a single teleservice, group of teleservices, or all teleservices. The services are defined in GSM TS 22.003. The internal structure is defined as follows: octet 1, bits 87654321, group (bits 8765) and specific service (bits 4321); octets 2-5, reserved for future use. If received, Ext-TeleserviceCode shall be treated according to the exception handling defined for the operation that uses this type. Ext-TeleserviceCode includes all values defined for TeleserviceCode.

5.3.19.6 Extension-Container

An instance of OM class Extension-Container represents the corresonding ExtensionContainer of the GSM MAP. This object is used to contain extension parameters that are used by a number of GSM MAP mobile application services.

An instance of this OM class has the OM attributes of its superclass, Object, and additionally the OM attributes listed in Table 41.

xmap_tab041.png

Table 41. OM Attributes of OM class Extension-Container

This OM class contains the following class-specific OM attributes:

private-Extension-List
This attribute is an optional list of private extensions.
pcs-Extensions
This attribute is an optional sequence of PCS extensions.

5.3.19.7 External-Signal-Info

An instance of OM class External-Signal-Info represents external signal information.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 423.

xmap_tab423.png

Table 423. OM Attributes of OM class External-Signal-Info

This OM class contains the following class-specific OM attributes:

protocol-Id
An enumeration containing one of the following values:
gsm-0408
(‘MAP_T_GSM_0408’ ‘1’)
gsm-0806
(‘MAP_T_GSM_0806’ ‘2’)
gsm-bssmap
(‘MAP_T_GSM_BSSMAP’ ‘3’)
ets-300102-1
(‘MAP_T_ETS_300102_1’ ‘4’)

signal-Info
SignalInfo ::= OCTET STRING (SIZE (1..200)) The value 200 represents the theoretical maximum number of octets that is available to carry a single instance of the SignalInfo data type, without requiring segmentation to cope with the network layer service. However, the actual maximum size available for an instance of the data type may be lower, especially when other information elements have to be included in the same component. Information about the internal structure is given in 3GPP TS 29.002 section 7.6.9.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container. This attribute must not be used in version 2 application contexts.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.8 Ext-External-Signal-Info

An instance of OM class Ext-External-Signal-Info represents extended external signal information.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 424.

xmap_tab424.png

Table 424. OM Attributes of OM class Ext-External-Signal-Info

This OM class contains the following class-specific OM attributes:

ext-Protocol-Id
An enumeration containing one of the following values:
ets-300356
(‘MAP_T_ETS_300356’ ‘1’)
For sequences containing this parameter with any other value than the ones listed, the receiver shall ignore the entire Ext-ExternalSignalInfo sequence.
signal-Info
SignalInfo ::= OCTET STRING (SIZE (1..200)) The value 200 represents the theoretical maximum number of octets that is available to carry a single instance of the SignalInfo data type, without requiring segmentation to cope with the network layer service. However, the actual maximum size available for an instance of the data type may be lower, especially when other information elements have to be included in the same component. Information about the internal structure is given in 3GPP TS 29.002 section 7.6.9.10.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.9 HLR-List

An instance of HLR-List represents a list of HLR identities.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 421.

xmap_tab421.png

Table 421. OM Attributes of OM class HLR-List

This OM class contains the following class-specific OM attributes:

hlr-Id
One to fifty (maxNumOfHLR-Id) instances of an hlr-Id attributes which is coded as an IMSI, with the leading digits of IMSI, i.e. (MCC, MNC, leading digits of MSIN) forming HLR Id defined in 3GPP TS 23.003.

5.3.19.10 Identity

An instance of OM class Identity represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 413.

xmap_tab413.png

Table 413. OM Attributes of OM Class Identity

This OM class represents a choice and exactly one instance of one attribute shall exist in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
ismi-With-LMSI
This choice attribute is an instance of OM class IMSI-With-LMSI. See IMSI-With-LMSI.

5.3.19.11 IMSI-With-LMSI

An instance of OM class IMSI-With-LMSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 414.

xmap_tab414.png

Table 414. OM Attributes of OM Class IMSI-With-LMSI

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string. A special value of ‘00000000’ indicates that the LMSI is not in use.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.12 LCS-Client-External-ID

An instances of LCS-Client-External-ID represent the external identifier for an LCS client.

An instances of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 420.

xmap_tab420.png

Table 420. OM Attributes of OM class LCS-Client-External-ID

This OM class contains the following class-specific OM attributes:

external-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.13 MC-SS-Info

An instance of OM class MC-SS-Info represents multicall bearer supplementary service information.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attribtues listed in Table 417.

xmap_tab417.png

Table 417. OM Attributes of OM class MC-SS-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
nbr-SB
MaxMC-Bearers ::= INTEGER (2..7)
nbr-User
MC-Bearers ::= INTEGER(1..7)
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.14 NAEA-Preferred-CI

An instance of OM class NAEA-Preferred-CI represents the North American Equal Access preferred Carrier Identification.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 416.

xmap_tab416.png

Table 416. OM Attributes of OM class NAEA-Preferred-CI

This OM class contains the following class-specific OM attributes:

naea-Preferred-CIC
NAEA-CIC ::= OCTET STRING (SIZE(3)) The internal structure is defined by the Carrier Identification parameter in ANSI T1.113.3. Carrier codes between ‘000’ and ‘999’ may be encoded as 3 digits using ‘000’ to ‘999’, or as 4 digits using ‘0000’ to ‘0999’. Carrier codes between ‘1000’ and ‘9999’ are encoded using 4 digits.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.15 PCS-Extensions

An instances of OM class PCS-Extensions represents a sequence of PCS extensions each with an ASN.1 encoding. It is an optional attribute of OM class Extension-Container.

An instance of this OM class has the OM attributes of its superclass, Object, and additionally the OM attributes listed in Table 42.

xmap_tab042.png

Table 42. OM Attributes of OM class PCS-Extensions

This OM class contains the following class-specific OM attributes:

pcs-Extension
The pcs-Extension attribute consists of one or more ASN.1 encoded strings. Each string encoding is an element in a sequence of PCS extensions.

5.3.19.16 Private-Extension

An instance of OM class Private-Extension represents a single instance of private extension as defined by the MAP-EXTENSION macro of GSM MAP. Each private extension consists of a object identifier that identifies the type of the extension and an optional encoding of the extension value.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 39.

xmap_tab039.png

Table 39. OM Attributes of OM class Private-Extension

This OM class contains the following class-specific OM attributes:

ext-Type
The ext-Type attribute is an ASN.1 encoding of the extension type.
ext-Id
The ext-Id attribute is an object identifier that cannot exceed 16 octets in length and cannot exceed 16 sub-identifiers.

5.3.19.17 Private-Extension-List

An instance of OM class Private-Extension-List represents a list of private extensions used as an optional attribute of the OM class Extension-Container. The list may contain between one and ten private extensions.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 40.

xmap_tab040.png

Table 40. OM Attributes of OM class Private-Extension-List

This OM class contains the following class-specific OM attributes:

private-Extension
This attribute represents an instance of the MAP-CONTAINTER macro from the GSM MAP. There may be one to ten private extensions in an extension list.

5.3.19.18 SLR-Arg-Extension-Container

An instance of OM class SLR-Arg-Extension-Container represents an extension container for use within the Subscriber-Location-Report-Arg argument. See Subscriber-Location-Report-Arg.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 426.

xmap_tab426.png

Table 426. OM Attributes of OM class SLR-Arg-Extension-Container

This OM class contains the following class-specific OM attributes:

private-Extension-List
This optional attribute is an instance of OM class Private-Extension-List. See Private-Extension-List.
slr-Arg-PCS-Extensions
This optional attribute is an instance of OM class SLR-Arg-PCS-Extensions. See SLR-Arg-PCS-Extensions.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.3.19.19 SLR-Arg-PCS-Extensions

An instance of OM class SLR-Arg-PCS-Extensions represents PCS extensions for use within the SLR-Arg-Extension-Container. See SLR-Arg-Extension-Container.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 427.

xmap_tab427.png

Table 427. OM Attributes of OM class SLR-Arg-PCS-Extensions

This OM class contains the following class-specific OM attributes:

extension
This optional attribute is an instance of OM class Extension. See Extension.
na-ESRK-Request
A Null value whose presence provides indication.

5.3.19.20 Specific-Information

An instance of OM class Specific-Information represents additional specific extensions or private extensions added to a GSM MAP dialogue.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 44.

xmap_tab044.png

Table 44. OM Attributes of OM class Specific-Information

This OM class contains the following class-specific OM attributes:

extensions
This optional attribute is zero or more instances of OM class Extension. See Extension.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container. This attribute may only be used with GSM MAP version 3 dialogues and is not applicable to version 1 or 2 dialogues.

5.3.19.21 Subscriber-Identity

An instance of OM class Subscriber-Identity represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 410. This OM class represents a choice and exactly one attributes shall be present in an instance of this object.

xmap_tab410.png

Table 410. OM Attributes of OM Class Subscriber-Identity

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).

5.4 GSM MAP Services Packages

5.4.1 GSM Mobile Service Package

OM Hierarchy
  • Object
    • Service-Argument
      • GSM-Service-Argument
        • Any-Time-Interrogation-Arg
        • Any-Time-Modification-Arg
        • Any-Time-Subscription-Interrogation-Arg
        • Authentication-Failure-Report-Arg
        • Cancel-Location-Arg
        • Check-IMEI-Arg
        • Delete-Subscriber-Data-Arg
        • Failure-Report-Arg
        • Forward-Access-Signalling-Arg
        • Forward-Check-SS-Indication-Arg
        • Insert-Subscriber-Data-Arg
        • Note-MM-Event-Arg
        • Note-Ms-Present-For-Gprs-Arg
        • Note-Subscriber-Data-Modified-Arg
        • Prepare-HO-Arg
        • Prepare-Subsequent-HO-Arg
        • Process-Access-Signalling-Arg
        • Provide-Subscriber-Info-Arg
        • Purge-MS-Arg
        • Reset-Arg
        • Restore-Data-Arg
        • Send-Authentication-Info-Arg
        • Send-End-Signal-Arg
        • Send-Identification-Arg
        • Send-Routing-Info-For-Gprs-Arg
        • Update-Gprs-Location-Arg
        • Update-Location-Arg
    • Service-Result
      • GSM-Service-Result
        • Any-Time-Interrogation-Res
        • Any-Time-Modification-Res
        • Any-Time-Subscription-Interrogation-Res
        • Authentication-Failure-Report-Res
        • Cancel-Location-Res
        • Check-IMEI-Res
        • Delete-Subscriber-Data-Res
        • Failure-Report-Res
        • Insert-Subscriber-Data-Res
        • MNP-Info-Res
        • Note-MM-Event-Res
        • Note-Ms-Present-For-Gprs-Res
        • Note-Subscriber-Data-Modified-Res
        • Prepare-HO-Res
        • Prepare-Subsequent-HO-Res
        • Provide-Subscriber-Info-Res
        • Purge-MS-Res
        • Restore-Data-Res
        • Send-Authentication-Info-Res
        • Send-End-Signal-Res
        • Send-Identification-Res
        • Send-Routing-Info-For-Gprs-Res
        • Update-Gprs-Location-Res
        • Update-Location-Res

5.4.1.1 Add-Info

An instance of OM class Add-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 124.

xmap_tab125.png

Table 125. OM Attributes of OM Class Add-Info

This OM class contains the following class-specific OM attributes:

imeisv
IMEI ::= TBCD-STRING(SIZE(8)) Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in 3GPP TS 23.003. If the SVN is not present, the last octet shall contain digit 0 and a filler. If present, the SVN shall be included in the last octet.
skip-Subscriber-Data-Update
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.2 Allowed-UMTS-Algorithms

An instance of OM class Allowed-UMTS-Algorithms represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 148.

xmap_tab148.png

Table 148. OM Attributes of OM Class Allowed-UMTS-Algorithms

This OM class contains the following class-specific OM attributes:

integrity-Protection-Algorithm
PermittedIntegrityProtectionAlgorithms ::= OCTET STRING (SIZE(1..9)) Octets contain a complete PermittedIntegrityProtectionAlgorithms data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
encryption-Algorithm
PermittedEncryptionAlgorithm ::= OCTET STRING (SIZE(1..9)) Octets contain a complete PermittedEncryptionAlgorithms data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.3 AMBR

An instance of OM class AMBR represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 183.

xmap_tab183.png

Table 183. OM Attributes of OM Class AMBR

This OM class contains the following class-specific OM attributes:

max-Requested-Bandwidth-UL
Bandwidth ::= INTEGER Bits per second.
max-Requested-Bandwidth-DL
Bandwidth ::= INTEGER Bits per second.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.4 Any-Time-Interrogation-Arg

An instance of OM class Any-Time-Interrogation-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 288.

xmap_tab288.png

Table 288. OM Attributes of OM Class Any-Time-Interrogation-Arg

This OM class contains the following class-specific OM attributes:

subscriber-Identity
This attribute is an instance of OM class Subscriber-Identity. See Subscriber-Identity.
requested-Info
This attribute is an instance of OM class Requested-Info. See Requested-Info.
gsmSCF-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.5 Any-Time-Interrogation-Res

An instance of OM class Any-Time-Interrogation-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 289.

xmap_tab289.png

Table 289. OM Attributes of OM Class Any-Time-Interrogation-Res

This OM class contains the following class-specific OM attributes:

subscriber-Info
This attribute is an instance of OM class Subscriber-Info. See Subscriber-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.6 Any-Time-Modification-Arg

An instance of OM class Any-Time-Modification-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 299.

xmap_tab299.png

Table 299. OM Attributes of OM Class Any-Time-Modification-Arg

This OM class contains the following class-specific OM attributes:

subscriber-Identity
This attribute is an instance of OM class Subscriber-Identity. See Subscriber-Identity.
gsmSCF-Address
An ISDN Address String.
modification-Request-For-CF-Info
This optional attribute is an instance of OM class Modification-Request-For-CF-Info. See Modification-Request-For-CF-Info.
modification-Request-For-CB-Info
This optional attribute is an instance of OM class Modification-Request-For-CB-Info. See Modification-Request-For-CB-Info.
modification-Request-For-CSI
This optional attribute is an instance of OM class Modification-Request-For-CSI. See Modification-Request-For-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
long-FTN-Supported
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.
modification-Request-For-ODB-Data
This optional attribute is an instance of OM class Modification-Request-For-ODB-Data. See Modification-Request-For-ODB-Data.
modification-Request-For-IP-SM-GW-Data
This optional attribute is an instance of OM class Modification-Request-For-IP-SM-GW-Data. See Modification-Request-For-IP-SM-GW-Data.

5.4.1.7 Any-Time-Modification-Res

An instance of OM class Any-Time-Modification-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 300.

xmap_tab300.png

Table 300. OM Attributes of OM Class Any-Timer-Modification-Res

This OM class contains the following class-specific OM attributes:

ss-Info-For-CSE
This optional attribute is an instance of OM class Ext-SS-Info-For-CSE. See Ext-SS-Info-For-CSE.
camel-Subscription-Info
This optional attribute is an instance of OM class CAMEL-Subscription-Info. See CAMEL-Subscription-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
odb-Info
This optional attribute is an instance of OM class ODB-Info. See ODB-Info.

5.4.1.8 Any-Time-Subscription-Interrogation-Arg

An instance of OM class Any-Time-Subscription-Interrogation-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 290.

xmap_tab290.png

Table 290. OM Attributes of OM Class Any-Time-Subscription-Interrogation-Arg

This OM class contains the following class-specific OM attributes:

subscriber-Identity
This attribute is an instance of OM class Subscriber-Identity. See Subscriber-Identity.
requested-Subscription-Info
This attribute is an instance of OM class Requested-Subscription-Info. See Requested-Subscription-Info.
gsmSCF-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
long-FTN-Supported
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.9 Any-Time-Subscription-Interrogation-Res

An instance of OM class Any-Time-Subscription-Interrogation-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 291.

xmap_tab291.png

Table 291. OM Attributes of OM Class Any-Time-Subscription-Interrogation-Res

This OM class contains the following class-specific OM attributes:

call-Forwarding-Data
This optional attribute is an instance of OM class Call-Forwarding-Data. See Call-Forwarding-Data.
call-Barring-Data
This optional attribute is an instance of OM class Call-Barring-Data. See Call-Barring-Data.
odb-Info
This optional attribute is an instance of OM class ODB-Info. See ODB-Info.
camel-Subscription-Info
This optional attribute is an instance of OM class CAMEL-Subscription-Info. See CAMEL-Subscription-Info.
supported-VLR-CAMEL-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

supported-SGSN-CAMEL-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
offered-Camel4-CSIs-In-VLR
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

offered-Camel4-CSIs-In-SGSN
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

msisdn-BS-List
A Null value whose presence indicates support.

5.4.1.10 APN-Configuration-Profile

An instance of OM class APN-Configuration-Profile represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 179.

xmap_tab179.png

Table 179. OM Attributes of OM Class APN-Configuration-Profile

This OM class contains the following class-specific OM attributes:

default-Context
ContextID ::= INTEGER(1..50)
complete-Data-List-Included
A Null value whose presence provides indication.
eps-Data-List
This optional attribute is an instance of OM class EPS-Data-List. See EPS-Data-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.11 APN-Configuration

An instance of OM class APN-Configuration represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 181.

xmap_tab181.png

Table 181. OM Attributes of OM Class APN-Configuration

This OM class contains the following class-specific OM attributes:

context-Id
ContextID ::= INTEGER(1..50)
served-Party-IP-Address
PDP-Address ::= OCTET STRING (SIZE(1..16)) Octets are coded according to 3GPP TS 29.060. The possible values are: 1-7 octets X.25 address type, 4 octets IPv4 address type, 16 octets IPv6 address type.
apn
APN ::= OCTET STRING (SIZE(2..63)) Octets are coded according to 3GPP TS 23.003.
eps-Qos-Subscribed
This optional attribute is an instance of OM class EPS-QoS-Subscribed. See EPS-QoS-Subscribed.
pdn-Gw-Identity
This optional attribute is an instance of OM class PDN-GW-Identity. See PDN-GW-Identity.
pdn-Gw-Allocation-Type
An enumeration containing one of the following values:
static
(‘MAP_T_STATIC’ ‘0’)
dynamic
(‘MAP_T_DYNAMIC’ ‘1’)

vplmn-Address-Allowed
A Null value whose presence provides indication.
charging-Characteristics
ChargingCharacteristics ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 32.215.
ambr
This optional attribute is an instance of OM class AMBR. See AMBR.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.12 Authentication-Failure-Report-Arg

An instance of OM class Authentication-Failure-Report-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 140.

xmap_tab140.png

Table 140. OM Attributes of OM Class Authentication-Failure-Report-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
failure-Cause
An enumeration containing one of the following values:
wrong-user-response
(‘MAP_T_WRONG_USER_RESPONSE’ ‘0’)
wrong-network-signature
(‘MAP_T_WRONG_NETWORK_SIGNATURE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
re-attempt
A boolean value indicating whether reattempt should be performed.
access-Type
An enumeration containing one of the following values:
call
(‘MAP_T_CALL’ ‘0’)
emergency-call
(‘MAP_T_EMERGENCY_CALL’ ‘1’)
location-updating
(‘MAP_T_LOCATION_UPDATING’ ‘2’)
supplementary-service
(‘MAP_T_SUPPLEMENTARY_SERVICE’ ‘3’)
short-message
(‘MAP_T_SHORT_MESSAGE’ ‘4’)
gprs-attach
(‘MAP_T_GPRS_ATTACH’ ‘5’)
routing-area-updating
(‘MAP_T_ROUTING_AREA_UPDATING’ ‘6’)
service-request
(‘MAP_T_SERVICE_REQUEST’ ‘7’)
pdp-context-activation
(‘MAP_T_PDP_CONTEXT_ACTIVATION’ ‘8’)
pdp-context-deactivation
(‘MAP_T_PDP_CONTEXT_DEACTIVATION’ ‘9’)
gprs-detach
(‘MAP_T_GPRS_DETACH’ ‘10’)

rand
RAND ::= OCTET STRING (SIZE(16))
vlr-Number
This attribute refers to the ISDN number of a VLR. An ISDN Address String containing the ISDN address of the VLR.
sgsn-Number
This attribute refers to the ISDN number of an SGSN. An ISDN Address String containing the ISDN address of the SGSN.

5.4.1.13 Authentication-Failure-Report-Res

An instance of OM class Authentication-Failure-Report-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 141.

xmap_tab141.png

Table 141. OM Attributes of OM Class Authentication-Failure-Report-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.14 Authentication-Quintuplet

An instance of OM class Authentication-Quintuplet represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 136.

xmap_tab136.png

Table 136. OM Attributes of OM Class Authentication-Quintuplet

This OM class contains the following class-specific OM attributes:

rand
RAND ::= OCTET STRING (SIZE(16))
xres
XRES ::= OCTET STRING (SIZE(4..16))
ck
CK ::= OCTET STRING (SIZE(16))
ik
IK ::= OCTET STRING (SIZE(16))
autn
AUTN ::= OCTET STRING (SIZE(16))
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.15 Authentication-Set-List

An instance of OM class Authentication-Set-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 132. This OM class represents a choice and exactly one attributes shall be present in an instance of this object.

xmap_tab132.png

Table 132. OM Attributes of OM Class Authentication-Set-List

This OM class contains the following class-specific OM attributes:

triplet-List
TripleList ::= SEQUENCE SIZE(1..5) OF AuthenticationTriplet This optional attribute is an instance of OM class Triplet-List. See Triplet-List.
quintuplet-List
QuintupletList ::= SEQUENCE SIZE(1..5) OF AuthenticationQuintuplet This optional attribute is an instance of OM class Quintuplet-List. See Quintuplet-List.

5.4.1.16 Authentication-Triplet

An instance of OM class Authentication-Triplet represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 135.

xmap_tab135.png

Table 135. OM Attributes of OM Class Authentication-Triplet

This OM class contains the following class-specific OM attributes:

rand
RAND ::= OCTET STRING (SIZE(16))
sres
SRES ::= OCTET STRING (SIZE(4))
kc
KC ::= OCTET STRING (SIZE(8))
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.17 Basic-Service-Criteria

An instance of OM class Basic-Service-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 251.

xmap_tab251.png

Table 251. OM Attributes of OM Class Basic-Service-Criteria

This OM class contains the following class-specific OM attributes:

ext-Basic-Service-Code
One to five (maxNumOfCamelBasicServiceCriteria) instances of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.

5.4.1.18 Basic-Service-List

An instance of OM class Basic-Service-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 230.

xmap_tab230.png

Table 230. OM Attributes of OM Class Basic-Service-List

This OM class contains the following class-specific OM attributes:

ext-Basic-Service-Code
One to seventy (maxNumOfBasicServices) instances of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.

5.4.1.19 Bearer-Service-List

An instance of OM class Bearer-Service-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 198.

xmap_tab198.png

Table 198. OM Attributes of OM Class Bearer-Service-List

This OM class contains the following class-specific OM attributes:

ext-Bearer-Service-Code
One to fifty instances of Ext-BearerServiceCode.

Ext-BearerServiceCode ::= OCTET STRING (SIZE(1..5)) This type is used to represent the code identifying a single bearer service, a group of bearer services, or all bearer services. The services are defined in 3GPP TS 22.002. The internal structure is defined as follows: octet 1, plmn-specific bearer services, bits 87654321, defined by the HPLMN operator; rest of bearer services, bit 8, 0 (ununsed); bits 7654321, group (bits 7654), and rate, if applicable (bits 321); octets 2-5: reserved for future use. If received the Ext-BearerServiceCode shall be treated according to the exception handling defined for the operation that uses this type. Ext-BearerServiceCode includes all values defined for BearerServiceCode.

5.4.1.20 BSSMAP-Service-Handover-Info

An instance of OM class BSSMAP-Service-Handover-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 152.

xmap_tab152.png

Table 152. OM Attributes of OM Class BSSMAP-Service-Handover-Info

This OM class contains the following class-specific OM attributes:

bssmap-Service-Handover
BSSMAP-ServiceHandover ::= OCTET STRING (SIZE(1)) Octets are coded according to the Service Handover information element in 3GPP TS 48.008.
rab-Id
RAB-Id ::= INTEGER(1..255)
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.21 BSSMAP-Service-Handover-List

An instance of OM class BSSMAP-Service-Handover-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 151.

xmap_tab151.png

Table 151. OM Attributes of OM Class BSSMAP-Service-Handover-List

This OM class contains the following class-specific OM attributes:

bssmap-Service-Handover-Info

5.4.1.22 Call-Barring-Data

An instance of OM class Call-Barring-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 296.

xmap_tab296.png

Table 296. OM Attributes of OM Class Call-Barring-Data

This OM class contains the following class-specific OM attributes:

call-Barring-Feature-List
This attribute is an instance of OM class Ext-Call-Bar-Feature-List. See Ext-Call-Bar-Feature-List.
password
Password ::= NumericString (FROM (0|1|2|3|4|5|6|7|8|9)) (SIZE(4))
wrong-Password-Attempts-Counter
WrongPasswordAttemptsCounter ::= INTEGER(0..4)
notification-To-CSE
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.23 Call-Forwarding-Data

An instance of OM class Call-Forwarding-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 295.

xmap_tab295.png

Table 295. OM Attributes of OM Class Call-Forwarding-Data

This OM class contains the following class-specific OM attributes:

forwarding-Feature-List
This attribute is an instance of OM class Ext-Forw-Feature-List. See Ext-Forw-Feature-List.
notification-To-CSE
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.24 CAMEL-Subscription-Info

An instance of OM class CAMEL-Subscription-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 298.

xmap_tab298.png

Table 298. OM Attributes of OM Class CAMEL-Subscription-Info

This OM class contains the following class-specific OM attributes:

o-CSI
This optional attribute is an instance of OM class O-CSI. See O-CSI.
o-Bcsm-Camel-TDP-Criteria-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Criteria-List. See O-Bcsm-Camel-TDP-Criteria-List.
d-CSI
This optional attribute is an instance of OM class D-CSI. See D-CSI.
t-CSI
This optional attribute is an instance of OM class T-CSI. See T-CSI.
t-BCSM-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class T-BCSM-CAMEL-TDP-Criteria-List. See T-BCSM-CAMEL-TDP-Criteria-List.
vt-CSI
This optional attribute is an instance of OM class T-CSI. See T-CSI.
vt-BCSM-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class T-BCSM-CAMEL-TDP-Criteria-List. See T-BCSM-CAMEL-TDP-Criteria-List.
tif-CSI
A Null value whose presence provides indication.
tif-CSI-Notification-To-CSE
A Null value whose presence provides indication.
gprs-CSI
This optional attribute is an instance of OM class GPRS-CSI. See GPRS-CSI.
mo-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
ss-CSI
This optional attribute is an instance of OM class SS-CSI. See SS-CSI.
m-CSI
This optional attribute is an instance of OM class M-CSI. See M-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
specific-CSI-Deleted-List
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
ss-csi
(‘MAP_T_SS_CSI’ ‘1’)
tif-csi
(‘MAP_T_TIF_CSI’ ‘2’)
d-csi
(‘MAP_T_D_CSI’ ‘3’)
vt-csi
(‘MAP_T_VT_CSI’ ‘4’)
mo-sms-csi
(‘MAP_T_MO_SMS_CSI’ ‘5’)
m-csi
(‘MAP_T_M_CSI’ ‘6’)
gprs-csi
(‘MAP_T_GPRS_CSI’ ‘7’)
t-csi
(‘MAP_T_T_CSI’ ‘8’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘9’)
mg-csi
(‘MAP_T_MG_CSI’ ‘10’)
o-im-csi
(‘MAP_T_O_IM_CSI’ ‘11’)
d-im-csi
(‘MAP_T_D_IM_CSI’ ‘12’)
vt-im-csi
(‘MAP_T_VT_IM_CSI’ ‘13’)

mt-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
mt-sms-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class MT-SMS-CAMEL-TDP-Criteria-List. See MT-SMS-CAMEL-TDP-Criteria-List.
mg-CSI
This optional attribute is an instance of OM class MG-CSI. See MG-CSI.
o-IM-CSI
This optional attribute is an instance of OM class O-CSI. See O-CSI.
o-IM-Bcsm-Camel-TDP-Criteria-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Criteria-List. See O-Bcsm-Camel-TDP-Criteria-List.
d-IM-CSI
This optional attribute is an instance of OM class D-CSI. See D-CSI.
vt-IM-CSI
This optional attribute is an instance of OM class T-CSI. See T-CSI.
vt-IM-BCSM-CAMEL-TDP-Criterial-List
This optional attribute is an instance of OM class T-BCSM-CAMEL-TDP-Criteria-List. See T-BCSM-CAMEL-TDP-Criteria-List.

5.4.1.25 Cancel-Location-Arg

An instance of OM class Cancel-Location-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 126.

xmap_tab126.png

Table 126. OM Attributes of OM Class Cancel-Location-Arg

This OM class contains the following class-specific OM attributes:

identity
This attribute is an instance of OM class Identity. See Identity.
cancellation-Type
An enumeration containing one of the following values:
update-procedure
(‘MAP_T_UPDATE_PROCEDURE’ ‘0’)
subscription-withdraw
(‘MAP_T_SUBSCRIPTION_WITHDRAW’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
type-Of-Update
An enumeration containing one of the following values:
sgsn-change
(‘MAP_T_SGSN_CHANGE’ ‘0’)
mme-change
(‘MAP_T_MME_CHANGE’ ‘1’)

5.4.1.26 Cancel-Location-Res

An instance of OM class Cancel-Location-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 127.

xmap_tab127.png

Table 127. OM Attributes of OM Class Cancel-Location-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.27 Check-IMEI-Arg

An instance of OM class Check-IMEI-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 171.

xmap_tab171.png

Table 171. OM Attributes of OM Class Check-IMEI-Arg

This OM class contains the following class-specific OM attributes:

imei
IMEI ::= TBCD-STRING(SIZE(8)) Refers to International Mobile Station Equipment Identity defined in 3GPP TS 23.003. The last octet shall contain digit 0 and a filler.
requested-Equipment-Info
A bit string containing zero or more of the following bits:
equipment-status
(‘MAP_T_EQUIPMENT_STATUS’ ‘0’)
bmuef
(‘MAP_T_BMUEF’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.28 Check-IMEI-Res

An instance of OM class Check-IMEI-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 172.

xmap_tab172.png

Table 172. OM Attributes of OM Class Check-IMEI-Res

This OM class contains the following class-specific OM attributes:

equipment-Status
An enumeration containing one of the following values:
white-listed
(‘MAP_T_WHITE_LISTED’ ‘0’)
black-listed
(‘MAP_T_BLACK_LISTED’ ‘1’)
grey-listed
(‘MAP_T_GREY_LISTED’ ‘2’)

bmuef
This optional attribute is an instance of OM class UESBI-Iu. See UESBI-Iu.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.29 Chosen-Radio-Resource-Information

An instance of OM class Chosen-Radio-Resource-Information represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 156.

xmap_tab156.png

Table 156. OM Attributes of OM Class Chosen-Radio-Resource-Information

This OM class contains the following class-specific OM attributes:

chosen-Channel-Info
ChosenChannelInfo ::= OCTET STRING (SIZE(1)) Octets are coded according to the Chosen Channel information element in 3GPP TS 48.008.
chosen-Speech-Version
ChosenSpeechVersion ::= OCTET STRING (SIZE(1)) Octets are coded according to the Speech Version (chosen) information element in 3GPP TS 48.008.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.30 Codec-List

An instance of OM class Codec-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 161.

xmap_tab161.png

Table 161. OM Attributes of OM Class Codec-List

This OM class contains the following class-specific OM attributes:

codec1
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec2
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec3
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec4
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec5
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec6
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec7
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
codec8
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.31 Context-Id-List

An instance of OM class Context-Id-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 227.

xmap_tab227.png

Table 227. OM Attributes of OM Class Context-Id-List

This OM class contains the following class-specific OM attributes:

context-Id
One to fifty (maxNumOfPDP-Contexts) instances of ContextID which is an Integer value between one and 50. ContextID ::= INTEGER(1..50)

5.4.1.32 CSG-Subscription-Data-List

An instance of OM class CSG-Subscription-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 176.

xmap_tab176.png

Table 176. OM Attributes of OM Class CSG-Subscription-Data-List

This OM class contains the following class-specific OM attributes:

csg-Subscription-Data
Between one and fifty instances of the OM Class CSG-Subscription-Data. See CSG-Subscription-Data.

5.4.1.33 CSG-Subscription-Data

An instance of OM class CSG-Subscription-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 177.

xmap_tab177.png

Table 177. OM Attributes of OM Class CSG-Subscription-Data

This OM class contains the following class-specific OM attributes:

csg-Id
CSG-Id ::= BIT STRING (SIZE(27)) Coded according to 3GPP TS 23.003.
expiration-Date
Time ::= OCTET STRING (SIZE(4)) Octets are coded according to IETF RFC 3588.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.34 CUG-Feature-List

An instance of OM class CUG-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 212.

xmap_tab212.png

Table 212. OM Attributes of OM Class CUG-Feature-List

This OM class contains the following class-specific OM attributes:

cug-Feature
One to maxNumOfExt-BasicServiceGroups instances of OM Class CUG-Feature. See CUG-Feature.

5.4.1.35 CUG-Feature

An instance of OM class CUG-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 408.

xmap_tab408.png

Table 408. OM Attributes of OM Class CUG-Feature

This OM class contains the following class-specific OM attributes:

basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
preferential-CUG-Indicator
CUG-Index ::= INTEGER(0..32767) The internal structure is defined in ETS 300 138.
inter-CUG-Restrictions
InterCUG-Restrictions ::= OCTET STRING (SIZE(1)) Bits 876543, 000000 (unused); bits 21, 00, CUG only facilities; 01, CUG with outgoing access; 10, CUG with incoming access; 11, CUG with both outgoing and incoming access.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.36 CUG-Info

An instance of OM class CUG-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 209.

xmap_tab209.png

Table 209. OM Attributes of OM Class CUG-Info

This OM class contains the following class-specific OM attributes:

cug-Subscription-List
This attribute is an instance of OM class CUG-Subscription-List. See CUG-Subscription-List.
cug-Feature-List
This optional attribute is an instance of OM class CUG-Feature-List. See CUG-Feature-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.37 CUG-Subscription-List

An instance of OM class CUG-Subscription-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 210.

xmap_tab210.png

Table 210. OM Attributes of OM Class CUG-Subscription-List

This OM class contains the following class-specific OM attributes:

cug-Subscription
One to ten instances of OM class CUG-Subscription. See CUG-Subscription.

5.4.1.38 CUG-Subscription

An instance of OM class CUG-Subscription represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 211.

xmap_tab211.png

Table 211. OM Attributes of OM Class CUG-Subscription

This OM class contains the following class-specific OM attributes:

cug-Index
CUG-Index ::= INTEGER(0..32767) The internal structure is defined in ETS 300 138.
cug-Interlock
CUG-Interlock ::= OCTET STRING (SIZE(4))
intra-CUG-Options
An enumeration containing one of the following values:
no-cug-restrictions
(‘MAP_T_NO_CUG_RESTRICTIONS’ ‘0’)
cug-ic-call-barred
(‘MAP_T_CUG_IC_CALL_BARRED’ ‘1’)
cug-og-call-barred
(‘MAP_T_CUG_OG_CALL_BARRED’ ‘2’)

basic-Service-Group-List
This optional attribute is an instance of OM class Ext-Basic-Service-Group-List. See Ext-Basic-Service-Group-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.39 Current-Security-Context

An instance of OM class Current-Security-Context represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 137. The OM class represent a choice and exactly one attribute shall appear in an instance of this class.

xmap_tab137.png

Table 137. OM Attributes of OM Class Current-Security-Context

This OM class contains the following class-specific OM attributes:

gsm-Security-Context-Data
This choice attribute is an instance of OM class GSM-Security-Context-Data. See GSM-Security-Context-Data.
umts-Security-Context-Data
This choice attribute is an instance of OM class UMTS-Security-Context-Data. See UMTS-Security-Context-Data.

5.4.1.40 D-CSI

An instance of OM class D-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 236.

xmap_tab236.png

Table 236. OM Attributes of OM Class D-CSI

This OM class contains the following class-specific OM attributes:

dp-Analysed-Info-Criteria-List
This optional attribute is an instance of OM class DP-Analysed-Info-Criteria-List. See DP-Analysed-Info-Criteria-List.
camel-Capability-Handling
CamelCapabilityHandling ::= INTEGER(1..16) Value 1, CAMEL phase 1; value 2, CAMEL phase 2; value 3, CAMEL phase 3; value 4, CAMEL phase 4. Receiption of values greater than 4 shall be treated as CAMEL phase 4.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.41 Delete-Subscriber-Data-Arg

An instance of OM class Delete-Subscriber-Data-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 224.

xmap_tab224.png

Table 224. OM Attributes of OM Class Delete-Subscriber-Data-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
basic-Service-List
This optional attribute is an instance of OM class Basic-Service-List. See Basic-Service-List.
ss-List
This optional attribute is an instance of OM class SS-List. See SS-List.
roaming-Restriction-Due-To-Unsupported-Feature
A Null value whose presence provides indication.
regional-Subscription-Identifier
ZoneCode ::= OCTET STRING (SIZE(2)) Internal structure is defined in 3GPP TS 23.003.
vbs-Group-Indication
A Null value whose presence provides indication.
vgcs-Group-Indication
A Null value whose presence provides indication.
camel-Subscription-Info-Withdraw
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
gprs-Subscription-Data-Withdraw
This optional attribute is an instance of OM class GPRS-Subscription-Data-Withdraw. See GPRS-Subscription-Data-Withdraw.
roaming-Restricted-In-Sgsn-Due-To-Unsupported-Feature
A Null value whose presence provides indication.
lsa-Information-Withdraw
This optional attribute is an instance of OM class LSA-Information-Withdraw. See LSA-Information-Withdraw.
gmlc-List-Withdraw
A Null value whose presence provides indication.
ist-Information-Withdraw
A Null value whose presence provides indication.
specific-CSI-Withdraw
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
ss-csi
(‘MAP_T_SS_CSI’ ‘1’)
tif-csi
(‘MAP_T_TIF_CSI’ ‘2’)
d-csi
(‘MAP_T_D_CSI’ ‘3’)
vt-csi
(‘MAP_T_VT_CSI’ ‘4’)
mo-sms-csi
(‘MAP_T_MO_SMS_CSI’ ‘5’)
m-csi
(‘MAP_T_M_CSI’ ‘6’)
gprs-csi
(‘MAP_T_GPRS_CSI’ ‘7’)
t-csi
(‘MAP_T_T_CSI’ ‘8’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘9’)
mg-csi
(‘MAP_T_MG_CSI’ ‘10’)
o-im-csi
(‘MAP_T_O_IM_CSI’ ‘11’)
d-im-csi
(‘MAP_T_D_IM_CSI’ ‘12’)
vt-im-csi
(‘MAP_T_VT_IM_CSI’ ‘13’)

charging-Characteristics-Withdraw
A Null value whose presence provides indication.
stn-sr-Withdraw
A Null value whose presence provides indication.
eps-Subscription-Data-Withdraw
This optional attribute is an instance of OM class EPS-Subscription-Data-Withdraw. See EPS-Subscription-Data-Withdraw.
apn-oi-replacement-Withdraw
A Null value whose presence provides indication.
csg-Subscription-Deleted
A Null value whose presence provides indication.

5.4.1.42 Delete-Subscriber-Data-Res

An instance of OM class Delete-Subscriber-Data-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 231.

xmap_tab231.png

Table 231. OM Attributes of OM Class Delete-Subscriber-Data-Res

This OM class contains the following class-specific OM attributes:

regional-Subscription-Response
An enumeration containing one of the following values:
network-node-area-restricted
(‘MAP_T_NETWORK_NODE_AREA_RESTRICTED’ ‘0’)
too-many-zone-codes
(‘MAP_T_TOO_MANY_ZONE_CODES’ ‘1’)
zone-codes-conflict
(‘MAP_T_ZONE_CODES_CONFLICT’ ‘2’)
regional-subsc-not-supported
(‘MAP_T_REGIONAL_SUBSC_NOT_SUPPORTED’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.43 Destination-Number-Criteria

An instance of OM class Destination-Number-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 248.

xmap_tab248.png

Table 248. OM Attributes of OM Class Destination-Number-Criteria

This OM class contains the following class-specific OM attributes:

match-Type
an enumeration containing one of the following values:
inhibiting
(‘MAP_T_INHIBITING’ ‘0’)
enabling
(‘MAP_T_ENABLING’ ‘1’)

destination-Number-List
This optional attribute is an instance of OM class Destination-Number-List. See Destination-Number-List.
destination-Number-Length-List
This optional attribute is an instance of OM class Destination-Number-Length-List. See Destination-Number-Length-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.44 Destination-Number-Length-List

An instance of OM class Destination-Number-Length-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 250.

xmap_tab250.png

Table 250. OM Attributes of OM Class Destination-Number-Length-List

This OM class contains the following class-specific OM attributes:

destination-Number-Length
One to three (maxNumOfCamelDestinationNumberLengths) instances of number lengths.

5.4.1.45 Destination-Number-List

An instance of OM class Destination-Number-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 249.

xmap_tab249.png

Table 249. OM Attributes of OM Class Destination-Number-List

This OM class contains the following class-specific OM attributes:

destination-Number
One to ten (maxNumOfCamelDestinationNumbers) instances of an ISDN address string.

5.4.1.46 DP-Analysed-Info-Criteria-List

An instance of OM class DP-Analysed-Info-Criteria-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 237.

xmap_tab237.png

Table 237. OM Attributes of OM Class DP-Analysed-Info-Criteria-List

This OM class contains the following class-specific OM attributes:

dp-Analysed-Info-Criterium
One to ten (maxMumOfDP-AnalysedInfoCriteria) instances of OM class DP-Analysed-Info-Criterium. See DP-Analysed-Info-Criterium.

5.4.1.47 DP-Analysed-Info-Criterium

An instance of OM class DP-Analysed-Info-Criterium represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 238.

xmap_tab238.png

Table 238. OM Attributes of OM Class DP-Analysed-Info-Criterium

This OM class contains the following class-specific OM attributes:

dialed-Number
An ISDN Address String.
service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
default-Call-Handling
An enumeration containing one of the following values:
continue-call
(‘MAP_T_CONTINUE_CALL’ ‘0’)
release-call
(‘MAP_T_RELEASE_CALL’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.48 EPS-Authentication-Set-List

An instance of OM class EPS-Authentication-Set-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 169.

xmap_tab169.png

Table 169. OM Attributes of OM Class EPS-Authentication-Set-List

This OM class contains the following class-specific OM attributes:

epc-AV
One to five instances of OM Class EPS-AV. See EPS-AV.

5.4.1.49 EPS-AV

An instance of OM class EPS-AV represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 170.

xmap_tab170.png

Table 170. OM Attributes of OM Class EPS-AV

This OM class contains the following class-specific OM attributes:

rand
RAND ::= OCTET STRING (SIZE(16))
xres
XRES ::= OCTET STRING (SIZE(4..16))
autn
AUTN ::= OCTET STRING (SIZE(16))
kasme
KASME ::= OCTET STRING (SIZE(16))
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.50 EPS-Data-List

An instance of OM class EPS-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 180.

xmap_tab180.png

Table 180. OM Attributes of OM Class EPS-Data-List

This OM class contains the following class-specific OM attributes:

apn-Configuration
One to fifty instancs of OM Class APN-Configuration. See APN-Configuration.

5.4.1.51 EPS-Info

An instance of OM class EPS-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 144. This OM class represents a choice and exactly one instance of one attribute shall exist in an instance of this OM class.

xmap_tab144.png

Table 144. OM Attributes of OM Class EPS-Info

This OM class contains the following class-specific OM attributes:

pdn-Gw-Update
This optional attribute is an instance of OM class PDN-GW-Update. See PDN-GW-Update.
isr-Information
A bit string containing zero or more of the following bits:
update-mme
(‘MAP_T_UPDATE_MME’ ‘0’)
cancel-sgsn
(‘MAP_T_CANCEL_SGSN’ ‘1’)

5.4.1.52 EPS-QoS-Subscribed

An instance of OM class EPS-QoS-Subscribed represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 182.

xmap_tab182.png

Table 182. OM Attributes of OM Class EPS-QoS-Subscribed

This OM class contains the following class-specific OM attributes:

qos-Class-Identifier
QoS-Class-Identifier ::= INTEGER(1..9) Values are defined in 3GPP TS 29.212.
arp
ARP ::= OCTET STRING Octets are coded according to 3GPP TS 29.272.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.53 EPS-Subscription-Data

An instance of OM class EPS-Subscription-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 178.

xmap_tab178.png

Table 178. OM Attributes of OM Class EPS-Subscription-Data

This OM class contains the following class-specific OM attributes:

apn-oi-Replacement
APN-OI-Replacement ::= OCTET STRING (SIZE(9..100)) Octets are coded as APN Operator Identifier according to 3GPP TS 23.003.
rfsp-Id
RFSP-ID ::= INTEGER(1..256)
ambr
This optional attribute is an instance of OM class AMBR. See AMBR.
apn-Configuration-Profile
An optional instance of OM Class APN-Configuration-Profile. See APN-Configuration-Profile.
stn-sr
An ISDN address string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.54 EPS-Subscription-Data-Withdraw

An instance of OM class EPS-Subscription-Data-Withdraw represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 226. This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

xmap_tab226.png

Table 226. OM Attributes of OM Class EPS-Subscription-Data-Withdraw

This OM class contains the following class-specific OM attributes:

all-EPS-Data
A Null value whose presence provides indication.
context-Id-List
This choice attribute is an instance of OM class Context-Id-List. See Context-Id-List.

5.4.1.55 Ext-Basic-Service-Group-List

An instance of OM class Ext-Basic-Service-Group-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 419.

xmap_tab419.png

Table 419. OM Attributes of OM Class Ext-Basic-Service-Group-List

This OM class contains the following class-specific OM attributes:

ext-Basic-Service-Code
One to thirty-two (maxNumOfExt-BasicServiceGroups) instances of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.

5.4.1.56 Ext-Call-Bar-Feature-List

An instance of OM class Ext-Call-Bar-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 207.

xmap_tab207.png

Table 207. OM Attributes of OM Class Ext-Call-Bar-Feature-List

This OM class contains the following class-specific OM attributes:

ext-Call-Barring-Feature
One to maxNumOfExt-BasicServiceGroups instances of OM Class Ext-Call-Barring-Feature. See Ext-Call-Barring-Feature.

5.4.1.57 Ext-Call-Bar-Info

An instance of OM class Ext-Call-Bar-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 206.

xmap_tab206.png

Table 206. OM Attributes of OM Class Ext-Call-Bar-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
call-Barring-Feature-List
This attribute is an instance of OM class Ext-Call-Bar-Feature-List. See Ext-Call-Bar-Feature-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.58 Ext-Call-Barring-Feature

An instance of OM class Ext-Call-Barring-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 208.

xmap_tab208.png

Table 208. OM Attributes of OM Class Ext-Call-Barring-Feature

This OM class contains the following class-specific OM attributes:

basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.59 Ext-Call-Barring-Info-For-CSE

An instance of OM class Ext-Call-Barring-Info-For-CSE represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 312.

xmap_tab312.png

Table 312. OM Attributes of OM Class Ext-Call-Barring-Info-For-CSE

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
call-Barring-Feature-List
This optional attribute is an instance of OM class Ext-Call-Bar-Feature-List. See Ext-Call-Bar-Feature-List.
password
Password ::= NumericString (FROM (0|1|2|3|4|5|6|7|8|9)) (SIZE(4))
wrong-Password-Attempts-Counter
WrongPasswordAttemptsCounter ::= INTEGER(0..4)
notification-To-CSE
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.60 External-Client-List

An instance of OM class External-Client-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 216.

xmap_tab216.png

Table 216. OM Attributes of OM Class External-Client-List

This OM class contains the following class-specific OM attributes:

external-Client
One to five instances of OM Class External-Client. See External-Client.

5.4.1.61 External-Client

An instance of OM class External-Client represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 409.

xmap_tab409.png

Table 409. OM Attributes of OM Class External-Client

This OM class contains the following class-specific OM attributes:

client-Identity
This attribute is an instance of OM class LCS-Client-External-ID. See LCS-Client-External-ID.
gmlc-Restriction
An enumeration containing one of the following values:
gmlc-list
(‘MAP_T_GMLC_LIST’ ‘0’)
home-country
(‘MAP_T_HOME_COUNTRY’ ‘1’)

notification-To-MS-User
An enumeration containing one of the following values:
notify-location-allowed
(‘MAP_T_NOTIFY_LOCATION_ALLOWED’ ‘0’)
notify-and-verify-location-allowed-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_NO_REPONSE’ ‘1’)
notify-and-verity-location-allowed-if-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_IF_NO_RESPONSE’ ‘2’)
location-not-allowed
(‘MAP_T_LOCATION_NOT_ALLOWED’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.62 Ext-External-Client-List

An instance of OM class Ext-External-Client-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 218.

xmap_tab218.png

Table 218. OM Attributes of OM Class Ext-External-Client-List

This OM class contains the following class-specific OM attributes:

ext-External-Client
One to thirty-five instances of OM class External-Client. See External-Client.

5.4.1.63 Ext-Forwarding-Info-For-CSE

An instance of OM class Ext-Forwarding-Info-For-CSE represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 311.

xmap_tab311.png

Table 311. OM Attributes of OM Class Ext-Forwarding-Info-For-CSE

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
forwarding-Feature-List
This optional attribute is an instance of OM class Ext-Forw-Feature-List. See Ext-Forw-Feature-List.
notification-To-CSE
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.64 Ext-Forw-Feature-List

An instance of OM class Ext-Forw-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 204.

xmap_tab204.png

Table 204. OM Attributes of OM Class Ext-Forw-Feature-List

This OM class contains the following class-specific OM attributes:

ext-Forw-Feature
One to maxNumOfExt-BasicServiceGroups instances of OM Class Ext-Forw-Feature. See Ext-Forw-Feature.

5.4.1.65 Ext-Forw-Feature

An instance of OM class Ext-Forw-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 205.

xmap_tab205.png

Table 205. OM Attributes of OM Class Ext-Forw-Feature

This OM class contains the following class-specific OM attributes:

basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
forwarded-To-Number
An ISDN Address String. See String(Address).
forwarded-To-Subaddress
An ISDN Subaddress String. See String(Subaddress).
forwarding-Options
Ext-ForwOptions ::= OCTET STRING (SIZE(1..5)) Octet 1, bit 8, notification to forwarding party: 0, no notification, 1 notification; bit 7, redirecting presentation: 0, no presentation, 1, presentation; bit 6, notification to calling party: 0, no notification, 1, notification; bit 5, 0 (unused); bits 43, forwarding reason: 00, ms not reachable, 01 ms busy, 10, no reply, 11 unconditional; bits 21, 00 (unused); octets 2-5, reserved for future use. They shall be discarded if received and not understood.
no-Reply-Condition-Time
Ext-NoRepCondTime ::= INTEGER(1..100) Only values 5-30 are used. Values in the range 1-4 and 31-100 are reserved for future use: if received, values 1-4 shall be mapped onto value 5; values 31-100 shall be mapped onto value 30.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-Forwarded-To-Number
FTN-AddressString ::= AddressString (SIZE(1..15)) This type is used to represent forwarded-to numbers. If NAI is “international”, the first digits represent the country code (CC) and the network destination code (NDC) as for E.164.

5.4.1.66 Ext-Forw-Info

An instance of OM class Ext-Forw-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 203.

xmap_tab203.png

Table 203. OM Attributes of OM Class Ext-Forw-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
forwarding-Feature-List
This attribute is an instance of OM class Ext-Forw-Feature-List. See Ext-Forw-Feature-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.67 Ext-SS-Data

An instance of OM class Ext-SS-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 213.

xmap_tab213.png

Table 213. OM Attributes of OM Class Ext-SS-Data

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
ss-Subscription-Option
This optional attribute is an instance of OM class SS-Subscription-Option. See SS-Subscription-Option.
basic-Service-Group-List
This optional attribute is an instance of OM class Ext-Basic-Service-Group-List. See Ext-Basic-Service-Group-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.68 Ext-SS-Info-For-CSE

An instance of OM class Ext-SS-Info-For-CSE represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 310. This OM class represents a choice and exactly one attribute is present in an instance of this OM class.

xmap_tab310.png

Table 310. OM Attributes of OM Class Ext-SS-Info-For-CSE

This OM class contains the following class-specific OM attributes:

forwarding-Info-For-CSE
This choice attribute is an instance of OM class Ext-Forwarding-Info-For-CSE. See Ext-Forwarding-Info-For-CSE.
call-Barring-Info-For-CSE
This choice attribute is an instance of OM class Ext-Call-Barring-Info-For-CSE. See Ext-Call-Barring-Info-For-CSE.

5.4.1.69 Ext-SS-Info-List

An instance of OM class Ext-SS-Info-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 201.

xmap_tab201.png

Table 201. OM Attributes of OM Class Ext-SS-Info-List

This OM class contains the following class-specific OM attributes:

ext-SS-Info
One to thirty (maxNumOfSS) instances of OM Class Ext-SS-Info. See Ext-SS-Info.

5.4.1.70 Ext-SS-Info

An instance of OM class Ext-SS-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 202. This OM class represents a choice and exactly one attribute is present in an instance of this OM class.

xmap_tab202.png

Table 202. OM Attributes of OM Class Ext-SS-Info

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Ext-Forw-Info. See Ext-Forw-Info.
call-Barring-Info
This choice attribute is an instance of OM class Ext-Call-Bar-Info. See Ext-Call-Bar-Info.
cug-Info
This choice attribute is an instance of OM class CUG-Info. See CUG-Info.
ss-Data
This choice attribute is an instance of OM class Ext-SS-Data. See Ext-SS-Data.
emlpp-Info
This choice attribute is an instance of OM class EMLPP-Info. See EMLPP-Info.

5.4.1.71 Failure-Report-Arg

An instance of OM class Failure-Report-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 265.

xmap_tab265.png

Table 265. OM Attributes of OM Class Failure-Report-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
ggsn-Number
An ISDN Address String.
ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.72 Failure-Report-Res

An instance of OM class Failure-Report-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 266.

xmap_tab266.png

Table 266. OM Attributes of OM Class Failure-Resport-Res

This OM class contains the following class-specific OM attributes:

ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.73 Forward-Access-Signalling-Arg

An instance of OM class Forward-Access-Signalling-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 147.

xmap_tab147.png

Table 147. OM Attributes of OM Class Forward-Access-Signalling-Arg

This OM class contains the following class-specific OM attributes:

an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
integrity-Protection-Info
IntegrityProtectionInformation ::= OCTET STRING (SIZE(18..100)) Octets contain a complete IntegrityProtectionInformation data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
encryption-Info
EncryptionInformation ::= OCTET STRING (SIZE(18..100)) Octets contain a complete EncryptionInformation data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
key-Status
old
(‘MAP_T_OLD’ ‘0’)
new
(‘MAP_T_NEW’ ‘1’)

allowed-GSM-Algorithms
AllowedGSM-Algorithms ::= OCTET STRING (SIZE(1)) Internal structure is coded as Algorithm identifier octet from Permitted Algorithms defined in 3GPP TS 48.008. A node shall mark all GSM algorithms that are allowed in MSC-B.
allowed-UMTS-Algorithms
This optional attribute is an instance of OM class Allowed-UMTS-Algorithms. See Allowed-UMTS-Algorithms.
radio-Resource-Information
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
radio-Resource-List
This optional attribute is an instance of OM class Radio-Resource-List. See Radio-Resource-List.
bssmap-Service-Handover
BSSMAP-ServiceHandover ::= OCTET STRING (SIZE(1)) Octets are coded according to the Service Handover information element in 3GPP TS 48.008.
ranap-Service-Handover
RANAP-ServiceHandover ::= OCTET STRING (SIZE(1)) Octet contains a complete Service-Handover data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included in the least significant bits.
bssmap-Service-Handover-List
This optional attribute is an instance of OM class BSSMAP-Service-Handover-List. See BSSMAP-Service-Handover-List.
currently-Used-Codec
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
iu-Supported-Codecs-List
This optional attribute is an instance of OM class Supported-Codecs-List. See Supported-Codecs-List.
rab-Configuration-Indicator
A Null value whose presence provides indication.
iu-Selected-Codec
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
alternative-Channel-Type
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
trace-Propagation-List
This optional attribute is an instance of OM class Trace-Propagation-List. See Trace-Propagation-List.

5.4.1.74 Forward-Check-SS-Indication-Arg

An instance of OM class Forward-Check-SS-Indication-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument; it does not define any class-specific OM attributes.

5.4.1.75 GMLC-List

An instance of OM class GMLC-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 186.

xmap_tab186.png

Table 186. OM Attributes of OM Class GMLC-List

This OM class contains the following class-specific OM attributes:

gmlc
One to five instances of an ISDN Address String.

5.4.1.76 GPRS-Camel-TDP-Data-List

An instance of OM class GPRS-Camel-TDP-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 192.

xmap_tab192.png

Table 192. OM Attributes of OM Class GPRS-Camel-TDP-Data-List

This OM class contains the following class-specific OM attributes:

gprs-Camel-TDP-Data
One to ten instances of OM Class GPRS-Camel-TDP-Data. See GPRS-Camel-TDP-Data.

5.4.1.77 GPRS-Camel-TDP-Data

An instance of OM class GPRS-Camel-TDP-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 193.

xmap_tab193.png

Table 193. OM Attributes of OM Class GPRS-Camel-TDP-Data

This OM class contains the following class-specific OM attributes:

gprs-Trigger-Detection-Point
An enumeration containing one of the following values:
attach
(‘MAP_T_ATTACH’ ‘1’)
attach-change-of-position
(‘MAP_T_ATTACH_CHANGE_OF_POSITION’ ‘2’)
pdp-context-establishment
(‘MAP_T_PDP_CONTEXT_ESTABLISHMENT’ ‘11’)
pdp-context-establishment-acknowledgement
(‘MAP_T_PDP_CONTEXT_ESTABLISHMENT_ACKNOWLEDGEMENT’ ‘12’)
pdp-context-change-of-position
(‘MAP_T_PDP_CONTEXT_CHANGE_OF_POSITION’ ‘14’)

service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
default-Session-Handling
An enumeration containing one of the following values:
continue-transaction
(‘MAP_T_CONTINUE_TRANSACTION’ ‘0’)
release-transaction
(‘MAP_T_RELEASE_TRANSACTION’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.78 GPRS-CSI

An instance of OM class GPRS-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 191.

xmap_tab191.png

Table 191. OM Attributes of OM Class GPRS-CSI

This OM class contains the following class-specific OM attributes:

gprs-Camel-TDP-Data-List
This optional attribute is an instance of OM class GPRS-Camel-TDP-Data-List. See GPRS-Camel-TDP-Data-List.
camel-Capability-Handling
CamelCapabilityHandling ::= INTEGER(1..16) Value 1, CAMEL phase 1; value 2, CAMEL phase 2; value 3, CAMEL phase 3; value 4, CAMEL phase 4. Receiption of values greater than 4 shall be treated as CAMEL phase 4.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.79 GPRS-Data-List

An instance of OM class GPRS-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 187.

xmap_tab187.png

Table 187. OM Attributes of OM Class GPRS-Data-List

This OM class contains the following class-specific OM attributes:

pdp-Context
One to fifty instances of OM Class PDP-Context. See PDP-Context.

5.4.1.80 GPRS-MS-Class

An instance of OM class GPRS-MS-Class represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 280.

xmap_tab280.png

Table 280. OM Attributes of OM Class GPRS-MS-Class

This OM class contains the following class-specific OM attributes:

ms-Network-Capability
MSNetworkCapability ::= OCTET STRING (SIZE(1..8)) This parameter carries the value part of the MS Network Capability IE defined in 3GPP TS 24.008.
ms-Radio-Access-Capability
MSRadioAccessCapability ::= OCTET STRING (SIZE(1..50)) This parameter carries the value part of the MS Radio Access Capability IE defined in 3GPP TS 24.008.

5.4.1.81 GPRS-Subscription-Data

An instance of OM class GPRS-Subscription-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 189.

xmap_tab189.png

Table 189. OM Attributes of OM Class GPRS-Subscription-Data

This OM class contains the following class-specific OM attributes:

complete-Data-List-Included
A Null value whose presence provides indication.
gprs-Data-List
This attribute is an instance of OM class GPRS-Data-List. See GPRS-Data-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.82 GPRS-Subscription-Data-Withdraw

An instance of OM class GPRS-Subscription-Data-Withdraw represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 225. This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

xmap_tab225.png

Table 225. OM Attributes of OM Class GPRS-Subscription-Data-Withdraw

This OM class contains the following class-specific OM attributes:

all-GPRS-Data
A Null value whose presence provides indication.
context-Id-List
This choice attribute is an instance of OM class Context-Id-List. See Context-Id-List.

5.4.1.83 GSM-Security-Context-Data

An instance of OM class GSM-Security-Context-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 138.

xmap_tab138.png

Table 138. OM Attributes of OM Class GSM-Security-Context-Data

This OM class contains the following class-specific OM attributes:

kc
KC ::= OCTET STRING (SIZE(8))
cksn
Cksn ::= OCTET STRING (SIZE(1)) The internal structure is defined in 3GPP TS 24.008.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.84 Insert-Subscriber-Data-Arg

An instance of OM class Insert-Subscriber-Data-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 174.

xmap_tab174.png

Table 174. OM Attributes of OM Class Insert-Subscriber-Data-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
subscriber-Data
Components of subscriber data as follows:
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
category
Category ::= OCTET STRING (SIZE(1)) The internal structure is defined in ITU-T Rec. Q.763.
subscriber-Status
An enumeration containing one of the following values:
service-granted
(‘MAP_T_SERVICE_GRANTED’ ‘0’)
operator-determined-barring
(‘MAP_T_OPERATOR_DETERMINED_BARRING’ ‘1’)

bearer-Service-List
This optional attribute is an instance of OM class Bearer-Service-List. See Bearer-Service-List.
teleservice-List
This optional attribute is an instance of OM class Teleservice-List. See Teleservice-List.
provisioned-SS
This optional attribute is an instance of OM class Ext-SS-Info-List. See Ext-SS-Info-List.
odb-Data
This optional attribute is an instance of OM class ODB-Data. See ODB-Data.
roaming-Restriction-Due-To-Unsupported-Feature
A Null value whose presence provides indication.
regional-Subscription-Data
This optional attribute is an instance of OM class Zone-Code-List. See Zone-Code-List.
vbs-Subscription-Data
This optional attribute is an instance of OM class VBS-Data-List. See VBS-Data-List.
vgcs-Subscription-Data
This optional attribute is an instance of OM class VGCS-Data-List. See VGCS-Data-List.
vlr-Camel-Subscription-Info
This optional attribute is an instance of OM class Vlr-Camel-Subscription-Info. See Vlr-Camel-Subscription-Info.

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
naea-Preferred-CI
This optional attribute is an instance of OM class NAEA-Preferred-CI. See NAEA-Preferred-CI.
gprs-Subscription-Data
This optional attribute is an instance of OM class GPRS-Subscription-Data. See GPRS-Subscription-Data.
roaming-Restricted-In-Sgsn-Due-To-Unsupported-Feature
A Null value whose presence provides indication.
network-Access-Mode
An enumeration containing one of the following values:
packet-and-circuit
(‘MAP_T_PACKET_AND_CIRCUIT’ ‘0’)
only-circuit
(‘MAP_T_ONLY_CIRCUIT’ ‘1’)
only-packet
(‘MAP_T_ONLY_PACKET’ ‘2’)

lsa-Information
This optional attribute is an instance of OM class LSA-Information. See LSA-Information.
lmu-Indicator
A Null value whose presence provides indication.
lcs-Information
This optional attribute is an instance of OM class LCS-Information. See LCS-Information.
ist-Alert-Timer
IST-AlertTimerValue ::= INTEGER(15..255)
super-Charger-Supported-In-HLR
AgeIndicator ::= OCTET STRING (SIZE(1..6)) The internal structure of this parameter is implementation specific.
mc-SS-Info
This optional attribute is an instance of OM class MC-SS-Info. See MC-SS-Info.
cs-Allocation-Retention-Priority
CS-AllocationRetentionPriority ::= OCTET STRING (SIZE(1)) This data type encodes each priority level defined in TS 23.107 as the binary value of the priority level.
sgsn-Camel-Subscription-Info
This optional attribute is an instance of OM class SGSN-CAMEL-Subscription-Info. See SGSN-CAMEL-Subscription-Info.
charging-Characteristics
ChargingCharacteristics ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 32.215.
access-Restriction-Data
A bit string containing zero or more of the following bits:
utran-not-allowed
(‘MAP_T_UTRAN_NOT_ALLOWED’ ‘0’)
geran-not-allowed
(‘MAP_T_GERAN_NOT_ALLOWED’ ‘1’)
gan-not-allowed
(‘MAP_T_GAN_NOT_ALLOWED’ ‘2’)
i-hspa-evolution-not-allowed
(‘MAP_T_I_HSPA_EVOLUTION_NOT_ALLOWED’ ‘3’)
e-utran-not-allowed
(‘MAP_T_E_UTRAN_NOT_ALLOWED’ ‘4’)
ho-to-non-3gpp-access-not-allowed
(‘MAP_T_HO_TO_NON_3GPP_ACCESS_NOT_ALLOWED’ ‘5’)

ics-Indicator
A boolean value indicator.
eps-Subscription-Data
This optional attribute is an instance of OM class EPS-Subscription-Data. See EPS-Subscription-Data.
csg-Subscription-Data-List
This optional attribute is an instance of OM class CSG-Subscription-Data-List. See CSG-Subscription-Data-List.

5.4.1.85 Insert-Subscriber-Data-Res

An instance of OM class Insert-Subscriber-Data-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 175.

xmap_tab175.png

Table 175. OM Attributes of OM Class Insert-Subscriber-Data-Res

This OM class contains the following class-specific OM attributes:

teleservice-List
This optional attribute is an instance of OM class Teleservice-List. See Teleservice-List.
bearer-Service-List
This optional attribute is an instance of OM class Bearer-Service-List. See Bearer-Service-List.
ss-List
This optional attribute is an instance of OM class SS-List. See SS-List.
odb-General-Data
A bit string containing zero or more of the following bits:
all-og-calls-barred
(‘MAP_T_ALL_OG_CALLS_BARRED’ ‘0’)
international-og-calls-barred
(‘MAP_T_INTERNATIONAL_OG_CALLS_BARRED’ ‘1’)
international-og-calls-not-to-hplmn-country-barred
(‘MAP_T_INTERNATIONAL_OG_CALLS_NOT_TO_HPLMN_COUNTRY_BARRED’ ‘2’)
interzonal-og-calls-barred
(‘MAP_T_INTERZONAL_OG_CALLS_BARRED’ ‘6’)
interzonal-og-calls-no-to-hplmn-country-barred
(‘MAP_T_INTERZONAL_OG_CALLS_NO_TO_HPLMN_COUNTRY_BARRED’ ‘7’)
interzonal-og-calls-and-international-og-calls-not-to-hplmn-country-barred
(‘MAP_T_INTERZONAL_OG_CALLS_AND_INTERNATIONAL_OG_CALLS_NOT_TO_HPLMN_COUNTRY_BARRED’ ‘8’)
premium-rate-information-og-calls-barred
(‘MAP_T_PREMIUM_RATE_INFORMATION_OG_CALLS_BARRED’ ‘3’)
premium-rate-entertainment-og-calls-barred
(‘MAP_T_PREMIUM_RATE_ENTERTAINMENT_OG_CALLS_BARRED’ ‘4’)
ss-access-barred
(‘MAP_T_SS_ACCESS_BARRED’ ‘5’)
all-ect-barred
(‘MAP_T_ALL_ECT_BARRED’ ‘9’)
chargeable-ect-barred
(‘MAP_T_CHARGEABLE_ECT_BARRED’ ‘10’)
international-ect-barred
(‘MAP_T_INTERNATIONAL_ECT_BARRED’ ‘11’)
interzonal-ect-barred
(‘MAP_T_INTERZONAL_ECT_BARRED’ ‘12’)
doubly-chargeable-ect-barred
(‘MAP_T_DOUBLY_CHARGEABLE_ECT_BARRED’ ‘13’)
multiple-ect-barred
(‘MAP_T_MULTIPLE_ECT_BARRED’ ‘14’)
all-packet-oriented-service-barred
(‘MAP_T_ALL_PACKET_ORIENTED_SERVICE_BARRED’ ‘15’)
roamer-access-to-hplmn-ap-barred
(‘MAP_T_ROAMER_ACCESS_TO_HPLMN_AP_BARRED’ ‘16’)
roamer-access-to-vplmn-ap-barred
(‘MAP_T_ROAMER_ACCESS_TO_VPLMN_AP_BARRED’ ‘17’)
roaming-outside-plmn-og-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_OG_CALLS_BARRED’ ‘18’)
all-ic-calls-barred
(‘MAP_T_ALL_IC_CALLS_BARRED’ ‘19’)
roaming-outside-plmn-ic-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_IC_CALLS_BARRED’ ‘20’)
roaming-outside-plmn-i-country-ic-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_I_COUNTRY_IC_CALLS_BARRED’ ‘21’)
roaming-outside-plmn-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_BARRED’ ‘22’)
roaming-outside-plmn-country-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_COUNTRY_BARRED’ ‘23’)
registration-all-cf-barred
(‘MAP_T_REGISTRATION_ALL_CF_BARRED’ ‘24’)
registration-cf-not-to-hplmn-barred
(‘MAP_T_REGISTRATION_CF_NOT_TO_HPLMN_BARRED’ ‘25’)
registration-interzonal-cf-barred
(‘MAP_T_REGISTRATION_INTERZONAL_CF_BARRED’ ‘26’)
registration-interzonal-cf-not-to-hplmn-barred
(‘MAP_T_REGISTRATION_INTERZONAL_CF_NOT_TO_HPLMN_BARRED’ ‘27’)
registration-interational-cf-barred
(‘MAP_T_REGISTRATION_INTERATIONAL_CF_BARRED’ ‘28’)

regional-Subscription-Response
An enumeration containing one of the following values:
network-node-area-restricted
(‘MAP_T_NETWORK_NODE_AREA_RESTRICTED’ ‘0’)
too-many-zone-codes
(‘MAP_T_TOO_MANY_ZONE_CODES’ ‘1’)
zone-codes-conflict
(‘MAP_T_ZONE_CODES_CONFLICT’ ‘2’)
regional-subsc-not-supported
(‘MAP_T_REGIONAL_SUBSC_NOT_SUPPORTED’ ‘3’)

supported-Camel-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
offered-Camel4-CSIs
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

supported-Features
A bit string containing zero or more of the following bits:
odb-all
(‘MAP_T_ODB_ALL’ ‘0’)
odb-HPLMN-APN
(‘MAP_T_ODB_HPLMN_APN’ ‘1’)
odb-VPLMN-APN
(‘MAP_T_ODB_VPLMN_APN’ ‘2’)
reg-Sub
(‘MAP_T_REG_SUB’ ‘3’)

5.4.1.86 LCS-Information

An instance of OM class LCS-Information represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 185.

xmap_tab185.png

Table 185. OM Attributes of OM Class LCS-Information

This OM class contains the following class-specific OM attributes:

gmlc-List
This optional attribute is an instance of OM class GMLC-List. See GMLC-List.
lcs-Privacy-Exception-List
This optional attribute is an instance of OM class LCS-Privacy-Exception-List. See LCS-Privacy-Exception-List.
molr-List
This optional attribute is an instance of OM class MOLR-List. See MOLR-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.
add-Lcs-Privacy-Exception-List
This optional attribute is an instance of OM class LCS-Privacy-Exception-List. See LCS-Privacy-Exception-List.

5.4.1.87 LCS-Privacy-Class

An instance of OM class LCS-Privacy-Class represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 215.

xmap_tab215.png

Table 215. OM Attributes of OM Class LCS-Privacy-Class

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
notification-To-MS-User
An enumeration containing one of the following values:
notify-location-allowed
(‘MAP_T_NOTIFY_LOCATION_ALLOWED’ ‘0’)
notify-and-verify-location-allowed-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_NO_REPONSE’ ‘1’)
notify-and-verity-location-allowed-if-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_IF_NO_RESPONSE’ ‘2’)
location-not-allowed
(‘MAP_T_LOCATION_NOT_ALLOWED’ ‘3’)

external-Client-List
This optional attribute is an instance of OM class External-Client-List. See External-Client-List.
plmn-Client-List
This optional attribute is an instance of OM class PLMN-Client-List. See PLMN-Client-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
ext-external-Client-List
This optional attribute is an instance of OM class Ext-External-Client-List. See Ext-External-Client-List.
service-Type-List
This optional attribute is an instance of OM class Service-Type-List. See Service-Type-List.

5.4.1.88 LCS-Privacy-Exception-List

An instance of OM class LCS-Privacy-Exception-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 214.

xmap_tab214.png

Table 214. OM Attributes of OM Class LCS-Privacy-Exception-List

This OM class contains the following class-specific OM attributes:

lcs-Privacy-Class
One to four instances of OM Class LCS-Privacy-Class. See LCS-Privacy-Class.

5.4.1.89 Location-Area

An instance of OM class Location-Area represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 121.

xmap_tab121.png

Table 121. OM Attributes of OM Class Location-Area

This OM class contains the following class-specific OM attributes:

lai-Fixed-Length
LAIFixedLength = OCTET STRING(SIZE(5)) Refers to Location Area Identification defined in 3GPP TS 23.003. The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code 3rd digit; 8765 mobile netework code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, location area code (LAC) according to 3GPP TS 24.008.
lac
LAC ::= OCTET STRING(SIZE(2)) Refers to Location Area Code of the Location Area Identification defined in 3GPP TS 23.003. Location Area Code according to 3GPP TS 24.008.

5.4.1.90 Location-Information-GPRS

An instance of OM class Location-Information-GPRS represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 283.

xmap_tab283.png

Table 283. OM Attributes of OM Class Location-Information-GPRS

This OM class contains the following class-specific OM attributes:

cell-Global-Id-Or-Service-Area-Id-Or-LAI
This optional attribute is an instance of OM class Cell-Global-Id-Or-Service-Area-Id-Or-LAI. See Cell-Global-Id-Or-Service-Area-Id-Or-LAI.
routeing-Area-Identity
RAIdentity ::= OCTET STRING (SIZE(6)) Routing Area Identity is coded in accordance with 3GPP TS 29.060. It shall contain the value part defined in 3GPP TS 29.060 only. That is, the 3GPP TS 29.060 type identifier octet shall not be included.
geographical-Information
GeographicalInformation ::= OCTET STRING (SIZE(8)) Refers to geographical information defined in 3GPP TS 23.032. Only the description of an ellipsoid point with uncertainty circle as specified in 3GPP TS 23.032 is allowed to be used. The internal structure according to 3GPP TS 23.032 is as follows: 1 octet, type of shape (elipsoid point with uncertanty circle), 3 octets, degrees of latitude, 3 octets degrees of longitude, 1 octet, uncertainty code.
sgsn-Number
This attribute refers to the ISDN number of an SGSN. An ISDN Address String containing the ISDN address of the SGSN.
selected-LSA-Identity
LSA-Identity ::= OCTET STRING (SIZE(3)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
sai-Present
A Null value whose presence provides indication.
geodetic-Information
GeodeticInformation :;= OCTET STRING (SIZE(10)) Referes to calling geodetic location defined in ITU-T Recommendation Q.763 (1999). Only the description of an ellispoid point with uncertainty circle as specified in Q.763 (1999) is allowed to be used. The internal structure according to Q.763 (1999) is as follows: 1 octet, screening and presence indicators, 1 octet, type of shape (ellipsoid point with uncertainty circle), 3 octets, degrees of latitude, 3 octets, degrees of longitude, 1 octet, uncertainty code, 1 octet, confidence.
current-Location-Retrieved
A Null value whose presence provides indication.
age-Of-Location-Information
AgeOfLocationInformation ::= INTEGER (0..32767) The value represents the elapsed time in minutes since the last network contact of the mobile station (i.e. the actuality of the location information). A value of ‘0’ indicates that the MS is currently in contact with the network. A value of ‘32767’ indicates that the location information is at least ‘32767’ minutes old.

5.4.1.91 Location-Information

An instance of OM class Location-Information represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 282.

xmap_tab282.png

Table 282. OM Attributes of OM Class Location-Information

This OM class contains the following class-specific OM attributes:

age-Of-Location-Information
AgeOfLocationInformation ::= INTEGER (0..32767) The value represents the elapsed time in minutes since the last network contact of the mobile station (i.e. the actuality of the location information). A value of ‘0’ indicates that the MS is currently in contact with the network. A value of ‘32767’ indicates that the location information is at least ‘32767’ minutes old.
geographical-Information
GeographicalInformation ::= OCTET STRING (SIZE(8)) Refers to geographical information defined in 3GPP TS 23.032. Only the description of an ellipsoid point with uncertainty circle as specified in 3GPP TS 23.032 is allowed to be used. The internal structure according to 3GPP TS 23.032 is as follows: 1 octet, type of shape (elipsoid point with uncertanty circle), 3 octets, degrees of latitude, 3 octets degrees of longitude, 1 octet, uncertainty code.
vlr-Number
This attribute refers to the ISDN number of a VLR. An ISDN Address String containing the ISDN address of the VLR.
location-Number
LocationNumber ::= OCTET STRING (SIZE(2..10)) The internal structure is defined in ITU-T Rec. Q.763.
cell-Global-Id-Or-Service-Area-Id-Or-LAI
This optional attribute is an instance of OM class Cell-Global-Id-Or-Service-Area-Id-Or-LAI. See Cell-Global-Id-Or-Service-Area-Id-Or-LAI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
selected-LSA-Id
LSA-Identity ::= OCTET STRING (SIZE(3)) Octets are coded according to 3GPP TS 23.003.
msc-Number
This attribute refers to the ISDN number of an MSC. An ISDN Address String containing the number of the MSC.
geodetic-Information
GeodeticInformation :;= OCTET STRING (SIZE(10)) Referes to calling geodetic location defined in ITU-T Recommendation Q.763 (1999). Only the description of an ellispoid point with uncertainty circle as specified in Q.763 (1999) is allowed to be used. The internal structure according to Q.763 (1999) is as follows: 1 octet, screening and presence indicators, 1 octet, type of shape (ellipsoid point with uncertainty circle), 3 octets, degrees of latitude, 3 octets, degrees of longitude, 1 octet, uncertainty code, 1 octet, confidence.
current-Location-Retrieved
A Null value whose presence provides indication.
sai-Present
A Null value whose presence provides indication.

5.4.1.92 LSA-Data-List

An instance of OM class LSA-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 194.

xmap_tab194.png

Table 194. OM Attributes of OM Class LSA-Data-List

This OM class contains the following class-specific OM attributes:

lsa-Data
One to twenty instances of of OM class LSA-Data. See LSA-Data.

5.4.1.93 LSA-Data

An instance of OM class LSA-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 195.

xmap_tab195.png

Table 195. OM Attributes of OM Class LSA-Data

This OM class contains the following class-specific OM attributes:

lsa-Identity
LSA-Identity ::= OCTET STRING (SIZE(3)) Octets are coded according to 3GPP TS 23.003.
lsa-Attributes
LSA-Attributes ::= OCTET STRING (SIZE(1)) Octets are coded according to 3GPP TS 48.008.
lsa-Active-Mode-Indicator
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.94 LSA-Identity-List

An instance of OM class LSA-Identity-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 229.

xmap_tab229.png

Table 229. OM Attributes of OM Class LSA-Identity-List

This OM class contains the following class-specific OM attributes:

lsa-Identity
One to maxNumOfLSAs instances of an LSA-Identity. LSA-Identity ::= OCTET STRING (SIZE(3)) Octets are coded according to 3GPP TS 23.003.

5.4.1.95 LSA-Information

An instance of OM class LSA-Information represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 196.

xmap_tab196.png

Table 196. OM Attributes of OM Class LSA-Information

This OM class contains the following class-specific OM attributes:

complete-Data-List-Included
A Null value whose presence provides indication.
lsa-Only-Access-Indicator
An enumeration containing one of the following values:
access-outside-lsas-allowed
(‘MAP_T_ACCESS_OUTSIDE_LSAS_ALLOWED’ ‘0’)
access-outside-lsas-restricted
(‘MAP_T_ACCESS_OUTSIDE_LSAS_RESTRICTED’ ‘1’)

lsa-Data-List
This optional attribute is an instance of OM class LSA-Data-List. See LSA-Data-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.96 LSA-Information-Withdraw

An instance of OM class LSA-Information-Withdraw represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 228. This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

xmap_tab228.png

Table 228. OM Attributes of OM Class LSA-Information-Withdraw

This OM class contains the following class-specific OM attributes:

all-LSA-Data
A Null value whose presence provides indication.
lsa-Identity-List
This choice attribute is an instance of OM class LSA-Identity-List. See LSA-Identity-List.

5.4.1.97 M-CSI

An instance of OM class M-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 257.

xmap_tab257.png

Table 257. OM Attributes of OM Class M-CSI

This OM class contains the following class-specific OM attributes:

mobility-Triggers
This attribute is an instance of OM class Mobility-Triggers. See Mobility-Triggers.
service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.98 MG-CSI

An instance of OM class MG-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 258.

xmap_tab258.png

Table 258. OM Attributes of OM Class MG-CSI

This OM class contains the following class-specific OM attributes:

mobility-Triggers
This attribute is an instance of OM class Mobility-Triggers. See Mobility-Triggers.
service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.99 MNP-Info-Res

An instance of OM class MNP-Info-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 279.

xmap_tab279.png

Table 279. OM Attributes of OM Class MNP-Info-Res

This OM class contains the following class-specific OM attributes:

routeing-Number
RouteingNumber ::= TBCD-STRING(SIZE(1..5))
imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
number-Portability-Status
An enumeration containing one of the following values:
not-known-to-be-ported
(‘MAP_T_NOT_KNOWN_TO_BE_PORTED’ ‘0’)
own-number-ported-out
(‘MAP_T_OWN_NUMBER_PORTED_OUT’ ‘1’)
foreign-number-ported-to-foreign-network
(‘MAP_T_FOREIGN_NUMBER_PORTED_TO_FOREIGN_NETWORK’ ‘2’)
own-number-not-ported-out
(‘MAP_T_OWN_NUMBER_NOT_PORTED_OUT’ ‘4’)
foreign-number-ported-in
(‘MAP_T_FOREIGN_NUMBER_PORTED_IN’ ‘5’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.100 Mobility-Triggers

An instance of OM class Mobility-Triggers represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 259.

xmap_tab259.png

Table 259. OM Attributes of OM Class Mobility-Triggers

This OM class contains the following class-specific OM attributes:

mm-Code
One to ten (maxNumOfMobilityTriggers) instances of a MM-code. MM-Code ::= OCTET STRING (SIZE(1))

5.4.1.101 Modification-Request-For-CB-Info

An instance of OM class Modification-Request-For-CB-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 302.

xmap_tab302.png

Table 302. OM Attributes of OM Class Modification-Request-For-CB-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
password
Password ::= NumericString (FROM (0|1|2|3|4|5|6|7|8|9)) (SIZE(4))
wrong-Password-Attempts-Counter
WrongPasswordAttemptsCounter ::= INTEGER(0..4)
modify-Notification-To-CSE
An enumeration containing one of the following values:
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.102 Modification-Request-For-CF-Info

An instance of OM class Modification-Request-For-CF-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 301.

xmap_tab301.png

Table 301. OM Attributes of OM Class Modification-Request-For-CF-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
forwarded-To-Number
An address string.
forwarded-To-Subaddress
An ISDN subaddress string.
no-Reply-Condition-Time
Ext-NoRepCondTime ::= INTEGER(1..100) Only values 5-30 are used. Values in the range 1-4 and 31-100 are reserved for future use. If received, values 1-4 shall be mapped onto value 5 and values 31-100 shall be mapped onto value 30.
modify-Notification-To-CSE
An enumeration containing one of the following values:
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.103 Modification-Request-For-CSI

An instance of OM class Modification-Request-for-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 304.

xmap_tab304.png

Table 304. OM Attributes of OM Class Modification-Request-for-CSI

This OM class contains the following class-specific OM attributes:

requested-Camel-Subscription-Info
An enumeration containing one of the following values:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
t-csi
(‘MAP_T_T_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
tif-csi
(‘MAP_T_TIF_CSI’ ‘3’)
grps-csi
(‘MAP_T_GPRS_CSI’ ‘4’)
mo-sms-csi
(‘MAP_T_MO_SMS_CSI’ ‘5’)
ss-csi
(‘MAP_T_SS_CSI’ ‘6’)
m-csi
(‘MAP_T_M_CSI’ ‘7’)
d-csi
(‘MAP_T_D_CSI’ ‘8’)

modify-Notification-To-CSE
An enumeration containing one of the following values:
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

modify-CSI-State
An enumeration containing one of the following values:
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
additional-Requested-Camel-Subscription-Info
An enumeration containing one of the following values:
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘0’)
mg-csi
(‘MAP_T_MG_CSI’ ‘1’)
o-im-csi
(‘MAP_T_O_IM_CSI’ ‘2’)
d-im-csi
(‘MAP_T_D_IM_CSI’ ‘3’)
vt-im-csi
(‘MAP_T_VT_IM_CSI’ ‘4’)

5.4.1.104 Modification-Request-For-IP-SM-GW-Data

An instance of OM class Modification-Request-For-IP-SM-GW-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 305.

xmap_tab305.png

Table 305. OM Attributes of OM Class Modification-Request-For-IP-SM-GW-Data

This OM class contains the following class-specific OM attributes:

modify-Registration-Status
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.105 Modification-Request-For-ODB-Data

An instance of OM class Modification-Request-For-ODB-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 303.

xmap_tab303.png

Table 303. OM Attributes of OM Class Modification-Request-For-ODB-Data

This OM class contains the following class-specific OM attributes:

odb-Data
This optional attribute is an instance of OM class ODB-Data. See ODB-Data.
modify-Notification-To-CSE
An enumeration containing one of the following values:
deactivate
(‘MAP_T_DEACTIVATE’ ‘0’)
activate
(‘MAP_T_ACTIVATE’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.106 MOLR-Class

An instance of OM class MOLR-Class represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 222.

xmap_tab222.png

Table 222. OM Attributes of OM Class MOLR-Class

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
Ext-SS-Status ::= OCTET STRING(SIZE(1..5)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. Octet 1, bits 8765, unused (0000); bits 4321, used to convey the “P bit”, “R bit”, “A bit” and “Q bit”, representing supplementary service state information as defined in 3GPP TS 23.011: bit 4, “Q bit”; bit 3, “P bit”; bit 2, “R bit”; bit 1, “A bit”; octets 2-5, reserved for future use. They shall be discarded if received and not understood.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.107 MOLR-List

An instance of OM class MOLR-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 221.

xmap_tab221.png

Table 221. OM Attributes of OM Class MOLR-List

This OM class contains the following class-specific OM attributes:

molr-Class
One to three instances of OM class MOLR-Class. See MOLR-Class.

5.4.1.108 MSISDN-BS-List

An instance of OM class MSISDN-BS-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 293.

xmap_tab293.png

Table 293. OM Attributes of OM Class MSISDN-BS-List

This OM class contains the following class-specific OM attributes:

msisdn-BS
One to fifty (maxNumOfMSISDN) instances of OM class MSISDN-BS. See MSISDN-BS.

5.4.1.109 MSISDN-BS

An instance of OM class MSISDN-BS represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 294.

xmap_tab294.png

Table 294. OM Attributes of OM Class MSISDN-BS

This OM class contains the following class-specific OM attributes:

msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
basic-Service-List
This optional attribute is an instance of OM class Basic-Service-List. See Basic-Service-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.110 MT-SMS-CAMEL-TDP-Criteria-List

An instance of OM class MT-SMS-CAMEL-TDP-Criteria-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 233.

xmap_tab233.png

Table 233. OM Attributes of OM Class MT-SMS-CAMEL-TDP-Criteria-List

This OM class contains the following class-specific OM attributes:

mt-Sms-Camel-TDP-Criteria
One to ten (maxNumOfCamelTDPData) instances of OM class MT-SMS-CAMEL-TDP-Criteria. See MT-SMS-CAMEL-TDP-Criteria.

5.4.1.111 MT-SMS-CAMEL-TDP-Criteria

An instance of OM class MT-SMS-CAMEL-TDP-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 234.

xmap_tab234.png

Table 234. OM Attributes of OM Class MT-SMS-CAMEL-TDP-Criteria

This OM class contains the following class-specific OM attributes:

sms-Trigger-Detection-Point
An enumeration containing one of the following values:
sms-collected-info
(‘MAP_T_SMS_COLLECTED_INFO’ ‘1’)
sms-delivery-request
(‘MAP_T_SMS_DELIVERY_REQUEST’ ‘2’)

tpdu-Type-Criterion
This optional attribute is an instance of OM class TPDU-Type-Criterion. See TPDU-Type-Criterion.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.112 Note-MM-Event-Arg

An instance of OM class Note-MM-Event-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 308.

xmap_tab308.png

Table 308. OM Attributes of OM Class Note-MM-Event-Arg

This OM class contains the following class-specific OM attributes:

service-Key
ServiceKey ::= INTEGER(0..2147483647)
event-Met
MM-Code ::= OCTET STRING (SIZE(1))
imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
location-Information
This optional attribute is an instance of OM class Location-Information. See Location-Information. A bit string containing zero or more of the following bits:
supported-Camel-Phases
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
location-Information-GPRS
This optional attribute is an instance of OM class Location-Information-GPRS. See Location-Information-GPRS.
offered-Camel4-Functionalities
A bit string containing zero or more of the following bits:
initiate-call-attempt
(‘MAP_T_INITIATE_CALL_ATTEMPT’ ‘0’)
split-leg
(‘MAP_T_SPLIT_LEG’ ‘1’)
move-leg
(‘MAP_T_MOVE_LEG’ ‘2’)
disconnect-leg
(‘MAP_T_DISCONNECT_LEG’ ‘3’)
entity-released
(‘MAP_T_ENTITY_RELEASED’ ‘4’)
dfc-with-argument
(‘MAP_T_DFS_WITH_ARGUMENT’ ‘5’)
play-tone
(‘MAP_T_PLAY_TONE’ ‘6’)
dtmf-midcall
(‘MAP_T_DTMF_MIDCALL’ ‘7’)
charging-indicator
(‘MAP_T_CHARGING_INDICATOR’ ‘8’)
altering-dp
(‘MAP_T_ALERTING_DP’ ‘9’)
location-at-alterting
(‘MAP_T_LOCATION_AT_ALERTING’ ‘10’)
change-of-position-dp
(‘MAP_T_CHANGE_OF_POSITION_DP’ ‘11’)
or-interactions
(‘MAP_T_OR_INTERACTIONS’ ‘12’)
warning-tone-enhancements
(‘MAP_T_WARNING_TONE_ENHANCEMENTS’ ‘13’)
cf-enhancements
(‘MAP_T_CF_ENHANCEMENTS’ ‘14’)
subscribed-enhanced-dialled-services
(‘MAP_T_SUBSCRIBED_ENHANCED_DIALLED_SERVICES’ ‘15’)
serving-network-enhanced-dialled-services
(‘MAP_T_SERVING_NETWORK_ENHANCED_DIALLED_SERVICES’ ‘16’)
criteria-for-change-of-position-dp
(‘MAP_T_CRITERIA_FOR_CHANGE_OF_POSITION_DP’ ‘17’)
service-change-dp
(‘MAP_T_SERVICE_CHANGE_DP’ ‘18’)
collect-information
(‘MAP_T_COLLECT_INFORMATION’ ‘19’)

5.4.1.113 Note-MM-Event-Res

An instance of OM class Note-MM-Event-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 309.

xmap_tab309.png

Table 309. OM Attributes of OM Class Note-MM-Event-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.114 Note-Ms-Present-For-Gprs-Arg

An instance of OM class Note-Ms-Present-For-Gprs-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 267.

xmap_tab267.png

Table 267. OM Attributes of OM Class Note-Ms-Present-For-Gprs-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
sgsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.115 Note-Ms-Present-For-Gprs-Res

An instance of OM class Note-Ms-Present-For-Gprs-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 268.

xmap_tab268.png

Table 268. OM Attributes of OM Class Note-Ms-Present-For-Gprs-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.116 Note-Subscriber-Data-Modified-Arg

An instance of OM class Note-Subscriber-Data-Modified-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 306.

xmap_tab306.png

Table 306. OM Attributes of OM Class Note-Subscriber-Data-Modified-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
forwarding-Info-For-CSE
This optional attribute is an instance of OM class Ext-Forwarding-Info-For-CSE. See Ext-Forwarding-Info-For-CSE.
call-Barring-Info-For-CSE
This optional attribute is an instance of OM class Ext-Call-Barring-Info-For-CSE. See Ext-Call-Barring-Info-For-CSE.
odb-Info
This optional attribute is an instance of OM class ODB-Info. See ODB-Info.
camel-Subscription-Info
This optional attribute is an instance of OM class CAMEL-Subscription-Info. See CAMEL-Subscription-Info.
all-Information-Sent
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.117 Note-Subscriber-Data-Modified-Res

An instance of OM class Note-Subscriber-Data-Modified-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 307.

xmap_tab307.png

Table 307. OM Attributes of OM Class Note-Subscriber-Data-Modified-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.118 O-Bcsm-Camel-TDP-Criteria-List

An instance of OM class O-Bcsm-Camel-TDP-Criteria-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 411.

xmap_tab411.png

Table 411. OM Attributes of OM Class O-Bcsm-Camel-TDP-Criteria-List

This OM class contains the following class-specific OM attributes:

o-Bcsm-Camel-TDP-Criteria
One to ten (maxNumOfCamelTDPData) instances of OM class O-Bcsm-Camel-TDP-Criteria. See O-Bcsm-Camel-TDP-Criteria.

5.4.1.119 O-Bcsm-Camel-TDP-Criteria

An instance of OM class O-Bcsm-Camel-TDP-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 246.

xmap_tab246.png

Table 246. OM Attributes of OM Class O-Bcsm-Camel-TDP-Criteria

This OM class contains the following class-specific OM attributes:

o-Bcsm-Trigger-Detection-Point
An enumeration containing one of the following values:
collected-info
(‘MAP_T_COLLECTED_INFO’ ‘2’)
route-select-failure
(‘MAP_T_ROUTE_SELECT_FAILURE’ ‘4’)

destination-Number-Criteria
This optional attribute is an instance of OM class Destination-Number-Criteria. See Destination-Number-Criteria.
basic-Service-Criteria
This optional attribute is an instance of OM class Basic-Service-Criteria. See Basic-Service-Criteria.
call-Type-Criteria
An enumeration containing one of the following values:
forwarded
(‘MAP_T_FORWARDED’ ‘0’)
not-forwarded
(‘MAP_T_NOT_FORWARDED’ ‘1’)

extension
This optional attribute is an instance of OM class Extension. See Extension.
o-Cause-Value-Criteria
This optional attribute is an instance of OM class O-Cause-Value-Criteria. See O-Cause-Value-Criteria.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.

5.4.1.120 O-Bcsm-Camel-TDP-Data-List

An instance of OM class O-Bcsm-Camel-TDP-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 243.

xmap_tab243.png

Table 243. OM Attributes of OM Class O-Bcsm-Camel-TDP-Data-List

This OM class contains the following class-specific OM attributes:

o-Bcsm-Camel-TDP-Data
One to ten (maxNumOfCamelTDPData) instances of OM class O-Bcsm-Camel-TDP-Data. See O-Bcsm-Camel-TDP-Data.

5.4.1.121 O-Bcsm-Camel-TDP-Data

An instance of OM class O-Bcsm-Camel-TDP-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 244.

xmap_tab244.png

Table 244. OM Attributes of OM Class O-Bcsm-Camel-TDP-Data

This OM class contains the following class-specific OM attributes:

o-Bcsm-Trigger-Detection-Point
An enumeration containing one of the following values:
collected-info
(‘MAP_T_COLLECTED_INFO’ ‘2’)
route-select-failure
(‘MAP_T_ROUTE_SELECT_FAILURE’ ‘4’)

service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
default-Call-Handling
An enumeration containing one of the following values:
continue-call
(‘MAP_T_CONTINUE_CALL’ ‘0’)
release-call
(‘MAP_T_RELEASE_CALL’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.122 O-Cause-Value-Criteria

An instance of OM class O-Cause-Value-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 252.

xmap_tab252.png

Table 252. OM Attributes of OM Class O-Cause-Value-Criteria

This OM class contains the following class-specific OM attributes:

cause-Value
One to five (maxNumOfCAMEL-O-CauseValueCriteria) instances of a cause value. CauseValue ::= OCTET STRING (SIZE(1)) Type extracted from Cause parameter in ITU-T Recommendation Q.763. For the use of cause value refer to ITU-T Recommendation Q.850.

5.4.1.123 O-CSI

An instance of OM class O-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 242.

xmap_tab242.png

Table 242. OM Attributes of OM Class O-CSI

This OM class contains the following class-specific OM attributes:

o-Bcsm-Camel-TDP-Data-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Data-List. See O-Bcsm-Camel-TDP-Data-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
camel-Capability-Handling
CamelCapabilityHandling ::= INTEGER(1..16) Value 1, CAMEL phase 1; value 2, CAMEL phase 2; value 3, CAMEL phase 3; value 4, CAMEL phase 4. Receiption of values greater than 4 shall be treated as CAMEL phase 4.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.

5.4.1.124 ODB-Data

An instance of OM class ODB-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 200.

xmap_tab200.png

Table 200. OM Attributes of OM Class ODB-Data

This OM class contains the following class-specific OM attributes:

odb-General-Data
A bit string containing zero or more of the following bits:
all-og-calls-barred
(‘MAP_T_ALL_OG_CALLS_BARRED’ ‘0’)
international-og-calls-barred
(‘MAP_T_INTERNATIONAL_OG_CALLS_BARRED’ ‘1’)
international-og-calls-not-to-hplmn-country-barred
(‘MAP_T_INTERNATIONAL_OG_CALLS_NOT_TO_HPLMN_COUNTRY_BARRED’ ‘2’)
interzonal-og-calls-barred
(‘MAP_T_INTERZONAL_OG_CALLS_BARRED’ ‘6’)
interzonal-og-calls-no-to-hplmn-country-barred
(‘MAP_T_INTERZONAL_OG_CALLS_NO_TO_HPLMN_COUNTRY_BARRED’ ‘7’)
interzonal-og-calls-and-international-og-calls-not-to-hplmn-country-barred
(‘MAP_T_INTERZONAL_OG_CALLS_AND_INTERNATIONAL_OG_CALLS_NOT_TO_HPLMN_COUNTRY_BARRED’ ‘8’)
premium-rate-information-og-calls-barred
(‘MAP_T_PREMIUM_RATE_INFORMATION_OG_CALLS_BARRED’ ‘3’)
premium-rate-entertainment-og-calls-barred
(‘MAP_T_PREMIUM_RATE_ENTERTAINMENT_OG_CALLS_BARRED’ ‘4’)
ss-access-barred
(‘MAP_T_SS_ACCESS_BARRED’ ‘5’)
all-ect-barred
(‘MAP_T_ALL_ECT_BARRED’ ‘9’)
chargeable-ect-barred
(‘MAP_T_CHARGEABLE_ECT_BARRED’ ‘10’)
international-ect-barred
(‘MAP_T_INTERNATIONAL_ECT_BARRED’ ‘11’)
interzonal-ect-barred
(‘MAP_T_INTERZONAL_ECT_BARRED’ ‘12’)
doubly-chargeable-ect-barred
(‘MAP_T_DOUBLY_CHARGEABLE_ECT_BARRED’ ‘13’)
multiple-ect-barred
(‘MAP_T_MULTIPLE_ECT_BARRED’ ‘14’)
all-packet-oriented-service-barred
(‘MAP_T_ALL_PACKET_ORIENTED_SERVICE_BARRED’ ‘15’)
roamer-access-to-hplmn-ap-barred
(‘MAP_T_ROAMER_ACCESS_TO_HPLMN_AP_BARRED’ ‘16’)
roamer-access-to-vplmn-ap-barred
(‘MAP_T_ROAMER_ACCESS_TO_VPLMN_AP_BARRED’ ‘17’)
roaming-outside-plmn-og-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_OG_CALLS_BARRED’ ‘18’)
all-ic-calls-barred
(‘MAP_T_ALL_IC_CALLS_BARRED’ ‘19’)
roaming-outside-plmn-ic-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_IC_CALLS_BARRED’ ‘20’)
roaming-outside-plmn-i-country-ic-calls-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_I_COUNTRY_IC_CALLS_BARRED’ ‘21’)
roaming-outside-plmn-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_BARRED’ ‘22’)
roaming-outside-plmn-country-barred
(‘MAP_T_ROAMING_OUTSIDE_PLMN_COUNTRY_BARRED’ ‘23’)
registration-all-cf-barred
(‘MAP_T_REGISTRATION_ALL_CF_BARRED’ ‘24’)
registration-cf-not-to-hplmn-barred
(‘MAP_T_REGISTRATION_CF_NOT_TO_HPLMN_BARRED’ ‘25’)
registration-interzonal-cf-barred
(‘MAP_T_REGISTRATION_INTERZONAL_CF_BARRED’ ‘26’)
registration-interzonal-cf-not-to-hplmn-barred
(‘MAP_T_REGISTRATION_INTERZONAL_CF_NOT_TO_HPLMN_BARRED’ ‘27’)
registration-interational-cf-barred
(‘MAP_T_REGISTRATION_INTERATIONAL_CF_BARRED’ ‘28’)

odb-HPLMN-Data
A bit string containing zero or more of the following bits:
plmn-specific-barring-type1
(‘MAP_T_PLMN_SPECIFIC_BARRING_TYPE1’ ‘0’)
plmn-specific-barring-type2
(‘MAP_T_PLMN_SPECIFIC_BARRING_TYPE2’ ‘1’)
plmn-specific-barring-type3
(‘MAP_T_PLMN_SPECIFIC_BARRING_TYPE3’ ‘2’)
plmn-specific-barring-type4
(‘MAP_T_PLMN_SPECIFIC_BARRING_TYPE4’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.125 ODB-Info

An instance of OM class ODB-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 297.

xmap_tab297.png

Table 297. OM Attributes of OM Class ODB-Info

This OM class contains the following class-specific OM attributes:

odb-Data
This attribute is an instance of OM class ODB-Data. See ODB-Data.
notification-To-CSE
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.126 Paging-Area

An instance of OM class Paging-Area represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 120.

xmap_tab120.png

Table 120. OM Attributes of OM Class Paging-Area

This OM class contains the following class-specific OM attributes:

location-Area
One to five instances of the OM Class Location-Area. See Location-Area.

5.4.1.127 PDN-GW-Identity

An instance of OM class PDN-GW-Identity represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 184.

xmap_tab184.png

Table 184. OM Attributes of OM Class PDN-GW-Identity

This OM class contains the following class-specific OM attributes:

pdn-Gw-IPv4-Address
PDP-Address ::= OCTET STRING (SIZE(1..16)) Octets are coded according to 3GPP TS 29.060. The possible values are: 1-7 octets X.25 address type, 4 octets IPv4 address type, 16 octets IPv6 address type.
pdn-Gw-IPv6-Address
PDP-Address ::= OCTET STRING (SIZE(1..16)) Octets are coded according to 3GPP TS 29.060. The possible values are: 1-7 octets X.25 address type, 4 octets IPv4 address type, 16 octets IPv6 address type.
pdn-Gw-Name
FQDN :;= OCTET STRING (SIZE(9..100))
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.128 PDN-GW-Update

An instance of OM class PDN-GW-Update represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 145.

xmap_tab145.png

Table 145. OM Attributes of OM Class PDN-GW-Update

This OM class contains the following class-specific OM attributes:

apn
APN ::= OCTET STRING (SIZE(2..63)) Octets are coded according to 3GPP TS 23.003.
pdn-Gw-Identity
This attribute is an instance of OM class PDN-GW-Identity. See PDN-GW-Identity.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.129 PDP-Context-Info-List

An instance of OM class PDP-Context-Info-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 286.

xmap_tab286.png

Table 286. OM Attributes of OM Class PDP-Context-Info-List

This OM class contains the following class-specific OM attributes:

pdp-Context-Info
One to fifty (maxNumOfPDP-Contexts) instances of OM class PDP-Context-Info. See PDP-Context-Info.

5.4.1.130 PDP-Context-Info

An instance of OM class PDP-Context-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 287.

xmap_tab287.png

Table 287. OM Attributes of OM Class PDP-Context-Info

This OM class contains the following class-specific OM attributes:

pdp-Context-Identifier
ContextID ::= INTEGER(1..50)
pdp-Context-Active
A Null value whose presence provides indication.
pdp-Type
PDP-Type ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 29.060.
apn-Subscribed
APN ::= OCTET STRING (SIZE(2..63)) Octets are coded according to 3GPP TS 23.003.
apn-In-Use
APN ::= OCTET STRING (SIZE(2..63)) Octets are coded according to 3GPP TS 23.003.
nsapi
NAPSI ::= INTEGER(0..15) This type is used to indicate the Network layer Service Access Point.
transaction-Id
TransactionId ::= OCTET STRING (SIZE(1..2)) This type carries the value part of the trasnaction identifier which is used in the session management messages on the access interface. The encoding is defined in 3GPP TS 24.008.
teid-For-Gn-And-Gp
TEID ::= OCTET STRING (SIZE(4)) This type carries the value part of the Tunnel Endpoint Identifier which is used to distinguish between different tunnels between the same pair of entities which communicate using GPRS Tunnelling Protocol. The encoding is defined in 3GPP TS 29.060.
teid-For-Iu
TEID ::= OCTET STRING (SIZE(4)) This type carries the value part of the Tunnel Endpoint Identifier which is used to distinguish between different tunnels between the same pair of entities which communicate using GPRS Tunnelling Protocol. The encoding is defined in 3GPP TS 29.060.
ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
qos-Subscribed
Ext-QoS-Subscribed ::= OCTET STRING (SIZE(1..9)) Octet 1, allocation/retention priority (this octet encodes each priority level defined in 23.107 as the binary value of the priority level, declaration in 29.060); octets 2-9 are coded according to 3GPP TS 24.008 Quality of Service Octets 6-13.
qos-Requested
Ext-QoS-Subscribed ::= OCTET STRING (SIZE(1..9)) Octet 1, allocation/retention priority (this octet encodes each priority level defined in 23.107 as the binary value of the priority level, declaration in 29.060); octets 2-9 are coded according to 3GPP TS 24.008 Quality of Service Octets 6-13.
qos-Negotiated
Ext-QoS-Subscribed ::= OCTET STRING (SIZE(1..9)) Octet 1, allocation/retention priority (this octet encodes each priority level defined in 23.107 as the binary value of the priority level, declaration in 29.060); octets 2-9 are coded according to 3GPP TS 24.008 Quality of Service Octets 6-13.
charging-Id
GPRSChargingID ::= OCTET STRING (SIZE(4)) The Charging ID is a unique four octet value generated by the GGSN when a PDP context is activated. A Charging ID is generated for each activated context. The encoding s defined in 3GPP TS 29.060.
charging-Characteristics
ChargingCharacteristics ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 32.215.
rnc-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
qos2-Subscribed
Ext2-QoS-Subscribed ::= OCTET STRING (SIZE(1..3)) Octets 1-3 are coded according to 3GPP TS 24.008 Quality of Service octets 14-16. If Quality of Service information is structured with 14 octet length, then Octet 1 is coded accoring to 3GPP TS 24.008 Quality of Service Octet 14.
qos2-Requested
Ext2-QoS-Subscribed ::= OCTET STRING (SIZE(1..3)) Octets 1-3 are coded according to 3GPP TS 24.008 Quality of Service octets 14-16. If Quality of Service information is structured with 14 octet length, then Octet 1 is coded accoring to 3GPP TS 24.008 Quality of Service Octet 14.
qos2-Negotiated
Ext2-QoS-Subscribed ::= OCTET STRING (SIZE(1..3)) Octets 1-3 are coded according to 3GPP TS 24.008 Quality of Service octets 14-16. If Quality of Service information is structured with 14 octet length, then Octet 1 is coded accoring to 3GPP TS 24.008 Quality of Service Octet 14.
qos3-Subscribed
Ext3-QoS-Subscribed ::= OCTET STRING (SIZE(1..2)) Octets 1-2 are coded according to 3GPP TS 24.008 Quality of Service Octets 17-18.
qos3-Requested
Ext3-QoS-Subscribed ::= OCTET STRING (SIZE(1..2)) Octets 1-2 are coded according to 3GPP TS 24.008 Quality of Service Octets 17-18.
qos3-Negotiated
Ext3-QoS-Subscribed ::= OCTET STRING (SIZE(1..2)) Octets 1-2 are coded according to 3GPP TS 24.008 Quality of Service Octets 17-18.

5.4.1.131 PDP-Context

An instance of OM class PDP-Context represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 188.

xmap_tab188.png

Table 188. OM Attributes of OM Class PDP-Context

This OM class contains the following class-specific OM attributes:

pdp-Context-Id
ContextID ::= INTEGER(1..50)
pdp-Type
PDP-Type ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 29.060.
pdp-Address
PDP-Address ::= OCTET STRING (SIZE(1..16)) Octets are coded according to 3GPP TS 29.060. The possible values are: 1-7 octets X.25 address type, 4 octets IPv4 address type, 16 octets IPv6 address type.
qos-Subscribed
QoS-Subscribed ::= OCTET STRING (SIZE(3)) Octets are coded according to 3GPP TS 24.008 Quality of Service Octets 3-5.
vplmn-Address-Allowed
A Null value whose presence provides indication.
apn
APN ::= OCTET STRING (SIZE(2..63)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
ext-QoS-Subscribed
Ext-QoS-Subscribed ::= OCTET STRING (SIZE(1..9)) Octet 1, allocation/retention priority (this octet encodes each priority level defined in 23.107 as the binary value of the priority level, declaration in 29.060); octets 2-9 are coded according to 3GPP TS 24.008 Quality of Service Octets 6-13.
pdp-Charging-Characteristics
ChargingCharacteristics ::= OCTET STRING (SIZE(2)) Octets are coded according to 3GPP TS 32.215.
ext2-QoS-Subscribed
Ext2-QoS-Subscribed ::= OCTET STRING (SIZE(1..3)) Octets 1-3 are coded according to 3GPP TS 24.008 Quality of Service octets 14-16. If Quality of Service information is structured with 14 octet length, then Octet 1 is coded accoring to 3GPP TS 24.008 Quality of Service Octet 14.
ext3-QoS-Subscribed
Ext3-QoS-Subscribed ::= OCTET STRING (SIZE(1..2)) Octets 1-2 are coded according to 3GPP TS 24.008 Quality of Service Octets 17-18.

5.4.1.132 PLMN-Client-List

An instance of OM class PLMN-Client-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 217.

xmap_tab217.png

Table 217. OM Attributes of OM Class PLMN-Client-List

This OM class contains the following class-specific OM attributes:

lcs-Client-Internal-ID
One to five instances of Enum(LCS-Client-Internal-ID), where LCS-Client-Internal-ID is an enumeration containing one of the following values:
broadcast-service
(‘MAP_T_BROADCAST_SERVICE’ ‘0’)
o-and-m-hplmn
(‘MAP_T_O_AND_M_HPLMN’ ‘1’)
o-and-m-vplmn
(‘MAP_T_O_AND_M_VPLMN’ ‘2’)
anonymous-location
(‘MAP_T_ANONYMOUS_LOCATION’ ‘3’)
target-ms-subscribed-service
(‘MAP_T_TARGET_MS_SUBSCRIBED_SERVICE’ ‘4’)

5.4.1.133 Prepare-HO-Arg

An instance of OM class Prepare-HO-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 149.

xmap_tab149.png

Table 149. OM Attributes of OM Class Prepare-HO-Arg

This OM class contains the following class-specific OM attributes:

target-Cell-Id
GlobalCellId ::= OCTET STRING (SIZE(5..7)) Refers to Cell Global Identification defined in 3GPP TS 23.003. The internal structures is as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digi; octet 2, bits 4321, mobile country code 3rd digit; bits 8765, mobile network code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, Location Area Code according to 3GPP TS 24.008; octets 6 and 7, Call Identity (CI) according to 3GPP TS 24.008.
ho-Number-Not-Required
A Null value whose presence provides indication.
an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
multiple-Bearer-Requested
A Null value whose presence provides indication.
imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
integrity-Protection-Info
IntegrityProtectionInformation ::= OCTET STRING (SIZE(18..100)) Octets contain a complete IntegrityProtectionInformation data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
encryption-Info
EncryptionInformation ::= OCTET STRING (SIZE(18..100)) Octets contain a complete EncryptionInformation data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included, if needed, in the least significant bits of the last octet of the octet string.
radio-Resource-Information
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
allowed-GSM-Algorithms
AllowedGSM-Algorithms ::= OCTET STRING (SIZE(1)) Internal structure is coded as Algorithm identifier octet from Permitted Algorithms defined in 3GPP TS 48.008. A node shall mark all GSM algorithms that are allowed in MSC-B.
allowed-UMTS-Algorithms
This optional attribute is an instance of OM class Allowed-UMTS-Algorithms. See Allowed-UMTS-Algorithms.
radio-Resource-List
This optional attribute is an instance of OM class Radio-Resource-List. See Radio-Resource-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
rab-Id
RAB-Id ::= INTEGER(1..255)
bssmap-Service-Handover
BSSMAP-ServiceHandover ::= OCTET STRING (SIZE(1)) Octets are coded according to the Service Handover information element in 3GPP TS 48.008.
ranap-Service-Handover
RANAP-ServiceHandover ::= OCTET STRING (SIZE(1)) Octet contains a complete Service-Handover data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included in the least significant bits.
bssmap-Service-Handover-List
This optional attribute is an instance of OM class BSSMAP-Service-Handover-List. See BSSMAP-Service-Handover-List.
asci-Call-Reference
A TBCD string of 1 to 8 octets representing the destination of the Short Message. Digits of VGCS/VBS-area and Group-ID are concatenated in this order if there is a VGCS/VBS-area.
geran-Classmark
GERAN-Classmark ::= OCTET STRING (SIZE(2..87)) Octets are coded according to GERAN Classmark information element in 3GPP TS 48.008.
iu-Current-Used-Codec
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
iu-Supported-Codecs-List
This optional attribute is an instance of OM class Supported-Codecs-List. See Supported-Codecs-List.
rab-Configuration-Indicator
A Null value whose presence provides indication.
uesbi-Iu
This optional attribute is an instance of OM class UESBI-Iu. See UESBI-Iu.
imeisv
IMEI ::= TBCD-STRING(SIZE(8)) Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in 3GPP TS 23.003. If the SVN is not present, the last octet shall contain digit 0 and a filler. If present, the SVN shall be included in the last octet.
alternative-Channel-Type
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
trace-Propagation-List
This optional attribute is an instance of OM class Trace-Propagation-List. See Trace-Propagation-List.

5.4.1.134 Prepare-HO-Res

An instance of OM class Prepare-HO-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 150.

xmap_tab150.png

Table 150. OM Attributes of OM Class Prepare-HO-Res

This OM class contains the following class-specific OM attributes:

handover-Number
An ISDN Address string.
relocation-Number-List
This optional attribute is an instance of OM class Relocation-Number-List. See Relocation-Number-List.
an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
multicall-Bearer-Info
MulticallBearerInfo ::= INTEGER(1..7)
multiple-Bearer-Not-Supported
A Null value whose presence provides indication.
selected-UMTS-Algorithms
This optional attribute is an instance of OM class Selected-UMTS-Algorithms. See Selected-UMTS-Algorithms.
chosen-Radio-Resource-Information
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
iu-Selected-Codec
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
iu-Available-Codec-List
This optional attribute is an instance of OM class Codec-List. See Codec-List.

5.4.1.135 Prepare-Subsequent-HO-Arg

An instance of OM class Prepare-Subsequent-HO-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 157.

xmap_tab157.png

Table 157. OM Attributes of OM Class Prepare-Subsequent-HO-Arg

This OM class contains the following class-specific OM attributes:

target-Cell-Id
GlobalCellId ::= OCTET STRING (SIZE(5..7)) Refers to Cell Global Identification defined in 3GPP TS 23.003. The internal structures is as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digi; octet 2, bits 4321, mobile country code 3rd digit; bits 8765, mobile network code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, Location Area Code according to 3GPP TS 24.008; octets 6 and 7, Call Identity (CI) according to 3GPP TS 24.008.
target-MSC-Number
This parameter refers to the ISDN number of an MSC to which a call has to be handed over. An ISDN Address String containing the number of the MSC.
target-RNC-Id
RNCId ::= OCTET STRING (SIZE(7)) The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; octet 1, bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code, 3rd digit; bits 8765, mobile network code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, location area code according to 3GPP TS 24.008; octets 6 and 7, RNC Id value according to 3GPP TS 25.413.
an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
selected-Rab-Id
RAB-Id ::= INTEGER(1..255)
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
geran-Classmark
GERAN-Classmark ::= OCTET STRING (SIZE(2..87)) Octets are coded according to GERAN Classmark information element in 3GPP TS 48.008.
rab-Configuration-Indicator
A Null value whose presence provides indication.

5.4.1.136 Prepare-Subsequent-HO-Res

An instance of OM class Prepare-Subsequent-HO-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 158.

xmap_tab158.png

Table 158. OM Attributes of OM Class Prepare-Subsequent-HO-Res

This OM class contains the following class-specific OM attributes:

an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.137 Process-Access-Signalling-Arg

An instance of OM class Proces-Access-Signalling-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 159.

xmap_tab159.png

Table 159. OM Attributes of OM Class Process-Access-Signalling-Arg

This OM class contains the following class-specific OM attributes:

an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
selected-UMTS-Algorithm
This optional attribute is an instance of OM class Selected-UMTS-Algorithms. See Selected-UMTS-Algorithms.
selected-GSM-Algorithm
SelectedGSM-Algorithm ::= OCTET STRING (SIZE(1)) Internal structure is coded as Algorithm Identifier octet from Chosen Encryption Algorithm defined in 3GPP TS 48.008. A node shall mark only the selected GSM algorithm.
chosen-Radio-Resource-Information
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
selected-Rab-Id
RAB-Id ::= INTEGER(1..255)
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
iu-Selected-Codec
Codec ::= OCTET STRING (SIZE(1..4)) The internal structure is defined as follows: octet 1, coded as codec identification code in 3GPP TS 26.103; octets 2, 3, 4, parameters for the codec as defined in 3GPP TS 26.103, if available, length depending on the codec.
iu-Available-Codec-List
This optional attribute is an instance of OM class Codec-List. See Codec-List.

5.4.1.138 Provide-Subscriber-Info-Arg

An instance of OM class Provide-Subscriber-Info-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 276.

xmap_tab276.png

Table 276. OM Attributes of OM Class Provide-Subscriber-Info-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string.
requested-Info
This attribute is an instance of OM class Requested-Info. See Requested-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
call-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.

5.4.1.139 Provide-Subscriber-Info-Res

An instance of OM class Provide-Subscriber-Info-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 277.

xmap_tab277.png

Table 277. OM Attributes of OM Class Provide-Subscriber-Info-Res

This OM class contains the following class-specific OM attributes:

subscriber-Info
This attribute is an instance of OM class Subscriber-Info. See Subscriber-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.140 PS-Subscriber-State

An instance of OM class PS-Subscriber-State represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 285. This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

xmap_tab285.png

Table 285. OM Attributes of OM Class PS-Subscriber-State

This OM class contains the following class-specific OM attributes:

not-Provided-From-SGSN
A Null value whose presence provides indication.
ps-Detached
A Null value whose presence provides indication.
ps-Attached-Not-Reachable-For-Paging
A Null value whose presence provides indication.
ps-Attached-Reachable-For-Paging
A Null value whose presence provides indication.
ps-PDP-Active-Not-Reachable-For-Paging
This optional attribute is an instance of OM class PDP-Context-Info-List. See PDP-Context-Info-List.
ps-PDP-Active-Reachable-For-Paging
This optional attribute is an instance of OM class PDP-Context-Info-List. See PDP-Context-Info-List.
net-Det-Not-Reachable
An enumeration containing one of the following values:
ms-purged
(‘MAP_T_MS_PURGED’ ‘0’)
imsi-detached
(‘MAP_T_IMSI_DETACHED’ ‘1’)
restricted-area
(‘MAP_T_RESTRICTED_AREA’ ‘2’)
not-registered
(‘MAP_T_NOT_REGISTERED’ ‘3’)

5.4.1.141 Purge-MS-Arg

An instance of OM class Purge-MS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 128.

xmap_tab128.png

Table 128. OM Attributes of OM Class Purge-MS-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
vlr-Number
This attribute refers to the ISDN number of a VLR. An ISDN Address String containing the ISDN address of the VLR.
sgsn-Number
This attribute refers to the ISDN number of an SGSN. An ISDN Address String containing the ISDN address of the SGSN.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.142 Purge-MS-Res

An instance of OM class Purge-MS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 129.

xmap_tab129.png

Table 129. OM Attributes of OM Class Purge-MS-Res

This OM class contains the following class-specific OM attributes:

freeze-TMSI
A Null value whose presence provides indication.
freeze-P-TMSI
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
freeze-N-TMSI
A Null value whose presence provides indication.

5.4.1.143 Quintuplet-List

An instance of OM class Quintuplet-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 134.

xmap_tab134.png

Table 134. OM Attributes of OM Class Quintuplet-List

This OM class contains the following class-specific OM attributes:

authentication-Quintuplet
This optional attribute is one to five instances of OM class Authentication-Quintuplet. See Authentication-Quintuplet.

5.4.1.144 Radio-Resource-List

An instance of OM class Radio-Resource-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 153.

xmap_tab153.png

Table 153. OM Attributes of OM Class Radio-Resource-List

This OM class contains the following class-specific OM attributes:

radio-Resource
One to seven instances of OM class Radio-Resource. See Radio-Resource.

5.4.1.145 Radio-Resource

An instance of OM class Radio-Resource represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 154.

xmap_tab154.png

Table 154. OM Attributes of OM Class Radio-Resource

This OM class contains the following class-specific OM attributes:

radio-Resource-Information
RadioResourceInformation ::= OCTET STRING (SIZE(3..13)) Octets are coded according to the Channel Type information element in 3GPP TS 48.008.
rab-Id
RAB-Id ::= INTEGER(1..255)
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.146 Relocation-Number-List

An instance of OM class Relocation-Number-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 164.

xmap_tab164.png

Table 164. OM Attributes of OM Class Relocation-Number-List

This OM class contains the following class-specific OM attributes:

relocation-Number
This optional attribute is an instance of OM class Relocation-Number. See Relocation-Number.

5.4.1.147 Relocation-Number

An instance of OM class Relocation-Number represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 165.

xmap_tab165.png

Table 165. OM Attributes of OM Class Relocation-Number

This OM class contains the following class-specific OM attributes:

handover-Number
An ISDN address string.
rab-Id
RAB-Id ::= INTEGER(1..255)
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.148 Requested-Info

An instance of OM class Requested-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 281.

xmap_tab281.png

Table 281. OM Attributes of OM Class Requested-Info

This OM class contains the following class-specific OM attributes:

location-Information
A Null value whose presence provides indication.
subscriber-State
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
current-Location
A Null value whose presence provides indication.
requested-Domain
An enumeration containing one of the following values:
cs-domain
(‘MAP_T_CS_DOMAIN’ ‘0’)
ps-domain
(‘MAP_T_PS_DOMAIN’ ‘1’)

imei
A Null value whose presence provides indication.
ms-Classmark
A Null value whose presence provides indication.
mnp-Requested-Info
A Null value whose presence provides indication.

5.4.1.149 Requested-Subscription-Info

An instance of OM class Requested-Subscription-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 292.

xmap_tab292.png

Table 292. OM Attributes of OM Class Requested-Subscription-Info

This OM class contains the following class-specific OM attributes:

requested-SS-Info
This optional attribute is an instance of OM class SS-For-BS-Code. See SS-For-BS-Code.
odb
A Null value whose presence indicates support.
requested-CAMEL-Subscription-Info
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
t-csi
(‘MAP_T_T_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
tif-csi
(‘MAP_T_TIF_CSI’ ‘3’)
gprs-csi
(‘MAP_T_GPRS_CSI’ ‘4’)
mo-sms-csi
(‘MAP_T_MO_SMS_CSI’ ‘5’)
ss-csi
(‘MAP_T_SS_CSI’ ‘6’)
m-csi
(‘MAP_T_M_CSI’ ‘7’)
d-csi
(‘MAP_T_D_CSI’ ‘8’)

supported-VLR-CAMEL-Phases
A Null value whose presence indicates support.
supported-SGSN-CAMEL-Phases
A Null value whose presence indicates support.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
additional-Requested-CAMEL-Subscription-Info
A bit string containing zero or more of the following bits:
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘0’)
mg-csi
(‘MAP_T_MG_CSI’ ‘1’)
o-im-csi
(‘MAP_T_O_IM_CSI’ ‘2’)
d-im-csi
(‘MAP_T_D_IM_CSI’ ‘3’)
vt-im-csi
(‘MAP_T_VT_IM_CSI’ ‘4’)

msdisdn-BS-List
A Null value whose presence indicates support.

5.4.1.150 Reset-Arg

An instance of OM class Reset-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 269.

xmap_tab269.png

Table 269. OM Attributes of OM Class Reset-Arg

This OM class contains the following class-specific OM attributes:

hlr-Number
This attribute refers to the ISDN number of an HLR. An ISDN Address String containing the ISDN address of the HLR.
hlr-List
This optional attribute is an instance of OM class HLR-List. See HLR-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.151 Restore-Data-Arg

An instance of OM class Restore-Data-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 270.

xmap_tab270.png

Table 270. OM Attributes of OM Class Restore-Data-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
vlr-Capability
This optional attribute is an instance of OM class VLR-Capability. See VLR-Capability.

5.4.1.152 Restore-Data-Res

An instance of OM class Restore-Data-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 271.

xmap_tab271.png

Table 271. OM Attributes of OM Class Restore-Data-Res

This OM class contains the following class-specific OM attributes:

hlr-Number
This attribute refers to the ISDN number of an HLR. An ISDN Address String containing the ISDN address of the HLR.
ms-Not-Reachable
A Null value whose presence indicates support.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.153 Resynchronisation-Info

An instance of OM class Resynchronisation-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 168.

xmap_tab168.png

Table 168. OM Attributes of OM Class Resynchronisation-Info

This OM class contains the following class-specific OM attributes:

rand
RAND ::= OCTET STRING (SIZE(16))
auts
AUTS ::= OCTET STRING (SIZE(16))
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.154 Selected-UMTS-Algorithms

An instance of OM class Selected-UMTS-Algorithms represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 155.

xmap_tab155.png

Table 155. OM Attributes of OM Class Selected-UMTS-Algorithms

This OM class contains the following class-specific OM attributes:

integrity-Protection-Algorithm
ChosenIntegrityProtectionAlgorithm ::= OCTET STRING(SIZE(1)) Octet contains a complete IntegrityProtectionAlgorithm data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included in the least significant bits.
encryption-Algorithm
ChosenEncryptionAlgorithm ::= OCTET STRING(SIZE(1)) Octet contains a complete EncryptionAlgorithm data type as defined in 3GPP TS 25.413, encoded according to the encoding scheme mandated by 3GPP TS 25.413. Padding bits are included in the least significant bits.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.155 Send-Authentication-Info-Arg

An instance of OM class Send-Authentication-Info-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 166.

xmap_tab166.png

Table 166. OM Attributes of OM Class Send-Authentication-Info-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
number-Of-Requested-Vectors
NumberOfRequestedVectors ::= INTEGER(1..5)
segmentation-Prohibited
A Null value whose presence provides indication.
immediate-Response-Preferred
A Null value whose presence provides indication.
re-synchronisation-Info
This optional attribute is an instance of OM class Resynchronisation-Info. See Resynchronisation-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
requesting-Node-Type
An enumeration containing one of the following values:
vlr
(‘MAP_T_VLR’ ‘0’)
sgsn
(‘MAP_T_SGSN’ ‘1’)
s-cscf
(‘MAP_T_S_CSCF’ ‘2’)
bsf
(‘MAP_T_BSF’ ‘3’)
gan-aaa-server
(‘MAP_T_GAN_AAA_SERVER’ ‘4’)
wlan-aaa-server
(‘MAP_T_WLAN_AAA_SERVER’ ‘5’)
mme
(‘MAP_T_MME’ ‘16’)
mme-sgsn
(‘MAP_T_MME_SGSN’ ‘17’)

requesting-PLMN-Id
PLMN-Id ::= OCTET STRING (SIZE(3)) The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code 3rd digit; bits 8765, mobile network code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit.
number-Of-Requested-Additional-Vectors
NumberOfRequestedVectors ::= INTEGER(1..5)
additional-Vectors-Are-For-EPS
A Null value whose presence provides indication.

5.4.1.156 Send-Authentication-Info-Res

An instance of OM class Send-Authentication-Info-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 167.

xmap_tab167.png

Table 167. OM Attributes of OM Class Send-Authentication-Info-Res

This OM class contains the following class-specific OM attributes:

authentication-Set-List
This optional attribute is an instance of OM class Authentication-Set-List. See Authentication-Set-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
eps-Authentication-Set-List
This optional attribute is an instance of OM class EPS-Authentication-Set-List. See EPS-Authentication-Set-List.

5.4.1.157 Send-End-Signal-Arg

An instance of OM class Send-End-Signal-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 162.

xmap_tab162.png

Table 162. OM Attributes of OM Class Send-End-Signal-Arg

This OM class contains the following class-specific OM attributes:

an-APDU
This attribute is an instance of OM class Access-Network-Signal-Info. See Access-Network-Signal-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.158 Send-End-Signal-Res

An instance of OM class Send-End-Signal-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 163.

xmap_tab163.png

Table 163. OM Attributes of OM Class Send-End-Signal-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.159 Send-Identification-Arg

An instance of OM class Send-Identification-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 130.

xmap_tab130.png

Table 130. OM Attributes of OM Class Send-Identification-Arg

This OM class contains the following class-specific OM attributes:

tmsi
TMSI ::= OCTET STRING(SIZE(1..4)) This attribute is the Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003. It is between one and four octets in length.
number-Of-Requested-Vectors
NumberOfRequestedVectors ::= INTEGER(1..5)
segmentation-Prohibited
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
msc-Number
This attribute refers to the ISDN number of an MSC. An ISDN Address String containing the number of the MSC.
previous-LAI
LAIFixedLength = OCTET STRING(SIZE(5)) Refers to Location Area Identification defined in 3GPP TS 23.003. The internal structure is defined as follows: octet 1, bits 4321, mobile country code 1st digit; bits 8765, mobile country code 2nd digit; octet 2, bits 4321, mobile country code 3rd digit; 8765 mobile netework code 3rd digit or filler (1111) for 2 digit MNCs; octet 3, bits 4321, mobile network code 1st digit; bits 8765, mobile network code 2nd digit; octets 4 and 5, location area code (LAC) according to 3GPP TS 24.008.
hop-Counter
HopCounter ::= INTEGER(0..3)

5.4.1.160 Send-Identification-Res

An instance of OM class Send-Identification-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 131.

xmap_tab131.png

Table 131. OM Attributes of OM Class Send-Identification-Res

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
authentication-Set-List
This optional attribute is an instance of OM class Authentication-Set-List. See Authentication-Set-List.
current-Security-Context
This optional attribute is an instance of OM class Current-Security-Context. See Current-Security-Context.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.161 Send-Routing-Info-For-Gprs-Arg

An instance of OM class Send-Routing-Info-For-Gprs-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 263.

xmap_tab263.png

Table 263. OM Attributes of OM Class Send-Routing-Info-For-Gprs-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
ggsn-Number
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.162 Send-Routing-Info-For-Gprs-Res

An instance of OM class Send-Routing-Info-For-Gprs-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 264.

xmap_tab264.png

Table 264. OM Attributes of OM Class Send-Routing-Info-For-Gprs-Res

This OM class contains the following class-specific OM attributes:

sgsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
ggsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
mobile-Not-Reachable-Reason
AbsentSubscriberDiagnosticSM ::= INTEGER (0..255) Values are defined in 3GPP TS 23.040.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.163 Service-Type-List

An instance of OM class Service-Type-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 219.

xmap_tab219.png

Table 219. OM Attributes of OM Class Service-Type-List

This OM class contains the following class-specific OM attributes:

service-Type
One to thirty-two instaces of OM class Service-Type. See Service-Type.

5.4.1.164 Service-Type

An instance of OM class Service-Type represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 220.

xmap_tab220.png

Table 220. OM Attributes of OM Class Service-Type

This OM class contains the following class-specific OM attributes:

service-Type-Identity
LCSServiceTypeID ::= INTEGER (0..127) The integer values 0-63 are reserved for standard LCS service types; the integer values 64-127 are reserved for non-standard LCS service types.
gmlc-Restriction
An enumeration containing one of the following values:
gmlc-list
(‘MAP_T_GMLC_LIST’ ‘0’)
home-country
(‘MAP_T_HOME_COUNTRY’ ‘1’)

notification-To-MS-User
An enumeration containing one of the following values:
notify-location-allowed
(‘MAP_T_NOTIFY_LOCATION_ALLOWED’ ‘0’)
notify-and-verify-location-allowed-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_NO_REPONSE’ ‘1’)
notify-and-verity-location-allowed-if-no-response
(‘MAP_T_NOTIFY_AND_VERIFY_LOCATION_ALLOWED_IF_NO_RESPONSE’ ‘2’)
location-not-allowed
(‘MAP_T_LOCATION_NOT_ALLOWED’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.165 SGSN-CAMEL-Subscription-Info

An instance of OM class SGSN-CAMEL-Subscription-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 190.

xmap_tab190.png

Table 190. OM Attributes of OM Class SGSN-CAMEL-Subscription-Info

This OM class contains the following class-specific OM attributes:

gprs-CSI
This optional attribute is an instance of OM class GPRS-CSI. See GPRS-CSI.
mo-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
mt-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
mt-sms-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class MT-SMS-CAMEL-TDP-Criteria-List. See MT-SMS-CAMEL-TDP-Criteria-List.
mg-CSI
This optional attribute is an instance of OM class MG-CSI. See MG-CSI.

5.4.1.166 SGSN-Capability

An instance of OM class SGSN-Capability represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 146.

xmap_tab146.png

Table 146. OM Attributes of OM Class SGSN-Capability

This OM class contains the following class-specific OM attributes:

solsa-Support-Indicator
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
super-Charger-Supported-In-Serving-Network-Entity
This optional attribute is an instance of OM class Super-Charger-Info. See Super-Charger-Info.
gprs-Enhancement-Support-Indicator
A Null value whose presence provides indication.
supported-Camel-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

offered-Camel4-CSIs
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

sms-Call-Barring-Support-Indicator
A Null value whose presence provides indication.
supported-RAT-Types-Indicator
A bit string containing zero or more of the following bits:
utran
(‘MAP_T_UTRAN’ ‘0’)
geran
(‘MAP_T_GERAN’ ‘1’)
gan
(‘MAP_T_GAN’ ‘2’)
i-hspa-evolution
(‘MAP_T_I_HSPA_EVOLUTION’ ‘3’)
e-utran
(‘MAP_T_E_UTRAN’ ‘4’)

supported-Features
A bit string containing zero or more of the following bits:
odb-all
(‘MAP_T_ODB_ALL’ ‘0’)
odb-HPLMN-APN
(‘MAP_T_ODB_HPLMN_APN’ ‘1’)
odb-VPLMN-APN
(‘MAP_T_ODB_VPLMN_APN’ ‘2’)
reg-Sub
(‘MAP_T_REG_SUB’ ‘3’)

5.4.1.167 SMS-CAMEL-TDP-Data-List

An instance of OM class SMS-CAMEL-TDP-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 255.

xmap_tab255.png

Table 255. OM Attributes of OM Class SMS-CAMEL-TDP-Data-List

This OM class contains the following class-specific OM attributes:

sms-CAMEL-TDP-Data
One to ten (maxNumOfCamelTDPData) instances of OM class SMS-CAMEL-TDP-Data. See SMS-CAMEL-TDP-Data.

5.4.1.168 SMS-CAMEL-TDP-Data

An instance of OM class SMS-CAMEL-TDP-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 256.

xmap_tab256.png

Table 256. OM Attributes of OM Class SMS-CAMEL-TDP-Data

This OM class contains the following class-specific OM attributes:

sms-Trigger-Detection-Point
An enumeration containing one of the following values:
sms-collected-info
(‘MAP_T_SMS_COLLECTED_INFO’ ‘1’)
sms-delivery-request
(‘MAP_T_SMS_DELIVERY_REQUEST’ ‘2’)

service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
default-SMS-Handling
continue-transaction
(‘MAP_T_CONTINUE_TRANSACTION’ ‘0’)
release-transaction
(‘MAP_T_RELEASE_TRANSACTION’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.169 SMS-CSI

An instance of OM class SMS-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 254.

xmap_tab254.png

Table 254. OM Attributes of OM Class SMS-CSI

This OM class contains the following class-specific OM attributes:

sms-CAMEL-TDP-Data-List
This optional attribute is an instance of OM class SMS-CAMEL-TDP-Data-List. See SMS-CAMEL-TDP-Data-List.
camel-Capability-Handling
CamelCapabilityHandling ::= INTEGER(1..16) Value 1, CAMEL phase 1; value 2, CAMEL phase 2; value 3, CAMEL phase 3; value 4, CAMEL phase 4. Receiption of values greater than 4 shall be treated as CAMEL phase 4.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.170 SS-Camel-Data

An instance of OM class SS-Camel-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 240.

xmap_tab240.png

Table 240. OM Attributes of OM Class SS-Camel-Data

This OM class contains the following class-specific OM attributes:

ss-Event-List
This optional attribute is an instance of OM class SS-Event-List. See SS-Event-List.
gsmSCF-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.171 SS-CSI

An instance of OM class SS-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 239.

xmap_tab239.png

Table 239. OM Attributes of OM Class SS-CSI

This OM class contains the following class-specific OM attributes:

ss-Camel-Data
This attribute is an instance of OM class SS-Camel-Data. See SS-Camel-Data.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.

5.4.1.172 SS-Event-List

An instance of OM class SS-Event-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 241.

xmap_tab241.png

Table 241. OM Attributes of OM Class SS-Event-List

This OM class contains the following class-specific OM attributes:

ss-Code
One to ten (maxNumOfCamelSSEvents) instances of an SS-Code. SS-Code ::= OCTET STRING (SIZE(1))

5.4.1.173 Subscriber-Data

An instance of OM class Subscriber-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 197.

xmap_tab197.png

Table 197. OM Attributes of OM Class Subscriber-Data

This OM class contains the following class-specific OM attributes:

msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
category
Category ::= OCTET STRING (SIZE(1)) The internal structure is defined in ITU-T Rec. Q.763.
subscriber-Status
An enumeration containing one of the following values:
service-granted
(‘MAP_T_SERVICE_GRANTED’ ‘0’)
operator-determined-barring
(‘MAP_T_OPERATOR_DETERMINED_BARRING’ ‘1’)

bearer-Service-List
This optional attribute is an instance of OM class Bearer-Service-List. See Bearer-Service-List.
teleservice-List
This optional attribute is an instance of OM class Teleservice-List. See Teleservice-List.
provisioned-SS
This optional attribute is an instance of OM class Ext-SS-Info-List. See Ext-SS-Info-List.
odb-Data
This optional attribute is an instance of OM class ODB-Data. See ODB-Data.
roaming-Restriction-Due-To-Unsupported-Feature
A Null value whose presence provides indication.
regional-Subscription-Data
This optional attribute is an instance of OM class Zone-Code-List. See Zone-Code-List.
vbs-Subscription-Data
This optional attribute is an instance of OM class VBS-Data-List. See VBS-Data-List.
vgcs-Subscription-Data
This optional attribute is an instance of OM class VGCS-Data-List. See VGCS-Data-List.
vlr-Camel-Subscription-Info
This optional attribute is an instance of OM class Vlr-Camel-Subscription-Info. See Vlr-Camel-Subscription-Info.

5.4.1.174 Subscriber-Info

An instance of OM class Subscriber-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 278.

xmap_tab278.png

Table 278. OM Attributes of OM Class Subscriber-Info

This OM class contains the following class-specific OM attributes:

location-Information
This optional attribute is an instance of OM class Location-Information. See Location-Information.
subscriber-State
This attribute is an instance of OM class Subscriber-State. See Subscriber-State.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
location-Information-GPRS
This optional attribute is an instance of OM class Location-Information-GPRS. See Location-Information-GPRS.
ps-Subscriber-State
This attribute is an instance of OM class PS-Subscriber-State. See PS-Subscriber-State.
imei
IMEI ::= TBCD-STRING(SIZE(8)) Refers to International Mobile Station Equipment Identity defined in 3GPP TS 23.003. The last octet shall contain digit 0 and a filler.
ms-Classmark-2
MS-Classmark2 ::= OCTET STRING (SIZE(3)) This parameter carries the value part of the MS Classmark 2 IE defined in 3GPP TS 24.008.
gprs-MS-Class
This optional attribute is an instance of OM class GPRS-MS-Class. See GPRS-MS-Class.
mnp-Info-Res
This optional attribute is an instance of OM class MNP-Info-Res. See MNP-Info-Res.

5.4.1.175 Subscriber-State

An instance of OM class Subscriber-State represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 284. This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

xmap_tab284.png

Table 284. OM Attributes of OM Class Subscriber-State

This OM class contains the following class-specific OM attributes:

assumed-Idle
A Null value whose presence provides indication.
camel-Busy
A Null value whose presence provides indication.
net-Det-Not-Reachable
An enumeration containing one of the following values:
ms-purged
(‘MAP_T_MS_PURGED’ ‘0’)
imsi-detached
(‘MAP_T_IMSI_DETACHED’ ‘1’)
restricted-area
(‘MAP_T_RESTRICTED_AREA’ ‘2’)
not-registered
(‘MAP_T_NOT_REGISTERED’ ‘3’)

not-Provided-From-VLR
A Null value whose presence provides indication.

5.4.1.176 Super-Charger-Info

An instance of OM class Super-Charger-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 123. This OM class represents a choice and exaclty one attribute must appear in an instance of this OM class.

xmap_tab123.png

Table 123. OM Attributes of OM Class Super-Charger-Info

This OM class contains the following class-specific OM attributes:

send-Subscriber-Data
A Null value whose presence provides indication.
subscriber-Data-Stored
AgeIndicator ::= OCTET STRING (SIZE(1..6)) The internal structure of this parameter is implementation specific.

5.4.1.177 Supported-Codecs-List

An instance of OM class Supported-Codecs-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 160.

xmap_tab160.png

Table 160. OM Attributes of OM Class Supported-Codecs-List

This OM class contains the following class-specific OM attributes:

utran-Codec-List
This optional attribute is an instance of OM class Codec-List. See Codec-List.
geran-Codec-List
This optional attribute is an instance of OM class Codec-List. See Codec-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.178 T-BCSM-CAMEL-TDP-Criteria-List

An instance of OM class T-BCSM-CAMEL-TDP-Criteria-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 245.

xmap_tab245.png

Table 245. OM Attributes of OM Class T-BCSM-CAMEL-TDP-Criteria-List

This OM class contains the following class-specific OM attributes:

t-BCSM-CAMEL-TDP-Criteria
One to ten (maxNumOfCamelTDPData) instances of OM class T-BCSM-CAMEL-TDP-Criteria. See T-BCSM-CAMEL-TDP-Criteria.

5.4.1.179 T-BCSM-CAMEL-TDP-Criteria

An instance of OM class T-BCSM-CAMEL-TDP-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 247.

xmap_tab247.png

Table 247. OM Attributes of OM Class T-BCSM-CAMEL-TDP-Criteria

This OM class contains the following class-specific OM attributes:

t-BCSM-Trigger-Detection-Point
An enumeration containing one of the following values:
term-attempt-authorized
(‘MAP_T_TERM_ATTEMPT_AUTHORIZED’ ‘12’)
t-busy
(‘MAP_T_T_BUSY’ ‘13’)
t-no-answer
(‘MAP_T_T_NO_ANSWER’ ‘14’)

basic-Service-Criteria
This optional attribute is an instance of OM class Basic-Service-Criteria. See Basic-Service-Criteria.
t-Cause-Value-Criteria
This optional attribute is an instance of OM class T-Cause-Value-Criteria. See T-Cause-Value-Criteria.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.180 T-Bcsm-Camel-TDP-Data-List

An instance of OM class T-Bcsm-Camel-TDP-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 261.

xmap_tab261.png

Table 261. OM Attributes of OM Class T-Bcsm-Camel-TDP-Data-List

This OM class contains the following class-specific OM attributes:

t-Bcsm-Camel-TDP-Data
One to ten (maxNumOfCamelTDPData) instances of OM class T-Bcsm-Camel-TDP-Data. See T-Bcsm-Camel-TDP-Data.

5.4.1.181 T-Bcsm-Camel-TDP-Data

An instance of OM class T-Bcsm-Camel-TDP-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 262.

xmap_tab262.png

Table 262. OM Attributes of OM Class T-Bcsm-Camel-TDP-Data

This OM class contains the following class-specific OM attributes:

t-Bcsm-Trigger-Detection-Point
An enumeration containing one of the following values:
term-attempt-authorized
(‘MAP_T_TERM_ATTEMPT_AUTHORIZED’ ‘12’)
t-busy
(‘MAP_T_T_BUSY’ ‘13’)
t-no-answer
(‘MAP_T_T_NO_ANSWER’ ‘14’)

service-Key
ServiceKey ::= INTEGER(0..2147483647)
gsmSCF-Address
An ISDN Address String.
default-Call-Handling
An enumeration containing one of the following values:
continue-call
(‘MAP_T_CONTINUE_CALL’ ‘0’)
release-call
(‘MAP_T_RELEASE_CALL’ ‘1’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.182 T-Cause-Value-Criteria

An instance of OM class T-Cause-Value-Criteria represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 253.

xmap_tab253.png

Table 253. OM Attributes of OM Class T-Cause-Value-Criteria

This OM class contains the following class-specific OM attributes:

cause-Value
One to five (maxNumOfCAMEL-T-CauseValueCriteria) instances of a cause value. CauseValue ::= OCTET STRING (SIZE(1)) Type extracted from Cause parameter in ITU-T Recommendation Q.763. For the use of cause value refer to ITU-T Recommendation Q.850.

5.4.1.183 T-CSI

An instance of OM class T-CSI represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 260.

xmap_tab260.png

Table 260. OM Attributes of OM Class T-CSI

This OM class contains the following class-specific OM attributes:

t-Bcsm-Camel-TDP-Data-List
This attribute is an instance of OM class T-Bcsm-Camel-TDP-Data-List. See T-Bcsm-Camel-TDP-Data-List.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
camel-Capability-Handling
CamelCapabilityHandling ::= INTEGER(1..16) Value 1, CAMEL phase 1; value 2, CAMEL phase 2; value 3, CAMEL phase 3; value 4, CAMEL phase 4. Receiption of values greater than 4 shall be treated as CAMEL phase 4.
notification-To-CSE
A Null value whose presence provides indication.
csi-Active
A Null value whose presence provides indication.

5.4.1.184 Teleservice-List

An instance of OM class Teleservice-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 199.

xmap_tab199.png

Table 199. OM Attributes of OM Class Teleservice-List

This OM class contains the following class-specific OM attributes:

ext-Teleservice-Code
One to twenty instances of Ext-TeleserviceCode.

Ext-TeleserviceCode ::= OCTET STRING (SIZE(1..5)) This type is used to represent the code identifying a single teleservice, group of teleservices, or all teleservices. The services are defined in GSM TS 22.003. The internal structure is defined as follows: octet 1, bits 87654321, group (bits 8765) and specific service (bits 4321); octets 2-5, reserved for future use. If received, Ext-TeleserviceCode shall be treated according to the exception handling defined for the operation that uses this type. Ext-TeleserviceCode includes all values defined for TeleserviceCode.

5.4.1.185 TPDU-Type-Criterion

An instance of OM class TPDU-Type-Criterion represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 235.

xmap_tab235.png

Table 235. OM Attributes of OM Class TPDU-Type-Criterion

This OM class contains the following class-specific OM attributes:

mt-Sms-TPDU-Type
One to five (maxNumOfTPDUTypes) instances of an MT-SMS-TPDU-Type, which is an enumeration containing one of the following values:
sms-deliver
(‘MAP_T_SMS_DELIVER’ ‘0’)
sms-submit-report
(‘MAP_T_SMS_SUBMIT_REPORT’ ‘1’)
sms-status-report
(‘MAP_T_SMS_STATUS_REPORT’ ‘2’)

5.4.1.186 Triplet-List

An instance of OM class Triplet-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 133.

xmap_tab133.png

Table 133. OM Attributes of OM Class Triplet-List

This OM class contains the following class-specific OM attributes:

authentication-Triplet
This optional attribute is one to five instances of OM class Authentication-Triplet. See Authentication-Triplet.

5.4.1.187 UESBI-Iu

An instance of OM class UESBI-Iu represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 173.

xmap_tab173.png

Table 173. OM Attributes of OM Class UESBI-Iu

This OM class contains the following class-specific OM attributes:

uesbi-IuA
UESBI-IuA ::= BIT STRING (SIZE(1..128)) See 3GPP TS 25.413.
uesbi-IuB
UESBI-IuB ::= BIT STRING (SIZE(1..128)) See 3GPP TS 25.413.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.188 UMTS-Security-Context-Data

An instance of OM class UMTS-Security-Context-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 139.

xmap_tab139.png

Table 139. OM Attributes of OM Class UMTS-Security-Context-Data

This OM class contains the following class-specific OM attributes:

ck
CK ::= OCTET STRING (SIZE(16))
ik
IK ::= OCTET STRING (SIZE(16))
ksi
KSI ::= OCTET STRING (SIZE(1)) The internal structure is defined in 3GPP TS 24.008.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.1.189 Update-Gprs-Location-Arg

An instance of OM class Update-Gprs-Location-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 142.

xmap_tab142.png

Table 142. OM Attributes of OM Class Update-Gprs-Location-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
sgsn-Number
This attribute refers to the ISDN number of an SGSN. An ISDN Address String containing the ISDN address of the SGSN.
sgsn-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
sgsn-Capability
This optional attribute is an instance of OM class SGSN-Capability. See SGSN-Capability.
inform-Previous-Network-Entity
A Null value whose presence provides indication.
ps-LCS-Not-Supported-By-UE
A Null value whose presence provides indication.
v-Gmlc-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
add-Info
This optional attribute is an instance of OM class Add-Info. See Add-Info.
eps-Info
This optional attribute is an instance of OM class EPS-Info. See EPS-Info.
serving-Node-Type-Indicator
A Null value whose presence provides indication.
skip-Subscriber-Data-Update
A Null value whose presence provides indication.
used-RAT-Type
An enumeration containing one of the following values:
utran
(‘MAP_T_UTRAN’ ‘0’)
geran
(‘MAP_T_GERAN’ ‘1’)
gsn
(‘MAP_T_GSN’ ‘2’)
i-hspa-evolution
(‘MAP_T_I_HSPA_EVOLUTION’ ‘3’)
e-utran
(‘MAP_T_E_UTRAN’ ‘4’)

5.4.1.190 Update-Gprs-Location-Res

An instance of OM class Update-Grps-Location-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 143.

xmap_tab143.png

Table 143. OM Attributes of OM Class Update-Gprs-Location-Res

This OM class contains the following class-specific OM attributes:

hlr-Number
This attribute refers to the ISDN number of an HLR. An ISDN Address String containing the ISDN address of the HLR.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
add-Capability
A Null value whose presence provides indication.
sgsn-mme-Separation-Supported
A Null value whose presence provides indication.

5.4.1.191 Update-Location-Arg

An instance of OM class Update-Location-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 119.

xmap_tab119.png

Table 119. OM Attributes of OM Class Update-Location-Arg

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msc-Number
This attribute refers to the ISDN number of an MSC. An ISDN Address String containing the number of the MSC.
vlr-Number
This attribute refers to the ISDN number of a VLR. An ISDN Address String containing the ISDN address of the VLR.
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
vlr-Capability
This optional attribute is an instance of OM class VLR-Capability. See VLR-Capability.
inform-Previous-Network-Entity
A Null value whose presence provides indication.
cs-LCS-Not-Supported-By-UE
A Null value whose presence provides indication.
v-Gmlc-Address
GSN-Address ::= OCTET STRING(SIZE(5..17)) Octets are coded according to 3GPP TS 23.003.
add-Info
This optional attributes is an instance of OM calss Add-Info. See Add-Info.
paging-Area
PagingArea ::= SEQUENCE SIZE(1..5) OF LocationArea
skip-Subscriber-Data-Update
A Null value whose presence provides indication.

5.4.1.192 Update-Location-Res

An instance of OM class Update-Location-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 124.

xmap_tab124.png

Table 124. OM Attributes of OM Class Update-Location-Res

This OM class contains the following class-specific OM attributes:

hlr-Number
This attribute refers to the ISDN number of an HLR. An ISDN Address String containing the ISDN address of the HLR.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
add-Capability
A Null value whose presence provides indication.
paging-Area-Capability
A Null value whose presence provides indication.

5.4.1.193 VBS-Data-List

An instance of OM class VBS-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 272.

xmap_tab272.png

Table 272. OM Attributes of OM Class VBS-Data-List

This OM class contains the following class-specific OM attributes:

voice-Broadcast-Data
One to fifty (maxNumOfVBSGroupIds) instances of OM class Voice-Broadcast-Data. See Voice-Broadcast-Data.

5.4.1.194 VGCS-Data-List

An instance of OM class VGCS-Data-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 273.

xmap_tab273.png

Table 273. OM Attributes of OM Class VGCS-Data-List

This OM class contains the following class-specific OM attributes:

voice-Group-Call-Data
One to fifty (maxNumOfVGCSGroupIds) instances of OM class Voice-Group-Call-Data. See Voice-Group-Call-Data.

5.4.1.195 Vlr-Camel-Subscription-Info

An instance of OM class Vlr-Camel-Subscription-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 232.

xmap_tab232.png

Table 232. OM Attributes of OM Class Vlr-Camel-Subscription-Info

This OM class contains the following class-specific OM attributes:

o-CSI
This optional attribute is an instance of OM class O-CSI. See O-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
ss-CSI
This optional attribute is an instance of OM class SS-CSI. See SS-CSI.
o-Bcsm-Camel-TDP-Criteria-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Criteria-List. See O-Bcsm-Camel-TDP-Criteria-List.
tif-CSI
A Null value whose presence provides indication.
m-CSI
This optional attribute is an instance of OM class M-CSI. See M-CSI.
mo-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
vt-CSI
This optional attribute is an instance of OM class T-CSI. See T-CSI.
t-BCSM-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class T-BCSM-CAMEL-TDP-Criteria-List. See T-BCSM-CAMEL-TDP-Criteria-List.
d-CSI
This optional attribute is an instance of OM class D-CSI. See D-CSI.
mt-sms-CSI
This optional attribute is an instance of OM class SMS-CSI. See SMS-CSI.
mt-sms-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class MT-SMS-CAMEL-TDP-Criteria-List. See MT-SMS-CAMEL-TDP-Criteria-List.

5.4.1.196 VLR-Capability

An instance of OM class VLR-Capability represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 122.

xmap_tab122.png

Table 122. OM Attributes of OM Class VLR-Capability

This OM class contains the following class-specific OM attributes:

supported-Camel-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
solsa-Support-Indicator
A Null value whose presence indicates support.
ist-Support-Indicator
An enumeration containing one of the following values:
basic-ist-support
(‘MAP_T_BASIC_IST_SUPPORT’ ‘0’)
ist-command-supported
(‘MAP_T_IST_COMMAND_SUPPORTED’ ‘1’)

super-Charger-Supported-In-Serving-Network-Entity
An optional instance of OM class Super-Charger-Info. See Super-Charger-Info.
long-FTN-Supported
A Null value whose presence indicates support.
supported-LCS-Capability-Sets
A bit string containing zero or more of the following bits:
lcs-capability-set1
(‘MAP_T_LCS_CAPABILITY_SET1’ ‘0’)
lcs-capability-set2
(‘MAP_T_LCS_CAPABILITY_SET2’ ‘1’)
lcs-capability-set3
(‘MAP_T_LCS_CAPABILITY_SET3’ ‘2’)
lcs-capability-set4
(‘MAP_T_LCS_CAPABILITY_SET4’ ‘3’)
lcs-capability-set5
(‘MAP_T_LCS_CAPABILITY_SET5’ ‘4’)

offered-Camel4-CSIs
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

supported-RAT-Types-Indicator
A bit string containing zero or more of the following bits:
utran
(‘MAP_T_UTRAN’ ‘0’)
geran
(‘MAP_T_GERAN’ ‘1’)
gan
(‘MAP_T_GAN’ ‘2’)
i-hspa-evolution
(‘MAP_T_I_HSPA_EVOLUTION’ ‘3’)
e-utran
(‘MAP_T_E_UTRAN’ ‘4’)

long-Group-ID-Supported
A Null value whose presence indicates support.

5.4.1.197 Voice-Broadcast-Data

An instance of OM class Voice-Broadcast-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 275.

xmap_tab275.png

Table 275. OM Attributes of OM Class Voice-Broadcast-Data

This OM class contains the following class-specific OM attributes:

group-Id
GroupId ::= TBCD-STRING(SIZE(3)) When Group-Id is less than six characters in lneght, the TBCD filler (1111) is used to fill unused half octets. Referes to the Group Identification as specified in 3GPP TS 23.003 and 3GPP TS 43.068/43.069.
broadcast-Init-Entitlement
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-Group-Id
Long-GroupId ::= TBCD-STRING (SIZE(4)) When Long-Group-Id is less than eight characters in length, the TBCD filler (1111) is used to fill unused half octets. Refers to Group Identification as specified in 3GPP TS 23.003 and 3GPP TS 43.068/43.069.

5.4.1.198 Voice-Group-Call-Data

An instance of OM class Voice-Group-Call-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 274.

xmap_tab274.png

Table 274. OM Attributes of OM Class Voice-Group-Call-Data

This OM class contains the following class-specific OM attributes:

group-Id
GroupId ::= TBCD-STRING(SIZE(3)) When Group-Id is less than six characters in lneght, the TBCD filler (1111) is used to fill unused half octets. Referes to the Group Identification as specified in 3GPP TS 23.003 and 3GPP TS 43.068/43.069.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
additional-Subscriptions
A bit string containing zero or more of the following bits:
privileged-up-link-request
(‘MAP_T_PRIVILEGED_UP_LINK_REQUEST’ ‘0’)
emergency-up-link-request
(‘MAP_T_EMERGENCY_UP_LINK_REQUEST’ ‘1’)
emergency-reset
(‘MAP_T_EMERGENCY_RESET’ ‘2’)

additional-Info
AdditionalInfo ::= BIT STRING (SIZE(1..136)) Refers to additional info as specified in 3GPP TS 43.068.
long-Group-Id
Long-GroupId ::= TBCD-STRING (SIZE(4)) When Long-Group-Id is less than eight characters in length, the TBCD filler (1111) is used to fill unused half octets. Refers to Group Identification as specified in 3GPP TS 23.003 and 3GPP TS 43.068/43.069.

5.4.1.199 Zone-Code-List

An instance of OM class Zone-Code-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 223.

xmap_tab223.png

Table 223. OM Attributes of OM Class Zone-Code-List

This OM class contains the following class-specific OM attributes:

zone-Code
ZoneCode ::= OCTET STRING (SIZE(2)) Internal structure is defined in 3GPP TS 23.003. One to ten instances of a Zone-Code. A zone code is a two octet string.

5.4.2 GSM Operations and Maintenance Package

OM Hierarchy
  • Object
    • Service-Argument
      • GSM-Service-Argument
        • Activate-Trace-Mode-Arg
        • Deactivate-Trace-Mode-Arg
    • Service-Result
      • GSM-Service-Result
        • Activate-Trace-Mode-Res
        • Deactivate-Trace-Mode-Res

5.4.2.1 Activate-Trace-Mode-Arg

An instance of OM class Activate-Trace-Mode-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 313.

xmap_tab313.png

Table 313. OM Attributes of OM Class Activate-Trace-Mode-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
trace-Reference
TraceReference ::= OCTET STRING (SIZE(1..2))
trace-Type
TraceType ::= INTEGER(0..255) Trace types are fully defined in 3GPP TS 52.008.
omc-Id
An address string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
trace-Reference-2
TraceReference2 ::= OCTET STRING (SIZE(3))
trace-Depth-List
This optional attribute is an instance of OM class Trace-Depth-List. See Trace-Depth-List.
trace-NE-Type-List
A bit string containing zero or more of the following bits:
msc-s
(‘MAP_T_MSC_S’ ‘0’)
mgw
(‘MAP_T_MGW’ ‘1’)
sgsn
(‘MAP_T_SGSN’ ‘2’)
ggsn
(‘MAP_T_GGSN’ ‘3’)
rnc
(‘MAP_T_RNC’ ‘4’)
bm-sc
(‘MAP_T_BM_SC’ ‘5’)

trace-Interface-List
This optional attribute is an instance of OM class Trace-Interface-List. See Trace-Interface-List.
trace-Event-List
This optional attribute is an instance of OM class Trace-Event-List. See Trace-Event-List.

5.4.2.2 Activate-Trace-Mode-Res

An instance of OM class Activate-Trace-Mode-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 318.

xmap_tab318.png

Table 318. OM Attributes of OM Class Activate-Trace-Mode-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
trace-Support-Indicator
A Null value whose presence provides indication.

5.4.2.3 Deactivate-Trace-Mode-Arg

An instance of OM class Deactivate-Trace-Mode-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 319.

xmap_tab319.png

Table 319. OM Attributes of OM Class Deactivate-Trace-Mode-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
trace-Reference
TraceReference ::= OCTET STRING (SIZE(1..2))
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
trace-Reference-2
TraceReference2 ::= OCTET STRING (SIZE(3))

5.4.2.4 Deactivate-Trace-Mode-Res

An instance of OM class Deactivate-Trace-Mode-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 320.

xmap_tab320.png

Table 320. OM Attributes of OM Class Deactivate-Trace-Mode-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.2.5 Send-IMSI-Arg

An instance of OM class Send-IMSI-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 428.

xmap_tab428.png

Table 428. OM Attributes of OM Class Send-IMSI-Arg

This OM class contains the following class-specific OM attributes:

msisdn
An ISDN address string.

5.4.2.6 Send-IMSI-Res

An instance of OM class Send-IMSI-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 429.

xmap_tab429.png

Table 429. OM Attributes of OM Class Send-IMSI-Res

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.

5.4.2.7 Trace-Depth-List

An instance of OM class Trace-Depth-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 314.

xmap_tab314.png

Table 314. OM Attributes of OM Class Trace-Depth-List

This OM class contains the following class-specific OM attributes:

msc-s-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
mgw-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
sgsn-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
ggsn-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
rnc-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
bmsc-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)
The value medium is applicable only for RNC. For other network elements, if value medium is received, value minimum shall be applied.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.2.8 Trace-Event-List

An instance of OM class Trace-Event-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 316.

xmap_tab316.png

Table 316. OM Attributes of OM Class Trace-Event-List

This OM class contains the following class-specific OM attributes:

msc-s-List
A bit string containing zero or more of the following bits:
mo-mt-call
(‘MAP_T_MO_MT_CALL’ ‘0’)
mo-mt-sms
(‘MAP_T_MO_MT_SMS’ ‘1’)
lu-imsi-attach-imsi-detach
(‘MAP_T_LU_IMSI_ATTACH_IMSI_DETACH’ ‘2’)
handovers
(‘MAP_T_HANDOVERS’ ‘3’)
ss
(‘MAP_T_SS’ ‘4’)

mgw-List
A bit string containing zero or more of the following bits:
context
(‘MAP_T_CONTEXT’ ‘0’)

sgsn-List
A bit string containing zero or more of the following bits:
pdp-context
(‘MAP_T_PDP_CONTEXT’ ‘0’)
mo-mt-sms
(‘MAP_T_MO_MT_SMS’ ‘1’)
rau-gprs-attach-gprs-detach
(‘MAP_T_RAU_GPRS_ATTACH_GRPS_DETACH’ ‘2’)
mbms-context
(‘MAP_T_MBMS_CONTEXT’ ‘3’)

ggsn-List
A bit string containing zero or more of the following bits:
pdp-context
(‘MAP_T_PDP_CONTEXT’ ‘0’)
mbms-context
(‘MAP_T_MBMS_CONTEXT’ ‘1’)

bmsc-List
A bit string containing zero or more of the following bits:
mbms-multicast-service-activation
(‘MAP_T_MBMS_MULTICAST_SERVICE_ACTIVATION’ ‘0’)

extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.2.9 Trace-Interface-List

An instance of OM class Trace-Interface-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 315.

xmap_tab315.png

Table 315. OM Attributes of OM Class Trace-Interface-List

This OM class contains the following class-specific OM attributes:

msc-s-List
A bit string containing zero or more of the following bits:
a
(‘MAP_T_A’ ‘0’)
iu
(‘MAP_T_IU’ ‘1’)
mc
(‘MAP_T_MC’ ‘2’)
map-g
(‘MAP_T_MAP_G’ ‘3’)
map-b
(‘MAP_T_MAP_B’ ‘4’)
map-e
(‘MAP_T_MAP_E’ ‘5’)
map-f
(‘MAP_T_MAP_F’ ‘6’)
cap
(‘MAP_T_CAP’ ‘7’)
map-d
(‘MAP_T_MAP_D’ ‘8’)
map-c
(‘MAP_T_MAP_C’ ‘9’)

mgw-List
A bit string containing zero or more of the following bits:
mc
(‘MAP_T_MC’ ‘0’)
nb-up
(‘MAP_T_NB_UP’ ‘1’)
iu-up
(‘MAP_T_IU_UP’ ‘2’)

sgsn-List
A bit string containing zero or more of the following bits:
gb
(‘MAP_T_GB’ ‘0’)
iu
(‘MAP_T_IU’ ‘1’)
gn
(‘MAP_T_GN’ ‘2’)
map-gr
(‘MAP_T_MAP_GR’ ‘3’)
map-gd
(‘MAP_T_MAP_GD’ ‘4’)
map-gf
(‘MAP_T_MAP_GF’ ‘5’)
gs
(‘MAP_T_GS’ ‘6’)
ge
(‘MAP_T_GE’ ‘7’)

ggsn-List
A bit string containing zero or more of the following bits:
gn
(‘MAP_T_GN’ ‘0’)
gi
(‘MAP_T_GI’ ‘1’)
gmb
(‘MAP_T_GMB’ ‘2’)

rnc-List
A bit string containing zero or more of the following bits:
iu
(‘MAP_T_IU’ ‘0’)
iur
(‘MAP_T_IUR’ ‘1’)
iub
(‘MAP_T_IUB’ ‘2’)
uu
(‘MAP_T_UU’ ‘3’)

bmsc-List
A bit string containing zero or more of the following bits:
gmb
(‘MAP_T_GMB’ ‘0’)

extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.2.10 Trace-Propagation-List

An instance of OM class Trace-Propagation-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 317.

xmap_tab317.png

Table 317. OM Attributes of OM Class Trace-Propagation-List

This OM class contains the following class-specific OM attributes:

trace-Reference
TraceReference ::= OCTET STRING (SIZE(1..2))
trace-Type
TraceType ::= INTEGER(0..255) Trace types are fully defined in 3GPP TS 52.008.
trace-Reference-2
TraceReference2 ::= OCTET STRING (SIZE(3))
trace-Recording-Session-Reference
TraceRecordingSessionReference ::= OCTET STRING (SIZE(2))
rnc-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)

rnc-Interface-List
A bit string containing zero or more of the following bits:
iu
(‘MAP_T_IU’ ‘0’)
iur
(‘MAP_T_IUR’ ‘1’)
iub
(‘MAP_T_IUB’ ‘2’)
uu
(‘MAP_T_UU’ ‘3’)

msc-s-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)

msc-s-Interface-List
A bit string containing zero or more of the following bits:
a
(‘MAP_T_A’ ‘0’)
iu
(‘MAP_T_IU’ ‘1’)
mc
(‘MAP_T_MC’ ‘2’)
map-g
(‘MAP_T_MAP_G’ ‘3’)
map-b
(‘MAP_T_MAP_B’ ‘4’)
map-e
(‘MAP_T_MAP_E’ ‘5’)
map-f
(‘MAP_T_MAP_F’ ‘6’)
cap
(‘MAP_T_CAP’ ‘7’)
map-d
(‘MAP_T_MAP_D’ ‘8’)
map-c
(‘MAP_T_MAP_C’ ‘9’)

msc-s-Event-List
A bit string containing zero or more of the following bits:
mo-mt-call
(‘MAP_T_MO_MT_CALL’ ‘0’)
mo-mt-sms
(‘MAP_T_MO_MT_SMS’ ‘1’)
lu-imsi-attach-imsi-detach
(‘MAP_T_LU_IMSI_ATTACH_IMSI_DETACH’ ‘2’)
handovers
(‘MAP_T_HANDOVERS’ ‘3’)
ss
(‘MAP_T_SS’ ‘4’)

mgw-Trace-Depth
An enumeration containing one of the following values:
minimum
(‘MAP_T_MINIMUM’ ‘0’)
medium
(‘MAP_T_MEDIUM’ ‘1’)
maximum
(‘MAP_T_MAXIMUM’ ‘2’)

mgw-Interface-List
A bit string containing zero or more of the following bits:
mc
(‘MAP_T_MC’ ‘0’)
nb-up
(‘MAP_T_NB_UP’ ‘1’)
iu-up
(‘MAP_T_IU_UP’ ‘2’)

mgw-Event-List
A bit string containing zero or more of the following bits:
context
(‘MAP_T_CONTEXT’ ‘0’)

extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3 GSM Call Handling Package

OM Hierarchy
  • Object
    • Service-Argument
      • GSM-Service-Argument
        • IST-Alert-Arg
        • IST-Command-Arg
        • Provide-Roaming-Number-Arg
        • Release-Resources-Arg
        • Remote-User-Free-Arg
        • Resume-Call-Handling-Arg
        • Send-Routing-Info-Arg
        • Set-Reporting-State-Arg
        • Status-Report-Arg
    • Service-Result
      • GSM-Service-Result
        • IST-Alert-Res
        • IST-Command-Res
        • Provide-Roaming-Number-Res
        • Release-Resources-Res
        • Remote-User-Free-Res
        • Resume-Call-Handling-Res
        • Send-Routing-Info-Res
        • Set-Reporting-State-Res
        • Status-Report-Res

5.4.3.1 Call-Report-Data

An instance of OM class Call-Report-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 339.

xmap_tab339.png

Table 339. OM Attributes of OM Class Call-Report-Data

This OM class contains the following class-specific OM attributes:

monitoring-Mode
An enumeration containing one of the following values:
a-side
(‘MAP_T_A_SIDE’ ‘0’)
b-side
(‘MAP_T_B_SIDE’ ‘1’)
Values ‘2’ to ‘10’ shall be mapped to ‘0’; values greater than ‘10’ mapped to ‘1’.
call-Outcome
An enumeration containing one of the following values:
success
(‘MAP_T_SUCCESS’ ‘0’)
failure
(‘MAP_T_FAILURE’ ‘1’)
busy
(‘MAP_T_BUSY’ ‘2’)
Values ‘3’ to ‘10’ shall be mapped to ‘0’; ‘11’ to ‘20’, ‘1’, and greater than ‘20’, ‘2’.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.2 Camel-Info

An instance of OM class Camel-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 331.

xmap_tab331.png

Table 331. OM Attributes of OM Class Camel-Info

This OM class contains the following class-specific OM attributes:

supported-Camel-Phases
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

suppress-T-CSI
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
offered-Camel4-CSIs
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

5.4.3.3 Camel-Routing-Info

An instance of OM class Camel-Routing-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 333.

xmap_tab333.png

Table 333. OM Attributes of OM Class Camel-Routing-Info

This OM class contains the following class-specific OM attributes:

forwarding-Data
This optional attribute is an instance of OM class Forwarding-Data. See Forwarding-Data.
gmsc-Camel-Subscription-Info
This attribute is an instance of OM class Gmsc-Camel-Subscription-Info. See Gmsc-Camel-Subscription-Info.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.4 CCBS-Indicators

An instance of OM class CCBS-Indicators represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 324.

xmap_tab324.png

Table 324. OM Attributes of OM Class CCBS-Indicators

This OM class contains the following class-specific OM attributes:

ccbs-Possible
A Null value whose presence provides indication.
keep-CCBS-Call-Indicator
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.5 CUG-Check-Info

An instance of OM class CUG-Check-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 321.

xmap_tab321.png

Table 321. OM Attributes of OM Class CUG-Check-Info

This OM class contains the following class-specific OM attributes:

cug-Interlock
CUG-Interlock ::= OCTET STRING (SIZE (4))
cug-Outgoing-Access
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.6 Event-Report-Data

An instance of OM class Event-Report-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 338.

xmap_tab338.png

Table 338. OM Attributes of OM Class Event-Report-Data

This OM class contains the following class-specific OM attributes:

ccbs-Subscriber-Status
An enumeration containing one of the following values:
ccbs-not-idle
(‘MAP_T_CCBS_NOT_IDLE’ ‘0’)
ccbs-idle
(‘MAP_T_CCBS_IDLE’ ‘1’)
ccbs-not-reachable
(‘MAP_T_CCBS_NOT_REACHABLE’ ‘2’)
Values of ‘3’ to ‘10’ shall be mapped to ‘0’; ‘11’ to ‘20’, mapped to ‘1’; values greater than ‘20’, to ‘2’.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.7 Extended-Routing-Info

An instance of OM class Extended-Routing-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 332.

xmap_tab332.png

Table 332. OM Attributes of OM Class Extended-Routing-Info

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

routing-Info
This choice attribute is an instance of OM class Routing-Info. See Routing-Info.
camel-Routing-Info
This choice attribute is an instance of OM class Camel-Routing-Info. See Camel-Routing-Info.

5.4.3.8 Forwarding-Data

An instance of OM class Forwarding-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 326.

xmap_tab326.png

Table 326. OM Attributes of OM Class Forwarding-Data

This OM class contains the following class-specific OM attributes:

forwarded-To-Number
An ISDN Address String. When this data type is sent from an HLR that supports CAMEL Phase 2 to a GMSC that supports CAMEL Phase 2 the GMSC shall not check the format of the number.
forwarded-To-Subaddress
An ISDN Subaddress String.
forwarding-Options
ForwardingOptions ::= OCTET STRING (SIZE (1)) Encoded as follows:
bit ‘8’ — notification to forwarding party

0no notification
1notification

bit ‘7’ — redirecting presentation

0no presentation
1presentation

bit ‘6’ — notification to calling party

0no notification
1notification

bit ‘5

0unused

bits ‘43’ — forwarding reason

00ms not reachable
01ms busy
10no reply
11unconditional when used in a SRI Result, or call deflection when used in a RCH Argument.

bits ‘21

00(unused)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-Forwarded-To-Number
FTN-AddressString ::= AddressString (SIZE(1..15)) This type is used to represent forwarded-to numbers. If NAI is “international”, the first digits represent the country code (CC) and the network destination code (NDC) as for E.164.

5.4.3.9 Gmsc-Camel-Subscription-Info

An instance of OM class Gmsc-Camel-Subscription-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 334.

xmap_tab334.png

Table 334. OM Attributes of OM Class Gmsc-Camel-Subscription-Info

This OM class contains the following class-specific OM attributes:

t-CSI
This optional attribute is an instance of OM class T-CSI. See T-CSI.
o-CSI
This optional attribute is an instance of OM class O-CSI. See O-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
o-Bcsm-Camel-TDP-Criteria-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Criteria-List. See O-Bcsm-Camel-TDP-Criteria-List.
t-BCSM-CAMEL-TDP-Criteria-List
This optional attribute is an instance of OM class T-BCSM-CAMEL-TDP-Criteria-List. See T-BCSM-CAMEL-TDP-Criteria-List.
d-CSI
This optional attribute is an instance of OM class D-CSI. See D-CSI.

5.4.3.10 IST-Alert-Arg

An instance of OM class IST-Alert-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 343.

xmap_tab343.png

Table 343. OM Attributes of OM Class IST-Alert-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.11 IST-Alert-Res

An instance of OM class IST-Alert-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 344.

xmap_tab344.png

Table 344. OM Attributes of OM Class IST-Alert-Res

This OM class contains the following class-specific OM attributes:

ist-Alert-Timer
IST-AlertTimerValue ::= INTEGER(15..255)
ist-Information-Withdraw
A Null value whose presence provides indication.
call-Termination-Indicator
An enumeration containing one of the following values:
terminate-call-activity-referred
(‘MAP_T_TERMINATE_CALL_ACTIVITY_REFERRED’ ‘0’)
terminate-all-call-activities
(‘MAP_T_TERMINATE_ALL_CALL_ACTIVITIES’ ‘1’)
Values ‘2’ to ‘10’ are mapped to ‘0’; greater than ‘10’, ‘1’. In MSCs not supporting linkage of all call activities, any value received shall be interpreted as terminate-call-activity-referered.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.12 IST-Command-Arg

An instance of OM class IST-Command-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 345.

xmap_tab345.png

Table 345. OM Attributes of OM Class IST-Command-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.13 IST-Command-Res

An instance of OM class IST-Command-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 346.

xmap_tab346.png

Table 346. OM Attributes of OM Class IST-Command-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.14 Provide-Roaming-Number-Arg

An instance of OM class Provide-Roaming-Number-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 327.

xmap_tab327.png

Table 327. OM Attributes of OM Class Provide-Roaming-Number-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msc-Number
This attribute refers to the ISDN number of an MSC. An ISDN Address String containing the number of the MSC.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string.
gsm-Bearer-Capability
This optional attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
network-Signal-Info
This optional attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
suppression-Of-Announcement
A Null value whose presence provides indication.
gmsc-Address
An ISDN Address String.
call-Reference-Number
CallReferenceNumber ::= OCTET STRING (SIZE(1..8))
or-Interrogation
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
ccbs-Call
A Null value whose presence provides indication.
supported-Camel-Phases-In-Interrogating-Node
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

additional-Signal-Info
This optional attribute is an instance of OM class Ext-External-Signal-Info. See Ext-External-Signal-Info.
or-Not-Supported-In-GMSC
A Null value whose presence provides indication.
pre-Paging-Supported
A Null value whose presence provides indication.
long-FTN-Supported
A Null value whose presence provides indication.
suppress-VT-CSI
A Null value whose presence provides indication.
offered-Camel4-CSIs-In-Interrogating-Node
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

mt-Roaming-Retry-Supported
A Null value whose presence provides indication.
paging-Area
This optional attribute is an instance of OM class Paging-Area. See Paging-Area.
call-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.

5.4.3.15 Provide-Roaming-Number-Res

An instance of OM class Provide-Roaming-Number-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 328.

xmap_tab328.png

Table 328. OM Attributes of OM Class Provide-Roaming-Number-Res

This OM class contains the following class-specific OM attributes:

roaming-Number
An ISDN address string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
release-Resources-Supported
A Null value whose presence provides indication.

5.4.3.16 Release-Resources-Arg

An instance of OM class Release-Resources-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 347.

xmap_tab347.png

Table 347. OM Attributes of OM Class Release-Resources-Arg

This OM class contains the following class-specific OM attributes:

msrn
An ISDN address string.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.17 Release-Resources-Res

An instance of OM class Release-Resources-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 348.

xmap_tab348.png

Table 348. OM Attributes of OM Class Release-Resources-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.18 Remote-User-Free-Arg

An instance of OM class Remote-User-Free-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 341.

xmap_tab341.png

Table 341. OM Attributes of OM Class Remote-User-Free-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
call-Info
This attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
ccbs-Feature
This attribute is an instance of OM class CCBS-Feature. See CCBS-Feature.
translated-B-Number
An ISDN address stirng.
replace-B-Number
A Null value whose presence provides indication.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.19 Remote-User-Free-Res

An instance of OM class Remote-User-Free-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 342.

xmap_tab342.png

Table 342. OM Attributes of OM Class Remote-User-Free-Res

This OM class contains the following class-specific OM attributes:

ruf-Outcome
An enumeration containing one of the following values:
accepted
(‘MAP_T_ACCEPTED’ ‘0’)
rejected
(‘MAP_T_REJECTED’ ‘1’)
no-reponse-from-free-ms
(‘MAP_T_NO_RESPONSE_FROM_FREE_MS’ ‘2’)
no-reponse-from-busy-ms
(‘MAP_T_NO_RESPONSE_FROM_BUSY_MS’ ‘3’)
udub-from-free-ms
(‘MAP_T_UDUB_FROM_FREE_MS’ ‘4’)
udub-from-busy-ms
(‘MAP_T_UDUB_FROM_BUSY_MS’ ‘5’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.20 Resume-Call-Handling-Arg

An instance of OM class Resume-Call-Handling-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 425.

xmap_tab425.png

Table 425. OM Attributes of OM Class Resume-Call-Handling-Arg

This OM class contains the following class-specific OM attributes:

call-Reference-Number
CallReferenceNumber ::= OCTET STRING (SIZE(1..8))
basic-Service-Group
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
forwarding-Data
This optional attribute is an instance of OM class Forwarding-Data. See Forwarding-Data.
imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
cug-Check-Info
This optional attribute is an instance of OM class CUG-Check-Info. See CUG-Check-Info.
o-CSI
This optional attribute is an instance of OM class O-CSI. See O-CSI.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
ccbs-Possible
A Null value whose presence provides indication.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
uu-Data
This optional attribute is an instance of OM class UU-Data. See UU-Data.
all-Information-Sent
A Null value whose presence provides indication.
extension
This optional attribute is an instance of OM class Extension. See Extension.
d-CSI
This optional attribute is an instance of OM class D-CSI. See D-CSI.
o-Bcsm-Camel-TDP-Criteria-List
This optional attribute is an instance of OM class O-Bcsm-Camel-TDP-Criteria-List. See O-Bcsm-Camel-TDP-Criteria-List.
basic-Service-Group-2
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
mt-Roaming-Retry
A Null value whose presence provides indication.

5.4.3.21 Resume-Call-Handling-Res

An instance of OM class Resume-Call-Handling-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 330.

xmap_tab330.png

Table 330. OM Attributes of OM Class Resume-Call-Handling-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.22 Routing-Info

An instance of OM class Routing-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 325.

xmap_tab325.png

Table 325. OM Attributes of OM Class Routing-Info

This OM class represents a choice and exactly one instance of one attribute shall be present in an instances of this OM class.

This OM class contains the following class-specific OM attributes:

roaming-Number
An ISDN Address String.
forwarding-Data
This choice attribute is an instance of OM class Forwarding-Data. See Forwarding-Data.

5.4.3.23 Send-Routing-Info-Arg

An instance of OM class Send-Routing-Info-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 322.

xmap_tab322.png

Table 322. OM Attributes of OM Class Send-Routing-Info-Arg

This OM class contains the following class-specific OM attributes:

msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
cug-Check-Info
This optional attribute is an instance of OM class CUG-Check-Info. See CUG-Check-Info.
number-Of-Forwarding
NumberOfForwarding ::= INTEGER (1..5)
interrogation-Type
An enumeration containing one of the following values:
basic-call
(‘MAP_T_BASIC_CALL’ ‘0’)
forwarding
(‘MAP_T_FORWARDING’ ‘2’)

or-Interrogation
A Null value whose presence provides indication.
or-Capability
OR-Phase ::= INTEGER(1..127)
gmsc-Or-gsmSCF-Address
An ISDN Address String.
call-Reference-Number
CallReferenceNumber ::= OCTET STRING (SIZE(1..8))
forwarding-Reason
An enumeration containing one of the following values:
not-reachable
(‘MAP_T_NOT_REACHABLE’ ‘0’)
busy
(‘MAP_T_BUSY’ ‘1’)
no-reply
(‘MAP_T_NO_REPLY’ ‘2’)

basic-Service-Group
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
network-Signal-Info
This optional attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
camel-Info
This optional attribute is an instance of OM class Camel-Info. See Camel-Info.
suppression-Of-Announcement
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
ccbs-Call
A Null value whose presence provides indication.
supported-CCBS-Phase
SupportedCCBS-Phase ::= INTEGER(1..127)
additional-Signal-Info
This optional attribute is an instance of OM class Ext-External-Signal-Info. See Ext-External-Signal-Info.
ist-Support-Indicator
An enumeration containing one of the following values:
basic-ist-supported
(‘MAP_T_BASIC_IST_SUPPORTED’ ‘0’)
ist-command-supported
(‘MAP_T_IST_COMMAND_SUPPORTED’ ‘1’)
Values greater than 1 shall be mapped to 1.
pre-Paging-Supported
A Null value whose presence provides indication.
call-Diversion-Treatment-Indicator
CallDiversionTreatmentIndicator ::= OCTET STRING (SIZE(1)) call diversion allowed: xxxx xx01; call diversion not allowed xxxx xx10; network default is call diversion allowed.
long-FTN-Supported
A Null value whose presence provides indication.
suppress-VT-CSI
A Null value whose presence provides indication.
suppress-Incoming-Call-Barring
A Null value whose presence provides indication.
gsmSCF-Initiated-Call
A Null value whose presence provides indication.
basic-Service-Group-2
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
network-Signal-Info-2
This optional attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
suppress-MT-SS
An enumeration containing one of the following values:
suppress-cug
(‘MAP_T_SUPPRESS_CUG’ ‘0’)
suppress-ccbs
(‘MAP_T_SUPPRESS_CCBS’ ‘1’)

mt-Roaming-Retry-Supported
A Null value whose presence provides indication.
call-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.

5.4.3.24 Send-Routing-Info-Res

An instance of OM class Send-Routing-Info-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 323.

xmap_tab323.png

Table 323. OM Attributes of OM Class Send-Routing-Info-Res

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.

IMSI must be present if the request is not segmented. If the result is segmented (TC-Result-NL), the IMSI must be present in one segmented transmission.

extended-Routing-Info
This optional attribute is an instance of OM class Extended-Routing-Info. See Extended-Routing-Info.
cug-Check-Info
This optional attribute is an instance of OM class CUG-Check-Info. See CUG-Check-Info.
cug-Subscription-Flag
A Null value whose presence provides indication.
subscriber-Info
This optional attribute is an instance of OM class Subscriber-Info. See Subscriber-Info.
ss-List
This optional attribute is an instance of OM class SS-List. See SS-List.
basic-Service
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
forwarding-Interrogation-Required
A Null value whose presence provides indication.
vmsc-Address
An ISDN Address String.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
naea-Preferred-CI
This optional attribute is an instance of OM class NAEA-Preferred-CI. See NAEA-Preferred-CI.
ccbs-Indicators
This optional attribute is an instance of OM class CCBS-Indicators. See CCBS-Indicators.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
number-Portability-Status
An enumeration containing one of the following values:
not-known-to-be-ported
(‘MAP_T_NOT_KNOWN_TO_BE_PORTED’ ‘0’)
own-number-ported-out
(‘MAP_T_OWN_NUMBER_PORTED_OUT’ ‘1’)
foreign-number-ported-to-foreign-network
(‘MAP_T_FOREIGN_NUMBER_PORTED_TO_FOREIGN_NETWORK’ ‘2’)
own-number-not-ported-out
(‘MAP_T_OWN_NUMBER_NOT_PORTED_OUT’ ‘4’)
foreign-number-ported-in
(‘MAP_T_FOREIGN_NUMBER_PORTED_IN’ ‘5’)

ist-Alert-Timer
IST-AlertTimerValue ::= INTEGER (15..255)
supported-Camel-Phases-In-VMSC
A bit string containing zero or more of the following bits:
phase-1
(‘MAP_T_PHASE_1’ ‘0’)
phase-2
(‘MAP_T_PHASE_2’ ‘1’)
phase-3
(‘MAP_T_PHASE_3’ ‘2’)
phase-4
(‘MAP_T_PHASE_4’ ‘3’)

offered-Camel4-CSIs-In-VMSC
A bit string containing zero or more of the following bits:
o-csi
(‘MAP_T_O_CSI’ ‘0’)
d-csi
(‘MAP_T_D_CSI’ ‘1’)
vt-csi
(‘MAP_T_VT_CSI’ ‘2’)
t-csi
(‘MAP_T_T_CSI’ ‘3’)
mt-sms-csi
(‘MAP_T_MT_SMS_CSI’ ‘4’)
mg-csi
(‘MAP_T_MG_CSI’ ‘5’)
psi-enhancements
(‘MAP_T_PSI_ENHANCEMENTS’ ‘6’)

routing-Info-2
This optional attribute is an instance of OM class Routing-Info. See Routing-Info.
ss-List-2
This optional attribute is an instance of OM class SS-List. See SS-List.
basic-Service-2
This optional attribute is an instance of OM class Ext-Basic-Service-Code. See Ext-Basic-Service-Code.
allowed-Services
A bit string containing zero or more of the following bits:
first-service-allowed
(‘MAP_T_FIRST_SERVICE_ALLOWED’ ‘0’)
second-service-allowed
(‘MAP_T_SECOND_SERVICE_ALLOWED’ ‘1’)

unavailability-Cause
An enumeration containing one of the following values:
bearer-service-not-provisioned
(‘MAP_T_BEARER_SERVICE_NOT_PROVISIONED’ ‘1’)
teleservice-not-provisioned
(‘MAP_T_TELESERVICE_NOT_PROVISIONED’ ‘2’)
absent-subscriber
(‘MAP_T_ABSENT_SUBSCRIBER’ ‘3’)
busy-subscriber
(‘MAP_T_BUSY_SUBSCRIBER’ ‘4’)
call-barred
(‘MAP_T_CALL_BARRED’ ‘5’)
cug-reject
(‘MAP_T_CUG_REJECT’ ‘6’)

release-Resources-Supported
A Null value whose presence provides indication.
gsm-Bearer-Capability
This optional attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.

5.4.3.25 Set-Reporting-State-Arg

An instance of OM class Resume-Call-Handling-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 335.

xmap_tab335.png

Table 335. OM Attributes of OM Class Set-Reporting-State-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
lmsi
This attribute provides the local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. The LMSI shall not be sent to an SGSN. This attribute is encoded as a 4 octet string.
ccbs-Monitoring
An enumeration containing one of the following values:
stop-monitoring
(‘MAP_T_STOP_MONITORING’ ‘0’)
start-monitoring
(‘MAP_T_START_MONITORING’ ‘1’)
Values from ‘2’ to ‘10’ shall be mapped to ‘0’. Values greater than ‘10’ sahll be mapped to ‘1’.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.26 Set-Reporting-State-Res

An instance of OM class Set-Reporting-State-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 336.

xmap_tab336.png

Table 336. OM Attributes of OM Class Set-Reporting-State-Res

This OM class contains the following class-specific OM attributes:

ccbs-Subscriber-Status
An enumeration containing one of the following values:
ccbs-not-idle
(‘MAP_T_CCBS_NOT_IDLE’ ‘0’)
ccbs-idle
(‘MAP_T_CCBS_IDLE’ ‘1’)
ccbs-not-reachable
(‘MAP_T_CCBS_NOT_REACHABLE’ ‘2’)
Values of ‘3’ to ‘10’ shall be mapped to ‘0’; ‘11’ to ‘20’, mapped to ‘1’; values greater than ‘20’, to ‘2’.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.27 Status-Report-Arg

An instance of OM class Status-Report-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 337.

xmap_tab337.png

Table 337. OM Attributes of OM Class Status-Report-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
event-Report-Data
This optional attribute is an instance of OM class Event-Report-Data. See Event-Report-Data.
call-Report-Data
This optional attribute is an instance of OM class Call-Report-Data. See Call-Report-Data.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.28 Status-Report-Res

An instance of OM class Status-Report-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 340.

xmap_tab340.png

Table 340. OM Attributes of OM Class Status-Report-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.3.29 UU-Data

An instance of OM class UU-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 329.

xmap_tab329.png

Table 329. OM Attributes of OM Class UU-Data

This OM class contains the following class-specific OM attributes:

uu-Indicator
UUIndicator ::= OCTET STRING (SIZE(1)) Octets are coded according to ETS 300 356.
uui
UUI ::= OCTET STRING (SIZE(1..131)) Octets are coded accoridng to ETS 300 356.
uusCF-Interaction
A Null value whose presence provides indication.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4 GSM Supplementary Service Package

OM Hierarchy
  • Object
    • Service-Argument
      • GSM-Service-Argument
        • Activate-SS-Arg
        • Deactivate-SS-Arg
        • Erase-CC-Entry-Arg
        • Erase-SS-Arg
        • Get-Password-Arg
        • Interrogate-SS-Arg
        • Notify-USSD-Arg
        • Process-USSD-Arg
        • Register-CC-Entry-Arg
        • Register-Password-Arg
        • Register-SS-Arg
        • SS-Invocation-Notification-Arg
        • USSD-Arg
    • Service-Result
      • GSM-Service-Result
        • Activate-SS-Res
        • Deactivate-SS-Res
        • Erase-CC-Entry-Res
        • Erase-SS-Res
        • Get-Password-Res
        • Interrogate-SS-Res
        • Notify-USSD-Res
        • Process-USSD-Res
        • Register-CC-Entry-Res
        • Register-Password-Res
        • Register-SS-Res
        • SS-Invocation-Notification-Res
        • USSD-Res

5.4.4.1 Activate-SS-Arg

An instance of OM class Activate-SS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 430.

xmap_tab430.png

Table 430. OM Attributes of OM Class Activate-SS-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-FTN-Supported
A Null value whose presence provides indication.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

This OM class encodes the same as USSD-Arg.

5.4.4.2 Activate-SS-Res

An instance of OM class Activate-SS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 431.

xmap_tab431.png

Table 431. OM Attributes of OM Class Activate-SS-Res

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Forwarding-Info. See Forwarding-Info.
call-Barring-Info
This choice attribute is an instance of OM class Call-Barring-Info. See Call-Barring-Info.
ss-Data
This choice attribute is an instance of OM class SS-Data. See SS-Data.

This service result is optional.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

This OM class encodes the same as USSD-Res.

5.4.4.3 Basic-Service-Group-List

An instance of OM class Basic-Service-Group-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 367.

xmap_tab367.png

Table 367. OM Attributes of OM Class Basic-Service-Group-List

This OM class contains the following class-specific OM attributes:

basic-Service-Code
One to thirteen (maxNumOfBasicServiceGroups) instances of OM class Basic-Service-Code. See Basic-Service-Code.

5.4.4.4 Call-Barring-Feature

An instance of OM class Call-Barring-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 356.

xmap_tab356.png

Table 356. OM Attributes of OM Class Call-Barring-Feature

This OM class contains the following class-specific OM attributes:

basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.5 Call-Barring-Feature-List

An instance of OM class Call-Barring-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 355.

xmap_tab355.png

Table 355. OM Attributes of OM Class Call-Barring-Feature-List

This OM class contains the following class-specific OM attributes:

call-Barring-Feature
One to thirteen (maxNumOfBasicServiceGroups) instances of OM class Call-Barring-Feature. See Call-Barring-Feature.

5.4.4.6 Call-Barring-Info

An instance of OM class Call-Barring-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 354.

xmap_tab354.png

Table 354. OM Attributes of OM Class Call-Barring-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
call-Barring-Feature-List
This attribute is an instance of OM class Call-Barring-Feature-List. See Call-Barring-Feature-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.7 CCBS-Data

An instance of OM class CCBS-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 372.

xmap_tab372.png

Table 372. OM Attributes of OM Class CCBS-Data

This OM class contains the following class-specific OM attributes:

ccbs-Feature
This attribute is an instance of OM class CCBS-Feature. See CCBS-Feature.
translated-B-Number
An ISDN address string.
service-Indicator
An enumeration containing one of the following values:
clir-invoked
(‘MAP_T_CLIR_INVOKED’ ‘0’)
camel-invoked
(‘MAP_T_CAMEL_INVOKED’ ‘1’)

call-Info
This attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
network-Signal-Info
This attribute is an instance of OM class External-Signal-Info. See External-Signal-Info.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.8 CCBS-Feature

An instance of OM class CCBS-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 362.

xmap_tab362.png

Table 362. OM Attributes of OM Class CCBS-Feature

This OM class contains the following class-specific OM attributes:

ccbs-Index
CCBS-Index ::= INTEGER (1..5)
b-Subscriber-Number
An ISDN address string.
b-Subscriber-Subaddress
An ISDN subaddress string.
basic-Service-Group
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.9 CCBS-Feature-List

An instance of OM class CCBS-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 361.

xmap_tab361.png

Table 361. OM Attributes of OM Class CCBS-Feature-List

This OM class contains the following class-specific OM attributes:

ccbs-Feature
One to five (maxNumOfCCBS-Requests) instances of OM class CCBS-Feature. See CCBS-Feature.

5.4.4.10 Deactivate-SS-Arg

An instance of OM class Deactivate-SS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 432.

xmap_tab432.png

Table 432. OM Attributes of OM Class Deactivate-SS-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-FTN-Supported
A Null value whose presence provides indication.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

This OM class encodes the same as USSD-Arg.

5.4.4.11 Deactivate-SS-Res

An instance of OM class Deactivate-SS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 433.

xmap_tab433.png

Table 433. OM Attributes of OM Class Deactivate-SS-Res

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Forwarding-Info. See Forwarding-Info.
call-Barring-Info
This choice attribute is an instance of OM class Call-Barring-Info. See Call-Barring-Info.
ss-Data
This choice attribute is an instance of OM class SS-Data. See SS-Data.

This service result is optional.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

This OM class encodes the same as USSD-Res.

5.4.4.12 Erase-CC-Entry-Arg

An instance of OM class Erase-CC-Entry-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 374.

xmap_tab374.png

Table 374. OM Attributes of OM Class Erase-CC-Entry-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ccbs-Index
CCBS-Index ::= INTEGER (1..5)
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.13 Erase-CC-Entry-Res

An instance of OM class Erase-CC-Entry-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 375.

xmap_tab375.png

Table 375. OM Attributes of OM Class Erase-CC-Entry-Res

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.14 Erase-SS-Arg

An instance of OM class Erase-SS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 434.

xmap_tab434.png

Table 434. OM Attributes of OM Class Erase-SS-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-FTN-Supported
A Null value whose presence provides indication.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.15 Erase-SS-Res

An instance of OM class Erase-SS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 435.

xmap_tab435.png

Table 435. OM Attributes of OM Class Erase-SS-Res

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Forwarding-Info. See Forwarding-Info.
call-Barring-Info
This choice attribute is an instance of OM class Call-Barring-Info. See Call-Barring-Info.
ss-Data
This choice attribute is an instance of OM class SS-Data. See SS-Data.

This service result is optional.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.16 Forwarding-Feature

An instance of OM class Forwarding-Feature represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 353.

xmap_tab353.png

Table 353. OM Attributes of OM Class Forwarding-Feature

This OM class contains the following class-specific OM attributes:

basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
forwarded-To-Number
An ISDN address string.
forwarded-To-Subaddress
An ISDN subaddress string.
forwarding-Options
ForwardingOptions ::= OCTET STRING (SIZE(1))
no-Reply-Condition-Time
NoReplyConditionTime ::= INTEGER(5..30)
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-Forwarded-To-Number
FTN-AddressString ::= AddressString (SIZE(1..15)) This type is used to represent forwarded-to numbers. If NAI is “international”, the first digits represent the country code (CC) and the network destination code (NDC) as for E.164.

5.4.4.17 Forwarding-Feature-List

An instance of OM class Forwarding-Feature-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 352.

xmap_tab352.png

Table 352. OM Attributes of OM Class Forwarding-Feature-List

This OM class contains the following class-specific OM attributes:

forwarding-Feature
One to thirteen (maxNumOfBasicServiceGroups) instances of OM class Forwarding-Feature. See Forwarding-Feature.

5.4.4.18 Forwarding-Info

An instance of OM class Forwarding-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 351.

xmap_tab351.png

Table 351. OM Attributes of OM Class Forwarding-Info

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
forwarding-Feature-List
This optional attribute is an instance of OM class Forwarding-Feature-List. See Forwarding-Feature-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.19 Generic-Service-Info

An instance of OM class Generic-Service-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 360.

xmap_tab360.png

Table 360. OM Attributes of OM Class Generic-Service-Info

This OM class contains the following class-specific OM attributes:

ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
cli-Restriction-Option
An enumeration containing one of the following values:
permanent
(‘MAP_T_PERMANENT’ ‘0’)
temporary-default-restricted
(‘MAP_T_TEMPORARY_DEFAULT_RESTRICTED’ ‘1’)
temporary-default-allowed
(‘MAP_T_TEMPORARY_DEFAULT_ALLOWED’ ‘2’)

extension
This optional attribute is an instance of OM class Extension. See Extension.
maximum-Entitled-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
default-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
ccbs-Feature-List
This optional attribute is an instance of OM class CCBS-Feature-List. See CCBS-Feature-List.
nbr-SB
MaxMC-Bearers ::= INTEGER (2..7)
nbr-User
MC-Bearers ::= INTEGER(1..7)
nbr-SN
MC-Bearers ::= INTEGER(1..7)

5.4.4.20 Get-Password-Arg

An instance of OM class Get-Password-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 436.

xmap_tab436.png

Table 436. OM Attributes of OM Class Get-Password-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.21 Get-Password-Res

An instance of OM class Get-Password-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 437.

xmap_tab437.png

Table 437. OM Attributes of OM Class Get-Password-Res

This OM class contains the following class-specific OM attributes:

password
Password ::= NumericString (FROM (0|1|2|3|4|5|6|7|8|9)) (SIZE(4))

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.22 Interrogate-SS-Arg

An instance of OM class Interrogate-SS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 438.

xmap_tab438.png

Table 438. OM Attributes of OM Class Interrogate-SS-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-FTN-Supported
A Null value whose presence provides indication.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.23 Interrogate-SS-Res

An instance of OM class Interrogate-SS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 363.

xmap_tab363.png

Table 363. OM Attributes of OM Class Interrogate-SS-Res

This OM class contains the following class-specific OM attributes:

ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
basic-Service-Group-List
This attribute is an instance of OM class Basic-Service-Group-List. See Basic-Service-Group-List.
forwarding-Feature-List
This attribute is an instance of OM class Forwarding-Feature-List. See Forwarding-Feature-List.
generic-Service-Info
This attribute is an instance of OM class Generic-Service-Info. See Generic-Service-Info.

5.4.4.24 Notify-USSD-Arg

An instance of OM class Notify-USSD-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 439.

xmap_tab439.png

Table 439. OM Attributes of OM Class Notify-USSD-Arg

This OM class contains the following class-specific OM attributes:

ussd-Data-Coding-Scheme
USSD-DataCodingScheme ::= OCTET STRING (SIZE (1)) The structure of the USSD-DataCodingScheme is defined by the Cell Broadcast Data Scheme as described in 3GPP TS 23.038.
ussd-String
USSD-String ::= OCTET STRING (SIZE (1..160)) The structure of the contents of the USSD-String is dependent on the USSD-DataCodingScheme as described in 3GPP TS 23.038.
extension
This optional attribute is an instance of OM class Extension. See Extension.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.25 Notify-USSD-Res

An instance of OM class Notify-USSD-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 440.

xmap_tab440.png

Table 440. OM Attributes of OM Class Notify-USSD-Res

This OM class contains the following class-specific OM attributes:

ack (Boolean) ::= TRUE

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.26 Process-USSD-Arg

An instance of OM class Process-USSD-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 441.

xmap_tab441.png

Table 441. OM Attributes of OM Class Process-USSD-Arg

This OM class contains the following class-specific OM attributes:

ussd-Data-Coding-Scheme
USSD-DataCodingScheme ::= OCTET STRING (SIZE (1)) The structure of the USSD-DataCodingScheme is defined by the Cell Broadcast Data Scheme as described in 3GPP TS 23.038.
ussd-String
USSD-String ::= OCTET STRING (SIZE (1..160)) The structure of the contents of the USSD-String is dependent on the USSD-DataCodingScheme as described in 3GPP TS 23.038.
extension
This optional attribute is an instance of OM class Extension. See Extension.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.27 Process-USSD-Res

An instance of OM class Process-USSD-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 442.

xmap_tab442.png

Table 442. OM Attributes of OM Class Process-USSD-Res

This OM class contains the following class-specific OM attributes:

ussd-Data-Coding-Scheme
USSD-DataCodingScheme ::= OCTET STRING (SIZE(1)) The structure of the USSD-DataCodingScheme is defined by the Cell Broadcast Data Coding Scheme as described in 3GPP TS 23.038.
ussd-String
USSD-String ::= OCTET STRING(SIZE(1..160)) The structure of the contents of the USSD-String is dependent on the USSD-DataCodingScheme as described in 3GPP TS 23.038.
extension
This optional attribute is an instance of OM class Extension. See Extension.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.28 Register-CC-Entry-Arg

An instance of OM class Register-CC-Entry-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 371.

xmap_tab371.png

Table 371. OM Attributes of OM Class Register-CC-Entry-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ccbs-Data
This optional attribute is an instance of OM class CCBS-Data. See CCBS-Data.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.29 Register-CC-Entry-Res

An instance of OM class Register-CC-Entry-Res represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 373.

xmap_tab373.png

Table 373. OM Attributes of OM Class Register-CC-Entry-Res

This OM class contains the following class-specific OM attributes:

ccbs-Feature
This optional attribute is an instance of OM class CCBS-Feature. See CCBS-Feature.
extension
This optional attribute is an instance of OM class Extension. See Extension.

5.4.4.30 Register-Password-Arg

An instance of OM class Register-Password-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 443.

xmap_tab443.png

Table 443. OM Attributes of OM Class Register-Password-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.31 Register-Password-Res

An instance of OM class Register-Password-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 444.

xmap_tab444.png

Table 444. OM Attributes of OM Class Register-Password-Res

This OM class contains the following class-specific OM attributes:

password
Password ::= NumericString (FROM (0|1|2|3|4|5|6|7|8|9)) (SIZE(4))

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.32 Register-SS-Arg

An instance of OM class Register-SS-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 349.

xmap_tab349.png

Table 349. OM Attributes of OM Class Register-SS-Arg

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
forwarded-To-Number
An address string.
forwarded-To-Subaddress
An ISDN subaddress string.
no-Reply-Condition-Time
NoReplyConditionTime ::= INTEGER(5..30)
extension
This optional attribute is an instance of OM class Extension. See Extension.
default-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
nbr-User
MC-Bearers ::= INTEGER(1..7)
long-FTN-Supported
A Null value whose presence provides indication.

5.4.4.33 Register-SS-Res

An instance of OM class Register-SS-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 445.

xmap_tab445.png

Table 445. OM Attributes of OM Class Register-SS-Res

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Forwarding-Info. See Forwarding-Info.
call-Barring-Info
This choice attribute is an instance of OM class Call-Barring-Info. See Call-Barring-Info.
ss-Data
This choice attribute is an instance of OM class SS-Data. See SS-Data.

This service result is optional.

This OM class does not directly correspond to an ASN.1 type in TS 29.002.

5.4.4.34 SS-Data

An instance of OM class SS-Data represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 357.

xmap_tab357.png

Table 357. OM Attributes of OM Class SS-Data

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
ss-Status
SS-Status ::= OCTET STRING (SIZE(1)) This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011. SS-Status is a one byte octet string where bits 8765 are unused and coded zero. Bit 4 is the “Q bit”; 3, the “P bit”, 2 the “R bit”, 1, “A bit”. These bits are defined in 3GPP TS 23.011.
ss-Subscription-Option
This optional attribute is an instance of OM class SS-Subscription-Option. See SS-Subscription-Option.
basic-Service-Group-List
This optional attribute is an instance of OM class Basic-Service-Group-List. See Basic-Service-Group-List.
extension
This optional attribute is an instance of OM class Extension. See Extension.
default-Priority
EMLPP-Priority ::= INTEGER(0..15). The mapping from the values, A, B, 0, 1, 2, 3, 4 to the integer value is specified as follows where A is the highest and 4 is the lowest priority level. The integer values 7-15 are speare and shall be mapped to value 4.
nbr-User
MC-Bearers ::= INTEGER(1..7)

5.4.4.35 SS-Event-Specification

An instance of OM class SS-Event-Specification represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 370.

xmap_tab370.png

Table 370. OM Attributes of OM Class SS-Event-Specification

This OM class contains the following class-specific OM attributes:

ss-Event-Spec
One to two (maxEventSpecification) instances of AddressString.

5.4.4.36 SS-For-BS-Code

An instance of OM class SS-For-BS-Code represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 359.

xmap_tab359.png

Table 359. OM Attributes of OM Class SS-For-BS-Code

This OM class contains the following class-specific OM attributes:

ss-Code
SS-Code ::= OCTET STRING (SIZE(1))
basic-Service
This optional attribute is an instance of OM class Basic-Service-Code. See Basic-Service-Code.
extension
This optional attribute is an instance of OM class Extension. See Extension.
long-FTN-Supported
A Null value whose presence provides indication.

5.4.4.37 SS-Info

An instance of OM class SS-Info represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 350.

xmap_tab350.png

Table 350. OM Attributes of OM Class SS-Info

This OM class represents a choice and exactly one instance of one attribute shall be present in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

forwarding-Info
This choice attribute is an instance of OM class Forwarding-Info. See Forwarding-Info.
call-Barring-Info
This choice attribute is an instance of OM class Call-Barring-Info. See Call-Barring-Info.
ss-Data
This choice attribute is an instance of OM class SS-Data. See SS-Data.

5.4.4.38 SS-Invocation-Notification-Arg

An instance of OM class SS-Invocation-Notification-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 368.

xmap_tab368.png

Table 368. OM Attributes of OM Class SS-Invocation-Notification-Arg

This OM class contains the following class-specific OM attributes:

imsi
This attribute represents the International Mobile Subscriber Identity defined in 3GPP TS 23.003. The syntax of this attribute is an octet string containing a TBCD string (see String(TBCD)) between 3 and 8 octets (5 and 16 digits) in length, inclusive. Digits of MCC, MNC and MSIN are concatenated in the listed order.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).
ss-Event
SS-Code ::= OCTET STRING (SIZE(1)) The following SS-Code values are allowed: ect, '00110001'B, multi-pty, '01010001'B, cd, '00100100'B, ccbs, '01000100'B.
ss-Event-Specification
This optional attribute is an instance of OM class SS-Event-Specification. See SS-Event-Specification.
extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
b-Subscriber-Number
An ISDN address string.
ccbs-Request-State
An enumeration containing one of the following values:
request
(‘MAP_T_REQUEST’ ‘0’)
recall
(‘MAP_T_RECALL’ ‘1’)
active
(‘MAP_T_ACTIVE’ ‘2’)
completed
(‘MAP_T_COMPLETED’ ‘3’)
suspended
(‘MAP_T_SUSPENDED’ ‘4’)
frozen
(‘MAP_T_FROZEN’ ‘5’)
deleted
(‘MAP_T_DELETED’ ‘6’)

5.4.4.39 SS-Invocation-Notification-Res

An instance of OM class SS-Invocation-Notification-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 369.

xmap_tab369.png

Table 369. OM Attributes of OM Class SS-Invocation-Notification-Res

This OM class contains the following class-specific OM attributes:

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.

This service result is optional.

5.4.4.40 SS-List

An instance of OM class SS-List represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 366.

xmap_tab366.png

Table 366. OM Attributes of OM Class SS-List

This OM class contains the following class-specific OM attributes:

ss-Code
One to thirty (maxNumOfSS) instances of SS-Code. SS-Code ::= OCTET STRING (SIZE(1))

5.4.4.41 SS-Subscription-Option

An instance of OM class SS-Subscription-Option represents the corresponding GSM MAP information object.

An instance of this OM class has the OM attributes of it superclasses, Object, and additionally the OM attributes listed in Table 358.

xmap_tab358.png

Table 358. OM Attributes of OM Class SS-Subscription-Option

This OM class represents a choice and exactly one instance of one attribute shall exists in an instance of this OM class.

This OM class contains the following class-specific OM attributes:

cli-Restriction-Option
An enumeration containing one of the following values:
permanent
(‘MAP_T_PERMANENT’ ‘0’)
temporary-default-restricted
(‘MAP_T_TEMPORARY_DEFAULT_RESTRICTED’ ‘1’)
temporary-default-allowed
(‘MAP_T_TEMPORARY_DEFAULT_ALLOWED’ ‘2’)

override-Category
An enumeration containing one of the following values:
override-enabled
(‘MAP_T_OVERRIDE_ENABLED’ ‘0’)
override-disabled
(‘MAP_T_OVERRIDE_DISABLED’ ‘1’)

5.4.4.42 USSD-Arg

An instance of OM class USSD-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 364.

xmap_tab364.png

Table 364. OM Attributes of OM Class USSD-Arg

This OM class contains the following class-specific OM attributes:

ussd-Data-Coding-Scheme
USSD-DataCodingScheme ::= OCTET STRING (SIZE (1)) The structure of the USSD-DataCodingScheme is defined by the Cell Broadcast Data Scheme as described in 3GPP TS 23.038.
ussd-String
USSD-String ::= OCTET STRING (SIZE (1..160)) The structure of the contents of the USSD-String is dependent on the USSD-DataCodingScheme as described in 3GPP TS 23.038.
extension
This optional attribute is an instance of OM class Extension. See Extension.
alerting-Pattern
AlertingPattern ::= OCTET STRING (SIZE (1)) This type is used to represent alerting patterns: bits 8765, ‘0000’ (unused), bits 43, ‘00’, level; ‘01’, category; ‘10’, category; ‘11’, reserved; bits 21, type of alerting.
alterting-level-0
(‘MAP_T_ALERTING_LEVEL_0'00000000'B)
alterting-level-1
(‘MAP_T_ALERTING_LEVEL_1'00000001'B)
alterting-level-2
(‘MAP_T_ALERTING_LEVEL_2'00000010'B)
alterting-category-1
(‘MAP_T_ALERTING_CATEGORY_1'00000100'B)
alterting-category-2
(‘MAP_T_ALERTING_CATEGORY_2'00000101'B)
alterting-category-3
(‘MAP_T_ALERTING_CATEGORY_3'00000110'B)
alterting-category-4
(‘MAP_T_ALERTING_CATEGORY_4'00000111'B)
alterting-category-5
(‘MAP_T_ALERTING_CATEGORY_5'00001000'B)
All other values are reserved. Alerting levels and categories are defined in GSM 02.07.
msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute has syntax String(Address). See String(Address).

5.4.4.43 USSD-Res

An instance of OM class USSD-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result, and additionally the OM attributes listed in Table 365.

xmap_tab365.png

Table 365. OM Attributes of OM Class UUSD-Res

This OM class contains the following class-specific OM attributes:

ussd-Data-Coding-Scheme
USSD-DataCodingScheme ::= OCTET STRING (SIZE(1)) The structure of the USSD-DataCodingScheme is defined by the Cell Broadcast Data Coding Scheme as described in 3GPP TS 23.038.
ussd-String
USSD-String ::= OCTET STRING(SIZE(1..160)) The structure of the contents of the USSD-String is dependent on the USSD-DataCodingScheme as described in 3GPP TS 23.038.
extension
This optional attribute is an instance of OM class Extension. See Extension.

This service result is optional.

5.4.5 GSM Short Message Service Package

  • Object
    • Service-Argument
      • GSM-Service-Argument
        • Alert-Service-Centre-Arg
        • Inform-Service-Centre-Arg
        • MO-Forward-SM-Arg
        • MT-Forward-SM-Arg
        • MT-Forward-SM-VGCS-Arg
        • Ready-For-SM-Arg
        • Report-SM-Delivery-Status-Arg
        • Send-Info-For-Mo-Sms-Argument
        • Send-Info-For-Mt-Sms-Argument
        • Routing-Info-For-SM-Arg
    • Service-Result
      • GSM-Service-Result
        • Alert-Service-Centre-Res
        • MO-Forward-SM-Res
        • MT-Forward-SM-Res
        • MT-Forward-SM-VGCS-Res
        • Ready-For-SM-Res
        • Report-SM-Delivery-Status-Res
        • Send-Info-For-Mo-Sms-Result
        • Send-Info-For-Mt-Sms-Result
        • Routing-Info-For-SM-Res

5.4.5.1 Additional-Number

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 34. This class represents a choice and exactly one of the attributes must be present in an instance of the object.

xmap_tab034.png

Table 34. OM Attributes of OM class Additional-Number

This OM class contains the following class-specific OM attributes:

msc-Number
This attribute refers to the ISDN number of an MSC. An ISDN Address String containing the number of the MSC.
sgsn-Number
This attribute refers to the ISDN number of an SGSN. An ISDN Address String containing the ISDN address of the SGSN.

5.4.5.2 Alert-Service-Centre-Arg

An instance of OM class Alert-Service-Centre-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 8.

xmap_tab008.png

Table 8. OM Attributes of OM class Alert-Service-Centre-Arg

This OM class contains the following class-specific OM attributes:

msisdn
This attribute refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service Centre when the MS is again attainable. This attribute has syntax String(Address). See String(Address).
service-Centre-Address
This attribute represents the address of a Short Message Service Centre. This attribute has syntax String(Address). See String(Address).

5.4.5.3 Alert-Service-Centre-Res

An instance of OM class Alert-Service-Centre-Res represents the information of a mobile application service operation response supplied as the Response argument to the Service-rsp() function (see Service-rsp) or is returned in the Result-Or-Argument result by the Receive() function (see Receive) for a mobile application service operation confirmation.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Result, GSM-Service-Result; it doest not provide any attributes of its own.

5.4.5.4 Dispatcher-List

An instance of OM class Dispatcher-List represents a list of one to five ISDN dispatch addresses.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionaly the OM attributes listed in Table 118.

xmap_tab118.png

Table 118. OM Attributes of OM class Dispatcher-List

dispatcher
One to five ISDN address strings.

5.4.5.5 Inform-Service-Centre-Arg

An instance of OM class Inform-Service-Centre-Arg represents the information of a mobile application service operation request supplied as an argument to the Service-req() function (see Service-req) or is returned by the Receive() function (see Receive) for a mobile application service operation indication.

An instance of this OM class has the OM attributes of it superclasses, Object, Service-Argument, GSM-Service-Argument, and additionally the OM attributes listed in Table 9.

xmap_tab009.png

Table 9. OM Attributes of OM class Inform-Service-Centre-Arg

This OM class contains the following class-specific OM attributes:

msisdn
An MS-ISDN refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with ITU-T Recommendation E.213. This attribute refers to the MS-ISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service Centre when the MS is again attainable. This attribute has syntax String(Address). See String(Address).
mw-Status
This attribute indicates whether or not the address of the originator service centre is already contained in the Message Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flat (MCEF), the status of the Mobile Subscriber Not Reachable Flag (MNRF) and the status of the Mobile station Not Reachable for GPRS flag (MNRG).

mw-Status is a bit string with 6 to 16 bits with the following bits defined:

sc-Address-Not-Included
(‘MAP_T_SC_ADDRESS_NOT_INCLUDED’ ‘0’)
mnrf-Set
(‘MAP_T_MNRF_SET’ ‘1’)
mcef-Set
(‘MAP_T_MCEF_SET’ ‘2’)
mnrg-Set
(‘MAP_T_MNRG_SET’ ‘3’)

extension-Container
This optional attribute is an instance of OM class Extension-Container. See Extension-Container.
extension
This optional attribute is an instance of OM class Extension. See Extension.
absent-Subscriber-Diagnostic-SM
This optional attribute is used to indicate the reason why the subscribe is absent. For the values for this attribute, see 3GPP TS 23.040.
additional-Absent-Subscriber-Diagnostic-SM
This optional attribute indicates the reason of the additional SM Delivery Outcome. additional-Absent-Subscriber-Diagnostic-SM may be present only if absent-Subscriber-Diagnostic-SM is present. If included, additional-Absent-Subscriber-Diagnostic-SM is for GPRS and absent-Subscriber-Diagnostic-SM is for non-GPRS.

5.4.5.6 Location-Info-With-LMSI

An instance of OM class Location-Info-With-LMSI contains information returned as a result in a object of OM class Routing-Info-For-SM-Res.43 It contains information as to where to route a relayed short message.

An instance of this OM class has the OM attributes of its superclasses, Object, and additionally the OM attributes listed in Table 33.

xmap_tab033.png

Table 33. OM Attributes of OM class Location-Info-With-LMSI

This OM class contains the following class-specific OM attributes:

network-Node-Number
This attribute provides a network node number coded as an octet string containing one to sixteen TBCD encoded digits. This attribute has syntax