Page History

<style>.widget_list {
    margin: 0;
    padding: 0;
}
.widget_list li{
    margin: 0 0 20px;
    padding: 0;
    list-style:none;
}
.widget_list li a{
    display:block;
  color: #000 !important;
    font-weight: 600;
    padding: 10px;
    border:1px solid #ccc;
    background-color:#f6f6f6;
    padding: 25px 25px 25px 80px;
   position:relative;
}
.widget_list li a:hover {
    color: #133595 !important;
    text-decoration: none;
}
.widget_list li a img {
    max-width: 100% !important;
    height: auto !important;
}
.widget_list li a .confluence-embedded-file-wrapper {
    position: absolute;
    width: 50px !important;
    display: block !important;
    left: 10px;
    top: 50%;
    transform: translateY(-50%);
}
</style>
<scriptstyle><script src="//app-ab16.marketo.com/js/forms2/js/forms2.min.js"></script>
<formscript><form id="mktoForm_2355" style="display:none"></form>
<script>MktoForms2form><script>MktoForms2.loadForm("//app-ab16.marketo.com", "021-WLD-815", 2355);</script>

21.0.0

(v4.0.0)

Geographic Address Management API

Provides a standardized client interface to an Address management system. It allows looking for worldwide addresses. It can also be used to validate geographic address data, to be sure that it corresponds to a real geographic address. Finally, it can be used to look for a geographic address by: searching an area as a start (city, town ...), then zooming on the streets of this area, and finally listing all the street segments (numbers) in a street.

20.5.0

(v4.0.0)

Geographic Location Management API

Provides the information of a geographic region of the entity (customer, equipment, address).

19.5.0

(v4.0.0)

IoT Device Management API Component Suite

In addition to including established TM Forum Open APIs, such as alarm management, resource management and activation APIs, the IoT Device Management API Component Suite also includes an IoT Data Access Endpoint API. This API allows for IoT data access using different types of protocols (MQTT IoT, CoAP, etc.). It encapsulates the protocols and allows devices to be easily integrated into solutions that support a host of IoT initiatives, including smart cities, smart factories and other vertical markets.

19.0.0

(v4.0.0)

IoT Service Management API Component Suite

The IoT Service Management Component suite captures the minimal essential operational APIs required to manage IoT service end to end, and therefore accelerate IoT infrastructure as a service and help manage IoT at scale.

20.5.0

(v4.0.0)

Payment Method API

This API supports the frequently-used payment methods for the customer to choose and pay the usage, including voucher card, coupon, and money transfer.

21.0.0

(v4.0.0)

Performance Management API

Provides a standardized mechanism for performance management such as the creation, partial or full update and retrieval of resources involved in performance management (Measurement Production Job, Measurement Collection Job, and Ad hoc Collection). It also allows notification of events related to performance. 

20.5.0

(v4.0.0)

Promotion API

Used to provide the additional discount, voucher, bonus or gift to the customer who meets the pre-defined criteria. Using promotion, the enterprise is able to attract the users and encourage more consumption, especially continuous purchases. Normally Promotion is not regarded as one type of product or product offering. It is often applied when the customer buys the product offerings with the price or amount surpassing the certain limit

21.0.0

(v4.0.0)

Recommendation API

Recommendation API is used to recommend offering quickly based on the history and real-time context of a customer. It is a real-time and personalized recommendation API. It is usually provided by e-commerce or BSS, CRM system in omni-channel.

20.5.0

(v4.0.0)

Resource Activation and Configuration API

The Resource Activation and Configuration API can be used to query resource instances to acquire the resource activation states and attributes, and it can be used to create/update, configure and activate the resource instances.

21.0.0

(v4.0.0)

Resource Catalog Management API

The Resource Catalog Management API REST specification allows the management of the entire lifecycle of the Resource Catalog elements and the consultation of resource catalog elements during several processes such as ordering process.

19.5.0

(v4.1.0)

Resource Function Activation and Configuration API

This API introduces Resource Function which is used to represent a Network Service as well as a Network Function. The Network Service and Network Function class definitions and associations in TR244 (which, in turn, builds on concepts from the SID addenda on Logical Resource and Service) are utilized to define the Resource Function

19.5.0

(v4.0.0)

Resource Ordering Management API

The REST API for Resource Order Management. It includes the model definition as well as all available operations. Possible actions are creating, updating and retrieving Resource Orders (including filtering). A Resource Order API provides a standard mechanism for placing a Resource Order with all necessary order parameters.

21.0.0

(v4.0.0)

Risk Management API

The Risk Management API allows the retrieval of Risk Assessments during interaction with PartyRoles (individualsor organizations) typically engaged in an Order process from ProviderPartyRole. The Risk Assessment request is usually issued by the ProviderPartyRole (e.g. Service Provider). The resources used to retrieve these assessment are Task resources, as per the Open API guidelines for tasks.

Service Catalog API

The Service Catalog Management API allows the management of the entire lifecycle of the service catalog elements.

20.5.0

(v4.0.0)

Service Ordering Management API

The REST API for Service Order Management provides a standardized mechanism for placing a service order with all of the necessary order parameters. It allows users to create, update & retrieve Service Orders and manages related notifications.

21.0.0

(4.1.0)

Service Problem Management

The SPM API is used to manage service problems. Service problems are generated based on the information declared by a partner or the event information notified from infrastructure providers. The event information includes alarm information, performance anomaly information, trouble ticket information, SLA violation, maintenance information, and prediction information.