• Save
PoC UK OSS Design
Upcoming SlideShare
Loading in...5
×
 

PoC UK OSS Design

on

  • 161 views

PoC UK OSS Design

PoC UK OSS Design

Statistics

Views

Total Views
161
Views on SlideShare
124
Embed Views
37

Actions

Likes
0
Downloads
0
Comments
0

9 Embeds 37

http://philipjung.blogspot.kr 22
http://philipjung.blogspot.in 6
http://philipjung.blogspot.hk 3
http://philipjung.blogspot.sg 1
https://philipjung.blogspot.com 1
http://philipjung.blogspot.dk 1
http://philipjung.blogspot.ru 1
http://philipjung.blogspot.no 1
https://www.blogger.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

PoC UK OSS Design PoC UK OSS Design Presentation Transcript

  • Inventory Design – Mobile Resource Modeling (Type: PPT, Total Page: 53) Mobile service mainly involves resources like Subscriber Identity Module (SIM), International Mobile Subscriber Identify (IMSI), Home Location Register (HLR) and Telephone number (TN). SIM: The Subscriber Identity Module (SIM card) is the key to identify and authenticate the subscriber. An Equipment resource is used to model as a SIM. IMSI: The International Mobile Subscriber Identity (IMSE) is the subscriber identity in the network. A Network Element Account (NEA) is used to model as an IMSI. It is closely related to SIM as well as HLR. Please refer to the resource relationship HLR: The Home Location Register is a database for a mobile network in which stores subscribe information. A Network Element is used to model as a HLR. IMSI is closely related to it and model as the NEA on it. TN: It is the subscriber’s Telephone Number (TN). There is a delegated Telephone Number resource in SSM. Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Example Name Description Char? Type ID It is the SIM ID and is used to unique identify a SIM N Numeric (20) PIN Personal Identification Number Y Numeric (20) PUK PIN Unblocking Key. It is used to unblock the SIM. The SIM is blocked because the PIN is input incorrectly for 4 times Y Numeric (20) Name Description Char? Type ID An ID that unique identify a HLR N String (20) Name Gives the HLR a more description name N String (255) Name Description Char? Type ID Use it to store the telephone number N Numeric (8) Name Description Char? Type ID It is the IMSI ID and is used to unique identify a IMSI N Numeric (15) Network Element ID The Network Element in this case is HLR and this is the ID of the HLR, which the IMSI belongs to N String (20)
  • Inventory Design – Mobile Resource Relationship Modeling IMSI and HLR The relationship between IMSI and HLR is natively support in SSM. During Network Element Account (NEA) creation, a Network Element must be specified. In this case, during the creation of IMSI, a HLR must be specified. SIM and IMSI SIM and IMSI are related together via another SSM feature; Pre-configuration. e.g SIM and IMSI are paired up before assigning to a service. Once 2 resources are pre-configured, when one of them is assigned to a service, another one will be assigned automatically. Similar happens to un-assignment. Usually, SIM card is used to assign to service and the IMSI will be assigned automatically. TN and HLR TN and HLR are related via another SSM feature; Inventory Group. TN does not have any relationship with HLR when it is in “unassigned” state. However, when it is assigned to a service, its Inventory Group must be same as the Inventory Group of the HLR. Please note, HLR is NOT assigned to the service directly, instead, it is the IMSI is assigned to service. I.e. the Inventory Group of the TN must be same as the HLR Inventory Group of the assigned IMSI. Although Inventory Group is supported in SSM, the matching of Inventory Group between resource must be done via customized Rule Set. SIM The Subscriber Identity Module (SIM card) is the key to identify and authenticate the subscriber. An Equipment resource is used to model as a SIM. Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Example Resource Model As Related with Relationship Type SIM Equipment IMSI Pre-configuration IMSI Network Element Account SIM Pre-configuration HLR Native HLR Network Element IMSI Native Telephone Number Telephone Number HLR Inventory Group
  • Inventory Design – Inventory Interface Design In order to fulfill the above features, the API can be categorized into 4 functional areas: 1. Resource Lookup: There are a lot of different way to locate a resource, e.g. by name, specification name, characteristic, status, inventory group or even by another resource. 2. Resource Creation: Some resources are created during service creation. e.g. Email account. 3. Service Lookup: In order to operate the service after its creation, it has to be a way to find it out. The easier way is search it by its service id. However, external systems are seldom to store this id. In most of the cases, search by a relevant feature that is unique in the service. For example, search a mobile service by the mobile phone number. Service Creation The API call will perform several UIM operations: 1. Service Creation: The service and its configuration will be created. 2. Resource Allocation: Depending the service and the input parameters, resources will be lookup or created, allocated and assigned to the services. 3. Approve and Issue service: In UIM, after resources allocation, each service configuration must go through approve and issue state. With the GCI API, these 2 stages will be automated. the service status after the successful of this call will be always “ISSUED”. Service Completion Once the resources are assigned to the service and the service status becomes “ISSUED”, integration systems can perform their jobs to prepare the service, such as Activation, which activates equipments for the service. When the service is ready to rollout for customer, integration system can make this “Service Completion” call to change the service status to “IN-SERVICE”. Service Disconnection If the status of a service is “IN-SERVICE”, integration system can make this call to disconnect the service. Note that the basic API provides the simplest way to locate a service, which is by UIM service id. However, the integration system may not know this id and service specific key must be provided to locate the service. e.g. mobile number for mobile service, web account login id for broadband service etc. Service Change Support for service change is limited. It only supports upload and download speed change for Broadband service. Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Example
  • Activation – Mobile Activation Overall Service The following table lists the cartridge services and CSDLs used for the PoC Ericsson HLR The following table lists the cartridge services used for the PoC CSDL Configuration The following table lists the CSDLs used for the PoC Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Service Description CSDL Add mobile service subscription Create a GSM subscription C_ERIC-HLR_R11-0_CREATE_SUBSCRIPTION C_ERIC-AUC_R11-0_CREATE_SUBSCRIPTION Delete mobile service subscription Delete a GSM subscription C_ERIC-HLR_R11-0_DELETE_SUBSCRIPTION C_ERIC-AUC_R11-0_DELETE_SUBSCRIPTION Activate SMS service Activate SMS service C_ERIC-HLR_R11-0_ACT_TSMO Network Element ASAP Cartridge Version Ericsson HLR R11.0 11.0 Ericsson AUC R11.0 11.0 Service Description Create HLR subscription Create a GSM subscription Delete HLR subscription Delete a GSM subscription Activate SMS service Activate SMS service Example
  • Activation – Mobile Activation C_ERIC-HLR_R11-0_CREATE_SUBSCRIPTION CSDL-ASDL Configuration A_ERIC-HLR_R11-0_CREATE_SUBSCRIPTION Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr ASDL Label CSDL Label Parameter Type Description MCLI NE_ID_ERIC-HLR Required scalar Logical network element name IMSI IMSI Required scalar International Mobile Subscriber Identity MSISDN MSISDN Required scalar Mobile Systems International Subscriber Identity Number CSDL ASDL C_ERIC-HLR_R11.0_CREATE_SUBSCRIPTION A_ERIC-HLR_R11.0_CREATE_SUBSCRIPTION C_ERIC-HLR_R11.0_DELETE_SUBSCRIPTION A_ERIC-HLR_R11.0_DELETE_SUBSCRIPTION C_ERIC_HLR_R11.0_ACT_TSMO A_ERIC_HLR_R11.0_ACT_TSMO CSDL Label Default Value Parameter Type Description NE_ID_ERIC-HLR Required scalar Logical network element name IMSI Required scalar International Mobile Subscriber Identity MSISDN Required scalar Mobile Systems International Subscriber Identity Number Example