Function Specification Multi Service Consumer Common Data
Ericsson Dynamic Activation 1

Contents

1Introduction
1.1Purpose and Scope
1.2Target Group
1.3Typographic Conventions

2

Multi Service Common Data Provisioning Solution
2.1Overview
2.2Multi Service Common Data Provisioning

Reference List

1   Introduction

This section contains information about the purpose, scope, and target group for the document.

1.1   Purpose and Scope

This document gives a brief introduction to Multiple Service Consumer Common Data provisioning solution, provided by Ericsson™ Dynamic Activation (EDA).

1.2   Target Group

The target group for this document is as follows:

For more information regarding the different target groups, see Library Overview Reference [1].

1.3   Typographic Conventions

Typographic conventions are described in Library Overview Reference [1].

2   Multi Service Common Data Provisioning Solution

2.1   Overview

Multi Service Consumer contains multiple services. There are some common data to be synchronized among multiple services, and EDA supports this kind of provisioning via the MultiSCCat CAI3G interface.

The following common data is supported:

CAI3G interface parameter mapping is shown in the following table:

Table 1    Mapping Relationship of CAI3G Interface Parameters

MOType

MultiSCCat @http://schemas.ericsson.com/pg/cudb/1.0/

EPSMultiSC @http://schemas.ericsson.com/ma/HSS/

Subscription @http://schemas.ericsson.com/ema/ UserProvisioning/GsmHlr/

Attribute

AdminUserDisable

epsAdminDisable

N/A

NetworkAccessMode

epsNam

nam

An overview of the provisioning flow for MultiSCCat is shown in Figure 1.

Figure 1   Provisioning Flow for Subscriber Provisioning

The MultiSCCat subscriber provisioning workflow procedure is as follows:

  1. A provisioning MultiSCCat request is received and its syntax is validated. MultiSCCat checks existing services and decides to execute corresponding operation on the existing services.
  2. An EPS provisioning request is received and its syntax is validated. For detailed steps of EPS provisioning, refer to Function Specification Layered LTE EPC, Reference [2].
  3. A response is sent back to the MultiSCCat.
  4. An HLR provisioning request is received and its syntax is validated. For detailed steps of HLR provisioning, refer to Function Specification Layered HLR, Reference [3].
  5. A response is sent back to MultiSCCat.
  6. The MultiSCCat response message is sent back.
Note:  
The Get operation of MultiSCCat provisioning interacts with CUDB directly.

The Fault Tolerant function is supported in the Set operation. When the Set operation fails, the same request can be re-sent.


2.2   Multi Service Common Data Provisioning

CAI3G is offered for the provisioning of Multiple Service Consumer Common Data. Through the CAI3G provisioning interface, it is possible to perform the following Customer Service Orders (CSOs):


Reference List

Ericsson Documents
[1] Library Overview, 18/1553-CSH 109 628 Uen
[2] Function Specification Layered LTE EPC, 5/155 17-CSH 109 628 Uen
[3] Function Specification Layered HLR, 4/155 17-CSH 109 628 Uen


Copyright

© Ericsson AB 2017. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    Function Specification Multi Service Consumer Common Data         Ericsson Dynamic Activation 1