Transcript Standards-enabled E-Commerce: From Telecommunications to

Standards-enabled E-Commerce:
From Telecommunications to Open-edi to ebXML
Paul Levine
Prepared For:
Phone: +1 732 699-3024
SC 32 Tutorial on WG 1 Activities
Fax: +1 732 336-2980
Email:[email protected]
22 October 2001
COMMON LANGUAGE and LocateIt are registered trademarks and CLCI, CLEI, CLFI, CLLI, NC/NCI and TeleHunt are trademarks of Telcordia Technologies, Inc.
Proprietary - Licensed Material
Possession or use of this material or any of the COMMON LANGUAGE Codes, Rules and Information disclosed herein requires a written license agreement and is
governed by its terms and condition.s. For more information, visit www.commonlanguage.com/notices.
Copyright © 1999, Telcordia Technologies, Inc. All rights reserved.
An SAIC Company
Outline
 Standards bodies/consortiums, work effort, deliverables
 Open-edi
 UN/CEFACT Modeling Methodology Framework
 ebXML technical architecture
 tML
 Generic Telecommunications Data Dictionary
 TeleManagement Forum BOV methodology
 COMMON LANGUAGE® Products
 ANSI T1 standardized codes for interoperability
 ITU-T Rec. M.1400 formalization proposal
Proprietary - Licensed Material. See proprietary restrictions on title page.
2
Standards
Body/
Consortium
ISO/IEC JTC 1/
SC 32/WG 1
UN/
CEFACT
TMWG
&
ANSI X12PITG
ebXML
[Cosponsored
by
UN/CEFACT
& OASIS]
Work effort
Open-edi
Framework
B2B
Business
Collaborations
via
Business
Process &
Information
Models
(Protocolneutral
methodology)
Apply B2B
Business
Collaborations
via
Business
Process &
Information
Models that
generate
XML DDTs/
Schemas
(Protocolspecific
derivation)
Standards/
Deliverables
Open-edi
Reference
Model,
ISO/IEC 14662
&
Operational
Aspects of
Open-edi for
Implementation,
ISO/IEC 15944-1
UN/CEFACT
Modeling
Methodology
TMWG N090
Technical
Specifications, e.g.
ebXML
Business
Process
Specification
Schema
TM Forum
[telecom
service
providers,
service
integrators,
suppliers of
hardware &
software]
Apply
BP&IM to
specification of A2A
business
collaborations via
protocolneutral
“contracts”
supported
by a Shared
Data Model
ANSI T1M1
CLDR-SWG
&
tML/GTDD
ITU-T SG 4
&
tML
Develop ITenabled
standardized codes
for
information
exchange
& apply
XML
constructs
in a tML
repository
based on a
GTDD
Develop ITenabled
standardized codes
for information
exchange &
apply XML
constructs in
a tML
repository
Next
Generation
OSS
Framework
Architecture
Technology
Neutral
Specification
ANSI T1
Standards,
e.g.,
Location
Entity
Identification,
GTDD
coordination, tML
Framework
ITU-T
Recommendation M.1400
Designations
for
Interconnections among
Network
Operators,
tML
Framework
Proprietary - Licensed Material. See proprietary restrictions on title page.
3
Open-edi Transaction
Party
Proprietary - Licensed Material. See proprietary restrictions on title page.
4
Information Management Domain Breakdown
IMD
Party
edi Support
Business Agreement
edi Principal
Service
Service
Proprietary - Licensed Material. See proprietary restrictions on title page.
5
Open-edi Conceptual Model
Business and Organizational Requirements
Open-edi Conceptual Model Boundary
Requires
Open-edi Reference Model Boundary
Business
Operational
View
“Business”
Rules &
Semantics
Realized as
Conforms to
Requires
Functional
Service
View
Supports
Functional Capabilities and
Open-edi Support Services
Realized as
S
T
A
N
D
A
R
D
S
Conforms to
Open-edi Implementations
Proprietary - Licensed Material. See proprietary restrictions on title page.
6
Relationships: Open-edi Transactions, IMDs, Open-edi Conceptual Model
IMD
edi Support
Business Agreement
edi Principal
Service
Service
Business and Organizational
Requirements
Open-edi Conceptual Model Boundary
Open-edi Reference Model Boundary
Business
Operational
View
“Business” Rules &
Semantics
Requires
Functional
Service View
Requires
Supports
Functional Capabilities
and edi Support
Services
Realized as
Realized as
Conforms to
S
T
A
N
D
A
R
D
S
Conforms to
Party
Open-edi Implementations
Proprietary - Licensed Material. See proprietary restrictions on title page.
7
Open-edi Reference Model
B
U
S
I
N
E
S
S
T
R
A
N
S
A
C
T
I
O
N
S
Open-edi Reference Model
Business Operational View
Com ply with
Business aspects
of
business transactions
Covered by
BOV RELATED
STANDARDS
Viewed as
Inter-related
Functional Service View
Information technology
aspects of
Business transactions
Com ply with
Covered by
FSV RELATED
STANDARDS
Proprietary - Licensed Material. See proprietary restrictions on title page.
8
Sources of Requirements on the Business Operational View (BOV)
aspects of Open-edi which need to be integrated and/or taken into account in
Business Transactions
(Open-edi based)
Commercial
Framework &
Requirements
Characteristics of Open-edi
-Rule-Based
-Commitment Exchange
-Unambiguous Identification
-Business Transaction Model: Key
Components
Person
Process
Data
Business Transaction Model:
Classes of Constraints
Specification, Identification &
Classification of Open-edi scenarios
(and components)
FSV Business Demands on Open-edi
Support Infrastructure
Open-edi Scenario Templates
Public Policy
Req’mts
(Privacy,
Consumer,
etc.)
(For use in various applications areas
such as: e-commerce, eadministration, e-business, e-logistics,
e-government, etc.)
Sectorial (&
CrossSectorial)
Requirements
Cultural Adaptability
Localization &
Multilingualism
(IT vs Human Interface)
Adaptability
Legal
Framework &
Requirements
Information
Technology
Requirements
& Standards
Telecommunications
Requirement
s&
Standards
ISO & Other
Standards
Environments
Functional Services View (FSV)
Proprietary - Licensed Material. See proprietary restrictions on title page.
9
Business Collaboration Framework
The Business Collaboration Framework (BCF) is a formally defined set of model views of
business collaboration, each from a different and gradually more detailed perspective.
Open-edi Business Operational View (technology neutral)
 Business Operations Map (BOM) – the partitioning of business processes into business areas and
business categories.
 Business Requirements View (BRV) – the view of a business process model that captures the
requirements of a business collaboration protocol.
 Business Transaction View (BTV) - the view of a business process model that specifies the contract
formation process for various types of commercial contracts.
 Business Service View (BSV) - the view of a business process model that specifies the electronic
formation of commercial contracts using an electronic medium.
Open-edi Functional Service View (technology specific)
 Implementation Framework View (IFV) - the view of a business process model that specifies
specific network protocols necessary to communicate business information necessary for contract
formation.
Proprietary - Licensed Material. See proprietary restrictions on title page.
10
UN/CEFACT Modeling Methodology (UMM)
Workflows
 Business Modeling - the Business Modeling workflow provides an
organizational context for the business-to-business project. (BOM)
 Requirements - the Requirements workflow uses business models to
understand requirements on the business-to-business processes.
(BRV)
 Analysis - the Analysis workflow details the activities that occur, more
refined business processes, and identify high level objects. (BTV)
 Design - the Design workflow elaborates on the initial information
models and process interactions. (BSV)
Proprietary - Licensed Material. See proprietary restrictions on title page.
11
Business Operation Map
The BOM is an organizational view
of the Business Areas and Process
Areas as defined by a domain
taxonomy.
Process Areas
BOM
· Business Area [Package]
· Process Area [Package]
· Process(es) [Use Cases]
[Activity Diagrams]
· Categorization/ClassificationSchema
Business Areas
Business Operations Map
Business Processes
Communication
Prov ider
Subscriber
<<BusinessProcess>>
Create Serv ice Request
<<BusinessProcess>>
Activ ate Serv ice
Field Labor
Prov ider
<<BusinessProcess>>
<<BusinessCollaboration>>
Dev elop Serv ice Work Order Plan
Create Serv ice Work Order
<<BusinessProcess>>
Determine Serv ice Work Order
<<BusinessCollaboration>>
Assignment
Check Materials
<<BusinessProcess>>
<<BusinessCollaboration>>
Negotiate Reserv ation
Accept Conf iguration
<<BusinessProcess>>
Conduct Preserv ice Activ ity
<<BusinessCollaboration>>
Check Skills
<<BusinessProcess>>
Conf igure Serv ice
<<BusinessCollaboration>>
Assign Serv ice Work Order
<<BusinessTransaction>>
<<BusinessTransaction>> Negotiate Time
<<BusinessTransaction>>
Check Time Slot Av ailability
Request Time Slot Reserv ation
<<BusinessCollaboration>>
Check Time Av ailability
<<BusinessCollaboration>>
Initiate Installation Work
<<BusinessProcess>>
Conf igure Network and CPE
<<BusinessCollaboration>>
Update Materials
Field Techician
<<BusinessProcess>>
Update Installed Product
Materials Supplier
<<BusinessCollaboration>>
Close Serv ice Work Order
Proprietary - Licensed Material. See proprietary restrictions on title page.
12
Business Requirements View
Business Operations Map
The Business Requirement View is a specification
view of Business Processes defined as use cases,
requirements and collaborations. Defines the
choreography of Business Transactions. Defines the
Economic Resources, Economic Events and the
Economic Agents.
Business Processes
Communication
Prov ider
Subscriber
<<BusinessProcess>>
Create Serv ice Request
<<BusinessProcess>>
Activ ate Serv ice
Field Labor
Prov ider
<<BusinessProcess>>
<<BusinessCollaboration>>
Dev elop Serv ice Work Order Plan
Create Serv ice Work Order
<<BusinessProcess>>
Determine Serv ice Work Order
<<BusinessCollaboration>>
Assignment
Check Materials
<<BusinessProcess>>
<<BusinessCollaboration>>
Negotiate Reserv ation
Accept Conf iguration
<<BusinessProcess>>
Conduct Preserv ice Activ ity
<<BusinessCollaboration>>
Check Skills
<<BusinessProcess>>
Conf igure Serv ice
<<BusinessCollaboration>>
Assign Serv ice Work Order
<<BusinessTransaction>>
<<BusinessTransaction>> Negotiate Time
<<BusinessTransaction>>
Check Time Slot Av ailability
Request Time Slot Reserv ation
<<BusinessCollaboration>>
Check Time Av ailability
<<BusinessCollaboration>>
Initiate Installation Work
<<BusinessProcess>>
Conf igure Network and CPE
<<BusinessCollaboration>>
Update Materials
Field Techician
<<BusinessProcess>>
Update Installed Product
Materials Supplier
<<BusinessCollaboration>>
Close Serv ice Work Order
Business
Transaction
Business
Transaction
Business
Transaction
Business Requirements View
BRV
 Business Process(es) [Use Case]
 Business Collaboration Use Case
 Business Collaboration [Collaboration-Use Case
Realization, Business Objects]
Business Transaction View
Proprietary - Licensed Material. See proprietary restrictions on title page.
13
Business Transaction/Service View
Initiator
Responder
Resp
Business
Activity
Business Transaction
View
Business Transaction
The Business Service View
is a explicit specification of
business process
interactions according to
the type of transaction, type
of role, security and timing
parameters. The set of
interactions is derived from
the BT according to the
system requirements.
The Business
Transaction View is a
specification of a
business transaction
according to 6
predefined, legally
binding patterns.
Biz Doc

:

 OriginatingService
:
 RespondingService
Business Service View
1. request(BusinessAction)

1.1. signal(ReceiptAcknowledgement)

1.2. signal(AcceptanceAcknowledgement)

System
Technology
Transport
Implementation View
The Implementation View is a
specification of a business
interaction according to these
selected technology and
protocol. (Not part of UMM.)
Proprietary - Licensed Material. See proprietary restrictions on title page.
14
UN/CEFACT Modeling Methodology Framework
Workflow
Business
Modelling
Requirements








Analysis
Design








Methodology
Domain Analysis
Use Case Analysis
Process Discovery
Activity Modeling
Requirements
Gathering
Use Case Analysis
Process Analysis
Activity Modeling


Pattern
Business
Patterns (TBD)
Business
Collaboration
(TBD)






Process Analysis
Activity Modelling
Conceptual Class
Modeling

Process Analysis
Collaboration
Modelling
Message Sequencing
Information Modelling
Message Modelling
(protocol neutral)

Business
Information
Flow Patterns




Business
Service
Interaction
Patterns
Information
Modelling
Patterns





Implementation


Message Translation
Software
Development


Message
Design Rules
UML to XML
Mapping



Model Artifacts [UML]
Business Area [Package]
Process Area [Package]
Process(es) [Use Cases][Activity
Diagrams]
Business Process(es) [Use
Case]
Business Collaboration Use
Case
Business Collaboration
[Collaboration-Use Case
Realization]
Business Collaboration Protocol
[Activity Diagram]
Business Transactions [Activity
Diagram]
Business Documents
(conceptual) [Class Diagram]
Service Collaboration [Object
Collaboration]
Network Component [Class
Diagram]
Business Service [Class
Diagram]
Service Transactions [Sequence
Diagram]
Business Documents (detail)
[Class Diagram]
Component Diagrams
Message Specifications
Software Components
Proprietary - Licensed Material. See proprietary restrictions on title page.
15
Patterns - key to prescriptive reusability
 Business Collaboration patterns
– Open-edi scenario
– Choreography of multiple atomic Business Transaction Activity patterns that
transition the scenario from one state to another
– e.g., Negotiation to establish a legally binding commitment between a buyer
and a seller
 Business Transaction Activity patterns
– 6 patterns cover all known types of bilateral business transactions
– Identified by business experts answering simple questions
 Business Service Interaction patterns
– Specify specific interaction sequences between two application systems in
terms of business action and business signal messages
 Information Modeling patterns
– Attributes of Business Information Objects
Proprietary - Licensed Material. See proprietary restrictions on title page.
16
UN/CEFACT Business Transaction Patterns
 Commercial Transaction - used to model the “offer and acceptance”
business transaction process that results in a residual obligation between
both parties to fulfill the terms of the contract
 Query/Response – used to query for information that a responding partner
already has e.g. against a fixed data set that resides in a database
 Request/Response - used for business contracts when an initiating
partner requests information that a responding partner already has and
when the request for business information requires a complex
interdependent set of results
 Request/Confirm - used for business contracts where an initiating partner
requests confirmation about their status with respect to previously
established contracts or with respect to a responding partner’s business
rules
 Information Distribution - used to model an informal information
exchange business transaction that therefore has no non-repudiation
requirements
 Notification - used to model a formal information exchange business
transaction that therefore has non-repudiation requirements
Proprietary - Licensed Material. See proprietary restrictions on title page.
17
Business Transaction Selection Decision Tree
Is there a
response
required?
Yes
Does the
responder already
have the
information?
No
Is this a
formal nonreputable
notification?
No
Select
Information
Distributio
n
Select
Notification
Yes
Yes
No
Is pre-editor context
validation required
before processing?
Select
Query/
Response
No
Yes
Is there a residual
obligation between roles
No
to fulfill terms of the
contract?
Yes
Select
Commercia
l
Transactio
n
Proprietary - Licensed Material. See proprietary restrictions on title page.
Select
Request
/
Confirm
Select Request/
Response
18
Business Transaction Activity Pattern
:RespondingRole
:RequestingRole
CONTRACT
FAILED
START
[CONTRACTFAIL]
<<BusinessTransactionActivity>>
Activity
Document
Response
[CONTROLFAIL]
[SUCCESS]
CONTROL
FAILED
END
Document
Request
Proprietary - Licensed Material. See proprietary restrictions on title page.
Activity
19
Generic Business Service Interaction Pattern
Proprietary - Licensed Material. See proprietary restrictions on title page.
20
Conducting eBusiness via ebXML
Proprietary - Licensed Material. See proprietary restrictions on title page.
21
ebXML Business Operational View
based on UN/CEFACT Modeling Methodology
Business Knowledge
Lexicon
Library
Core Components &
Core Processes
Business Objects &
Business Processes
Business Modeling
Artifacts
Requirements Artifacts
Analysis Artifacts
Design Artifacts
Packages
Use Case Diagrams
Activity Diagrams
Sequence Diagrams
Conceptual Use Case
Diagrams & Description
Use Case Realization
Sequence Diagrams (opt)
Collaboration Diagrams (opt)
Conceptual Activity
Description
Activity Diagrams
Conceptual Class Diagrams
Final Class Diagrams
Business Process and Information Models
Proprietary - Licensed Material. See proprietary restrictions on title page.
22
ebXML Functional Service View
Proprietary - Licensed Material. See proprietary restrictions on title page.
23
What is tML?
 tML is a language derived from XML based on plain text tags
that describe vocabulary used in the exchange of data between
telecommunications entities
Proprietary - Licensed Material. See proprietary restrictions on title page.
24
Importance of tML
 Adds consistencies in development of
– tML schemas
– Vocabularies
– Namespaces
– Transformations
– Repository usage
Proprietary - Licensed Material. See proprietary restrictions on title page.
25
Goals of tML Framework Document
 Approve tML Framework Document as an ITU-T
recommendation
 Provide guidance for development of interoperable OAM&P
interfaces using TMN domain specific applications of XML
 Be applicable to various telecoms OAM&P domains
 Provide way for multiple telecoms industry fora to use a
common framework in developing network management
specifications using tML vocabulary
Proprietary - Licensed Material. See proprietary restrictions on title page.
26
Generic Telecommunications Data Dictionary
 Contributions to ITU-T SG 4 and ASC T1M1 requesting
standard data element names and descriptions for interenterprise information exchange
 Need industry recognition and cooperation of experts groups to
provide stewarded data elements and descriptions to a registrar
 T1M1 drafted ATIS Incubator proposal for a GTDD
– Requirements in compliance with X3.285 American National
Standard for Information Technology – Metamodel for the
Management of Shareable Data
 TeleManagement Forum Work Register response
– 6-month prototype in TMF KnowledgeBase
– GTDD is central to 4-step NGOSS methodology
– Makes GTDD international in scope
Proprietary - Licensed Material. See proprietary restrictions on title page.
27
TeleManagement Forum BOV Methodology
Business Analysis
System Integration & Engineering
Process
Modeler
Requirements
Process Library
eTOM
Analysis
Design
BAC
SDM
I n fo rmation Services and Communications
E-T OM Process Framework Operations Map
using
Ente rpris e
Support
B u s i ness
P lanning
Cu stomer
F i nancial
M a nagement
H R Management
M ar ket ing and Sales
M anag ement
M ar ket Research
and Analysis
L egal
M a nagement
PR and
C o m munity
R e lations
M a nagement
P r o cess
A r c hitecture
M a n agement &
S u pp. ort
P r o curement
M a nagement
R & D / Technology
A c q uisition
M a nagement
R e a l Estate
M a nagement
R egulatory
M a nagement
C ustomer
Fulfillm ent
A s surance
Fulfillm e nt
Billing
As s urance
Bi l ling
M ar ket
M anag ement and
S t r ategy
C hannel/Selling
C hain
M anag ement
S ales
M anag ement
P r oduct and Offer
D evel opment and
M anag ement
S uppl i er/Partner
R el at ionship
M anag ement
S uppl i er/Partner
D evel opment
Cus tom e r Re lations hip M anage m e nt Proce s s e s
K now ledge
M a nagement
C R M Planning
and
D evel opment
M ar keting
F ul fillment
S elling
O rder
H andling
P r oblem
H andling
C us tomer
Q oS Manage
ment
R et ention
and
Loyalty
I nvoicing
and Collect
i ons
D epl oyment
M anag ement
Se rvice De ve lopm e nt and Ope rations Proce s s e s
S er vi ce Planning
and D evelopment
S er vice
C onf iguration
Re s ource Infras tructure
R es ource Planning
and D evelopment
S er vi c e Problem
M anag ement
S er vi ce Quality
M anag ement
R at ing and
D i s counting
M anage m e nt Proce s s e s
R es ource
P r ovisioning
R es ource
I nvent ory
M anag ement
C ontract
D evel opment and
N eg otiation
R es ource
M ai nt enenance
and R estoration
R es ource Data
M anag ement
Val ue/ Contract
M eas urement /
M anag ement
org
S et t l ements and
B illing
M anag ement
M ar keting Promo
S t o ckholder
R e lations
M a nagement
N et wor k, C omput i ng and Application Resource Infrastructures
Re s ource Ele m e nt
SIMorg map
org
map
map
P h y si ca l Network /Informa ti on Technol ogy
contents
info
A2
Customer Invoice
Product
Catalog
Service
Network
Technology
M anage m e nt Proce s s e s
S e c urity and
Fraud
M a nagement
roles
A1
Metamodel
C us t omer I nt erface Management
Interpreted contents
contents
FSC
A3
Order
Business Process
Non-Computer
Jobs, Roles, Depts.
Info Description
Business Process Reqts
Analysis
Use cases
Process Plan
interpret
er uses
Activities
process snippets
info contracts
process contracts
decision contracts
Process
Plan
UML
Use Case & Activities
Contracts
Snippets
Naming
Extensions
Mediation
Gateways
UML
Component Diag
Proprietary - Licensed Material. See proprietary restrictions on title page.
contents
Class Diagram
Interaction
Data Translation
UML
Class & Relationships
28
Critical Information: Network Management
 Where is it?
– Location, frame, slot, port
 What is it?
– Facility/bearer ID
– Circuit ID
– Equipment (e.g., circuit board) ID
 How does it interface?
– Technical specifications
Proprietary - Licensed Material. See proprietary restrictions on title page.
29
What are COMMON LANGUAGE Products?
 Network Identification Solutions
– CLLI™ Location Identification
– CLFI™ Facility Identification
– CLCI™ MSG Message Trunk Circuit Identification
– CLCI S/S Special Services Circuit Identification
– NC/NCI™ Network Channel/Channel Interface Identification
– General Codes
 Equipment Identification Solutions
– CLEI ™ Equipment Identification
– Barcode Label Information
 Service Information Solutions
– USO Universal Service Order (USO)
– USOC Uniform Service Order Codes
– FID Field Identifiers
AND: The code sets change
dynamically to meet/manage
new business needs and new
technologies.
Proprietary - Licensed Material. See proprietary restrictions on title page.
30
COMMON LANGUAGE Products
Customer Overview
 180+ Telecoms Service Providers
– Licensees = more than 90% of North American market including ALL
major operators in USA & Canada
– International penetration includes Telekom SA, Telmex, most
Canadian operators, Telecom Italia, Guam, Axtel, Global Crossing,
and other global operators
– COMMON LANGUAGE Products have been an integral part of all of
Telcordia's major OSS Solution sales
 900+ Equipment Suppliers
– Every major equipment manufacturer, service company, and reseller,
including Siemens, Alcatel, Nortel, Fujitsu, Lucent, Cisco
– Telcordia includes descriptions of equipment in the CLEI code catalog
 11 OSS Providers & Telcordia
Proprietary - Licensed Material. See proprietary restrictions on title page.
31
Customer Need Model
Why do telecommunications companies
use COMMON LANGUAGE Products?
Network and
Service
Management
Proprietary - Licensed Material. See proprietary restrictions on title page.
32
Identification of Network Elements & Service Info
Customer
Premises
Equipment
Switching
Systems
Local
Distribution
Interoffice
Trunks
Switching
Systems
Local
Distribution
CLLI
CLLI
Carrier Subsystem
Toll
Connecting
Trunks
CLCI
MSG
CLLI
CLFI
CLLI
CLLI
CLLI
Local
End
Office
Switch
e
PABX
PABX
CLLI
CLFI
CLLI
CLCI
MSG
Modem
Pool
USOC
FAX
USOC
CLLI
DSLAM
DSLAM
CLLI
MSC/
MTSO
CLCI
S/S
CLCI
MSG
NC/NCI
USO/FID
USOC
CLCI
S/S
Tandem
CLFI
Switch
CLCI
MSG
NC/NCI
PCS
Mobile
CLLI
CLLI CLLI
CLFI
Local
End
Office
Switch CLCI
MSG Switch
Tandem
CLLI
GSM
Mobile
Proprietary - Licensed Material. See proprietary restrictions on title page.
USOC
CLCI
S/S
CLLI
USOC
CLFI
Fiber Optic
Carrier System
NC/NCI Access Server
CLEI
Local
CLCI
CLLI
USOC
End
Local
S/S
Office
CLFI
Central
CLCI
Switch
CLFI
Office
ATM/FR
MSG
ATM/FR
(Packet)
(Packet)
Network
Network
CLLI
CLLI
USOC
MSC/
MTSO
CLCI
IP Phone
USO/FID MSG
Interoffice
Trunks
Customer
Equipment
CLFI
ADM
CLLI
Router
MUX
NC/NCI
CLEI
MultiMultiplexer
Plexer
Multiplexer
CLLI
CLLI
33
CLLI Codes
Buildings,
Network Entities,
& Customer
Sites
Purpose
CLLI Code
 Clearly identify any physical location (site) worldwide,
including, network sites, network support sites, customer
locations, e.g. earth satellite stations, buildings, underground
vaults, switches, repeaters, etc.
 Specific place and functional category of a location
 Facilitate interactions within and among companies
 Centrally maintained location data repository
OSLONWRSDS1
11-character CLLI Code
Entity
City
Network Site (Building)
Network site identifier for a digital switching
office located at a specific address (stored in
Telcordia’s location database) in Oslo, Norway
Country
Proprietary - Licensed Material. See proprietary restrictions on title page.
34
ANSI T1 COMMON LANGUAGE-Based Standards
 T1.211-2001 Telecom Service Priority Codes: Revised 2001
 T1.213-2001 Equipment Entity ID: Revised 2001
 T1.220-1999 Manufacturer ID
 T1.223-1997 Network Channel/Network Channel Interface Code
Structures
 T1.238-1997 Facility Identification Code ID Structure
 T1.251-2001 Telecom Service Provider Codes
 T1.253-2001 Location Entity ID
 T1.266-1999 Circuit ID Codes
 T1.269-2000 Trace Message Formats
 dp/ANS for Interconnection Location Entity, IP Network Element
ID structure, and physical location address
Proprietary - Licensed Material. See proprietary restrictions on title page.
35
Telcordia - ANSI T1 Standards Relationship
 Telcordia COMMON LANGUAGE Products reflected in structure
and format in T1 standards
 Limited code instances included in T1 standards and
assigned/provided by Telcordia under Maintenance Agent
agreements
 Telcordia maintains COMMON LANGUAGE Products code
conventions and instances for new applications in telecom
technology and OSS requirements in cooperation with licensed
clients
 Preservation of Telcordia client investment in COMMON
LANGUAGE Products is carefully balanced with maintaining the
role of these code structures/formats in industry practice
Proprietary - Licensed Material. See proprietary restrictions on title page.
36
ANSI T1.253 Location Entity Code Structure
ELEMENTS/POSITIONS
Geographical Code
Geopolitical Code
Network Site Code
Network Entity Code
1 2 3 4
A A A A
5 6
7 8
9
10
11
A A
A A
A/N A/N A/N
or
ELEMENTS/POSITIONS
Geographical Code
Geopolitical Code
Network Site Code
Network Entity Code
1 2 3 4
A A A A
5 6
7 8
9
10
11
A A
N N
Proprietary - Licensed Material. See proprietary restrictions on title page.
A/N A/N A/N
37
Levels of Information Design
 Transactions
– Thousands
 Objects/attributes
– Hundreds of thousands
 Object/Attribute Values
– Millions
Must be actively managed & kept up to date
Proprietary - Licensed Material. See proprietary restrictions on title page.
38
ITU-T Rec. M.1400 Layer 1 - “Designation”
 Circuit ID
– Route termination identifiers




Town identification
Termination detail
Operator identification
Country code
– Function code
– Serial number
Proprietary - Licensed Material. See proprietary restrictions on title page.
39
Number of
characters
Letters
Hyphen
Letters or
space
Slash
Letters or
digits
Slash
Letters or
digits
Slash
Letters
Space
Letters or
digits
Digits
6
1
3
1
 12 1
3
1
6
4
Town B
Country Code
–
Slash
1
Operator ID
6
/
Letters or
digits
Slash
1
Termination
detail
 12
/
Letters or
digits
/
Slash
Character
Types
Town A
Format of
designation
Letters or
space
/
Termination
detail
6
/
1
Operator ID
6
Proprietary - Licensed Material. See proprietary restrictions on title page.
/
1
Serial number
Function code
Country Code
M.1400 Layer 1 format “Designation”
Table 1/M.1400 - layer 1 designation format

No space
40
M.1400 Layer 2 for circuits designated in Layer 1
 Varies by Layer 1 Function code
 Many fields (up to 18), e.g.,
– Restoration urgency
– Network operator/service provider ID
– Bandwidth
– Routing
– Associated circuit
Proprietary - Licensed Material. See proprietary restrictions on title page.
41
M.1400 Layer 2 - “Related Information”
 1. Urgency for restoration
xxx…xx; (max 10 chars)
 2. Terminal countries
xxx,yyy; (3 chars for each per ISO 3166)
 3. Network operators ID
yyyyyy,zzzzzz; (max 6 chars each)
 4. Control and subcontrol stations
CS:
SCS1:
.
SCSn:
“designation”
“designation”
“designation”;
 5. Fault report points
“designations” for Towns A and B;
 6. Routing
designation(s) that carry the circuit;
Proprietary - Licensed Material. See proprietary restrictions on title page.
42
Attachment 2 (cont’d.)
M.1400 Layer 2 - “Related Information”
 7. Association
association code: designation of associated
circuit;
 8. Equipment information
xx,xx,xx,xx,xx;
 9. Use
xx,yyyy; (max 7 chars)
 10. Transmission medium
ST or -;
 11. Composition of transmission
 12. Bandwidth
A, N, C
xxxx.x Hz; or kHz; or MHz; or bit/s; or kbit/s; or Mbit/s
 13.Signalling type xx…..xx;
(max 20 chars)
Proprietary - Licensed Material. See proprietary restrictions on title page.
43
ITU-T Rec. M.1400 Application Schema Graph
Country
Operator
Town
Address
Transport
Relation
Route
Termination
Exchange
Position
Equipment
Route
S
Position
Proprietary - Licensed Material. See proprietary restrictions on title page.
Multiplex
channel
44