Proof of Concept - OSS Design

336 views
259 views

Published on

Proof of Concept - OSS Design

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
336
On SlideShare
0
From Embeds
0
Number of Embeds
115
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Proof of Concept - OSS Design

  1. 1. Central Order Mgmt Provisioning Activation Inventory 1.captureInteraction 2.automateInteraction 3.changeServiceConfigurationState 4.getServiceConfiguration 5.changeServiceConfigurationState 7.changeInteractionState 6.execute Activation Order Inventory – Process Flow (Type: PPT, Total Page: 41) This operation captures the action to be accomplished within a business interaction that serves as the long running transaction context for all the consequent design activities. The action is parameterized with information that is input to the design activities, which log their service configuration and life cycle management changes to the business interaction. Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Input Parameter Parameter Type Description interaction.name String Identify the BusinessInteraction by aggregating the Provisioning Order id, revision, order line number into an encoded textual identifier. interaction.effDate DateTime The date-time when the BusinessInteraction is due to complete (become effective). interaction.specification.name String This BusinessInteraction specification name identifies the type of business interaction that is being captured. (Normally, OSM would identify the BusinessInteraction by aggregating the Order id, revision, order line number into an encoded textual identifier). request ActionRequest The action that is being performed within the context of this BusinessInteraction. Output Parameter Parameter Type Description bi BusinessInteraction This operation returns the BusinessInteraction that was found by name or created. The bi contains a valid bi id, which will need to be used in subsequent operations by setting the bi id on the request context, so that the operations are performed within the context of the BusinessInteraction. Example
  2. 2. Specification Class Cartridge Description NE_ID_CSCO-BTS-10200_4-4 identifier Required Scalar (R) TBD ID SIP Subscriber ID Required Scalar (R) sip_subscriber_1 CATEGORY Subscriber category Optional Scalar (O) INDIVIDUAL NAME Subscriber name Optional Scalar (O) JohnSmith SUB_STATUS Subscriber status Optional Scalar (O) ACTIVE LANGUAGE Subscriber’s preferred language Optional Scalar (O) English BILLING_DN Billing number to use Optional Scalar (O) 6.14E+09 DN1 Subscriber Directory Number Optional Scalar (O) 6.14E+09 RING_TYPE_DN1 Ring type for DN1 Optional Scalar (O) 1 SUB_PROFILE_ID Subscriber profile id Optional Scalar (O) sub_profile_1 TERM_TYPE The termination type Optional Scalar (O) SIP AOR_ID Address of record Optional Scalar (O) 6135551234@oracle.com PRIVACY Privacy Optional Scalar (O) user AUTH_USER Authentication user name Optional Scalar (O) JohnSmith AUTH_REALM_ID Authentication realm ID Optional Scalar (O) oracle USER_AUTH_PASSWORD Password for this auth-user Optional Scalar (O) my_password Specification Class Cartridge Description NE_ID_CSCO-BTS-10200_4-4 identifier Required Scalar (R) TBD SUB_ID SIP Subscriber ID Required Scalar (R) sip_subscriber_1 FEATURE_NAME Required Scalar (R) VOICE_MAIL_ID Optional Scalar (O) Activation – CSDL, ADSL Mapping The CSDL C_CSCO-BTS-10200_4-4_ADD_SIP-SUBSCRIBER calls the following ASDLs: A_CSCO-BTS-10200_4-4_ADD_SUBSCRIBER A_CSCO-BTS-10200_4-4_ADD_USER-AUTHENTICATION A_CSCO-BTS-10200_4-4_QRY_AOR-TO-SUBSCRIBER A_CSCO-BTS-10200_4-4_MOD_AOR-TO-SUBSCRIBER A_CSCO-BTS-10200_4-4_SHOW-TRANSACTION-QUEUE The CSDL C_CSCO-BTS-10200_4-4_ADD_SUBSCRIBER-FEATURES calls the following ASDLs: A_CSCO-BTS-10200_4-4_ADD_SUBSCRIBER-FEATURES A_CSCO-BTS-10200_4-4_SHOW-TRANSACTION-QUEUE Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Example

×