Operations Support Systems (OSS) through Java Initiative

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

This interface contains definitions for trend indication types for
 observed conditions. It's possible to indicate if some observed
 condition is getting better, worse, or not changing.

This interface contains definions for probable causes that are used in
 reported alarms.

This interface represents the payload of the event that is sent when
 the API server changes the severity of an alarm in the alarm list.
 See package desciption for information on how NotifyChangedAlarmEvent
 events are used.

This interface defines the content of an event signaling that the list
 of Alarm has been rebuilt.

This interface represents the payload of an event that is sent when
 a comment is associated to an alarm in the API server's alarm list.
 See package desciption for information on how NotifyNewAlarmEvent
 events are used.

This interface defines the content of an event signaling a change in the
 ackState for an Alarm.

This interface identifies all 3G TS 32.111-2 [5] defined alarm event
 types used by this API. Their semantics are defined by 3GPP. Their
 encodings for this API are defined here.

This interface represents a super interface containing all the methods
 common to events associated with a single alarm.

This interface defines the possible values for alarm acknowledgement
 state.
 </p>
 <p>
 The alarm acknowledgement state is a part of the alarm information that
 is stored in systems Alarm List. It is used for management purposes only
 to mark alarms that are handled by operator or client application. The
 state of the new alarm is always set as <code>UNACKNOWLEDGED</code>.
 After the alarm perceived serverity is set as <code>
 PerceivedSeverity.CLEARED</code> and acknowledgement state as <code>
 ACKNOWLEDGED</code>, the alarm can be removed from systems Alarm List.

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:27

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:27

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:27

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:27

This interface defines the <CODE>StartMode</CODE> enumeration.

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

Get the names of the optional operations supported by this JVT
 Session Bean. The names of the optional operations are defined
 in the <CODE>JVT&lt;ApplicationType&gt;SessionOptionalOps</CODE> interface as
 defined by the API.

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

Get the names of the optional operations supported by this JVT
 Session Bean. The names of the optional operations are defined
 in the <CODE>JVT&lt;ApplicationType&gt;SessionOptionalOps</CODE> interface as
 defined by the API.

This Schema was generated by the OSS through Java XML Toolkit Doclet 3-30-2005 15:26

Get the names of the optional operations supported by this JVT
 Session Bean. The names of the optional operations are defined
 in the <CODE>JVT&lt;ApplicationType&gt;SessionOptionalOps</CODE> interface as
 defined by the API.

This Schema is used to provide common framework components for the OSS/J XML Interfaces. This Schema was generated by the OSS Through Java XML Toolkit Doclet 1-26-2004 7:3

Returns the supported granularity periods for the provided ActivityValue
 or, if the value is null, return the summary of all supported granularity
 periods.
 This operation returns a list of granularity periods that can be used
 when a measurement job shall be created, with the specified definition
 of the measurement job.
 If no granularity period is supported for the specified instances and
 attributes, an empty array shall be returned.
 The returned granularity periods shall be a factor or a multiple of a
 hour.

Interface for the Activity Creation event
 Raised by an OSS/J application, when an activity has been created.

Defines enumeration values for report mode.
 The report mode for the measurement results can be done in different
 ways. The following report modes exists:
 <ul>
 <li> event per measurement job.
 <li> event for multiple measurement jobs.
 <li> report file per measurement job.
 <li> report file for multiple measurement jobs.
 <li> proprietary mechanism per measurement job.
 <li> proprietary mechanism for multiple measurement jobs.
 <li> iterator per measurement job.
 <li> iterator for multiple measurement jobs.
 </ul>
  <p>
 If the reporting mode is set to event the system will emit an event
 that carries the measurement result report. If the reporting mode is set to
 file, the measurement job will capture the measurement result reports into
 a data storage and then emit an event to the client about the availability
 of the data. If the reporting mode is set to proprietary then the proprietary
 of the data. If the reporting mode is set to iterator, then the system will
 emit an event that includes the iterator.  The frequency of this event is
 det ermined by the data storage creation frequency. When a client receives
 an event of data availability, the client can retrieve the data, by using
 appropriate mechanism.
 <p>
 Also, the support for stream oriented protocol makes it
 real-time report forwarding feasible with no inherent delays
 introduced by Activity Scheduling mechanism.
 <p>
 Example stream oriented protocols supported could include
 FTP, HTTP/HTTPS or low-level RAW SOCKET (or SSL socket) based transfers.
 The details of the actual transfer primitives are currently out of
 scope of
 this API specification and are left to individual implementaion.
 <p>

This interface is an enumeration of the
 valid values for the Control State of an ActivityValue

Interface for the Activity Removal event
 Raised by an OSS/J application, when an activity has been removed
 by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the removal of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity Reporting Results Availability
 notification.
 Raised by an OSS/J implementation, when an Activity has
 report results ready, to be sent to the client.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Suspend event
 Raised by an OSS/J application, when an activity has been temporarily
 suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the suspension of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the sending Activity Report Data in a
 notification to the client.
 <p>
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Resume event
 Raised by an OSS/J application, when an activity is resumed,
 after it has been temporarily suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the resumption of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity events.
 Raised by an OSS/J application, when individual Activities are
 created or removed or when there is a change an activity's
 Control Status.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.

This interface is an enumeration of the
 valid values for the Execution State of an ActivityValue

This Schema is used to provide common framework components for the OSS/J XML Interfaces. This Schema was generated by the OSS Through Java XML Toolkit Doclet 1-26-2004 7:3

Returns the supported granularity periods for the provided ActivityValue
 or, if the value is null, return the summary of all supported granularity
 periods.
 This operation returns a list of granularity periods that can be used
 when a measurement job shall be created, with the specified definition
 of the measurement job.
 If no granularity period is supported for the specified instances and
 attributes, an empty array shall be returned.
 The returned granularity periods shall be a factor or a multiple of a
 hour.

Interface for the Activity Creation event
 Raised by an OSS/J application, when an activity has been created.

Defines enumeration values for report mode.
 The report mode for the measurement results can be done in different
 ways. The following report modes exists:
 <ul>
 <li> event per measurement job.
 <li> event for multiple measurement jobs.
 <li> report file per measurement job.
 <li> report file for multiple measurement jobs.
 <li> proprietary mechanism per measurement job.
 <li> proprietary mechanism for multiple measurement jobs.
 <li> iterator per measurement job.
 <li> iterator for multiple measurement jobs.
 </ul>
  <p>
 If the reporting mode is set to event the system will emit an event
 that carries the measurement result report. If the reporting mode is set to
 file, the measurement job will capture the measurement result reports into
 a data storage and then emit an event to the client about the availability
 of the data. If the reporting mode is set to proprietary then the proprietary
 of the data. If the reporting mode is set to iterator, then the system will
 emit an event that includes the iterator.  The frequency of this event is
 det ermined by the data storage creation frequency. When a client receives
 an event of data availability, the client can retrieve the data, by using
 appropriate mechanism.
 <p>
 Also, the support for stream oriented protocol makes it
 real-time report forwarding feasible with no inherent delays
 introduced by Activity Scheduling mechanism.
 <p>
 Example stream oriented protocols supported could include
 FTP, HTTP/HTTPS or low-level RAW SOCKET (or SSL socket) based transfers.
 The details of the actual transfer primitives are currently out of
 scope of
 this API specification and are left to individual implementaion.
 <p>

This interface is an enumeration of the
 valid values for the Control State of an ActivityValue

Interface for the Activity Removal event
 Raised by an OSS/J application, when an activity has been removed
 by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the removal of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity Reporting Results Availability
 notification.
 Raised by an OSS/J implementation, when an Activity has
 report results ready, to be sent to the client.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Suspend event
 Raised by an OSS/J application, when an activity has been temporarily
 suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the suspension of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the sending Activity Report Data in a
 notification to the client.
 <p>
 <p>
 It is sufficient for implementatations to just set the Key attribute
 of the ActivityValue for this notification. All the other attributes
 of the ActivityValue need not be present in the ActivityValue.

Interface for the Activity Resume event
 Raised by an OSS/J application, when an activity is resumed,
 after it has been temporarily suspended by the client.
 <p>
 The reporting results of a single activity may be shared by multiple
 clients (as listeners or receivers). Hence, it is important to
 notify all registered parties of the resumption of an Activity by
 emitting this event to common "JVTEventTopic" JMS topic.

Base Interface for the Activity events.
 Raised by an OSS/J application, when individual Activities are
 created or removed or when there is a change an activity's
 Control Status.
 <p>
 The Factory method for making empty instances of ActivityValue are
 not specified in this interface. It is expected that each API using
 this interface, will have its own sub interface of ActivityValue as
 well as a sub interface of ActivityEvent, so that the appropriate
 makexxxValue(String typename) will be provided by that API.

This interface is an enumeration of the
 valid values for the Execution State of an ActivityValue

Service Activation XML schema.

Part 1 version: Id: structures.xsd,v 1.2 2004/01/15 11:34:25 ht Exp
Part 2 version: Id: datatypes.xsd,v 1.3 2004/01/23 18:11:13 ht Exp

The schema corresponding to this document is normative,
with respect to the syntactic constraints it expresses in the
XML Schema language.  The documentation (within <documentation> elements)
below, is not normative, but rather highlights important aspects of
the W3C Recommendation of which this is a part

The simpleType element and all of its members are defined
   towards the end of this schema document

simple type for the value of the 'namespace' attr of
'any' and 'anyAttribute'

Value is
           ##any      - - any non-conflicting WFXML/attribute at all
           ##other    - - any non-conflicting WFXML/attribute from
                           namespace other than targetNS
           ##local    - - any unqualified non-conflicting WFXML/attribute
           one or     - - any non-conflicting WFXML/attribute from
           more URI        the listed namespaces
           references
           (space separated)
 ##targetNamespace or ##local may appear in the above list, to
     refer to the targetNamespace of the enclosing
     schema or an absent targetNamespace respectively

notations for use within XML Schema schemas

First the built-in primitive datatypes.  These definitions are for
information only, the real built-in definitions are magic.

For each built-in datatype in this schema (both primitive and
derived) can be uniquely addressed via a URI constructed
as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the datatype
For example, to address the int datatype, the URI is:
  http://www.w3.org/2001/XMLSchema#int
Additionally, each facet definition element can be uniquely
addressed via a URI constructed as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the facet
For example, to address the maxInclusive facet, the URI is:
  http://www.w3.org/2001/XMLSchema#maxInclusive
Additionally, each facet usage in a built-in datatype definition
can be uniquely addressed via a URI constructed as follows:
  1) the base URI is the URI of the XML Schema namespace
  2) the fragment identifier is the name of the datatype, followed
     by a period (".") followed by the name of the facet
For example, to address the usage of the maxInclusive facet in
the definition of int, the URI is:
  http://www.w3.org/2001/XMLSchema#int.maxInclusive

Now the derived primitive types