Next figure, shows the main parts related to configuration and provisioning in the SAPC.

Figure 1   Configuration and Provisioning Overview

The purpose of this document is to provide guidelines and examples to configure the SAPC node for the Ericsson SIM-based Untrusted Wi-Fi Calling Solution.

This document is not intended as an exhaustive guide to configure the SAPC for every possible scenario.

The complete parameter list and details of all the SAPC configuration options are included in separate documents, refer to Managed Object Model (MOM) and Provisioning REST API for more information.

The following typographic and document conventions are used:

This document refers to some configuration and provisioning data.

To clarify which detailed data is managed by COM or by the REST API, this document uses the following conventions:

• Configuration: whenever referring to Managed Object Class (MOC).

  The detailed description of the object and attributes can be found in Managed Object Model (MOM).

  Example: set enableReauthsOnSubsChange attribute in class AppConfig.

  The tools or interfaces to manage these data in the SAPC are:

  • NETCONF interface, refer to Ericsson NETCONF Interface.

    The configuration examples show the NETCONF file contents, using the following syntax:

    <edit-config>
      ...
      <config>
      <ManagedElement xmlns="urn:com:ericsson:ecim:ComTop">
      <managedElementId>1</managedElementId>
           ...
      </ManagedElement>
      </config>
    </edit-config>

  • COM CLI, refer to Ericsson Command-Line Interface.

• Provisioning: mainly subscribers, subscriber groups (dataplans), services (contents), profiles, and policy-related data. The SAPC provides a REST API for them, see Provisioning REST API.

  This document uses the following terminology for them: <resource-name> URI in the provisioning REST API.

  Example: To provision subscriber groups, use the dataplan URI in the provisioning REST API.

  Provisioning examples show HTTP operations on REST resources with the following syntax:

  HTTP-Operation /resource-URI 
      {json content}

  where /resource-URI is the relative URI from the SAPC provisioning base URI detailed in Provisioning REST API.

  Example:

  PUT /dataplans/Gold   
  { "dataplanName" : "Gold",
    "subscribedContents" : [{"contentName" : "HTTP_Streaming",
                             "redirect" : false}]
  }

  Note:

  To ease provisioning operations, the SAPC provides an HTTPS CLI client named resty, refer to Provisioning Tools.