25:
432:
572:
The early focus of the TM Forum's NGOSS work was on building reference models to support a business stakeholder view on process, information and application interaction. Running in parallel were activities that supported an implementation stakeholder view on interface specifications to provide access
388:
model—Fault, Configuration, Accounting, Performance and
Security. This basis was adopted by the ITU-T TMN standards as the Functional model for the technology base of the TMN standards M.3000 – M.3599 series. Although the FCAPS model was originally conceived and is applicable for an IT enterprise
485:, formerly the TeleManagement Forum, is an international membership organization of communications service providers and suppliers to the communications industry. While OSS is generally dominated by proprietary and custom technologies, TM Forum promotes standards and frameworks in OSS and BSS.
299:
Many OSS systems were initially not linked to each other and often required manual intervention. For example, consider the case where a customer wants to order a new telephone service. The ordering system would take the customer's details and details of their order, but would not be able to
593:
Open
Digital Architecture (ODA) offers an industry-agreed blueprint, language and set of key design principles to follow. It will provide pragmatic pathways for the journey from maintaining monolithic, legacy software solutions, towards managing nimble, cloud based capabilities that can be
309:
the details from one screen into another—a process often referred to as "swivel chair integration". This was clearly another source of inefficiency, so the focus for the next few years was on creating automated interfaces between the OSS applications—OSS integration. Cheap and simple OSS
171:(BSS), operations support systems support various end-to-end telecommunication services. BSS and OSS have their own data and service responsibilities. The two systems together are often abbreviated OSS/BSS, BSS/OSS or simply B/OSS.
304:
directly—this would be done by a switch management system. Details of the new service would need to be transferred from the order handling system to the switch management system—and this would normally be done by a technician
396:
and core networks. Historically, many efforts have been spent in standardization fora (ITU-T, 3GPP) in order to define standard protocol for network management, but with no success and practical results. On the other hand
492:(NGOSS) program, which was established in 2000. This established a set of principles that OSS integration should adopt, along with a set of models that provide standardized approaches. NGOSS was renamed Frameworx.
380:
A fifth level is mentioned at times being the elements themselves, though the standards speak of only four levels. This was a basis for later work. Network management was further defined by the
569:). The behavior can be controlled through the use of process management and/or policy management to orchestrate the functionality provided by the services offered by the components.
411:
From 2000 and beyond, with the growth of the new broadband and VoIP services, the management of home networks is also entering the scope of OSS and network management.
450:
224:
Before about 1970, many OSS activities were performed by manual administrative processes. However, it became obvious that much of this activity could be replaced by
381:
356:
42:
418:
specification has defined the CPE WAN Management
Protocol (CWMP), suitable for managing home networks devices and terminals at the EML-NML interface.
277:
695:
573:
to OSS capability (primarily MTNM). The MTNM work evolved into a set of Web
Services providing Multi-Technology Operations System Interfaces
360:
778:
145:
798:
89:
621:
558:
401:
61:
468:
203:
108:
389:
network, it was adopted for use in the public networks run by telecommunication service providers adhering to ITU-T TMN standards.
68:
636:
269:
758:
141:
46:
75:
728:
281:
257:
318:
A lot of the work on OSS has been centered on defining its architecture. Put simply, there are four key elements of OSS:
535:) – now known as the Application Framework, an architecture (the Technology Neutral Architecture) and a lifecycle model.
793:
616:
57:
557:
The components interact through a common communications vehicle (using an information exchange infrastructure; e.g.,
631:
273:
194:
174:
The acronym OSS is also used in a singular form to refer to all the
Operations Support Systems viewed as a whole
392:
A big issue of network and service management is the ability to manage and control the network elements of the
157:
185:, industrial research labs, or OSS vendors. In general, an OSS covers at least the following five functions:
748:
611:
168:
35:
711:
682:
289:
245:
240:) which automated much of this activity. This was one of the driving factors for the development of the
237:
82:
733:
153:
199:
738:
301:
404:
protocol (Simple
Network Management Protocol) has become the de facto standard for internet and
148:
to manage their networks (e.g., telephone networks). They support management functions such as
691:
528:
502:
405:
229:
208:
578:
306:
285:
213:
161:
233:
189:
544:
393:
517:
787:
657:
513:
506:
562:
532:
260:
for a variety of OSS applications. OSS systems used in the Bell System include
249:
24:
363:(TMN) model. This established a 4-layer model of TMN applicable within an OSS:
488:
By 2005, developments in OSS architecture were the results of the TM Forum's
412:
149:
482:
293:
225:
182:
280:(TIRKS), and many more. OSS systems from this era are described in the
626:
599:
415:
261:
253:
175:
355:
During the 1990s, new OSS architecture definitions were done by the
574:
489:
385:
265:
743:
521:
398:
241:
763:
509:) – now more commonly referred to as the Information Framework,
773:
753:
656:
NTT Access
Network Service Systems Laboratories (April 2003).
582:
566:
524:) – now more commonly known as the Business Process Framework,
425:
18:
539:
The TM Forum describes
Frameworx as an architecture that is:
310:
integration remains a major goal of most telecom companies.
595:
768:
759:
InsideTelephony OSS/BSS (2017.05.20 via
Wayback Machine)
181:
Different subdivisions of OSS have been proposed by the
446:
598:. It is a reference architecture that maps TM Forum’s
341:
the components that implement processes to manage data
602:against technical and business platform functions.
441:
may be too technical for most readers to understand
49:. Unsourced material may be challenged and removed.
202:, including the network inventory, activation and
577:. Most recently, the OSS through Java initiative
16:Systems used to manage telecommunication networks
408:management, at the EML-NML communication level.
589:Ongoing work - Open Digital Architecture (ODA)
581:joined the TMF to provide NGOSS-based BSS/OSS
490:New Generation Operations Systems and Software
268:, Remote Memory Administration System (RMAS),
8:
357:ITU Telecommunication Standardization Sector
749:OSS Observer landing page of Analysys Mason
469:Learn how and when to remove this message
453:, without removing the technical details.
109:Learn how and when to remove this message
684:Telecommunications Systems and Standards
648:
278:Trunks Integrated Record Keeping System
507:Shared Information/Data model, or SID
451:make it understandable to non-experts
361:Telecommunications Management Network
7:
252:purchased their own product line of
146:telecommunications service providers
47:adding citations to reliable sources
690:. World Technologies. p. 16.
622:Loop maintenance operations system
333:the information that is acted upon
228:. In the next 5 years or so, the
14:
349:how we implement the applications
430:
23:
637:Switching Control Center System
367:Business Management Level (BML)
270:Switching Control Center System
34:needs additional citations for
774:Telecommunications OSS and BSS
518:enhanced Telecom Operation Map
376:Element Management Level (EML)
373:Network Management Level (NML)
370:Service Management Level (SML)
1:
282:Bell System Technical Journal
258:Digital Equipment Corporation
144:are computer systems used by
739:OSS through Java initiative
712:"Open Digital Architecture"
617:COSMOS (telecommunications)
130:operational support systems
58:"Operations support system"
815:
799:Telecommunications systems
190:Network management systems
122:Operations support systems
632:Service Evaluation System
274:Service Evaluation System
244:operating system and the
533:Telecom Applications Map
169:business support systems
764:Billing & OSS World
729:Video: What is OSS/BSS?
612:Business support system
662:ANSL R&D Times #32
325:the sequence of events
290:Telcordia Technologies
246:C programming language
681:Latonia Gist (2013).
238:software applications
158:network configuration
132:in British usage, or
232:created a number of
154:service provisioning
43:improve this article
594:orchestrated using
230:telephone companies
200:Service fulfillment
794:Network management
658:"Operation system"
302:telephone exchange
779:Telcordia SR-2275
754:Pipeline Magazine
697:978-81-323-4238-0
529:application model
503:information model
479:
478:
471:
209:Service assurance
150:network inventory
119:
118:
111:
93:
806:
716:
715:
708:
702:
701:
689:
678:
672:
671:
669:
668:
653:
496:Frameworx models
474:
467:
463:
460:
454:
434:
433:
426:
286:Bell Labs Record
234:computer systems
195:Service delivery
162:fault management
134:Operation System
114:
107:
103:
100:
94:
92:
51:
27:
19:
814:
813:
809:
808:
807:
805:
804:
803:
784:
783:
744:OSS News Review
725:
720:
719:
710:
709:
705:
698:
687:
680:
679:
675:
666:
664:
655:
654:
650:
645:
608:
591:
553:component based
545:loosely coupled
498:
475:
464:
458:
455:
447:help improve it
444:
435:
431:
424:
359:(ITU-T) in its
316:
256:computers from
222:
115:
104:
98:
95:
52:
50:
40:
28:
17:
12:
11:
5:
812:
810:
802:
801:
796:
786:
785:
782:
781:
776:
771:
766:
761:
756:
751:
746:
741:
736:
731:
724:
723:External links
721:
718:
717:
703:
696:
673:
647:
646:
644:
641:
640:
639:
634:
629:
624:
619:
614:
607:
604:
590:
587:
555:
554:
551:
548:
537:
536:
525:
510:
497:
494:
477:
476:
459:September 2008
438:
436:
429:
423:
420:
378:
377:
374:
371:
368:
353:
352:
351:
350:
344:
343:
342:
336:
335:
334:
328:
327:
326:
315:
312:
300:configure the
221:
218:
217:
216:
211:
206:
197:
192:
167:Together with
117:
116:
99:September 2024
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
811:
800:
797:
795:
792:
791:
789:
780:
777:
775:
772:
770:
767:
765:
762:
760:
757:
755:
752:
750:
747:
745:
742:
740:
737:
735:
732:
730:
727:
726:
722:
713:
707:
704:
699:
693:
686:
685:
677:
674:
663:
659:
652:
649:
642:
638:
635:
633:
630:
628:
625:
623:
620:
618:
615:
613:
610:
609:
605:
603:
601:
597:
588:
586:
584:
580:
576:
570:
568:
564:
560:
552:
549:
546:
542:
541:
540:
534:
530:
526:
523:
519:
515:
514:process model
511:
508:
504:
500:
499:
495:
493:
491:
486:
484:
473:
470:
462:
452:
448:
442:
439:This section
437:
428:
427:
421:
419:
417:
414:
409:
407:
403:
400:
395:
390:
387:
383:
375:
372:
369:
366:
365:
364:
362:
358:
348:
347:
345:
340:
339:
338:Applications
337:
332:
331:
329:
324:
323:
321:
320:
319:
313:
311:
308:
303:
297:
295:
292:(now part of
291:
287:
283:
279:
275:
271:
267:
263:
259:
255:
251:
247:
243:
239:
235:
231:
227:
219:
215:
214:Customer care
212:
210:
207:
205:
201:
198:
196:
193:
191:
188:
187:
186:
184:
179:
177:
172:
170:
165:
163:
159:
155:
151:
147:
143:
139:
135:
131:
127:
123:
113:
110:
102:
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
706:
683:
676:
665:. Retrieved
661:
651:
592:
571:
563:Web Services
556:
538:
487:
480:
465:
456:
440:
410:
391:
379:
354:
317:
314:Architecture
298:
223:
204:provisioning
180:
173:
166:
137:
133:
129:
125:
121:
120:
105:
96:
86:
79:
72:
65:
53:
41:Please help
36:verification
33:
550:distributed
346:Technology
296:) SR-2275.
250:Bell System
788:Categories
667:2021-01-25
643:References
384:using the
322:Processes
69:newspapers
600:Open APIs
413:DSL Forum
307:re-keying
264:, CSOBS,
226:computers
769:OSS Line
734:TM Forum
627:OA&M
606:See also
483:TM Forum
422:TM Forum
294:Ericsson
272:(SCCS),
183:TM Forum
579:(OSS/J)
445:Please
276:(SES),
248:. The
220:History
83:scholar
694:
416:TR-069
394:access
288:, and
262:AMATPS
254:PDP-11
176:system
85:
78:
71:
64:
56:
688:(PDF)
575:MTOSI
531:(the
520:, or
516:(the
505:(the
406:telco
386:FCAPS
330:Data
266:EADAS
140:) in
90:JSTOR
76:books
692:ISBN
583:APIs
522:eTOM
481:The
402:SNMP
399:IETF
242:Unix
236:(or
160:and
62:news
567:EJB
559:EAI
527:An
501:An
449:to
382:ISO
142:NTT
138:OpS
128:),
126:OSS
45:by
790::
660:.
596:AI
585:.
565:,
561:,
512:A
284:,
178:.
164:.
156:,
152:,
714:.
700:.
670:.
547:"
543:"
472:)
466:(
461:)
457:(
443:.
136:(
124:(
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
